From 1372004a5441c61527c633f49e1fcf44b6da3ebe Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 21:44:52 +0000 Subject: [PATCH] Testnet go checklist: the staging 47b9b229 on the 0.3.24 object commit, its gates and canary; the seeds carry the 0.3.22 interim object Co-Authored-By: Claude Fable 5.1 --- docs/plans/testnet-go.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/plans/testnet-go.md b/docs/plans/testnet-go.md index 8d5105284..73e072ba7 100644 --- a/docs/plans/testnet-go.md +++ b/docs/plans/testnet-go.md @@ -56,11 +56,16 @@ lane as `tn-on-0324` 28d3dcab on c8f9b383 (clean), to land as 0.3.24's second co | From genesis | difficulty v2 and v3, proving v0, finality v3, the DAA-second rule, the leave item (delay 3,600), the signing bonus 0 at 1,000 bps (no burn), the per-block subsidy, class v3 and v4 under the Devnet 3 shape's one-day signal window (byte 7 stamped from genesis), the ladder at rung 0 (window 86,400; 27/35/53 admissible, 88/173/267 not), the era VDF (scheme 0, the reference T), proving v1 with the fresh rule (the Devnet 3 shape), fees v1, consensus proof verification under the manifest's ids (shard `0x2b1a81cb...`, aggregator `0x474678f3...`), `sig_scheme` 0 with its switch, the W5 succession, the cache rung (512 MiB inadmissible) behind its switch | | Held at never | the fork gate (window 600), the peer directory, the pool split, the class v5 floor (0 by the post-crossing re-cut of row 9n if Devnet 3's v5 crossing reads clean), exec restart | | Pairing | igneum-pow at the class v5 freeze commit 1c420786 | -| Where | fork `testnet-genesis-3-node` 34892a36 (both node mirrors), staging `tn-on-0324` 28d3dcab (build-1), repository `testnet-genesis-2` (both repo mirrors) | +| Where | fork `testnet-genesis-3-node` 34892a36 (both node mirrors); the node lane's staging `tn-on-0324` 47b9b229 on the 0.3.24 object commit 774f16c9 (both box mirrors; artefact `/srv/artefacts/0324-tn-47b9b229/node-lane`, igneumd `6bc18ac2...`), to merge onto `release-0.3.24-node` once the shipper opens it; repository `testnet-genesis-2` (both repo mirrors) | Suites on 34892a36 (bounded, build-2 and build-1): consensus-core 168, exec 47, p2p-flows 38, pow 19, kaspad 2; consensus 134 one test at a time with the pre-existing m20 red (9f); the parallel lib run aborts in the test-order race class the node lane owns, noted, not chased -tonight. The digest lineage: `b7d8c915...` (1c19441d) to `87d103b6...` (the 0.3.22 interim re-arm) to `b2e856ed...` (this). The runbook's +tonight. On the staging 47b9b229 (the node lane, 22:35 to 22:43 UK, against the freeze pairing): consensus 134, core 175, exec 47, miner 28, +p2p-flows 38, pow 19, the build rc 0; the testnet canary on build-1: digest `b2e856ed...` on igneum-testnet-1, the genesis as cut, 18 decimals +in the fee floors, object version 7 stamped, the override file refused (rc 1), two empty nodes handshaking on `b2e856ed...`, a Devnet 3 +node reading its own digest beside it. During the handshake step seed 2 (5.161.232.205) dialled the canary and was refused on the digest +(remote: the 0.3.22 testnet object `87d103b6...`), so the seeds today carry the 0.3.22 interim re-arm, not 1c19441d; the runbook's wipe +stands either way. The digest lineage: `b7d8c915...` (1c19441d) to `87d103b6...` (the 0.3.22 interim re-arm) to `b2e856ed...` (this). The runbook's values: `--genesis 01294fd3...`, `--digest b2e856ed...`, the seed-class binaries of the cut's commit (the build-server lane's build from the named commit, the sha asserted), no override, `--wipe-genesis`. 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,