-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fault_proving(compression): include commitment to registry in compressed block header #2571
Conversation
6e6e82d
to
2594aa0
Compare
b41ff8a
to
aceba71
Compare
} | ||
}}; | ||
} | ||
|
||
// Don't change the order of these, it will affect the order of hashing |
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.
created: FuelLabs/fuel-specs#623
aceba71
to
4d998ae
Compare
4d998ae
to
4ca0445
Compare
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.
Are you sure RegistrationsPerTable contains the entire registry? I was under the impression that this is only the new registrations introduced by the block, and we need to commit to the entire registry here.
In either case, it would be great if we could add a test which compresses a few subsequent blocks and verifies the compression registry ID.
why do we have to commit to the whole registry? |
Your impression is correct |
needs to be reworked. closing for now |
Linked Issues/PRs
Description
We implement a function
id
forRegistrationsPerTable
which yields aRegistryId
that is included within theCompressedBlockHeader
Checklist
Before requesting review
After merging, notify other teams
[Add or remove entries as needed]