Fixseal guard on NEAR testnet

An AI agent spends through this contract. Its spending rule can only be replaced by the exact rule an accept record covers: the fix beat the exploit, passed regressions, and its Lean proof was checked against a fixed specification. This page reads the contract live. It is read-only: no wallet, no keys, no transactions.

Contract fixseal-guard.testnet Agent fixseal-agent.testnet Loading…
Activity
Refusals (failed transactions) do not change on-chain state; they are visible in the terminal output and the explorer.

Live state

Spending cap
–
yoctoNEAR
Spent counter
–
u64 counter used by the current rule
Total actually paid
–
Cumulative yoctoNEAR transferred by guard_spend
Rule in force now
–
Installed from record –

Try an amount

Quick:
Vulnerable rule (as deployed)
spent + amount ≤ limit
SHA-256 –
–
Rule in force now
–
SHA-256 –
–

Computed in your browser from the rule stored on chain. Nothing is sent.

Checks this page runs in your browser

Agent spend key (live)

Loading…

Judge records on chain

VerdictProposed ruleRecordSubmitted
Loading…

Rule changes

WhenFromToRecord
Loading…

Recorded run, 2026-11-10 (UTC)

Saved run for the default contract; the live state above may have changed. Each outcome was checked from final receipts. Links open the public explorer.

#StepOutcomeTx

Limits

The contract trusts the record submitter (the registered agent) and the owner; it does not run Lean. Attestation is mock. The Lean-to-contract match is tested on 1,028 fixed inputs, not proved. The agent account also holds its own full-access key; the spend calls in the run were signed with the restricted key shown above.