-
Notifications
You must be signed in to change notification settings - Fork 56
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
feat: Implement BundleDataClient and Dataworker #1155
Merged
Merged
Conversation
This file contains 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
- We should now invalidate bundle block ranges before we attempt to propose or dispute them if the SpokePool client does not have enough of a lookback to fetch all expired deposits in the latest bundle. See `DataworkerUtils.blockRangesAreInvalidForSpokeClients` - Add algorithm in-comments in BundleDataClient for loading "newly expired" deposits for a bundle - This PR should be reviewed in tandem with SDK #TODO which has the required SDK changes to make this work
nicholaspai
added a commit
to across-protocol/sdk
that referenced
this pull request
Jan 23, 2024
…lient These will be useful for the dataworker functions (beginning to be implemented in across-protocol/relayer#1155 ) that have to deal with expired deposits. We need to be able to know when a deposit is expired (comparing its fill deadline TIMESTAMP with a bundle BLOCK NUMBER), and also whether our spoke pool clients have enough of a lookback to fetch expired deposits for a bundle
pxrl
reviewed
Jan 24, 2024
Co-authored-by: Paul <[email protected]>
Co-authored-by: Paul <[email protected]>
nicholaspai
added a commit
to across-protocol/sdk
that referenced
this pull request
Jan 29, 2024
These will be useful for the dataworker functions (beginning to be implemented in across-protocol/relayer#1155 ) that have to deal with expired deposits. We need to be able to know when a deposit is expired (comparing its fill deadline TIMESTAMP with a bundle BLOCK NUMBER), and also whether our spoke pool clients have enough of a lookback to fetch expired deposits for a bundle Signed-off-by: nicholaspai <[email protected]>
nicholaspai
changed the title
feat: Add helper methods for dealing with V3 expired-deposit logic
feat: Add skeleton for V3 BundleDataClient and Dataworker logic
Feb 1, 2024
nicholaspai
commented
Feb 18, 2024
This reverts commit 3553aee.
pxrl
reviewed
Feb 20, 2024
pxrl
approved these changes
Feb 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huge effort 👏
pxrl
approved these changes
Feb 20, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few issues in type narrowing in test.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
DataworkerUtils
DataworkerUtils.blockRangesAreInvalidForSpokeClients
BundleDataClient
Unit tests
Unit tests in
Dataworker.loadData
andDataworker.buildRoots
are illustrative of new logic inBundleDataClient
andDataworkerUtils
.Note this PR will only work with across-protocol/sdk#535 as the SDK versionUpdated now to v0.21.1