nanalLabs BlogIn the end, records are kept to be shown to someone. nanalStamp has four proof instruments, and all of them start from a note's proof & timeline.
Certificate PDF
"Issue certificate (PDF)" produces a certificate carrying the issue number, SHA-256 hash, sealing time, Bitcoin anchor, issuer signature, and a public verification URL with QR code. Need proof as of a past version? Choose the reference point in the submission package flow.
Public verification link — facts public, content private
A "public verification link" opens without login. The recipient sees the hash, the time, and the block — never the content. Once the anchor is confirmed, the page shows "sealed in Bitcoin block #N · no tampering" with a link to a block explorer.
Verifying without our server — the offline bundle
Choosing "this note only" in the submission package produces a .nanalproof bundle — original, proof, and verification instructions in one. Drop the original and the bundle into np-verify: all computation runs inside your browser and nothing is sent to any server. Change a single character of the original and verification fails with a mismatch — the chain and signatures still pass, which is exactly what proves that only the original changed.
The submission package — one zip for audits and examinations
For bundled submissions — patent examination, project audits — use ribbon → "Create submission package (.zip)": originals, the seal chain, Bitcoin evidence, certificate PDFs, and a verifier program in a single zip.
The core design here is the disposition ledger. Submitted material is a subset of the chain, and silence about what was omitted is indistinguishable from hiding unfavorable records. So the ledger inside the package lists every sequence number in the chain with its disposition — included / superseded / after-cutoff / out-of-scope — and the recipient's verifier computes the "should exist" list from the chain itself, catching even the forgery that deletes a note and its ledger entry together.