Trace protocol revenue to token-holder entitlement

Practical guide · prepared 19 September 2026. Sources were checked for this workflow; linked interfaces and policies can change. Research scope.

Revenue is not one number

A dashboard may call transaction fees, interest spread, liquidation proceeds or token incentives 'protocol revenue'. Those flows have different payers and destinations. Start with a single fee type and draw the path: who pays, which contract receives it, whether it is immediately passed to service providers, which asset it uses, and who can withdraw or redirect it. Gross user fees are not net treasury inflow. Treasury inflow is not token-holder income. A token-holder entitlement exists only if code or an enforceable agreement gives holders a defined claim.

Make a four-column cash-flow table

1. Generation: name the action that creates the fee and reproduce the rate from current contract parameters or first-party docs.
2. Collection: identify the receiving contract or account and read its balance or accounting variable over a fixed period.
3. Control: trace the function that can move the assets, then trace its governor, timelock, multisig or admin using the proxy-control workflow.
4. Entitlement: locate a distribution, redemption, buyback, burn or claim function. Record eligibility, discretion, costs and whether governance must act first.

Compound III is a useful mechanical example. Its documentation says reserves arise partly from the difference between borrower interest and supplier earnings. Separate governance documentation says the Governor may withdraw reserves to a specified address. That supports a claim that the protocol accumulates governed reserves. It does not, by itself, support a claim that every COMP holder owns a proportional share.

Hypothetical example

Hypothetical: Protocol Blue generated $12 million in user fees during a quarter. Contracts paid $9 million to liquidity providers, retained $2 million in a reserve contract and spent $1 million on rebates. Governance can withdraw the reserve, but no contract distributes it to BLUE holders and no legal document promises a dividend. The accurate chain is: $12 million gross fees, $2 million retained reserves, governance discretion over those reserves, and no identified holder entitlement. Calling BLUE a claim on $12 million would skip three control boundaries.

Test the token link separately

Read token and governance contracts for rights, not slogans. A vote may be able to change fees or spend a treasury, as the governance-token guide explains, while still giving an individual holder no automatic payment. If a fee switch exists but is off, report capability and current state separately. If buybacks occur, check who authorizes them, whether purchased tokens are burned, distributed or retained, and whether future governance can stop the process.

Decision criteria and limits

Use three labels: mechanical entitlement for an executable holder claim, governance-contingent for a flow requiring a vote or admin action, and no demonstrated link when revenue exists without a holder path. Do not infer legal rights from code alone; wrappers, foundations and terms may alter the analysis. Conversely, a written promise may be discretionary or unenforceable. Accounting can also be distorted by token incentives, mark-to-market assets and cross-chain balances. This workflow establishes a documented flow at a date. It is not a valuation model or investment advice.