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

Gnosis Chain is a smart contract platform for decentralized applications (a blockchain). Gnosis was founded by Martin Köppelmann and Stefan George and launched in 2015.

GNO holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). 

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

Gnosis

# Gnosis Transaction count Methodology

## 1. Overview

The Gnosis transaction count metric measures the daily number of unique transactions processed on the Gnosis blockchain, aggregated by destination contract or address. This metric provides insights into network usage patterns and helps identify the most actively used contracts and services on the Gnosis ecosystem. The calculation counts distinct transactions per day and enriches the data with contract labels to provide meaningful categorization of transaction destinations.

## 2. Data sources

The calculation relies on these underlying data sources:
- **Gnosis blockchain transaction records**: Complete transaction history from the Gnosis blockchain including transaction hashes, addresses, gas usage, and block information
- **Public account labeling database**: Community-maintained labels for Gnosis contracts and addresses that provide human-readable names for transaction destinations
- **Token metadata**: wxDAI token contract address used as the native token for the Gnosis chain

## 3. Step-by-step calculation

### Component A: Raw transaction processing
- **Purpose**: Extract and standardize Gnosis blockchain transaction data with proper decimal handling for gas calculations
- **Logic**: Raw Gnosis transaction records are processed to extract key transaction details. Gas price fields are converted from wei to proper decimal format by dividing by 10^18. Each transaction record includes the block timestamp, transaction hash, sender address, destination address, transaction type, and gas usage metrics. The wxDAI token address is assigned as the native token for all transactions.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, `gas_used`, `effective_gas_price` (decimal corrected)

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day grouped by destination address
- **Logic**: Transactions are aggregated to daily granularity by truncating block timestamps to day boundaries. For each day and destination address combination, the system counts distinct transaction hashes to determine the number of unique transactions. Each record is tagged with chain identifier, market sector, and business segment classifications.
- **Key fields**: `timestamp` (daily), `to_address`, `transaction_count` (distinct count), `chain_id`, `market_sector_id`, `business_segment_id`

### Component C: Contract label enrichment
- **Purpose**: Add human-readable contract names to transaction destination addresses
- **Logic**: The daily transaction aggregates are joined with the public account labeling database to attach contract names to destination addresses. This left join preserves all transaction data while adding descriptive labels where available. Addresses without labels are marked as 'Unlabeled' to maintain data completeness.
- **Key fields**: `contract_name` (derived from account labels or 'Unlabeled'), all previous aggregation fields

### Final aggregation
- **Combining components**: The enriched transaction data flows through a finalization macro that validates the metric schema, ensures proper data types, and fills any gaps in the time series
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day precision, with incremental updates processing recent days plus a configurable lookback period
- **Final calculation**: The final metric represents the count of distinct transaction hashes per day per destination address, enriched with contract labels and validated through quality checks including chain availability filtering

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

Confirmed transactions added to the blockchain.

GnosisGNO

Transaction count

Transaction count

Competitive landscape