Add ERC: Post-Quantum Anchored Key-Binding - #1932
Open
TMerlini wants to merge 4 commits into
Open
Conversation
Collaborator
File
|
0x2kNJ
reviewed
Aug 6, 2026
| eip: 8360 | ||
| title: Post-Quantum Anchored Key-Binding | ||
| description: Anchored classical-to-PQ key bindings plus an anchor-time consumer cutoff, verified by recomputation | ||
| author: Tiago Merlini (@TMerlini), babyblueviper (@babyblueviper1), Pavlo (@pipavlo82) |
There was a problem hiding this comment.
Confirmed, happy to be on it. Same string as my ERC-8312 entry so an editor reads the two as one contributor.
Suggested change
| author: Tiago Merlini (@TMerlini), babyblueviper (@babyblueviper1), Pavlo (@pipavlo82) | |
| author: Tiago Merlini (@TMerlini), babyblueviper (@babyblueviper1), Pavlo (@pipavlo82), Matthias Hauser (@0x2kNJ) |
Author
There was a problem hiding this comment.
Applied — welcome aboard, and thanks for the exact ERC-8312-matching string. All four authors now confirmed on the line.
TMerlini
force-pushed
the
pq-anchored-key-binding
branch
from
August 6, 2026 12:34
d95dec9 to
65bd470
Compare
abcoathup
reviewed
Aug 6, 2026
TMerlini
force-pushed
the
pq-anchored-key-binding
branch
from
August 6, 2026 23:11
871eab9 to
658dbb5
Compare
TMerlini
force-pushed
the
pq-anchored-key-binding
branch
from
August 6, 2026 23:21
658dbb5 to
143d9b5
Compare
|
The commit 658dbb5 (as a parent of 4b2c431) contains errors. |
TMerlini
force-pushed
the
pq-anchored-key-binding
branch
from
August 6, 2026 23:58
143d9b5 to
5d77b0a
Compare
…larification Assets: swap cutoff_enforce.py to the v1 enforcer (baseline activation + tri-state evidence) and flip the single pre-baseline case in the cutoff, rotation and revocation vectors from REJECT to ADMIT (anchored_before_cutoff) — a pre-baseline artifact is back catalogue and admits classical-only rather than being retroactively invalidated. All three suites reproduce (8/8, 7/7, 6/6). Spec: qualify verification step 3 and Backwards Compatibility so a revocation ends authority even for a pre-cutoff artifact (revocation overrides the cutoff; signed off in the revocation lane, recompute-kit#16). Add a Related Work paragraph (Lean Consensus PQ validator registry: cryptographic expiry from statefulness vs explicit anchored authority-termination). Surfaced by zexoverz's review; conformance mirrored in trustless-ai/recompute-kit#16 (merged).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ERC-8373: Post-Quantum Anchored Key-Binding
Migrates the signature layer of on-chain / agent identity to post-quantum via an anchored classical-to-PQ key-binding and a consumer-enforced anchor-time cutoff — deliberately not a second signature (a forger who derives the classical key simply omits an optional extra signature; under this ERC, post-cutoff omission fails closed).
Discussion: https://ethereum-magicians.org/t/post-quantum-migration-for-on-chain-identity-an-anchored-key-binding-a-cutoff-verified-by-recompute-not-a-second-signature/29225
Reference implementations (production): two independent implementations under two NIST families (ML-DSA-65 / FIPS 204 and SLH-DSA-SHA2-192s / FIPS 205) converge on byte-compatible content-addresses; the SLH-DSA lane is mainnet-anchored with a live cutoff enforcer implementing the full verification procedure (in-force resolution, rotation, revocation). Conformance vectors for the binding, cutoff, rotation, revocation, and recovery classes are included under
assets/erc-8373/with executable checkers (stdlib Python).Authorship: all four authors confirmed.