Protocol Fees vs Revenue in On-Chain Analytics
Distinguish user-paid fees, liquidity-provider earnings, protocol receipts and token-holder distributions, preserving actual recipient and allocation evidence.
Overview
When translating these concepts into an integration, keep the scope described by the wallet history api with the result. The examples in wallet transaction history and smart contract event logs show how the same distinction affects neighbouring data questions.
A protocol’s activity can generate several kinds of fees. Calling all of them protocol revenue hides who actually receives the value and under which mechanism.
Define the recipient boundary
Separate gross user fees, amounts allocated to liquidity providers or operators, protocol-controlled receipts and later distributions. Network execution fees can be unrelated to the application’s own revenue. Use actual contract and transfer evidence where available; a published fee percentage does not prove the realised allocation for every transaction.
Worked example: one hundred in gross fees
Users pay one hundred units. Eighty go to liquidity providers and twenty to a protocol-controlled destination under a simplified allocation. Gross fees are one hundred, while protocol receipts under that boundary are twenty. A later distribution of those twenty should not be counted again as newly generated protocol fees.
Handle timing and units
Record accrual, collection and distribution separately where the mechanism distinguishes them. Test fee changes, rebates and multiple assets. Keep fiat-equivalent conversions traceable to prices. A revenue chart should state its economic boundary and exclusions rather than rely on a familiar label with no reproducible formula.
A practical acceptance test
Allocate gross fees of one hundred into eighty for participants and twenty for a protocol-controlled recipient. Assert the correct boundary-specific totals. Distribute the twenty later and verify that fee generation does not become 120. Keep accrual, collection and distribution records linked but distinct, with compatible asset units and conversion observations.
Questions about the topic
Frequently asked questions
Are all user fees protocol revenue?
No. Recipients and allocation rules differ.
Is a later distribution new fee generation?
Not necessarily; it can redistribute already counted receipts.
Standards & technical documentation