Users deposit and lock assets on Ethereum in exchange for an equivalent amount of a corresponding token on zkSync Era. Conversely, users can withdraw assets from zkSync Era in exchange for the same amount on Ethereum.

zkSync Era Bridge is an asset bridge built on Ethereum and zkSync Era. zkSync Era Bridge was developed by Matter Labs and launched in 2023.

Matter Labs team owns and governs the protocol. Matter Labs' investors include a16z, Lightspeed Venture Partners, Blockchain Capital, etc.

twitter

discord

website

Bridges

zkSync Era Bridge

# zkSync Era Bridge Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) for zkSync Era Bridge measures the average daily revenue generated per active user of the bridge protocol. This metric answers the business question "How much revenue does the bridge generate per user on average?" For zkSync Era Bridge specifically, ARPU is consistently zero because the bridge operates without charging user fees. The calculation divides total daily revenue by the number of daily active users, where daily active users are identified from bridge interaction events on Ethereum mainnet.

## 2. Data sources

- **Bridge interaction events**: Parsed Ethereum `L1ERC20Bridge_DepositInitiated`, `L1ERC20Bridge_WithdrawalFinalized`, and `Diamond_EthWithdrawalFinalized` events that capture user deposits and withdrawals
- **Priority request events**: Ethereum `Diamond_NewPriorityRequest` events for ETH deposits to L2
- **Function call data**: Ethereum `Diamond_requestL2Transaction` function calls that identify additional depositors
- **End-of-day token price feeds**: Used for transfer volume USD conversion (though not directly used in ARPU calculation)
- **Token metadata**: Token contract information including decimal places for proper amount normalization

## 3. Step-by-step calculation

### Component A: User identification and classification
- **Purpose**: Identify all users who interact with the zkSync Era Bridge on a daily basis
- **Logic**: Extract user addresses from Ethereum bridge events and function calls. Parse `DepositInitiated` events to identify depositors using the `from` address parameter. Parse `WithdrawalFinalized` and `EthWithdrawalFinalized` events to identify withdrawers using the `to` address parameter. Include users from `requestL2Transaction` function calls where transaction status is successful. Classify each user interaction by type as either "Depositor" or "Withdrawer". Truncate all timestamps to daily boundaries for consistent aggregation.
- **Key fields**: `user_address` from event parameters, `user_type` classification, `block_timestamp` truncated to day, `transaction_hash` for deduplication

### Component B: Daily active user aggregation
- **Purpose**: Count unique daily active users efficiently across multiple dimensional breakdowns
- **Logic**: Create HyperLogLog sketches for each unique user address within each day to enable scalable distinct counting. Group users by timestamp, chain, user type, and product dimensions. Aggregate HyperLogLog sketches across different dimensional combinations including project-level, chain-level, user type-level, and product-level breakdowns. Extract final distinct user counts from merged HyperLogLog sketches. Apply fill zeros strategy to ensure continuous daily time series with no gaps.
- **Key fields**: `user_dau` count from HyperLogLog extraction, `dimensions` indicating aggregation level, `timestamp` at daily grain

### Component C: Revenue calculation
- **Purpose**: Calculate total daily revenue generated by the bridge protocol
- **Logic**: For zkSync Era Bridge, revenue is hardcoded to zero because the protocol does not charge fees for bridge operations. The revenue calculation references the fees model structure but sets all revenue values to 0. This maintains consistency with the dimensional structure from transfer volume data while accurately reflecting the fee-free nature of the bridge.
- **Key fields**: `revenue` value set to 0, `timestamp` for daily aggregation, dimensional identifiers matching user data

### Final aggregation
- **Combining components**: Join daily revenue totals with daily active user counts on matching timestamp and dimensional keys (chain, product). Both datasets use the same daily time boundaries and dimensional structure to ensure proper alignment.
- **Currency conversion**: Revenue is already in USD terms (though zero), so no additional currency conversion is needed for the final ARPU calculation
- **Time aggregation**: Both revenue and user metrics are aggregated to daily boundaries using timestamp truncation to day level
- **Final calculation**: Divide total daily revenue by daily active user count to get Average Revenue Per User. Since revenue is consistently zero for zkSync Era Bridge, the resulting ARPU is also zero across all time periods and dimensions. Apply forward-filling with zeros strategy to handle any missing data points and maintain continuous time series.

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

zkSync Era Bridge

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape