In the execute A proposal is executed in two steps, it should be in a succeded state to be queued and then queued to be executed, However A proposal that was that was successfully queued in the timelock can become defeated due to lost quorum, requiring it to be re-queued with a new timelock delay. This creates an inefficient loop where a proposal could continuously need to be re-queued if quorum fluctuates.
The proposal execution flow:
What can happen:
Proposal reaches Succeeded state and is queued
During timelock delay, quorum drops
State becomes Defeated due to lost quorum
When trying to execute after timelock, it reverts
If quorum is regained, state goes back to Succeeded
Must be queued again with new timelock delay
This cycle can repeat indefinitely
Medium. This creates potential indefinite delays in proposal execution
Consider modifying the state function to respect timelock queuing:
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.