igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Testnet go checklist: the dry run on 5b673577 done (10:23 UK, rc 0 on the three seeds, the read-back lines); the genesis read-back must come from getBlockDagInfo, not the journal

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-08 09:27:48 +00:00
parent 291170a2ef
commit 15371eba34
1 changed files with 7 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/plans/testnet-go.md
View file

@ -73,7 +73,13 @@ values: `--genesis 01294fd3...`, `--digest b2e856ed...` (or row 9n's digest afte
build-server lane built from 5b673577 at 09:43 UK on build-1: `/srv/artefacts/0324-5b673577/seed/igneumd` sha256
`3a204fd9d3a4840dcef430e73cbfa986881db915d5459533d395dc0563a597a8` (glibc 2.34, the commit string twice, igneum-pow 1c420786) and
`igneum-miner` sha256 `464dca078db54434b2ce4cdf8b5975a614141d20907a9d941cc88667b85144ba`, `--commit 5b673577`, no override, `--wipe-genesis`;
the read-back includes `Base unit: 10^18`; the dry run on the three seeds at 10:20 UK (after Devnet 3's move minute), its read-back owed by 10:30 UK. The gate rows 9g, 9h and 9j re-run on it; row 9c reads "re-arms on each
the read-back includes `Base unit: 10^18`. DRY RUN DONE 10:23 UK, 8 October 2026: rc 0 on seed1, seed2 and seed3 ("DRY RUN, nothing
touched; the box answers as seedN, active a9ea25f8ada2", the 5 October binary still running), the pair's shas asserted; the same binary
started bare on build-1 with `--testnet` prints `igneumd/2.1.0-5b673577`, the digest `b2e856ed...`, `Base unit: 10^18`, fees v1 from DAA 0,
proving v0 from DAA 0, the follower at genesis (height 0). One hazard the read exposed: the `[igneum-exec] genesis <hash> executed` line is
not a start line in this build (it was in the 5 October one), so the seeds mode's `--genesis` read-back must take the hash from
`getBlockDagInfo` after the start (at height 0 the pruning point and the sink ARE the genesis, `01294fd3...`), not from the journal, or it
reads "not seen in 60 s" and the go run reports a false MISMATCH; the build-server lane adds that read before `--go`. Nothing mines. The gate rows 9g, 9h and 9j re-run on it; row 9c reads "re-arms on each
cut". Everything below this paragraph in this section is the 7 October RE-CUT of this lane on the 0.3.18 line, the source of the carry,
kept as the record of what was built and gated.