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

## 1. Overview

Lens Protocol earnings represents the net profit generated by the Lens social media protocol from user payments for social interactions. The metric captures revenue retained by the protocol after subtracting operational expenses. Earnings are calculated by subtracting total expenses from total revenue, where expenses include token incentives and operational costs. For Lens Protocol specifically, this metric tracks the protocol's ability to generate sustainable profit from monetized social interactions like collecting posts and following profiles.

## 2. Data sources

The calculation relies on several key data sources:

- **Lens Protocol event logs**: Parsed `HubEvents_Collected_event` and `HubEvents_Followed_event` smart contract events from Polygon blockchain containing encoded payment data for social interactions
- **Token payment data**: Embedded payment information within event logs, including token contract addresses and payment amounts stored in hexadecimal format within module data fields
- **End-of-day token price feeds**: Daily USD price data for tokens used in payments to convert native token amounts to standardized USD values
- **Token metadata**: Decimal precision and contract information for proper token amount calculations and normalization

## 3. Step-by-step calculation

### Component A: Social interaction payments extraction

- **Purpose**: Extract and decode payment data from Lens Protocol social interaction events
- **Logic**: Process `HubEvents_Collected_event` logs to identify collect and mirror actions, where collect actions occur when `rootPubId` equals `pubId`, otherwise they are mirror actions. Similarly, process `HubEvents_Followed_event` logs to capture follow payments. For both event types, extract token addresses by taking substring positions 27-40 from the module data field and prepending with "0x". Extract payment amounts by taking substring positions 67-64 from module data, converting from hexadecimal to decimal format. Handle cases where amount data is missing by defaulting to zero.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` and `log_index` for uniqueness, `collectModuleData` and `followModuleDatas` for encoded payment information, `rootPubId` and `pubId` for action type classification

### Component B: Trading volume aggregation

- **Purpose**: Combine all social interaction payments into a unified trading volume measure
- **Logic**: Union the collect/mirror payments with follow payments to create a comprehensive view of all monetized social interactions. Aggregate data daily using timestamp truncation to day boundaries. Apply token decimal correction to ensure proper token amount representation, then convert all amounts to USD using end-of-day price feeds. Classify all activities under the social market sector and business segment.
- **Key fields**: `timestamp` aggregated to daily grain, `chain` set to Polygon, `token_address` for payment tokens, `amount` for USD-converted payment values

### Component C: Fee calculation

- **Purpose**: Determine total fees generated from social interactions
- **Logic**: Take the trading volume data directly as fees, representing the total payment flow through the protocol from users engaging in monetized social actions. This assumes all trading volume represents fee-generating activity within the Lens ecosystem.
- **Key fields**: `trading_volume` becomes `fees` representing total user payments

### Component D: Token incentives determination

- **Purpose**: Calculate token incentives paid out by the protocol
- **Logic**: Set token incentives to zero across all time periods and chains, indicating that Lens Protocol does not currently distribute token-based rewards or incentives to users for social interactions.
- **Key fields**: `token_incentives` set to constant zero value

### Component E: Expenses calculation

- **Purpose**: Aggregate all protocol operational expenses
- **Logic**: Take token incentives as the primary expense component. Since token incentives are zero, total expenses are also zero, indicating minimal operational costs tracked in this calculation methodology.
- **Key fields**: `token_incentives` becomes `expenses` with zero values

### Component F: Revenue calculation

- **Purpose**: Determine revenue retained by the Lens Protocol
- **Logic**: Set revenue to zero for all time periods, indicating that while fees are collected from user interactions, none are retained as protocol revenue. This suggests fees flow through to other parties (creators, validators, etc.) rather than being captured by the protocol itself.
- **Key fields**: `revenue` set to constant zero value

### Final aggregation

- **Combining components**: Apply the earnings calculation formula using the `calculate_earnings` macro, which subtracts total expenses from total revenue
- **Currency conversion**: All amounts are converted to USD using end-of-day token price feeds with proper decimal correction applied during the trading volume calculation phase  
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with the finalization macro ensuring consistent daily time series with gap filling
- **Final calculation**: Earnings equals revenue minus expenses, which results in zero minus zero equals zero, indicating that Lens Protocol currently operates without generating net earnings from social interaction fees

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

Net profit (also profits, net income, profitability) — revenue remaining after subtracting expenses.

Lens

Earnings

Earnings

Competitive landscape