Runtime 1300:
This update introduces two new extrinsics for the dAppStaking pallet:
move_stake
: This feature allows users to reallocate their staked voting bonuses among dApps while keeping the bonus reward. The maximum number of moves is configurable via the MaxBonusMovesPerPeriod parameter, which is set to 2.set_static_tier_params
: This feature allows for the dynamic modification of tier-related dApp staking parameters and requires Root privileges.Additionally, this update includes fixes for the dAppStaking protocol:
This update also fixes the fee calculation via the xcmPaymentApi and removes unused calls and types from the pallet-treasury. These calls were incorrectly used in governance and have been removed since they were non-functional.
Runtime 1301: Fixes a SingularStakingInfo invariant in the dAppStaking protocol:
previous_staked
value now only retains information from previous eras, preventing future stakes from affecting past operations.
The proposal has been fast-tracked into a referendum.
Voting duration is 5 and half days, while enactment period is half a day.
The reason for the shortened periods duration is to ensure upgrade is applied before next
Build&Earn
subperiod in dApp staking begins. This is necessary to properly enablemove_stake
functionality` for stakers.