AIP-22 conformance corpus complete: the ninth kind (classical-only fork, from rehearsal network 28099), all nine kinds judged conformingly by both clients; the options and files each harness judged with, per chain (config-28001/, config-28099/)

This commit is contained in:
Aere Network committed 2026-09-27 05:57:01 +03:00
1 parent dccd277337
commit 6d907fa2e9
21 files changed
+1147 -6

No files matched your search

+10 -2
View File
@@ -2,6 +2,8 @@
The corpus that section 9 of [AIP-22](../AIP-22.md) asks for: header and registry cases on which every client of chain 2800 must reach the same verdict, each case with the verdict the two existing clients reached on it. Published 2026-09-27. `VECTORS.json` is generated from the working corpus in one place; do not edit it by hand.
`config-<chain>/` holds, for each chain the header vectors come from, what the two harnesses judged with: the Besu-derived client's options (`besu/`, as Java system properties) and the Nethermind-derived client's variables (`nethermind/`), with the registries, manifests, v3 epochs and genesis they name. A vector's own `chainId` says which configuration applies. For chain 28001 the two v3 registry epochs the options name (`registry-v3-3080010.json`, `registry-v3-3097600.json`) are the published ones, served beside the testnet's key manifests (`pq/manifests/`), and pinned by the hashes in the options.
## What a vector is
| field | meaning |
@@ -30,6 +32,12 @@ Each client's own rule classes were run on the vectors, in each client's test bu
A third client conforms on a vector when it admits a valid one, and refuses an invalid one for the reason in `reasonTag`.
## Not yet in the corpus (2026-09-27)
## The classical-only fork (chain 28099)
Section 9 names nine kinds; eight are here. The ninth, a classical-only fork of 31 blocks, is not yet a static vector. Its behaviour was measured on a live rehearsal network, with a Besu-derived reader on 2026-09-23 and with readers of both clients on 2026-09-24 (recorded in AIP-22's stage record of 2026-09-27): a reader fed the fork follows it until the height of the next anchor, which the fork cannot certify, and moves to the anchored chain when it reaches it; with the anchor rule disarmed, the same reader stays on the fork. A static form needs the fork's blocks, which only a rehearsal network's keys can make, and a configuration other than chain 28001's.
Section 4 rule 4: a reader fed a classical-only fork of up to 31 blocks moves to the anchored chain within one interval. The fork's blocks can only be made with a validator's ECDSA key, so these vectors come from the rehearsal network 28099 (one validator; the attack of 2026-09-24): an attacker holding the validator's ECDSA key and no post-quantum key, started from the validator's database at block 2,691, wrote blocks 2,692 to 2,719 and, with the anchor rule disarmed on it and on the reader, also the anchor height 2,720. Each vector names the fork point and lists the fork's blocks (`forkPoint`, `forkTail`).
- `28099-fork-honest-anchor-2720` (valid): the honest anchor at 2,720, certified by the validator's Falcon-512 seal over `M(parent)`.
- `28099-fork-anchor-2720-no-certificate` (invalid): the fork's own block at 2,720, as the attacker wrote it; refused because an anchor height carries no certificate.
- `28099-fork-anchor-2720-honest-certificate` (invalid): the same block carrying the honest anchor's certificate (digest re-bound); refused because a certificate signs `M(parent)` and does not verify over the fork's parent.
The move from the fork to the anchored chain is behaviour, not a single header: it was measured on the live rehearsal network in both clients, with a negative control (AIP-22 stage record of 2026-09-27). A header of the fork between anchors is not a vector here, because the anchor rule does not judge it.