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

Block rate on Devnet 2: run A measured (10 blocks/s on a star: 4.25 blocks/s, 1.09 blue/s, 77.6 percent red, difficulty easing, exec follower at 0.05 blocks/s)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-josh 2026-10-06 21:57:29 +01:00
parent f9ad70e1d2
commit bf3da7fe30
1 changed files with 31 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
docs/analysis/block-rate-devnet2.md
View file

@ -21,7 +21,37 @@ Payout interval per tier, from each run's measured block rate and the chain's ha
## Measured
RUN_A
### Run A: 10 blocks per second, star topology (19:17Z to 20:25Z)
Seed: the fork's igneumd (83702a35, `IGNEUMD_DEVNET_BPS=10`) on igneum-build-1 (188.40.146.49:26611, a public port), genesis
f682b78a4e64f0d2, digest 436d62a5b962e1c2, mining from 19:17:26Z. Miners: dn2-1/2/3 from 19:25Z, the 38 wave pods from 19:26Z
(each node beside the pod's live-devnet node on other ports, each dialling the seed only: no pod has an inbound port), 41 peers
on the seed. Collector rows every minute in `~/Desktop/fleet/bps/A.jsonl` (the first 20 minutes carry the seed's log counts only;
the watch line from 19:37Z after the seed's miner binary was staged).
| Read | Value | Source |
|---|---|---|
| Blocks at 10 min (19:36Z) | 5,733 (12.4 blocks/s over the last 159 s) | seed watch line |
| Blue score at 10 min | 1,307 (77 percent of blocks red) | the same |
| Blocks 19:37Z to 20:24Z (47 min) | 7,204 to 19,153: 4.25 blocks/s; blue +2,926: 1.09 blue/s; red share 77.6 percent | A.jsonl |
| Rate by six-minute interval | 7.7, 1.9, 2.9, 2.8, 5.9, 4.2, 3.2, 5.1 blocks/s; blue 0.6 to 1.6/s | A.jsonl |
| Tips | 246 at 10 min, 295 to 662 through the hour, rising | A.jsonl |
| Difficulty | 6,719 at 19:33Z, 3,551 at 19:36Z, 1,307 at 19:42Z, falling the whole hour (the rule reads the blue rate under target and eases) | seed watch, by hand |
| Max selected-chain reorg | 55 blocks (a late pod unwinding its genesis-only view at join) | seed log |
| Exec follower | tip 84 at 19:30Z, 240 at 20:19Z: 0.05 blocks/s against 1.1 blue/s; lag 18,901 blocks at the end | igneum_getExecStatus on the seed |
| Finality | 18 locks over the run (the voters are the 42 miners' keys) | seed log |
What it says: with 42 cards on a 10 blocks/s profile the DAG ran at 4 to 12 blocks a second but the selected chain at about
1.1 blue blocks a second, three in four blocks red, tips in the hundreds, and the difficulty rule eased all hour because it
measures the blue rate. The Horizon network lane's read of the same rows (`docs/analysis/horizon/network.md`): the reds came
from node throughput, not the star: the seed spent 61 to 345 ms of CPU per accepted block (mergeset 8 to 200), a 100 ms-per-block
knee at 10 blocks/s, RSS 5.4 GB at 12,000 blocks, and the propagation model gives 0.0 percent red for both star and mesh at
the measured latencies. So a topology run (A2) proves nothing without per-block CPU profiling on a pod, and was dropped. A
true mesh was also not possible tonight: no provider gave a pod with an inbound p2p port, the live devnet has the same star
(every rented node dials the two hands and the hub), and the standing-fleet ports rule in `docs/plans/gpu-fleet.md` is the fix.
The exec follower is the second finding: at 1.1 blue blocks a second it executed 0.05 blocks a second, so a 10 blocks/s chain
with payload would leave every wallet and prover reading state hours behind the tip within the first hour.
RUN_B