-
Notifications
You must be signed in to change notification settings - Fork 381
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
dApp staking v3 - Cycle Alignment #1134
Conversation
/bench shibuya-dev pallet_inflation,pallet_dapp_staking_v3 |
Benchmarks job is scheduled at https://github.com/AstarNetwork/Astar/actions/runs/7527934157. |
Benchmarks have been finished. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
(I didn't thoroughly go though inflation migration logic)
Minimum allowed line rate is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Pull Request Summary
Related to: #1127
Even though the implementation in this PR is labeled as Less Proper Solution, it proved to be more proper than extracting the logic to a new pallet.
Two main reasons being:
For that reason, the following architecture is used:
pallet_dapp_staking_v3
has a newObservers
trait which it uses to notify observers about events of interestpallet_inflation
keeps track at which era should it trigger inflation recalculation, and relies on the notification from dApp staking pallet about era changesCheck list
force
should also inform observers