Warden
A gasless, policy-gated firewall for autonomous on-chain agents, enforced on-chain instead of in a prompt.
- Six on-chain policies enforced in the EVM before any signature exists
- Gasless execution via an EOA Paymaster
- Refuse-and-record model: blocked actions stay on-chain as Decision events instead of silent reverts
- Separate owner and agent keys: the agent can only call screenAndExecute, never move funds unilaterally
An LLM agent can propose an on-chain action, but it can never sign one on its own. WardenGuard sits between the agent and the chain: every proposed action is checked against six policies (per-tx spend cap, rolling 24h budget, destination allowlist, cooldown, slippage ceiling, session balance) inside the EVM before a signature exists. Actions that pass execute gaslessly through an EOA Paymaster; actions that fail are refused and recorded, not just rejected client-side.
Refusals don't revert. A hard revert would enforce the policy but drop the record of the attempt, since reverted transactions emit no persistent events. WardenGuard emits a Decision event either way, so every allowed or blocked action stays on the permanent chain history: a tamper-evident audit trail of agent behavior, built for the BOT Chain Builder Challenge's AI Agent track.