Fees are the amounts users pay for a crypto service. Protocol revenue is the portion retained for the protocol under a stated methodology, usually after payouts to liquidity providers or other suppliers. Token-holder revenue tracks a further allocation, where one exists. These figures do not establish profit or a holder's return; check the fee split, costs and actual destination.
A statement that a protocol “generated $1 million” is incomplete until it names the measure. The money could largely belong to liquidity providers, sit in a treasury, fund operating costs, or support a token-specific mechanism. Start with a receipt and follow its allocation before connecting activity to token value.
Give each fee number a recipient
In DefiLlama's terminology, fees cover users' payments, revenue excludes the portion distributed to liquidity providers, and holders revenue is a subset of protocol revenue. That last category can include direct staker distributions, fee burns, or buyback-and-burn mechanisms. A holder-revenue figure therefore does not necessarily describe cash paid into every holder's wallet. DefiLlama's metric definitions.
Names can change meaning between a dashboard and a protocol's own documentation. Uniswap uses “protocol fees” for a portion of swap fees directed away from LPs toward the protocol. Its documentation also distinguishes how fees work across versions. Reading “protocol fees” as the total paid by traders would mix two different measures. Uniswap's fee documentation.
For each figure, write down the payer, recipient, activity and coverage. A DEX trader's swap payment, a borrower's interest payment and a blockchain transaction fee arise from different services. Equal dollar totals do not establish equal margins or equal token-holder benefits.
Also distinguish fees earned from fees collected. Uniswap documents claimable fee balances for v3 and v4 positions. Uniswap's fee accrual rules. A later withdrawal of previously earned fees is a settlement event, rather than another fee generated by users. A reconciliation must either follow accruals or follow cash movements, with an explicit bridge between them.
Reconcile one hypothetical week
Consider a fictional DEX over one seven-day UTC period. This is an invented accounting exercise, not a named protocol's fee schedule or a KLINEO feature.
Assume $12 million of trading volume, a constant 0.30% swap fee, and settlement in an asset worth $1 throughout the period. Liquidity providers receive 80% of swap fees; the protocol receives 20%. One-third of protocol revenue goes directly to eligible token stakers, and the rest goes to the treasury.
For this example, every fee accrual and allocation settles in the same period. There are no refunds, rebates or deferred claims. The treasury pays $3,000 of operating costs, with no other cash flows.
| Stage in the hypothetical ledger | Calculation | USD |
|---|---|---|
| User swap fees | $12,000,000 × 0.30% | 36,000 |
| LP allocation | $36,000 × 80% | 28,800 |
| Protocol revenue | $36,000 − $28,800 | 7,200 |
| Fee-funded holder distribution | $7,200 ÷ 3 | 2,400 |
| Treasury allocation before costs | $7,200 − $2,400 | 4,800 |
| Treasury cash operating costs | Stipulated payment | 3,000 |
| Added treasury cash after those payments | $4,800 − $3,000 | 1,800 |
The first reconciliation is $36,000 in user fees equals $28,800 for LPs plus $7,200 of protocol revenue. The second is $7,200 equals $2,400 for eligible stakers plus $4,800 for the treasury. The third is $4,800 equals $3,000 spent plus $1,800 retained as additional treasury cash.
These are successive allocations of the same money. Adding $7,200 of revenue to $2,400 of holder distributions would count that distribution twice.
The protocol's take rate is revenue divided by fees: $7,200 / $36,000 = 20%. Token Terminal uses that definition of take rate. Token Terminal's metric definitions. Relative to trading volume, the protocol captures only 0.06%, or six basis points. The full 30-basis-point swap charge is not its retained rate.
Holder distributions are approximately 6.67% of user swap fees: $2,400 / $36,000. That is an allocation percentage, not a staking yield. Calculating a yield would require the eligible stake denominator, reward timing, valuation and other conditions.
Keep network costs outside the DEX receipt
Now stipulate that these users also pay $4,000 of network fees. Their combined modeled fee cost is $40,000, but the DEX's swap fees remain $36,000 and its revenue remains $7,200. The additional payment has a different destination.
For an Ethereum-specific example, gas pays for execution, including execution that fails. Its base fee is burned, while its priority fee goes to the validator. Those network flows do not become DEX treasury receipts simply because the transaction interacted with a DEX. Ethereum's gas documentation.
A user-cost report can include both distinct charges. A DEX-revenue report needs to preserve the DEX boundary. Router, interface and hook charges need the same treatment: identify the charged service and recipient before deciding which total includes them.
Separate revenue, treasury cash and incentives
The example's $1,800 treasury cash increase does not replace its $7,200 revenue figure. The difference reflects an allocation to holders and a cash expense.
Before holder distributions, revenue less the modeled operating costs is $4,200. After the $2,400 distribution, the treasury has $1,800 more cash. Both calculations are valid, but they describe different stages. Calling either one “net” without naming the deductions conceals the distinction.
Revenue can also precede additional costs. Token Terminal explicitly places its revenue metric before cost of revenue, token incentives and operating expenses. Its earnings definition warns that missing on-chain operating expense reporting can understate costs. A revenue field should therefore not be treated as complete profit evidence. Token Terminal's revenue and earnings definitions.
Extend the fictional week with 3,000 newly issued reward tokens, valued at a stipulated $2 each when distributed. Their measured incentive value is $6,000. These rewards do not add another $6,000 of user fees: they are newly issued tokens, rather than payment for this week's swaps.
In an analytical worksheet that charges those incentives at distribution value, the remainder before holder distributions is $7,200 − $3,000 − $6,000 = −$1,800. That convention exposes the incentive cost alongside the fee stream. It is not an audited accounting profit, and the $6,000 is not a cash outflow from the modeled settlement-asset treasury.
Save the reward quantity and valuation rule together. A later token-price change would alter a new dollar valuation without changing how many reward tokens were issued. If a staking display blends issuance with fee-funded rewards, the staking APR versus APY guide explains the additional balance, commission and compounding checks needed at the individual position level.
Verify how the token receives value
Protocol revenue and token-holder payments can diverge completely. A protocol can retain fees in its treasury while the token has no active fee distribution. A proposal to introduce sharing describes a possible future rule; it does not prove a payment occurred.
Trace the actual mechanism. A direct distribution needs an eligible recipient set, a paid asset and a settlement record. Staking or locking requirements can limit participation. A buyback needs evidence of purchases and the destination of acquired tokens. A burn needs evidence that units were removed under the relevant token rules.
Avoid counting one mechanism at multiple stages. If revenue funds a buyback followed by burning those purchased tokens, the purchase value and burn value are not two independent user-funded distributions. A burn also does not place cash in each remaining wallet or establish a price response.
Uniswap's current documentation, for example, describes collection contracts whose assets can be claimed by searchers that burn UNI. That is a specific conversion mechanism, rather than a direct fee payment to every UNI balance. The documentation alone does not verify a particular pool's settings or an individual transaction. Uniswap's protocol-fee mechanism.
If a report divides token valuation by revenue, identify which revenue it uses. User fees, protocol revenue and holder distributions would produce different denominators in the fictional week. The market cap versus FDV guide addresses the separate supply-definition problem in the numerator. A clean ratio still does not establish an entitlement to the denominator.
Check coverage before comparing protocols
A rolling 24-hour total and a completed UTC day can contain different transactions. Match start and end times, chains, contract versions and included products. If a fee split changes partway through the period, apply each rule to its effective transactions rather than applying today's split to the whole history.
Check the pricing convention as well. Retain original token quantities and the dollar conversion times. A USD fee series can change because the payment token's price changed, even when the quantity paid did not. One provider's transaction-time valuation and another's daily closing price may therefore fail to reconcile.
Capital and activity measures need their own records. The TVL versus net deposits comparison helps separate deposit flows from the value of assets already present. Neither is a substitute for a fee receipt. For claims based on how quickly a token circulates, use the separate token velocity analysis, then return to the payment ledger to identify who received fees.
If fees are reported after rebates or refunds, retain the gross charges and adjustments separately. State which basis the displayed total uses before comparing take rates.
Treat a missing cost or missing holder-distribution field as unknown until you verify its coverage. A blank value does not establish zero expense, while a zero holder payout does not by itself establish zero protocol revenue.
Use a fee-to-recipient worksheet
For one closed period, preserve the following evidence. A dashboard screenshot can help locate a claim; it does not replace the underlying definitions and records.
| Worksheet field | Evidence to retain | Reconciliation check |
|---|---|---|
| Identity and scope | Protocol, chain, contracts, version and included service | Every payment belongs to the stated boundary |
| Measurement window | UTC endpoints, block range and capture date | Fee totals and allocations cover the same activity |
| User fee basis | Gross charges, refunds, rebates, asset quantities and valuation | Reconcile gross charges to the stated fee total |
| Supplier and protocol split | Effective rules and recipient records | User fees equal supplier allocation plus protocol allocation |
| Holder mechanism | Eligibility, paid asset, claim or burn records | Identify a subset of revenue without double counting |
| Treasury movement | Opening balance, receipts, payments and closing balance | Explain cash changes separately from fee accrual |
| Costs and incentives | Cash expenses, issued units, valuation and missing coverage | State every deduction behind a claimed net result |
Finish with one explicit statement: users paid this amount, suppliers received this share, the protocol was allocated this amount, and this portion reached the documented holder mechanism. Then name the cost records still missing.
If that statement cannot be reproduced, mark the value-distribution claim unverified and resolve the missing recipient or deduction before using the headline to assess a token.