Texts after the AIP-22 erratum of 2026-10-01 (an anchor certificate shows that its signers sealed the block post-quantum, not that it was decided); SD-JWT key-binding nbf probe and its negative control

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
Aere NetworkandClaude Opus 5.5 committed 2026-10-01 17:15:48 +03:00
1 parent 5f1e60b8d2
commit f84a5e8c18
6 files changed
+17 -7

No files matched your search

+4 -3
View File
@@ -4,7 +4,8 @@ A sidecar that runs next to a deployment, on any cloud or on premises, and keeps
AERE Proof Protocol envelope (AIP-23), built by the same `proof-kinds` builder and checked by the same AIP-23 reference
verifier as every other AERE proof, and every entry covers the hash of the one before it (an append-only hash chain,
`hash = sha256(seq | prev | envelope)`, genesis `0x00..00`). The head of the chain can be notarized on Aere Network, which
gives the history up to that head post-quantum finality that anyone can check.
binds the history up to that head under a post-quantum validator certificate that anyone can check (what such a
certificate proves, and what it does not, is in the AIP-22 erratum of 2026-10-01).
Node.js 24, no dependencies; `notarize-head` alone needs `ethers` (`npm install` in this directory).
@@ -17,8 +18,8 @@ Node.js 24, no dependencies; `notarize-head` alone needs `ethers` (`npm install`
`verify-log` on that file alone reports it intact. A partial edit is caught (the chain breaks at the edited entry and
`verify-log` names it), a full rewrite is not.
- **What is checkable without trusting the host is the history before a published head.** `attest-head` turns the current
head into an envelope; `notarize-head` records its hash on the AereNotary contract; the AIP-23 reference verifier then gives
it post-quantum finality (the most recent certified anchor, the parent header bound by hash, its state root, and a Merkle
head into an envelope; `notarize-head` records its hash on the AereNotary contract; the AIP-23 reference verifier then shows
it under a post-quantum certificate (the most recent certified anchor, the parent header bound by hash, its state root, and a Merkle
proof of `firstSeen[statementHash]`). `verify-log --attested <head.json>` requires that today's log **continues** that head:
the same first `count` entries, the entry `count - 1` hashing to the attested head. A rewritten or shortened history fails.