Sync Relayer from previous Ethereum block #384
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
|
@denalimarsh i know you're blocked on parity, but is this existing functionality something we could complete/merge in and address the initialization extras when the apis are ready? |
philipstanislaus
approved these changes
May 11, 2021
denalimarsh
force-pushed
the
dm-relayer-sync-beefy
branch
from
3f21899 to
767be45
Compare
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.
This PR includes the Ethereum-side functionality required for the Relayer to sync from a previous block. Syncing process steps:
InitialVerificationSuccessfulevents from Ethereum, use them to update the status of items in the databaseFinalVerificationSuccessfulevents, update the status of database itemsI'm currently blocked by step 1, as it's not possible to query BEEFY justifications by block yet.