Liquidity providers deposit funds into Everclear and receive transfer fees from users (supply-side fees).

Everclear is a cross-chain liquidity network that enables fully non-custodial transfers between EVM-compatible chains and L2 systems. Everclear was co-founded by  Arjun Bhuptani, Rahul Sethuram, and Layne Haber and launched in 2021.

Everclear team & investors own and govern the protocol. They do not currently take a cut of the total transfer fees paid by users (revenue).

github

twitter

discord

etherscan

website

Bridges

Everclear

# Everclear Active users (daily) Methodology

## 1. Overview

The Connext Daily Active Users (DAU) metric measures the number of unique user addresses that successfully complete cross-chain bridge transactions on the Connext protocol each day. This metric tracks user engagement across Connext's multi-chain bridge infrastructure, counting users who have completed transactions on either the v1 or v2 protocol versions across supported chains.

## 2. Data sources

The calculation relies on parsed blockchain events from Connext protocol smart contracts deployed across eight different chains:
- **Connext v1 events**: Parsed `TransactionFulfilled` events from TransactionManager contracts on Arbitrum, Avalanche, BSC, Ethereum, Fantom, Gnosis, Optimism, and Polygon
- **Connext v2 events**: Parsed `XCalled` events from ConnextDiamond contracts on Arbitrum, BSC, Ethereum, Gnosis, Optimism, and Polygon  
- **Additional v1 variants**: Parsed `TransactionFulfilled` events from TransactionManagerV2 and TransactionManagerV3 contracts on BSC, Fantom, and Polygon
- **Chain availability data**: Internal chain availability filters to ensure data quality

## 3. Step-by-step calculation

### Component A: User transaction extraction
- **Purpose**: Identifies all users who completed cross-chain bridge transactions on Connext protocol
- **Logic**: Extracts user addresses from successful bridge transaction events across multiple chains and protocol versions. For v1 protocol events (`TransactionFulfilled`), the user address is taken from the `user` parameter. For v2 protocol events (`XCalled`), the user address is extracted from the nested `params.originSender` parameter. Each transaction record includes the block timestamp, transaction hash, and chain identifier.
- **Key fields**: User addresses from `user` or `params.originSender` fields, `block_timestamp` for timing, `transaction_hash` for transaction identification, and chain identifiers

### Component B: User classification and standardization  
- **Purpose**: Standardizes user records with consistent metadata across all chains and protocol versions
- **Logic**: All extracted user addresses are classified as 'Trader' type users within the 'bridges' market sector and 'amm' business segment. This classification reflects that all Connext users are performing cross-chain trading/bridging activities. Chain information is preserved to maintain granularity for cross-chain analysis.
- **Key fields**: `user_type` set to 'Trader', `market_sector_id` set to 'bridges', `business_segment_id` set to 'amm', and `chain` for network identification

### Final aggregation
- **Time aggregation**: Block timestamps are truncated to daily granularity using day-level time boundaries to group transactions by calendar day
- **Uniqueness logic**: User addresses are deduplicated using distinct count within each day-chain combination to ensure users are counted only once per day per chain
- **Chain filtering**: Chain availability filters are applied to exclude data from chains or time periods where data completeness may be compromised  
- **Final calculation**: The result is a daily count of unique user addresses that completed bridge transactions on Connext protocol, segmented by chain and maintaining daily time series granularity

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

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

EverclearCLEAR

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown