Post-Quantum Notarization
Anchor a document hash on chain 2800 and get a timestamp whose proof outlives the cryptography that made it. No file leaves your hands.
A timestamp is only as durable as the cryptography under it. Anchor a document's hash on a public chain today and you get proof it existed at a moment in time, verifiable by anyone. But the classical signatures that secure most chains are on a retirement schedule: once elliptic-curve cryptography falls, an adversary who recovers old validator keys could, in principle, re-sign an alternative history and cast doubt on a record you meant to keep for decades. For a legal exhibit, an archive, or a compliance record that must survive twenty or thirty years, that is not an abstract risk.
A timestamp that outlives the cryptography that made it
Chain 2800 leaves post-quantum evidence in its own block record. Since block 13,014,000, every anchor block binds a certificate of Falcon-512 validator signatures under the block hash, at an enforced minimum of three per block. A document hash committed on this chain inherits that durability: the proof it existed is carried in a record whose integrity does not rest on classical signatures alone. When you need to show, years from now, that a file is exactly the one you timestamped, the verification does not depend on cryptography that has since been retired.
How it works
You compute the SHA-256 (or SHAKE-256, via the precompile at 0x0AE5) hash of your document locally, so the file itself never leaves your hands. That 32-byte hash is committed on chain 2800 with half-second deterministic finality. You receive a receipt: the block number, the transaction, and the anchor certificate covering it. Anyone can later verify the hash against the chain, independently of us, with a single read-only call. No file is uploaded, no personal data is stored.
Who this is for
Law firms and courts that need tamper-evident exhibits. Archives and registries with retention obligations measured in decades. Intellectual-property and research teams establishing priority. Regulated firms under records-retention rules (SEC 17a-4, MiFID II, MiCA) who must keep records provably unaltered. Anywhere the value of a proof is that it will still hold up long after today's cryptography is gone.
What exists today, honestly
The anchoring mechanism is real and running: this network's own whitepaper re-anchors its content hash on a fresh block several times a day, and that anchor is publicly verifiable right now. What a customer engagement builds on top of it is the productised path: a per-document API with authentication and billing, a verification page your counterparties can use, and a signed conformance report. We would rather tell you what is a working mechanism versus what is a delivery than dress a roadmap as a product.
Verify an anchor yourself
npm install @noble/hashes curl -O https://aere.network/tools/verify-anchor.mjs node verify-anchor.mjs # the same tool that checks a document anchor checks the # chain's own post-quantum certificate: 20/20 blocks bound.