README facts as of 2026-08-19: consensus (classical ECDSA per block + post-quantum anchor checkpoint, >=3 of 9 since 2026-08-14), nine validators, EVM parity stated precisely, public source links that resolve

This commit is contained in:
Aere Network 2026-08-19 15:51:36 +03:00
parent 6d6c18ae41
commit e215e2f713

View File

@ -6,7 +6,7 @@ account-abstraction and post-quantum contract surface, the seedless hybrid PQC
wallet, and AERE's native NIST post-quantum precompiles.
**SDK version:** 0.16.12
**Last updated:** 2026-07-16
**Last updated:** 2026-08-19 (consensus and network facts; the rest is as of 2026-07-16)
**Network state at this release:** 35+ typed contract clients over a canonical
address book of 130+ live contracts on chain 2800.
@ -24,7 +24,7 @@ address book of 130+ live contracts on chain 2800.
| Block period | 0.5 s (500 ms) target, sub-second deterministic finality |
| Native token | AERE (18 decimals) |
| Max supply | 2,800,000,000 AERE (capped at genesis-v2, 2026-05-07) |
| EVM ruleset | Pectra + Fusaka, full functional parity with Ethereum mainnet |
| EVM ruleset | Pectra + Fusaka opcode and precompile set (Besu), plus five AERE post-quantum precompiles; not full parity with Ethereum mainnet (the beacon-chain system contracts, e.g. EIP-4788 beacon roots, have no code on chain 2800) |
| HTTP RPC | `https://rpc.aere.network` |
| WebSocket RPC | `wss://wss.aere.network` |
| Explorer (Blockscout) | `https://explorer.aere.network` |
@ -35,10 +35,15 @@ address book of 130+ live contracts on chain 2800.
AERE draws a hard line between consensus and the application layer, and this SDK
keeps it:
- **Consensus is classical.** Blocks are proposed and sealed under Besu QBFT with
secp256k1 ECDSA signatures. Consensus is **not** post-quantum. Any Falcon
quorum-certificate or second-client work is isolated-testnet R&D and has never
run on chain 2800.
- **Consensus is classical ECDSA on every block, with a post-quantum checkpoint
every 32 blocks.** Blocks are proposed and sealed under Besu QBFT with secp256k1
ECDSA signatures (nine Foundation validators, quorum 6 of 9, f=2). Since block
13,014,000 anchor blocks also carry, under the block hash, a certificate of
validator Falcon-512 seals, and since 2026-08-14 a node rejects an anchor block
with fewer than three valid seals (f+1 of nine, not a quorum). That is the whole
post-quantum part of consensus: not a per-block quorum (the claim published on
2026-08-15 was withdrawn on 2026-08-19). A second client (Nethermind) validates
and follows the public chain at client2.aere.network; it does not produce blocks.
- **PQC lives at the application layer.** Five NIST post-quantum verification
precompiles are live on mainnet (see below). Contracts and this SDK use them for
application-layer signatures, attestations, key registries, agent DIDs, t-of-n
@ -147,12 +152,12 @@ single flow. Three ready-made entry points:
npm run build && node examples/pqc-identity-e2e.mjs
```
- **Reference wallet dApp**`blocky-chain-forge/pqc-wallet/`. A single
- **Reference wallet dApp**`pqc-wallet/` in the (not yet published) website source tree. A single
self-contained HTML page (no external CDN, all crypto bundled inline) that walks
the same flow in the browser against the live read-only RPC. Build it with
`node pqc-wallet/build.mjs`; the output is served at `/pqc-wallet.html`.
- **Project scaffolder**`create-aere-pqc` (`aerenew/tools/create-aere-pqc`).
- **Project scaffolder**`create-aere-pqc` (in the private working tree; not yet published).
Generates a wired-up wallet or agent project:
```bash
@ -343,8 +348,8 @@ Each contract's exact status is documented inline in `src/addresses.ts`.
## Source
- SDK source: <https://git.aere.network/aere-network/sdk-js>
- Contract source: <https://git.aere.network/aere-network/aerenew>
- Website source: <https://git.aere.network/aere-network/blocky-chain-forge>
- Contract source: <https://git.aere.network/aere-network/aere-contracts> (published Solidity sources and tests; the full working tree is private)
- Website source: not published yet
## License