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
Somewhat similar to #2828, we don't currently get enough information in the API to display coherent information about the success or failure of an auction.
What we have now
{
proposals {
party { id }
iddatetimestateyesVotes { value }
noVotes { value }
rejectionReason
}
}
So we can infer that this one passed because there's more yes votes than no votes. But after #2997 when the calculation is fixed, there may be more YES votes than NO votes but it might be rejected.
What we need
Extra fields on each vote
By adding two extra fields on the VOTE, we can see what effect each vote has on the proposal. The downside is this would need to be updated with each transfer, so the half-arsed solution is to split this in to two types: OpenVote and AcceptedVote, and only track these fields on AcceptedVote after the proposal voting period closes.
Somewhat similar to #2828, we don't currently get enough information in the API to display coherent information about the success or failure of an auction.
What we have now
So we can infer that this one passed because there's more yes votes than no votes. But after #2997 when the calculation is fixed, there may be more YES votes than NO votes but it might be rejected.
What we need
Extra fields on each vote
By adding two extra fields on the VOTE, we can see what effect each vote has on the proposal. The downside is this would need to be updated with each transfer, so the half-arsed solution is to split this in to two types:
OpenVote
andAcceptedVote
, and only track these fields onAcceptedVote
after the proposal voting period closes.Current VOTE object
Proposed VOTE object
Extra fields on each proposal
This replaces #2828, as having a simple tally would not give us sufficient detail
Current PROPOSAL object
Proposed PROPOSAL object
The text was updated successfully, but these errors were encountered: