How this works
1
Human approves a mandate
A spending limit + recipient allowlist, installed once on the smart account's agent-scoped context rule.
2
Agent proposes payments
Signed with the agent's own Ed25519 key — a separate identity the admin can't be impersonated by.
3
Soroban checks the mandate
Every payment is verified on-chain by the mandate policy contract before it can settle.
4
Admin can adjust it later
A second, admin-only context rule — unreachable by the agent's key — lets the limit or allowlist change without redeploying.
Limit per transaction
…
Adjustable by the mandate's admin
Allowed payees
…
Settled this session
0
Confirmed on testnet
Rejected this session
0
Blocked by the mandate
Propose a payment as the AI agent
Manage the mandate as the human admin — the agent's key cannot reach this
Activity
| Time | Recipient / action | Amount | Status | Reference |
|---|---|---|---|---|
| No payments proposed yet this session | ||||