Migrate core data fetching from RPCs to The Graph subgraph #327

Activity

1. ECWireless

   added this to the Explorer Maintenance - Milestone 1 milestone on Oct 21, 2025
2. ECWireless

   added the

   Feature

   issue type on Oct 21, 2025
3. ECWireless

   moved this to Todo in Explorer Revampon Oct 21, 2025
4. ECWireless

   added this to Explorer Revampon Oct 21, 2025
5. ECWireless

   self-assigned this

   on Oct 22, 2025
6. ECWireless

   modified the milestones: Explorer Maintenance - Milestone 1, Explorer Maintenance - Milestone 2 on Nov 3, 2025
7. ECWireless

   moved this from Todo to Backlog in Explorer Revampon Nov 3, 2025
8. ECWireless

   moved this from Backlog to Todo in Explorer Revampon Nov 11, 2025
9. ECWireless

   moved this from Todo to In Progress in Explorer Revampon Dec 11, 2025
10. ECWireless commented on Dec 13, 2025

    

    ECWireless

    on Dec 13, 2025

    Last edited by ECWireless

    CollaboratorAuthor

    More actions

    Best Candidates for RPC -> The Graph

    @rickstaa

    New AddressBook Entity Type

    • For core contract addresses
    • These contracts:

    LivepeerTokenFaucet
    BondingManager
    RoundsManager
    Minter
    MerkleSnapshot
    ServiceRegistry
    TicketBroker
    LivepeerGovernor
    Treasury
    BondingVotes
    

    • Honestly, not a priority. But would mean slightly less RPC calls

    Pending Stake and Fees

    • pendingStake
    • pendingFees
    • Could probably be added to the Delegator entity type

    More Treasury Data

    api/treasury/proposal/[proposalId]/state.tsx

    • clock -> What does this number refer to?
    • proposalSnapshot -> What does this number refer to?
    • getPastTotalSupply -> What does this number refer to?
    • proposalVotes -> part of feat(treasury): index governor votes and tallies subgraph#175
    • state -> What does this number refer to?
    • quorum -> Unsure where to get this
    • quota -> Unsure where to get this

    api/treasury/proposal/[proposalId]/votes.tsx

    • clock -> What does this number refer to?
    • proposalSnapshot -> What does this number refer to?
    • getVotes -> Likely can't get this from subgraph
    • getPastVotes -> Part of feat(treasury): index governor votes and tallies subgraph#175
    • hasVoted -> Part of feat(treasury): index governor votes and tallies subgraph#175
    • delegatedAt -> https://github.com/livepeer/subgraph/blob/main/schema.graphql#L189

    api/treasury/votes/[address].tsx

    • proposalThreshold -> What does this number refer to?
    • getPastVotes -> Part of feat(treasury): index governor votes and tallies subgraph#175
    • delegates -> Likely https://github.com/livepeer/subgraph/blob/main/schema.graphql#L189

    api/treasury/votes/[address]/registered.tsx

    • getDelegator -> https://github.com/livepeer/subgraph/blob/main/schema.graphql#L189 and https://github.com/livepeer/subgraph/blob/main/schema.graphql#L205
    • hasCheckpoint -> Not positive, but believe it's this: https://github.com/livepeer/subgraph/blob/main/schema.graphql#L104
11. ECWireless

    linked a pull request that will close this issuefeat: remove L2 RPC from all but treasury calls #444on Dec 15, 2025
12. ECWireless

    moved this from In Progress to In Review in Explorer Revampon Dec 15, 2025
13. ECWireless

    closed this as completedin #444on Dec 17, 2025
14. github-project-automation

    moved this from In Review to Done in Explorer Revampon Dec 17, 2025
15. rickstaa commented on Dec 24, 2025

    

    rickstaa

    on Dec 24, 2025

    Member

    More actions

    @ECWireless thanks for outlining the additional subgraph improvements in #327 (comment).

    As we’re starting a partnership with another group to work on the subgraph in January, these items will be handled outside the current RFP. I’ve created an upstream issue on the subgraph for that team to pick up: livepeer/subgraph#182.

    I’ve also opened a related Explorer tracking issue that your team can follow up on once the upstream subgraph changes are completed: #462.

    For now you can consider this work completed in the scope of the RFP.

    👍React with 👍1Reacted by ECWireless