Paid for compute, last month
USDCustomer payments for compute across the selected networks in the last complete month, valued at the time of each payment.
Dashboard · VantagePlanned
Decentralized GPU Compute: Render, io.net, Akash Usage
How much are customers paying on-chain for decentralized GPU compute each month?
What customers pay on-chain for decentralized GPU compute each month on Render, io.net and Akash, beside the rewards each emits.
ShareEmail it
Blueprint
What the dashboard will show.
The dashboard as it will open in Vantage. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
Usage
Customer payments for compute by network and month.
Render burns, last month
USDValue of RENDER burned for work in the last complete month.
io.net payments, last month
USDCustomer payments and IO burns on io.net in the last complete month.
Akash leases, last month
USDLease settlements from escrow on Akash in the last complete month.
Payments by network and month
USDMonthly customer payments for compute, stacked by network, over the selected period.
Usage and rewards
Payments against emissions for each network.
Usage to emissions
ratioCustomer payments divided by the value of emissions over the last complete month, across the selected networks.
Emissions, last month
USDValue of the tokens issued to providers and stakers by the selected networks in the last complete month.
Usage to emissions by network
ratioEach network's customer payments divided by its emissions over the last complete month.
Payments against emissions
USDMonthly payments and monthly emissions for the selected network over the selected period.
How each network is measured
Each network's payment path, unit of work, chain, contracts or programs read and price source.
- Network
- Render, io.net, Akash or all three
- Period
- Last 6 or 12 months, or all history
About
What it answers, and for whom.
Decentralized compute networks rent out GPUs owned by many independent providers for rendering, AI training and inference. Render, io.net and Akash each take customer payment in a different way, through token burns, direct payments or leases settled on their own chain, and each leaves a record that can be read.
This dashboard turns those records into one monthly figure per network: what customers paid for compute, in dollars at the time of payment. Beside it sits what each network emitted to its providers and stakers, so usage and rewards can be compared on the same scale.
The networks measure different things, from rendered frames to GPU hours to container leases, so the dashboard compares money paid rather than units of work, and names each network's payment path.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Render usage is RENDER burned for completed work under its burn-and-mint model, read from the burns on Solana for each epoch.
- io.net usage is customer payments and IO burns read from their transfers on Solana, with payments in stablecoins counted at face value.
- Akash usage is lease settlements from deployment escrow accounts on the Akash chain, in AKT and stablecoins; the economic rules its governance sets are recorded for each period.
- Burned and paid tokens are valued at DEX pool prices at the block of each burn or payment, and emissions at the price at the time of each emission.
The data it needs
Chain data, with some off-chain sources
- depin_networks_dailyTo buildDePIN networksUsage and token flows of decentralized physical infrastructure networks: burns for usage, emissions to operators, and active nodes where on-chain.
- protocol_revenue_dailyTo buildProtocol fees, revenue and buybacksFees users paid to each protocol and the part kept by the protocol or its token holders, per protocol and day, including buybacks.
- dex_swaps_dailyTo buildDEX volumeSwap counts and volume per DEX, pool and chain per day, decoded from Swap events, valued with stablecoin legs and oracle prices.
- Render RENDER burns per epoch under burn-and-mint equilibrium on Solana
- io.net IO burns and customer payment transfers on Solana
- Akash escrow lease settlements and fees on the Akash chain
- Provider reward emissions per network, for comparison
- Token USD value at burn time from DEX pool prices
Questions
Questions people ask.
What is decentralized GPU compute?
A marketplace where independent providers, from data centers to individual machines, rent out GPUs to customers who need rendering, AI training or inference. Payments and rewards run through a network token and on-chain records.
How do Render burns work?
Under Render's burn-and-mint model, creators pay for jobs priced in dollars and the equivalent RENDER is burned, while node operators are paid from a separate emission schedule. The burns are the network's usage.
How does io.net charge for compute?
Customers pay for GPU time in IO or in stablecoins, and the network uses part of its revenue to buy and burn IO. The dashboard reads both the payments and the burns on Solana.
What does Akash network usage measure?
Akash customers lease compute by funding escrow accounts that pay providers as a deployment runs. Lease settlements from escrow are the usage figure, read from the Akash chain itself.
Why compare usage with emissions?
Emissions are new tokens paid to providers whether or not customers use the network. Comparing them with usage shows how much of what providers earn comes from paying customers.
- GPU hour
- One hour of use of one GPU, the unit most compute networks price their capacity in.
- Escrow lease
- On Akash, a deployment's funds held in an escrow account and paid out to the provider as the lease runs.
- Emissions
- New tokens a network issues on a schedule to reward providers and stakers, separate from what customers pay.
Related
More apps like this.
DePIN Revenue Leaderboard: On-Chain Fees and Burns
DePIN networks ranked by revenue paid on-chain through burns, fees and lease payments, with off-chain reported revenue labelled apart.
Multi-chainSolanaDePIN Revenue vs Emissions: Monthly Burn and Mint Report
Each month, the tokens every major DePIN network burned for usage set against the tokens it emitted as rewards, cited to the chain.
Multi-chainSolanaHelium Network Stats: Data Credit Burns and Hotspots
Helium's Data Credit burns, HNT burned against HNT emitted and hotspots onboarded by subnetwork, all read from Solana.
SolanaBittensor Subnets Ranked by TAO Emissions and Stake
Every Bittensor subnet with its share of TAO emissions, the TAO in its pool, net staking flows and alpha reserves, by netuid.
Multi-chainHivemapper Network Stats: HONEY Burns, Rewards and Mapping
HONEY burned for map data and issued to contributors each week on Solana, the network's net supply change and reported mapping coverage.
SolanaGrass Network Tracker: GRASS Staking, Airdrops and Holders
GRASS staked, claimed and held on Solana, with exchange balances, unlocks and the network size Grass reports, each figure sourced.
SolanaBuild Decentralized GPU Compute: Render, io.net, Akash Usage on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.