diff --git a/docs/plans/testnet-go.md b/docs/plans/testnet-go.md
index 4ae5e766d..4d1ad5b9c 100644
--- a/docs/plans/testnet-go.md
+++ b/docs/plans/testnet-go.md
@@ -39,12 +39,12 @@ genesis), not a fault. The check: `cd infra/seed-nodes && NET=testnet ./health.s
 
 By the coordinator's ruling of the evening of 7 October 2026, igneum-testnet-1 goes on the 0.3.23 testnet object (the Devnet 3 shape:
 byte 7 from genesis, every Devnet 3 activation at 0, the era VDF at 0, class v5 at 0 if its Devnet 3 crossing reads clean, the heights,
-the bonus's switch field), cut and re-armed on the seeds by the build-server lane, which owns them; the interim re-arm is the
+the bonus's switch field) AT 18 DECIMALS (the project lead's word, 21:35 BST: the decimals lane's code merged, the schedule at 18, the 16-byte
+genesis payload on the final message, the scale factor tested known-failed first), cut and re-armed on the seeds by the build-server lane, which owns them; the interim re-arm is the
 release-0.3.22-node object (34a2dbaa, digest `87d103b6...`, genesis `52a3e6a9...`). Two orders ride with it: the testnet genesis carries
 the FINAL message (the 5 October payload that `87617621...` carried, never the 4 October "proposed, not final" text that `52a3e6a9...`
-hashes: a public node never starts on a proposal; the digest moves and the re-arm absorbs it), and the base unit, 8 or 18, is the project lead's word
-(asked 21:40 BST, 7 October 2026), with the object cut both ways in a scratch read so his answer is a one-line switch, and nothing on a
-seed before it. This section's object table is rewritten against that object once the node lane names the cut; the gate rows 9g, 9h and
+hashes: a public node never starts on a proposal; the digest moves and the re-arm absorbs it), and the base unit is 18 by the project lead's word of 21:35 BST (the
+8-decimal scratch form is no longer needed); nothing on a seed before the node lane names the cut and the build-server lane's dry run reads clean. This section's object table is rewritten against that object once the node lane names the cut; 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, void as a go object by the ruling and kept as the record of what was built and gated.
 
@@ -132,7 +132,7 @@ Mac: 27 passed (the crate is not in the PC build inputs). The packager's self-te
 | 9f | A pre-existing red, not the object's: `processes::pruning_proof::igneum_m20_tests::witnesses_are_checked_in_epoch_order_under_their_own_seeds` fails under `--features igneum-pow` on the untouched `release-0.3.18-node` e69e8a39 (08:52 UK, box load under 10) and on the decimals base eec34ac3 (that lane's record); no lane's suite compiles the feature-gated test. Owner: the m20 tests' lane | the consensus engineer | OPEN, recorded |
 | 9c | Mission item 8: the genesis forward-compatibility fields (the sig_scheme byte, the W5 key-succession item, the cache rung on the ladder behind its own switch), lane `genesis-forward` (daa61847 to f95178a1 and ff06c05c on the fork; its gates: consensus-core 124, consensus 114 twice on build-2, the fast-time harness's known-failed FAIL and pass PASS on build-1). The testnet object RE-ARMS ON EACH CUT (the ruling of 19:2x UK): whatever the 0.3.23 object compiles for these four is what the seeds take | lane `genesis-forward`, the build-server lane re-arms | re-arms on each cut (this lane's re-cut had the four at 0, digest `63faee44...`) |
 | 9k | The genesis message: the go object's genesis carries the FINAL 5 October message, never the 4 October proposal's text (the coordinator's order, 19:2x UK, to the node lane through the build-server lane); the hash and the digest follow it | the node lane, the build-server lane re-arms | ORDERED 19:2x UK, not yet read back |
-| 9l | The base unit on the testnet, 8 or 18: the project lead's word, asked 21:40 BST 7 October 2026; the object is cut both ways in a scratch read (this lane's 18-decimal form is the record of the 18 side: the 16-byte genesis payload, the rescaled schedule, the two-node GPU gate 9j); nothing on a seed before the word | the project lead | OPEN |
+| 9l | The base unit on the testnet: 18 decimals, the project lead's word at 21:35 BST 7 October 2026 (through main). The go object is re-cut on the 0.3.23 line (7c7489ac's node pin 2720d8d2, or the 0.3.24 line if the v5 object lands first; the shipper names which) at 18: the decimals lane's code merged, the EmissionSchedule and every per-tier row at 18, the UTXO/EVM scale factor fixed and tested known-failed first on an 8-decimal fixture, the FINAL 5 October genesis message, the cache-rung field at 0, class v5 at 0 if its Devnet 3 crossing reads clean, chain id 4462. This lane's 7 October re-cut (fork testnet-genesis-2-node 59d05bf2) is that work on the 0.3.18 line and was handed to the node lane for the cherry-pick; its gates (9g, 9h, 9j) are the 18-decimal record until the re-runs on the go object | the project lead (decided), the node lane re-cuts, the build-server lane re-arms | DECIDED 21:35 BST: 18 |
 | 9m | GitHub: the igneum-labs (igneum-labs) account is suspended since 18:02 BST 7 October 2026 (pushes 403, "Your account is suspended"); the project lead's ticket is open; every lane lands on the box mirror (`build`) with the box gate as the verdict until it lifts; this file's branch is on the mirror and the Mac, GitHub at 1f4793c1 | the project lead | OPEN |
 | 9d | Windows: `igneum-prove-host` beside every Windows node (verification from genesis); PC 1's node refuses to start without it | the release engineer (the 0.4.0 package) | NOT DONE: to check in the 0.4.0 Windows installer |
 | 9j | The two-node 18-decimal gate on the FINAL binaries (fork e6dd3afd, igneumd 58f96049..., igneum-miner 5625caee...; `tools/fleet/base-unit-gate.sh` 72b02b48, the GPU form on a RunPod RTX A5000 rented and run by the fleet lane): PASS at 15:19 UK, 7 October 2026: 322 chain blocks in 600 s, both nodes on one sink and one exec tip (0x142), the 30 inspected payloads all the 18-decimal schedule, 491 segment rewards against the schedule at each blue block's own DAA with 0 wrong, eth_getBalance 3,929.11134259 IGN (3,929,111,342,592,592,592,602 wei) equal on both nodes and to the sum of the rewards; both node heads print `Base unit: 10^18`, the digest `4fbb2152...` and `igneumd/2.1.0-e6dd3afd`, node B's exec line the genesis `01294fd3...`. The known-failed form (the 8-decimal schedule, 420 s) FAILED as it must at 15:27 UK: payloads wrong 30 of 30, rewards wrong 305 of 305. The logs: ~/igneum-fleet/tn-gate/out/ on the Mac | the fleet lane ran it, this lane reads it | PASS (the cut's closing gate) ON THE 7 OCTOBER RE-CUT; RE-RUNS ON THE GO OBJECT (the ruling of 19:2x UK) |
diff --git a/docs/testnet/README.md b/docs/testnet/README.md
index f1c19b452..57aee9669 100644
--- a/docs/testnet/README.md
+++ b/docs/testnet/README.md
@@ -1,4 +1,4 @@
-# Igneum public testnet: identity, parameters and reset policy (ADOPTED 5 October 2026; genesis RE-CUT 7 October 2026)
+# Igneum public testnet: identity, parameters and reset policy (ADOPTED 5 October 2026; genesis RE-CUT 7 October 2026; the GO object re-cut on the 0.3.23 line at 18 decimals by the project lead's word of 21:35 BST)
 
 Every value in this file was proposed on the night of 4 October 2026 and ADOPTED by the owner on 5 October 2026,
 as proposed (sign-off recorded in `docs/plans/release-0.3.6.md`). The genesis below is the one the proposal
@@ -65,7 +65,7 @@ read methods plus `eth_sendRawTransaction`; `infra/seed-nodes/rpc/`).
 | Consensus proof verification | from genesis (`proving_consensus_verify_daa` 0) under the shard program id `0x2b1a81cb...ef7a` and the aggregator id `0x474678f3...3896` of `proving/igneum-prove/elf/manifest.json` (pinned 2026-10-05T16:20:38Z); a node whose embedded keys differ refuses to start; a Windows node verifies through the installed `igneum-prove-host` and refuses to start without it | off | the project lead, 6 October 2026, question 3 |
 | Program class | v4 from genesis, unconditional (`program_class_v4_activation_daa` 0, signal window 0) | v4 by miner signal | fresh chain |
 | The latency ladder | active from genesis at rung 0 (`latency_ladder_activation_daa` 0, window 86,400 DAA, seven windows at 90 percent to step): rungs 27, 35, 53 passes admissible; 88 inadmissible (quiet-core re-measure 7 October 2026, 08:46 UK: 10.85 ms cold with the SMT sibling loaded, over the 10 ms gate); 173 and 267 inadmissible | never | the project lead, 7 October 2026, row 3 |
-| Base unit | 18 decimals (`base_unit_decimals` 18): one IGN is 10^18 base units, the EVM's wei, the bridge is the identity | 8 (sompi) | the project lead, 6 October 2026, question 5; `docs/design/base-unit.md` |
+| Base unit | 18 decimals (`base_unit_decimals` 18): one IGN is 10^18 base units, the EVM's wei, the bridge is the identity | 8 (sompi) | the project lead, 6 October 2026, question 5, CONFIRMED 7 October 2026, 21:35 BST for the go object on the 0.3.23 line; `docs/design/base-unit.md` |
 | Per-block subsidy on the EVM side | from genesis (`subsidy_per_block_activation_daa` 0): each merged block credited the subsidy of its own DAA, as the UTXO coinbase pays it | at an upgrade height with 0.3.19 | the project lead, 7 October 2026, 09:5x UK |
 | Genesis forward-compatibility (mission item 8) | from genesis: `sig_scheme` 0 (BLS12-381) with `sig_scheme_activation_daa` 0 (every vote item and key reveal carries the scheme byte; any other scheme refused until a program class the 95 percent signal moves to names it), `finality_succession_activation_daa` 0 (W5: a vote key hands its window weight and forfeit term to a successor once), the ladder's cache rung 512 MiB inadmissible until measured, behind its own switch (`latency_ladder_cache_rung_activation_daa` 0) | never | the project lead, 7 October 2026, 10:1x UK; `docs/design/genesis-forward.md` |
 | Proving v0 payouts | from genesis | from the override file | fresh chain |