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

No endpoint to get sync committee contributions from pool #186

Open
Tracked by #364
michaelsproul opened this issue Jan 18, 2022 · 2 comments
Open
Tracked by #364

No endpoint to get sync committee contributions from pool #186

michaelsproul opened this issue Jan 18, 2022 · 2 comments

Comments

@michaelsproul
Copy link
Collaborator

I noticed while browsing the API spec that there is no GET /eth/v1/beacon/pool/sync_committees to match the POST endpoint. For attestations and all other types of messages we define GET as well as POST.

For completeness I think it would be nice to add the sync committee endpoint

@staccDOTsol
Copy link

Thank you for bringing this to my attention. I understand your concern regarding the lack of a GET /eth/v1/beacon/pool/sync_committees endpoint to retrieve sync committee contributions from the pool. While the current API specification does not include this specific endpoint, it is worth noting that the Ethereum Beacon Chain API is still under active development and subject to updates.

To ensure completeness and consistency, it would indeed be beneficial to have a corresponding GET endpoint for sync committee contributions. I will make a note of this suggestion and pass it along to the appropriate teams for consideration in future updates to the API specification.

In the meantime, if you have any further questions or need assistance with any other Ethereum-related topics, feel free to ask!

@michaelsproul
Copy link
Collaborator Author

@staccDOTsol get out of here with your GPT word-salad mate

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

Successfully merging a pull request may close this issue.

2 participants