-
Notifications
You must be signed in to change notification settings - Fork 247
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
Move InvalidExtrinsicsRootProof storage so it is easier to combine later #3312
Conversation
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.
Make sense to me, thanks!
@@ -414,16 +414,27 @@ impl MaybeDomainRuntimeUpgradedProof { | |||
} | |||
|
|||
#[derive(Clone, Debug, Decode, Encode, Eq, PartialEq, TypeInfo)] | |||
pub struct DomainInherentExtrinsicDataProof { | |||
pub struct InvalidExtrinsicsDataProof { |
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.
Non-blocker but it may be worth having Inherent
in the name, to distinguish it from the invalid extrinsic from the invalid bundle fraud proof.
@@ -262,6 +262,8 @@ where | |||
domain_inherent_extrinsic_data: DomainInherentExtrinsicData, | |||
) -> Option<DomainInherentExtrinsic> { | |||
let DomainInherentExtrinsicData { | |||
// Used by caller | |||
block_randomness: _, |
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.
This PR contains a host function change, which we are planning to revert in #3314
This PR is a refactor to prepare for combining storage in #3281. It moves all the storage that will be combined together, and moves out large storage that we won't combine.
In the next PR, I'll combine all the storage proofs in
InvalidExtrinsicsDataProof
into a single storage proof.Breaking changes:
Code contributor checklist: