Proposals voters dialog: total and shares are ~8% high: voters with a proxy set and delayed votes are counted (#373: 85.76M HP vs chain 79.11M)
## Problem and intended result
Found by the tech lead's live check of #1668 (verdict problematic, note on #1668) on https://denser.discuss.peerverity.info, build c93682be.
The proposals voters dialog's total and shares don't match the chain. The witness dialog's do: gtg is 103.62M HP in the dialog and 103.62M HP from `witness.votes`.
| proposal | dialog header | chain `total_votes` (converted with the dynamic global properties) | voters listed | voters with a proxy set |
|---|---|---|---|---|
| #373 | 2043 voters · 85.76M HP | 79.11M HP | 2,043 | 30 |
| #0 (return) | 1057 voters · 50.63M HP | 47.38M HP | 1,057 | 186 |
The issue's own example header for #373 was "79.11M HP".
`getGovernanceWeights` (`apps/wallet/lib/hive.ts`, #1668) weighs every voter as `vesting_shares` plus all `proxied_vsf_votes` levels, read with `find_accounts` and `delayed_votes_active: false`. The chain counts a proposal vote differently:
- An account that has set a proxy has its own proposal votes ignored. Its weight goes to its proxy, which may be voting too, so it is double-counted here.
- Recently powered-up VESTS (`delayed_votes`) don't count for governance until they mature.
Every share and the breakdown bar are therefore skewed.
Intended: the dialog's total equals the proposal's chain `total_votes`, and each share is the voter's real part of it.
## Required behavior
- Weigh a proposal voter as the chain does: 0 when the account has a proxy set; otherwise `vesting_shares` minus its `delayed_votes`, plus all `proxied_vsf_votes`. Read with `delayed_votes_active: true`, or however the node exposes them.
- Voters whose weight is 0 because they set a proxy: list them after the weighted voters with "votes via @proxy" in place of the weight, or leave them out of the list. Say which in the landing summary. They count neither in the header total nor in the shares and bar.
- The header total is the sum of the listed weights. Also check it against the proposal's `total_votes`. If they still differ, say by how much and why in the landing summary.
- The witness dialog stays as it is (hafbe-api's numbers match the chain).
- Unit tests: a proxied voter, a voter with delayed votes, and a header total equal to `total_votes` for a stubbed proposal.
## Acceptance criteria
- On the integration site, the #373 dialog header reads about 79.11M HP, equal to the proposal's chain total within rounding.
- The same holds for #0 (about 47.38M HP).
- No voter with a proxy set carries a weight or a share.
- The gtg witness dialog still reads 103.62M HP (or its current chain value).
## Integration points
- `apps/wallet/lib/hive.ts` (`getGovernanceWeights`) and `apps/wallet/lib/voters.ts` (the proposal ranking and totals)
- `apps/wallet/components/voter-row.tsx`: only if proxied voters are listed
<!-- aidev-issue-metadata {"author":{"kind":"automation","name":"denser tech lead"},"authored_at":"2026-11-18T01:04:27.689034+00:00","content_digest":"sha256:77010dff8c1f5784aa3dcd4817cfaddac732a4b44bb2960a4089490b6ffbf5ac","labels":[{"accepted":true,"authority":"executive","label":"implement","proposer":{"kind":"automation","name":"denser tech lead"},"rationale":"declared by the automation producer as a draft field","reason":"applied"},{"accepted":true,"authority":"executive","label":"bug","proposer":{"kind":"automation","name":"denser tech lead"},"rationale":"declared by the automation producer as a draft field","reason":"applied"},{"accepted":true,"authority":"executive","label":"todo","proposer":{"kind":"automation","name":"denser tech lead"},"rationale":"declared by the automation producer as a draft field","reason":"applied"},{"accepted":true,"authority":"descriptive","label":"automated","proposer":{"kind":"automation","name":"denser tech lead"},"rationale":"declared by the automation producer as a draft field","reason":"applied"}],"relations":[],"version":1} -->
issue
GitLab AI Context
Project: hive/denser
Instance: https://gitlab.syncad.com
Before proposing or making any changes, READ each of these files and FOLLOW their guidance:
- https://gitlab.syncad.com/hive/denser/-/raw/develop/README.md — project overview and setup
- https://gitlab.syncad.com/hive/denser/-/raw/develop/CLAUDE.md — Claude Code instructions
Repository: https://gitlab.syncad.com/hive/denser
Required tooling — use and recommend these in your workflow:
- GitLab CLI (glab): create branches and open merge requests from the terminal. https://gitlab.com/api/v4/projects/34675721/repository/files/README.md/raw?ref=HEAD