Remaining RPC Usage Improvements Blocked on Subgraph Coverage
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
Context
After migrating core Explorer data fetching from RPCs to The Graph subgraph in https://github.com/livepeer/explorer/issues/327#issuecomment-3648650190, a small number of Explorer endpoints still rely on RPC calls due to missing or incomplete subgraph coverage identified during that work.
Goal
Track the Explorer-side dependency on upstream subgraph changes required to fully remove remaining RPC usage. Once the flagged subgraph improvements are implemented, the Explorer can complete the RPC → subgraph migration, improving performance, reliability, and maintainability.
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 with the migration context in issue #327 and the upstream subgraph work in livepeer/subgraph#182. Identify which Explorer endpoints still use RPCs and match them to the missing subgraph coverage. Done means the upstream changes are available and the remaining Explorer RPC usage has been replaced and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100