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

bench-log: the proof-system slot on the fast-time harness (21 and 34 checks)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 11:54:40 +00:00
parent 796a67eb52
commit 29bc922422
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/bench-log.md
View file

@ -1846,3 +1846,14 @@ Run b (`segments-pc2-pv1b`, 07:20Z to 07:51Z) claimed nothing in 88 passes: the
| The rule as shipped (no switch): fresh refused while the previous segment is pending (known-failed), accepted after it is unproven | 22 passed | 166.2 s |
| `--fresh-rule 0`: fresh accepted while the previous segment is pending, `freshAdmissible` true, still refused after a proven one, the second offer a duplicate ("segment already paid") | 23 passed | 139.9 s |
### 6 October 2026, 11:47Z to 11:54Z, the proof-system slot on the fast-time harness (Mac, `tools/lock/with-lock.sh run`)
`IGNEUM_PV1_BIN=vendor/igneum-node/target-pv2/release node tools/proving-v1/net.mjs --segment 8 --unproven 10 [--v2 200 --fresh-rule 0]` (fork proving-v2 at d0522b52, app proving-v2 at b133fd6; 3 nodes at 60x on ports 29950+, every node with trust for both systems and fake RISC Zero ids through `IGNEUM_PROOF_PROGRAM_IDS_V2`):
| Case | Checks | Time |
|---|---|---|
| No switch (SP1 only, the rule as shipped): the proving v1 cases | 21 passed | 142.5 s |
| `--v2 200 --fresh-rule 0`: the status reports both systems and the switch; the system 2 statement names the RISC Zero ids and is not admissible before the switch; a version 3 segment record and a version 2 shard record are refused before it ("not admissible before DAA 200"); from it the statement is admissible, a version 3 segment record is accepted, carried and paid with chain_len 8, a version 2 shard record is accepted; the SP1 statement after the system 2 segment names a different-system previous, an SP1 fresh-chain record is accepted after the proven system 2 segment and paid (the chain restarts at the system change) | 34 passed | 222.0 s |
Unit tests (fork): the digest moves once `proving_v2_activation_daa` is set; a version 3 record names the RISC Zero ids, is refused before the switch, accepted from it, fresh after a proven SP1 segment, vetoed when its statement names the SP1 ids; a re-labelled version breaks the signature; a version 2 shard record is admissible only from the switch; an unknown version names no system (`cargo test -p kaspa-consensus-core -p igneum-exec proving`, 8 and 11 passed). App: 120 tests pass.