ETH: SushiSwap Fees, Supply Side and Revenue [USD]
Ethereum SushiSwap: Fees, Supply Side and Revenue: daily data through 8 Nov 2026.
The fees users paid to SushiSwap on Ethereum each period, split into the part paid out to liquidity providers (the supply side) and the part SushiSwap kept (revenue).
Why use it. Fees show how much the protocol is used and paid for; revenue is what it earns for itself, the figure its token's value is usually measured against. A growing gap between them means more of the money goes to liquidity providers. How to read it. The fees line is the total; supply side plus revenue add up to it. Read the trend over weeks rather than single hours: trading volume and the fee tiers traders use move the lines.
Calculation. Fees are what users pay to use a protocol: interest paid by borrowers, swap fees paid by traders, rewards earned by staked ether. The supply side is the part paid out to whoever supplies the capital (lenders, liquidity providers, stakers); revenue is the rest, what the protocol keeps; the take rate is revenue divided by fees. Decentralised exchanges (Uniswap v2, v3 and v4, SushiSwap v2): every trade's fee is its value x its fee rate, the value being the side priced as in the DEX volume charts (dollar stablecoins at face value, ether and wrapped bitcoin at CryptoKeyhole's hourly prices; trades with neither are not counted). Rates: 0.3% on Uniswap v2 and SushiSwap pairs, the pool's fee tier on Uniswap v3, and on Uniswap v4 the rate each Swap event reports. The protocol's part: 1/6 of the 0.3% on SushiSwap since 9 September 2020 and on Uniswap v2 since 27 December 2025 (when each factory's fee recipient was set); on Uniswap v3 the pool's protocol fee setting (1/4 or 1/6 of the fee), read from the pool at the end of each range of about 50 blocks; on Uniswap v4 the part of the swap fee above the pool's liquidity-provider fee (pools whose hook sets the fee show no protocol part). The rest goes to liquidity providers. SushiSwap v2 on Ethereum; its other networks and pool types are not counted. Ethereum mainnet deployments only: each protocol's other networks are not counted, so these are lower than the protocols' worldwide totals. Hourly values: each completed UTC hour once its blocks are final on our node, so the latest hour shown ended one to two hours earlier; a day is the sum of its 24 hours, and the open day is a partial through the latest hour.