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
In the current implementation, we index group votes. EventVote is emitted when a single voter has submitted their vote but the event only includes the proposal id. In order to then query the vote to index, we need to query all current votes by proposal id and then loop through the votes rather than querying the single vote by proposal id and voter address.
Possible Solutions
The voter address could be added to EventVote enabling us to query a specific vote (historical events would not be updated so this would only solve future votes).
We could extract the voter address from the transaction messages (this would solve historical events and future events but there is some complexity as to how we would do this to account for MsgVote being wrapped in other messages, i.e. gov and group proposal messages, authz authorization messages, and interchain transactions). See golang example here.
The text was updated successfully, but these errors were encountered:
Summary
In the current implementation, we index group votes.
EventVote
is emitted when a single voter has submitted their vote but the event only includes the proposal id. In order to then query the vote to index, we need to query all current votes by proposal id and then loop through the votes rather than querying the single vote by proposal id and voter address.Possible Solutions
EventVote
enabling us to query a specific vote (historical events would not be updated so this would only solve future votes).MsgVote
being wrapped in other messages, i.e. gov and group proposal messages, authz authorization messages, and interchain transactions). See golang example here.The text was updated successfully, but these errors were encountered: