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
At the moment Jetton Lock contract always prolong lock expiration date by constant value of 30 days on proposal voting.
This creates conditions in which every Proposal voting limited by 30 days. If we want to create proposal with voting duration of (for example) 3 month we have to change lock duration to that value for every(!) proposal, we have to change global constant value.
It obliges DAO participant to lock their tokens to 3 month even if they didn't want to participate so long votings.
I suggest to use dynamic lock period and dynamic proposal voting period. It will allow to create proposals with any duration. But it imposes limit to participants who want to vote in this proposal. Proposal should check lock duration before accept participant vote.
The text was updated successfully, but these errors were encountered:
At the moment
Jetton Lock
contract always prolong lock expiration date by constant value of 30 days on proposal voting.This creates conditions in which every Proposal voting limited by 30 days. If we want to create proposal with voting duration of (for example) 3 month we have to change lock duration to that value for every(!) proposal, we have to change global constant value.
It obliges DAO participant to lock their tokens to 3 month even if they didn't want to participate so long votings.
I suggest to use dynamic lock period and dynamic proposal voting period. It will allow to create proposals with any duration. But it imposes limit to participants who want to vote in this proposal. Proposal should check lock duration before accept participant vote.
The text was updated successfully, but these errors were encountered: