AgentVault

Policy-bound treasuries for autonomous agents on BOT Chain.

AgentVault gives AI agents a controlled treasury they can use without taking full custody of user funds. Owners define policies such as allowed actions, daily spend limits, agent roles, and emergency pause. A hosted worker signs as the approved agent, executes through the deployed vault contract, and exposes every transaction through the app and BOT Chain explorer.

Live Links

• App: https://agentvault-frontend.vercel.app
• Worker status: https://agent-vault-1.onrender.com/status
• Repository: https://github.com/0xNexuz/agent-vault
• BOT Chain explorer: https://scan.bohr.life

What It Does

• Connects BO Wallet or any injected EVM wallet.
• Switches to BOT Chain testnet.
• Lets owners configure agent roles, allowed actions, daily limits, and emergency pause.
• Supports single proposal signing and one-shot policy bundle signing.
• Shows live hosted-agent activity after the browser wallet is disconnected.
• Displays latest tx hash, block number, vault address, agent wallet, and explorer link.
• Indexes recent AgentExecution logs and exposes a public vault activity view.
• Monitors the hosted agent wallet gas balance and execution threshold.
• Scores agent reliability using heartbeat, gas, bytecode, and execution history.
• Includes Trader, Bridge Guardian, Rewards Operator, and DAO Ops policy templates.
• Deploys new vaults from the browser, with verified BDEX V2 target and selector policy for Trader vaults.
• Delivers confirmed-transaction alerts through browser notifications, Telegram, email, or webhooks.
• Creates shareable vault and referral links.
• Exports an audit log covering approvals, policies, manual wallet txs, and autonomous agent txs.

BOT Chain Testnet

Chain ID: 968 / 0x3c8
RPC: https://rpc.bohr.life
Native token: BOT
Explorer: https://scan.bohr.life

BOT Chain Mainnet

Chain ID: 677
RPC: https://rpc.botchain.ai
Native token: BOT
Explorer: https://scan.botchain.ai

Architecture

flowchart TD
  U["Owner / user"] --> FE["AgentVault frontend on Vercel"]
  FE --> W["Injected wallet: BO Wallet / EVM wallet"]
  FE --> R["Render worker API"]
  W -->|personal_sign| A["Owner approval intent"]
  W -->|optional owner tx| C["BOT Chain testnet"]
  R --> AG["Hosted agent worker"]
  AG -->|signs with AGENT_PRIVATE_KEY| V["AgentVault smart contract"]
  V -->|AgentExecution / protocol call| C
  C --> E["BOT Chain explorer"]
  R --> IX["Event indexer + gas monitor"]
  IX -->|activity, score, vault state| FE
  R --> N["Email / Telegram / webhook alerts"]
  FE -->|Open transaction| E

Loading

Smart Contract

The vault contract is in contracts/AgentVault.sol.

It enforces:

• owner-only configuration
• allowed agent addresses
• allowed action IDs
• daily spend limits
• event receipts for agent execution
• protocol target and function-selector allowlists
• reentrancy protection and owner withdrawals
• BDEX V2 calls from newly deployed, funded vaults

Current BOT testnet deployment:

Vault: 0xacACe949cdf6f2202F2c510d5D0674af97C11b87
Agent: 0xe5ABF60A6855048fEd12938aA6C699c86C09b915

Current BOT mainnet deployment:

Vault: 0xacACe949cdf6f2202F2c510d5D0674af97C11b87
Owner: 0x9CBc32a0aCDe85f4e25b23eb064f46EE788bA4d6
Agent: 0xe5ABF60A6855048fEd12938aA6C699c86C09b915
Daily limit: 50 BOT
Explorer: https://scan.botchain.ai/address/0xacACe949cdf6f2202F2c510d5D0674af97C11b87

The mainnet and testnet vault addresses match because the same deployer address used nonce 0 on both chains. They are separate contracts on separate networks.

Local Setup

npm install
npm run dev

Use .env.example for local environment values.

Guided Vault Setup

This creates fresh testnet-only deployer and agent wallets, prints the public addresses to fund, deploys the vault when both have BOT, and saves the vault address locally.

npm run setup:agentvault

Never commit .env or paste private keys into chat.

Hosted Agent

Run locally:

npm run agent:worker

Production worker:

https://agent-vault-1.onrender.com/status

The worker submits a new agent execution roughly every 60 seconds, depending on RPC and hosting latency. The hosted demo remains in proof mode. Newly deployed vaults can use bdex-v2 mode after the owner configures the verified router policy and funds the vault with test BOT.

Worker API:

GET /status                 latest heartbeat and transaction
GET /api/activity           indexed AgentExecution events
GET /api/vault              hosted vault state and agent score
GET /api/vault?address=...  public state for a shared AgentVault
GET /health                 service and gas health

To run the hosted worker against mainnet, set the host environment to:

BOT_CHAIN_ID=677
BOT_NETWORK_NAME=BOT Chain Mainnet
BOT_RPC_URL=https://rpc.botchain.ai
BOT_EXPLORER_URL=https://scan.botchain.ai
VAULT_ADDRESS=0xacACe949cdf6f2202F2c510d5D0674af97C11b87
AGENT_PRIVATE_KEY=...

Leaving these unset keeps the worker on the current BOT testnet defaults.

Production Build

npm run build

Deploy

Frontend:

vercel --prod

Worker:

Build command: npm install
Start command: npm run agent:worker

Required worker environment variables:

BOT_TESTNET_RPC_URL=https://rpc.bohr.life
BOT_TESTNET_EXPLORER_URL=https://scan.bohr.life
AGENT_PRIVATE_KEY=...
VAULT_ADDRESS=...
AGENT_INTERVAL_MS=60000
AGENT_ACTION_AMOUNT_BOT=0
AGENT_EXECUTION_MODE=proof
AGENT_GAS_THRESHOLD_BOT=0.05
AGENT_INDEX_LOOKBACK_BLOCKS=25000
AGENT_INDEX_CHUNK_BLOCKS=5000

Execution modes:

proof     Emits a policy-scoped AgentExecution receipt without moving assets.
bdex-v2   Swaps vault BOT through the allowlisted BDEX V2 selector and router.
bridge    Executes owner-reviewed BRIDGE_CALLDATA through the configured bridge selector.

Optional alerts:

TELEGRAM_BOT_TOKEN=...
TELEGRAM_CHAT_ID=...
RESEND_API_KEY=...
ALERT_EMAIL_TO=...
ALERT_EMAIL_FROM=AgentVault <alerts@example.com>
ALERT_WEBHOOK_URL=https://...