Skip to content
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

Should lighthouse sync blocks outside da window? #7011

Open
dapplion opened this issue Feb 19, 2025 · 0 comments
Open

Should lighthouse sync blocks outside da window? #7011

dapplion opened this issue Feb 19, 2025 · 0 comments
Labels

Comments

@dapplion
Copy link
Collaborator

dapplion commented Feb 19, 2025

The Deneb p2p makes it impossible for nodes to download blobs outside the data availability (da) window (approx 18 days from the clock slot).

During forward sync, Lighthouse currently imports these blocks outside the data availability (DA) retention window regardless of whether they were available.

Consider the following chain. Should a Lighthouse full node attest to this head?

Image

And this one?

Image

IMO it should not. A full node must independently check that blocks are valid and available, without relying on any majority. A finalized un-available block is still an un-available block that must be rejected.

Therefore LH should reject blocks from outside the DA window that it can't independently verify to be available. If a node runner has a node that has been stopped for more than 18 days, it should do one of the following:

  • Checkpoint sync into a finalized checkpoint inside the retention window
  • Run the node with a flag like --unsafe-da-sync
  • Manually tell the node that some block hash and its ancestors are available
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants