Commit Graph

7 Commits

Author SHA1 Message Date
Aere Network
72468c4c47 registries: manifest-18082816.json and hibrid-10.properties (ten indices, bound at 18,082,816); genesis.json with the third pqRegistryHash entry; follower options re-derived from the live archive node (22 properties) 2026-09-10 20:20:23 +03:00
Aere Network
367d44d21b SPEC.md was a THIRD copy of the follower configuration, and it had drifted: it was missing aere.pq.hybridRegistry entirely, without which no SLH-DSA seal in a v2 certificate can be verified, and its anchorMinSeals still lacked the two dated steps from 4 September. It is now generated from the same live source as run-node.sh and RUN-A-NODE.md, and the gate compares all three: a value that lives in three places drifts in at least one 2026-09-06 21:24:13 +03:00
Aere Network
32ca7453e0 Anchor corpus at the live overlay: hybrid v2 certificate (Falcon-512 + SLH-DSA-SHA2-128s), in-tree SLH-DSA engine on the JDK digest (Bouncy Castle licence alongside), seal-store fix (D-339), anchor interval schedule; docs and SPEC 1.2.0 state the arming heights measured on the fleet on 2026-09-05 2026-09-05 07:48:07 +03:00
Aere Network
971754aad9 SPEC 8: D9, Osaka header fields under QBFT (block 0 only), found 2026-09-02 2026-09-02 22:54:57 +03:00
Aere Network
1d3fc3e54e Citations: the unresolved-citation disclosure regenerated (2026-09-02) 2026-09-02 21:39:30 +03:00
Aere Network
8d3ae8a83d SPEC 1.1.0: section 2.6 consensus messages under post-quantum seal (wire format, domains, commit form under armed anchor = D8, emission gates, enforcement rules, activation order), G11, registry-binding domains; amended 2026-09-02 2026-09-02 16:08:24 +03:00
Aere Network
44dbc1bc06 Point 47: the unified protocol specification, SPEC.md
One document from which a third party can implement a client that follows chain
2800 without reading our code: chain parameters, QBFT with the full extraData
layout and what the block hash does and does not cover, the post-quantum anchor
rules with exact pre-images and the follower configuration, precompile formats
with the message in the middle and variable signature lengths, fee rules with
their historical windows, sync requirements including the genesis-set ceiling,
and the formal models with their honest boundaries.

Every normative statement carries a file citation, a [MEASURED <date>] marker
with the command, or [NOT MEASURED]. Section 8 documents twelve dated
divergences a syncing client will meet on the real chain (the 2138451 transition
value that must not be corrected, the base-fee lapse window, the anchor disarmed
window, the threshold window, the retired falcon.forkBlock rule), because a spec
that hides history cannot sync anyone. Section 9 lists ten things this spec
cannot state from published sources, by name, rather than papering over them.
2026-08-25 00:57:53 +03:00