chore: update know blocks

[akaladarshi]

Summary of changes

Changes introduced in this pull request:

• update know blocks chceckpoint

Reference issue to close (if applicable)

Closes: #6270

Other information and links

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Summary by CodeRabbit

• Chores
  • Updated block header mappings for calibnet and mainnet networks to support additional network epochs.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added checkpoint block header mappings to build/known_blocks.yaml for calibnet epoch 3196800 and mainnet epoch 5529600 to improve blockchain snapshot loading performance.

Changes

Cohort / File(s)	Summary
Checkpoint updates build/known_blocks.yaml	Added block header mappings for calibnet (epoch 3196800) and mainnet (epoch 5529600)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file, straightforward data-only additions with no logic or control flow changes
• Consistent, repetitive pattern (same type of entry added for two networks)

Possibly related issues

• Issue #6270 (cron: update known_blocks.yaml) — This PR implements the monthly checkpoint update procedure documented in the linked issue.

Possibly related PRs

• PR #6163 — Adds new block header mappings to build/known_blocks.yaml for calibnet and mainnet (similar checkpoint updates).
• PR #6228 — Updates build/known_blocks.yaml with epoch→header checkpoint mappings for calibnet and mainnet.
• PR #6017 — Adds new checkpoint entries to build/known_blocks.yaml for calibnet and mainnet.

Suggested reviewers

• LesnyRumcajs
• sudo-shashank
• hanabi1224

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update know blocks' contains a typo ('know' instead of 'known') and is slightly vague, but it is clearly related to the main change—updating the known_blocks.yaml file with new checkpoint mappings.
Linked Issues check	✅ Passed	The PR adds checkpoint mappings for both mainnet (epoch 5529600) and calibnet (epoch 3196800) to build/known_blocks.yaml, which directly fulfills the requirement in issue #6270 to update known_blocks.yaml for both chains.
Out of Scope Changes check	✅ Passed	All changes are strictly limited to updating the build/known_blocks.yaml file with new epoch-to-header mappings, which is exactly what the linked issue #6270 requires; no extraneous changes are present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch akaladarshi/update-known-blocks

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e373a21 and 71e2441.

📒 Files selected for processing (1)

• build/known_blocks.yaml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: cargo-publish-dry-run
• GitHub Check: Build Ubuntu
• GitHub Check: Build MacOS
• GitHub Check: All lint checks
• GitHub Check: tests
• GitHub Check: tests-release
• GitHub Check: Build forest binaries on Linux AMD64

🔇 Additional comments (1)

build/known_blocks.yaml (1)

10-10: LGTM!

The new checkpoint entries follow the existing format and maintain proper descending epoch order on both chains. Calibnet's epoch 3196800 and mainnet's epoch 5529600 are correctly positioned as the latest entries.

To confirm these are the correct hashes from the latest snapshots, please verify:

• The hashes were obtained using forest-tool archive checkpoints on the latest downloaded snapshots for each chain
• The epochs match the expected checkpoint intervals (typically 86400 blocks per epoch)

Also applies to: 48-48

---

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