feat!: change timepoint interpretation #897
Merged
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.
The PR brings two major changes:
The interpretation of both the block timepoint change from occurance block timestamp to future finalized timestamp, as well the global state last finalized timepoint change from last finalized timestamp to current timestamp.
You can see the differences via diff:
Note that
WithdrawalLockArgs.withdrawal_block_timepoint
,CustodianLockArgs.deposit_block_timepoint
andStakeLockArgs.stake_block_timepoint
is also block timepoint.Check v2 withdrawal cell finality based on input since.
Without replying
GlobalState
, or say rollup_state_cell, we still can check a v2 withdrawal cell finality based on input since, so that avoid celldep-race issue.Proposal for further changes:
Timepoint::BlockNumber
toTimepoint::Lagecy
,Timepoint::Timestamp
toTimepoint::New
GlobalState.lats_finalized_timepoint
,WithdrawalLockArgs.withdrawal_block_timepoint
,CustodianLockArgs.deposit_block_timepoint
andStakeLockArgs.stake_block_timepoint
.This PR will not make these changes, since I am having some problems bumping gw-types in the "develop" branch.