IntersectMBO / IntersectMBO/govtool
💡 Update SPO vote counting for Protocol Version 10
- Dominant language
- HTML
- Stars
- 21
- Forks
- 29
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
Description
### Area
Voting Pillar
### Is there new design needed?
Yes
### What?
- There was a change introduced to CIP1694 around how SPO vote totals are calculated https://github.com/cardano-foundation/CIPs/pull/916
- GovTool's SPO vote totals should reflect this
- This change will take effect post Plomin hardfork
### Why?
- Changing how GovTool totals this will ensure that values shown to users are correct
### How?
Change the calculation to match the change
### (Optional) User Story with acceptance criteria
_No response_
Contributor guide
Research direction
Start by reading the referenced CIP-1694 pull request 916 to understand the revised SPO vote-total rules, then locate GovTool's existing SPO vote calculation. Done means the displayed totals match the new rules and apply after the Plomin hardfork.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100