receipt-chain-live · Khipu hash-chain verifier

SHA3-256 · schema szl.lake.receipt/v1 · re-verified in your browser
⏳ fetching live lake…

This page fetches the live a11oy receipt lake and recomputes every receipt's chain_hash locally — the exact SHA3-256(canonical_json{prev_hash, receipt_id, organ, ts, chain_index}) the ledger commits — then checks that each prev_hash links to the previous chain_hash. Green means the chain is intact as measured on your machine, not as merely claimed by the server.

MEASURED — recomputed in your browser REPORTED — asserted by the lake, not re-checked here UNAVAILABLE — no live data / capability absent
Honest scope. This verifier proves the SHA3-256 hash-chain integrity in-browser (MEASURED). It does not verify each receipt's DSSE ECDSA-P256 signature — those are shown as REPORTED. Full signature verification (against the org cosign.pub) is the end-to-end cookbook recipe “Verify a receipt end-to-end”. Energy is {"label":"UNAVAILABLE"} unless a real NVML/joules reading exists — never fabricated. The Khipu chain is Conjecture 2 (advisory BFT), not a proven theorem; Λ remains Conjecture 1.
⟨ 4TH WALL ⟩ You are reading rendered bytes. Don’t trust them — hash them:
canonical source: SZLHOLDINGS/receipt-chain-live · verify from outside: curl -sL https://huggingface.co/spaces/SZLHOLDINGS/receipt-chain-live/resolve/main/index.html | sha256sum
Integrity & origin of this page only — never the accuracy of anything on it. Known platform delta: Hugging Face may inject one window.huggingface variables <script> into <head> of the served page, so the in-browser hash can differ from the source hash by exactly that banner — diff the two documents to see it. Distrust only differences beyond that. Doctrine v11.