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

Fails to decode blob sidecars from Prysm #129

Open
danyalprout opened this issue Apr 10, 2024 · 2 comments
Open

Fails to decode blob sidecars from Prysm #129

danyalprout opened this issue Apr 10, 2024 · 2 comments

Comments

@danyalprout
Copy link

Hi 👋

We use this library to fetch blobs from the beacon chain. We noticed that when using Prysm as the beacon node the SSZ decoding of blob sidecars fails (see issue).

The error is happening here, due to the response from Prysm having an extra four bytes at the start (it appears to be an offset to the first element).

I suspect this maybe a Prysm encoding bug, as the spec reads as if the offset isn't required when a response is just an array of ojects.

Just wanted to double check and see if you had any insight/any other reports of this. Thank you 🙏

@mcdee
Copy link
Contributor

mcdee commented Apr 28, 2024

It's possible that this library is the incorrect one, did you resolve the issue to know if providing the number of elements in the array (which I assume are the first four items in the data) is required?

@mcdee
Copy link
Contributor

mcdee commented Jun 10, 2024

After further investigation it appears that this is a prysm issue, as testing against lighthouse, nimbus and teku returns the same SSZ and it is prysm which is the odd one out. Did you raise an issue with them regarding this?

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

2 participants