The agent asks, the vault decides
Every payment goes through pay, where per-transaction and daily limits are checked in contract state. The agent never touches the rules.
the wallet your agent can't sweet-talk.
Let Budi pay for things. He believes anything,
attackers included. The
vault enforces the rules on NEAR, so a fooled agent still can't drain funds or raise its own limit.
This preview simulates the contract's rules in your browser (1 NEAR per tx, 3 per day, allowlist: toko-arr.testnet). The real vault runs on NEAR testnet.
Budi follows every instruction he reads, hidden ones too. Between him and your money sits a contract he can't argue with, and a key that only knows how to ask.
When the thing being tricked is also the thing guarding the money, the money goes with it. So we moved the guard.
One NEAR contract between an AI agent and the money it spends. The agent can ask. The contract decides.
Every payment goes through pay, where per-transaction and daily limits are checked in contract state. The agent never touches the rules.
If it can sign a NEAR transaction, it can use the vault. Budi runs on NEAR AI Cloud by default, or any OpenAI-compatible API.
Limits and the allowlist are contract state. Calls run one after another, so the daily cap holds exactly.
Payments to unknown receivers are held, not sent. Only the owner can approve or reject them, from a separate process.
Rejections return instead of panicking, so the log entry survives. Attacks leave public evidence.
Locks the agent can't pick.
Three checks stand between a fooled agent and your funds. A fourth makes every attempt visible.
Budi's NEAR access key is scoped to the vault and the single method pay. set_policy is refused by the protocol before any contract runs.
Per-transaction cap, daily cap and allowlist live in contract state. Policy methods check the caller and only accept the owner.
Within the limits, a payment to anyone outside the allowlist is held. The owner approves or rejects it from a separate process.
Rejected payments return a reason instead of panicking, so the log entry is committed. The vault keeps its last 100 decisions.
The console preview at the top is a simulation. This panel isn't: your browser reads the vault's state straight from NEAR testnet with a read-only view call. No wallet, no key, no server of ours in between.
near contract call-function as-read-only vault-arr.testnet get_logs json-args '{}' network-config testnet now
npm run attack-suite against vault-arr.testnet, with Budi's real key. Each card opens its transaction.
Short answers about what Trickproof does, and what it doesn't.
Read the README →pay, so the protocol refuses any other method. And the contract checks the caller, accepting only the owner for policy changes.Five testnet accounts and one setup command. Then try to talk Budi into anything.
Let your agent be gullible. Keep the rules where no prompt can reach them.