Aere Proof

A proof answers two questions a reader can check without trusting the producer: what exactly was signed, and when. Proof is one envelope format, one public reference verifier that prints four levels and names every reason it refuses, and the anchor that fixes the time: the Aere registry on chain 2800, whose blocks carry post-quantum certificates. An independent Bitcoin witness exists today for the record of the quantum shield and is being extended to every proof (see what it is not, yet).

What exists today, measured

Every line below names the date its module was published in the public repository, the page or the contract behind it. Each module ships its README, its tests and its negative controls; nothing here asks you to take our word.

• The proof protocol and its reference verifier, AIP-23, 2026-09-27. An envelope with a statement, its hash, an ML-DSA signature and a notarization; the verifier checks form, integrity, signature and finality in four levels and refuses by name. Served from this site: verify-proof.mjs.
• Notarization, live on mainnet since 2026-08-23. A document hash committed on chain 2800 through the AereNotary contract, with the timestamp of a post-quantum-certified block; the file never leaves your hands. Pages: notarization and verify a notarization.
• Proof of Software, 2026-09-18. An attestation of a software release made from the committed bytes (the git tree hash), so that a stranger can rebuild the artifact and compare it byte for byte. Repository: aere-proof-of-software.
• Proof of AI and verifiable data, 2026-10-02. Provenance of an AI action (model, version, prompt, tools, output, agent, requester) and of a dataset, as AIP-23 envelopes checked by the same verifier. Modules proof-of-ai and verifiable-data.
• Conformance suite, 2026-10-03, updated 2026-10-15. One place that says, for every proof kind and every verifier of the house, that an artifact passes or does not, at level N, for reason M, with a published set of vectors. Module conformance.
• A Bitcoin witness for the shield's record, since 2026-10-11. The heads of the record kept by the Aere quantum shield are attested through OpenTimestamps, with the first attestations confirmed in Bitcoin blocks on 2026-10-14: a witness that is not ours and does not depend on Aere existing tomorrow. Today it covers that record, not each notarization.

What it is not, yet

• Not deepfake detection. A proof says what bytes were signed, by which key and when; it does not say that the content is true or that the camera was real. It makes the authentic version provable, which is a different and stronger thing.
• Not yet anchored in Bitcoin per proof. The OpenTimestamps witness covers the shield's record heads; extending it to every notarization is being built, and until then a notarization's time rests on chain 2800 alone.
• Not a qualified electronic timestamp in the legal sense of eIDAS; no qualified trust service provider is involved.
• No third-party audit of the verifier or the contracts has been published yet.

How it uses the engine

Every notarization is written to chain 2800, whose every 32nd block carries a certificate of post-quantum validator seals under its own hash, verifiable with the public anchor verifier. The chain is the notary under the proofs, and it is described at Developers.