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 post-quantum validator signatures (Falcon-512, and since 2026-09-04 SLH-DSA as well) under the block hash, introduced at a minimum of three seals, raised at block 14,961,456 (August 21, 2026) to six of nine and at block 20,715,632 (2026-09-29) to seven of ten, as many as the quorum each time; below block 24,148,752 the seals proved those validators signed the block, not that it was decided (AIP-22 erratum, 2026-10-01), and from that block a certificate that carries the quorum of one round proves the decision. 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. Once the next anchor block is produced (at most 32 blocks later), rewriting the block that holds your hash would need the validators' post-quantum signatures, not only classical keys; the one narrow exception is named in the AIP-22 erratum of 2026-10-01.
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 sub-second deterministic finality (a block about every 0.62 s, measured on 2026-10-15). 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 productised path is live as of August 23, 2026: the AereNotary contract at 0x4aB392c4…bd58c7 records each digest’s first appearance immutably (re-notarizing can never move the original timestamp, by contract), and the Aere Cloud API notarizes and verifies per document, with authentication and billing: we pay the gas and carry the transaction; your file never leaves your hands. The contract is permissionless on purpose: you can bypass our API entirely and call notarize(bytes32) yourself. What remains an engagement deliverable: a counterparty-facing verification page under your brand and a signed conformance report.
Verify an anchor yourself
curl -O https://aere.network/tools/verify-anchor.mjs -O https://aere.network/tools/mpt.mjs -O https://aere.network/tools/falcon512.mjs -O https://aere.network/tools/registry-v3.mjs -O https://aere.network/tools/package.json && npm install node verify-anchor.mjs # with no argument it checks the newest 20 anchors: 20/20 bound; # give it the anchor height the API names for your document # (node verify-anchor.mjs <height>) to check the one that covers it.