Lens provides a full-stack platform combining Lens Chain for blockchain infrastructure and Lens Protocol for modular social primitives. Lens Chain offers instant transaction settlement with stable, low costs powered by GHO, backed by Ethereum security. Lens Protocol provides smart accounts with signless and gasless functionality, customizable usernames, graphs, feeds, and groups.

Lens is the full-stack platform for social and financial experiences, enabling developers to build SocialFi applications on-chain. The platform features Lens Chain as its blockchain infrastructure layer optimized for speed and scalability, and Lens Protocol for composable social primitives including accounts, usernames, graphs, feeds, and groups. Lens simplifies onchain adoption through portable data, simple onboarding via email or phone, and settlements in the USD-native stablecoin GHO.

Lens is built by the Aave team and is currently overseen by a multisig.

github

twitter

discord

website

Social

Lens

# Lens Average fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average daily fee revenue generated per active user on the Lens Protocol. This metric is calculated by dividing the total daily fees collected from user interactions by the number of daily active users. The metric helps assess the monetization efficiency of the Lens social protocol by showing how much fee revenue is generated per user engagement.

## 2. Data sources

- **Lens protocol event logs**: Parsed Polygon blockchain event logs from the Lens V1 Hub contract including `ProfileCreated`, `Collected`, `Followed`, `PostCreated`, `CommentCreated`, and `MirrorCreated` events
- **Transaction payment data**: Fee amounts embedded within `collectModuleData` and `followModuleDatas` hex-encoded fields from collect and follow events
- **End-of-day token price feeds**: External price data for converting token amounts to USD values
- **Token metadata**: Token decimal information for proper amount normalization

## 3. Step-by-step calculation

### Component A: Daily active users calculation
- **Purpose**: Calculate the number of unique users actively engaging with the Lens Protocol each day
- **Logic**: Extract user addresses from various Lens protocol events. For direct user events like profile creation, collects, and follows, the user address is directly available in event fields (`to`, `collector`, `follower`). For profile-based actions like posts, comments, and mirrors, map profile IDs to user addresses using the profile creation allowlist. Aggregate all unique user addresses per day using HyperLogLog to handle large-scale unique counting efficiently across different user types (Profile Creator, Collector, Follower, Poster, Commenter, Mirrorer).
- **Key fields**: `user_address` from various events, `profileId` for profile-based actions, `block_timestamp` for daily aggregation

### Component B: Daily fees calculation
- **Purpose**: Calculate total fee revenue generated from user interactions on the Lens Protocol
- **Logic**: Extract fee amounts from collect and follow actions by parsing hex-encoded payment data. Use substring operations on `collectModuleData` and `followModuleDatas` fields to extract token addresses (characters 27-66) and amounts (characters 67-130). Convert hex amounts to decimal values and identify the payment token. Combine fee data from both collect actions (content monetization) and follow actions (follow-to-earn mechanism). Convert all fee amounts to USD using end-of-day price feeds and apply decimal corrections based on token metadata.
- **Key fields**: `collectModuleData` and `followModuleDatas` for payment parsing, `token_address` and `amount` after extraction, `block_timestamp` for daily aggregation

### Final aggregation
- **Combining components**: Join daily fees and daily active users on the same date, ensuring both metrics cover the same time periods and dimensional breakdowns
- **Currency conversion**: Apply USD conversion to all fee amounts using end-of-day token prices, with proper decimal correction based on each token's decimal places
- **Time aggregation**: Aggregate all data to daily boundaries using timestamp truncation to day granularity
- **Final calculation**: Divide total daily fees (in USD) by the count of daily active users to produce the average fees per user. Apply a fill-zeros strategy to populate missing days with zero values, maintaining continuous daily time series data

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

Lens

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape