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
Currently, as per the spec, each proposal has 3 relevant timestamps
a creation time, corresponding to when it is submitted
a voting time, when voting starts, set on submission to begin some vote_delay time after the creation time
an expiration time, when it is concluded, set on submission to occur some expire_time time after the creation time
This is however a bit awkward because someone could submit their proposal with an expire_time smaller than their vote_delay, which would cause a proposal to expire before voting is allowed.
We have some choices on how to handle this:
check for expire_time to be smaller than vote_delay when the proposal is submitted, fail otherwise
make the expiration time start some expire_time time after the voting time
ignore this potential problem in the contract, have it be handled in the off-chain app instead
Acceptance criteria
A decision is taken and if necessary the specification and the smart contract are updated accordingly.
The text was updated successfully, but these errors were encountered:
Clarification and motivation
Currently, as per the spec, each proposal has 3 relevant timestamps
vote_delay
time after the creation timeexpire_time
time after the creation timeThis is however a bit awkward because someone could submit their proposal with an
expire_time
smaller than theirvote_delay
, which would cause a proposal to expire before voting is allowed.We have some choices on how to handle this:
expire_time
to be smaller thanvote_delay
when the proposal is submitted, fail otherwiseexpire_time
time after the voting timeAcceptance criteria
A decision is taken and if necessary the specification and the smart contract are updated accordingly.
The text was updated successfully, but these errors were encountered: