Load a fresh receipt from the Hive mesh, or paste your own. We check its Ed25519 signature two ways: once on the Hive mesh, and once fully offline right here in your browser. Nothing is faked. Flip the tamper switch and watch a good receipt turn red.
New here? Just press Load a live receipt, then Verify. It pulls one real signed receipt off the ledger and checks it. You can also paste a receipt, or type a ledger number.
Tamper switch. Turn this on to change one value in the receipt before checking. A real signature will not cover the changed bytes, so both checks should go red. That is the whole point: the proof is in the provenance.
On the Hive mesh
·Not run yet
The Hive mesh re-checks the signature and returns a signed answer.
Offline in your browser
·Not run yet
Your browser re-checks the same Ed25519 signature against the published key. No trust in our server needed.
Ledger number
·
Event
·
Receipt hash
·
Signature
·
Public key
·
Signer
·
How this check works
We read one receipt from the Hive ledger: GET /v1/receipts/verify/{n}. It returns the exact signed payload, the Ed25519 signature, and the public key.
Mesh check: the Hive mesh confirms the signature and returns verified: true with the key id.
Offline check: your browser rebuilds the exact signed bytes (sorted-key compact JSON, matching the issuer), then runs Ed25519.verify(publicKey, signature, bytes) using an audited open-source library. No secret ever touches your browser, and the check does not trust our server.
Change one byte and the math fails. That is what the tamper switch shows.
Private by design. Hive does not store your prompts. Every request is receipted by a one-way SHA-256 fingerprint, not the words. Proof, not surveillance.