What did you build?
Two additive features on the Explorer account pages, both built on existing infrastructure. No subgraph or indexer change, no new server code.
Delegators tab (#719, closes #106)
Adds a Delegators tab to the orchestrator account page listing every account that has delegated stake to that orchestrator. Each row shows Stake (subgraph bondedAmount) and Pending Rewards (live on-chain pendingStake − bondedAmount, via the existing /api/pending-stake endpoint), so a row’s total matches what that delegator sees on their own profile. Orchestrators can now reconcile their delegator set from the Explorer instead of querying the subgraph themselves; delegators can see the composition of the stake behind an orchestrator before delegating. Gated to orchestrator accounts, paginated, and it reuses the same per-cell fetch pattern already used for ENS data.
History event filter (#720, closes #511)
Adds a Filter popover to the account History tab covering 12 event categories (Delegated, Reward calls, Reward cut & fee changes, Winning tickets, Votes, and so on), with All/None shortcuts and an active-count badge. Filtering is display-only: paging stays filter-agnostic, so the filter changes what you see, never what is fetched. The infinite-scroll observer was also reworked to attach once on sentinel mount, so a short filtered list can no longer self-retrigger and crawl an account’s entire history.
Both PRs went through CodeRabbit review with the actionable comments addressed, and codegen / typecheck / eslint --max-warnings 0 / prettier are clean on both.
Why does it matter?
Both features surface data the protocol already emits but the Explorer didn’t expose. An orchestrator’s delegator base was only reachable by querying the subgraph directly or using a third-party tool, and the account History tab was a single undifferentiated feed. Fnding a specific vote, reward call, or cut change meant scrolling past everything else.
The beneficiaries are delegators doing due diligence before they stake (they can now see the stake composition behind an orchestrator, and filter its history down to whether it calls reward consistently, etc.), and orchestrators, who can see their own delegator base and each delegator’s pending rewards directly on their profile instead of reconstructing it from the subgraph.
Link to the work
Evidence of impact
The need was named by the maintainers #511 was opened by @ECWireless in January 2026 following the discussion in #115; #106 is a long-standing open request*; @Mehrdad grouped both into #711 and labelled them help wanted / retrospective compensation as bounty-suitable work.
Reach. The Delegators tab appears on every orchestrator profile. The active set alone is the top 100 orchestrators by stake, and every one of them has a delegator base that was previously invisible from the Explorer. The History filter applies to every account page on the Explorer, across 12 event categories.
Community proof points
Link to the Discord thread. Community review is requested
Amount requested
$500 USD-equivalent in LPT, covering both features. The compensation cap stated on umbrella issue #711.
— [Delegators] Governance & Observability. Two Explorer features on existing infra: 
— Reviewable, not yet merged. Both PRs open with live previews (