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

Node lane, plan 6.11: the proof window opened 17:57:05Z, the verify-Off-never-carries runbook fact, the announcers

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 17:59:08 +00:00
parent da14538230
commit 7eacc3bd6f
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/plans/counter-asic-3-node.md
View file

@ -248,6 +248,8 @@ Pin ruling (shipper, 17:5xZ): 34a2dbaa is HELD for the crossings; the pin is the
the project lead's word on the signing bonus (17:5xZ, main's plan): do it. (1) 0.3.23 carries the bonus with c7ea1e21 silent_split so the UTXO and the EVM agree (silent 72/28, signed 80/20, fees untouched, the coinbase total unchanged), the test known-failed first on the EVM/UTXO disagreement. The 0.3.23 node line opened at 18:0xZ: release-0.3.23-node = 34a2dbaa + fd7de1b4 (8582a571, the sink tally off the request path) + 420f9305 (201b3613, vote-or-burn removed; three conflicts resolved: the OverrideParams keys stay as ignored input, the emission argument kept in CoinbaseManager::new, the digest edit list at 24) + c7ea1e21 (43360992, silent_split; the executor test's block carries both `silent` and `split`). Its suites run on build-2. Note from c7ea1e21: the shard guest's port of the executor must carry the same two inputs and the same split, so the segment statement changes and the shard program id re-pins (the testnet lane owns that on its cut) before the bonus height. (2) Before any height: the app signs by default and shows the signing state on the Overview card row (the UI lane); the hash-origin report carries the silent share per day (the fleet); one week of Devnet 3 reads that share and any silence from a bug (missing key, clock, template) is fixed first. (3) On Devnet 3 by height after that week; at 0 in the testnet and mainnet objects.
Mandatory proof verification, the 24-hour window: OPENED 17:57:05Z (dn3-x1's first paid segment 1256..1263, 0.7036 IGN, carrier block 1403, key 0x5413853a…; dn3-g1 paidShards 10 at 17:57Z). Runbook fact found on the way (the fleet, 17:52Z): a node started bare (no `IGNEUM_PROOF_VERIFIER`) logs "proof verifier: Off" and, by design (`VerifyMode::Off`: records relayed, stored and checked natively, never offered to this node's templates; the template section carries `verified == Some(true)` only), its blocks carry NO proof records, whatever finality or the window says; 72 records waited twelve minutes on Devnet 3 while every builder was bare. Every Devnet 3 block builder runs with `IGNEUM_PROOF_VERIFIER=<igneum-prove-host>` whose `--mode id` prints the node's embedded ids (shard 0x2b1a81cb…, aggregator 0x474678f3…; the 0.3.17 floor's host pairs), read back as "proof verifier: Command(…)"; `IGNEUM_PROOF_VERIFY=trust` carries unchecked and is not for the window. Peer directory announcers: dn3-g1 (64.119.209.250:21703) and dn3-g2 (154.64.230.67:27017) mine with --announce since 17:49:03Z and 17:50:32Z (pack gate PASS, id fce15bf61030be57); the window for their keys' weight runs from their first announced block after the verifier restart.
| Switch | State | Owner | Gate (last green, commit; in 69d1b56e?) | Earliest Devnet 3 height |
|---|---|---|---|---|
| fork_gate_activation_daa (window 600) | built and gated | horizon lane | infra/fast-time/fork-gate-gate.mjs 6 of 6, 12:58Z 7 Oct on build-2 (6eb21fc9 = 437f0438 rebased); finality module 24 of 24 with five fork-gate tests; 437f0438 is in 96161037, so in 69d1b56e | genesis lock DAA + 7,200 (one weight window; inert before), once every node runs 0.3.21+ (the field enters the digest), after a mixed-version ten-minute run and a mid-window restart |