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

exec-sync plan: the fresh node's IBD finding (10 retries over 40 min from the finality route's capacity; the igneum-pow feature needed to join)

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 14:49:10 +00:00
parent 0b75539b1c
commit 2332ff326f
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/plans/exec-sync.md
View file

@ -41,6 +41,22 @@ network holds the bodies the state was built from, and the state cannot be rebui
| Provers | payouts invisible | every carried record since proving v0 paid as carried (1,482 shards); new proofs verify against the new state from the trust DAA on |
| Joiners today | an empty EVM for ever | IBD gives the pruning point 27,276 and the bodies from it, so a fresh node replays the same 90 s with no snapshot; once the pruning point moves past R the p2p snapshot (protocol 16) starts it |
## A fresh node today (the rented RTX 4090 box, 6 October 2026, 14:04Z on)
The exec-sync node built with the `igneum-pow` feature (a node without it refuses the headers proof: "epoch seed
header ... fails its own proof of work", the stub engine; the Linux cross-build sets the feature, a hand build must),
a fresh data dir, the live override object, the seed as the peer.
| Phase | What happened |
|---|---|
| IBD with the headers proof | failed 10 times from 14:04Z to 14:45Z, "peer connection is closed" from the seed and the hub about 25 s after the proof arrived, each right after "incoming route capacity for message type IgneumFinality has been reached" for that peer; the 11th attempt went through at 14:45Z |
| Bodies from the pruning point | 5 to 10 blocks a second (1% at 14:46Z, 2% at 14:47Z of the blocks since 11:40Z) |
Consequence: a home miner installing today waits about an hour before the node is synced, most of it in IBD retries
the finality relay causes, not in execution. The fix is in the p2p layer (the finality flow's route capacity during
IBD, or no finality messages to a peer still in IBD): the consensus engineer's, not this branch's. The executed tip
and the replay time follow the sync.
## Open
The fresh-join time on a rented box (in progress); the trust DAA's value (at or above the switch); the first 12