DeFi Saver aggregates multiple DeFi protocols and users perform different strategies through DeFi Saver.

DeFi Saver is a non-custodial DeFi aggregator built on Ethereum. DeFi Saver was founded by Nenad Palinkasevic & Andrej Cvoro and launched in 2019.

DeFi Saver team & investors own and govern the protocol. They currently take all of the total trading fees paid by traders (revenue).

github

twitter

discord

website

Infrastructure

DeFi Saver

# DeFi Saver Revenue Methodology

## 1. Overview

DeFiSaver revenue measures the total daily USD value of fees collected by DeFiSaver's asset management platform across Ethereum, Arbitrum, and Optimism networks. This metric tracks revenue generated from DeFiSaver's yield aggregation services by monitoring token transfers to designated fee receiver addresses. The calculation identifies all inbound token transfers to these addresses, converts them to USD, and aggregates them daily to provide a comprehensive view of platform revenue.

## 2. Data sources

- **Token transfer events**: Parsed ERC-20 `Transfer` events from Ethereum, Arbitrum, and Optimism networks, specifically filtering for transfers where DeFiSaver fee receiver addresses are the recipients
- **Token metadata**: Token contract information including decimal places for proper amount calculation
- **End-of-day price feeds**: Daily closing prices for token-to-USD conversion
- **Chain availability data**: Network operational status for filtering results by chain availability

## 3. Step-by-step calculation

### Component A: Fee collection identification
- **Purpose**: Identify all token transfers representing DeFiSaver fee collection across supported networks
- **Logic**: Extract all ERC-20 token transfers where the recipient address matches DeFiSaver's designated fee receiver addresses. For Ethereum, the fee receiver is `0x6467e807db1e71b9ef04e0e3afb962e4b0900b2b`. For Arbitrum and Optimism, the fee receiver is `0x76720ac2574631530ec8163e4085d6f98513fb27`. Only successful transfers are included by filtering out any transfers marked as removed. Each transfer is classified with business metadata: 'Asset Management' as the business line, 'asset_management' as the market sector, 'yield_aggregator' as the business segment, and 'v1' as the version
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for unique identification, `to_address` as the fee receiver, `chain` for network identification, `token_address` for the specific token, and `value` as the transfer amount

### Component B: Revenue standardization and conversion
- **Purpose**: Standardize raw token transfer amounts into comparable USD values with proper time aggregation
- **Logic**: Aggregate identified fee transfers by truncating timestamps to daily boundaries. Apply decimal correction using token metadata to convert raw token amounts to their proper decimal representation. Convert corrected token amounts to USD using end-of-day price feeds. Fill any missing dates with zero values to ensure complete daily time series coverage. Apply project metadata population to add consistent labeling across all records
- **Key fields**: `timestamp` truncated to day level, `revenue` as the corrected and USD-converted amount, dimensional fields including `chain`, `business_line`, `market_sector_id`, `business_segment_id`, `product_id`, `version`, `account_address`, and `token_address`

### Final aggregation
- **Combining components**: Sum all USD-converted fee transfers by timestamp, chain, and other dimensional attributes to produce daily revenue totals for each combination of dimensions
- **Currency conversion**: Apply end-of-day USD conversion rates to each token type, ensuring consistent valuation timing across all transfers
- **Time aggregation**: Group all transfers within each calendar day boundary, creating daily revenue snapshots
- **Final calculation**: The final revenue value represents the sum of all USD-converted token transfers received by DeFiSaver fee receiver addresses on each day, filtered by chain availability to only include results from operational networks

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

DeFi Saver

Revenue

Revenue

Competitive landscape

Chain breakdown