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

SSZ support for publishing blocks to the beacon node #525

Open
avalonche opened this issue Sep 11, 2023 · 3 comments
Open

SSZ support for publishing blocks to the beacon node #525

avalonche opened this issue Sep 11, 2023 · 3 comments

Comments

@avalonche
Copy link
Collaborator

avalonche commented Sep 11, 2023

Is your feature request related to a problem? Please describe.
The new v2 publish block endpoint can accept either json or ssz. We should publish blocks to the beacon node using ssz with the v2 endpoint being supported in the relay. This will improve block publishing latency.

Describe the solution you'd like
Serialise the payload with ssz instead of json when publishing to the v2 endpoint.

@hopinheimer
Copy link

This will be a modification of original the PublishBlock() or do we keep the PublishBlock() as is for a fallback option. I see that the SubmitBlockRequestV2Optimitic is already implemented. I hope I'm making some sense in my findings 😅

@avalonche
Copy link
Collaborator Author

PublishBlock() will retain the functionality to switch between v1 and v2 but v2 will default to using ssz encoding.

@avalonche
Copy link
Collaborator Author

will bump this to high priority as may be causing too high latency:

"error":"write tcp write: broken pipe","level":"error","msg":"Couldn't write response"

on devnet 10.

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

No branches or pull requests

2 participants