From efeab4b23db82f8a55682403b5544d04180c4d92 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Mon, 5 Oct 2026 20:29:37 +0000 Subject: [PATCH] Counter ASIC 2.0 rollout: ota-k2 commit on the next-cut list --- docs/plans/counter-asic-2-rollout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/plans/counter-asic-2-rollout.md b/docs/plans/counter-asic-2-rollout.md index 9393ea34c..b51f04861 100644 --- a/docs/plans/counter-asic-2-rollout.md +++ b/docs/plans/counter-asic-2-rollout.md @@ -85,7 +85,7 @@ The fee switch H = 210,000 arrives about 19:50Z on 6 October. The 0.3.10 node's the project lead delegated the proving v1 decisions to its agent (acd4f36bc2c07a4e2): fork branch proving-v1 (from a24ab01a: segment records, the pool split, five RPCs, p2p message 72, parameters proving_v1_activation_daa, segment_blocks, unproven_daa, aggregator_share_bps, in the digest only once set) and its app branch, rebased onto the 0.3.10 tips. 0.3.11 carries program_class_v3 AND proving v1 together: one override object, one digest, one publish, the same gates for each half (its fast-time harness green on the final tree, suites on PC 2); both activation heights set at publish by the same rule (tip + 14,400, checked >= 10,800). If one half is not ready when the other is, the ready half ships as 0.3.11 and the other as 0.3.12; the status file says which. -Next-cut list (not consensus, not in 0.3.11 unless a one-file app change with tests): ota-k2 (second update key with revocation), rig-install, pool-v0 (its own service, no app change), repro-bench; fork-side pack-loop 05ef0fa3 is merged into the v3 node branch because v3 touches the same miner paths. +Next-cut list (not consensus, not in 0.3.11 unless a one-file app change with tests): ota-k2 (branch ota-k2, commit c722579e, "OTA: the second signing key (K2) with revocation": manifest.rs, ota.rs, jobrun.rs, jobs.rs, inputs.rs, ota-sign.rs, engine.rs, the publish scripts, tools/keys, docs/security/keys.md section 4; ships signed with K1; K2's public half is empty until the project lead runs tools/keys/keygen-k2.sh), rig-install, pool-v0 (its own service, no app change), repro-bench; fork-side pack-loop 05ef0fa3 is merged into the v3 node branch because v3 touches the same miner paths. ## 9. After the publish: Counter ASIC 3.0