-
Notifications
You must be signed in to change notification settings - Fork 1.1k
SSZ support for submitAttestationsV2 #15422
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
Conversation
} | ||
i := 0 | ||
for len(body) > 0 { | ||
sszLen := 1 + int(body[0]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why isn't this sszLen := (ð.Attestation{}).SizeSSZ()
like in the Electra case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because if I recall correctly, the ssz payload for an Attestation
is 1 byte that specifies the length of the rest of the payload, and then the payload itself, and then the same for the next attestation
Ignore this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for clarification: the reason was that since AggregationBits
in Attestation
is variable length, the length of the Attestation
object will be added as the first byte, per SSZ spec.
Co-authored-by: Radosław Kapka <[email protected]>
This reverts commit 9927cea.
What type of PR is this?
Feature
What does this PR do? Why is it needed?
This PR adds SSZ support for the
submitPoolAttestationsV2
beacon API.Which issues(s) does this PR fix?
Per this PR