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.

Sign up for GitHub

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

Jump to bottom

Improve Historical Sync to speed up backfill #7244

Closed
Tracked by #6822
tbenr opened this issue Jun 8, 2023 · 3 comments
Closed
Tracked by #6822

Improve Historical Sync to speed up backfill #7244

tbenr opened this issue Jun 8, 2023 · 3 comments
Labels
Epic Deneb Issues required to implement Deneb upgrade

Comments

@tbenr
Copy link
Contributor

tbenr commented Jun 8, 2023 •
edited
Loading

related to #7243

since the node cannot perform duties until it has validated the entire Data Availability window, we must evolve the historical sync to be multi-peer (similarly to forward sync) to be able to download and validate as quick as possible the whole DA and start performing duties.
@tbenr tbenr mentioned this issue Jun 8, 2023
Closed
44 tasks
@rolfyone
Copy link
Contributor

rolfyone commented Jun 8, 2023

wow this seems like a huge step backwards... why is that a requirement??

@tbenr tbenr added the Epic Deneb Issues required to implement Deneb upgrade label Jun 9, 2023
@tbenr
Copy link
Contributor Author

tbenr commented Jun 9, 2023

It's a forkchoice requirement in spec. Was a bit unclear to me and I asked for confirmation in yesterday's ACDC

@tbenr
Copy link
Contributor Author

tbenr commented Jun 14, 2023

After per latest 4844 implementers call I'm going to close these tickets.

@tbenr tbenr closed this as completed Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic Deneb Issues required to implement Deneb upgrade
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rolfyone @tbenr