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

Counter ASIC 2.0: C40, the publish-1 order (hand nodes and the seed first); status 23:14

Browse source
This commit is contained in:
igneum-labs 2026-10-05 23:14:21 +00:00
parent 0f1fc50349
commit 02f2bc6e4b
2 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/plans/counter-asic-2-rollout.md
View file

@ -30,7 +30,7 @@ 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.
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 publish 1 goes in this order (C40: the 0.3.11 binary itself flips the digest from the fleet's 1f4b4425 to c562d70e because the class v3 field enters it at never, so the apps must not take 0.3.11 before the hand nodes): FIRST the hand nodes and the seed on the 0.3.11 binaries with the four-field file, each printing c562d70e..., THEN the first 0.3.11 manifest with the live four-field object UNCHANGED and update-now to the apps machine by machine, every app's node joining at c562d70e; 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 '<object without the new field>'`, 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.

2
docs/plans/counter-asic-2-status.md
View file

@ -647,3 +647,5 @@ The shipper found it from the intake: PC 2 has two new engine runs (win-1ccfe586
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.
23:14. C40, confirmed to the shipper as the rule and written into section 4: publish 1 moves the hand nodes and the seed to the 0.3.11 binaries with the four-field file FIRST (each printing c562d70e), then the manifest and the apps; otherwise the apps on c562d70e and the hand nodes on 1f4b4425 would partition for the window between the publishes. Publish 2 flips everything to 0139ab9d in one sweep.