livepeer / livepeer/explorer

Consolidate Data Sources for Accurate Display of 'Lifetime Rewards' in RCP Stake Movement

Open
#256 1 comment 0 reactions 1 assignee View on GitHub

@ECWireless is already working on this.

Since Feb 2, 2026.

Dominant language
TypeScript
Stars
11
Forks
26
Avg merge
11h 58m
Merged PRs (30d)
16

Description

### Issue Observed

In the Livepeer Explorer, when stakeholders move their stake, the [bondingManager](https://arbiscan.io/address/0x35Bcf3c30594191d53231E4FF333E8A770453e40)'s [pendingStake](https://arbiscan.io/address/0x35Bcf3c30594191d53231E4FF333E8A770453e40#readProxyContract#F19) (see [this YouTube video](https://www.youtube.com/watch?v=SWN6xV5Rvo0)), there's an inconsistency in the display of "Lifetime Rewards." This inconsistency arises due to the current method of data retrieval: the `principal` stake information is fetched using the subgraph, while the pending stake and unbonded information are sourced from the RCP. Since these data sources update at different intervals, the "Lifetime Rewards" display becomes temporarily inaccurate. This discrepancy resolves itself once the RCP cache expires, but it can confuse the interim.

### Proposed Solution

To address this, I propose integrating the `pendingStake` data into the subgraph. This change would allow us to use a singular data source for calculating the "Lifetime Rewards," ensuring consistent and accurate information display. Implementing this feature should eliminate the temporary discrepancies caused by the different update rates of the current data sources.

I've initiated a feature request for this improvement on our GitHub repository, which can be tracked [here](https://github.com/livepeer/subgraph/issues/158).

@adamsoffer and @0xcadams, although this is a low-priority issue, I'd appreciate your input on this proposal. Would this effectively resolve the issue and improve the accuracy of our data display?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.