-
Notifications
You must be signed in to change notification settings - Fork 42
NTTP Suggestion: Cycle TX management #31
Comments
support 2nd |
I agree on both changes. |
3 months seems an absolute minimum for me, maybe too short. It depends on the vote, but we can see some users don't follow very closely and can check only from time to time (like, 2 times a year). |
Definitely agree, current system is wasteful and strides against Nyzo ethos. I think we need both rules, since 50% NO may never be reached and CTX could remain wasting block space indefinitely, hence we need a timeout as well. 1-3 months sounds like an appropriate time limit. |
I feel like not enough people will do the no-voting. Definitely need for a timeout. I'd say 3 months. Shorter could hinder the voting process. If a tx is open longer than 3 months, I think it will most likely never pass + a new tx can always be created anyway. |
In the current working, once a cycle tx is issued, it remains active until
Some cycle tx, or spammy cycle tx can therefore remain indefinitely active, with many YES and NO votes, or just NO votes.
They occupy blocks space and will not clear.
I suggest 2 possible changes to the cycle TX cycle of life:
The text was updated successfully, but these errors were encountered: