diff --git a/docs/fud-ledger.md b/docs/fud-ledger.md index 6d494a9a9..35cd23476 100644 --- a/docs/fud-ledger.md +++ b/docs/fud-ledger.md @@ -2089,7 +2089,7 @@ The first disagreement of that run was on an A row (a signing key, so not N7's b Per tier: no balance anyone can see is wrong (0.0003 percent of a share on the ramp), but the bridge identity the base-unit gate asserts is false by that slope on the devnet today and on the testnet from its first block, and a strict reconciler reports it. -Fix (switched, since it changes the EVM state transition): `Params::subsidy_per_block_activation_daa`, a new object field in the subsidy family, never on every network as compiled, in the digest once set; from that chain-block DAA the service fills `SegmentBlock::subsidy` with the block's own `block_subsidy(daa)` and the executor splits it. Known failed first in the executor's test: two blocks a second apart on the ramp and two straddling the first halving boundary, the chain block's subsidy without the rule and their own with it. The harness reports the exact per-row identity beside the N7 bonus ratio and fails on it under `--subsidy-per-block`. The value is the project lead's word (the coordinator recommends 0 on the testnet, an upgrade height with 0.3.19 on the devnet); the testnet lane's re-cut gains the one field. Commit hash: in the status log once green. +Fix (switched, since it changes the EVM state transition): `Params::subsidy_per_block_activation_daa`, a new object field in the subsidy family, never on every network as compiled, in the digest once set; from that chain-block DAA the service fills `SegmentBlock::subsidy` with the block's own `block_subsidy(daa)` and the executor splits it. Known failed first in the executor's test: two blocks a second apart on the ramp and two straddling the first halving boundary, the chain block's subsidy without the rule and their own with it. The harness reports the exact per-row identity beside the N7 bonus ratio and fails on it under `--subsidy-per-block`. Fixed in d840537b on ca3-v4-0318 (09:21 UK; igneum-exec 26, consensus-core 113, consensus 109 plus the two moved targets, kaspad check clean on igneum-build-1). the project lead's ruling (09:5x UK): the testnet active from genesis (the field at 0 in the re-cut object; the digest and the genesis hash move with it), the devnet at an upgrade height carried by 0.3.19 under the fleet's one-box-at-a-time rollout, the height named at that cut. The testnet lane's re-cut gains the one field. ## Status updates, 5 October 2026 (ledger sweep, night of 4 to 5 October)