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 Trading volume Methodology

## 1. Overview

The Lens trading volume metric measures the total daily USD value of paid social media interactions on the Lens Protocol, a decentralized social network built on Polygon. This metric captures revenue-generating activities including content collection fees, mirror/share fees, and follow fees. The calculation aggregates payment amounts from two main Lens protocol event types, converts them to USD, and presents them as daily trading volume figures.

## 2. Data sources

- **Lens protocol events**: Parsed `HubEvents_Collected_event` and `HubEvents_Followed_event` logs from the Lens v1 smart contract on Polygon blockchain
- **Event data structure**: Encoded module data fields containing payment token addresses and amounts in hexadecimal format
- **Transaction metadata**: Block timestamps, transaction hashes, and log indices for event tracking
- **External price data**: End-of-day token price feeds for USD conversion
- **Token metadata**: Token decimal information for amount standardization

## 3. Step-by-step calculation

### Component A: Content collection revenue
- **Purpose**: Extracts payment data from content collection and mirroring activities
- **Logic**: Parses Lens `HubEvents_Collected_event` logs from Polygon blockchain. The `collectModuleData` field contains encoded payment information that requires string manipulation to extract. Token addresses are extracted from character positions 27-66 with '0x' prefix added. Payment amounts are extracted from positions 67-130, converted from hexadecimal to decimal format. Events are classified as either 'Collect' (original content collection) or 'Mirror' (sharing/reposting) based on comparing the `rootPubId` and `pubId` fields - when they match, it's a collect action, otherwise it's a mirror
- **Key fields**: `collectModuleData` (encoded payment data), `rootPubId` and `pubId` (for action classification), `block_timestamp`, `transaction_hash`

### Component B: Follow revenue
- **Purpose**: Extracts payment data from paid follow transactions
- **Logic**: Parses Lens `HubEvents_Followed_event` logs from Polygon blockchain using the same string parsing approach. The `followModuleDatas` field contains encoded payment information structured identically to collect events. Token addresses are extracted from positions 27-66 and amounts from positions 67-130, with hexadecimal to decimal conversion applied. All events are classified as 'Follow' actions since they represent users paying to follow other profiles
- **Key fields**: `followModuleDatas` (encoded payment data), `block_timestamp`, `transaction_hash`

### Final aggregation
- **Combining components**: Union all collect/mirror events and follow events into a single dataset, maintaining event-level detail with timestamps, token addresses, and amounts
- **Currency conversion**: Apply USD conversion using end-of-day price feeds matched by token address and event date. Correct token amounts for decimal places based on token metadata (e.g., dividing by 10^18 for 18-decimal tokens)
- **Time aggregation**: Truncate event timestamps to daily boundaries and aggregate total USD amounts by day, chain (Polygon), and token
- **Final calculation**: Sum all USD-converted amounts per day to calculate total daily trading volume. Apply gap-filling logic to ensure continuous daily time series, filling missing days with zero values. All data is classified under 'social' market sector and business segment to reflect the social media nature of Lens protocol

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

Total value of spot trades executed on the exchange.

Lens

Trading volume

Trading volume

Competitive landscape