From 971754aad9459999793e7983ac86cbf316cc93b4 Mon Sep 17 00:00:00 2001 From: Aere Network Date: Wed, 2 Sep 2026 22:54:57 +0300 Subject: [PATCH] SPEC 8: D9, Osaka header fields under QBFT (block 0 only), found 2026-09-02 --- SPEC.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/SPEC.md b/SPEC.md index 7516f3a..b1a57a7 100644 --- a/SPEC.md +++ b/SPEC.md @@ -1030,6 +1030,16 @@ third-party client implementing COMMIT enforcement MUST verify over the anchor f `height + 1 >= aere.pq.anchorBlock` (source: `testnet-public/D-311-DOVADA-2026-09-02.md`, `deploy/validators/d311-2026-09-02/SURSA.md`). +**D9. Osaka header fields under QBFT (found 2026-09-02, D-322).** On an AERE QBFT chain with the Osaka +fork active from genesis (the public testnet 28001: `osakaTime=0`, `futureEipsTime=0`), Besu writes the +EIP-7928 block access list hash (`balHash`) and the EIP-7843 `slotNumber` ONLY in block 0; every later block +omits both fields (measured on blocks 1 and 47744 through `eth_getBlockByNumber`). A second client that +requires them on every header, or that stamps a computed access list hash onto the processed header, +diverges at block 1. The Nethermind client accepts the chain's form after genesis and keeps validating the +fields wherever a header carries them (source: `nethermind-pqc/nethermind-intree/patches/osaka-antet-besu.sh` +in the operator repository; gate `scripts/deschise/antetul-osaka-e-al-lantului.sh`). Chain 2800 has not +reached Osaka; this divergence will apply to it on the same terms when it does. + ## 9. What this specification cannot state from the published sources Honest list, for completion in a later revision. An implementer hitting one of these should treat