Open Eduardogbg opened 1 month ago
Eduardogbg
commented
1 month ago Nevermind I just realized that the validators by state route already has an in-progress PR: https://github.com/berachain/beacon-kit/pull/2050 As does config Spec: https://github.com/berachain/beacon-kit/pull/2056
Would like contributing with the status filter on #2050 if possible
nidhi-singh02
commented
1 month ago 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
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 forheadandpayload_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/withdrawalsI 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: https://github.com/berachain/beacon-kit/pull/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.