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

Set CollectedBlockFees to an empty value during block initialization #2782

Merged
merged 1 commit into from
May 28, 2024

Conversation

NingLin-P
Copy link
Member

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 the DomainChainAllowlistUpdate storage in 9dba588

I 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:

  • With ValueQuery, it can successfully generate storage proof but fail with MissingValue error when verifying the proof (e.g. CollectedBlockFees)
  • With OptionQuery, it will fail with MissingValue error when generating the storage proof (e.g. DomainChainAllowlistUpdate)

Code contributor checklist:

We can't remove the value completely because the fraud proof need to generate a proof
of empty value for this storage

Signed-off-by: linning <linningde25@gmail.com>
@NingLin-P NingLin-P added this pull request to the merge queue May 28, 2024
Merged via the queue into main with commit d3096b8 May 28, 2024
9 checks passed
@NingLin-P NingLin-P deleted the block-fees-fp branch May 28, 2024 10:23
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.

None yet

2 participants