From 2332ff326fb079b1639d3c59b8dfa8f41d0b7d50 Mon Sep 17 00:00:00 2001 From: igneum-labs <337424239+igneum-labs@users.noreply.github.com> Date: Tue, 6 Oct 2026 14:49:10 +0000 Subject: [PATCH] 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) Co-Authored-By: Claude Fable 5.1 --- docs/plans/exec-sync.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/plans/exec-sync.md b/docs/plans/exec-sync.md index a1c7decdf..a45a4e11b 100644 --- a/docs/plans/exec-sync.md +++ b/docs/plans/exec-sync.md @@ -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