dApps Staking v3 - proposal

[Dino]

No problem! Just wanted to get discussion back on the topic

@you425

The Tier reward calculation may still be good, but if you are going to reconfigure the Tier configuration, it would be best to reset the voting as well. Otherwise, if the slots were to be reduced if they were filled, we would be talking about what to do with the dApp tiers (in which case, I think the solution would be to lower the tier of the dApps with the lowest number of votes in that tier).

That’s not a problem, I think. The whole idea of the system is to be competitive.
There’s not unlimited amount of slots, and numbers change depending on how ASTR price changes. So one era a dApp might be in tier 2, and in another it might be in tier 3. It’s up to stakers to support & dApp to attract support to stay in tier 2.

The system will work like this anyways, technically it’s all the same whether we reset the votes or not.

---

@you425

I now think the tier configuration thing is about the number of slots, tier thresholds, and amount of rewards. My apologies if I have misunderstood.

That’s exactly it!

---

@you425

This is why I am raising it. I don’t think that is much different than talking about how often the hierarchical structure should be recalculated.

It’s not, but it’s more related to tier config, not tier assignment.

At the end of each era, dApps are assigned into tiers. Tier config defines what are the number of slots, rewards & thresholds per tier.

Right now, this tier config is recalculated once per 4 months, or 122 eras as you noted. And that’s way too slow. Especially if we consider how ASTR price has moved in the last 4 months.

I’ll work on solution proposal for this very soon, but right now my thoughts are going towards:

• recalculate tier config daily (beginning of a new era)
• ASTR price should be averaged (rolling average) over some time period to smoothen out the price spikes.
  • that way we prevent drastic changes in slot numbers from era to era