liveBV Authorized Agents

Hand an AI agent the work. Keep the keys. Revoke in one click.

BV Authorized Agents sits between your wallet and any AI system acting on your behalf. You write the mandate — what the agent can do, how much, until when. The contract enforces it. One transaction shuts it off.

What it is, in one paragraph

You have a treasury. You'd like an AI agent to do the boring parts — rebalance positions weekly, roll futures, sweep stable yield — without giving it the actual keys. BV Authorized Agents is the contract layer that sits between your wallet and the agent. You write a mandate ("you can trade up to $5M of MXD per day in BVNRG forwards, expiry in 90 days"). The agent acts inside that envelope or not at all. You can shut it off in one transaction.

Why this matters

Most "AI agent" treasury products on the market today fall into two categories:

  1. Read-only dashboards — the agent recommends, a human executes. Safe but slow; defeats the point.
  2. Full key delegation — the agent has the keys. Fast but a bad day means a drained wallet.

BV Authorized Agents is the third option: bounded execution. The agent acts immediately within the bounds; it cannot act outside them; you can revoke faster than it can mis-trade.

How it works (the technical bit)

Skip this section if you're not the engineer. The audit story:

  • Mandate scope: per-market caps, daily volume limits, an allowlist of contract function selectors the agent can call, and an expiry timestamp. All on-chain.
  • Revocation: instant, single-transaction, no notice period.
  • Audit trail: every agent call is signed against a mandate ID that ties back to the policy you wrote. Every action is in the public ledger.
  • EIP-7702 native: when the chain supports it, mandates use 7702 delegations directly. On pre-7702 chains, an equivalent CREATE2 proxy pattern provides the same guarantees.
  • Multi-mandate: one wallet can hold many mandates to many different agents or strategies, each scoped independently.

What a real mandate looks like

A treasurer typically grants one of these patterns:

  • Roll-forward agent: can close expiring BVNRG/BVGPU positions and open the equivalent next-period contract; cap $X notional per week; cannot withdraw to any external address.
  • Yield-harvest agent: can claim accrued yield from tranche positions and re-deposit; cannot reduce position size.
  • Rebalance agent: can move between specified MXD positions up to a target weight delta; cap on slippage.

In each case, the agent has authority for one job, can't escalate, and you can fire it instantly.

Get started

Talk to us about scoping a mandate for your treasury setup. We'll walk through what the agent should be able to do, what it absolutely cannot do, and the right cap structure for your risk tolerance.