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

## 1. Overview

The Lens fees metric measures the total fees paid by users for social interactions on the Lens protocol. In the Lens ecosystem, fees are equivalent to trading volume since users pay fees for social actions like collecting posts and following profiles. The metric captures all fee-generating activities on the platform and converts them to USD for consistent measurement across different payment tokens.

## 2. Data sources

- **Polygon blockchain event logs**: Parsed `HubEvents_Collected_event` and `HubEvents_Followed_event` logs from Lens V1 protocol containing encoded payment module data
- **Module data fields**: `collectModuleData` and `followModuleDatas` fields containing hex-encoded token addresses and payment amounts
- **End-of-day token price feeds**: For converting payment amounts from native tokens to USD
- **Token metadata**: Decimal precision information for accurate amount calculations

## 3. Step-by-step calculation

### Component A: Collect fees extraction
- **Purpose**: Extract payment data from content collection events on Lens protocol
- **Logic**: Process `HubEvents_Collected_event` logs from Polygon blockchain to extract payment information. Parse the `collectModuleData` field using substring operations to extract token addresses (characters 27-66) and payment amounts (characters 67-130). Convert hex-encoded amounts to numeric values. Distinguish between 'Collect' actions (when `rootPubId` equals `pubId`) and 'Mirror' actions (when they differ). Include transaction metadata like `block_timestamp`, `transaction_hash`, and `log_index`
- **Key fields**: `block_timestamp` for timing, `token_address` from parsed module data, `amount` from hex conversion, `action_type` based on publication ID comparison

### Component B: Follow fees extraction  
- **Purpose**: Extract payment data from profile following events on Lens protocol
- **Logic**: Process `HubEvents_Followed_event` logs from Polygon blockchain to extract payment information. Parse the `followModuleDatas` field using substring operations to extract token addresses (characters 27-66) and payment amounts (characters 67-130). Convert hex-encoded amounts to numeric values. All events are classified as 'Follow' action type. Include transaction metadata for tracking and deduplication
- **Key fields**: `block_timestamp` for timing, `token_address` from parsed module data, `amount` from hex conversion, `action_type` set to 'Follow'

### Final aggregation
- **Combining components**: Union collect fees and follow fees data, ensuring no duplicate entries across the combined dataset. Aggregate all fee-generating social interactions into a single daily time series
- **Currency conversion**: Convert payment amounts to USD using end-of-day token price feeds and apply decimal correction based on token metadata to ensure accurate monetary values
- **Time aggregation**: Truncate timestamps to daily boundaries and group by day, chain (Polygon), and business segment (social). Apply zero-filling strategy to ensure continuous daily time series
- **Final calculation**: Sum all USD-converted payment amounts by day to create the fees metric. Since Lens protocol treats all social interaction payments as fees, the trading volume calculation becomes the fees metric directly through a simple field mapping

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

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

Lens

Fees

Fees

Competitive landscape