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

reproducible-builds scope note corrected: the recipe's image cannot follow chain 2800, because the base-fee floor and the anchor rules are client patches, not config (D-378)

Browse Source
This commit is contained in:
Aere Network 2026-09-11 22:17:56 +03:00
parent 3ae88212d7
commit 9f4e3cb1ab
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
AERE-REPRODUCIBLE-BUILDS.md
View File

@ -97,8 +97,18 @@ digests. This is the single most important gap in the "what exists" column.]
**Scope note.** This Dockerfile builds stock upstream Hyperledger Besu at `v25.5.0` plus the AERE
genesis and config. QBFT consensus and the 0.5 second block period are configured through
`config/genesis.json` and `config/config.toml`, not through a client source patch, so the mainnet
consensus binary in this image is upstream Besu with AERE configuration. The post-quantum precompile
`config/genesis.json` and `config/config.toml`.
**Corrected 2026-09-11.** This paragraph used to continue "not through a client source patch, so the
mainnet consensus binary in this image is upstream Besu with AERE configuration". That is false, and
our own measurement said so from 2026-08-07: the base-fee floor has been a client patch since block
10,141,734, and a binary without it rejects every block with a state-root mismatch; the post-quantum
anchor rules are client patches as well. **An image built from this recipe cannot follow chain 2800
past those heights.** It is a reproducibility demonstration of an upstream build, not a mainnet node.
The mainnet node is built from the published patches by `run-node.sh` in the aere-node package. The
same day it was also measured that `config/genesis.json` and `config/config.toml` did not exist in the
tree at all, so this recipe could not even complete its COPY step; both files were written from the
fleet genesis and from CLI-only options respectively. The post-quantum precompile
work (Falcon, ML-DSA, SLH-DSA, ML-KEM, HashToPoint at `0x0AE1..0x0AE7`) is a **separate** build path
with its own pinned base commit; see section 2.5. [VERIFY: confirm whether the live N=7 validator
image is this stock-Besu-25.5.0 build or the PQC-precompile fork build, and if the latter, whether