Account policy
Approved versions
Under EIP-7702 the guard runs at the account’s own address, so this list lives in the account’s storage rather than in a shared registry. Each entry names one exact set of bytes. Nothing else can move funds.
2 approvals
kuru-quote1.0.0
1 capability · ceiling no native value
helix-lend2.4.1
3 capabilities · 1 high risk · ceiling 0.5 MON
Settled
Executed under an approved pin
Each row is a SkillExecuted event from the account. The pin and hash recorded here are what the guard checked before letting the calls through.
| Skill | Hash checked | Executor | Calls | When |
|---|---|---|---|---|
| kuru-quote | 1 | 2026-02-25 | ||
| helix-lend | 2 | 2026-02-25 | ||
| kuru-quote | 1 | 2026-02-24 |
The executor is not the account
An agent holds an executor key, which pays gas and can ask the guard to run a batch. It never holds the account key. That separation is what makes the guard enforceable rather than advisory: an agent holding the account key could sign straight past it, so the chain adapter refuses to start if the two are ever the same.