On-Chain Fundamentals: Protocol Revenue Analysis 2026
In the shifting landscape of 2026, yield sustainability is no longer a buzzword—it’s the dividing line between enduring protocols and those that fade with the next liquidity cycle. The days of arbitrarily high APYs backed by token inflation are over. Sophisticated investors and analysts now demand a clear view of true on-chain revenue, net of emissions, to separate genuine cash flow from manufactured incentives.
This guide cuts through the noise. You’ll learn how to use Dune Analytics—not as a dashboard consumer, but as a query architect—to perform your own deep-dive on-chain protocol revenue analysis. We’ll move beyond simple “fees collected” metrics and into net revenue, sustainability ratios, and supply dilution adjustments. By the end, you’ll be equipped to build queries that reveal whether a protocol’s yield is a byproduct of real economic activity or a short-term subsidy.
- True protocol revenue is net of operational costs (LP rewards, subsidies), not just total fees collected.
- Dune Analytics’ raw event tables let you trace every dollar—avoid black-box dashboards.
- The sustainability ratio (Net Revenue / Token Emissions) is the #1 metric for judging yield durability.
- Dilution-adjusted revenue per token reveals whether growth outpaces inflation.
- Cross-protocol benchmarks like revenue/TVL provide context; a standalone number is meaningless.
- Always verify fee structures, contract upgrades, and circulating supply definitions to avoid false signals.
1. Defining Protocol Revenue: The True Metric
Most casual on-chain protocol revenue analysis starts and ends with “total fees.” That’s a trap. Total fees include everything users pay, but a protocol’s financial health depends on how much of that flows to its treasury or token holders after paying out liquidity providers and other participants. The durable metric is net protocol revenue: fees minus direct operational costs (like LP rewards, oracle fees, or gas subsidies).
For example, a lending protocol may collect 1,000 ETH in interest, but 600 ETH goes to depositors as yield. Net revenue is 400 ETH. If the protocol’s own token is minted to incentivise borrow, that’s an expense that further reduces true revenue. Takeaway: Always decompose the fee waterfall. On Dune, this means joining events from the protocol’s core contracts with transfer tables to track where fees end up.
“Revenue without cost context is vanity. Net revenue, post-emissions, is sanity.”
Use the Dune spellbook module for each protocol (e.g., aave_v2.revenue) as a starting point, but always verify assumptions about which fee streams are truly retained.
2. Why Dune Analytics for Revenue Analysis
Dune’s strength in 2026 remains its community-driven, open SQL environment. Unlike black-box dashboards, Dune lets you query raw decoded events, trace every fee dollar, and cross-reference token transfers. This transparency is critical for on-chain protocol revenue analysis because no two protocols define “revenue” identically.
You can isolate revenue by chain, by asset, or by user segment. More importantly, you can build timed queries that track weekly or daily net revenue, and then join with token supply tables to calculate dilution-adjusted metrics. Dune’s erc20_ethereum.evt_Transfer and prices.usd datasets allow you to convert revenue into a common denomination without relying on external APIs.
- Access to decoded contract events for any major protocol.
- Ability to customize time windows and aggregation logic.
- Open-source queries that you can fork and adapt.
- Spellbook maintains standardized ‘revenue’ tables for many protocols.
If you’re serious about sustainable yield, Dune is not optional—it’s the workshop.
3. Building a Revenue Query: Step‑by‑Step
Let’s walk through a real Dune query skeleton for a hypothetical lending protocol. Start with the erc20_ethereum.evt_Transfer table filtering for the protocol’s fee receiver address. You need to isolate inflows from users repaying loans (a common fee collection point).
Step 1: Identify fee-collection events. Look at the lending contract’s repay event; it often emits a feeAmount or logs a transfer to a fee vault. Use the protocol’s ABI or the decoded events in Dune’s schema explorer.
Step 2: Aggregate by time slices. Use date_trunc('day', evt_block_time) AS day to get daily sums. Join with prices.usd to convert token amounts to USD (e.g., JOIN prices.usd ON symbol='ETH' AND minute = date_trunc('hour', evt_block_time)).
Step 3: Subtract direct operational costs. If the protocol pays LP rewards in the same token, query the payout events on the same contract and subtract. This yields gross protocol revenue.
| Metric | SQL Source | Notes |
|---|---|---|
| Gross fees collected | SELECT SUM(amount) FROM fee_events | Include all fee streams |
| LP incentive payouts | SELECT SUM(amount) FROM reward_events | Often cumulative per day |
| Net protocol revenue | Gross fees - LP payouts | First approximation |
Tip: Always check if the protocol has changed fee structures; Dune’s versioned spellbook tables can help.
4. Decomposing Revenue Sources: Lending, DEX, and More
Not all revenue is equal. For a thorough on-chain protocol revenue analysis, you must decompose revenue by source. A lending protocol might earn from borrowing fees, flash loan fees, and liquidation penalties. A DEX earns from swap fees; a derivatives protocol earns from funding rates and trading fees. Each source has different sustainability characteristics.
On Dune, use the protocol’s event logs to tag each revenue type. For example, in Uniswap, every swap emits a Swap event with amount0In, amount1In, etc. The fee (0.3% default) is embedded in the input amount; you can calculate revenue as amountIn * fee (e.g., 0.3% of amountIn). For lending, use Repay and interest-accrual events to measure interest paid — Borrow events only log the principal drawn, not interest.
- Borrow interest: Recurring, but dependent on demand.
- Flash loan fees: Lower but stable from arbitrage.
- Liquidation penalties: Spiky, but often large.
- Swap fees: Volume-driven, highly volatile.
Create a pivot table in Dune by source. This helps you assess whether a sudden revenue spike came from a one-time liquidation event or sustained lending activity.
5. The Sustainability Ratio: Revenue vs. Token Emissions
The core of sustainable yield analysis is the sustainability ratio: Net Protocol Revenue ÷ Token Emissions (in USD). A ratio above 1 means the protocol generates enough revenue to cover its token incentives; below 1 means it’s burning through the treasury or diluting holders. This is the single most important metric for long-term yield viability.
In Dune, you need to join your revenue query with token mint events from the protocol’s token contract. Use erc20_ethereum.evt_Transfer with from = '0x0000000000000000000000000000000000000000' to catch mints. Multiply by the token’s USD price (daily average) to get emission cost.
“If a protocol pays $1M in token rewards to attract $800k in revenue, it’s not generating value—it’s marketing spend disguised as yield.”
Track this ratio over at least 90 days to account for emission schedule changes and market cycles. A falling ratio is a red flag; a rising one suggests the protocol is reaching product-market fit.
6. Circulating Supply Impact: Inflation Dilution
Even if a protocol’s net revenue is positive, high inflation can destroy per-token value. You must adjust for dilution. The metric is revenue per fully diluted share (or per circulating token). On Dune, query the total supply (circulating) at each snapshot. Use supply_usd from the token’s transfer events to get day-wise totals.
Calculate: Revenue per token = Net Protocol Revenue (USD) / Circulating Supply. Compare this to the token’s price. If the P/E (price / revenue-per-token) is extremely high, the market is pricing in future revenue that hasn’t materialized. Conversely, a low P/E (e.g., below 10) may indicate undervaluation if the revenue is recurring.
- Use Dune’s
erc20_ethereum.evt_Transferto track supply changes. - Community-built supply dashboards on Dune can be a starting point.
- Always verify circulating definitions—some tokens have locked vesting contracts.
Dilution analysis separates short-term speculation from long-term fundamentals.
7. Comparative Analysis: Cross‑Protocol Benchmarks
No on-chain protocol revenue analysis is complete without benchmarks. Use Dune to compare your target protocol against peers. For example, compare net revenue per dollar of total value locked (TVL)—a capital efficiency ratio. A lending protocol with $10M TVL and $100k weekly net revenue is more efficient than one with $100M TVL and $200k revenue.
Build a master dashboard with Dune’s parameterized queries. Set up a protocol_name parameter so you can toggle between Aave, Compound, and Morpho. Key comparative metrics:
| Metric | Formula | Interpretation |
|---|---|---|
| Net Revenue / TVL | Net Revenue / (Avg TVL) | Capital efficiency; higher is better |
| Sustainability Ratio | Net Revenue / Token Emissions | Self-sufficiency; >1 is healthy |
| Revenue Growth (30d) | WoW or MoM change | Momentum indicator |
Use these to spot outliers. A protocol with growing net revenue and a sustainability ratio above 2 is a strong candidate for sustainable yield.
8. Pitfalls and Advanced Adjustments
Even advanced analysts make errors. Common pitfalls in on-chain protocol revenue analysis include: (1) double-counting fees when a protocol uses multiple contracts, (2) ignoring non-circulating token supply in dilution calculations, (3) using spot prices instead of time-weighted averages for revenue converted to USD, and (4) mistaking “Treasury revenue” (which includes protocol-owned liquidity returns) for true operating revenue.
To adjust: for non-circulating tokens (e.g., team vesting), subtract them from the denominator when computing revenue per token. Use a time-weighted average price (TWAP) via Dune’s prices.usd table with hourly or finer granularity. Also, check if the protocol uses a fee switch—some fees are optionally turned on; you need to verify via governance proposals on Dune (using gnosis_ethereum_proposals or similar).
Finally, distinguish gross versus net in the sustainability ratio—some protocols treat token buyback as revenue when it’s really returning capital. Always go back to the source events.
Frequently asked questions
How do I get started with Dune for revenue analysis?
Create a free Dune account, use the Spellbook tables (e.g., aave.revenue) as a template, and modify the SQL to isolate net revenue. Then join with token mint events for the sustainability ratio.
What token price source should I use in Dune?
Use the prices.usd table with minute-level data for TWAP adjustments. Avoid spot prices from a single block to reduce noise.
What if a protocol doesn’t have a Spellbook table?
You must decode the contract ABI yourself. Use Dune’s schema explorer to find the fee-collection events, and query raw Transfer logs filtered by the protocol’s fee address.
How often should I recalculate the sustainability ratio?
Daily is ideal to capture emission schedule changes, but weekly aggregates are sufficient for trend analysis. Always use a rolling 30- or 90-day average.
Related reading
Track the entities behind the concepts
DeFi Intel maps 11,000+ protocols, tokens and companies to a typed knowledge graph — with live data, incidents and regulation.