Proposals: 2 const. proposal with manual trigger period has visibility issues about voting period + execution timeline

[mochet]

Problem

Link to proposal: https://pioneerapp.xyz/#/proposals/preview/787

• The time left seems to be indicating how long until the grace period would start supposing that it is actually approved
• Typically the time left is used to indicate how long the current council has to vote on the proposal, this could be misleading and make the current council believe they have ~12 days left to vote when it is ~6 days

[thesan]

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:

• Deciding stage: "Time left to vote"
• Dormant stage: "Time until deciding stage"
• Gracing stage: "Time until execution"

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.

[mochet]

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.

[thesan]

@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 ?