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

Hedera is a decentralized enterprise-grade public network that uses proof-of-stake hashgraph consensus to offer low & fixed fees, 10k TPS, and instant transaction finality. Hedera was founded by Leemon Baird, Mance Harmon, etc. and launched in 2019.

HBAR holders own and govern the protocol. They currently take a cut of the total transaction and query fees paid by users (revenue). Hedera’s investors include BlockTower Capital, Continue Capital, Unanimous Capital, etc.

github

twitter

discord

website

Blockchains (L1)

Hedera

# Hedera Contracts deployed Methodology

## 1. Overview

The Hedera contracts deployed metric measures the daily number of smart contracts deployed on the Hedera network. This metric counts unique contract creation transactions per day, providing insight into development activity and ecosystem growth on Hedera. The calculation identifies contract deployments by filtering for Hedera's specific `CONTRACTCREATEINSTANCE` transaction type, which is used exclusively for deploying smart contracts on the network.

## 2. Data sources

- **Hedera transaction records**: Complete transaction history from the Hedera network including transaction types, entity IDs, transaction identifiers, and execution metadata
- **Hedera block data**: Block timestamps for temporal organization and daily aggregation boundaries
- **Hedera entity registry**: Entity identification system that assigns unique IDs to newly created contracts on the network

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Gather all Hedera network transactions with their metadata for analysis
- **Logic**: Extract transaction records from Hedera network data including `transaction_hash`, `transaction_id`, `block_timestamp`, `entity_id`, and `transaction_type`. Each transaction includes network-specific metadata such as node information, fees, and entity relationships. The data represents the complete transaction history on Hedera with proper temporal ordering.
- **Key fields**: `block_timestamp` for timing, `transaction_id` for deployer identification, `entity_id` for contract identification, `transaction_type` for filtering contract creations

### Component B: Contract creation identification  
- **Purpose**: Isolate transactions that represent smart contract deployments on Hedera
- **Logic**: Filter transactions to only include those with `transaction_type` equal to `CONTRACTCREATEINSTANCE`, which is Hedera's specific transaction type for contract deployments. Extract the deployer address from the `transaction_id` field using regex pattern to capture the portion before any hyphens or spaces. Map the `entity_id` field to `contract_id` to identify the newly created contract. Apply distinct selection to ensure each contract creation is counted only once.
- **Key fields**: `transaction_type` filtered to `CONTRACTCREATEINSTANCE`, `entity_id` mapped to `contract_id`, deployer address extracted from `transaction_id`

### Final aggregation
- **Combining components**: Use the filtered contract creation transactions as the basis for daily counting
- **Time aggregation**: Truncate `block_timestamp` to daily boundaries to group contract creations by day. This ensures consistent daily reporting regardless of the specific time contracts were deployed
- **Final calculation**: Count the total number of contract creations per day using standard counting aggregation. Apply the finalize metric macro with a fill zeros strategy to ensure consistent daily reporting, filling any days with no contract deployments with zero values rather than missing data points
- **Output standardization**: Structure the final output with standard metric fields including `timestamp`, `timestamp_grain` (set to 'day'), `chain_id` (set to 'hedera'), `product_id` (set to null), and `contracts_deployed` containing the daily count

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

Unique smart contracts published onchain.

HederaHBAR

Contracts deployed

Contracts deployed

Competitive landscape