chore(sequencer)!: put blocks and deposits to non-verified storage (ENG-812) #1525
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.
Summary
This changes where sequencer blocks and the
TracePrefixed
native asset are stored, and also persistsDeposit
s to non-verifiable storage.Background
Sequencer blocks are currently written to verified storage, which is unnecessary as all of their constituent data is already available there.
We want to avoid the cost of storing full blocks in verified storage, but still have the ability to provide a third party with a full block if requested. To further assist with this, deposits will also be written to non-verified storage.
It also seemed appropriate to store the
TracePrefixed
native asset in verified storage, since this is something which all validators should reach consensus over.Changes
SequencerBlock
s are now stored in non-verifiable storage.Deposit
s are now stored in non-verifiable storage.Testing
Existing unit tests have been updated as required to assert these changes.
Breaking Changelist
Related Issues
Closes #1493.