Chapter 20 · What Tokenomics Really Means
What must Tokenomics answer beyond an allocation pie chart?
- Capabilities practiced
- ResearchFinancial LiteracySystem Thinking
- Hands on
- Draw a protocol's money flow: users pay → protocol revenue → who receives it → what token holders get.
- AI Lab
- Have AI design two tokenomics models for the same protocol, one with value capture and one without. Compare their long-term outcomes.
A Real-World Problem
You open a project's Tokenomics page.
A polished pie chart assigns 20% to the team, 18% to early investors, 30% to an ecosystem fund, and 32% to community and airdrops. Small print states one billion tokens. An unlock chart follows.
That is the entire page.
What have you learned?
You know who receives the billion units and roughly when. Chapter 19 showed how to turn that into a 24-row schedule.
But the page leaves more basic questions unanswered:
- Why would a stranger buy the first token?
- Why keep holding rather than immediately sell?
- If the protocol earns money, how does that connect to my token?
- If newly issued tokens subsidize users, who pays for that subsidy?
The pie chart explains distribution; these questions explain value.
Many mistake the former for all of Tokenomics.
Thought Experiment
You design an on-chain market. The working product charges 0.3% per trade and earns $10 million annually, growing steadily.
You issue a token. Add one feature at each of five steps.
Step 1: only an allocation chart.
Issue 100 million units: team 20%, investors 18%, ecosystem 30%, community 32%.
Why would a stranger buy one?
The only current answer is expecting a higher future buyer. That can support prices, as Chapter 22 discusses, but it has no connection to your $10 million business.
Step 2: voting rights.
Holders vote on protocol parameters.
Who pays for a vote? People seeking influence. If votes merely change fees from 0.3% to 0.25%, few will pay much.
Voting rights are worth what they can control.
Step 3: introduce revenue.
The $10 million enters a multisig wallet.
How does it connect to holders?
It does not, unless a rule establishes that connection. Blockchains do not automatically link protocol income to a token; contracts or governance must do so explicitly.
Step 4: write the rule.
Allocate 50% of fees to quarterly token repurchases and burning.
Now $5 million in genuine annual buying demand enters the market and supply declines. Holders gain a reason independent of sentiment.
Step 5: include the other side.
You also issue eight million annual reward tokens to attract liquidity.
At current prices, these are worth $12 million.
Compare:
Value entering +$5 million (buyback and burn)
Value leaving −$12 million (new subsidy issuance)
───────────────────────────────────────────────
Net outflow −$7 million per yearThe token captures value but still dilutes holders on net.
This calculation is Tokenomics' core. The pie chart did not participate.
Your Decision
The protocol's $10 million annual fees sit in its treasury. How do you use them?
What Happens
No option is universally correct, but all reveal:
Tokenomics designs money flows, beyond initial distribution.
A pie chart is a static ownership photograph. Cash flow is a moving picture of payers, routes, and recipients.
Compare:
| Revenue use | Direct recipient | Diluted party | If it stops |
|---|---|---|---|
| Treasury retention | Whoever governance chooses | No direct dilution | Treasury remains a buffer |
| Buyback and burn | All holders proportionally | Nobody | Buying ends and supply stops shrinking |
| Staker distribution | Stakers | Non-stakers if funded by issuance | Staking falls; tokens unlock and sell |
| Growth subsidies | Incentivized users and LPs | All holders through issuance | Purchased activity disappears |
The middle columns ask: who pays, and who is diluted?
Protocols can repurchase and issue large rewards simultaneously. Users notice quarterly burns but often fail to calculate issuance.
Therefore ask more than whether value capture exists:
Does value enter faster than ownership is diluted?
Both rates are public and calculable. Comparing them completes much of the analysis.
Build a Model
Five questions describe a token's economic structure:
| Question | Meaning | What missing answers imply |
|---|---|---|
| Who receives it? | Distribution and timing | Chapter 19's schedule is the easiest part |
| Why hold? | Benefits of holding and costs of not holding | Price may rely entirely on sentiment |
| Why pay? | Real external payers | Revenue may come from new entrants |
| Who is diluted? | Issuance, unlocks, and rewards | Often skipped at substantial cost |
| How does value enter? | Mechanism linking income to tokens | No explicit mechanism means no link |
Connect them into cash flow:
- Users pay
- Protocol earns revenue
- Rules allocate it
- Treasury / buybacks / stakers / subsidies
- Holder gains or losses
Identify a contract function, parameter, or governance decision for every arrow. Unsupported arrows should be dashed and labeled "no explicit mechanism". Many diagrams break at the third arrow.
The other half comprises opposing loops.
Forward loop: users increase revenue; value reaches holders; holding becomes attractive; tokens stabilize; liquidity and partnerships grow; more users arrive.
Reverse loop: falling tokens shrink incentives; LPs leave; depth and experience deteriorate; users and revenue decline; tokens fall further.
Both use the same mechanism in different directions. Designing one also creates its reverse. Chapter 21 expands this to market cycles.
Remember an unintuitive principle:
A token's strongest support may come from what consumes it rather than what it earns.
Fees, collateral, staking locks, and burning remove supply from circulation. Recurring consumption can support demand more durably than a one-time buying reason.
What It Is Called
Initial division among teams, investors, foundations, ecosystem incentives, and communities.
The pie chart is the first Tokenomics question, not the entire model.
Scheduled release of allocated units, including cliffs and linear periods, covered in Chapter 19.
Its incentive role determines how long teams and early investors remain tied to the project.
Mechanisms connecting protocol-generated value to token holders.
Common forms: buyback and burn, revenue sharing with stakers, token-denominated fees, and collateral or security requirements.
The key is an explicit mechanism. Success implying price appreciation is a hope unless contracts or governance establish the connection.
Uses that remove tokens from circulation through fees, staking, collateral, burning, or long-term rights locks.
Its opposite is a Faucet: issuance, unlocks, and rewards. Healthy token economics needs sinks capable of matching its faucets, rather than no faucets at all.
A loop whose components reinforce one another.
Always simulate reversal: the same mechanism reinforces declines equally effectively. Chapter 21 expands this.
New circulating tokens reduce the share represented by each existing unit.
Sources include unlocks of existing allocations and newly created emissions.
Evaluate net effects: value inflow rate minus dilution rate. Examining only one side often misleads.
Hands-on
Choose a revenue-generating exchange, lending protocol, or perpetual platform. Produce a diagram and a number.
First arrow: user payments.
List trading fees, lending spreads, withdrawal fees, liquidation charges, and funding shares, recording rates and documentation pages.
Ask: does this come from a customer's pocket or another holder's pocket? Their economic meanings differ.
Second arrow: receiving address.
Find fee addresses in documents or contracts and inspect recent inflows.
Documents may claim one treasury destination while actual flows split three ways. Use on-chain evidence.
Third arrow: allocation rules.
Find splits, proportions, and authority. Are they hard-coded or decided quarterly?
Does a team or operating entity receive a share? Governance proposals often disclose what Tokenomics pages omit.
Fourth arrow: holder benefit.
For repurchases, find burn records and total the past 90 days.
For staking distributions, inspect contracts and amounts, distinguishing revenue from newly issued tokens.
If no mechanism exists, draw a broken arrow. That is a finding.
Calculate 90-day supply expansion.
Include emissions and unlocks and multiply by the period's average price.
Compare both directions.
| Past 90 days | Annualized | |
|---|---|---|
| Value entering: buybacks + distributions | ||
| Value leaving: emissions + unlocks | ||
| Net | ||
| Net ÷ market cap |
The final row provides a percentage comparable across protocols.
Compare your diagram with the official page. The page may cover only a corner of the full structure.
This diagram forms the stage project's core. Chapter 26 applies the method to net protocol revenue.
AI Lab
Describe a real protocol's business and revenues, then request:
Design two Tokenomics systems for this protocol:
A: explicit value capture.
B: governance only, with no value capture.
For each, state:
1. Token recipients and release timing
2. Reasons to hold and what non-holders lose
3. Who pays money into the system
4. Who is diluted and at what rate
5. The specific connection between revenue and tokens; write "none" if absent
Simulate three years with revenue tripling and with revenue falling 70%.
Explain every step rather than jumping to conclusions.
Identify the most likely failure point of each design.Find ambiguous claims, rather than simply selecting a preferred design.
Models often make A concrete while softening B with vague claims about governance's long-term value.
Mark every plausible statement that cannot become a contract rule. More such statements generally mean fewer actual mechanisms.
For advanced comparison, place B beside a real governance-only protocol. The experiment already exists.
Verify these points yourself after using AI
- Does the no-capture design honestly state that holders receive nothing?
- Can the capture mechanism actually be implemented in a contract?
- Does each design calculate dilution as well as inflows?
- Does it mislabel newly issued staker rewards as dividends?
- Can revenue assumptions be checked against real data?
- Does it show reasoning for long-term outcomes?
- Does it identify each design’s most likely failure point?
Real-World Case
Many protocols initially excluded revenue capture partly from regulatory caution.
Products could succeed and revenues grow while holders remained separated from that success, hoping for future governance distributions.
Some later activated sharing. No capture today does not mean never, but the connection truly remains absent until activation.
A repurchase announcement receives enthusiastic support.
Meanwhile, annualized liquidity issuance exceeds repurchases severalfold.
Net dilution continues, although announcements emphasize buybacks. This may reflect newsworthy decisions versus old recurring parameters rather than deliberate deception.
Calculate net effects yourself.
A staking interface quotes 40% from protocol rewards.
Contracts reveal all rewards are newly issued tokens, transferring share from non-stakers without protocol revenue contributing.
This can create an effective sink by locking tokens, but it is not a dividend.
Trace rewards to revenue or issuance. Interfaces look identical.
Some tokens rely on required transaction fees, validator security, or collateral rights rather than distributions.
Demand is recurring and linked to usage, increasing automatically.
Buybacks and payouts instead need decisions or votes. Rule-based consumption is harder to interrupt than discretionary distribution, a useful comparison dimension.
Change One Variable
An existing mechanism passes threefold value to holders.
Without one, tripled revenue still has no direct holder connection. The protocol becomes more valuable; the token may not.
Protocol and token value need an explicit bridge. Chapter 26 returns from the revenue side.
Dilution disappears and net inflow improves.
But issuance previously attracted users and liquidity. Stopping it can reduce depth, volume, and fee revenue.
Both outflows and inflows may shrink, requiring calculation rather than assumption. Chapter 28 measures the remainder.
Flexibility supports growth in strong conditions and holders in weaker ones.
But changing quarterly decisions are difficult to project long-term, and voting power may concentrate in a few addresses.
Chapter 24's Governance Risk asks whether a vote can redirect funds. Here it clearly can set their destination.
Usage creates required purchasing demand independently of decisions.
The cost is requiring new users to hold a volatile asset. Stablecoin payment with automatic conversion often follows, softening the originally rigid demand.
Capture strength and user friction often move along the same trade-off.
Takeaway Questions
Remove the token: does the protocol still function?
If yes, financing and distribution may be its main roles. State that honestly. Chapter 30 applies this to your own project.
Trace fees, spreads, and liquidation charges to specific payers.
Issuance itself is not revenue; it is dilution producing a paper figure. Chapters 17 and 26 explain the distinction.
The answer is either an explicit contract or governance mechanism, or none.
Project success alone is insufficient. Name and locate the mechanism, or record no explicit mechanism.
Tokenomics designs incentives.
Ask what users, LPs, and teams are encouraged to do. If any answer is sell quickly, that follows the design rather than a failure of character.
Chapter Check
It answers only who receives tokens, statically.
The other questions concern holding, paying, dilution, and value entry: ongoing flows absent from the chart.
If the page contains only allocations and unlocks, the remaining answers exist elsewhere or do not exist. Investigate which.
It assumes a bridge that may not exist.
Treasury income has no default holder connection. Repurchases, distributions, required token fees, or collateral rules must establish one.
Find that rule instead of inferring from success.
Trace its source.
Protocol revenue brings external funds, visible through transfers to distribution contracts.
New issuance gives stakers share diluted from others. It may be an effective sink but is not a dividend.
Inspect contracts or documents; the headline percentage cannot distinguish them.
Consumption is often rule-based while distributions are discretionary.
Fees, collateral, and security deposits arise automatically with use.
Repurchases and sharing depend on execution or governance and can be paused or changed.
Both capture value, but their resistance to interruption differs. Include that distinction.
Check:
- Were user payments copied from documents or verified on-chain?
- Does the diagram include outflows as well as inflows?
- Are unsupported connections dashed and labeled rather than invented?
- Is net value divided by market cap for comparability?
- Remove trading conclusions; the deliverable is a structural diagram.
The sticking point is useful information. Many get stuck at the third arrow, the rule allocating treasury revenue. Identifying that gap means the diagram is doing its job.
Key idea
Tokenomics answers who pays, who gets diluted, and how value flows into the token.