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
We don't need to do #1200, because we can instead submit a current proof for each note commitment, and check that the position was less than the proposal start block. This requires us to not forget commitments when any proposal is open for voting: eventually we want to have a table of delayed commitments to forget, and process their forgession as soon as a proposal is no longer in process of voting, but for now we can leak storage and postpone that clean-up to after the MVP for voting.
The text was updated successfully, but these errors were encountered:
We don't need to do #1200, because we can instead submit a current proof for each note commitment, and check that the position was less than the proposal start block. This requires us to not forget commitments when any proposal is open for voting: eventually we want to have a table of delayed commitments to forget, and process their forgession as soon as a proposal is no longer in process of voting, but for now we can leak storage and postpone that clean-up to after the MVP for voting.
The text was updated successfully, but these errors were encountered: