-
Notifications
You must be signed in to change notification settings - Fork 902
Custody backfill sync #7907
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
Open
eserilev
wants to merge
39
commits into
sigp:unstable
Choose a base branch
from
eserilev:custody-backfill-sync
base: unstable
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Custody backfill sync #7907
+2,960
−29
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to reduce edge cases, we should wait until the cgc epoch reaches finality before begining custody backfill sync If a node needs to custody backfilll during periods of nonfinality they can simply restart the node and checkpoint sync. |
Some required checks have failed. Could you please take a look @eserilev? 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
das
Data Availability Sampling
fulu
Required for the upcoming Fulu hard fork
syncing
v8.0.0-rc.0
Q3 2025 release for Fusaka on Holesky
waiting-on-author
The reviewer has suggested changes and awaits thier implementation.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Addressed
#7603
Proposed Changes
Custody backfill sync service
Similar in many ways to the current backfill service. There may be ways to unify the two services. The difficulty there is that the current backfill service tightly couples blocks and their associated blobs/data columns. Any attempts to unify the two services should be left to a separate PR in my opinion.
SyncNeworkContext
SyncNetworkContext
manages custody sync data columns by range requests separetly from other sync RPC requests. I think this is a nice separation considering that custody backfill is its own service.Data column import logic
The import logic verifies KZG committments and that the data columns block root matches the block root in the nodes store before importing columns
New channel to send messages to
SyncManager
Now external services can communicate with the
SyncManager
. In this PR this channel is used to trigger a custody sync. Alternatively we may be able to use the existingmpsc
channel that theSyncNetworkContext
uses to communicate with theSyncManager
. I will spend some time reviewing this.TODOs
ValidatorRegistrations.epoch_validator_custody_requirements
while custody syncing, or once its completedspeedo
logicAddtional notes
This needs to be throughouly tested before being included in
8.0.0-rc.0
.