Dated corrections (2026-10-27): AIP-7 and AIP-13 carry a note that their statements that AERE consensus is classical describe chain 2800 before AIP-22 stage 4 (block 24,300,000); AIP-22 gains three dated notes (section 3.3, the clause on the envelope's recovered address no longer applies from stage 4; the correction of 2026-10-25 to section 5, every consensus message still carries the ECDSA envelope, whose form both clients judge; Security Considerations, 'Denial of service by seals': no per-peer bound in the consensus layer of either client, and a forged proposal can cost about 1,025 Falcon-512 verifications) and an Errata entry; execution-kernel/MACHINE-INTERFACE-CONTRACT.md no longer says it was written the day a consensus milestone went live at block 14,050,000 (withdrawn 2026-08-19) and names what the block hash covers; formal-consensus/RULEAZA-TOT.md dated.
This commit is contained in:
1 parent
6d24576357
commit
ac3d299e3f
5 files changed
+22
-5
No files matched your search
@@ -1,7 +1,9 @@
|
||||
# MachineInterface (MI) contract, Execution Kernel treapta 1
|
||||
|
||||
Chain 2800 (AERE). Written 2026-08-15, the day the post-quantum consensus milestone went
|
||||
live at block 14,050,000. This is the seam for interface **I3** in
|
||||
Chain 2800 (AERE). Written 2026-08-15 (Corrected 2026-10-27: this line said it was written the day
|
||||
the post-quantum consensus milestone went live at block 14,050,000; that claim was withdrawn on
|
||||
2026-08-19, nothing changed at that height, see https://aere.network/docs/network/forks.html).
|
||||
This is the seam for interface **I3** in
|
||||
`aerenew/strategie/EXECUTION-KERNEL-2026-08-15.md`.
|
||||
|
||||
This document is a **contract**, not an implementation. Treapta 1 adds no new infrastructure.
|
||||
@@ -145,7 +147,8 @@ both directions (section 7). Two MI results for the same input are equal when, a
|
||||
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 `CLAUDE.md`). None of that is an MI
|
||||
locally, and the block hash does not cover the seals; 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.
|
||||
|
||||
**Determinism is measured across implementations, not asserted from one.** A single client
|
||||
|
||||
Reference in new issue
Block a user