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 Active users (daily) Methodology

## 1. Overview

The Lens protocol daily active users (DAU) metric measures the number of unique wallet addresses that interact with the Lens Protocol social platform on any given day. This metric captures user engagement across various social activities including profile creation, content posting, commenting, mirroring, collecting, and following. The calculation identifies distinct users by their wallet addresses and aggregates them by day to provide a measure of daily platform activity.

## 2. Data sources

The calculation relies on parsed smart contract events from the Lens Protocol v1 deployment on the Polygon blockchain:
- **Lens Protocol events**: Six types of parsed smart contract events from the Lens v1 Hub contract on Polygon, including profile management events (`ProfileCreated`), social interaction events (`Collected`, `Followed`), and content creation events (`PostCreated`, `CommentCreated`, `MirrorCreated`)
- **Blockchain metadata**: Block timestamps and transaction hashes from Polygon blockchain records for temporal and transactional context

## 3. Step-by-step calculation

### Component A: Direct user activity extraction
- **Purpose**: Captures user activities where wallet addresses are directly available in the event parameters
- **Logic**: Extracts user addresses from three event types: `ProfileCreated` events (using the `to` parameter representing profile creators), `Collected` events (using the `collector` parameter for users collecting content), and `Followed` events (using the `follower` parameter for users following others). Each event record includes the block timestamp, transaction hash, and the user's wallet address directly from the event parameters.
- **Key fields**: `block_timestamp` for temporal tracking, `transaction_hash` for deduplication, user wallet addresses (`to`, `collector`, `follower` depending on event type), and user activity classification as Profile Creator, Collector, or Follower

### Component B: Profile-based activity resolution  
- **Purpose**: Captures user activities for content creation events that reference profile IDs rather than wallet addresses directly
- **Logic**: First creates an allowlist by extracting the mapping between profile IDs (`profileId`) and wallet addresses (`to`) from `ProfileCreated` events. Then processes content creation events (`PostCreated`, `CommentCreated`, `MirrorCreated`) which contain profile IDs (`profileId`) but not wallet addresses. Joins these events with the allowlist to resolve profile IDs back to the corresponding wallet addresses of the profile owners.
- **Key fields**: Profile ID (`profileId`) for mapping, resolved wallet addresses from the allowlist join, block timestamps and transaction hashes from the content creation events, and user activity classification as Poster, Commenter, or Mirrorer

### Component C: Activity standardization
- **Purpose**: Unifies all user activities into a consistent format with standardized metadata
- **Logic**: Combines the direct user activities and profile-based activities into a single dataset. Applies consistent labeling with 'social' as both market sector and business segment, 'polygon' as the blockchain, and assigns user type labels based on the specific activity (Profile Creator, Collector, Follower, Poster, Commenter, Mirrorer). Preserves block-level timestamps and transaction hashes for subsequent aggregation.
- **Key fields**: Standardized `chain`, `market_sector_id`, `business_segment_id`, `user_type`, `user_address`, and `block_timestamp` fields across all activity types

### Final aggregation
- **Combining components**: All user activities are unioned together into a comprehensive user activity dataset covering all forms of Lens protocol engagement
- **Time aggregation**: Block timestamps are truncated to day boundaries using day-level granularity, grouping all activities within a 24-hour period
- **Deduplication**: Applies distinct count on user addresses within each day to ensure each unique wallet address is counted only once per day, regardless of how many different activities they performed
- **Final calculation**: The daily active user count is calculated as the distinct count of wallet addresses that performed any Lens protocol activity on each given day, with chain availability filtering applied to ensure data quality and completeness

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

Unique revenue-generating users over a fixed 24-hour window.

Lens

Active users (daily)

Active users (daily)

Competitive landscape