Skip to main content

Signo compared: trading bots, session keys, delegations and spend vaults

Signo is the one way to let an AI agent act on your DeFi wallet, among those compared here, that keeps your wallet as it is and your key with you, enforces your limits in a contract, checks the result of each action, and needs no developer. Signo gives you AI agents that watch your DeFi positions around the clock. Each agent follows a position or a market condition you choose, alerts you on Telegram when it matters, and prepares the next step for you to review and sign in your own wallet. Signo never holds your funds.

Last verified: 16 October 2026. Every fact about another product comes from that product's own documentation, linked in Sources.

At a glance​

ApproachWallet unchangedKey stays with youLimits in a contractResult checkedNo developer needed
SignoYesYesYesYesYes
Trading bots
Banana Gun, BONKbot
No: the bot holds itNoNo: service settingsNoYes
Session keys
ZeroDev, Biconomy
No: a smart accountYesIf the developer sets a policyNoNo
EIP-7702 delegations
MetaMask
No: account upgradedYesIf caveats are setWith a balance caveatNo
Spend vaults
MoonPay PayBox, Coinbase CDP
No: a provider walletNo: provider MPC or enclaveNo: provider policyNoPayBox only
Automation
DeFi Saver
No: a Safe or DSProxyYesYesYes: ratio checksYes
Alert-only tools
DeFi Saver Notify, Tenderly
YesYesNothing movesNothing movesYes

Wallet unchanged: you keep using the wallet you have, with no new account or upgrade. Result checked: a contract checks the outcome after each action, not only the call before it; "No" means the product's own docs describe no such check. For Signo, the contract and result columns apply to Execute agents; Notify and Prepare agents never move funds without your signature.

Why Signo​

  • Your wallet stays as it is. No smart account to deploy, no account upgrade, no new wallet to fund. You connect the wallet you already use.
  • Your key stays with you. Notify and Prepare agents never sign: you sign each prepared plan in your own wallet. Signo never receives your private key or seed phrase.
  • Limits in a contract, not in a settings page. An Execute agent acts only inside a permission you sign in the Signo Shield contract: one action, one token, the exact venue contracts, a limit per firing, a lifetime limit and an expiry.
  • The result is checked, not only the call. The Shield re-reads the trigger onchain when the chain can read it, and checks a required result after the action, such as "your debt fell". If any check fails, the whole transaction reverts and nothing moves.
  • AI that plans, not only a fixed strategy. You describe the condition and the response in plain English. The agent watches it and prepares or performs the next step.
  • You can stop it yourself. Revoke a permission onchain at any time, with no approval from Signo.

What to know:

  • Execute is in early access, on X Layer and Arbitrum. Notify and Prepare are open to everyone.
  • Agents check on a schedule, about once an hour for most conditions, not continuously.
  • The Shield contracts went through 15 review passes. They have not been formally audited. The code is public in the signo-shield repository.
  • Signo charges 0.1% of what each Execute firing spends.

Details: Give an AI agent limited spending rights, What you authorize with an Execute agent and Security.

Notes on each approach​

Trading bots that store the wallet key. In Banana Gun you create a wallet in the bot or import one with a private key, and a deleted wallet is removed from its server. BONKbot generates and seals keys in a secure execution environment, says no one, BONKbot included, can view, extract or use them, and calls its setup non-custodial. Its Signer matches each transaction to a blueprint you approved, and 2FA for each transaction is optional. Slippage settings are yours to set; in Banana Gun, 100% slippage counts as unlimited.

Session keys. ZeroDev and Biconomy let an owner authorize a key for an app or an agent, with policies for targets, functions, arguments, gas, rate, time and usage. Biconomy says its policies are enforced onchain by smart contracts and that a failed check reverts. What the key can do depends on the policy a developer writes.

EIP-7702 delegations. EIP-7702 is a final standard. ERC-7710 (delegations) and ERC-7715 (permission requests) are drafts. In the MetaMask Smart Accounts Kit, caveat enforcer contracts limit what a delegate can do, and the delegation manager calls them before and after each execution. In MetaMask's guide, the delegate is a session account that holds no tokens. By default, a delegation with no caveats allows any onchain action.

Spend vaults and agent wallets. MoonPay PayBox keeps the key in an MPC system inside secure hardware (a TEE), gives agents signatures and never key shares, and lets you choose per grant to always approve, approve above a limit, or let the agent act within a policy. Each approval is tied to one operation. A kill switch revokes all agents. Coinbase CDP wallets keep keys in AWS Nitro Enclaves, and a policy engine accepts or rejects a signing request by value and address.

Automation services. DeFi Saver Automation runs strategies through your Safe or DSProxy. Only its approved bots can call a strategy, the bots hold no rights over your funds, and the contracts check that every trigger is true and that the resulting ratio is in range.

Alert-only tools. DeFi Saver Notify and Tenderly Alerts send notifications and move nothing. HAL, an earlier alert service, shut down on 1 June 2024, as a post on the Aave governance forum notes.

Sources​

All read on 16 October 2026.