Build once, connect everywhere. Hyperbridge gives developers the secure infrastructure to scale applications across any network.

website

twitter

github

discord

Bridges

Hyperbridge

# Hyperbridge Token holders Methodology

## 1. Overview

The Hyperbridge tokenholders metric measures the total number of unique addresses holding Hyperbridge tokens at specific points in time across supported blockchain networks. This metric provides insights into token distribution and adoption by counting distinct wallet addresses with non-zero token balances. The calculation aggregates holder counts across multiple chains where Hyperbridge tokens are deployed and maintains time-series data for tracking growth trends.

## 2. Data sources

The calculation relies on several key data sources:

- **Token balance snapshots**: Daily snapshots of token balances across all addresses holding Hyperbridge tokens on supported blockchain networks
- **Blockchain transaction logs**: Historical transaction data to track token transfers and balance changes over time
- **Token contract metadata**: Information about Hyperbridge token contracts across different chains to identify relevant addresses and tokens
- **Chain availability configuration**: Configuration data specifying which blockchain networks are currently supported and available for the metric
- **Address classification data**: Information to distinguish between different types of addresses (user wallets, contracts, exchanges, etc.)

## 3. Step-by-step calculation

### Component A: Native tokenholder aggregation
- **Purpose**: Aggregates the count of unique addresses holding Hyperbridge tokens across all supported chains
- **Logic**: The system identifies all addresses with non-zero balances of Hyperbridge tokens from daily balance snapshots. For each timestamp and chain combination, it counts the distinct number of addresses that hold any amount of the token. The calculation excludes zero-balance addresses and may apply additional filters to remove inactive or dust accounts. Each chain reports its tokenholder count independently with associated timestamp and granularity information.
- **Key fields**: The `timestamp` field indicates when the count was calculated, `timestamp_grain` specifies the aggregation period (typically daily), `chain` identifies the blockchain network, and `tokenholders` contains the count of unique holder addresses

### Component B: Metric standardization
- **Purpose**: Applies standardization and formatting to ensure consistency with Token Terminal's metric framework
- **Logic**: The finalize macro processes the raw tokenholder counts to apply standard formatting, add necessary metadata fields, and ensure the data structure matches Token Terminal's metric specifications. This includes proper data typing, null handling, and addition of any required identifier fields. The process maintains data integrity while preparing it for consumption by downstream analytics systems.
- **Key fields**: Preserves core fields while potentially adding standardized metadata like `data_id` for project identification and formatting fields for consistent presentation

### Component C: Chain availability filtering
- **Purpose**: Filters results to only include data from blockchain networks that are currently supported and available
- **Logic**: Applies a filter based on chain availability configuration to exclude data from networks that may be temporarily unavailable, deprecated, or not yet fully supported. This ensures the metric only reflects data from reliable, actively monitored blockchain networks and prevents incomplete or unreliable data from affecting the final results.
- **Key fields**: Uses the `chain_id` field to match against the availability configuration and determine which records to include in the final output

### Final aggregation
- **Combining components**: The system combines tokenholder counts across all supported chains while maintaining chain-level granularity. No cross-chain summation occurs at this level - each chain's tokenholder count remains separate to provide network-specific insights.
- **Currency conversion**: Not applicable for this count-based metric as it measures number of addresses rather than monetary values
- **Time aggregation**: Data is aggregated at the daily level with timestamps representing end-of-day snapshots. The `timestamp_grain` field indicates the aggregation period used.
- **Final calculation**: The final metric represents the count of unique addresses holding Hyperbridge tokens on each supported blockchain network at each timestamp, with high precision numeric formatting to handle large holder counts accurately.

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

Unique addresses holding a non-zero balance of the project's native token.

HyperbridgeBRIDGE

Archived

Token holders

Token holders

Competitive landscape

Chain breakdown