Users deposit single assets into wrapper contracts. Flying Tulip deploys these deposits into automated yield strategies (e.g., Aave V3) across Ethereum, Sonic, BNB Chain, Avalanche, and Base, maximizing capital efficiency.

Flying Tulip is a multi-chain yield aggregation protocol that pools user deposits into wrapper contracts and deploys them into automated yield strategies. The protocol supports assets including USDC, wETH, USDT, USDS, USDTb, and USDe, and uses an omnichain FT token to align incentives across its five supported networks.

FT tokenholders own and govern the Flying Tulip protocol. Flying Tulip is a yield aggregation protocol backed by partnerships with major DeFi protocols.

website

twitter

Asset management

Flying Tulip

# Flying Tulip Fees Supply Side Methodology

## 1. Overview

Fees Supply Side measures the total interest paid by borrowers that is distributed to lenders through Flying Tulip Lend. Because the reserve factor is set to zero on-chain (team-confirmed), 100% of borrower interest flows to lenders as supply-side fees — no portion is retained by the protocol. This metric is denominated in the FT asset and converted to USD. Only Flying Tulip Lend generates a supply-side fee stream; Flying Tulip Yield and Flying Tulip USD retain 100% of their respective revenues as protocol revenue and carry no supply-side distribution.

## 2. Data sources

- **Blockchain events**: `EpochSettled` events from `PositionsManager` contracts, covering Ethereum and Sonic
- **External data**: End-of-day price feeds for the FT asset

## 3. Step-by-step calculation

### Component A: Epoch reward extraction

- **Purpose**: Capture the full interest distribution amount per epoch settlement
- **Logic**: `EpochSettled` events are parsed from `PositionsManager` contracts on Ethereum and Sonic. The `rewardAmount` field from each event is extracted and cast to a high-precision numeric type. Only non-removed events are included. Results are aggregated to daily granularity by summing all `rewardAmount` values within each calendar day, per chain.
- **Key fields**: `rewardAmount` (total FT interest distributed to lenders per epoch)

### Component B: USD conversion

- **Purpose**: Normalize FT-denominated reward amounts to USD for cross-asset comparability
- **Logic**: Daily aggregated reward amounts are joined to asset metadata to obtain decimal precision for the FT asset, and amounts are normalized by that decimal precision. Normalized amounts are then multiplied by end-of-day FT price feeds, joined on timestamp, chain, and asset address, to produce USD-denominated supply-side fees.

### Component C: Final aggregation

- **Purpose**: Produce the final per-day, per-chain supply-side fee totals
- **Logic**: USD-converted values are summed by timestamp, chain, and product (Flying Tulip Lend), yielding one row per day per chain. The Flying Tulip Lend product is the sole contributor to this metric; Flying Tulip Yield and Flying Tulip USD are excluded as they carry no supply-side distribution.

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

Portion of fees distributed to service providers or supply-side participants.

Flying TulipFT

Supply-side fees

Supply-side fees

Competitive landscape

Chain breakdown