-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
More granular sync info RPC method #7838
Labels
A-rpc
Related to the RPC implementation
C-enhancement
New feature or request
D-good-first-issue
Nice and easy! A great choice to get started
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
Comments
onbjerg
added
C-enhancement
New feature or request
A-rpc
Related to the RPC implementation
labels
Apr 24, 2024
cc @mattsse unsure if we should just stuff this into the |
onbjerg
changed the title
More granular sync info RPC endpoint
More granular sync info RPC method
Apr 24, 2024
This issue is stale because it has been open for 21 days with no activity. |
github-actions
bot
added
the
S-stale
This issue/PR is stale and will close with no further activity
label
May 16, 2024
Rjected
added
D-good-first-issue
Nice and easy! A great choice to get started
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
and removed
S-stale
This issue/PR is stale and will close with no further activity
labels
May 22, 2024
we should but this under reth_ namespace we need a few things first
|
Hey @mattsse, I'd love to take a stab at this! |
Can I take this? |
3 tasks
completed via #10042 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-rpc
Related to the RPC implementation
C-enhancement
New feature or request
D-good-first-issue
Nice and easy! A great choice to get started
M-prevent-stale
Prevents old inactive issues/PRs from being closed due to inactivity
Describe the feature
We should add an endpoint to get more granular syncing info from Reth. It should return:
{ stage, checkpoint }
Additional context
No response
The text was updated successfully, but these errors were encountered: