Verify a Safe
Check what a trading bot's session key can do with a Safe — read live from the chain, for any address. It shows the Safe's owners, its modules, who controls the validator, and every bot session with its rules decoded into plain words. Anything that isn't an approve, a pinned swap or a fee transfer is flagged.
How to read this
- Safe owners and validator owners should be your own wallet only. They are the keys that can withdraw.
- Each bot session is a key held by the bot's server. On-chain rules (UniActionPolicy) decide what it may call; this page decodes those rules.
- A DCA Bot session should allow only three things: approve the Uniswap router, swap one pinned pair back into this Safe, and transfer the fee token to DCA Bot's fee wallet. Anything else is marked look at this.
- What the rules do not cap: the fee amount and the swap's minimum output are computed by our server. The threat model explains what that means if our server were compromised.
- Everything is read live from the chain through a public RPC. Nothing comes from our database.