Rules sealed in the mandate
Limits are fields of the policy, hashed into its root. A payment outside them has no valid authorisation, so there is nothing to approve.
Private banking & policy for autonomous agents
An account your agent cannot overspend.
Give an agent money the way a private bank gives a family office a mandate: a lifetime budget, a daily ceiling, a list of who it may pay, and a date the mandate ends. Every payment is checked against the sealed policy before it leaves. Auditors see one fact, never the book.
CA
VAULTAGENTMandate
•••• •••• •••• ••••
Agentresearch-desk-01
Valid thru—
- Loading the policy…
Policy root —
Principles
One fact, not the book
Show a lender the daily ceiling, or an auditor the end date. Each clause opens alone with a Merkle proof; the others stay sealed.
Audit against the chain
Any Solana wallet's real history can be replayed against a mandate: what it paid, to whom, and which clause each payment would have broken.
Draft the mandate
Every field becomes a numbered clause. The policy is hashed with SHA-256 and each clause, salted, becomes a leaf of a Merkle tree whose root seals the whole document.
Mandate · Schedule A
research-desk-01
Issued —
- Policy SHA-256
- —
- Merkle root of salted clauses
- —
Present a payment to the mandate
The agent proposes a payment and signs the intent with its own Ed25519 key, generated in this browser. The mandate checks every clause. Approved payments join this session's ledger, so the ceilings fill up. Simulation
Checks
- Present a payment to see each clause tested.
Session ledger
What happens to a payment, clause by clause
The last payment you presented, replayed through the mandate's six gates.
Disclose one clause, keep the rest sealed
Pick the clauses an auditor or lender may see. You hand over a package: the root, the opened clauses with their salts, and the sibling hashes up to the root. The verifier recomputes it in their own browser.
Open which clauses?
Verifier
Agent budget dashboard
A seeded simulation of how an agent with your spending habits lives inside this mandate: daily spend against the ceiling, payments the policy refused, and the day the budget runs out. Simulation
Spent—
Payments refused—
Days at ceiling—
Budget lasts—
Seed —
Audit a live wallet against the mandate
Connect, or paste any Solana address. Vaultagent reads its balances and its last 25 transactions from mainnet, works out what left the wallet and to whom, and marks every payment the mandate would have refused.
Connect a wallet at the top right, or paste an address.
Terms, plainly
Policy pages are where private banks hide things. Ours are short.
§1 What is live today?
The mainnet reads: wallet balances, transaction history, prices from Jupiter, and the optional memo that anchors your policy root. The policy engine, Merkle disclosure and agent signatures are real cryptography running in your browser.
§2 What is a model or simulation?
The session ledger in section II and the budget dashboard in section IV are simulations; they are labelled so. No agent account, shielded pool or lending market exists behind this page yet.
§3 Is a Merkle disclosure a zero-knowledge proof?
No. It proves that an opened clause belongs to the sealed policy without showing the others. It cannot prove a range such as "balance above 100" without revealing the number; that needs a ZK circuit, which this site does not claim to have.
§4 What does "Anchor root on mainnet" sign?
One SPL Memo containing your policy's Merkle root, signed by your own wallet. It moves no funds and sends nothing to anyone. You see the exact text and the network fee before your wallet opens.
§5 Where does the agent key live?
In this tab's memory, created with WebCrypto Ed25519. It is not saved and not sent anywhere. Never send funds to it: it exists to sign intents in this demonstration.
§6 Who stands behind Vaultagent?
It is an independent concept. There is no audit, no partner bank, no deposits and no users to report. The site never holds funds and never asks for a seed phrase.