Step 1: app/igneum-app/src/provedefault.rs decides once per install (NVIDIA 12 GB or more, WSL2 answering on Windows, Linux native, Apple silicon off until measured), never switching an explicit on back off; the Settings switch line and the tile line say why (5 unit tests). tools/proving-v1/pc2-prover-cost.ps1 is the PC 2 job (5 min mining alone, 5 min with the prover, GPU memory and host RAM peaks, the sp1-gpu-server's SM targets). Step 2: the host gains --mode chain (consecutive fixtures, each block aggregated with the previous block's proof by recursion), --mode aggregate (the live aggregator over shard proof files, a run of blocks in one process) and --mode verify-segment (the node's verifier against the pinned aggregator key); the app's prover loop gains aggregate_once (spec 7.8). Eight consecutive live fixtures (blocks 81046 to 81053, node 1's export at tip 81076) under proving/fixtures/chain/. tools/proving-v1/pc2-chain.ps1 is the PC 2 job (held). Steps 3 and 4: tools/proving-v1/coverage.mjs (the proven-block share and the on-chain latency from one node's RPC), tools/proving-v1/net.mjs (the fast-time 3-node harness on 29950+ with the known-finished and known-failed cases of the chain rule and the unproven rule), the four proving_v1 fields in infra/fast-time/override-60x.json. Spec 7.8, the 7.4 rows, the 5.3 sentence, docs/plans/proving-v1.md. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Symbolic link
1 line
No EOL
62 B
Text
Symbolic link
1 line
No EOL
62 B
Text
/Users/joshm/Projects/igneum/tools/prove-fixtures/node_modules |