Explorer displays incorrect voting power before vote
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
### Describe the bug
When voting on a proposal with my Pixelfield orchestrator, the Explorer displayed my voting power as 69 LPT.
However, after submitting my vote, the vote percentage appeared to increase by approximately 0.4%, which would correspond to roughly 12,000 LPT based on the total voting power. This suggests the actual voting power used was different from what was displayed.
Rick suggested this may be a UI issue where the Explorer only displays the voting power directly associated with the wallet, while the vote counting also includes delegated stake attached to the orchestrator.
### To Reproduce
https://explorer.livepeer.org/voting/0x74479927117d4158b32c03d5400c14bdd7e6a46a
see voting power on right side
### Expected behavior
The voting power shown in the UI should reflect the total voting power that will actually be used for the vote (or clearly distinguish between wallet voting power and delegated/orchestrator voting power).
### Screenshots
_No response_
### Desktop OS
Windows
### Desktop Browser
Brave
### Desktop Wallet
_No response_
### Desktop App/Extension Version
_No response_
### Smartphone Device
_No response_
### Smartphone OS
_No response_
### Smartphone Browser
_No response_
### Smartphone Wallet
_No response_
### Smartphone App/Extension Version
_No response_
### Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the voting page linked in the issue and trace how the Explorer displays voting power before a vote versus how the submitted vote affects the percentage. Determine whether delegated stake attached to the orchestrator is included in voting. Done means the displayed value matches the power used for voting or clearly distinguishes wallet and delegated/orchestrator power.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100