github

website

twitter

Blockchains (L2)

Sophon

# Sophon Bridge deposits Methodology

## 1. Overview

Bridge deposits measures the cumulative USD value of tokens deposited to the Sophon network via bridge contracts, net of withdrawals. This metric tracks the total value locked in the Sophon ecosystem through cross-chain transfers, providing insight into capital inflows and the network's total value secured from external chains. The calculation combines deposit and withdrawal flows from the ZkSync Era bridge infrastructure to compute net cumulative bridge activity on a daily basis.

## 2. Data sources

- **Ethereum bridge events**: Parsed `L1SharedBridge_BridgehubDepositInitiated_event`, `L1SharedBridge_BridgehubDepositFinalized_event`, and `L1SharedBridge_WithdrawalFinalizedSharedBridge_event` logs from the ZkSync Era L1 SharedBridge contract on Ethereum
- **Bridge transaction data**: Ethereum transaction records containing bridge deposit initiation, finalization, and withdrawal events specific to Sophon chain ID '50104'
- **Token metadata**: Token contract information including decimal places and address mappings for proper amount normalization
- **End-of-day price feeds**: Daily USD price data for converting token amounts to USD values
- **Chain availability data**: Data quality indicators for filtering reliable chain data

## 3. Step-by-step calculation

### Component A: Deposit event processing
- **Purpose**: Captures confirmed bridge deposits from Ethereum to Sophon
- **Logic**: Extracts deposit initiation events from Ethereum bridge logs filtered for Sophon chain ID '50104', then matches these with corresponding deposit finalization events using transaction hash joins. Only deposits that have been both initiated and finalized are included in the calculation. Native token addresses are converted to wrapped ETH addresses for consistency. The system captures amount, token address, timestamp, and transaction metadata from each confirmed deposit event.
- **Key fields**: `amount` (deposit value), `token_address` (deposited token), `block_timestamp` (event timing), `transaction_hash` (for matching initiation with finalization)

### Component B: Withdrawal event processing
- **Purpose**: Captures confirmed bridge withdrawals from Sophon to Ethereum
- **Logic**: Extracts withdrawal finalization events from Ethereum bridge logs, specifically the `L1SharedBridge_WithdrawalFinalizedSharedBridge_event` filtered for Sophon chain ID '50104'. Similar to deposits, native tokens are converted to wrapped ETH addresses. The system captures the same metadata structure as deposits to enable proper combination of flows.
- **Key fields**: `amount` (withdrawal value), `token_address` (withdrawn token), `block_timestamp` (event timing), `transaction_hash` (transaction identifier)

### Component C: Flow combination and decimal correction
- **Purpose**: Combines deposit and withdrawal flows into a single dataset with normalized amounts
- **Logic**: Unions deposit events with positive amounts and withdrawal events with negative amounts to create net flow calculations. Timestamps are truncated to daily boundaries for consistent aggregation. Token-specific decimal correction is applied to normalize amounts according to each token's decimal places, ensuring accurate value representation across different token standards.
- **Key fields**: `bridge_deposits` (normalized net flow amounts), `timestamp` (daily truncated), `token_address` (corrected token identifiers)

### Component D: Daily aggregation
- **Purpose**: Aggregates net flows by day and key dimensions
- **Logic**: Groups corrected flows by day, chain ID, market sector, business segment, product, and token address. Sums the net deposit amounts within each group to calculate daily net bridge activity. This aggregation removes duplicate events and provides clean daily totals for each token and dimension combination.
- **Key fields**: `bridge_deposits` (daily net amounts), dimension keys for grouping

### Component E: Cumulative calculation
- **Purpose**: Calculates running totals of bridge deposits over time
- **Logic**: Applies cumulative sum window functions partitioned by chain, market sector, business segment, product, and token address, ordered by timestamp. This creates a running total that represents the cumulative net value deposited to Sophon over time for each token and dimension combination.
- **Key fields**: `bridge_deposits` (cumulative running totals)

### Component F: Time series completion
- **Purpose**: Ensures continuous daily time series without gaps
- **Logic**: Forward-fills missing dates with the last known cumulative value for each token and dimension combination. This maintains data continuity and ensures that cumulative balances are carried forward even on days without bridge activity.
- **Key fields**: `bridge_deposits` (forward-filled cumulative values)

### Final aggregation
- **Combining components**: The completed time series data flows through the cumulative calculation pipeline where daily net flows become running totals
- **Currency conversion**: USD conversion occurs after cumulative calculation using end-of-day price feeds matched to each day and token address
- **Time aggregation**: Daily boundaries are established through timestamp truncation, with cumulative sums maintained across the full time series
- **Final calculation**: The metric represents the cumulative USD value of net bridge deposits (deposits minus withdrawals) for Sophon, calculated as the running sum of daily USD-converted net flows, forward-filled to maintain continuous values, and filtered for data quality through chain availability controls

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

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

SophonSOPH

Bridge deposits

Bridge deposits

Competitive landscape

Chain breakdown