✳️ dApp Staking Reset Mechanism

I can agree with you on many things.

Regarding progress reports, I think this should be done in the Portal, not in the Forum. If there are many active projects, discussions that should be in the Forum may drift away and become uncontrollable. Therefore, I propose that a section be added to each project page in the Portal to provide activity reports. This will also make it easier to see which projects to support from Portal.
Reporting should be done in the first week of each month and the dApps owner will leave a transaction with the report. If no reporting is done, the following penalties will be applied (automatically).

  • 1st stage: 33% cut in rewards
  • 2nd stage: 66% cut in rewards
  • 3rd stage: Delist

Even when a penalty has been incurred, a report can be made to restore the status to one of the previous stages.
It would be even better if the status of reporting and penalties could be easily understood by icons in the dApps list.

However, the drawback is that this would require a certain amount of development cost.

I disagree with you on this. Depending on the limit on the maximum number, it could be a burden on operations, as exchanges like Binance, for example, use dApp Staking. Also, the number of dApps that can be staked is limited to 16, which could also be a problem.

Interesting proposal, but may be difficult to justify; it might be interesting to do something like Curve’s Gauge ballot with a boost to the incentive in the form of a Subsquare voting.

T3 and T4 (especially T4) will only be a small part of the inflation and will not have a significant impact. I suggest adjusting the slots and increasing the amount of reward for T4. I’m posting the adjustments I proposed earlier here (they are still the same numbers as before, so please use them as a reference only).

I agree with you on this. It makes sense to support projects that are a public good with dApp Staking.

3 Likes