feat: replace sequence and confirmBy with hostBlockNumber #48
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.
Linear ticket
Motivation
The node will mine one RU block per host block.
Solution
As such, we can remove the
sequence
number (that tracks the rollup block number and ensures blocks are mined in correct order) and theconfirmBy
field (that ensures blocks are mined by a certain time).We can replace these fields with a
hostBlockNumber
field (that ensures that the rollup block is mined in the exact specified host block, encapsulating block ordering, block numbers, and expiration times within one field).As a convenience, we will also store the
deployBlockNumber
- the host block number at which the contract was deployed. Rollup block numbers can be derived from this value.