github

twitter

discord

website

Blockchains (L2)

ZKFair

# ZKFair Bridge deposits Methodology

## 1. Overview

The zkFair bridge deposits metric measures the total USD value of tokens held in zkFair's bridging infrastructure on Ethereum. This metric tracks the assets deposited by users that are awaiting transfer to the zkFair L2 network or are held as collateral for the bridging process. It provides insight into the demand for zkFair's L2 solution and the total value secured within their bridging contracts.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Ethereum token transfer events**: Parsed `Transfer` events from ERC20 token contracts to track token movements in and out of the bridge address
- **Token balance snapshots**: Daily balance calculations derived from cumulative token transfer events for the specified bridge address
- **End-of-day token price feeds**: USD price data for all tokens held in the bridge to enable value conversion
- **Token metadata**: Contract addresses, decimal places, and token identifiers for proper balance calculations
- **Chain availability data**: Data quality indicators to filter out periods with unreliable blockchain data

## 3. Step-by-step calculation

### Component A: Bridge address portfolio calculation
- **Purpose**: Calculate the daily token balances held at zkFair's bridge address on Ethereum
- **Logic**: The calculation targets a specific Ethereum address (`0x9cb4706e20a18e59a48ffa7616d700a3891e1861`) identified as zkFair's bridge contract. Using parsed `Transfer` events from Ethereum, the system tracks all token movements into and out of this address. For each token, it maintains a running balance by processing all historical transfers and calculating net holdings as of each day. Token amounts are adjusted for the appropriate decimal places based on each token's contract specifications.
- **Key fields**: The resulting data includes `timestamp`, `chain`, and `balance` representing the USD value of tokens held

### Component B: Business metadata application  
- **Purpose**: Apply zkFair-specific business categorization to the portfolio data
- **Logic**: Each balance record is tagged with business metadata identifying zkFair as an L2 blockchain project. The data is categorized with `market_sector_id` set to 'blockchains_l2' (indicating this is layer 2 blockchain infrastructure), `business_segment_id` set to 'blockchain' (indicating the blockchain segment), and `product_id` set to null (as this represents the overall bridge functionality rather than a specific product). The balance values are aggregated by day and chain to create daily totals.
- **Key fields**: Business identifiers `chain_id`, `market_sector_id`, `business_segment_id`, `product_id`, and the aggregated `bridge_deposits` value

### Final aggregation
- **Combining components**: The portfolio balance data is combined with business metadata through straightforward field assignment, with token balances summed across all tokens held at the bridge address for each day
- **Currency conversion**: All token balances are converted to USD using end-of-day price feeds, with the conversion applied at the token level before aggregation to ensure accurate valuations
- **Time aggregation**: Data is aggregated to daily granularity with timestamp boundaries aligned to standard daily periods
- **Final calculation**: The final bridge deposits value represents the sum of USD-converted balances for all tokens held at the zkFair bridge address, processed through a finalize metric macro that applies fill-forward logic to handle any missing data points and filtered by chain availability indicators to ensure data quality

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

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

ZKFairZKF

Bridge deposits

Bridge deposits

Competitive landscape

Chain breakdown