c03d4266ebDated correction 2026-11-04 (fourth pass) to vote and message attribution since block 24,300,000: one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01)
main
Aere Network
2026-11-04 10:35:12 +0200
8db21bdc75Dated correction 2026-11-04 (third pass) to vote attribution since block 24,300,000: README, anchor/README and validator/README (QBFT whose votes every validator attributes only through post-quantum seals; the second client's other three message types), one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01)
Aere Network
2026-11-04 08:39:11 +0200
6514604819Dated correction 2026-11-04 to the vote attribution since block 24,300,000 (one path of the second client until 2026-10-31 12:27Z; AIP-22 rule 3, correction of 2026-11-01): SECURITY.md, anchor/README.md, validator/README.md
Aere Network
2026-11-04 05:32:57 +0200
b75b3981b3validator/README.md: block interval 0.60 s on average over the 100,000 blocks to 2026-11-03 (was 0.62 s before 2026-10-15)
Aere Network
2026-11-04 01:34:33 +0200
ab9848ab24tools/verify-anchor.mjs: H_hdr per chain; a header without the proposer seal at or above H_hdr is a FAIL (D-401)
Aere Network
2026-10-31 21:32:37 +0200
528f88b53fAIP-22 T5 pe 2800 (H_hdr 25.080.000, 2026-10-30): proza scrisa de proza-trepte.py T5 --scrie --formulare 1
Aere Network
2026-10-31 14:28:21 +0200
961dc3c512T5 la 25.080.000 (la-activare.py T5 --scrie, 12:46Z): H_hdr si H_ev = 25.080.000 in configuratia kitului public de validator si de nod, in configuratiile de conformitate 2800 (Besu si clientul 2), in inaltimi.json si in asteptarile trusei publice; cele 4 copii ale verificatorului raman identice, proba orarului 35/0, verificatorul ca un strain VERIFIED 10/10. Proza ramane pe lumea de dinainte pana la H (pasul de dupa H)
Aere Network
2026-10-30 14:48:05 +0200
0861b2ca39validator/README.md: the published patch series (0001-0010) does not yet include the decision journal (2026-10-28)
Aere Network
2026-10-29 01:49:56 +0200
3b06139f6dRunda 11 a reviziei prozei (2026-10-28): anchor/README (treapta 5, clientul 2), tools/verify-proof.mjs (prefixul de integritate), vectors/SURSE.md in engleza, declaratia de citari
Aere Network
2026-10-29 00:25:55 +0200
521210c71bDated corrections (2026-10-28): SPEC.md, SECURITY.md, AUDITS.md and anchor/README.md state what an anchor certificate is bound by (its digest sits in the hashed part of the header, so a node that validates the header refuses a detached or replaced certificate, while the block hash does not change); tools/verify-proof.mjs and tools/verify-anchor.mjs are the same files as those served at aere.network/tools
Aere Network
2026-10-28 12:46:28 +0200
cdc523ea64Dated corrections (2026-10-27): anchor/README.md, the number of Falcon-512 seals an anchor carried in practice is stated with its measured ranges and dates (up to five, most three to five, under the write cap of five until 2026-08-16; eight or nine at nine validators; eight to ten at ten validators, over 400 anchors measured 2026-10-27). tools/verify-anchor.mjs: the ROUND leg names where it is active (testnet 28001 since block 6,157,024; chain 2800 since block 24,148,752), element 6 is counted from 0, and the tool exits 2 (UNMEASURED, with the reason) when the endpoint serves another chain than CHAIN_ID or does not say which. Correction to the message of 9820765 (2026-10-27): it also listed 'the follower's rewrite bound', which belonged to the previous round, and said 'three to five' where the text says 'three or more'.
Aere Network
2026-10-28 00:04:54 +0200
9820765ebbDated corrections (2026-10-27): the package publishes one bootnode (since 2026-08-25) and run-node.sh uses it by default; two addresses from 2026-08-25 to 2026-09-11, one since; the follower's rewrite bound and the threshold ceiling comment brought to the measured anchors (most carried three to five valid seals before 2026-08-14, only some in the lowered window one or two); SPEC and anchor/README the same
Aere Network
2026-10-27 15:00:44 +0200
6ece1f2a6cDated corrections (2026-10-27): a validator, not every node, refuses an anchor below the threshold (a node started from this package lowers the count to one seal; SPEC 6.4); the startup guard refuses above the quorum and only warns below it; anchors carry at least one seal in the warm-up and three or more after; the follower's rewrite bound is 33 from stage R; run-node.sh comment and verify-live-precompiles.mjs brought to the same form
Aere Network
2026-10-27 06:47:47 +0200
a537b7c9d1AIP-22 stage R and stage 4 on chain 2800, dated corrections (2026-10-26): README patch rows 0009 and 0010 now say the heights were crossed (24,148,752 on 2026-10-24, 24,300,000 on 2026-10-25); RUN-A-NODE: the seal-threshold ceiling of the published follower weakens what it checks (SPEC 6.4), the startup guard refuses above the quorum and only warns below it, the v2 certificate dated 2026-09-04; SPEC 3.7 and 6.4 the same
Aere Network
2026-10-26 22:55:29 +0200
c3e0bd3858RUN-A-NODE: AIP-22 stage R is in force on chain 2800 since block 24,148,752 (reached 2026-10-24); dated note, four rules, the certificate forms before H_r named as such
Aere Network
2026-10-26 14:25:13 +0200
7ba8334ecfAIP-22 stage R and stage 4 in force on chain 2800: SPEC amended 2026-10-26 (stage R since 24,148,752, stage 4 since 24,300,000; below H_hdr a header is still admitted on the ECDSA commit seals of one round), README and anchor/README dated
Aere Network
2026-10-26 06:27:51 +0200
6c13bb314danchor/README: remove the duplicated stage R row of the armed-on-2800 table (introduced by the previous commit); the row stays once
Aere Network
2026-10-25 23:57:23 +0200
3e49753b31Dated: 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
Aere Network
2026-10-25 22:52:21 +0200
c4771b6b32AIP-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
Aere Network
2026-10-25 08:14:30 +0200
89d557000aanchor/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
Aere Network
2026-10-24 12:16:21 +0300
07bee6902eanchor/README: validatorii sunt numiti prin id-urile post-cuantice AIP-22 din blocul 20,836,228 (treapta 3); corectie datata 2026-10-22
Aere Network
2026-10-22 19:45:44 +0300
9a65dce22fInaltimile AIP-22 anuntate pe 2026-10-22: H_r = 24.148.752 (purtat de run-node.sh si de validatori din 2026-10-21) si H_fin = 24.300.000; RUN-A-NODE nu mai spune ca H_r nu e setat (nota datata, inclusiv promisiunea de publicare in aceeasi ora, netinuta), SPEC: amendamentul din 2026-10-22, README si runbook-ul ancorei cu forma anuntata
Aere Network
2026-10-22 17:43:14 +0300
87d320e057validator/README.md: ritmul lantului la ~0,62 s pe bloc (masurat), nu 0,6
Aere Network
2026-10-22 15:23:06 +0300
bf1333c335run-node.sh and RUN-A-NODE.md: the four message-seal layer options (proposal, prepare, commit, round change) appeared twice after the T4 entry of the same day; they were already set in the follower options, so the second copy is removed (same values, same node behaviour)
Aere Network
2026-10-22 02:33:40 +0300
44eecf5aa6T4 on chain 2800 at block 24,300,000: from that height every block is final post-quantum (the anchor that covers it decides it, not ECDSA); run-node.sh and the runbooks carry aere.pq.finalityBlock with the four post-quantum layers it requires
Aere Network
2026-10-22 02:23:41 +0300
c3ef72b82cTR 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
Aere Network
2026-10-21 20:46:21 +0300
7e6dad4239TR 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
Aere Network
2026-10-21 20:02:04 +0300
604e33d0a0CITATIONS-UNRESOLVED.md: the six files the validator runbook names and this repository does not carry, declared (admission-params.json and static-nodes.json are sent by the Foundation, aere-candidacy.json is written by the kit on your machine, docker-compose.yml and config.toml are served at aere.network/validator/, registry-v3-20836228.json at aere.network/pq/manifests/)
Aere Network
2026-10-21 12:07:19 +0300
4f6970f31crun-node.sh and the two validator kit scripts are executable, as the runbooks invoke them (./run-node.sh, validator/validator-keys.sh, validator/validator-candidacy.sh)
Aere Network
2026-10-20 08:16:02 +0300
f7930b2ff9validator/: 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)
Aere Network
2026-10-20 08:12:28 +0300
3ff53e4c05tools/verify-anchor.mjs: the certificate form is judged by height, as the clients do (v1 below V, v2 from V: 17,047,600 on 2800, 176,000 on 28001; v3 from H_r), and the v1/v2 certificate rows are decoded canonically (whole scalar values, known scheme tag, index in four bytes, non-empty signature, at most 64 rows in v2); a v1 height accepts Falcon-512 only. Before this change the tool took the form from the bytes below H_r and accused 20 of 20 healthy v1 anchors of testnet 28001 (175,360 to 175,968). Measured: chain 2800 201 of 201 anchors past V verified, testnet 28001 40 of 40 past V; same verdict as the previous tool on anchor 23,452,880 of chain 2800.
Aere Network
2026-10-19 06:54:55 +0300
b1c6c6d1e9run-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
Aere Network
2026-10-19 02:59:06 +0300
dfdfc1ad66RUN-A-NODE: the one command applies nine mainnet patches (0001, then 0003 to 0010), not four; the sentence had not followed the patch set since 0005
Aere Network
2026-10-15 11:45:01 +0300
60ffd69de2Patch 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)
Aere Network
2026-10-14 19:44:51 +0300
e01ba38e6ftools/verify-anchor.mjs: commit-round height of testnet 28001 is set (6157024); mainnet 2800 unchanged
Aere Network
2026-10-12 12:39:28 +0300
5161a79eb7Citations: CITATIONS-UNRESOLVED.md regenerated with the checker's exclusions (a version range in backticks is not a file path)
Aere Network
2026-10-12 06:12:46 +0300
c017f22f98Citations: CITATIONS-UNRESOLVED.md regenerated against the whole published family (the previous regeneration indexed only the local bundle and declared as unpublished a few paths a reader can open)
Aere Network
2026-10-12 06:05:17 +0300
c3f0c01c8dCitations: regenerated CITATIONS-UNRESOLVED.md (O-017, 2026-10-12); cross-repository citations written in the side-by-side form
Aere Network
2026-10-12 06:02:39 +0300
8de1ab2184tools/verify-anchor.mjs: a certificate in v3 form below the commit-round height is refused with AERE-PQ-V3-01 before any decoding (form on height first, as both clients do); an index wider than 31 bits and an element 6 that is not a list are named refusals; v1/v2 verdicts unchanged (20 anchors on chain 2800 and 20 on 28001, identical rows)
Aere Network
2026-10-10 23:38:49 +0300
9fe4dac73eSPEC 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
Aere Network
2026-10-10 00:02:37 +0300
76a70f6422Patch 0009: the chain-2800 fleet distribution of 2026-10-02 (heard-seal judge and pending-commit buffer, both acting only from the AIP-22 stage 4 height; snap-request cap, GHSA-pcv4-pxhv-99m7); fifteen 4(b) notices of patch 0008 now name patch 0008; run-node.sh applies 0009; anchor corpus restaged from the recipe; measured: the recipe build equals the fleet distribution class for class
Aere Network
2026-10-09 14:25:20 +0300
c05b2ba97btools/verify-anchor.mjs: certificate form v3 (round-bound commit seal, AIP-22 erratum): dispatcher on the first element, refusal codes AERE-PQ-V3-01..08, validator set of the parent, 'PARENT DECIDED IN ROUND r' only at a QBFT quorum of verified members; v1/v2 verdicts unchanged (20/20 on chain 2800 and 28001 before and after)
Aere Network
2026-10-07 17:11:26 +0300
97542b5f1eSPEC 3.5: the seal-window journal domain AERE-PQ-SEALWINDOW-1 of AIP-21 (patch 0007) documented by dated note; nothing removed
Aere Network
2026-10-07 15:50:25 +0300
e05efd57f2SPEC/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
Aere Network
2026-10-07 15:31:41 +0300
1c6d583f6aregistries/README.md: the hosts the files were read from are separate hosts, all operated by the Foundation today (the text said 'independently operated')
Aere Network
2026-10-05 17:49:18 +0300
1fa2ed0f46tools/verify-proof.mjs: a file that is not an envelope is a named refusal, and the signature scheme is bound to the key (the form served at aere.network/tools since 2026-10-03); LICENSING.md regenerated over the files the package carries
Aere Network
2026-10-05 17:18:54 +0300
88a87df694tools: the on-chain pin proven under the certified state (mpt.mjs), shared by verify-anchor.mjs and verify-proof.mjs
Aere Network
2026-10-02 06:23:56 +0300
a406a193f6anchor/BASE.txt: the date of the restaging is 2026-10-01 (UTC), not 2026-10-02 (the author's local date)
Aere Network
2026-10-02 01:15:12 +0300
f4b0a3ce08Anchor corpus restaged from the published recipe itself (base tree plus the patches run-node.sh applies, not the working overlay): every file the patches change is here, modified upstream files carry their Apache 4(b) notices, one internal reference is gone; BASE.txt says what the directory holds
Aere Network
2026-10-02 00:50:15 +0300
725aeebb65Anchor verifier: the two dated historical lapse windows of chain 2800 transcribed from the production client (not enforced at all, then a threshold of one), the fleet's threshold before 13,034,000, and index order required as in production
Aere Network
2026-10-01 20:28:51 +0300
d56a120462Anchor verifier: the validator set is read from the parent header the certificate seals (bound to its hash), with no 1000-block cache; distinct members counted once per scheme
Aere Network
2026-10-01 20:03:55 +0300
e63135ed39Seals stated as many as the quorum, proving that those validators signed, not that the block was decided (AIP-22 erratum of 2026-10-01)
Aere Network
2026-10-01 19:11:34 +0300
1bd3f5b587SPEC 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
Aere Network
2026-10-01 18:33:22 +0300
1238760940D-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
Aere Network
2026-10-01 17:09:27 +0300
fe41803c07RUN-A-NODE and run-node.sh: the follower's emergency-ceiling ERROR line is logged for every imported block since patch 0008 (measured), not once per anchor
Aere Network
2026-10-01 15:24:14 +0300
063424c490Patch 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
Aere Network
2026-10-01 15:21:46 +0300
ea4ebcda5dAIP-22 stages 1 to 3 on chain 2800 in the node package; verifier no longer prints the stage-5 sentence on chain 2800
Aere Network
2026-10-01 13:27:11 +0300
9fd694b888AIP-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)
Aere Network
2026-09-29 21:09:36 +0300
6765c0d2b2anchor corpus: the consensus sources the fleet runs today (commit seal signed once per round, round-change round cap, anchor lapse guard, tests)
Aere Network
2026-09-29 16:20:57 +0300
1779ac8a8bAIP-22 stage 1 on chain 2800: anchor certificate threshold K=7, the QBFT quorum of ten validators, from block 20,715,632
Aere Network
2026-09-29 16:07:49 +0300
2d3812835ftools/package.json: the verifier's dependencies, so that the published instruction works from scratch (npm install in tools/, then node verify-proof.mjs proof-vectors/...). Until now the package had no package.json: npm install installed nothing and verify-proof.mjs could not start. proof-vectors/README.md: the commands run from tools/.
Aere Network
2026-09-29 11:47:48 +0300
31604bab02tools/verify-proof.mjs: exit 1 from verify-anchor.mjs counts as a failed anchor only with its own verdict line (FAIL:/PROBLEMS:); a verify-anchor.mjs that cannot start (a dependency not installed) now gives UNMEASURED instead of INVALID. proof-vectors/README.md: the notary on chain 2800 holds other digests (since 2026-09-17), none of these vectors; the earlier line said nothing was notarized there.
Aere Network
2026-09-29 11:43:27 +0300
a7fa601e97docs: 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
Aere Network
2026-09-28 01:15:22 +0300
c239cbd750tools/verify-proof.mjs: the chain comes from --chain, else from the chain the envelope's notarization declares (when known), else 2800. An envelope notarized on the testnet 28001 and checked without --chain used to be looked up on 2800 and reported INVALID. The notary stays the known contract of that chain (or --notary); an address written in the envelope is never trusted as the notary.
Aere Network
2026-09-27 20:48:58 +0300
93f9d5839banchor: the propagation adoption gate (rule C, D-412) is OBSERVE by default - it computes the same verdict and adopts, logging 'would NOT adopt'; ENFORCE only with aere.d412.adoptionGate=enforce. On the public testnet the enforcing form froze a validator that had missed one height's commit messages (D-419). Adds PqTipAdoptionGateModeTest. LICENSING.md regenerated over the 209 files the package carries.
Aere Network
2026-09-27 20:35:53 +0300
71bce697d1tools/verify-proof.mjs: reference verifier of the AERE Proof Protocol (AIP-23), finality from a state a verified post-quantum certificate covers (anchor via verify-anchor.mjs, parent header bound by hash, Merkle proof of the notary storage); tools/proof-vectors/: conformance envelopes with expected verdicts
Aere Network
2026-09-27 06:43:30 +0300
54ab30407cverify-anchor.mjs: ANCHOR_REPORT=<file> writes the most recent verified anchor and the parent hash its seals signed, as JSON, for tools that build on it (nothing printed changes)
Aere Network
2026-09-27 06:36:36 +0300
75b2872e13verify-anchor.mjs: early refusals stop without process.exit() (on Windows it returned 127 instead of 1 after a network request); any other uncaught error still fails the run
Aere Network
2026-09-27 05:32:06 +0300
0b36247051verify-anchor.mjs: step 6 admits a re-proposed block sealed by its round's proposer (AIP-22 section 5 as corrected 2026-09-25, now running on testnet 28001); builder rule, round bound and canonical round on every header; exit code set, not process.exit
Aere Network
2026-09-27 05:14:52 +0300
0f6ec82fa1verify-anchor.mjs: step 6, the proposer's Falcon-512 seal on every recent header (AIP-22 stage 5), verified against the v3 registry key of its index and bound to the coinbase; proven on testnet 28001 with two planted forgeries rejected
Aere Network
2026-09-24 23:01:51 +0300
c0e6b62d71anchor/README.md: ancora la fiecare al 128-lea bloc (la 32 pana la 17.225.968)
Aere Network
2026-09-24 22:38:50 +0300
387615b0fbCitations: declaration regenerated against the whole published family (paths in sdk-js and aere-client2 resolve and are no longer listed)
Aere Network
2026-09-24 17:36:27 +0300
294a041276Citations: the declaration of unpublished paths regenerated (2026-09-24); cross-repository citations written with their repository name
Aere Network
2026-09-24 17:34:13 +0300
344ba39314anchor: the corpus carries AIP-22 stage 5 (headers sealed by the proposer's post-quantum seal, no ECDSA committed seals) and the stage-3b correction (a commit's hybrid seal judged with the v3 epoch's key)
Aere Network
2026-09-24 02:29:37 +0300
ab90cc5b06verify-anchor: a certificate is a NON-EMPTY item 6 (AIP-22 stage 5 headers carry an empty certificate slot between anchors)
Aere Network
2026-09-24 00:03:31 +0300
71412b9792anchor: the corpus carries AIP-22 stage 4 (message authorship from VERIFIED post-quantum seals, the startup guards AERE-PQC-FIN-01/02/03, the checkpoint option), unarmed on chain 2800 and proven on testnet 28001 (H_fin 3,117,000); the armed-on-2800 table says so row by row; LICENSING.md lists the new files
Aere Network
2026-09-23 22:48:38 +0300
099908a4caanchor: the corpus carries the AIP-22 stage 1 to 3b code (per-scheme intervals, post-quantum validator identity, v3 key registry, key rotation under an id), unarmed on chain 2800 and proven on testnet 28001; the armed-on-2800 table says so row by row; LICENSING.md lists the new files
Aere Network
2026-09-23 20:08:22 +0300
a94c0f2686verify-anchor: from KEYS_FROM the OK line names the registry v3 epoch whose keys verified the seals, not the key manifest
Aere Network
2026-09-23 18:35:06 +0300
089dc9803cverify-anchor.mjs: AIP-22 stage 3b read path, inert until an index marks it - from KEYS_FROM (or the v3 epoch whose index entry carries keysFrom) the key and the id of a seal's index come from the v3 epoch in force at the parent, as both clients read them; the ECDSA link of an id is inherited across epochs that omit it, and an id linked again drops its older address. Without keysFrom anywhere nothing changes: chain 2800 5/5, testnet 28001 5/5 re-run on 2026-09-23.
Aere Network
2026-09-23 16:05:24 +0300
944dc0bba6tools: verify-anchor.mjs discovers registry v3 epochs (AIP-22 stage 3, formatVersion 3 entries of the same manifest index) and verifies each in full with registry-v3.mjs (every proof of possession, every ECDSA link, the rotation chain, the Merkle registry hash), then requires every v3 row to carry exactly the Falcon-512 key, SLH-DSA key and address of the key manifest that signs at its height; the identity height is the first epoch's bindHeight, IDENTITY_BLOCK=none disables it as a negative control. Adds tools/registry-v3.mjs and tools/falcon512.mjs, which verify-anchor.mjs imports and the package did not carry. Checked 2026-09-23: testnet 28001 20/20 with its published v3 epoch (registry hash 0xd19eef4a..., identity from 3,080,010); chain 2800 20/20 unchanged; a byte-altered epoch and an epoch whose SLH-DSA key differs from the signing manifest both refused with the reason.
Aere Network
2026-09-23 15:33:49 +0300
79e5dafd53verify-anchor.mjs: per-scheme anchor intervals (AIP-22 stage 2: SCHEME_SCHEDULE entries like falcon-512/32+slh-dsa-sha2-128s/128; a scheme off its own grid at an anchor is surplus, verified but not required) and post-quantum validator identity (AIP-22 stage 3: IDENTITY_BLOCK + REGISTRY_V3 translate the validator set to ids from H_id); testnet 28001 default gains the stage-2 step 3070656. Proven 2026-09-23 12:07Z on 28001: 11 of 11 anchors after 3,070,656 accepted (3 hybrid on the 128 grid, 8 Falcon-only at 32), and the pre-stage-2 schedule refuses exactly the 8 Falcon-only; 20 of 20 on chain 2800 unchanged.
Aere Network
2026-09-23 15:08:45 +0300
5c99d51a3cRUN-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
Aere Network
2026-09-23 12:24:50 +0300
b8e9bdf971verify-anchor.mjs: the testnet 28001 default seal-threshold schedule gains the AIP-22 stage-1 rehearsal step 2988864:4 (the per-scheme minimum becomes the QBFT quorum, 4 of 5); chain 2800 unchanged, and any value is still overridable via MIN_SEALS_SCHEDULE
Aere Network
2026-09-23 02:51:21 +0300
0d22adbd62Patches 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
Aere Network
2026-09-23 01:28:43 +0300
54774eb719SPEC 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
Aere Network
2026-09-17 21:25:42 +0300
690340357dLICENSING.md: the regenerator is cited by a path this package does not ship; the citation now names the file a reader can open. Unresolved-citation disclosure regenerated against the full published family
Aere Network
2026-09-12 09:50:41 +0300
17eee07493RUN-A-NODE: your clock is the fifth requirement, with the BREACH_OF_PROTOCOL line it produces when it is a second behind
Aere Network
2026-09-12 08:10:31 +0300
aeee182204LICENSING: lista fisierelor cu copyright strain e generata din fisierele pachetului, nu scrisa de mana; peticul 0003 arata antetul amontelui pentru build.gradle
Aere Network
2026-09-12 02:22:24 +0300
1fba9df623anchor/README: the six-of-nine quorum sentence is dated now that the set is ten; RUN-A-NODE: what the emergency-ceiling ERROR stream is and what a real refusal looks like
Aere Network
2026-09-12 01:51:12 +0300
50bf1a07caprecompiles: withdraw the uncitable 'audited' adjective from the patch and the published sources (O-006, D-376)
Aere Network
2026-09-11 21:33:52 +0300
ba7f09d46dRUN-A-NODE: banda de heap masurata iar la 8,4 milioane (2400m intra in colaps de colectare, 3400m zero colectari complete)
Aere Network
2026-09-11 19:02:55 +0300
7d40356aebbootnodes: 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)
Aere Network
2026-09-11 15:00:59 +0300
a2d2db9693SPEC.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
Aere Network
2026-09-11 14:18:32 +0300
3b085911faRUN-A-NODE.md: dated note (2026-09-11) on the bootnodes: the second accepts only its configured peers; a node behind NAT keeps one peer and Besu does not fetch transaction-bearing bodies from a single busy peer; forward the P2P port and set --p2p-host
Aere Network
2026-09-11 12:39:33 +0300
cbaf4e15b9run-node.sh: GENESIS_SHA256 pinned to the v10 fleet genesis (e5038e6a...) that this package ships since 2026-09-10; the old pin (361709dc...) made run-node.sh refuse its own genesis.json at step 2/6 for ~13 hours (found 2026-09-11 by the from-genesis import proof)
Aere Network
2026-09-11 09:34:49 +0300
5839eb0468patches 0001/0003/0004: original messages with the Apache-2.0 section 4(b) notice restored, regenerated from the production tree whose modified upstream files now carry the in-file section 4(b) notice; 20 lines of context so the upstream headers are visible
Aere Network
2026-09-10 22:40:48 +0300
bc8dc80946patches 0001/0003/0004 regenerated from the production tree over the same file sets (section 4(b) notices); measured: a build from this recipe reproduces the fleet's consensus jars class by class
Aere Network
2026-09-10 22:08:27 +0300
5aac751be5registries/README: the nine-key hybrid registry is dated (superseded by hibrid-10.properties on 2026-09-10)
Aere Network
2026-09-10 21:06:47 +0300
Aere Network