Hello everyone,
We have an important update coming regarding dApp Staking and tier thresholds (probably in the next runtime upgrade). This new feature dynamically adjusts tier threshold based on total issuance percentages. Given the recent burn event, which reduced total issuance, this change is particularly relevant and timely.
Context - Recent Burn Event
Due to a recent burn event, the total issuance of our native token has decreased. Here is an example of the change introduced by this feature:
- Old T1 Threshold: Suppose the old harcaoded threshold for tier 1 was 300,000 ASTR tokens.
- Burn Event: The burn event has reduced the total issuance by 5%.
- New T1 Threshold: The new threshold for the same tier might adjust to 285,000 ASTR tokens, reflecting the reduced total supply.
Impact
This feature impacts dApp developers and projects by potentially altering their tier classifications based on the dynamic thresholds. This does not impact stakers directly.
Feature Explanation
Tier threshold parameters are now configured as percentages of the total issuance at the moment dApp Staking V3 launched. This means that as the total issuance of the $ASTR native token fluctuates, so do the threshold amounts for entering different tiers. The recalculation mechanism is still triggered at each new era; this is unchanged, as well as the number of slots adjustment. However, the formula no longer uses hardcoded tier thresholds, which provides a fairer and more adaptive staking environment.
The technical implementation is introduced in this pull request #1306.
Percentage parameters
Here are the percentages used for each network (Astar/Shiden) based on total issuance at the moment dApp Staking V3 launched:
And here are the expected new thresholds at the moment of writing (these may change slightly in the upcoming days due to market conditions):
Any questions are warmly welcomed. Our goal is to continually improve the staking experience for all builders and users on our platform.
Thank you,
Igor