Skip to content
Yieldo
Protocol revenue

How to Read Crypto Protocol Revenue

Written by Yieldo

Protocol revenue answers a narrow question: how much of the money paid for a product is retained by the protocol under a stated accounting definition? It does not, by itself, tell you the protocol's profit, what its token holders receive, or whether the token is attractively priced. To read a revenue dashboard, follow the payment from the customer to its final use.

Start with the paying customer and the product

A trading fee, borrowing charge and NFT creation fee buy different services. Identify the payer, the operation and the product version before comparing totals. A protocol may include an exchange, a launchpad and several deployments. A parent total and its included products describe overlapping activity; adding them produces a larger number without another customer paying anything.

Scope matters within one brand too. Revenue from spot trading should not silently become perpetuals revenue. A figure from one chain is not automatically a global total. Trading volume is the notional amount exchanged, not the fee earned on that amount. Deposits, TVL and transfers between treasury wallets are not new customer revenue.

Fees, retained revenue and expenses

Fees measure the specified user payments. Protocol revenue measures the portion assigned to the protocol after the documented split with liquidity providers or other service providers. The provider's definition determines whether particular charges are included. Read that definition rather than interpreting every field called “revenue” identically.

Illustrative example, not a protocol snapshot: customers pay $100 in fees, of which $70 belongs to liquidity providers and $30 is retained. The retained revenue is $30. Subtracting the same $70 again from that $30 would count the distribution twice. Development, grants, infrastructure and other operating expenses may still be unknown. Without a sufficiently complete expense account, calling $30 “net profit” or calculating a genuine price-to-earnings ratio is unjustified.

Revenue earned is not revenue paid to holders

Next follow the retained money. It may remain in a reserve, fund operations, be allocated to a future buyback, purchase tokens now, or become a distribution that eligible recipients can claim. Allocation, claimability and payment are different states. A governance vote approving a budget establishes neither an executed purchase nor an individual holder's receipt.

“Holders revenue” is particularly definition-sensitive. A data provider may derive it from burned tokens or a fee allocation. Preserve that label and method; do not rename it “cash spent on buybacks.” Execution needs its own evidence. Conversely, a distribution funded from accumulated reserves can exceed the revenue earned in the same month without being an accounting error.

One period · separate observations

Hyperliquid

Protocol profile
Current data window — · UTC Snapshot cutoff:
User fees — Unknown · Source unavailable No verified observation for this period and scope.
Protocol revenue — Unknown · Source unavailable No verified observation for this period and scope.
Market cap — Unknown · Source unavailable No verified observation for this period and scope.
Known expenses — Unknown · Source unavailable No verified observation for this period and scope.
Token mechanism
  • Market buybackStatus unconfirmed
  • Treasury burnStatus unconfirmed

Protocol revenue is retained product income, not audited net profit. Market data may have a different observation time; see the evidence for each metric.

The block shows the period and availability of the current observations. Its figures can change independently of this educational text. A missing value means there is no publishable measurement for that field; it is not a zero.

Read the calendar before the multiple

For a complete rolling window of N calendar days, an annualized run rate is the observed amount multiplied by 365/N. A complete 30-day observation therefore uses 365/30. For an actual observed year, use the actual annual amount. An incomplete window is not a full month, and missing days must not be filled with zeros.

A run rate describes what the recent pace would imply if maintained. It is not a forecast. A token ratio also needs compatible dates, currency units, product coverage and a defined market-capitalization denominator. Today's market cap divided by an old, differently scoped revenue total can look precise while answering no coherent question.

A repeatable reading order

  1. Identify the product, payer, scope and observation period.
  2. Separate customer fees from retained revenue and known expenses.
  3. Check whether the token link is a documented rule, an allocation or an executed event.
  4. Read the source, coverage, methodology version and freshness state.
  5. Compare like periods and mechanisms, keeping missing fields visible.

Use the protocol revenue screener to inspect coverage and the methodology for exact definitions. The goal is an auditable account of money and token rights, not a ranking of promised yields.

Definitions reviewed on 6 October 2026. Reference: DeFiLlama's metric definitions; individual observations retain their own sources and dates.

Sources and review date

Sources reviewed on 06.10.2026. Current widget observations have their own periods and timestamps.

How we publish, date and correct material — editorial policy.

Keep exploring

Related Articles