You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice that if GRACE_PERIOD changes (e.g. by upgrading the timelock), a proposal can move from the Expired state back to the Queued state. This might have the undesirable effect of a proposal the DAO thought would not be executed, being executed unexpectedly.
A straightforward solution would be to capture a proposal's expiration timestamp when it is queued, similar to how a proposal's ETA (when it can be executed) is captured.
The text was updated successfully, but these errors were encountered:
Based on an issue found by C4 as part of the DAO V3 audit: code-423n4/2023-07-nounsdao-findings#55.
In this part of the proposal state function:
Notice that if
GRACE_PERIOD
changes (e.g. by upgrading the timelock), a proposal can move from the Expired state back to the Queued state. This might have the undesirable effect of a proposal the DAO thought would not be executed, being executed unexpectedly.A straightforward solution would be to capture a proposal's expiration timestamp when it is queued, similar to how a proposal's ETA (when it can be executed) is captured.
The text was updated successfully, but these errors were encountered: