Elara — verify it yourself

Paste a validation record below and check it in your browser — no server, no network, no account, and no trust in us. The same code the elara-verify CLI runs, compiled to WebAssembly. It confirms the post-quantum signature and identity binding, and it never prints a green it can't prove: an unproven bound shows ⚠ PARTIAL, a forged one shows ✗ FAILED.

This box checks the record's own integrity — structure, identity binding, and the post-quantum signature. To check a record against the chain — epoch seal, inclusion, a drand time beacon — paste a receipt in the next section, or use the elara-verify CLI (--inclusion / --seal / --anchor; Bitcoin .ots proofs are CLI-only).

…the whole chain, one file

A receipt (.elara-receipt) bundles the evidence for one verification — the signed record, the epoch seal, inclusion and account proofs — so "check it yourself" is one file. Paste it and the same shared core grades every leg and the cryptographic links between them, offline: post-quantum signatures, seal commitments, and a drand not-before beacon whose BLS signature is verified in your browser against the pinned League-of-Entropy key. (Bitcoin .ots existed-by proofs don't ride in receipts — that leg is graded by the CLI, and shows here as an honest ⚠.)

Trust pins come from you, never from the receipt. A receipt that vouched for its own trust root would prove nothing, so without a pinned anchor key the seal grades ⚠ PARTIAL — honestly. The sample button — and the "verify this" links on the receipts page — fill the pin with the repo's zone-0 anchor key for the demo; in real use you obtain that key from a source you already trust. Try "Drop the pins" to watch the verdict downgrade rather than lie.

…and who was authorized

A timestamp proves these bytes existed. A signature proves this key signed them. Neither can answer the question that matters for an autonomous agent: was this agent authorized to act — by whom, for what, and was that authority still valid when it signed? Paste a mandate bundle and check that chain offline, in your browser — the same verdict the node's /mandate/status endpoint computes.

A ✓ CONSISTENT result proves the signatures and that authority held at the act's signed time given the records in this bundle. It is deliberately not labelled "authorized": offline it cannot prove the records are on-chain or that a revocation wasn't withheld — that is the live node's answer. The named principal is shown only when the verdict attributes to them (an impostor's act exonerates them).

Runs entirely client-side via verify_record_offline() / verify_receipt_offline() in the Elara verify-only WASM module — no wallet, no secret keys, no signing, and no network code is linked into this binary (the separate web-wallet build is far larger). The logic is elara_runtime::verify_core — including grade::{grade_receipt_v1, bind_outcomes}, the identical node-free sequence elara-verify --receipt runs — so neither verdict here can drift from the CLI's; the drand not-before leg verifies the beacon's BLS signature against the pinned League-of-Entropy key (verify_core::anchor). The authorization check is evaluate_mandate_bundle() over elara_runtime::mandate_bundle — the same pure verdict core the node's /mandate/status endpoint runs. Build it yourself from the repo root with wasm-pack build --target web -d ../browser-node/verify-demo/pkg verify-wasm and diff the wasm to confirm it matches what runs here.

The verifier is MIT/Apache-2.0-licensed (the elara-verify + elara-record crates — no AGPL node code links into this wasm); its complete source is the public Elara repository this page is built from.