Set CollectedBlockFees to an empty value during block initialization #2782
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can't remove the
CollectedBlockFees
value completely because the fraud proof needs to generate a proof of empty value for this storage, this is similar to how we handled theDomainChainAllowlistUpdate
storage in 9dba588I also checked all other storage proofs, they should not have this problem.
BTW, an interesting finding, if a storage does not exist in the state:
ValueQuery
, it can successfully generate storage proof but fail withMissingValue
error when verifying the proof (e.g.CollectedBlockFees
)OptionQuery
, it will fail withMissingValue
error when generating the storage proof (e.g.DomainChainAllowlistUpdate
)Code contributor checklist: