Validators process transactions and receive validator rewards (supply-side fees).

NEAR Protocol is a smart contract platform for decentralized applications (a blockchain). NEAR Protocol was founded by Alexander Skidanov & Ilya Polosukhin and launched in 2017.

NEAR holders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). NEAR Protocol's investors include a16z, Pantera Capital, Libertus, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

NEAR Protocol

# near Contract Deployers Methodology

## 1. Overview

Contract Deployers measures the number of unique addresses that initiated the deployment of smart contracts on Near. This metric is used to evaluate developer activity and the growth of the application ecosystem. It serves as a key indicator of the health of the developer community by quantifying the specific accounts responsible for launching on-chain logic.

## 2. Data sources

- **Blockchain events**: Contract deployment records on Near
- **External data**: Asset metadata for chain identification and categorization

## 3. Step-by-step calculation

### Component A: Contract creation identification

- **Purpose**: To identify and isolate all unique instances of smart contract deployments.
- **Logic**: Data is extracted from contract deployment records. For every contract initialized on the network, the address of the account that performed the deployment and the associated timestamp are retrieved. Duplicate records are filtered to ensure that each unique contract deployment is represented accurately in the dataset.
- **Key fields**: `creation_timestamp` and `deployer_address`

### Component B: Daily unique aggregation

- **Purpose**: To determine the daily volume of unique developers active on the network.
- **Logic**: Timestamps are truncated to a daily granularity. Deployer addresses are then aggregated by day, and a distinct count is applied to the deployer addresses. This ensures that an account is only counted once per day, even if it initiated multiple contract deployments within that 24-hour period.
- **Key fields**: `deployer_address` and `block_timestamp`

### Component C: Data finalization and series continuity

- **Purpose**: To ensure the metric follows a consistent schema and reflects a continuous time series.
- **Logic**: Data types are cast to a standardized format for numerical processing. A zero-filling strategy is applied to the daily time series, ensuring that any day without recorded deployment activity is explicitly assigned a value of zero rather than being omitted from the dataset.
- **Key fields**: `contract_deployers` and `timestamp`

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

Unique addresses that deployed at least one smart contract.

NEAR ProtocolNEAR

Contract deployers

Contract deployers

Competitive landscape