Exit kit - verify without us
The promise «your proof survives our service» needs a mechanism, not a sentence. The exit kit is that mechanism: one command exports the whole log, and two commands verify it without asking AOTrust anything.
What you get
| Command | What it does | Network |
|---|---|---|
aotrust-export export --db queue.db --out DIR | Dumps every record (with its 239-byte PDR), every anchor (size, root, NEAR tx) and every Merkle leaf into JSONL + a MANIFEST with SHA-256 of each file. | none |
aotrust-export verify --dir DIR | Parses each receipt, checks the notary Ed25519 signature over the NEP-413 envelope, checks that payload_hash = work_hash for 0x03. | none |
aotrust-export roots --dir DIR --rpc URL | Recomputes every anchor root from the leaves (RFC 9162) and compares it with the recorded anchors; with --rpc also reads get_root(seq) from the NEAR contract and compares it with the chain. | public NEAR RPC only |
Proven on this log (11.11.2026)
exported: journal=230 anchors=33 leaves=236
receipts: ok=21 bad=0 without-pdr=209
roots: checked=33 mismatched=0 (leaves=236, anchors=33)
on-chain root (notary-node.near): 079074f46263a223…7865 - matches latest anchor #94: True209 records carry no embedded PDR in the database (legacy rows issued before the receipt was stored); their proofs exist in the PDF a customer holds and stay verifiable through the same anchor.
If AOTrust disappears
- The exported directory keeps every hash, timestamp, signature and anchor transaction.
- Receipts stay verifiable: signature → notary key from MANIFEST; inclusion → Merkle root from
anchors.jsonl→ the NEAR transaction. - Any party can continue the log elsewhere: leaves and proofs do not depend on our servers.
The tool lives in the service repository (tools/aotrust_export.py) and needs only Python 3 and pynacl.