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

docs: 7.6 the bridge-identity rows (known-failed on the old binary, N7 PASS on the fixed one, the pairing fault)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-07 08:43:16 +00:00
parent 446f2d38e1
commit c8624c68f0
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -264,7 +264,15 @@ Harness `infra/fast-time/vote-or-burn.mjs`: node A's miner votes, node B's runs
| `--rule bonus --expect bonus --replay --secs 660` (a span past two 120-DAA weight windows), 812c3ac2 | 00:31 to 00:42Z | PASS: C synced the 697-block span from genesis in 5 s (697 against 697, one sink fc4d942d), 0 rule error lines; the payout unchanged (ratio 0.9000, the pool 0.3500, 58 and 61 pairs over DAA 566 to 686) | `vote-or-burn-rule-bonus-expect-bonus-replay-long.json` |
| `--rule bonus --expect bonus --replay --secs 14700 --finality devnet` (the devnet's own finality object: weight window 7,200 DAA, presence 20, interval 30, depth 20; a span past two devnet windows), 812c3ac2 binaries | 01:00 to 05:19Z | the rule checks PASS: 65 pairs paying A and 55 paying B over DAA 14,419 to 14,538, producer ratio 0.9000 (want 0.9), B's pool 0.3500 of A's producer (want 0.35), 0 rule error lines on C; the harness's own sync check read FAIL and was wrong: A pruned at the moment C joined (the chain had passed the 13,838 pruning depth; "pruning points in history: 13" at 04:49:28Z), so A's count at C's start (the whole chain) is not reachable by a C that prunes too; by the logs C took A's 13,843 blocks and A's sink in 20 s (IBD done 04:49:25Z, C started 04:49:05Z). Clause corrected in the harness (C against A's current count) | `vote-or-burn-rule-bonus-expect-bonus-replay-devnet-window.json` (the json carries the harness's FAIL; the reading above is the gate's) |
**Closed by the project lead's word (7 October 2026, morning): the signing bonus at the testnet genesis (signing_bonus_activation_daa 0, signing_bonus_bps 1,000, the unsigned tenth to the pool) and NO burn.** Vote-or-burn is removed from the 0.3.19 line in 420f9305 on ca3-v4-0318 (the two Params fields, their digest arm, the four network constants, the coinbase manager's burn arm, both tests; `with_signing_bonus` replaces `with_silence_rules`; the shared silence reading `silent_builder` is unchanged; the override's two keys are accepted and ignored so a 0.3.16 to 0.3.18 file parses; no network's digest moves). The harness refuses its burn rule from the same day (92c6f0f5); the rows above stand as the record of the weigh-up and the replay gate. Ledger N7 (the testnet lane, 7 October 2026, 09:0x UK): the execution layer never read a block's silence, so with the bonus on the EVM ledger credited a silent block 80/20 against the coinbase's 72/28; fixed in c7ea1e21 (igneum::silent_split, the one arithmetic both ledgers apply; SegmentBlock::silent from consensus's silent_builder; the bonus bps on ChainBlockEnv), no guest change; the harness's bonus case checks the bridge identity per pair row (e726a0fe), the known-failed run on the old binary and the passing run on the fixed one recorded below once they land. The testnet lane compiles the switches into TESTNET_PARAMS on testnet-genesis-2-node (the testnet refuses an override file): signing bonus 0 and 1,000; finality_leave_activation_daa 0 with finality.leave_delay 3,600; finality_v3_activation_daa 0; finality_daa_rule_activation_daa 0; difficulty_v3_activation_daa 0; latency_ladder_activation_daa 0 with latency_ladder_window_daa 86,400 and the six rungs (27, 35, 53 admissible; 88, 173 and 267 not); proving_consensus_verify_daa 0 with the manifest's program ids. Rung 3 re-measured on the project lead's word (08:46 UK, igneum-build-1 under the measure hold, both build slots held, load 6.1, core 40 at 3.66 GHz, the ladder worktree's igneum-pow 59ae70cf): reps 88 cold alone 9.04 ms, cold with the SMT sibling loaded 10.85 ms (averages of 50: 5.95 and 10.11), over the 10 ms gate by 0.85, so it stays inadmissible; the control rung 2 (reps 53) read 9.25 cold loaded, admissible as before. Raw lines in `counter-asic-3-gate/ladder-bench/20261007T074547Z`.
**Closed by the project lead's word (7 October 2026, morning): the signing bonus at the testnet genesis (signing_bonus_activation_daa 0, signing_bonus_bps 1,000, the unsigned tenth to the pool) and NO burn.** Vote-or-burn is removed from the 0.3.19 line in 420f9305 on ca3-v4-0318 (the two Params fields, their digest arm, the four network constants, the coinbase manager's burn arm, both tests; `with_signing_bonus` replaces `with_silence_rules`; the shared silence reading `silent_builder` is unchanged; the override's two keys are accepted and ignored so a 0.3.16 to 0.3.18 file parses; no network's digest moves). The harness refuses its burn rule from the same day (92c6f0f5); the rows above stand as the record of the weigh-up and the replay gate. Ledger N7 (the testnet lane, 7 October 2026, 09:0x UK): the execution layer never read a block's silence, so with the bonus on the EVM ledger credited a silent block 80/20 against the coinbase's 72/28; fixed in c7ea1e21 (igneum::silent_split, the one arithmetic both ledgers apply; SegmentBlock::silent from consensus's silent_builder; the bonus bps on ChainBlockEnv), no guest change; the harness's bonus case checks the bridge identity per pair row (e726a0fe), the bridge rows:
| Run (UK) | Binary | Case | bridge line | SUMMARY |
|---|---|---|---|---|
| 09:10 to 09:16 | 27d1b520 (before c7ea1e21) | `--rule bonus --expect bonus`, the first pairing by address | 0 of 63 pair rows agree exactly; the first disagreement an A row 880 sompi apart (one second of launch ramp: the chain block's own entry, the N8 reading) | FAIL on the exact identity, as it must |
| 09:18 to 09:23 | 27d1b520 | the same, the EVM bonus ratio as the failing check | EVM medians null (the mergeset-position pairing found no rows) | FAIL as it must (`evm_bonus_ratio_matches`) |
| 09:31 to 09:37 | e5e6c2bf (d840537b: N7 in, N8's switch at never) | `--rule bonus --expect bonus` | EVM credit medians A 253,736,201 B 228,375,257 sompi, ratio 0.9000 (want 0.9): a silent key's credit is the bonus share on the EVM side too; exact identity 0 of 66 rows (N8's slope, the switch off) | PASS (N7 closed) |
| 09:37 to 09:42 | e5e6c2bf | `--subsidy-per-block` (N8's switch at 0) | ratio 0.9000; exact identity 0 of 59, the entry compared was the chain block's own (the pairing took the last entry for the address; the segment lists the parent first) | FAIL on `bridge_identity_exact`, the harness's fault; re-run with the pairing corrected recorded below |
The testnet lane compiles the switches into TESTNET_PARAMS on testnet-genesis-2-node (the testnet refuses an override file): signing bonus 0 and 1,000; finality_leave_activation_daa 0 with finality.leave_delay 3,600; finality_v3_activation_daa 0; finality_daa_rule_activation_daa 0; difficulty_v3_activation_daa 0; latency_ladder_activation_daa 0 with latency_ladder_window_daa 86,400 and the six rungs (27, 35, 53 admissible; 88, 173 and 267 not); proving_consensus_verify_daa 0 with the manifest's program ids. Rung 3 re-measured on the project lead's word (08:46 UK, igneum-build-1 under the measure hold, both build slots held, load 6.1, core 40 at 3.66 GHz, the ladder worktree's igneum-pow 59ae70cf): reps 88 cold alone 9.04 ms, cold with the SMT sibling loaded 10.85 ms (averages of 50: 5.95 and 10.11), over the 10 ms gate by 0.85, so it stays inadmissible; the control rung 2 (reps 53) read 9.25 cold loaded, admissible as before. Raw lines in `counter-asic-3-gate/ladder-bench/20261007T074547Z`.
### 7.7 The miner's stall guard and the node's idle-peer drop (ledger N4)