Protocol Revenue (30d)

Most fees are not kept: on a decentralized exchange the bulk of each swap fee goes to liquidity providers, and on a proof-of-stake chain most gas goes to validators. Protocol revenue is what remains for the protocol treasury, a token burn, or a distribution to stakers, depending on how the contracts are configured. For blockchains, the term is used inconsistently and often refers to the portion of fees destroyed by a burn mechanism such as the EIP-1559 base fee.

How it is computed

protocol fees over the last 30 days - supply-side revenue over the last 30 days

Where it misleads

There is no accounting standard behind the word revenue here: one provider treats Ethereum's burned base fee as revenue while another treats validator income as revenue and the burn as neither, so the same chain can show figures that differ by an order of magnitude. Treasury inflows frequently include one-off items such as grants, token sales to investors, or bridge rebates that are not recurring and are not user fees at all. Where a fee switch exists in the code but governance has left it off, revenue reads near zero even though the fee mechanism is fully built. Revenue received in a protocol's own governance token is marked at the spot price and may not be realizable at that mark in any size.

The equity comparison, and why it fails

Net revenue or gross profit. The analogy fails because there is no cost of goods sold inside the number, no obligation on anyone to distribute it, and a governance vote can change the split overnight in a way no income statement permits.

Reading a high or a low value

A higher figure means more fee income was retained at the protocol level over the month. The level is driven as much by how the contracts are configured as by how much users transacted.