Skip to content

do not merge: Electra sync forced with Sepolia #1449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 154 commits into from

Conversation

LeanSerra
Copy link
Contributor

Motivation

Sync Sepolia

Description

  • Comment out the blob validations
  • When we get a block with missing blobs we schedule the download but process the block anyways
  • We were constantly penalizing peers so that was also commented out

Findings

  • The peers are constantly being penalized resulting in running out of peers
  • After checkpoint-sync when downloading blocks the chain wouldn't advance because the next block was stuck in :download_blobs
  • After commenting the blob validation I run into an issue only once in several tries:
    • The chain was advancing but one block failed because it was from "the future" which resulted in that block having the status of :invalid when it wasn't the check for ForkChoice.future_slot? in process_block tries to fix this but its not really tested

rodrigo-o and others added 30 commits March 17, 2025 18:33
Base automatically changed from electra_max_blobs to electra-support April 25, 2025 20:19
@LeanSerra LeanSerra changed the base branch from electra-support to main April 28, 2025 12:23
@rodrigo-o
Copy link
Collaborator

This will be closed until we start delving in Sepolia syncing again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

2 participants