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 Fees Methodology

## 1. Overview

Fees measures the total value users pay to use Layer3 products and services. Revenue is aggregated from five distinct sources: cube minting, B2B escrow services, payments in the native L3 asset, bridge operations, and referral programs. All amounts are converted to USD using end-of-day price feeds. Token transfers to various revenue collection addresses are aggregated across 11 blockchain networks to determine the total economic value generated by the protocol.

## 2. Data sources

- **Blockchain events**: `CubeClaim` events from `Cube` contracts, `EscrowRegistered` events from `Factory` contracts, native asset transfers, and ERC-20 `Transfer` events, covering Arbitrum, Avalanche, Base, Blast, and 7 other chains
- **External data**: End-of-day asset price feeds and asset metadata including decimal precision information

## 3. Step-by-step calculation

### Component A: Cube minting fees

- **Purpose**: Captures fees paid in native assets (such as ETH, AVAX, or BNB) when users mint Layer3 cubes
- **Logic**: All cube minting transactions are identified by extracting `CubeClaim` events from `Cube` contracts across 10 chains. For each identified transaction, the native asset value is retrieved from the corresponding blockchain transaction records. Amounts are normalized by decimal precision. Price feeds are applied based on the specific chain, with Ethereum prices applied to zkSync Era transactions.
- **Key fields**: Transaction `value`, `block_timestamp`, `from_address`, and native asset addresses.

### Component B: B2B escrow service revenue

- **Purpose**: Tracks revenue from Layer3's B2B escrow services through asset transfers to designated addresses
- **Logic**: All asset transfers to primary wallets and registered escrow contracts (identified via `EscrowRegistered` events from `Factory` contracts) are monitored. Internal transfers originating from the protocol's internal escrow address are excluded. Transfers of any ERC-20 asset type are captured and joined with asset metadata to apply correct decimal precision.
- **Key fields**: Transfer `value`, `to_address` filtered to Layer3 addresses, `from_address`, and `token_address`.

### Component C: L3 token revenue collection

- **Purpose**: Tracks payments made specifically in the native L3 asset to designated collection wallets
- **Logic**: Transfers of the L3 asset (`0x46777c76dbbe40fabb2aab99e33ce20058e76c59`) to specific wallet addresses are monitored across 7 chains. Filters are applied to strictly include the L3 asset address only, representing revenue where customers pay using the native asset.
- **Key fields**: L3 asset transfer `value`, chain-specific collection wallet addresses, and the L3 asset address constant.

### Component D: Bridge operation fees

- **Purpose**: Captures fees generated from Layer3's bridge services
- **Logic**: Asset transfers to specific bridge operation wallet addresses (`0x399cf1ca9b8dcc369ee3bb2a6516144de43e506d` and `0x7225b33c16fba2dcb38b0acbcc562a72ef576a6b`) are tracked across 9 chains. Transfers of any asset type to these addresses are captured, representing fees collected from users of the cross-chain bridge services.
- **Key fields**: Transfer `value`, bridge wallet addresses, and `token_address`.

### Component E: Referral program revenue

- **Purpose**: Tracks revenue generated through Layer3's referral program
- **Logic**: All asset transfers to the designated referral wallet address (`0x98d62dd170d9b8979bddb98ae6bb6f7640a82ad3`) are monitored across 11 chains. Transfers of any asset type to this address are captured, representing revenue from referral activities and partnerships.
- **Key fields**: Transfer `value`, referral wallet address, and `token_address`.

### Final aggregation

- **Purpose**: Combine all revenue sources and normalize to USD
- **Logic**: Fees from all five components are combined and grouped by day, chain, and product type. All amounts are normalized by decimal precision and converted to USD using end-of-day price feeds. Daily granularity is maintained using UTC day boundaries, and zero-filling is applied to ensure time series continuity across all supported chains.

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

Total value users pay to use a protocol (gross fees, user-paid fees).

Layer3L3

Fees

Fees

Competitive landscape

Chain breakdown