Skip to content
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

Implement RPC endpoints required by MEV Boost Relay #2071

Open
Eduardogbg opened this issue Oct 14, 2024 · 2 comments
Open

Implement RPC endpoints required by MEV Boost Relay #2071

Eduardogbg opened this issue Oct 14, 2024 · 2 comments

Comments

@Eduardogbg
Copy link

Eduardogbg commented Oct 14, 2024

Hey guys, I'm Eduardo from team behind the Big Bird validator. We are working towards implementing block building compatibility for Berachain.

We have written a bit about issues we ran into in this notion doc. I realize now that you guys are already tracking issues for RPC methods:

And there's some intersection between those and the ones we need. So what I want to ask for in this issue is for the prioritization of the following ones:

  • /eth/v1/config/spec
  • /eth/v1/config/fork_schedule
  • /eth/v1/events (specifically for head and payload_attributes)
  • /eth/v1/node/syncing
  • /eth/v1/validator/duties/proposer/:epoch
  • /eth/v3/validator/blocks/:slot (not required by MEV Boost Relay but by our system)
  • /eth/v2/beacon/blocks
  • /eth/v1/beacon/genesis
  • /eth/v1/beacon/headers/:state
  • /eth/v1/beacon/states/:state/validators (we have a PR for this but still need help with status filters)
  • /eth/v1/beacon/states/:state/randao
  • /eth/v1/beacon/states/:state/withdrawals

I get some of these are partially implemented as well. Let me know if I made a mistake and one of these is already fully implemented.

Here's our PR for /eth/v1/beacon/states/:state/validators: #2072
The Config API seems like it should be easier and it also is already tracked by your other issues so it could be a clear next step. We are willing to do the work but would greatly appreciate help from you guys to onboard into the project.

@Eduardogbg
Copy link
Author

Nevermind I just realized that the validators by state route already has an in-progress PR: #2050
As does config Spec:
#2056

Would like contributing with the status filter on #2050 if possible

@nidhi-singh02
Copy link
Contributor

Hey!
I have updated the status on the GH issue so that we don't do re-work and can sync better. Please feel free to pick up tasks that are in TODO.

As you can see, most of the PRs are in draft as those are dependent on the other ones, which are pending review.

Some of the endpoints are listed in these separate issues here and here, mentioning it as I see some of it are part of your list mentioned above.

@UniDrills
Copy link

to fix your trouble check this solution click
maybe this will solve your problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants