AGENTVAULT
LIVE
BOT Chain Mainnet
syncing…
…
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
Daily budget used…
Vault funds remaining…
Largest payment vs per-tx cap…
Spent today
…BOT
resets daily, on-chain counter
Per-transaction cap
…BOT
any single payment above this reverts
Daily cap
…BOT
total the agent may move per day
STEP 1
Owner sets the policy
VaultMind's owner fixes the rules on-chain: a per-transaction cap, a daily cap, and the list of recipients the agent is allowed to pay.
STEP 2
Agent spends inside the caps
The AI agent holds its own key and pays for services from the vault. Any payment outside the policy reverts on-chain, no exceptions.
STEP 3
Every move is auditable
Deposits, spends and policy changes are recorded as events on BOT Chain, so the copilot and the owner always see the same truth.
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.
Use the Vault
the core product flow, run from this pageNo 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 spendAgent 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 6770x666dc10b61e05aab26673463170b7f5ac920825d
AgentVault contract address
…
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
Built on BOT Chain
AgentVault runs on BOT Chain mainnet. Explore the network and verify every transaction on the official explorer.