Base batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Base is an Ethereum Layer 2 (L2) offering a secure, low-cost, builder-friendly way for anyone, anywhere, to build onchain.

Coinbase team owns and governs the protocol. Coinbase is a public company and its investors include Andreessen Horowitz, Vanguard Group, ARK Investment Management, etc.

github

twitter

discord

website

Blockchains (L2)

Base

# Base Contract deployers Methodology

## 1. Overview

Base contract deployers measures the daily count of unique addresses that deploy smart contracts on the Base blockchain. This metric tracks ecosystem development activity by counting distinct deployer addresses per day, providing insight into developer adoption and smart contract creation patterns on Base. The calculation aggregates contract creation events to daily granularity and applies a distinct count to capture unique deploying entities.

## 2. Data sources

The metric relies on the following raw data sources:
- **Base contract creation data**: Complete records of smart contract deployments on the Base blockchain, including deployer addresses, creation timestamps, contract addresses, and deployment metadata
- **Chain availability metadata**: Base blockchain data availability periods used for data quality filtering to ensure accurate reporting during periods of complete data coverage

## 3. Step-by-step calculation

### Component A: Contract creation facts
- **Purpose**: Extracts and deduplicates contract creation records from Base blockchain data
- **Logic**: Selects distinct contract creation records from Base contracts data to ensure each deployment is counted only once. Captures key deployment metadata including the deployer address, creation timestamp, contract address, creation trace address, contract bytecode, and creator address. Applies deduplication to handle any potential duplicate records in the raw data
- **Key fields**: `creation_timestamp` for timing, `deployer_address` for the entity creating contracts, `contract_address` for the deployed contract, and various metadata fields for deployment context

### Component B: Daily deployer aggregation  
- **Purpose**: Groups contract creations by day and counts unique deployer addresses
- **Logic**: Truncates creation timestamps to daily boundaries using day-level timestamp truncation. Groups all contract creation records by the truncated daily timestamp. Counts distinct deployer addresses within each day to capture unique entities deploying contracts, ensuring that addresses deploying multiple contracts on the same day are counted only once per day
- **Key fields**: Daily `timestamp` boundary, `deployer_address` for distinct counting, and standardized metadata fields including `chain_id` as 'base', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'

### Final aggregation
- **Combining components**: The fact table provides cleaned, deduplicated input data which feeds directly into the daily aggregation component
- **Currency conversion**: Not applicable as this is a count-based metric
- **Time aggregation**: Contract creation timestamps are truncated to daily boundaries, with all deployments within a 24-hour period aggregated together
- **Final calculation**: The metric applies a distinct count of `deployer_address` values grouped by daily timestamp boundaries, resulting in the number of unique addresses that deployed contracts each day. The finalization macro applies a 'fill_zeros' strategy to ensure days with no contract deployments show zero rather than missing values. Chain availability filtering ensures only periods with complete Base blockchain data coverage are included in the results

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

Unique addresses that deployed at least one smart contract.

Base

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown