The trading key and the guardian
What our engine's trading key does, and how the separate guardian watches every vault trade.
Two platform keys touch your vault. The trading key (the operator) sends your agent's trades. The guardian is a separate watchdog that can stop all trading if something looks wrong. Neither can withdraw.
The trading key
Our engine runs your agent's AI and, when a trade passes every check, uses the trading key to ask your vault to swap. The vault re-checks everything on-chain: the route, your caps, the sell limiter, and that no pause is on. It also claims your token's creator fees for the vault. It pays the gas for these calls.
The guardian
The guardian runs as its own service, with its own key, and watches every vault transaction. It steps in when it sees:
- a vault trade that doesn't match any decision the engine recorded;
- a sell at a price more than 20% below the pool's recent price;
- a burst of sells across many vaults in a short time;
- a trade through a pool that isn't on the approved list.
Then it pauses trading for every vault at once. Only the platform admin can resume. Your Withdraw and Emergency exit keep working throughout.
How it works under the hood
- The guardian compares every on-chain vault swap with the engine's records and with a reference price built from several quotes over a few minutes.
- It can also remove a pool from the trading list at once.
- Its key is separate from every engine key, and it uses its own restricted database role.
- Trading can also be switched off platform-wide by the engine's kill switch: then vault trades are held, never simulated.