The RAACMinter::emergencyShutdown() function sets emission rate to 0 without a way to restore it, making it impossible to resume normal protocol operations after an emergency shutdown.
In RAACMinter::emergencyShutdown(), the emission rate is set to 0:
The issue is that once set to 0, there is no direct way to restore the emission rate. The only function that can modify emission rate is updateEmissionRate(), but this function calculates adjustments based on the current rate:
Since adjustments are calculated as percentages of the current rate, when the rate is 0, all adjustments will also be 0.
Protocol cannot resume normal operations after emergency shutdown
Permanent loss of emission functionality unless contract is redeployed
Admin calls emergencyShutdown() setting emission rate to 0
Later tries to resume operations by calling unpause()
updateEmissionRate() is called but cannot increase rate from 0
tick() function mints 0 tokens (emissionRate * blocksSinceLastUpdate = 0)
1) Add a recovery function to restore emission rate:
2) Store the pre-shutdown emission rate:
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.