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

Polygon is a smart contract platform for decentralized applications & interoperability platform for blockchains. Polygon was founded by Jaynti Kanani, Sandeep Nailwal & Anurag Arjun and launched in 2017.

MATIC holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Polygon’s investors include Coinbase Ventures, ZBS Capital, MiH Ventures, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Polygon

# Polygon Contract deployers Methodology

## 1. Overview

The Polygon contract deployers metric measures the daily count of unique addresses that deployed smart contracts on the Polygon blockchain. This metric tracks ecosystem developer activity by identifying how many distinct addresses created new contracts each day. The calculation aggregates contract creation events from Polygon blockchain data, counts unique deployer addresses per day, and applies standardization processes including gap-filling for missing days.

## 2. Data sources

The metric relies on the following raw data sources:

- **Polygon blockchain transaction data**: Transaction records from the Polygon blockchain containing contract creation transactions and their associated metadata
- **Contract deployment events**: Parsed contract creation events that identify when new smart contracts are deployed to the Polygon network
- **Transaction trace data**: Detailed execution traces from Polygon transactions that capture contract creation operations, including deployer addresses and creation timestamps
- **Chain availability data**: Operational status information for the Polygon blockchain to ensure data quality and completeness

## 3. Step-by-step calculation

### Component A: Contract creation event extraction
- **Purpose**: Identifies all contract deployment events on the Polygon blockchain with relevant metadata
- **Logic**: Extracts contract creation records from Polygon blockchain data, capturing the creation timestamp (`creation_timestamp`), deployed contract address (`contract_address`), deployer address (`deployer_address`), and trace address (`creation_trace_address`). The data is deduplicated to ensure each contract creation is counted only once.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for the deployed contract, `deployer_address` for the deploying entity, and `creation_trace_address` for transaction trace reference

### Component B: Daily aggregation and counting
- **Purpose**: Calculates the daily count of unique contract deployers
- **Logic**: Groups contract creation events by day using timestamp truncation to daily boundaries. For each day, counts the number of distinct deployer addresses that created contracts. Adds classification metadata including chain identifier as "polygon", market sector as "blockchains_l1", business segment as "blockchain", and sets product identifier as null.
- **Key fields**: `timestamp` (truncated to day), `contract_deployers` (distinct count of deployer addresses), plus categorical classification fields

### Final aggregation
- **Combining components**: The daily aggregated data is processed through a finalization macro that standardizes the metric format and applies gap-filling logic
- **Gap filling**: Missing days in the time series are filled with zero values using the "fill_zeros" strategy to ensure continuous daily data
- **Data quality filtering**: Chain availability filters are applied to exclude periods where Polygon blockchain data might be incomplete or unreliable
- **Final calculation**: The result is a daily time series showing the count of unique addresses that deployed contracts on Polygon for each day, with gaps filled as zeros and quality filters applied

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

Unique addresses that deployed at least one smart contract.

PolygonPOL

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown