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

Bench log: the rented fleet is the devnet's finality (the weight shares, the pause, the 10 percent rule, the supervisor's restart times, per tier)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 22:00:00 +00:00
parent 2b724114dd
commit 5fa4345181
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
docs/bench-log.md
View file

@ -2026,3 +2026,27 @@ star. Per tier the blue rate decides the payout interval (1.09 against 1.19 blue
for a paying block either way), so the higher rate buys the solo miner nothing until the node processes a block in under 50 ms
at mergeset 248. Recommendation (the lane's): 1 block/s for the testnet and the launch, 10 behind three measured gates.
Full tables and sources: `docs/analysis/block-rate-devnet2.md`, rows in `~/Desktop/fleet/bps/{A,B}.jsonl`.
## The rented fleet is the devnet's finality, 6 October 2026 (branch gpu-fleet)
Measured at 21:57Z from the hub's last 2,000 blocks: the 38 wave pods held 77.8 percent of the voter weight (mean 2.05 percent
a pod), the 14 standing boxes most of the rest, the hands and the hub the remainder; the last lock signed 93.5 percent of the
active voters and 89.9 percent of the frozen table (53 of 84 voters on the first certificate). Earlier the same evening the
fleet removed 13 miners' GPUs inside three minutes and finality paused for two hours five minutes (18:39:36Z to 20:44:44Z,
42.7 percent of the table gone with earlier leavers; rule v3 holds a full window). From that came the 10 percent rule (never
remove more than 10 percent of the live devnet's weight in an hour, `tools/fleet/lib/standing.py weight_check`) and the wave's
wind-down by hourly slices (`tools/fleet/winddown.py`: slice 1 at 21:58Z took 12 pods and the 8x rig at 8.6 percent of weight).
When the wave is gone the 14 standing boxes hold about 95 percent of the weight, so from then until public hash arrives the
fleet alone is the devnet's finality: a home miner's lock lands only while the fleet is up. What holds it up: every standing
box runs under `box-standing.sh`, which restarts a dead node within one of its 60-second passes (the hub's three deaths
tonight: 63 s, 41 s and 56 s to the restart line), restarts the miner with the node, prunes the prover's exports and trims
the node log, and runs the exec recovery recipe when the state layer reads zero; `lib/standing.py loop` re-rents a dead host
in the same shape and reports a box behind its wanted binary.
| Tier | What it means |
|---|---|
| Home miner | your lock depends on 14 rented cards staying up and mining; a finality pause is not your node's fault and nothing you can fix; the rule above is what keeps it from recurring on the fleet's side |
| 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 |