Security check
Policy checks stand between your AI agent and a wallet signature.
Agent request
SAMPLE REQUESTInspection trace
One failed gate stops the request.Fixed policy rules cannot be overridden by the agent.
On-chain proof
REAL · NEAR TESTNETvault.rimbux.testnet ↗
Agentagent.rimbux.testnet ↗
Payment · 0.01 NEAR8Z4eHU…q6Aq ↗
Blocked recipient · rejectedFN1uHR…xBym ↗
Over amount cap · rejectedCyR5ch…s85y ↗
Calls to execute_agent_payment on Nov 5, 2026 (UTC). The payment is a 0.01 NEAR transfer from the vault; the two rejections are panics raised by the vault contract itself. This demo screen does not broadcast.
Wallet policy
Scenario signals
SIMULATEDAudit trail
Transaction payload
BROADCAST: FALSE
// Run a check to build the payload
Rules
Spending limits, human approval and the agent’s on-chain key.
Spending rules
Human approval queue
Transfers at or above the approval threshold wait here for a human decision. Nothing is signed or sent until then.
Agent key
The agent never holds your main key. It only gets a limited FunctionCall access key. Revoking here stops local signing only; the key stays valid on NEAR until it is removed on-chain.
Snapshot from the NEAR testnet RPC on Nov 9, 2026 (final block). The allowance shrinks as the key pays gas. Press Check on-chain to read it live.
Audit log
Every decision is hash-chained, so editing a past entry is detectable.
Tamper-evident audit log
Each entry stores the SHA-256 hash of the entry before it. Click a row to see the full hashes.
| Time | Request | Verdict | Chain hash (previous → entry) |
|---|