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

Include RequestsHash in header encoding/decoding #301

Merged
merged 3 commits into from
Dec 20, 2024

Conversation

piersy
Copy link

@piersy piersy commented Dec 18, 2024

Updates header encoding/decoding

A new field 'RequestsHash' was added to the header, and we needed to run
go generate to regenerate the generated encoding/decoding. We also
needed to update celo_block.go to account for the new field.

Simplified the encoding and decoding in celo_block.go by simply casting
the header into the right type for encoding/decoding. This ensures that
we won't need to update celo_block.go in the future when fields are
added or removed.

These changes allowed us to unskip the tests that were skipped during the celo11 rebase.

Fixes https://github.com/celo-org/celo-blockchain-planning/issues/854

A new field 'RequestsHash' was added to the header, and we needed to run
go generate to regenerate the generated encoding/decoding and also update
celo_block.go to account for the new field.

Simplified the encoding and decoding in celo_block.go by simply casting
the header into the right type for encoding/decoding. This ensures that
we won't need to update celo_block.go in the future when fields are
added or removed.
@piersy piersy requested review from palango and Kourin1996 December 18, 2024 18:14
@piersy piersy requested a review from karlb December 20, 2024 10:09
@piersy piersy merged commit ba64a6c into celo11 Dec 20, 2024
7 checks passed
@piersy piersy deleted the piersy/add-requestshash-to-header branch December 20, 2024 14:57
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 this pull request may close these issues.

2 participants