AOTrust receipt verifier

239 bytes. Ed25519. NEAR. This page has no AOTrust backend in the path — it parses the receipt, checks the signature in your browser and reads the anchor root straight from notary-node.near.

Examples

Real receipts from the public log. Nothing leaves this page until you press “Check against NEAR”.

Structure
not checked
waiting for a receipt
Notary signature
not checked
Ed25519 over the envelope
Anchor root
not checked
on-chain root
How this works
  1. file — the artifact never leaves the machine; only its SHA-256 is sent to the notary.
  2. SHA-256 — the digest of the file is the payload_hash field inside the receipt.
  3. receipt (signature) — notary-node.near signs the 175-byte payload with Ed25519: sha256-free envelope = u32LE(2147484061) ‖ u32LE(175) ‖ payload. Verify it here with the notary public key — no server needed.
  4. Merkle leaf — the record is a leaf in an RFC 9162 tree: leaf = SHA-256(0x00 ‖ record), node = SHA-256(0x01 ‖ left ‖ right).
  5. hourly / cumulative root — folding the audit path from the leaf upwards yields one 32-byte root. If your fold equals the root the chain holds, the record is in that tree.
  6. NEAR transaction — the root is committed by the contract notary-node.near; get_root(seq) is a public read on any RPC. That is the only thing this page trusts.