reorg lag by 100 blocks

[nischitpra]

Summary by CodeRabbit

• Performance Improvements
  • Optimized block validation logic to reduce assessment frequency and system resource usage, improving overall platform stability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes modify block window thresholds in the reorg validator. The minimum block count for triggering reorg checks increases from 5 to 100 blocks. The safety lag in range calculation also increases from 5 to 100 blocks, adjusting the lookback window boundaries.

Changes

Cohort / File(s)	Summary
Reorg Validation Thresholds internal/committer/reorg.go	Updated RunReorgValidator threshold from endBlock-startBlock < 5 to endBlock-startBlock < 100; modified getReorgRange safety lag calculation from endBlock-5 to endBlock-100, increasing the block window buffer before reorg assessments are performed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Single file with localized threshold adjustments
• Changes are straightforward numeric modifications
• Recommend verifying the rationale behind increasing thresholds from 5 to 100 blocks to ensure this aligns with intended reorg detection timing and chain reorganization safety margins

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch np/reorg_minlength

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 385f7d7 and f968988.

📒 Files selected for processing (1)

• internal/committer/reorg.go (2 hunks)

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}