Skip to content

Extend Voting Transparency to Governance page #482

@ECWireless

Description

@ECWireless

Is your feature request related to a problem?

Voting Transparency (#310) shipped in #457, but only on the Account/Orchestrator and Treasury pages. The Governance page (LIP polls) still has no equivalent — you can't see how each orchestrator voted on a poll or their voting power. See #310 (comment).

Describe the solution you'd like

Bring the same Voting Transparency to the Yes/No governance poll votes, reusing the mechanism from #457 and keeping the Governance page consistent with the Treasury/voting pages where possible (DRY, best engineering practices).

Describe alternatives you've considered

No response

Additional context

Retroactive Grant Notice

Important

Compensation cap: $500

Before picking this up, read the Retroactive Grants post in full. Key points:

  • Not pay-for-delivery. Compensation is based on demonstrated adoption and community impact — not on shipping. Real, named community contributors must use your work and publicly attest to it. Building in isolation, then asking for a grant, does not qualify.
  • Talk to the community first. A public discussion (Discord or Forum) about the problem must precede the work, and evidence of it must be part of your application. No prior discussion, no tempcheck, no public signal = won't pass review.

Required steps before investing more time:

  1. Read the original Retroactive Grants post in full.
  2. Start a public discussion (Discord or Forum). Get input. Confirm direction.
  3. Secure at least one community proof point — a Discord thread with positive signal, a Review Team acknowledgement, or evidence of active adoption.
  4. Identify, by name, who has this problem.
  5. Build, ship, and confirm it's actually being used.
  6. Apply with at least one named community contributor willing to publicly attest to your work's impact on the forum post.

Skipping steps 2, 3, 4, or 6 will halt the application. Reach out to jj.a.ss.o.nn_everestnode on Discord before you start building.

Edited @rickstaa on 20-05-2026 to suggest as retroactive bounty opportunity.

Metadata

Metadata

Assignees

Labels

help wantedExtra attention is neededretrospective compensationAssigned issues eligible for retroactive funding only.
No fields configured for Feature.

Projects

Status
In Progress

Relationships

None yet

Development

No branches or pull requests

Issue actions