Liquidity providers deposit funds into Loopring and receive trading fees from traders. Market makers offer trades through order book and make money on bid-ask spreads and market maker rebates. (supply-side fees). 

Loopring is a non-custodial exchange protocol built on Ethereum (zkRollups). Loopring was founded by Daniel Wang & Jay Zhou and launched in 2017.

LRC tokenholders own and govern the protocol. They currently take a cut of the total trading fees paid by traders (revenue). Loopring's investors include Fundamental Labs, Obsidian Capital, Eden Block, etc.

github

twitter

discord

etherscan

website

Exchanges (DEX)

Loopring

# Loopring Bridge deposits Methodology

## 1. Overview

Bridge deposits measures the total USD value of tokens held in Loopring's bridging infrastructure. This metric tracks the cumulative value of assets deposited into Loopring's Layer 2 bridge but not yet withdrawn, providing insight into the protocol's bridge utilization and total value locked in the bridging mechanism. The calculation identifies Loopring's official bridge addresses and sums the current token balances held across all supported tokens, converted to USD using end-of-day prices.

## 2. Data sources

The bridge deposits calculation relies on several key data sources:
- **Token balance data**: Current token holdings derived from parsed Ethereum `Transfer` events and transaction traces for the specified bridge addresses
- **Token transfer events**: Parsed ERC20 `Transfer` events from Ethereum showing inflows and outflows to bridge addresses
- **Token metadata**: Token contract information including decimal places, symbols, and contract addresses for proper balance calculations
- **End-of-day price feeds**: Daily USD price data for all tokens held in bridge addresses to enable accurate valuation
- **Transaction data**: Ethereum transaction traces and logs to track token movements and balance changes
- **Chain availability data**: Information about which blockchain networks have complete data coverage for accurate reporting

## 3. Step-by-step calculation

### Component A: Bridge address identification
- **Purpose**: Identifies the official Loopring bridge addresses that hold deposited tokens
- **Logic**: The calculation targets the primary Loopring bridge address `0x674bdf20a0f284d710bc40872100128e2d66bd3f` on Ethereum. This address acts as the main custody contract where users deposit tokens before bridging to Loopring's Layer 2 network
- **Key fields**: The bridge address is hardcoded as the account to track, with `chain_id` set to Ethereum

### Component B: Token balance calculation  
- **Purpose**: Calculates current token balances held by the bridge address across all supported tokens
- **Logic**: The portfolio calculation analyzes all token `Transfer` events involving the bridge address to determine current holdings. For each token contract, it tracks transfers in (increasing bridge balance) and transfers out (decreasing bridge balance) to compute net balances. This includes ERC20 token transfers as well as ETH balance changes through transaction traces
- **Key fields**: Token contract addresses, transfer `amount` values, transfer direction (to/from bridge address), block timestamps for balance history

### Component C: USD conversion and aggregation
- **Purpose**: Converts token balances to USD values and aggregates by time period
- **Logic**: Each token balance is converted to USD using end-of-day price feeds matched by token contract address and date. Token amounts are first adjusted for decimal places (e.g., dividing by 10^18 for 18-decimal tokens) to get human-readable quantities, then multiplied by USD prices. The conversion uses the token price from the same day as the balance timestamp to ensure temporal consistency
- **Key fields**: Token `balance` amounts, `decimals` for proper scaling, `price_usd` from price feeds, `timestamp` for temporal matching

### Component D: Business categorization
- **Purpose**: Applies business context and categorization to the bridge deposits metric  
- **Logic**: The calculated USD values are tagged with business metadata including market sector (`blockchains_l2` to indicate Layer 2 blockchain category), business segment (`blockchain` for core blockchain infrastructure), and data identifier (`loopring` for protocol-specific attribution). Product ID is set to null as this represents protocol-level infrastructure rather than a specific product
- **Key fields**: `market_sector_id`, `business_segment_id`, `product_id`, and `data_id` for business classification

### Final aggregation
- **Combining components**: Token balances from all held tokens are summed to create total bridge deposits value, grouped by timestamp and time granularity to produce daily aggregate values
- **Currency conversion**: All token values are converted to USD using end-of-day price feeds, with proper decimal adjustment applied before price multiplication
- **Time aggregation**: Bridge deposits are calculated as daily snapshots, with timestamps rounded to daily boundaries for consistent time series data
- **Final calculation**: The final bridge deposits value equals the sum of all token balances held by the Loopring bridge address, each converted to USD using end-of-day prices and adjusted for token decimals. Missing data points are filled forward using the most recent available value to ensure continuous time series coverage, and chain availability filtering ensures only periods with complete data coverage are included in the final metric.

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

Value of assets held in a project's bridge contracts.

LoopringLRC

Bridge deposits

Bridge deposits

Competitive landscape

Chain breakdown