Clarify that 'Estimated Usage' reflects transcoding only, not AI compute
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
## Problem
The homepage "Estimated Usage" chart displays network usage in **minutes** — a metric inherited from Livepeer's transcoding origins to which does an estimation of minutes based on fees `fee_derived_minutes = volume_eth / (average_price_per_pixel × average_pixel_per_minute)`. As the network has shifted toward AI, this figure no longer reflects actual network activity:
- **AI compute jobs** are billed per **second** of compute.
Raised by Authority_Null in Discord.
## Proposal
Either:
- Replace the chart with a metric that makes sense for the current network (e.g. AI compute-seconds, LLM tokens, or a combined view), **or**
- Remove the chart entirely until a meaningful replacement exists.
Lives in `pages/index.tsx` (~line 198-233).
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 in pages/index.tsx around lines 198-233 and inspect how the homepage Estimated Usage chart derives and presents minutes. Confirm the current transcoding-only calculation and determine which proposal is selected: replacing it with a meaningful network metric or removing it. Done means the chart no longer presents transcoding minutes as total network activity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100