Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Bifrost is the Staking Yield Layer app-chain for stablecoins, RWAs, and DeFi, powered by the Polkadot Relay chain.

BNC holders own and govern the protocol. Bifrost’s investors include OKX Ventures, Long Hash Ventures, etc.

website

github

twitter

discord

etherscan

Blockchains (L2)

Bifrost

# Bifrost Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive block productions on the Bifrost blockchain, expressed in milliseconds and aggregated daily. This metric indicates blockchain performance and network health by showing how consistently blocks are being produced. The calculation determines the time difference between each block and its predecessor, then averages these intervals across each day to provide daily block time metrics.

## 2. Data sources

The calculation uses the following raw data sources:

- **Bifrost blockchain data**: Raw block data from the Bifrost blockchain containing block timestamps, sequential block numbers, and block author information
- **Chain availability configuration**: Metadata defining operational periods and data quality filters for the Bifrost chain

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieve and prepare raw block information from the Bifrost blockchain
- **Logic**: Extract block timestamps and numbers from Bifrost blockchain data, casting timestamps to proper timestamp format and block numbers to integers. Filter out the genesis block (block number 0) as it has an artificial timestamp at the start of Unix time that would skew calculations. For incremental processing, only include blocks from recent days based on the configured lookback period.
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential block identifier), `author_id` (block producer identifier)

### Component B: Timestamp pairing
- **Purpose**: Create pairs of consecutive block timestamps to enable interval calculations
- **Logic**: Use a lag window function ordered by block number to associate each block with the timestamp of the immediately preceding block. This creates timestamp pairs where each row contains both the current block timestamp and the previous block timestamp.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: Compute the time difference in milliseconds between each block timestamp and its predecessor using timestamp difference functions. Truncate block timestamps to daily boundaries to enable daily aggregation. Exclude any records where the previous timestamp is null (typically the first block in the dataset).
- **Key fields**: `timestamp` (daily boundary), `block_time` (interval in milliseconds), `timestamp_grain` (aggregation level)

### Final aggregation
- **Combining components**: Group block intervals by daily timestamp boundaries and calculate the average block time for each day across all block intervals within that day
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Block intervals are aggregated to daily averages, with timestamps truncated to day-level granularity
- **Final calculation**: The average block time is computed as the mean of all individual block intervals (in milliseconds) for each calendar day. The result includes chain identifier (`bifrostio`) and product identifier (`Bifrost Substrate`) metadata. Chain availability filtering is applied to ensure only periods with reliable data coverage are included in the final output.

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

avg(block_timestamp - previous_block_timestamp)

BifrostBNC

Archived

Block time

Block time

Competitive landscape

Chain breakdown