No account · no ticket · no trust in us required
Anyone can check the receipts.
Paste a notary receipt id from any North evidence pack and the chain answers — position, hashes, timestamp. The pack records evidence; it does not approve.
Check a North receipt (the desk recomputes the chain and checks the signature against the keys North publishes): 1. GET https://usenorth.xyz/api/verify?reference=north-notary:north@1 2. Expect ok=true, status=verified, mode=signature-v1, and every check passing. status=unverified (ok=false) means no notary signature verified: the receipt is not proven. 3. Optionally fetch https://usenorth.xyz/api/verify/keys and verify receipt signatures offline.
What this check is — and is not
The chain recomputes, every time.
Each lookup rebuilds the tenant's notary chain from its genesis hash and replays every link to your receipt's position: sequence contiguous, previous hash linked, entry hash recomputed. Nothing is taken on our word — the math is the witness. Export the ledger segment and the same math runs offline.
Signatures, said plainly.
A receipt is verified only when it carries a notary signature that checks against the public key registry, on top of the structure checks (recording, position, and chain integrity recomputed from genesis). Take the keys from /api/verify/keys and pin them against a copy you trust before checking offline. Receipts without a signature, including those recorded before signing was switched on, answer unverified: structure alone can be forged, so the desk never counts it as proof.
Verified requires signature-v1 · unsigned receipts answer unverified · writes nothing · answers in one call