Users complete Quests, Races, or other experiences to earn rewards.

Layer3 is a platform that allows anyone to discover web3 through interactive experiences.

L3 tokenholders own and govern the protocol. L3's investors include ParaFi Capital, Greenfield Capital, etc.

twitter

discord

website

Infrastructure

Layer3

# Layer3 Revenue Methodology

## 1. Overview

Layer3 revenue is measured as the total USD value of payments received by Layer3 across all revenue streams and supported blockchain networks. The metric captures revenue from cube minting fees, B2B escrow services, bridge operations, referral programs, and direct L3 token payments. Revenue is calculated by aggregating token transfers to designated wallet addresses and converting them to USD using end-of-day price feeds.

## 2. Data sources

- **Blockchain events**: `Transfer` events, transaction records, `EscrowRegistered` events from `Factory` contracts, and `CubeClaim` events from `Cube` contracts, covering Ethereum, Arbitrum, Base, Polygon, and 7 other chains
- **External data**: End-of-day price feeds for native gas assets and other tokens

## 3. Step-by-step calculation

### Component A: Cube mint transaction fees

- **Purpose**: Gas fees from transactions that mint Layer3 cubes are captured.
- **Logic**: Cube minting transactions are identified by finding all `CubeClaim` events from `Cube` contracts across supported chains. Corresponding transaction records are retrieved for these mints to extract the native token gas fees paid. Gas fee amounts are calculated using transaction `value` fields and normalized by decimal precision.
- **Key fields**: `block_timestamp`, `transaction_hash`, `value` (gas fee amount), native token addresses per chain

### Component B: B2B escrow revenue transfers
- **Purpose**: Token payments to B2B escrow services are tracked.
- **Logic**: Token transfers to designated primary wallets and dynamically registered escrow contracts are monitored. Escrow contracts are identified through `EscrowRegistered` events from `Factory` contracts. Transfers from the internal escrow address `0x584c038a2da87a2fe4253483a9d7595ba8d10785` are excluded to avoid double-counting.
- **Key fields**: `block_timestamp`, `from_address` (user), `to_address` (Layer3 wallet), `token_address`, `value`

### Component C: Cube revenue paid in L3 tokens

- **Purpose**: Revenue from cube services paid directly in L3 tokens is captured.
- **Logic**: Transfers of the L3 token `0x46777c76dbbe40fabb2aab99e33ce20058e76c59` to designated Layer3 wallet addresses are tracked on Base, Optimism, BSC, zkSync Era, Avalanche, Polygon, and Arbitrum. Only transfers where both the asset address matches the L3 token and the recipient matches the designated chain-specific wallet are included.
- **Key fields**: `block_timestamp`, `from_address` (user), specific L3 token address, designated wallet addresses per chain, `value`

### Component D: Bridge fees

- **Purpose**: Fees from cross-chain bridge operations are captured.
- **Logic**: Token transfers to designated bridge wallet addresses are monitored across Arbitrum, Avalanche, Base, Blast, BSC, Ethereum, Optimism, Polygon, and zkSync Era. All token types transferred to these bridge addresses are included.
- **Key fields**: `block_timestamp`, `from_address` (user), bridge wallet addresses, `token_address`, `value`

### Component E: Referral revenue

- **Purpose**: Revenue from the referral program is tracked.
- **Logic**: Token transfers to the referral wallet address `0x98d62dd170d9b8979bddb98ae6bb6f7640a82ad3` are monitored across 11 chains including Ethereum, Arbitrum, Base, and Polygon. All token types transferred to this specific address are captured.
- **Key fields**: `block_timestamp`, `from_address` (user), referral wallet address, `token_address`, `value`

### Component F: Aggregation and USD conversion

- **Purpose**: Revenue streams are combined and normalized to USD.
- **Logic**: All revenue streams are combined using union operations. Token amounts are normalized by decimal precision and converted to USD using end-of-day price feeds. Daily revenue is the sum of all USD-converted transfers across all components, with daily aggregation performed using UTC day boundaries. Any missing days are filled with zero values.

*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.

Layer3L3

Revenue

Revenue

Competitive landscape

Chain breakdown