🔧 CuteHive Proposal Voters Logic Upgrade: Fixing Voting Discrepancy

[cutehive.com]

While using CuteHive to browse proposal data, I recently noticed a significant issue — a major discrepancy between the total voting weight of a specific proposal and the calculated result from its voters list.

This prompted a deeper investigation, which ultimately led to identifying a critical logic flaw.

🧩 The Issue: Inconsistent Voting Weight

CuteHive provides a very useful feature:

👉 View voters of a proposal, sorted by voting weight, along with a calculated total.

In theory:

The total voting weight shown in the proposal list ≈ the sum calculated from the voters list

However, in practice:

• The difference was massive ❗
• This seriously affected the accuracy of evaluating proposal support

🔍 Root Cause: Ignoring the Proxy Mechanism

After further analysis, the issue turned out to be related to a core feature of the Hive blockchain — proxy voting.

In Hive:

• If a user sets a proxy
• Their governance voting power is delegated to that proxy account
• Their own direct votes no longer count

⚠️ However, in previous versions of CuteHive:

• ❌ Proxy status was not checked
• ❌ Voting weight from proxied users was still included
• 👉 This led to significantly inflated and inaccurate totals

🛠️ The Fix: Rebuilding Proposal Voters Logic

I have updated the calculation logic to align with Hive’s on-chain governance rules.

✅ Key Changes

1. Logic Update (ProposalList.tsx)

• Added a check for the proxy field
• Applied the rule:

  If a voter has a proxy set, their voting weight (HP) is counted as 0

2. Type Definition Update (types.ts & ProposalVotersModal.tsx)

• Added an optional proxy field to the VoterData interface:

  proxy?: string;

3. UI Feedback Enhancement (ProposalVotersModal.tsx)

For invalid votes caused by proxy settings:

• An orange warning is displayed under the username:

  Proxied to @username (Vote Ignored)

• These accounts are automatically sorted to the bottom (HP = 0)

🎯 Result

The updated Proposal Voters list now:

✅ Accurately reflects real, effective voting weight
✅ Clearly distinguishes between:

• ✔️ Direct support (valid votes)
• ⚠️ Ignored votes (proxied users)

✅ Improves transparency and trust in proposal analysis

---

🚀 Version Update

This fix has been released:

• 📦 Version: 3.3.63
• 🔗 Link: https://www.cutehive.com/proposals
• 💡 If you're using CuteHive, feel free to try the new version and share your feedback 🙌

Comments

[stresskiller]

to bad that https://www.cutehive.com/witnesses is only showing the top 100, that way people will never be able to find new started witness servers 😎 ok just noticed in settings that you can change it to max 200 , but looking at my backup witness as an example located down at 236 / 145 position imagine people start a new witness no one is able to find it :)

[cutehive.com]

Limiting the number of witnesses in the list is intended to avoid wasting API node resources.

In the next update, I will increase the selectable number to 300.

However, I think for a new witness node, the most important thing is to quickly accumulate around 30K HP in votes—then it can enter the top 200. 😀

[stresskiller]

yes it is but these days also very hard to find those 30k , since a lot of people don't even use their witness votes , or are still voting for inactive witnesses.

[cutehive.com]

You can also use the search function to look up a specific witness. 😀

[stresskiller]

that is good to know

[hivebuzz]

Congratulations @cutehive.com! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You got more than 100 replies. Your next target is to reach 200 replies.

_{You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP}