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 Average fees per user (AFPU) Methodology

## 1. Overview

Average fees per user (AFPU) is measured as the average daily revenue generated per active user on the Layer3 infrastructure platform. This metric is calculated by dividing total daily fees by the count of active users (daily), providing insight into revenue efficiency and user monetization across products including cube mints, bridge services, and referral programs.

## 2. Data sources

- **Fees**: Derived from the Fees metric
- **Active users (daily)**: Derived from the Active users (daily) metric
- **Blockchain events**: `Transfer` events, `CubeClaim` events from `Cube` contracts, `EscrowRegistered` events from `Factory` contracts, and native asset transfers covering Ethereum, Arbitrum, Avalanche, Base, and 7 other chains
- **External data**: End-of-day price feeds for assets and native gas assets

## 3. Step-by-step calculation

### Component A: Fees collection

- **Purpose**: Aggregate all revenue streams flowing to Layer3 across multiple chains and products
- **Logic**: Token transfers to specific Layer3 wallet addresses are collected from five distinct revenue sources. For cube mint transactions, transaction fees paid by users minting cubes are extracted from native asset transfers. For B2B escrow revenue, transfers to registered escrow contracts are tracked. For cube revenue in L3 assets, transfers of the L3 asset to designated wallets are monitored. For bridge fees and referral revenue, transfers to designated bridge operation and referral program wallets are captured. Each revenue stream is categorized by product type (cube, b2b, bridge, referral) and business segment
- **Key fields**: `block_timestamp` for daily aggregation, `token_address` for price lookup, `amount` for fee values, `chain_id` for cross-chain tracking

### Component B: User identification
- **Purpose**: Count distinct active users (daily) across all Layer3 services and products
- **Logic**: Unique addresses are identified from six different interaction types with Layer3 services. This includes participants making payments to escrow contracts, bridge users paying bridge fees, referrers earning income, and reward recipients receiving payouts from escrow contracts. Addresses triggering `CubeClaim` events or receiving payments in L3 assets are also included. Each unique address is aggregated by day to determine the total count of active users (daily)
- **Key fields**: `user_address` for user identification, `block_timestamp` for daily boundaries

### Component C: Escrow contract registration

- **Purpose**: Maintain a registry of valid Layer3 escrow contracts for revenue filtering
- **Logic**: `EscrowRegistered` events are parsed from `Factory` contracts across all supported chains to build a comprehensive list of legitimate escrow addresses. This registry is used to ensure only transfers to verified Layer3 escrow addresses are recognized as revenue, with unrelated transactions being filtered out
- **Key fields**: `escrowAddress` parameter from events, `chain` for multi-chain tracking

### Component D: Primary wallet identification

- **Purpose**: Define primary operational wallets for revenue recognition
- **Logic**: Lists of primary operational wallets are maintained for each supported chain. These addresses represent the main revenue collection points for bridge operations, referral payments, and general revenue, and are used to filter relevant transfers from the broader token transfer datasets
- **Key fields**: Wallet addresses per chain and product

### Component E: USD conversion and final calculation

- **Purpose**: Normalize values to USD and calculate the average per user
- **Logic**: All fee amounts are normalized by decimal precision and converted to USD using end-of-day asset prices. Total daily fees (USD) are divided by the count of active users (daily) to calculate the final average fees per user (AFPU). Missing daily values are filled with zeros, and chain availability filters are applied to ensure data completeness

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

Layer3L3

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape