-
Notifications
You must be signed in to change notification settings - Fork 692
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
Node/EVM: Track latest block #3470
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
bruce-riley
force-pushed
the
node/evm_track_latest_block
branch
from
October 27, 2023 12:53
a7d2076
to
b6ab5df
Compare
panoel
changed the title
DRAFE: Node/EVM track latest block
DRAFT: Node/EVM track latest block
Oct 27, 2023
bruce-riley
force-pushed
the
node/evm_track_latest_block
branch
3 times, most recently
from
October 29, 2023 18:17
e17bd21
to
5b4918a
Compare
bruce-riley
changed the title
DRAFT: Node/EVM track latest block
Node/EVM track latest block
Oct 29, 2023
bruce-riley
requested review from
evan-gray,
panoel and
kev1n-peters
as code owners
October 29, 2023 21:14
panoel
reviewed
Oct 30, 2023
panoel
reviewed
Oct 30, 2023
panoel
reviewed
Oct 30, 2023
panoel
reviewed
Oct 30, 2023
panoel
previously approved these changes
Oct 30, 2023
evan-gray
requested changes
Oct 30, 2023
bruce-riley
force-pushed
the
node/evm_track_latest_block
branch
from
October 31, 2023 16:26
1ee8654
to
aa31d1d
Compare
bruce-riley
force-pushed
the
node/evm_track_latest_block
branch
2 times, most recently
from
November 1, 2023 17:35
392a874
to
9458000
Compare
panoel
previously approved these changes
Nov 1, 2023
evan-gray
force-pushed
the
node/evm_track_latest_block
branch
from
November 1, 2023 19:33
9458000
to
be71ef8
Compare
evan-gray
requested changes
Nov 2, 2023
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.
I think there's one case of not setting safe + ccq that I'm concerned about.
panoel
approved these changes
Nov 2, 2023
evan-gray
approved these changes
Nov 2, 2023
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 changes the EVM watcher so that it publishes latest, safe and finalized blocks for all chains. These are published in the gossip heartbeats and in Prometheus metrics.
This PR does the following:
BatchPollConnector
which uses batch RPC calls to query chains that support querying forfinalized
andsafe
.EthereumConnector
andCeloConnector
publish each block aslatest
,safe
andfinalized
.finalized
tag (currently only Neon), the existingBlockPollConnector
that uses a finalizer was modified to also publish latest and safe, in addition to the current finalized.The result of this PR is that every chain now publishes all three finality types, where if the chain does not provide a query for
safe
, it is published when the block is finalized.