Chapter 26 · How Protocols Make Money
TVL is high, but is the protocol itself earning money?
- Capabilities practiced
- Financial LiteracyResearch
- Hands on
- Calculate a protocol's net revenue: fee income minus current-period incentives; see whether it is positive.
- AI Lab
- Have AI organize a protocol's revenue definition. Compare it with the official dashboard and identify inconsistencies.
A Real-World Problem
You are comparing two protocols to decide which is the better business.
The first ranks near the top of its sector by total value locked. Daily trading volume is large, tens of thousands of addresses interact with it every day, and its community is lively. Every public metric looks impressive.
The second has one tenth of the first protocol's TVL, four-digit daily activity, and hardly anyone discussing it.
Most people would choose the first, with good reasons: it is larger, more active, and more widely recognized.
Now add one more line of information. Look at both protocols' income and spending for the period:
Protocol A Users pay substantial fees, mostly distributed to liquidity providers by rule;
the protocol's share, minus token incentives issued during the period, is negative.
Protocol B Fees are much smaller, but incentives ended long ago;
the protocol's share stays in its treasury and is positive.A is paying for scale. B is earning money. Both can reasonably describe themselves as growing.
One thing needs to be clear immediately: this chapter is not saying B is a better investment than A. This stage is about evaluating and building a project, not trading it. Burning money to gain scale can be entirely reasonable at certain stages—provided you know you are doing it, when it should end, and what will remain afterward.
The real problem is that you will not find that extra line on the front page of any public dashboard. The front page shows TVL, volume, and user counts, and none of those three is revenue.
Chapter 23 taught you how to collect data and define its scope. This chapter goes one layer deeper: once you have the numbers, how do you arrange them into a statement that shows whether the protocol is making money?
Thought Experiment
Replace the protocol with a marketplace.
You open a market on an empty lot. The rules are simple:
- Vendors put out their goods, customers shop, and leave after buying.
- You take 1% of each sale. This is your only income.
- To attract activity, you print market vouchers. Each time a vendor makes a sale, you give them a voucher they can spend like money in the market.
After three months, four numbers are in front of you:
Total value of goods on the stalls 80 million ← The vendors' goods, not yours
Sales over three months 60 million ← Turnover, not your money
Your 1% commission 0.6 million ← Money you received
Vouchers issued, at face value 0.9 million ← Something you printedNow answer: how much money did this market make in three months?
The first number is easiest to present as an achievement: 80 million worth of goods sounds like a large market. But none of it belongs to you. The vendors could remove everything tomorrow, and its value changes with market prices—if the goods rise in price, your market gets “bigger” without a single additional transaction.
The second number is turnover. Sales of 60 million sound much more impressive than 0.6 million, but you receive only 1%. Worse, turnover can be manufactured: two people could repeatedly trade the same goods with each other, generating unlimited volume while you subsidize your 1% commission with vouchers.
The third number is money you actually received: 0.6 million.
The fourth is what you gave out: vouchers worth 0.9 million. They differ from cash—you can print them at almost no cost, with no cash leaving during the period. But eventually someone will spend them, exchanging them for real goods held by someone else. Who pays for those vouchers? Everyone holding market vouchers, through dilution.
So:
Excluding vouchers: +0.6 million; a profitable business
Including vouchers: 0.6 − 0.9 = −0.3 million; a net outflow over these three monthsBoth answers are internally consistent, and they lead to opposite decisions.
Ask one more question, the one many people miss: if you stop issuing vouchers, how much of that 60 million in sales remains?
The accounts cannot answer this. You have to try stopping. Once you realize you are afraid to stop, you already know something about the answer.
Your Decision
You want to know how a protocol makes money and whether it actually does. Which number do you start with?
What Happens
The four choices converge on three inequalities. They form this chapter's backbone and are worth writing down:
TVL ≠ Revenue, Volume ≠ Profit, User ≠ PMF.
Take them apart:
| Inequality | What the left measures | What the right requires | Why they differ |
|---|---|---|---|
| TVL ≠ Revenue | How much other people's money is deposited | How much the protocol actually receives | Deposits do not generate revenue; usage does. TVL also changes with token prices |
| Volume ≠ Profit | The size of turnover | What remains after costs | Fee rates, supply-side shares, and incentives stand between them |
| User ≠ PMF | How many addresses interacted | How many people return without subsidies | Incentives can buy interactions, but not return visits |
All three share a structure: the left side is easy to obtain, grow, and display; the right side requires your own calculations, grows slowly, and is rarely displayed willingly. This asymmetry explains why the industry's materials are full of numbers from the left.
Pair each metric on the left with one on the right, and you have a portable comparison table:
| Commonly displayed | What to view alongside it | In one sentence |
|---|---|---|
| TVL | Annualized revenue per unit of TVL | Is the same amount of money being put to work here? |
| Trading volume | Protocol share ÷ volume, the effective commission rate | Large turnover is useless if the protocol cannot retain a share |
| Active addresses | Active addresses on days without incentives | Chapter 28 turns this into a standard procedure |
| Fee income | Fees minus incentives during the period | This chapter's central calculation |
| Treasury size | How much consists of the protocol's own token | Something you print yourself is not a reserve |
The last row needs its own explanation and introduces the second half of this chapter. If a protocol reports a $100 million treasury and $90 million is its own token, that $100 million is not really $100 million. Selling it when funds are needed pushes the price down, leaving far less cash than the book value.
Build a Model
A Five-Line Protocol Income Statement
This is the structure to take away. You can apply it to any protocol:
- Fees paid by users
- Share paid to the supply side
- Protocol share
- Subtract current incentives
- Net revenue
As a statement:
Total fees paid by users Fees
− Share paid to the supply side LP / depositors / validators / market makers
= Share retained by the protocol Protocol Revenue
− Token incentives issued Incentive Cost
= Net revenue Net RevenueFive lines, four numbers, three minus signs. Each line has a recurring trap:
| Line | Common mistake | How to avoid it |
|---|---|---|
| Fees | Calling it protocol revenue, inflating the figure severalfold | Always ask whose address ultimately receives the money |
| Supply-side share | Omitting it because it is absent from the dashboard | Read sharing ratios from contract parameters, not articles |
| Protocol Revenue | Not saying whether incentives are included | State which layer you are citing |
| Incentive Cost | Counting tokens without converting to money | Show two curves: token quantity and value at contemporaneous prices |
| Net Revenue | Almost never appearing in promotional materials | This is the number you must calculate yourself |
The Other Side of Chapter 17
Chapter 17 examined yield sources: displayed APY equals fee APY plus interest APY plus subsidy APY. “Who pays this money?” was the first of its four questions.
That chapter took the recipient's side; this chapter takes the payer's side. The same money, viewed in two directions.
| What the user sees, in Chapter 17 | What the protocol records here | Where the money comes from |
|---|---|---|
| Fee APY | Fees minus the protocol's retained share | Actual payments from other users |
| Interest APY | The same, paid by borrowers | Actual payments from borrowers |
| Subsidy APY | Incentive Cost | Tokens printed by the protocol, paid for by dilution of all holders |
This connects the chapters and yields a useful inference: real yield on the user side equals the portion of protocol fees paid to the supply side. If the two calculations disagree, at least one has an incorrect definition—precisely the cross-check described in Chapter 23.
Effective Take Rate
Compress the protocol's business model into one number:
Effective take rate = Protocol share ÷ Total fees paid by usersThe ratio varies enormously between sectors, and higher is not always better—it is inseparable from the intensity of competition.
| Take-rate position | What it usually means | What to ask next |
|---|---|---|
| Near zero | Almost all fees go to the supply side | What keeps it alive: the treasury or fundraising? |
| Low but stable | Fierce supply-side competition limits the protocol's share | Can the supply side be replaced? |
| Moderate and adjustable | A fee switch exists and is partly enabled | Who can enable it, and would doing so drive suppliers away? |
| High | A barrier protects this position, or users lack alternatives | What is the barrier, and how long can it last? |
The fee switch deserves close attention. Many protocols include a contract parameter determining how much collected fees belong to the protocol. It is often zero at launch and later enabled through governance. Research three things: whether the switch exists, its current setting, and who can change it. The first two can be read from the contract; the third is governance risk from Chapter 24.
Three Treasury Questions
Negative net revenue does not mean the protocol will die, provided it has funds to burn. The treasury is therefore the final part of the model:
| Question | How to check | What an absent answer means |
|---|---|---|
| What is inside? | Assets in treasury addresses: stablecoins, major assets, and the protocol's own token | A treasury that is 90% its own token has much less spendable value than book value |
| How long can it last? | Available assets ÷ monthly net outflow | If you cannot calculate it, you have not established net outflow |
| Who can move it? | Multisig threshold, timelocks, and governance procedures | These are the Governance and Operational categories of the risk model |
The second question has a specific calculation worth writing down:
Cash runway in months = Spendable treasury assets excluding own tokens ÷ Average monthly net outflowThe numerator must exclude the protocol's own token because selling it depresses its price. Runway calculated from treasury book value is often several times the real figure.
Four Quadrants
Cross positive or negative net revenue with high or low incentives to get four kinds of protocol:
| Low incentives relative to fees | High incentives relative to fees | |
|---|---|---|
| Positive net revenue | The business works. Ask where growth comes from | Profitable even while subsidizing. Ask how much would disappear without subsidies |
| Negative net revenue | The take rate is too thin or scale too small. Ask whether it can rise | Printing tokens to buy scale. Ask how long the treasury lasts and what the spending has achieved |
The bottom-right quadrant is the industry's most common and the one most in need of an honest description. Being there is not inherently wrong—using incentives to bootstrap activity can be reasonable. Chapters 28 and 30 explain when it works.
The problem is that it is often presented as the top-left quadrant. Distinguishing them only requires calculating the fourth line of the income statement.
What It Is Called
The total amount users pay to use the protocol.
Chapter 23 already defined it. Add one usage rule here: whenever you cite this number, immediately explain how it is divided. In most trading protocols, most fees are distributed to liquidity providers; the protocol keeps only a small fraction.
Calling fees revenue is the industry's most common, and most easily exposed, exaggeration—one question is enough: which address received the money?
The portion of fees the protocol itself can control.
“Control” is the key: the money must reach an address whose spending the protocol can decide. Some protocols distribute all fees immediately and retain nothing. Their protocol revenue is zero, however large total fees are.
There is another fork: who controls it? It might enter a multisig-controlled treasury, be distributed to stakers by rule, or enter a contract only governance can access. “The protocol earned money” has very different implications for token holders in these three cases—this is value capture from Chapter 20.
Token rewards the protocol distributes over a period.
One property makes people complacent: no cash leaves during that period. The protocol prints and distributes tokens, and its cash balance does not fall. It is easy to exclude this from costs, and the resulting number always looks good.
But the cost is real and borne by all token holders through dilution, as Chapter 20 explains. Record two things together: how many tokens were issued (unaffected by price), and their value at contemporaneous prices (comparable, but sensitive to token prices).
Together, these answer how much the protocol spends to buy growth.
Funds the protocol can control.
Three essential checks: which assets it holds (list its own token separately), how long it lasts (non-own-token assets divided by average monthly net outflow), and who can move funds (multisig thresholds, timelocks, and governance procedures).
A common misreading treats treasury size as protocol value. It is closer to a company's cash reserves—important, but a measure of how long the company can survive, not what it is worth.
The protocol's retained share as a proportion of total fees paid by users.
It is the shortest way to compress a business model into a number and supports comparisons: if two protocols in the same sector have take rates differing threefold, there must be a structural reason. Find it.
Higher is not automatically better. The take rate is the result of how the protocol and supply side divide proceeds. Take too much and liquidity providers leave, removing the fees themselves. Understanding the take rate means understanding the protocol's bargaining relationship with suppliers.
Hands-on
Fill the five-line income statement, and be able to point to a source for every line.
Choose a protocol with a clear fee mechanism and current or past token incentives. Without incentives, the calculation is too simple to teach this lab's main lesson.
Consider doing this in two sessions: the first four steps in one, and the final three in the other.
Write definitions before collecting data.
Use the six questions from Chapter 23, adding three specific to this chapter:
Revenue share source: Contract parameter … (record its name and observed value), not documentation claims
Incentive accounting: Record quantities issued and a separate series valued at daily average prices
Time window: The most recent 90 complete calendar days, UTCThe revenue-sharing ratio is the easiest place to make a mistake. Documentation describes design intent; contract parameters show the currently effective value. They often differ.
Collect the first number: total fees paid by users.
This is the easiest figure to obtain, with ready-made fields on most data platforms. Confirm its coverage: does it include deployments on every chain? Does it include all protocol versions?
Download 90 days of daily data and sum them. Also record the contracts and chains covered, because that sentence must appear in your conclusion.
Collect the second number: the protocol's retained share.
Take both routes.
Route one, top-down: multiply total fees by the sharing ratio. Fast, but biased if fee rates vary across trading pairs or assets.
Route two, bottom-up: find the fee-collection address and total assets flowing into it over the 90 days. Slower, but first-hand evidence.
Compare the results. If they differ by over 20%, investigate, usually for a missing fee address or fee tier. The discrepancy itself is a finding.
Collect the third number: incentives spent during the period.
This is the hardest step because the figure usually appears on no dashboard. Three ways to find it:
| Method | What to do |
|---|---|
| Distribution contracts | Find the incentive distribution contract and total token outflows over 90 days |
| Governance proposals | Forums usually contain proposals and votes specifying weekly distributions |
| Work backward from supply changes | Subtract scheduled unlocks from changes in circulating supply; the remainder may be incentives |
Use at least two methods independently and investigate discrepancies. The third is least accurate and should only check the order of magnitude.
Convert quantities to money by multiplying each day's distribution by that day's average price, then summing. Do not multiply the whole quantity by the closing price—large price changes over 90 days can make the two methods differ severalfold.
Complete the statement and calculate the net amount.
Total fees paid by users ____________ Source:
− Supply-side share ____________ Source:
= Protocol share ____________
− Incentive spending, in money ____________ Source:
= Net revenue ____________
Effective take rate = Protocol share ÷ Total fees = ______
Incentive coverage = Protocol share ÷ Incentive spending = ______The last ratio, incentive coverage, is particularly useful: above 1 means protocol earnings cover its incentives; below 1 means they do not. It is better suited to comparing protocols than absolute net revenue.
Plot two daily curves together: protocol revenue and incentives valued at that day's prices. See whether the gap grows or shrinks, and investigate days with sudden incentive spikes. The chart cannot show where revenue would go if incentives dropped to zero; that is Chapter 28's question.
Add the treasury and calculate runway.
Find treasury addresses and list their assets, with the protocol's own token on a separate line.
Runway in months = Spendable assets excluding own tokens ÷ Average monthly net outflowIf net revenue is positive, write “Not applicable: net inflow this period.” If negative, this runway is one of the protocol's most important numbers.
You now have a five-line income statement, two ratios, two curves, a runway, and a source for each item.
You can apply this unchanged to any protocol, and repeat it next quarter for comparison. The business-model section of your capstone is the output of this lab.
AI Lab
Complete the previous lab yourself first. The value here lies in comparison—without your own numbers, you have no baseline.
This task has a useful training property: answers need not be unique, but definitions must be explicit. A single protocol can have three legitimate revenue numbers (the opening scenario of Chapter 23). The test is therefore not merely whether its number is correct, but whether it explained which number it was calculating.
Document revenue for <protocol name> over the most recent 90 days.
Part one: do not give numbers yet. First produce a definitions document:
1. Total user fees: covered contracts, chains, and versions
2. Supply-side share: source contract parameter, its name, and current value
3. Protocol share: destination address and who controls it
4. Token incentives: distribution contract, counting method, and valuation prices
5. Time-window boundaries
Part two: report these five lines, citing a source for each:
Total fees paid by users
− Supply-side share
= Protocol share
− Incentive spending during the period
= Net revenue
Part three: calculate two ratios: effective take rate, and protocol share divided by incentives.
Part four: separately list:
- What this analysis does not cover
- Which figures have explicit sources, and those sources
- Which figures you could not obtain
Rules:
- Cite every contract address and parameter name.
- Write “could not obtain” for unavailable figures; do not invent plausible values.
- Timestamp all collected figures.Then do two things: verify its contract addresses and parameters, and place its five-line figures beside the official dashboard's numbers.
Differences fall into three bands, pointing to different causes: a few percentage points usually suggest time boundaries or exchange rates; severalfold differences almost certainly mean different definitions (one counts total fees, another the protocol share); opposite signs mean one includes incentives and the other does not, precisely this chapter's core issue.
Models make four frequent errors here, ordered by danger:
- Omitting incentive spending entirely. The most common and expensive error. The attractive revenue report describes line three, not line five.
- Treating fees as revenue. Failing to separate total user payments from the protocol share can inflate the figure severalfold.
- Copying sharing ratios from documentation. Documentation expresses design intent; contract parameters show current settings. Models almost always copy the documentation.
- Valuing all incentives at the period's closing price. With volatile prices, this can differ severalfold from daily valuation, in either direction.
For an advanced exercise, request all three revenue definitions for the same protocol—total fees, protocol share, and post-incentive net revenue—side by side. Once you see all three, any isolated quotation becomes suspect, which is exactly the reflex to develop.
Verify these points yourself after using AI
- Did its sharing ratio come from contract parameters or documentation? They often differ
- Did it clarify whether revenue means total user fees, the protocol share, or the net amount after incentives?
- Most importantly, did it include incentive spending? Omitting incentives is the most common gap in this task
- Did it record incentive quantities or monetary values? Which dates supplied the conversion prices?
- Did it cover deployments on multiple chains and multiple versions, and disclose omissions?
- Have you checked its contract addresses and parameter names in a block explorer?
- What are the numerator and denominator of its take rate? Do they match your definition?
- How far do its numbers differ from the official dashboard? Did it explain or ignore the difference?
Real-World Case
A protocol attracts liquidity with token incentives, reaching near the top of its sector by TVL within weeks. Incentives decline as scheduled; in the week they expire, TVL returns close to its starting point within days.
Compare the two curves across this period: they almost perfectly track each other. The dollar value of incentives and TVL follow the same shape.
The industry has a familiar description for these funds: they follow yield, not the product. They are not enemies—they serve a real purpose during bootstrapping. Chapter 15 explained what a shallow pool means for users.
But TVL created this way is not evidence of product acceptance. The only way to distinguish them is to see how much remains after incentives stop, which Chapter 28 turns into a standard procedure.
A protocol ranks highly on public measures: substantial fees, many users, and a strong brand.
Complete its five-line statement and line five is substantially negative: the protocol keeps only a fraction of fees, while incentive spending is comparable to total fees.
This is not automatically bad news. Spending to gain scale is a clear strategy; the question is whether it is explicitly described. A team that knows its monthly net outflow, treasury runway, and the retention of users it paid to acquire is executing a strategy.
If it displays only lines one and three and never mentions line four, that is different. Distinguish these situations by checking whether its governance forum discusses line five, rather than guessing motives.
Many protocols launch with a zero fee switch: all fees go to the supply side, and the protocol retains nothing. Early liquidity requires the most attractive terms.
After some time, someone proposes enabling the switch in the governance forum. Discussion typically reveals the same tension:
- Supporters say the protocol needs revenue for long-term operations and value capture.
- Opponents say the take will reduce suppliers' returns and may send them to other protocols.
Both are right. This is why the take rate is a bargaining outcome rather than a freely chosen parameter.
These proposals are excellent research material: revenue structure, sharing ratios, supply-side mobility, and competition all appear in public discussion. A governance forum often explains how a protocol earns money better than its documentation does.
A protocol announces a treasury of approximately $100 million, seemingly ample reserves.
Inspect the assets: 90% is its own token valued at the market price. The remaining 10% is stablecoins and major assets.
The valuation is not necessarily wrong—at current prices, $100 million is accurate. The problem is the assets cannot be realized at that price: selling even part depresses the price, and awareness of protocol selling accelerates the process.
For runway, use only the remaining 10% in the numerator. The same treasury has $100 million on paper and $10 million available. At a $1 million monthly net outflow, runway is 10 months, not 100.
This difference can change every team decision, and a simple list of assets in treasury addresses reveals it.
Change One Variable
The accounts immediately look worse: actual cash leaves, and negative net revenue directly reduces the treasury balance.
But three things improve. Costs become honest: cash spending replaces dilution, making it impossible to ignore. Costs become bounded: only the stablecoins in the treasury can be distributed, whereas token printing theoretically has no limit. Recipients receive something that does not depreciate on its own, so the same spending can buy more behavior.
The trade-off is obvious: cash burns quickly, and rising token prices no longer expand the incentive budget during upswings.
This variable's greatest value is that it translates the cost into another form. If a team is unwilling to distribute the same value in stablecoins, it is admitting uncertainty about how real that expenditure is. Everyone designing incentives should ask themselves this question.
Incentive spending valued at contemporaneous prices drops sharply, so net revenue can turn positive without the protocol doing anything.
This is not a mistake but an inherent property of the definition, the same issue discussed in Chapter 23. Use the same response: show two curves, one in token quantities and one at contemporaneous prices.
There is a more important second layer: falling prices weaken incentives. The same quantity becomes 70% less attractive to recipients. Maintaining the behavior requires issuing more tokens, accelerating dilution and putting further pressure on price.
The feedback loop from Chapter 21 runs in reverse here. A protocol heavily dependent on token incentives has a cost structure tied to its token price, with effects amplified in the same direction.
Its retained share rises in the short term by arithmetic. Three things begin changing simultaneously.
Suppliers' actual returns fall. If liquidity providers can get better terms elsewhere, some funds leave. How much depends on other value this protocol offers them—whether fee income is all they care about.
Users may barely notice, or notice strongly. Redistributing an existing fee leaves user payments unchanged; but if suppliers leave, depth falls, and slippage rises, users may leave too. Chapter 15 explained how depth shapes experience.
Competitors react. The take rate is a public price, not merely an internal parameter.
The right question is therefore not how high to raise it, but how high it can go before suppliers begin leaving. There is no formula; you must experiment. The cost of error is asymmetric: raising the rate is easy, but lowering it does not necessarily restore trust.
The first four lines are zero, and so is line five. This is not an erroneous state; it means the protocol does not sustain itself through its own earnings.
What sustains it? Three common answers: funding, ongoing foundation support, or a company subsidizing it from another business. All are legitimate, but move the focus of research—Capital changes from background information to a lifeline, as Chapter 25 discussed.
Now ask how much remains, who decides how to spend it, and what happens if it stops.
There is a more interesting question, the subject of Chapter 30: if people use a protocol with no fees and no token, it is solving a real problem. A revenue model can come later; demand cannot. A zero here is not necessarily bad news—provided the claim that people use it survives Chapter 28's validation.
Takeaway Questions
This question becomes line one of the statement, with a requirement to trace the address: where does the money users pay end up, and who can move it?
Watch one particular situation: if the payer is the protocol itself, using tokens it prints, the actual payers are all holders. In data, this can look almost identical to real income. Reading contracts and governance records is the only way to distinguish them.
The full answer is the five-line statement, not one number.
Whenever you cite revenue, first say whether it is line one, three, or five. This habit makes your analysis more resilient to questioning than most industry material, which cites line one using line five's name.
Only after reaching line three does this question begin: how is the protocol's retained money connected to token holders?
Three possibilities: distribution to stakers under rules, a treasury capable of buybacks, or a multisig with no mechanism connecting proceeds to holders. The third is most common, formally called “value capture not established”—Chapter 20 explains how to identify it.
This chapter gives a calculable version: set incentives to zero, set the treasury's own tokens to zero, and ask what remains.
What remains—real fees, real suppliers, real users—is the business's foundation. If it is positive, token price fluctuations are noise. If it is zero, the token price is the protocol's lifeline itself.
Chapter Check
TVL has no direct relationship with revenue. Complete the five-line statement:
- Total fees paid by users: how many genuinely use it, and how much they pay.
- Subtract the supply-side share: read the ratio from contract parameters, not documentation.
- Equals the protocol's retained share: the money it can control.
- Subtract token incentives for the period: almost never shown in promotional materials.
- Equals net revenue: positive means earning; negative means buying growth.
TVL is merely an indirect upstream variable: it influences whether users come and how much slippage they face, but generates no money itself. Deposits do not generate revenue; usage does.
Also, TVL rises with asset prices. A 30% price rise can produce a 30% TVL rise, without another trade or another cent of revenue.
All holders bear the cost through dilution. The protocol prints and distributes tokens without reducing its cash balance, but every holder's proportional share shrinks.
This is the same as the market vouchers: printing costs nothing, but spending them exchanges them for real things belonging to others.
Record both together:
- Token quantity: unaffected by price, reflecting distribution intensity itself.
- Value at contemporaneous prices: comparable with revenue, but sensitive to token prices.
Quantity alone cannot answer how much was spent. Value alone produces a cost curve largely driven by token prices. Showing both is the only honest approach.
Three questions, in order:
- Which assets are inside? List its own token separately. A $100 million treasury that is 90% its own token is not $100 million of spendable money—selling depresses the price.
- How long can it last? Divide spendable non-own-token assets by average monthly net outflow. The denominator is the negative value of line five.
- Who can move it? Multisig thresholds, timelocks, and governance procedures. This belongs to Governance and Operational in Chapter 24.
Correct another common misreading: treasury size is not protocol value. It resembles corporate cash reserves, indicating survival time rather than valuation.
Not necessarily, but it means you must ask the next question.
Below 1 means earnings cannot cover distributed incentives, so the period has a net outflow. This is common and reasonable early on—bootstrapping through incentives is a strategy, not a mistake.
Distinguish executing a strategy from sustaining an illusion through three checks:
- Can you calculate treasury runway? If not, the team is not tracking it either.
- Where is the ratio heading? Quarterly improvement suggests the strategy works; stagnation or deterioration suggests purchased growth is not sticking.
- Have incentives stopped, and how much disappeared? This is the only empirical test. Chapter 28 turns it into a standard procedure.
A project answering all three understands its position even when losing money. With no answers, it is operating on inertia rather than strategy.
There is no standard answer. Check these points:
- Did you read the sharing ratio from contract parameters, or copy documentation? They often differ.
- Did you calculate the retained share using both routes, total fees times the ratio and inflows to fee addresses? How far apart were they?
- How did you find incentive spending? Did you cross-check at least two methods?
- Did you value incentives daily or at the closing price?
- What are your effective take rate and incentive coverage? Did you compare another protocol in the sector?
- Did you list the treasury's own tokens separately?
Most people spend longest on line four, incentive spending, because it is the only number without a ready-made dashboard. That is exactly why it matters: finding a number absent from every front page is the reason to do this research yourself.
Key idea
TVL ≠ Revenue,Volume ≠ Profit,User ≠ PMF。