aere-network/aere-node
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
141 Commits 1 Branch 0 Tags 17 MiB
c3ef72b82c
Commit Graph

30 Commits

Author SHA1 Message Date
Aere Network
c3ef72b82c TR on chain 2800 moved to block 24,148,752 (was 24,127,504, announced earlier the same day and never armed on any node): the fleet series could not finish 48 hours before the earlier height. verify-anchor.mjs (COMMIT_ROUND_BLOCK), run-node.sh and the runbooks carry the new aere.pq.commitRoundBlock 2026-10-21 20:46:21 +03:00
Aere Network
7e6dad4239 TR on chain 2800 from block 24,127,504: the post-quantum commit seal binds the consensus round and the anchor certificate takes the v3 form from that height; verify-anchor.mjs knows the height (COMMIT_ROUND_BLOCK), run-node.sh and the runbooks carry aere.pq.commitRoundBlock 2026-10-21 20:02:04 +03:00
Aere Network
f7930b2ff9 validator/: the operator kit for becoming a validator of chain 2800 (keys generated on the operator's machine, a public candidacy file with proof of possession and a signed clock report, the corrected runbook); run-node.sh, RUN-A-NODE.md and SPEC.md: the follower configuration described as it is (the attach, validatorCount, forkBlock and seal-cap properties it carries are inert on a follower) 2026-10-20 08:12:28 +03:00
Aere Network
b1c6c6d1e9 run-node.sh, RUN-A-NODE.md, SPEC.md: the follower options re-derived from the live archive node (30 properties); the four message-type post-quantum enforcement heights of chain 2800 (commit 17,250,000, proposal 17,400,000, round change 17,550,000, prepare 17,700,000) were missing 2026-10-19 02:59:06 +03:00
Aere Network
60ffd69de2 Patch 0010: the chain-2800 fleet distribution of 2026-10-14 (AIP-22 stage R: the round-bound post-quantum commit seal, the v3 anchor certificate and the decided head, inert until aere.pq.commitRoundBlock is set, which run-node.sh does not do; active on testnet 28001 from block 6,157,024 since 2026-10-14); run-node.sh applies 0010; anchor corpus restaged from the recipe (353 .java files, identical to the recipe); LICENSING regenerated; SPEC.md (2.3 certificate element in one place v1/v2/v3, 2.6, 2.7, 3.1, 3.3, 3.4, 3.5, 6.4, 7, 8 D13, 9 G11), RUN-A-NODE.md and README.md with dated notes; measured: patches 0001 and 0003 to 0010 on a pristine d2032017 reproduce the generator's tree exactly (same tree id), the build equals the fleet distribution class for class (3,602 classes, no class with different code) 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
 2026-10-14 19:44:51 +03:00
Aere Network
9fe4dac73e SPEC 2.6 and 3.1, README, anchor/README: message-layer enforcement stated per client (corrected 2026-10-09; from 2026-09-17 the text said all four message types are refused on both clients, while the second client enforces commits since block 18,131,633 and applies the other three types from AIP-22 stage 4, whose height is not yet set on chain 2800; on testnet 28001 since 1,314,403 and 3,117,000); dated notes, nothing removed 2026-10-10 00:02:37 +03:00
Aere Network
97542b5f1e SPEC 3.5: the seal-window journal domain AERE-PQ-SEALWINDOW-1 of AIP-21 (patch 0007) documented by dated note; nothing removed 2026-10-07 15:50:25 +03:00
Aere Network
e05efd57f2 SPEC/RUN-A-NODE: reference point aere.pq.checkpoint documented, rewrite bound of 2026-10-07 in the formal table, 3.1 corrected by dated note; nothing removed 2026-10-07 15:31:41 +03:00
Aere Network
e63135ed39 Seals stated as many as the quorum, proving that those validators signed, not that the block was decided (AIP-22 erratum of 2026-10-01) 2026-10-01 19:11:34 +03:00
Aere Network
1bd3f5b587 SPEC and anchor README: the certificate exception stated exactly (an anchor can be certified over the undecided sibling of the decided block; measured in a fixture, not exercised), with both adversaries; internal finding identifiers replaced by descriptions 2026-10-01 18:33:22 +03:00
Aere Network
1238760940 D-470 / AIP-22 erratum 2026-10-01: the verifier prints POST-QUANTUM CERTIFIED and says what a certificate proves (its signers sealed the block post-quantum, in some round) and what it does not (that the block was decided); SPEC and the anchor README qualified the same way 2026-10-01 17:09:27 +03:00
Aere Network
063424c490 Patch 0008: AIP-22 stages 1 to 3 and the rest of the chain-2800 fleet distribution of 2026-09-29; run-node.sh applies it, passes the stage-3 properties, ships the registry v3 epoch and rebuilds when the patch set changes 2026-10-01 15:21:46 +03:00
Aere Network
ea4ebcda5d AIP-22 stages 1 to 3 on chain 2800 in the node package; verifier no longer prints the stage-5 sentence on chain 2800 
README, SPEC, RUN-A-NODE, SECURITY, AUDITS and anchor/README now state the live rules: at least seven of
ten seals per scheme from block 20,715,632 (stage 1), Falcon-512 at every 32nd block and SLH-DSA-SHA2-128s
at every 128th from block 20,746,736 (stage 2), post-quantum validator ids in the header and in
qbft_getValidatorsByBlockNumber from block 20,836,228 (stage 3). Stages 4 and 5 are not active on chain 2800.

tools/verify-anchor.mjs: the FINALIZED line said on every chain that a header between anchors carries only
its proposer's seal, which is true only where AIP-22 stage 5 is active (testnet 28001). It now reports what
it measured: on chain 2800 headers between anchors carry the validators' classical ECDSA commit seals.
Checked on both chains on 2026-10-01: chain 2800, 4/4 anchors verified, ECDSA branch printed; testnet 28001,
2/2 anchors and 20/20 proposer seals verified, stage-5 branch printed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-01 13:27:11 +03:00
Aere Network
9fd694b888 AIP-22 stage 2 on chain 2800: from block 20,746,736 a Falcon-512 anchor certificate every 32 blocks and the SLH-DSA-SHA2-128s layer every 128 (schemeSchedule falcon-512/32+slh-dsa-sha2-128s/128) 2026-09-29 21:09:36 +03:00
Aere Network
1779ac8a8b AIP-22 stage 1 on chain 2800: anchor certificate threshold K=7, the QBFT quorum of ten validators, from block 20,715,632 2026-09-29 16:07:49 +03:00
Aere Network
a7fa601e97 docs: the anchor cadence is every 128th block from 17,225,968 (2026-09-05), not every 32nd; the minimum is six of each scheme, of ten validators since 2026-09-11; fork depth bound and checkpoint period restated for 128 2026-09-28 01:15:22 +03:00
Aere Network
294a041276 Citations: the declaration of unpublished paths regenerated (2026-09-24); cross-repository citations written with their repository name 2026-09-24 17:34:13 +03:00
Aere Network
5c99d51a3c RUN-A-NODE: the follower BESU_OPTS block carries -Daere.pqtx.forkBlock=19900000 like run-node.sh (the script already set it; the documented block lagged); SPEC 2.7: the seal-window journal opt-out is described as a property value, with its default read from PqSealWindowStore 2026-09-23 12:24:50 +03:00
Aere Network
0d22adbd62 Patches 0006 (AIP-20, native post-quantum transactions, type 0x50) and 0007 (AIP-21, per-block post-quantum finality record): the recipe now reproduces the chain-2800 fleet distribution of 2026-09-22 (wt3f12ef0d) class for class on consensus and on both AIPs, with the Apache 4(b) notice inside every modified upstream file and 20 lines of context; run-node.sh arms aere.pqtx.forkBlock=19900000 for followers of chain 2800; SPEC 2.7 and 5.3; RUN-A-NODE carries the measured record; LICENSING regenerated 2026-09-23 01:28:43 +03:00
Aere Network
54774eb719 SPEC 1.2.0 amended 2026-09-17: the four enforcement heights have passed (17,250,000 / 17,400,000 / 17,550,000 / 17,700,000, 5-8 September), hybrid keys live since 17,047,600; 'emission only' is dated history; LICENSING regenerated 2026-09-17 21:25:42 +03:00
Aere Network
7d40356aeb bootnodes: the second published address is withdrawn since 2026-09-11 (its host no longer fits the rule that a bootnode is not a validator; a replacement public read host follows); anchor corpus re-staged from the overlay (read-path classes and their tests, controller import-time retry) 2026-09-11 15:00:59 +03:00
Aere Network
a2d2db9693 SPEC.md, registries/README.md: ten validators since 2026-09-11 (the tenth is the Nethermind client): f=3, QBFT quorum 7 of 10; the anchor certificate minimum stays 6 seals, now below the quorum; dated history kept 2026-09-11 14:18:32 +03:00
Aere Network
b54aba6381 follower options re-derived after the fleet dropped attachBlockAcknowledgePast (21 properties) 2026-09-10 20:28:30 +03:00
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