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 Contract deployers Methodology

## 1. Overview

The Hedera contract deployers metric measures the daily count of unique addresses that deploy smart contracts on the Hedera network. This metric answers the question "How many distinct users are deploying new smart contracts each day?" and serves as an indicator of developer activity and smart contract ecosystem growth on Hedera. The calculation identifies contract deployment transactions and counts the unique deployer addresses per day.

## 2. Data sources

- **Hedera transaction records**: Raw blockchain transaction data from the Hedera network containing transaction metadata, timestamps, and transaction type classifications
- **Transaction identifiers**: Hedera transaction IDs that encode deployer address information in their structure
- **Entity identifiers**: Hedera entity IDs that represent newly created contract addresses
- **Transaction type classifications**: Hedera's native transaction type system, specifically the `CONTRACTCREATEINSTANCE` transaction type used for smart contract deployment

## 3. Step-by-step calculation

### Component A: Transaction filtering and processing
- **Purpose**: Extract and process all Hedera transactions to create a foundation dataset
- **Logic**: Raw Hedera transaction records are processed to extract key transaction metadata including block timestamps, transaction hashes, transaction IDs, entity IDs, fees, and transaction types. This creates a standardized transaction dataset that serves as the foundation for identifying contract deployments.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_id` for deployer extraction, `entity_id` for contract identification, and transaction type `name` for filtering

### Component B: Contract creation identification  
- **Purpose**: Identify specific transactions that represent smart contract deployments on Hedera
- **Logic**: From the processed transaction dataset, filter transactions to only include those with transaction type `CONTRACTCREATEINSTANCE`, which is Hedera's specific transaction type for smart contract deployment. Extract the deployer address from the `transaction_id` field using regex pattern matching to get the first part before any dash or space characters. Use the `entity_id` field as the contract identifier. Only include records where the contract identifier is not null to ensure valid contract creations.
- **Key fields**: `deployer_address` extracted from `transaction_id`, `contract_id` from `entity_id`, and `block_timestamp` for temporal grouping

### Final aggregation
- **Combining components**: The contract creation dataset is aggregated by truncating timestamps to daily boundaries and grouping by day, chain identifier, and product identifier
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation to day level, ensuring consistent daily counts regardless of transaction timing within the day
- **Final calculation**: Count distinct deployer addresses per day to measure unique contract deployers. The distinct count prevents double-counting users who deploy multiple contracts on the same day. The result is finalized using the `finalize_metric_contract_deployers` macro which standardizes the metric format and applies a fill-zeros strategy for days with no contract deployments. Chain availability filtering is applied to ensure data quality and availability requirements are met.

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

Unique addresses that deployed at least one smart contract.

HederaHBAR

Contract deployers

Contract deployers

Competitive landscape