twitter

Blockchains (L1)

DFK Chain

# Contract deployers Methodology

## Overview

Contract deployers measures the number of unique addresses that have deployed at least one smart contract. It is a proxy for how many independent developers or entities that actively publish code onchain.

## Data sources

- Blockchain transaction data capturing contract creation operations
- Transaction execution traces for internal contract deployments
- Block metadata for daily time boundary calculation

## Common calculation approaches

### Transaction-based deployment extraction
Contract creation data is extracted from blockchain transaction records where new contract addresses are initialized. For example, unique deployer addresses are identified from transaction metadata on networks such as Ethereum and Polygon.

### Trace-level execution analysis
Internal contract deployments are identified through the analysis of transaction execution traces, which capture creations triggered by other smart contracts. This approach is used to ensure comprehensive developer activity is captured from chains including Arbitrum One and Base.

### Multi-layer infrastructure aggregation
Deployment activity is aggregated across different environments within a single ecosystem to provide a unified view of developer adoption. For instance, unique addresses are consolidated from contract creation records across both the BNB Chain mainnet and opBNB.

**Note:** The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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

Unique addresses that deployed at least one smart contract.

DFK ChainJEWEL

Archived

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown