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 cosmos-sdk 0.47, they removed telemetry for counting votes and proposals. It was incorrectly counting votes. They suggest using alternatives, such as state streaming. cosmos/cosmos-sdk#17910
We have some scripts that rely on counting proposals which need to be upgraded.
Description of the Design
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered:
@mhofman I've been asked to drive this, but could you please give me a pointer to the scripts you're concerned about?
I don't specifically remember right now, but when auditing code which relied on query proposal, I noticed some surrounding code which relied on proposal count to guess the next proposal number. I think you can grep for proposal_id across our repos to find most location which may be involved with proposal querying. Looking for variants of gov proposal[s] might also lead you there.
What is the Problem Being Solved?
In cosmos-sdk 0.47, they removed telemetry for counting votes and proposals. It was incorrectly counting votes. They suggest using alternatives, such as state streaming. cosmos/cosmos-sdk#17910
We have some scripts that rely on counting proposals which need to be upgraded.
Description of the Design
Security Considerations
Scaling Considerations
Test Plan
Upgrade Considerations
The text was updated successfully, but these errors were encountered: