AIP-22 T5 pe 2800 (H_hdr 25.080.000, 2026-10-30): proza scrisa de proza-trepte.py T5 --scrie --formulare 1
Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
1 parent
7e1ba97afc
commit
5efd857998
4 files changed
+6
-6
No files matched your search
@@ -145,9 +145,7 @@ both directions (section 7). Two MI results for the same input are equal when, a
|
||||
| block `hash`, `parentHash` | identical 32-byte hash |
|
||||
|
||||
Determinism is a claim about these commitments, not about internal representation. Two clients
|
||||
may lay out their trie nodes differently in memory, name their threads differently, and store
|
||||
`extraData` differently for the same block (QBFT lets each node assemble the final header
|
||||
locally, and the block hash does not cover the seals; see aere-node `SPEC.md`, section 2.3; corrected
|
||||
may lay out their trie nodes differently in memory, name their threads differently, and store `extraData` differently for the same block (below block 25,080,000, AIP-22 stage 5, QBFT let each node assemble the final header locally; from it nodes that committed a block in the same round store the same bytes, and only the round (element 3) and the proposer seal of that round (element 6) can still differ under the same hash, for a block that nodes committed in different rounds (a value locked in one round and proposed again in a later one); a node that imports the block stores the form of the node that served it; the block hash does not cover the seals either way; see aere-node `SPEC.md`, section 2.3; corrected
|
||||
2026-10-27: this pointed to a file that is not public). None of that is an MI
|
||||
input or output. Only the commitments above are.
|
||||
|
||||
@@ -319,7 +317,7 @@ The harness prints a NOT MEASURED block naming these on every run, and its JSON
|
||||
them in the `honesty` field, so the non-claims travel with every result rather than living only
|
||||
in this document:
|
||||
|
||||
- **That consensus is post-quantum.** It is not. Consensus finality is QBFT whose votes every validator attributes only through their verified post-quantum seals since block 24,300,000 (AIP-22 stage 4), with classical secp256k1 ECDSA commit seals in the header until AIP-22 stage 5 and a Falcon certificate at every anchor. MI is an execution seam and says nothing about consensus.
|
||||
- **That consensus is post-quantum.** The contract does not make that claim: MI is an execution seam and says nothing about consensus. What the chain states is that since block 25,080,000 (AIP-22 stage 5) headers no longer carry ECDSA commit seals and, since block 24,300,000 (AIP-22 stage 4), every vote counts only with the verified post-quantum seal of its author, and a commit still carries the ECDSA commit seal of its validator as an additional check, which it calls post-quantum consensus, with three limits: the transport between nodes is still authenticated by secp256k1, the ten validators are run by one operator, and no third party has audited it yet; a Falcon certificate sits at every anchor.
|
||||
- **That equal header roots prove independent execution by themselves.** See the honesty boundary
|
||||
in section 5. The load-bearing fact is Nethermind's reject-on-disagreement behaviour, not the
|
||||
served bytes.
|
||||
|
||||
Reference in new issue
Block a user