Why
Security is not free and it is not a property of the code — it is a payroll. A proof-of-stake chain is secure because attacking it costs more than it yields, and that cost is maintained by paying validators enough to keep capital staked. That payment is the security budget, and like any payroll it has to be funded from somewhere.
There are only two sources, and the difference between them is the whole card. Either users pay, through transaction fees, or holders pay, through issuance that dilutes them. Both are legitimate at different stages — a young chain funding security by issuance is doing something perfectly normal. The problem is that the two are reported as though they were one, and the resulting number is called revenue.
So the ratio to compute is fee revenue over security budget, and it answers a question no other metric does: is this chain a business or a subsidy? A ratio near one says the network is self-funding: people value the block space enough to pay for the protection of their own transactions. A ratio near zero says the chain is being kept alive by the token, and the token is being kept alive by expectations. Neither is a verdict — but the second is a clock, because issuance schedules are finite and expectations are not contractual.
This ratio also disciplines a comparison that is otherwise unfalsifiable. Chains are usually ranked by TVL, which gross-over-net shows is often a leverage multiple, or by transactions per second, which measures a capability rather than a demand. Fee revenue over security budget cannot be inflated by looping, cannot be inflated by cheap blockspace, and cannot be inflated by a partnership announcement. It is the closest thing to an income statement the sector has, and its absence from every comparison table is conspicuous.
One nuance keeps it honest: a low ratio is not automatically bad, and a high one is not automatically good. Extremely cheap fees are a deliberate product decision that can be the right one — a chain optimising for volume may want fees near zero and fund security another way. The claim is only that the choice should be visible. Right now it is not, and monad-last-general-purpose-l1 is the worked example: a fee yield around 0.12% against a nearly $1B TVL is not a scandal, it is a sentence about what is actually being sold.
How it works
The two funding sources
| Source | Who pays | What it signals | Sustainable? |
|---|---|---|---|
| Transaction fees | Users | Block space is worth paying for | Yes — it is revenue |
| Token issuance | Holders, by dilution | The chain is buying its own security | Bounded — schedules end |
The ratio, and how to read it
| Fees ÷ security budget | Reading |
|---|---|
| > 1 | Users fund security and there is surplus — a business |
| ≈ 1 | Self-funding. The interesting threshold |
| 0.1 – 0.5 | Meaningful demand, still substantially subsidised |
| < 0.05 | Holders are paying for nearly all of it |
Why it beats the usual comparisons
| Metric | Can be inflated by |
|---|---|
| TVL | Recursive looping (gross-over-net) |
| Transactions per second | Cheap or free blockspace; it measures capability, not demand |
| Announced partnerships | Nothing at all — logos are not volume |
| Fees ÷ security budget | Nothing on that list |
How to build the table
- Fee revenue: what users actually paid, annualised. Exclude anything rebated back to them.
- Security budget: validator or miner compensation, annualised, at market value including newly issued tokens — issuance is the part usually left out, and it is usually the larger part.
- Divide, and also record fees ÷ TVL alongside, which is the demand-side version from
where-yield-comes-from. - Rank. Publish the ranking, because nobody else does.
The nuance that keeps it fair
A deliberately near-zero fee is a strategy, not a failure. Some chains want fees at the floor and intend to fund security another way — through an issuance budget treated as a capital expense, or through an operator who benefits elsewhere. The objection is never to the choice; it is that the choice is invisible in every metric currently published. Read with choosing-a-chain-is-a-lease, since a chain that cannot fund its own security is one whose terms will have to change.
Where it lands in Jayverse
- Devnet: this ratio doesn't apply on Anvil, but track it once on the OP-Stack L2. When Devnet becomes an actual L2 with a sequencer, compute fee revenue over sequencer/validator cost so the chain's self-funding status is visible from day one, not discovered later.
- Verex: publish fee revenue as its own line, not blended with anything else. Verex's trading fees are the "users pay" side of this ratio; keeping that number separate and visible is what would let Jayverse services be judged by the same honest standard this page asks of chains.
- OFA: price the solver auction's fee capture against what it costs to run. The same fees-over-cost discipline applies to OFA's solver competition — track whether auction fees actually cover the infrastructure needed to run it before treating the mechanism as self-sustaining.
Key expressions
| Expression | 뜻 · 쓰이는 자리 |
|---|---|
| income statement | 손익계산서 · 체인의 수익성을 비유적으로 설명할 때 쓰는 재무 용어. "the closest thing crypto has to an income statement" |
| through dilution | (지분·토큰) 희석을 통해 · 신규 발행으로 기존 보유자 가치가 줄어드는 방식을 말할 때. "holders are, through dilution, and the gap" |
| it is a payroll | 급여 지급과 같다(비유) · 보안 비용을 인건비에 빗대어 표현할 때. "it is not a property of the code — it is a payroll" |
| self-funding | 자체 조달되는, 스스로 자금을 대는 · 사용자 수수료만으로 운영비를 충당할 때. "the network is self-funding" |
| leverage multiple | 레버리지 배수 · 지표가 실제보다 부풀려졌을 때 쓰는 금융 용어. "is often a leverage multiple" |
| capital expense | 자본적 지출 · 발행 비용을 투자로 간주해 회계 처리할 때. "treated as a capital expense" |
| conspicuous | 눈에 띄게 두드러진 · 어떤 지표가 이상하게도 빠져 있음을 지적할 때. "is conspicuous" |
| a clock | 시한, 카운트다운(비유) · 유한한 자원이 언젠가 소진됨을 경고할 때. "the second is a clock, because issuance schedules are finite" |
| fund ... another way | 다른 방식으로 비용을 조달하다 · 수수료가 아닌 다른 수단으로 비용을 댈 때. "intend to fund security another way" |