# dApp Staking - Too High Threshold Incident

**URL:** https://forum.astar.network/t/dapp-staking-too-high-threshold-incident/6902
**Category:** General
**Created:** [May 29, 2024, 12:34pm UTC](https://forum.astar.network/t/dapp-staking-too-high-threshold-incident/6902 "2024-05-29T12:34:47Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Dino](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@Dino](https://forum.astar.network/u/Dino)
#### Post date: [May 29, 2024, 12:34pm UTC](https://forum.astar.network/t/dapp-staking-too-high-threshold-incident/6902/1 "2024-05-29T12:34:47Z")

</div>

Hello everyone,

this is just a quick info sharing regarding the ongoing incident related to dApp staking’s tier thresholds.

## Impact

The issue doesn’t impact stakers, only dApps & developers.

As tier thresholds have increased beyond what was expected, some dApps have been pushed to lower tiers, even though for the current ASTR price they should have remained in the higher tier.

## Issue

The issue is with the formula used to calculate the threshold adjustment. The formula from the report & implemented in the code is _essentially_ correct, but it must account for the fact that thresholds saturate at some point (e.g. for Tier 1 it’s 200M ASTR). Docs [here](https://docs.astar.network/docs/learn/dapp-staking/dapp-staking-protocol/#tier-threshold-entry) cover this, and will be updated after next docs release with corrections.

The slightly adjusted formula will always consider price changes compared to the _base_ price using which the model in the report(s) was made. That way, we have a guarantee that regardless of the current thresholds and number of slots, the calculated thresholds will be as expected. But to avoid tech details, for those interested feel free to check the PR: [Base native currency price for dApp Staking by Dinonard · Pull Request #1252 · AstarNetwork/Astar · GitHub](https://github.com/AstarNetwork/Astar/pull/1252)

The problem wasn’t introduced in any recent updates, but was made visible after the _oracle_ integration since this caused tier configuration to be recalculated on a daily basis.

## Technical Fix

The fix has been made in the PR linked above, and will be deployed any time now. From the next era, thresholds will be back to values similar as before.

NOTE: If ASTR price goes further down, thresholds will continue to increase.

## Missed Reward Compensation

We realize that projects have missed on some rewards due to this bug.  
To remedy that, we’ll compensate them accordingly.

We’ll calculate what the tier assignments would have been if runtime was working correctly, and payout the reward difference to the projects.

The calculation will be done via script, which will simulate reward distribution _if correct runtime logic was used_. The script will be shared publicly.

We cannot specify exact dates yet, but it should be done in the next weeks, by the end of June.

---

_[View the full topic](https://forum.astar.network/t/dapp-staking-too-high-threshold-incident/6902)._
