Skip to main content
In short: a new account fixes a list of the operations the agent may ever run for you. Before a plan runs, a zero-knowledge proof shows that every step is on your list, and a contract on the network checks that proof. On Base, Arbitrum and HyperEVM the agent cannot run anything outside the list. Ethereum does not check the proof yet (see below). The proof does not show that you asked for the plan, and it does not cap how much a step moves. Accounts created here are proved accounts, also called v2. An account made earlier keeps the older kind, called v1, and stays at its address.

​
What you get

The older kind installs each approved operation on your account, one by one. A proved account installs one door instead. The list of what that door may open is part of your account’s address. Every operation still has its own checks. The proof is an extra layer. It is not a replacement.

​
What the proof says

It says: every step in this plan is inside the list the owner committed. A contract verifies it on the network before the first step runs. Each step then draws against the plan the proof covered. It does not say you signed the plan. Anyone may generate a proof for a plan built from your list. So a compromised agent could still prove and run any plan that stays inside your list.
A proved account does not make a stolen agent safe on its own. The agent still chooses the amounts and the route for each step. The same limits apply as on an older account: it can only pay you or your account, a daily limit applies if you set one, and loans stay under the ceiling. The proof adds the list.

​
What you can still do

Each of these needs your own key and takes effect at once, even in the middle of a plan:
  • refuse one operation;
  • narrow the list;
  • end a plan that is running, so the rest of it is refused;
  • tighten your loan ceiling or set a daily limit;
  • stand the agent down.
You can always leave. Your wallet owns the account on every network, and an exit never needs the proof system.

​
The list follows our additions

The standard list covers every operation we offer. When we add an operation, it joins your list after a three-day notice. You do not sign anything. You can opt out by pinning your list, and then it stays as it is. This applies on Base, Arbitrum and HyperEVM. If you hold a key, the standard list also lets the agent send the proceeds of a plan back to your own wallet. If you asked the console to create your address and nobody holds its key, it does not, because money sent there would be lost.

​
Ethereum runs the older way

On Ethereum, a proved account’s steps are not proved. Operations install on the account as they do on an older account, and anyone may trigger that install. Only operations we approved can install, after the three-day wait, so the result matches what our own servers would install.
The address of a proved account does not change when a network is added or when the list grows. The list is fixed to names, not to contract code. A new version of an operation’s contract works under the same name once it passes the three-day wait.

​
Stops

We can switch the proved path off for a network, for one circuit version, or for one list, with one key touch. Your exit is not affected. See Emergency stops.

​
Under the hood

For integrators.
  • The account’s genesis installs the installer and a policy executor. The policy executor is the only door for the agent’s calls.
  • A circuit proves each step’s operation and adapter against two trees: your capabilities and the registry’s adapters. The proving system is Groth16, verified by a contract.
  • A plan’s allowance is declared in the proof and charged against the daily limit if one exists.
  • An account’s first step on a network where it is not deployed yet is judged under the list it will follow once deployed.
  • A worker must hold the matching proving key for a network, or a proved account cannot run there.