Block a user
6c13bb314d
anchor/README: remove the duplicated stage R row of the armed-on-2800 table (introduced by the previous commit); the row stays once
1b788f86d1
Dated corrections (2026-10-25): AIP-8 consensus note (per-block finality was the classical ECDSA statement until block 24,300,000, AIP-22 stage 4; the second client attributes every consensus message through its post-quantum seal since then); README: anchor certificate seals proved signing, not decision, below block 24,148,752
3e49753b31
Dated: below block 24,148,752 the anchor certificate seals proved signing, not decision; from that block (AIP-22 stage R) a certificate carrying the quorum of one round proves it. SPEC rows 5 and 3.4 and the anchor table carry stage R as set on chain 2800
53930c4a09
Dated corrections (2026-10-25): anchor certificate seals proved signing, not decision, below block 24,148,752 (AIP-22 stage R); per-block finality is no longer the classical ECDSA statement since block 24,300,000 (AIP-22 stage 4), and the second client attributes every consensus message through its post-quantum seal since then
c74184dc55
AIP index: the anchor certificate seals proved signing, not decision, below block 24,148,752; from that block (AIP-22 stage R) a certificate carrying the quorum of one round proves the decision
7493940923
AIP-22: dated correction to section 5 (after H_hdr a commit still carries the validator's ECDSA commit seal, checked by both clients as an additional check; no header carries an ECDSA signature)
7932becfb4
AIP-20, AIP-22, index and execution-kernel contract: AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25), dated notes
c4771b6b32
AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25): READMEs, SPEC and RUN-A-NODE say so, dated
200f4338f0
execution-kernel/MACHINE-INTERFACE-CONTRACT.md: restore the sentence on consensus finality as it stands today (classical secp256k1 ECDSA QBFT plus a Falcon certificate); the previous commit carried, by a staging race on 2026-10-24, a draft sentence written for AIP-22 stage 4, which is not in force before block 24,300,000
1e386c7e18
AIP-21, AIP-22: note added 2026-10-24: stage R (the round-bound post-quantum commit seal, COMMIT-2, and the v3 anchor certificate) is in force on chain 2800 since block 24,148,752; from that block a v3 certificate carrying the quorum of a single round proves the anchor's parent decided; stage 4 takes effect at block 24,300,000 (announced 2026-10-22)
89d557000a
anchor/README: stage R (the round-bound post-quantum commit seal and the v3 anchor certificate) is live on chain 2800 since block 24,148,752 (2026-10-24); the armed-on-2800 table carries the row
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
04e572fe15
Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction
9056e51679
Correct the source mapping for 0xCAB1DBA5 in the SpokePool invariant test: the live bytecode was compiled from the 2026-06-08 revision of bridge/AereSpokePool.sol, not from the current file
07bee6902e
anchor/README: validatorii sunt numiti prin id-urile post-cuantice AIP-22 din blocul 20,836,228 (treapta 3); corectie datata 2026-10-22