github

twitter

discord

website

Exchanges (DEX)

Paradex

# Paradex Bridge deposits Methodology

## 1. Overview

Paradex bridge deposits measures the total USD value of tokens held in Paradex's designated bridge deposit address on Ethereum. This metric tracks assets that users have deposited to the bridge contract for potential transfer to Paradex's Layer 2 infrastructure. The calculation aggregates all token balances held by the bridge address and converts them to USD values using end-of-day pricing.

## 2. Data sources

- **Ethereum token balances**: Daily balance snapshots for all ERC20 tokens and ETH held by the bridge address
- **End-of-day token price feeds**: USD prices for all tokens to enable value conversion  
- **Token metadata**: Decimal precision and basic token information for proper balance calculations
- **Blockchain availability data**: Operational status information to filter out periods when Ethereum data is unavailable

## 3. Step-by-step calculation

### Component A: Bridge address identification
- **Purpose**: Identify the specific Ethereum address that serves as Paradex's bridge deposit contract
- **Logic**: The methodology uses a hardcoded Ethereum address `0xe3cbe3a636ab6a754e9e41b12b09d09ce9e53db3` as the designated bridge deposit address where users send tokens for bridging to Paradex
- **Key fields**: `account_addresses` containing the bridge contract address

### Component B: Portfolio balance calculation  
- **Purpose**: Calculate the total token holdings for the bridge address across all supported tokens
- **Logic**: The system retrieves daily balance snapshots for the bridge address, covering all ERC20 tokens and ETH held by the contract. Each token balance is adjusted for the token's decimal precision and converted to USD using end-of-day price feeds. The calculation handles multiple tokens simultaneously and maintains daily timestamp granularity
- **Key fields**: `balance` representing USD-converted token holdings, `timestamp` for daily aggregation, `chain` identifying Ethereum as the source blockchain

### Component C: Business context assignment
- **Purpose**: Add standardized business metadata for categorization and reporting
- **Logic**: The system assigns business classification metadata to each balance record, including market sector identification as Layer 2 blockchain category, business segment classification as blockchain infrastructure, chain identification from the portfolio data, and product identification set to null since this represents bridge-level rather than product-specific deposits
- **Key fields**: `market_sector_id` set to 'blockchains_l2', `business_segment_id` set to 'blockchain', `chain_id` from portfolio data, `product_id` set to null

### Final aggregation
- **Combining components**: All token balances for the bridge address are summed together for each timestamp and chain combination, creating a single daily bridge deposits value
- **Currency conversion**: Token balances are converted to USD using end-of-day price feeds, with proper decimal adjustment applied during the portfolio calculation phase
- **Time aggregation**: Daily timestamp boundaries are used, with the system supporting multiple timestamp grains through the finalization process
- **Final calculation**: The final `bridge_deposits` value represents the sum of all USD-converted token balances held by the Paradex bridge address, filtered for blockchain availability and standardized with forward-filling for missing data points

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

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

ParadexDIME

Bridge deposits

Bridge deposits

Competitive landscape

Chain breakdown