igneum/docs/analysis/block-rate-devnet2.md

1.9 KiB

Block rate on Devnet 2: 10 blocks per second against 1, on the rented fleet

6 October 2026, the project lead's experiment (through the coordinator, 17:5xZ): "Devnet 2 at a higher block rate for solo miners (Kaspa's answer)". Branch gpu-fleet; the node profile on the fork branch devnet2-bps (1279a1d6 on release-0.3.14-node 4c6b129d): a suffixed devnet started with IGNEUMD_DEVNET_BPS=10 (or 5) runs BlockrateParams::new::<10>() with the TenBps subsidy and target time, Kaspa's Crescendo-style constants for that rate (k 124, merge depth, sample rates, mergeset limit, parents, coinbase maturity from consensus/core/src/config/bps.rs); the shared devnet never reads the variable, so the live digest and rules are untouched. Built on igneum-build-1 (tools/build-remote.sh). Numbers land below as they are measured; every figure carries its source file under ~/Desktop/fleet/bps/.

The runs

Run Chain Miners Length What is read
A igneum-devnet-2, fresh genesis, 10 bps the 38 wave pods plus the 4 Devnet 2 boxes (42 cards, about 2.0 GH/s) 60 min blocks per second achieved, blue and red blocks per minute (orphan rate), blue score growth, max reorg depth, checkpoint lock delay and weight at this voter count, p2p bytes per node per minute, node CPU and RSS, exec lag (height minus executed tip), payout intervals per miner from the coinbase records
B the same boxes, fresh genesis, 1 bps the same 30 min the same (the control)

Payout interval per tier, from each run's measured block rate and the chain's hash: a 4070 at 28 MH/s, a 5090 at 128 MH/s, an 8x 4090 rig at 459 MH/s, at tonight's network hash and extrapolated to 1, 10 and 100 TH/s networks (interval = blocks per second x miner share, the arithmetic in tools/fleet/bps-collect.py).

Measured

RUN_A

RUN_B

Per tier

TIER_TABLE

The recommendation for mainnet's rate

RECOMMENDATION