Network participants process transactions and receive fees from users (supply-side fees).

Cosmos Hub is an interoperability & security platform for blockchains and applications. Cosmos was founded by Ethan Buchman & Jae Kwon and launched in 2019.

ATOM holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Cosmos’s investors include Paradigm, IOSG Ventures, 1confirmation, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

Cosmos Hub

# Cosmos Hub Block time Methodology

## 1. Overview

The Cosmos block time metric measures the average time between consecutive blocks on the Cosmos Hub blockchain, aggregated daily. This metric provides insight into the blockchain's performance consistency and block production efficiency. The calculation takes raw block data with timestamps and computes the time intervals between consecutive blocks, then averages these intervals by day to create a daily block time metric.

## 2. Data sources

The calculation uses the following raw data sources:

- **Cosmos Hub block data**: Block records from the Cosmos Hub blockchain containing block timestamps, block heights (numbers), and proposer validator addresses
- **Chain availability metadata**: Data quality and completeness indicators used to filter reliable time periods

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extract foundational block information from Cosmos Hub blockchain
- **Logic**: Retrieve block timestamp, block number (height), and validator (proposer address) for each block produced on Cosmos Hub. Apply incremental processing with lookback days to ensure data completeness and handle any late-arriving block data
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential block height), `validator` (block proposer address)

### Component B: Consecutive block pairing  
- **Purpose**: Create pairs of consecutive blocks to enable time interval calculation
- **Logic**: Use window function to pair each block with the timestamp of the immediately preceding block based on block number ordering. This creates records where each block has both its own timestamp and the timestamp of the previous block
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Calculate the actual time duration between consecutive blocks
- **Logic**: Compute the time difference in milliseconds between each block and its predecessor using timestamp subtraction. Filter out the first block in the sequence since it has no predecessor. Truncate block timestamps to day boundaries to prepare for daily aggregation
- **Key fields**: `timestamp` (daily boundary), `block_time` (milliseconds between consecutive blocks)

### Final aggregation
- **Combining components**: Group all block time intervals by day and calculate the average block time for each day
- **Currency conversion**: Not applicable for time-based metrics
- **Time aggregation**: Daily boundaries using timestamp truncation, with all block intervals within each day averaged together
- **Final calculation**: Average of all individual block time intervals (in milliseconds) for each calendar day, along with standardized metadata including chain identifier (`cosmos`), market sector (`blockchains_l1`), business segment (`blockchain`), and timestamp grain (`day`). Apply chain availability filtering to ensure data quality and use zero-fill strategy for any missing days.

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

avg(block_timestamp - previous_block_timestamp)

Cosmos HubATOM

Block time

Block time

Competitive landscape