Verify a policy log against its anchor

A real Claude Code session, blocked by Warden's policy proxy, is checked here against the head published on Monad testnet. Break the log and see which check catches it.

Log

Recorded run Paste your own

Tamper with it

Leave it untouchedThe log exactly as Warden wrote it. Change the DENY to ALLOWEdit one decision, leave the hashes alone. Change it, then re-hash the chainThe log is internally consistent again. Only the anchor can tell. Remove the denial entryCut the end off the log.

Ledger JSON (the export from warden audit --export json, or its entries array) Anchor record JSON

Checking

Recomputing the hash chain in your browser.

Traverse: log entries closing on the anchor

Position	Entry	Time (UTC)	Tool	Decision	Hash	Link

Contract 0x8494...cb0 Monad testnet, chain id 10143 Check runs offline, no wallet or RPC

What this proves, and what it does not

The anchor proves the log head existed at that block. It does not prove the host was honest before anchoring, and entries the proxy never saw are not covered.

Warden enforces MCP tool calls routed through its proxy. Claude Code's own native tools are outside that boundary, so the demo switches them off. The contract is unaudited and testnet-only.