AGENTVAULT
LIVE BOT Chain Mainnet
syncing… …
AGENTVAULT · LIVE ON BOT CHAIN MAINNET

The vault
that says no.

VaultMind's AI agent holds its own key and spends from this vault — but only inside the policy the owner set on-chain. Over the cap, the chain itself refuses.

Vault Balance
…BOT
Held by the vault contract on BOT Chain mainnet · read live from chain
Chain ID 677Native token BOTExplorer scan.botchain.aiDeployed 7 Nov 2026
…
AgentVault vault emblem
Policy vault · BOT Chain mainnet
Daily budget used…
Vault funds remaining…
Largest payment vs per-tx cap…
View contract on scan.botchain.ai Executed spend · 0.005 BOT GitHub repository
Launch record · 7 Nov 2026 · verified on scan.botchain.ai
9
successful core-product transactions on mainnet
3
acting wallets: owner, agent and a third depositor
0.06 BOT
deposited into the vault in total
0.015 BOT
paid out by the agent, inside the caps
0.5 BOT
single payment rejected by the policy gate

How VaultMind works

An AI copilot manages the money, an on-chain vault enforces the rules. Three steps, no trust required.

01

Fund your own vault

Every vault holds its owner’s own funds. VaultMind does not pool funds and does not accept deposits from third parties. The website functions as an interface for configuration and monitoring; transfers occur on-chain between the vault and the recipient.

02

Set your own limits

The vault owner sets the policy: a per-payment cap, a daily cap, a recipient allowlist, and a freeze switch. This public demonstration deployment is configured with tight limits (0.01 BOT per payment, 0.025 BOT per day) because it holds real mainnet funds with an autonomous agent attached. Production deployments are configured by their respective owners, including their own limits.

03

The agent pays inside the rules

The agent can pay only within the policy. A payment that exceeds the caps, is directed to a recipient outside the allowlist, or is attempted while the vault is frozen, reverts on-chain.

Limits shown here are the policy settings of this deployment.

How a Payment Moves
the core VaultMind flow, live on this vault
👤
Owner
sets policy, funds the vault, can freeze
caps + allowlist→
🛡︎
Policy Vault
holds 0.04 BOT, checks every payment
agentSpend→
🤖
AI Agent
spends only inside the caps
0.005 BOT ✓→
🎯
Recipients
Wallet 1 + Wallet 2, allowlisted only
Over the cap, the chain says no: a 0.5 BOT payment from the agent reverted on this vault because it exceeded the 0.01 BOT per-transaction limit.

This dashboard presents a demonstration deployment operated by its owner. VaultMind does not provide custody services and does not accept deposits from third parties. Each vault deployment is funded and operated solely by its respective owner.

Live deployment data — read from the contract
Spent today — this deployment
…BOT
resets daily, on-chain counter
Per-payment limit — this deployment
…BOT
any single payment above this reverts
Daily limit — this deployment
…BOT
total the agent may move per day
Ownership
2-of-3 multisig Safe
Safe 0x6008…5e90 · changes need 2 of 3 signatures

These limits are the vault owner’s own policy settings, read live from the contract. This public demo runs deliberately tight limits because it holds real mainnet funds with an autonomous agent attached. Production deployments are configured by their respective owners, including their own limits.

Receipt · agent spend
0.005 BOT
Paid toWallet 1 · allowlisted
Policy check0.005 ≤ 0.01 BOT per-tx cap
ResultExecuted
Verify this payment on scan.botchain.ai ↗
Receipt · agent spend attempt
0.5 BOT
Paid toWallet 1 · allowlisted
Policy check0.5 > 0.01 BOT per-tx cap
ResultRejected
Reverted on-chain, no funds moved. A reverted payment emits no event, so this is a verified demo record with no transaction link.
Use the Vault
the core product flow, run from this page

No wallet connected. Connect a wallet to run the core VaultMind flow from this page: the owner can fund the vault, manage the recipient allowlist and pull the freeze switch, and the registered agent can pay inside the policy caps. The live reads above keep working without a wallet.

Policy Gate
checked on every spend
Agent identity
only the registered agent key can spend
…
Recipient allowlist
payments only to allowlisted services
…
Spending caps
per-transaction and daily limits enforced
…
Freeze switch
owner can halt all agent spending instantly
…
A payment that fails any check reverts on-chain. In the live demo, a 0.5 BOT payment was rejected for exceeding the per-transaction cap.
Keys & Parties
Vault Activity
loading on-chain events…
On-chain rows are the contract's real event history, read via eth_getLogs from the BOT Chain RPC. The rejected payment is a verified demo record: a reverted transaction emits no event, so it carries no block or transaction link.
Contract
BOT Chain Mainnet · Chain ID 677
0x666dc10b61e05aab26673463170b7f5ac920825d
AgentVault contract address
scan.botchain.ai
…
first on-chain activity (block 29,438,681)
…
events recorded
Built on BOT Chain
Mainnet · Chain ID 677 · botchain.ai · scan.botchain.ai
Owner controls
policy, allowlist, agent key, freeze and withdrawals stay with the owner
Source code
Built on BOT Chain
AgentVault runs on BOT Chain mainnet. Explore the network and verify every transaction on the official explorer.
botchain.aiscan.botchain.ai