From 07988628a9c19ca8df0815071eb1e73ebafb3409 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Wed, 7 Oct 2026 13:45:55 +0000 Subject: [PATCH] Testnet go checklist: the shipper's seeds route (wave1-0320.sh seeds and lift-rpc-filter modes) and the digest lineage b7d8c915 to 9537868d to 80af8aa1 Co-Authored-By: Claude Fable 5.1 --- docs/plans/testnet-go.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/plans/testnet-go.md b/docs/plans/testnet-go.md index e480335c9..2c4865498 100644 --- a/docs/plans/testnet-go.md +++ b/docs/plans/testnet-go.md @@ -140,6 +140,20 @@ chain is at height 0 and no miner exists). | 5 | The cross-check that the old chain is gone | a 5 October binary (`igneumd 1c19441d`) pointed at a seed is refused at the handshake on the digest | one refusal line in the seed's log | | 6 | Record | the digest, the genesis hash and the three sha256 lines in this file and in `docs/testnet/README.md`; the announcement text carries the genesis hash | | +The route the shipper staged (0.3.20 cut, main's ruling (b), 14:4x UK, `docs/plans/release-0.3.20.md` 5e74fa2f): the three seeds stay +on 1c19441d (digest `b7d8c915...`) through the 0.3.20 sweep and the public RPC filter's BLOCKED_UNTIL_FIXED_NODE set stays; at the go the +build-server lane's `wave1-0320.sh` seeds mode puts the re-cut binary on the three seeds in parallel (the sha asserted, the commit string +and the digest read back) and its lift-rpc-filter mode opens the RPC; steps 2 to 4 above are what that mode does, step 2's wipe included. + +The digest lineage, so the move is read right at the go: 1c19441d `b7d8c915...` (5 October); the 0.3.20 pin c4459193 `9537868d...`, the +whole move being five additions (`finality_leave_activation_daa` 0 with `finality.leave_delay` 3,600, `program_class_v3_activation_daa` 0, +`program_class_v4_activation_daa` 0 with the signal window 0 left out, `pow_genesis_dataset_log2` 28, `EmissionSchedule::TESTNET_1`), the +genesis, base params, finality table, fee table and pow schedule unchanged; this re-cut `80af8aa1...` on top of those: `base_unit_decimals` +18 (and the genesis itself, re-laid), `difficulty_v3_activation_daa` 0, `finality_daa_rule_activation_daa` 0, the signing bonus 0 at 1,000 bps, +`latency_ladder_activation_daa` 0 with the window and the six rungs, `proving_consensus_verify_daa` 0 with the two program ids, +`subsidy_per_block_activation_daa` 0; the genesis-forward fields move it once more. No override pins any old value, so every testnet node +swaps together or not at all; the digest is re-read on the re-cut's own binary at the go. + What the project lead's go needs from him, in order: (a) the word that mission item 8 is in the object (or that the cut goes without it, which means a reset later); (b) "cut the seeds over" (this runbook, about 20 minutes for the three); (c) the 0.4.0 cut from the merged branches (step 3 of the go table); (d) the first miner. Until (b) the seeds keep the 5 October chain and refuse every re-cut node, which is harmless: nothing mines on either. ## Cost