-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposals: 2 const. proposal with manual trigger period has visibility issues about voting period + execution timeline #4773
Comments
I agree this is misleading. Ultimately this should be solved by some greatly improved design as suggested in #4269. In the meantime "Time left" should indicate clearly what it's about. IMO this should be different for every stage:
In addition during the Deciding and Dormant stages I think that proposal without an exact execution block should have an additional statistic showing the earliest possible execution and the latest possible execution. |
I think also that any proposal that utilizes the trigger block should show this in Pioneer. It currently doesn't seem to do this and may lead to situations where the council votes on things without realizing this. |
@mochet I'm not sure if it's what you mean, but there is a statistic that shows that the proposal has an exact execution block: Also could you clarify what would be a harmful consequence of a council voting on a proposal with a trigger without realizing it ? |
Problem
Link to proposal: https://pioneerapp.xyz/#/proposals/preview/787
The text was updated successfully, but these errors were encountered: