From 0f1fc5034947d8b132ad35f520e2f024eb2615c1 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Mon, 5 Oct 2026 23:13:17 +0000 Subject: [PATCH] Counter ASIC 2.0: C39, the two-manifest order in the rollout plan; status 23:13 --- docs/plans/counter-asic-2-rollout.md | 2 ++ docs/plans/counter-asic-2-status.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/docs/plans/counter-asic-2-rollout.md b/docs/plans/counter-asic-2-rollout.md index adcc24332..ccb6fc049 100644 --- a/docs/plans/counter-asic-2-rollout.md +++ b/docs/plans/counter-asic-2-rollout.md @@ -30,6 +30,8 @@ The same nine-field object goes verbatim into the override files of Mac node 1, ## 4. The order +TWO MANIFESTS, never one (C39, confirmed to the shipper 23:12 UTC): the engine writes a manifest's consensus.override at the take and restarts the node with it at the next safe window whatever binary is installed, and a 0.3.10 node refuses a file carrying program_class_v3 or the proving v1 fields (deny_unknown_fields) and dies; so the first 0.3.11 manifest carries the live four-field object UNCHANGED, the update rolls machine by machine, the hand nodes and the seed take the 0.3.11 binaries with the four-field file (the rolling-upgrade digest c562d70e... everywhere), and only when every reporting app and node is on 0.3.11 does the second manifest carry the nine-field object (N4 = N5 re-pinned to tip + 14,400 rounded up to 3,600 at that moment if the 10,800 floor has passed), the hand nodes' and the seed's files switched, the digest sweep to the activation digest. The DMG's packaged nine-field line is fine for a fresh install. + 1. The digest flip: a node build that carries `program_class_v3_activation_daa` at never on every node (hand nodes and the seed first: `infra/devnet/restart-hand-nodes.sh ''`, then the app version through the manifest; every node prints the same `Consensus params digest`). 2. Fix N4, cut the app version (`packaging/mac/packaged-config.sh`, the three version files), commit as igneum-labs. 3. The Windows payload inputs (`packaging/windows/push-inputs.sh`) and the Mac DMG (`packaging/mac/build-dmg.sh`), the manifest (`publish-manifest.sh --activation-height N4 --deadline-note "program class v3" --override '' --deploy`), `fetch-ci-artifacts.sh --deploy`. diff --git a/docs/plans/counter-asic-2-status.md b/docs/plans/counter-asic-2-status.md index 1396e077d..74d204b56 100644 --- a/docs/plans/counter-asic-2-status.md +++ b/docs/plans/counter-asic-2-status.md @@ -645,3 +645,5 @@ The shipper found it from the intake: PC 2 has two new engine runs (win-1ccfe586 23:10. C32's premise withdrawn (the reviewer, from the code and the relay finding): an app update does not clear the jobs folder (the "AMD kit gone" read was PC 2, where it was never fetched); what stands is that an app restart aborts every running job, so the update-now is sequenced after the jobs that must not die, and the kit presence check is hygiene; rollout plan 4a reworded; the bench-log line 39f02ff on the stopped AMD agent's branch is corrected by this note (its owner is stopped). 23:11. For the morning: N4 = N5 = 154,800 (epoch 43) lands at about 03:30 UTC on 6 October (DAA 139,1xx at 23:1x at 1.002 DAA/s): class v3 and proving v1 switch on while everyone sleeps, the Mac, the laptop and PC 2 cross it on 0.3.11; PC 1 (down, 0.3.10, no class v3 field in its digest) shows "0 peers" at its relaunch until it takes 0.3.11, the digest rule working as written; 7c's first line says relaunch, update, reconnect. + +23:13. C39, confirmed to the shipper as the order: two manifests, never one. The first 0.3.11 manifest carries the live four-field override unchanged (a 0.3.10 node dies on a file with the new fields: deny_unknown_fields, and the engine restarts the node with a taken manifest's override whatever binary is installed); the nine-field object goes in a second manifest only when every reporting app and node is on 0.3.11 (N4 = N5 re-pinned then if the 10,800 floor has passed); the hand nodes and the seed switch files at that step; the digest sweep to 0139ab9d... after it. Rollout plan section 4.