Skip to content

add flag for prysm to use SSZ encoding for sending REST calls ( at least where we can) #14805

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

Open
3 tasks
james-prysm opened this issue Jan 16, 2025 · 1 comment · May be fixed by #15381
Open
3 tasks

add flag for prysm to use SSZ encoding for sending REST calls ( at least where we can) #14805

james-prysm opened this issue Jan 16, 2025 · 1 comment · May be fixed by #15381
Assignees
Labels

Comments

@james-prysm
Copy link
Contributor

james-prysm commented Jan 16, 2025

🚀 Feature Request

Description

more and more endpoints now support SSZ, we support it beacon apis and builders will be supporting ssz soon ethereum/builder-specs#104

we should have a flag turned on so that we can test our requests and responses in SSZ.

Describe the solution you'd like

  • Create of list of endpoints that support vs not support SSZ for this feature

  • have ssz fall back to json is not available

  • create list of endpoints that can be done in ssz and which are not for the validator client

  • add a flag for enabling ssz, add it as a new feature flag

  • add new condition either at the http client level or at the endpoint itself,

  • add some helper functions to make it easier + take a looka t how builder api does it.

Describe alternatives you've considered

@james-prysm james-prysm added the API Api related tasks label Jan 16, 2025
@rose2221
Copy link
Contributor

rose2221 commented Mar 3, 2025

i would like to work on this issue!

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

Successfully merging a pull request may close this issue.

2 participants