You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can put ending timestamp inside store keys to mitigate this problem.
When queuing staking, the end time is set to current blocktime + time.Duration(params.NextEpochDays), and queued staking will be processed at the end time, not when the epoch increases.
Tasks
Fix QueuedStaking logics
Fix relevant test cases
Add migration.go, legacy code
bump ConsensusVersion of farming to 2 from 1
Update Spec, docs, cli help
The text was updated successfully, but these errors were encountered:
We can put ending timestamp inside store keys to mitigate this problem.
When queuing staking, the end time is set to current blocktime +
time.Duration(params.NextEpochDays)
, and queued staking will be processed at the end time, not when the epoch increases.Tasks
ConsensusVersion
of farming to 2 from 1The text was updated successfully, but these errors were encountered: