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

Move InvalidExtrinsicsRootProof storage so it is easier to combine later #3312

Merged
merged 2 commits into from
Dec 12, 2024

Conversation

teor2345
Copy link
Member

@teor2345 teor2345 commented Dec 12, 2024

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:

@teor2345 teor2345 added the execution Subspace execution label Dec 12, 2024
@teor2345 teor2345 self-assigned this Dec 12, 2024
@teor2345 teor2345 enabled auto-merge December 12, 2024 05:18
Copy link
Member

@NingLin-P NingLin-P left a 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 {
Copy link
Member

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.

@teor2345 teor2345 added this pull request to the merge queue Dec 12, 2024
Merged via the queue into main with commit b51b689 Dec 12, 2024
8 checks passed
@teor2345 teor2345 deleted the move-extr-proof-data branch December 12, 2024 18:10
@teor2345 teor2345 added the host-function-change This PR introduce host function change, must test compatibility with existing network before release label Dec 19, 2024
@@ -262,6 +262,8 @@ where
domain_inherent_extrinsic_data: DomainInherentExtrinsicData,
) -> Option<DomainInherentExtrinsic> {
let DomainInherentExtrinsicData {
// Used by caller
block_randomness: _,
Copy link
Member Author

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

@teor2345 teor2345 added the breaking-runtime This PR introduces breaking changes to the runtime label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-runtime This PR introduces breaking changes to the runtime execution Subspace execution host-function-change This PR introduce host function change, must test compatibility with existing network before release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants