Explorer Bounty Umbrella: Delegators View & History Event Filter

Decision: Approved

The Review Team approves the requested $500 in full, subject to both pull requests completing the normal merge process.

The contribution addresses two established Explorer needs: visibility into an orchestrator’s delegator base and practical filtering of account history. Both features are implemented as low-risk, read-only additions that reuse the Explorer’s existing subgraph, on-chain API, account layout, design system, and table infrastructure.

The implementation shows good attention to pagination, partial-load failures, accessibility, responsive behaviour, and consistency with established repository patterns. The requested amount is modest and proportionate to the scope and utility of the work.

Before payment, PR #719 should be rebased and its conflict with the shared table component resolved while preserving the newer table-state behaviour on main. The forced wrapping of the Delegators headers should also be reviewed so the header height matches existing Explorer tables.

PR #720 would benefit from a small accessibility refinement before merge. The All and None controls should use clearer action labels or a standard master “Select all” checkbox, retain visible keyboard focus, and provide adequate hit areas. The unchecked checkbox boundary should also use a stronger contrast against the popover background.

The remaining history-pagination and indexed-versus-live data-freshness limitations are suitable follow-up work and do not justify reducing the award.

Future Follow-Ups

  • Add a manual “Load more” action or clearer loaded-window wording when a History filter produces a short list. The current observer can stop requesting additional pages while older matching events still exist.
  • Add focused tests for filtered infinite scrolling and multi-page delegator failure recovery as future hardening. The absence of these tests is consistent with the repository’s currently limited component-test coverage and is not a blocker for approval.
  • Consider persisting History filters in URL parameters for sharable links with active filters.