91 Commits
Author SHA1 Message Date
Aere Network 86e2b34be1 AIP-22 erratum 2026-11-05: the round in a proposal's header must be the round of its message from H_fin (found 2026-11-02, refused by both clients' validators on chain 2800 since 2026-11-04) 2026-11-05 04:11:17 +02:00
Aere Network 65a0bcc640 Dated correction 2026-11-04 (fourth pass): AIP-22 (note to the correction of 2026-10-26) and AIP-7 (note to the note of 2026-10-28), one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01) 2026-11-04 10:37:53 +02:00
Aere Network 65d0890c3a Dated correction 2026-11-04 (third pass) to vote attribution since block 24,300,000: the second client's proposal, prepare and round-change layers in AIP-20, AIP-22 and the AIP index carry the correction (one path of the second client until 2026-10-31 12:27Z; AIP-22 rule 3, correction of 2026-11-01); a dated note to the note of 2026-09-24 in seven documents outside aips/ 2026-11-04 08:38:33 +02:00
Aere Network 9b5476a3e4 formal-consensus/RULEAZA-TOT.md: SMT suite re-measured 2026-11-04 (37/37 models, 301 PROVED, 159 CEX-FOUND, 0 FAILED); the 2026-10-07 counts kept as history 2026-11-04 06:19:21 +02:00
Aere Network 89ed8ca22d Dated correction 2026-11-04 to 'since block 24,300,000 (AIP-22 stage 4) every vote counts only with the verified post-quantum seal of its author' and its variants: one path of the second client until 2026-10-31 12:27Z (AIP-22 rule 3, correction of 2026-11-01); dated notes at the top of AIP-4, 7, 9, 13, 22 2026-11-04 05:32:16 +02:00
Aere Network f0e476dac3 AIP-7, 8, 13, 15, 16: dated note 2026-11-03 on vote attribution since block 24,300,000 (one path of the second client until 2026-10-31 12:27Z; see AIP-22 rule 3, correction of 2026-11-01) 2026-11-04 01:33:45 +02:00
Aere Network 9ed3c91f7d AIP-22: four dated notes (2026-11-01): two items withdrawn from the 2026-10-27 erratum, a commit's author in the form of rule 3, the field ecdsa required in fact; Errata entry 2026-11-01 19:13:59 +02:00
Aere Network 777bebf547 AIP-22: dated correction to rule 3 of section 4 (one path of the second client until 2026-10-31 12:27Z), Errata entry 2026-11-01 2026-11-01 14:07:58 +02:00
Aere Network 9abcbbf9d9 AIP-22: the per-author message quotas named without an internal register identifier (four sentences, Errata entry 2026-11-01) 2026-11-01 09:04:15 +02:00
Aere Network 412fc73285 AIP-22 stage 5 live on chain 2800 since block 25,080,000 (2026-10-30): prose, AIPs and dated notes 2026-10-31 14:55:18 +02:00
Aere NetworkandClaude Opus 5.5 7dcad651ca AIP-22 T5: nota datata in 22 de documente datate/derivate (proza-trepte le numise de adus la zi de mana)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-31 14:46:53 +02:00
Aere NetworkandClaude Opus 5.5 5efd857998 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]>
2026-10-31 14:28:23 +02:00
Aere Network 7e1ba97afc Runda 11 a reviziei prozei AIP-22 (2026-10-28): nota de consens corectata (17,250,000 commit; 17,700,000 orice mesaj), AIP-22 patch 0009, Errata in loc de note in capul AIP-urilor Final (AIP-7, AIP-13); citarile nerezolvabile declarate (formal-tla/, manifestul registrului v3) 2026-10-29 00:25:02 +02:00
Aere Network 78cc137b7d Dated corrections (2026-10-28) from the tenth review round: AIP-7, AIP-10, AIP-13, AIP-15, AIP-16, AIP-20 and AIP-22 and seven research documents; each change states its date in the text (what the anchor certificate is bound by, the consensus note after AIP-22 stage 4, and the denial-of-service paragraph of AIP-20, which no longer claims per-peer limits on pool admission) 2026-10-28 12:47:00 +02:00
Aere Network ac3d299e3f 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. 2026-10-28 00:07:07 +02:00
Aere Network 6d24576357 Dated corrections (2026-10-27): formal-consensus/RULEAZA-TOT.md translated into English and dated (it stated, without a date, facts of the chain of August 2026); the models print the chain facts of their time with the date, or the facts of today (labels and printed strings only, the logic and the verdicts unchanged: 37 of 37 models pass); README: 37 models counted on 2026-10-27 and the reproduction pointer to aere-docs REPRODUCE.md section 3b 2026-10-27 15:01:25 +02:00
Aere Network 9b2a69ab6b Dated corrections (2026-10-27): README (a validator refuses an anchor below the threshold; the published follower lowers the count to one seal); formal-consensus models print the chain facts of today or date the ones of their time (ten validators, the anchor certificate enforced since 2026-08-14, votes attributed through post-quantum seals since block 24,300,000); verdicts unchanged (ALL MODELS PASS) 2026-10-27 06:48:09 +02:00
Aere Network 42047a8b48 Dated corrections (2026-10-26): execution-kernel/mi-replay-diferential.mjs honesty field (since block 24,300,000, AIP-22 stage 4, consensus votes count only through their verified post-quantum seals; headers are still admitted on ECDSA commit seals until stage 5); aips/README index brought to the AIP index of the same date 2026-10-26 22:55:48 +02:00
Aere Network c87197bd8b AIP-22: dated correction to the transition principle (from stage 5 one post-quantum validator key can serve a non-validating node a branch up to the next anchor, which a quorum certificate ends) 2026-10-26 09:41:57 +02:00
Aere Network 0bf80e42fe AIP-22 stage R and stage 4 in force on chain 2800 (2026-10-24, 2026-10-25): dated corrections to the README, pq-stark README and AIP index (votes attributed only through verified post-quantum seals since block 24,300,000; headers still admitted on ECDSA commit seals until stage 5), AIP-1 and CONTRIBUTING editorial rules corrected with their date, AIP-22 dated correction to rule 2 of section 4, AIP-3 interval dated 2026-10-26 06:27:26 +02:00
Aere Network 4c4d57cd2c Dated correction (2026-10-26): README, ten Foundation-run validators since 2026-09-11 (f=3, commit quorum 7 of 10) 2026-10-26 00:07:50 +02:00
Aere Network 1b788f86d1 Dated corrections (2026-10-25): AIP-8 consensus note (per-block finality was the classical ECDSA statement until block 24,300,000, AIP-22 stage 4; the second client attributes every consensus message through its post-quantum seal since then); README: anchor certificate seals proved signing, not decision, below block 24,148,752 2026-10-25 23:00:30 +02:00
Aere Network c74184dc55 AIP index: the anchor certificate seals proved signing, not decision, below block 24,148,752; from that block (AIP-22 stage R) a certificate carrying the quorum of one round proves the decision 2026-10-25 22:51:57 +02:00
Aere Network 7493940923 AIP-22: dated correction to section 5 (after H_hdr a commit still carries the validator's ECDSA commit seal, checked by both clients as an additional check; no header carries an ECDSA signature) 2026-10-25 20:17:51 +02:00
Aere Network 7932becfb4 AIP-20, AIP-22, index and execution-kernel contract: AIP-22 stage 4 in force on chain 2800 since block 24,300,000 (2026-10-25), dated notes 2026-10-25 08:14:53 +02:00
Aere Network 200f4338f0 execution-kernel/MACHINE-INTERFACE-CONTRACT.md: restore the sentence on consensus finality as it stands today (classical secp256k1 ECDSA QBFT plus a Falcon certificate); the previous commit carried, by a staging race on 2026-10-24, a draft sentence written for AIP-22 stage 4, which is not in force before block 24,300,000 2026-10-25 03:47:40 +03:00
Aere Network 1e386c7e18 AIP-21, AIP-22: note added 2026-10-24: stage R (the round-bound post-quantum commit seal, COMMIT-2, and the v3 anchor certificate) is in force on chain 2800 since block 24,148,752; from that block a v3 certificate carrying the quorum of a single round proves the anchor's parent decided; stage 4 takes effect at block 24,300,000 (announced 2026-10-22) 2026-10-24 12:57:55 +03:00
Aere Network f54fb37175 AIP-23 proof kinds: agent-witness-checkpoint, a checkpoint of the hosted agents witness log (log name, size, RFC 9162 root, the witness, the chain where it is notarized, the merge delay) 2026-10-20 01:16:45 +03:00
Aere Network 0a58d9f04a AIP-22 conformance corpus: two equivocation-pair descriptions name the repaired form by its date (2026-10-16) instead of an internal tracking identifier; vectors, verdicts and blocks unchanged 2026-10-19 09:41:25 +03:00
Aere Network 316ba7171f AIP-23 proof kinds: secret-access carries requestHash (the presentation is signed for this exact request), claimedHolder/claimedPresenter, judged, and the allowed values of each field 2026-10-19 00:06:23 +03:00
Aere Network 6110ef2047 AIP-23 proof kinds: secret-access (a secrets service judged one request on a named secret: verdict, rules, presented identity and policy by digest; never the value); 17 kinds 2026-10-18 15:47:41 +03:00
Aere Network 39e0d944ca AIP-22 conformance corpus (section 9) regenerated from the repository: the equivocation-pair vectors now carry the round-bound COMMIT-2 form of 2026-10-16 (eight, two valid), judged identically by both clients 2026-10-16 10:40:43 +03:00
Aere Network 84e00729d1 AIP-22 section 6 (2026-10-16): the erratum paragraph made precise: the evidence verifiers of both clients judge the equivocation vectors identically; on incoming consensus messages the second client on chain 2800 requires the post-quantum seal on commits only (the other three types from stage 4, whose height is not set there); 'all four instances' reworded as the two new and two retired contract instances 2026-10-16 10:24:25 +03:00
Aere Network e1c39747ed AIP-22 erratum (2026-10-16), section 6: the first form of the equivocation-evidence contract took two COMMIT-1 seals (no round) as evidence; COMMIT evidence is now round-bound (COMMIT-2), new instances on testnet 28001, the old ones retired, both clients agree on the eight vectors 2026-10-16 03:55:34 +03:00
Aere Network 7a5340aea5 AIP-22: the measured shape of chain 2800 'today' (Motivation) gave the certificate grid and threshold of before stages 1 and 2; corrected in place with today's values (Falcon-512 every 32nd block, hybrid every 128th, at least seven per scheme) and a dated note (2026-10-12) 2026-10-12 13:16:19 +03:00
Aere Network 994eaacf8e Correction (2026-10-12): the 2026-09-24 consensus note said every QBFT consensus message must carry a Falcon-512 seal; on chain 2800 the nine AERE-client validators refuse any message without it, the second client enforces it only on commit messages. Clause corrected in place, with the date of the correction 2026-10-12 11:45:11 +03:00
Aere Network 382d9c44fc Citations: 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) 2026-10-12 06:05:25 +03:00
Aere Network 19039e5b71 Citations: regenerated CITATIONS-UNRESOLVED.md (O-017, 2026-10-12); the cross-repository citation in the rewrite-bound note written in the side-by-side form; AIP-8 restaged 2026-10-12 06:03:27 +03:00
Aere Network 381c8e508b AIP-22: correction dated 2026-10-11 - the external audit is no longer a precondition of the chain 2800 heights (scheduled after the remaining stages since 2026-09-30); stages 4 and 5 follow testnet 28001 with both clients and an internal adversarial review, which is not a third-party audit; the rows that said otherwise are kept as written 2026-10-11 10:32:20 +03:00
Aere Network 3b62b2c757 AIP-20, AIP-22, README: message-layer enforcement stated per client (corrected 2026-10-09): every validator refuses a commit without a post-quantum seal, the nine primary-client validators any consensus message since block 17,700,000; the second client enforces commits since 18,131,633 and the other three types from AIP-22 stage 4, whose height is not yet set on chain 2800; dated notes and an Errata entry, nothing removed 2026-10-10 00:02:22 +03:00
Aere Network 39ec3c684a AIP-21/22: dated errata notes of 2026-10-07 (fixture seals, tail counting, checkpoint bound); nothing removed 2026-10-07 15:31:33 +03:00
Aere Network 2fe5a51bbd formal-consensus, research: the rewrite bound under the round-free seal model (2026-10-07): the security argument and its z3 model, 13 proofs with 8 negative controls; 37 of 37 models in the suite 2026-10-07 13:43:13 +03:00
Aere Network c5f4691dfa formal-consensus: the reproduction steps name the clone root instead of a workstation path 2026-10-06 01:37:05 +03:00
Aere NetworkandClaude Opus 5.5 51c17f08de AIP-20: clarification dated 2026-10-05 under the quantum threat model: the post-quantum seal is already required beside the classical signature on consensus messages; what is not active is the seal as the validity criterion (AIP-22 stage 4)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-05 17:11:14 +03:00
Aere Network 4739d4206b AIP-20: key reuse with the empty ML-DSA context, and a dated correction on consensus enforcement; AIP-22 and README: seals stated as many as the quorum, proving signing, not decision (erratum of 2026-10-01) 2026-10-01 19:11:23 +03:00
Aere NetworkandClaude Opus 5.5 c9ba6d4bec AIP-21 erratum and AIP-23 note (2026-10-01), formal models annotated: the post-quantum commit seal carries no round
AIP-21: a record that reaches `post-quantum` shows that the commit quorum of distinct validators sealed the block
post-quantum in some round; it does not by itself prove that the block was decided (follows the AIP-22 erratum of the same
day). AIP-23: dated note on what the finality level rests on; level names unchanged. Three formal models carry a dated note
where they treated certificate uniqueness as a property of the code rather than of the model.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-01 17:10:21 +03:00
Aere NetworkandClaude Opus 5.5 51d63e4c17 AIP index: numbering is contiguous from 1 to 23 (the sentence still said 22, and that no AIP numbered 23 or higher existed)
Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-01 16:19:01 +03:00
Aere NetworkandClaude Opus 5.5 95435019dd AIP-22 erratum 2026-10-01: the post-quantum commit seal carries no round, so a certificate of seals does not prove that the anchor's parent was decided
Measured in the reference client: at N = 10, seven valid Falcon-512 seals over M(p) from rounds 0 and 2 while p' is decided in
round 3, and an anchor over p carrying them passes the certificate rules. Withdrawn as written until the commit seal binds the
round: the finality definition of section 1, the Rationale's implication that a quorum of seals proves consensus, and the
Security Considerations claim for H_fin. Chain 2800 below stage 5 is not affected. The original text stays; the correction is
dated in a note at the top and in the Errata.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-01 15:28:19 +03:00
Aere NetworkandClaude Opus 5.5 856c5df2f8 AIPs: dated notes for AIP-20, AIP-21 and AIP-22 on chain 2800; AIP-22 stages 1 to 3 active
AIP-22 described chain 2800 "today" as the chain before stages 1 to 3. A note dated 2026-09-30 says which
stages are active from which block; the index row and the README summary carry the same heights.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-01 13:27:18 +03:00
Aere Network 3117a33107 AIP-23: a sixteenth proof kind, agent-decision (an AI agent's action judged against a policy named by its hash, allowed or refused and why), with its conformance envelope; its actionHash is the SHA-256 of the canonical JSON of the action, so anyone can recompute it. Produced by the agents component published in aere-quantum the same day. All sixteen envelopes VALID with verify-proof.mjs offline. 2026-09-29 22:01:33 +03:00
Aere Network a464214626 AIP-23: the proof kinds AERE produces, with their conformance envelopes (aips/aip23-kinds/: fifteen kinds, authorization, settlement and provenance added 2026-09-28; KINDS.json lists each kind's required fields); correction: the notary on chain 2800 has held digests since 2026-09-17 (the measured status of 2026-09-27 said nothing was notarized there), Errata 1 2026-09-29 11:44:27 +03:00
Aere Network f86746a376 AIP-23 AERE Proof Protocol (Draft) published with its reference verifier and conformance vectors (aere-node/tools/); index: AIP-22 status brought to date, AIP-23 added 2026-09-27 06:44:07 +03:00
Aere Network 6d907fa2e9 AIP-22 conformance corpus complete: the ninth kind (classical-only fork, from rehearsal network 28099), all nine kinds judged conformingly by both clients; the options and files each harness judged with, per chain (config-28001/, config-28099/) 2026-09-27 05:57:01 +03:00
Aere Network dccd277337 AIP-22: dated addition of 2026-09-27, the public verifier's early refusals exit 1 on Windows (were 127) 2026-09-27 05:32:14 +03:00
Aere Network fa920a45a5 AIP-22: conformance corpus published (aips/aip22-conformance/, eight of the nine kinds of section 9, every vector judged by both clients); section 5 re-proposal correction and the 2026-09-25/26/27 stage records; erratum for section 5 2026-09-27 05:24:44 +03:00
Aere Network c40c52d3b6 AIP-22 erratum, section 9: conformance vectors are to be published (none yet); the stage proofs on 28001 are the two clients checked against each other on a live chain 2026-09-25 01:32:33 +03:00
Aere Network cd0b36af8d AIP-22 erratum: ECDSA-quorum ZK light clients stop following at H_id (the set becomes ids), not at H_fin; read in the guest program's verify_finality, corrected in place 2026-09-24 23:42:40 +03:00
Aere Network b1eceecbd8 Note added 2026-09-24 in seven research documents (validator-set figures are dated; ten validators since 2026-09-11) and in the Stage 4 execution contract (Block-STM on since 2026-09-05) 2026-09-24 23:12:35 +03:00
Aere Network 7f00c88a86 AIP-22: dated record, the public verifier checks the proposer seal on every recent header (stage 5), proven on testnet 28001 with two planted forgeries rejected 2026-09-24 23:04:07 +03:00
Aere Network b1f852bc52 AIP-2, 3, 7, 17: propozitiile la prezent despre sapte validatori datate (setul de zece din 2026-09-11, al doilea client validator); AIP-7 fara 'audited native code' 2026-09-24 22:38:31 +03:00
Aere Network 95ef18af25 Citations: declaration regenerated against the whole published family (paths in sdk-js and aere-client2 resolve and are no longer listed) 2026-09-24 17:36:34 +03:00
Aere Network 5c8d100173 Citations: the declaration of unpublished paths regenerated (2026-09-24); cross-repository citations written with their repository name 2026-09-24 17:35:07 +03:00
Aere Network 57fef08cd2 AIP-20: live on chain 2800 since block 19,900,000; the first native post-quantum transaction (block 19,900,028) imported identically by every node, the corrupted-signature control refused by both clients 2026-09-24 02:05:16 +03:00
Aere Network 72360f1ea6 AIP-22: stage 6 (on-chain equivocation evidence) built and proven on testnet 28001; the gas estimate replaced by the measurement 2026-09-24 01:35:25 +03:00
Aere Network c5cef2821f AIP-22: section 5 made exact (the certificate slot is present when the proposer seal is; the rule judges every header from H_hdr); stage 5 rehearsed, armed and proven on testnet 28001 2026-09-24 01:17:07 +03:00
Aere Network fbb8f318d2 AIP-22: stage 4 on testnet 28001 (message authorship from verified post-quantum seals, H_fin 3,117,000): the two holes found by reading the code before any live step, the guards AERE-PQC-FIN-01/02/03, the shared authorship vectors, and the proof (502 of 502 hashes equal between clients, five of five ids proposing, rhythm unchanged, negative control of the method); section 4 rule 3 made precise 2026-09-23 22:49:31 +03:00
Aere Network f4db867d80 AIP-22: dated stage records for stages 1 to 3b on testnet 28001 (quorum threshold, per-scheme intervals, post-quantum validator identity, key rotation under an id), with their negative controls; stage-0 measurement replaces the NOT MEASURED row 2026-09-23 19:41:55 +03:00
Aere Network c94b3f5c06 AIPs: AIP-20 and AIP-21 status rows carry the chain-2800 deployment of 2026-09-22 (AIP-21 live on all ten validators, AIP-20 armed for block 19,900,000); AIP-22 (post-quantum-only finality) added as a design-only Draft; the index no longer describes the pre-September world (seven validators, one client, no AIP above 19) and states which post-quantum layers are live with their heights 2026-09-23 01:30:13 +03:00
Aere Network a2fe6c46ba Citations: the unresolved-citation disclosure regenerated against the full published family (nine repositories, not four) 2026-09-12 09:50:51 +03:00
Aere Network ec3ca3368f AIP-8 through AIP-19 and CONTRIBUTING.md published: the index linked twelve documents this package did not carry. Validator counts carry their measurement date (errata on the Final ones, per AIP-1 section 5), the Fusaka activation block corrected to the measured 2,106,597, and the staging rewrites are now a checked table 2026-09-12 09:49:12 +03:00
Aere Network 83453d9a79 AIP-1, AIP-2, AIP-7, the template and the index brought to the working generation: the published governance text was missing entire sections, including the rules themselves (D-377) 2026-09-11 22:04:15 +03:00
Aere Network 16ce7e8989 AIP-7 erratum 1 and the PQC precompile draft: withdraw the uncitable 'audited' adjective from the wrapped library (O-006) 2026-09-11 21:34:40 +03:00
Aere Network 16ccb98d34 Citations: family-wide resolution (published repositories on the forge) and the disclosure regenerated 2026-09-02 21:51:59 +03:00
Aere Network c7374df846 Citations: the unresolved-citation disclosure regenerated (2026-09-02) 2026-09-02 21:39:47 +03:00
Aere Network 5129289cea formal-consensus: the post-quantum message-enforcement model and the runner wiring all 36 models; bench: the local test key marked synthetic 2026-09-02 20:34:15 +03:00
Aere Network 3c9205c3dc formal-consensus: carry the 2026-08-12 fix into falcon_blocking (the old block proved a constant, not the property) 2026-08-28 01:01:12 +03:00
Aere Network bc947dd371 Citations ledger: prune entries whose targets now resolve 2026-08-28 00:51:43 +03:00
Aere Network dcf3374f45 Citations ledger refreshed: every unresolvable cited path declared, stale entries pruned (generated by legaturi-repara) 2026-08-28 00:46:17 +03:00
Aere Network a2f4d835a3 Formal: partitii de retea si view-change x certificat PQ dovedite la N=9, cu controale negative
partition_safety_smt.py (N=9 f=2 q=6): split-brain imposibil, starvatie clasificata,
vindecare fara fork. anchor_viewchange_smt.py: o schimbare de runda pe ancora nu da
doua certificate valide diferite, si unicitatea vine din legarea de bloc, nu din K=3
sigilii (< cvorum). Rulatorul cablat: 35 modele, 282 PROVED + 149 CEX, 0 FAILED.
2026-08-24 20:02:07 +03:00
Aere Network 0164207076 README: nine validators (seven until 2026-08-09); consensus is classical ECDSA on every block with a post-quantum checkpoint every 32 blocks (>=3 of 9 seals since 2026-08-14); live height dated 2026-08-19 15:50:49 +03:00
Aere Network cde69bd25f Precision fix 2026-08-19: the three-seal anchor minimum has been enforced since 2026-08-14 (the schedule step is at block 13,034,000 but an emergency ceiling held the effective minimum to one until then); anchors universal since block 13,889,296 2026-08-19 15:46:59 +03:00
Aere Network 8e2b2fa7fa Dated note: the post-quantum anchor checkpoint qualifies the 'consensus remains classical' statements; the 14,050,000 per-block quorum claim was withdrawn on 2026-08-19 2026-08-19 14:37:34 +03:00
Aere Network f0fb52862f Correction 2026-08-19: the anchor SMT model proves K=3-of-9 on anchor blocks since 13,034,000; the 14,050,000 fork height changed no enforcement and the 'blocking quorum' wording is withdrawn; runner entry added 2026-08-19 14:31:57 +03:00
Aere Network f2ab368c36 Hostile-read repairs across the kernel artifacts: 17 confirmed over-claims fixed to honest
A 6-lens hostile panel with adversarial verification confirmed 17 attacks that
would hold in a public takedown. All repaired: the MI contract now carries the
two base-fee floor-lapse windows (12,978,617-13,087,959 and
13,596,033-13,596,141) as explicit ruleset validation exceptions, so a stranger
implementing the written rules no longer halts where our own follower did; the
honesty boundary now states the full record of reject-on-disagreement including
the windows, and why the fact stays load-bearing; the independence claim is
bounded (upstream skeletons yes, AERE ruleset has one author in both forks, so
a common-author bug passes any differential gate by construction); the harness
verdict claims only what it measures, records engine identity via
web3_clientVersion on every run, refuses same-URL endpoint pairs, and prints
its NOT MEASURED block on every run; stage 4 names the live engine (upstream
parallel processing enabled by default, idling on empty blocks) and its
oracle's model limits; 'governed registry' became 'owner-controlled' with the
single-key fact stated. The panel also confirmed the import-proof doc claimed
a two-month validation history where six days is the truth; fixed.
2026-08-15 23:28:24 +03:00
Aere Network 46c42164de SMT: registry index binding, the loader and the seal rule must read ONE mapping
Motivated by a real defect a from-genesis import proof found the same day: the
public patch set's loader bound key index 0 while its seal rule called it
unbound, rejecting a valid first anchor certificate that production accepts.
The model proves with z3 that under one shared index->address mapping,
'unbound never validates' is a theorem, and exhibits both divergence
directions: valid-rejected (liveness loss, the defect measured today) and
unvouched-accepted (safety loss, the silent one). Both proven impossible under
agreement. Six checks, each with the solver required to SAT the planted bad
world before the UNSAT proof counts. Engineering consequence stated: one
function, not two implementations of the same idea.
2026-08-15 22:52:13 +03:00
Aere Network 8546a4592d Crypto-agility layer verified live from a stranger's machine, with a negative control
The governed on-chain registry (AereCryptoRegistry) maps every registered
post-quantum algorithm to a live verifier: measured 2026-08-15, all 5
algorithms (Falcon-512, Falcon-1024, ML-DSA-44, SLH-DSA-128s, SHAKE256)
resolve to the live NIST precompiles 0x0AE1..0x0AE5, status active, and the
registry contract itself bears code. So 'crypto agility' is not a slide: adding
a scheme or retiring one is a governed registry write, not a hard fork.
Negative control: a planted fake verifier address is caught. Read-only,
eth_call and eth_getCode only. Building this caught two of my own decode bugs
(wrong selector, wrong tuple word) before they became a false public claim,
which is what verification-before-publication is for.
2026-08-15 22:51:00 +03:00
Aere Network 85495f3830 Execution Kernel Stage 4: parallel execution under MI, with a determinism oracle that goes red
Block-STM enters the kernel through the MachineInterface seam, not beside it. The
one guarantee, stated as a contract and proven: parallel execution produces the
byte-identical state root that serial execution produces, or the kernel refuses
it. The feared failure mode is a silent state divergence under contention, and
that is exactly what the negative control plants.

Run 2026-08-15 (WSL, Rust release build of parallel-executor):
- positive: harness reports 0 mismatches, parallel Block-STM == sequential on
  all profiles, seeds, and thread counts 4/8/16.
- negative control: disable the validation phase (the mechanism that catches a
  stale read and forces re-execution) and the harness reports MISMATCH on every
  contended profile. So the oracle is load-bearing, not applause.

No throughput number is claimed; 8-10x is proven capacity while chain 2800
blocks are empty. Parallel execution is not put on mainnet in this stage; the
equality that would make that safe is proven, so the switch becomes a measured
decision. One coordinated activation if it ever changes an observable, the
discipline proven at block 14,050,000.
2026-08-15 22:36:27 +03:00
Aere Network 42dd039ddb Execution Kernel Stage 2: the claim-chain gap detector, with lag as a first-class metric
Execution proofs are an audit layer OVER the chain, never under it. For that
layer to mean anything, the claim chain must be continuous, and this tool
measures three properties from the live chain: linkage (each window's
prevStateRoot equals the previous window's postStateRoot and the chain's real
root before the first), no gaps or overlaps in the tiling, and anchoring (each
postStateRoot equals the header.stateRoot the chain actually published, so the
proof proves the committed state and not a parallel one). It reports proving
LAG as a first-class number, because lag is the cost curve of proving and
hiding it is the failure.

Run and measured 2026-08-15 against rpc.aere.network: an 8-window synthetic
chain built from live state roots verifies clean; four negative controls (gap,
overlap, linkage, anchor) each make the detector go red, and the anchor plant
is isolated on the last window so it trips the anchoring rule specifically,
not linkage. Read-only, installs nothing. Points at a claims file when a public
proof endpoint exists; the deprecated aggregator V1 stays fenced.
2026-08-15 22:15:54 +03:00
Aere Network cea943ff57 Execution Kernel, Stage 1: the MachineInterface seam, contract plus a differential replay harness proven on real blocks
The kernel's first stage is not new infrastructure, it is a written contract
for the state-transition seam (pre_state, block) -> (post_state, receipts)
through StateView only, plus a harness that proves two independent clients
agree on the state root of real chain-2800 blocks, in both directions per the
D-150 rule (what was lost, not only what was added).

Run and measured 2026-08-15, from the two public endpoints (Besu at
rpc.aere.network, Nethermind at client2.aere.network): 24 blocks, 168 fields,
zero divergences. All four negative-control plants (value differs, block only
on one side, a lost field, a corrupted side) make the gate go red exactly
where planted. Installs nothing, three read-only RPC methods, runnable by
anyone. This makes "a second execution machine tomorrow" a mechanical slot,
not a promise.
2026-08-15 22:13:28 +03:00
Aere Network 4ce1928d9e Three formal models for the blocking post-quantum consensus, each with its negative control
Written and run against z3 4.16.0, exit 0, on 2026-08-15, the day the blocking
fork went live:
- anchor_blocking_quorum: past block 14,050,000 no anchor block finalizes with
  fewer than K=3 distinct valid Falcon seals; the negative control that permits
  2 seals is SAT (the violation is expressible), the property itself UNSAT.
- pqanchor_ceiling_monotonicity: the emergency ceiling can only LOWER the
  effective threshold, never raise it, and K_eff always fits under the write
  cap; a planted max()-instead-of-min() ceiling is SAT.
- registry_rotation_coverage: the registry schedule covers every anchor height
  with exactly one registry, no gap and no overlap, and a seal is checked
  against the registry active at the ANCHOR height; a planted schedule with a
  gap is SAT.
These extend the existing SMT corpus toward end-to-end verifiability of the
consensus, one of the pieces the roadmap calls distinctive.
2026-08-15 21:05:47 +03:00
Aere Network 6cb0140fae Republished from a clean root: the compiled artifact is gone from history, and the local line of work joins the sanitized public line
The public history carried kat/__pycache__/mlkem768_reference.cpython-314.pyc,
a compiled Python artifact embedding the operator's absolute local path. Text
secret scanners do not read compiled binaries, which is exactly how it slipped
through, and removing it from the tip would have left it reachable through the
old root commits. So this repository is republished from a single clean root.

This root also carries, from the previously unpublished line of work:
- corrected LICENSE year, LICENSING.md, VERIFY-POLICY.md, and
  CITATIONS-UNRESOLVED.md remeasured 2026-08-11 (101 paths, README aligned)
- O-018: run_consensus_verification.py ran 19 of 29 models and reported PASS;
  it now runs all 29, and computemarket_smt.py gains resolveByTimeout /
  reclaimUnsettled cases plus a negative control
- O-006: the word 'audited' removed from next to Bouncy Castle, twice, after a
  concurrent edit resurrected it
- O-014: prior art named and dated - Algorand's native falcon_verify shipped
  about ten months before AERE's precompiles; the primacy claim is withdrawn
  where it was implied
- bench/ scripts parametrized so they actually run for an outsider (the
  earlier textual sanitization left $STAGING unexpanded inside Python strings)
- AIP-2/AIP-3 errata with measured figures, spec remeasurements at 2026-08-01,
  and the spec-zk-stack retractions (owner is an operational key, not the
  Foundation; 'maximally sound' withdrawn; aggregator V1 deprecated)
The redacted bench-host environment files from the sanitized line are kept
exactly as published; the unredacted local variants are not carried.
2026-08-15 13:52:14 +03:00