fix: start onchain events ingest from latest block by default

[aditiharini]

When starting a new validator node we end up picking up all blocks from beginning of history by default rather than starting at current. Fix this by starting at current if no explicit bounds are specified.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
snapchain-docs	Ready	Preview, Comment	Apr 28, 2026 0:22am

[Copilot]

Pull request overview

Adjusts the default onchain events ingestion start point so new validator nodes don’t backfill from the beginning of chain history when no explicit bounds are configured.

Changes:

• Introduces a default live-sync start offset from the chain head (LIVE_SYNC_BLOCK_OFFSET).
• Updates the Subscriber::run() default start-block logic to use (latest_on_chain - offset) as the baseline.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Diff Coverage

Diff: origin/main...HEAD, staged and unstaged changes

• src/connectors/onchain_events/mod.rs (87.2%): Missing lines 1293-1297

Summary

• Total: 39 lines
• Missing: 5 lines
• Coverage: 87%

src/connectors/onchain_events/mod.rs

  1289         );
  1290         let live_sync_block;
  1291         match self.start_block_number {
  1292             None => {
! 1293                 live_sync_block = Some(Self::live_sync_start_block(
! 1294                     latest_block_on_chain,
! 1295                     latest_block_in_db,
! 1296                     Self::first_block(self.chain),
! 1297                 ));
  1298             }
  1299             Some(start_block_number) => {
  1300                 let historical_sync_start_block = latest_block_in_db.max(start_block_number);
  1301                 let historical_sync_stop_block = latest_block_on_chain

---