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
Currently we index the DAO proposals the same way as the 'other' proposals and rfps. We get the contract state on the blockheight of the receipt from the RPC for every transaction. A problem presented itself when indexing the sputnik contract in this way. When an DAO member votes to remove the proposal it gets deleted from contract and the RPC returns an contract panic ERROR_NO_PROPOSAL.
User Story
As a user I would like to view which proposals have been voted to be removed.
Acceptance Criteria
The number of indexed proposals should be the same as the number that gets returned by the get_last_proposal_id. Ensuring that even the deleted proposals are indexed.
Resources & Additional Notes
No response
Priority
🟢 P3 : Normal
The text was updated successfully, but these errors were encountered:
Background
Currently we index the DAO proposals the same way as the 'other' proposals and rfps. We get the contract state on the blockheight of the receipt from the RPC for every transaction. A problem presented itself when indexing the sputnik contract in this way. When an DAO member votes to remove the proposal it gets deleted from contract and the RPC returns an contract panic
ERROR_NO_PROPOSAL
.User Story
As a user I would like to view which proposals have been voted to be removed.
Acceptance Criteria
The number of indexed proposals should be the same as the number that gets returned by the
get_last_proposal_id
. Ensuring that even the deleted proposals are indexed.Resources & Additional Notes
No response
Priority
🟢 P3 : Normal
The text was updated successfully, but these errors were encountered: