fin-proof: bench-log entry frame
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
parent
f4acab066d
commit
e94cc7ebfd
1 changed files with 17 additions and 0 deletions
|
|
@ -2633,3 +2633,20 @@ in the same shape and reports a box behind its wanted binary.
|
|||
| Rig | the same, and a rig that leaves is itself a weight removal: at 459 MH/s on tonight's devnet it is about 20 percent of the weight, over the hour's budget by itself |
|
||||
| Pool | a pool node is one voter carrying its members' whole weight; a pool restart is the largest single removal on the network and must be sliced like the fleet's |
|
||||
| The network | finality by miner weight is only as steady as the miners' uptime; until public hash dwarfs the fleet, the fleet's supervisor is a consensus component |
|
||||
|
||||
## Finality in the proof, 7 October 2026 (branch fin-proof, fork branch fin-proof-node): the weight table inside the recursive segment proof, what it costs
|
||||
|
||||
Design `docs/design/finality-in-proof.md` (frontier rank 1, 3.3). The aggregator guest folds one chain block's blue blocks into the carried W2 table (key table inline, block ring witnessed, history MMR), verifies lock certificates against the table the proof committed at the checkpoint's own block, and commits a 164-byte extension. Everything behind `finality_in_proof_activation_daa` (never until the override file sets it); nothing on the devnet.
|
||||
|
||||
### What was built and tested (box igneum-build-1, 09:02 UK)
|
||||
|
||||
| What | Result |
|
||||
|---|---|
|
||||
| `igneum-fin-core` harness (real BLS keys through blst, the guest's curve through zkcrypto `bls12_381` under SP1's patch) | 7 of 7: known-failed first (today's `core.js` rule locks on a forged voter list from the attacker's node; the proof-carried table refuses the same certificate twice, then the honest one locks), the table equals a brute-force window count at every one of 500 blocks, double counting refused and ageing exact at the edge, two thirds inclusive (160 of 240 locks, 120 does not), the frozen table holds a 60 percent side and a leave releases it only after `leave_delay`, stale after a window with no lock, a light client answers final / not final / not in this chain from the extension and an MMR path, the two curves agree and reject a flipped bit |
|
||||
| `igneum-prove-core` 8 of 8, `igneum-prove-host` 9 of 9 (1 ignored) | the old 340-byte statement unchanged byte for byte without the finality input |
|
||||
| Node: `igneum-exec` 26 of 26 | the new veto test: a record without the extension after the switch, a tampered extension, an extension before the switch, each refused naming `fin_ext` |
|
||||
| Node: `kaspa-consensus-core` 122 of 123 | the one red, `fast_time_60x_file_is_the_devnet_at_60x`, is master's `infra/fast-time/override-60x.json` lagging `difficulty_v3_activation_daa` (predates this lane; the new switch is in the file) |
|
||||
| Guests re-pinned on the Mac (succinct toolchain, 5 min 32 s full, 2 min 59 s incremental) | aggregator ELF 319,744 to 767,424 bytes (the BLS12-381 pairing, hash-to-curve and the fold), id `0x12bff5be...`; the shard ELF's id moved too (`0x2b1a81cb...` to `0x39db9d96...`) with no source change, the per-machine id class of 5 October |
|
||||
| Public values | 340 bytes without the finality input, 504 with (the 164-byte extension); the compressed proof size is the recursion's constant |
|
||||
|
||||
### Measurements
|
||||
|
|
|
|||
Loading…
Reference in a new issue