aere-network/aere-client2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

README: the tenth validator of chain 2800 runs this client since block 18,083,404 (2026-09-11); what this repository holds and what it does not yet hold

Browse Source 
The Status section said 'produces mainnet blocks: no' and 'on an isolated testnet only', out of date since 2026-09-11. The
repository still holds the validation side as published in August 2026; the block-producing engine and the post-quantum message
layers that run on mainnet are not in it yet, and the README now says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Aere Network 2026-10-05 17:10:18 +03:00
parent a766124043
commit 71380f549f
1 changed files with 22 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
README.md
View File

@ -7,13 +7,22 @@ language on a different codebase, can follow chain 2800 and reach the same state
## Why a second client exists
Chain 2800 produces every block with Hyperledger Besu today. A consensus bug in Besu would produce a
wrong block and nothing in the validator set would stop it, because every validator runs the same
code. A second implementation is the only thing that can disagree.
Until block 18,083,403 chain 2800 produced every block with one client, derived from Hyperledger
Besu. A consensus bug in that client would have produced a wrong block and nothing in the validator
set would have stopped it, because every validator ran the same code. A second implementation is
the only thing that can disagree.
That is the whole point of this repository, and it is also the honest limit of what it achieves so
far: **this client follows and validates, it does not produce blocks on mainnet.** Client diversity
in production does not exist on chain 2800 yet.
Since block 18,083,404 (2026-09-11) the tenth validator of chain 2800 runs the client these
additions belong to: it proposes its share of mainnet blocks and validates every block the other
nine produce. Nine of the ten seats still run the first client, so the second adds an independent
check, not yet fault tolerance.
**What this repository holds, and what it does not yet hold.** The files here are the validation
side as published in August 2026: the precompiles, the QBFT header decoding and hashing, header and
seal validation, and the base-fee floor. The block-producing consensus engine and the post-quantum
message layers that run on the tenth validator today (AIP-20, AIP-21 and the active stages of
AIP-22) are not in this repository yet. Until they are, this repository is not the complete source
of what runs on mainnet.
## What is here
@ -48,6 +57,11 @@ redistributing, check the upstream terms as well as these.
## Status, stated plainly
- follows and validates chain 2800: yes
- produces mainnet blocks: no
- reached consensus with Besu as an equal validator: on an isolated testnet only
- produces mainnet blocks: yes, as the tenth validator, since block 18,083,404 (2026-09-11); the
engine that does so is not yet published in this repository
- reached consensus with Besu as an equal validator: on the public testnet (chain 28001) first, on
mainnet since that block
- audited by a third party: no
Until 2026-10-05 this section said "produces mainnet blocks: no" and "on an isolated testnet only",
which had been out of date since 2026-09-11.