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

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

Browse Source
This commit is contained in:
Aere Network 2026-08-19 15:50:43 +03:00
parent ac7c0adaa5
commit 05192bcf9c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
RUN-A-NODE.md
View File

@ -132,7 +132,8 @@ enode by return. Everything else on this page works without one; discovery is th
that needs it. that needs it.
`--sync-mode=FULL` is deliberate. Chain 2800 runs QBFT with a half second block period, so the head `--sync-mode=FULL` is deliberate. Chain 2800 runs QBFT with a half second block period, so the head
is around twelve million blocks and climbing by two per second. Full sync from block 0 is the mode was about 12.2 million blocks when this was written (2026-08-03), passed 14.6 million on 2026-08-19,
and climbs by roughly two per second; read the live height with eth_blockNumber. Full sync from block 0 is the mode
that actually verifies the history we publish, which is the point of this repository. Snap sync that actually verifies the history we publish, which is the point of this repository. Snap sync
against a QBFT chain trusts a peer for the state and verifies far less. against a QBFT chain trusts a peer for the state and verifies far less.
@ -193,8 +194,8 @@ the two.
## What the two bootnodes are, and what they are not ## What the two bootnodes are, and what they are not
They are two full nodes that are **not** in the validator set. Chain 2800 seals blocks with seven They are two full nodes that are **not** in the validator set. Chain 2800 seals blocks with nine
QBFT validators, and none of the seven is listed here, on purpose. Publishing a validator's p2p QBFT validators (seven until 2026-08-09), and none of the nine is listed here, on purpose. Publishing a validator's p2p
address hands an attacker a target whose downtime costs the network consensus headroom, which is why address hands an attacker a target whose downtime costs the network consensus headroom, which is why
sentry style architectures exist. The two nodes above carry no consensus responsibility: if both are sentry style architectures exist. The two nodes above carry no consensus responsibility: if both are
taken down, new nodes cannot bootstrap until they are replaced, and block production is unaffected. taken down, new nodes cannot bootstrap until they are replaced, and block production is unaffected.