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

Arbitrum One is an L2 smart contract platform for decentralized applications on Ethereum. Arbitrum was founded by Offchain Labs and launched in 2021.

ARB tokenholders own and govern the protocol. They currently run the only sequencer and take a cut of the total transaction fees paid by users (revenue). Arbitrum’s investors include Polychain, Alameda Research, Coinbase Ventures, etc.

github

twitter

discord

etherscan

website

Blockchains (L2)

Arbitrum One

# Arbitrum One Contract deployers Methodology

## 1. Overview

The Arbitrum contract deployers metric measures the number of unique addresses that deploy smart contracts on the Arbitrum blockchain each day. This metric provides insight into developer activity and ecosystem growth by tracking how many distinct entities are creating new contracts on the network daily.

## 2. Data sources

- **Arbitrum contract creation events**: Parsed blockchain data containing all smart contract deployments on Arbitrum, including deployer addresses, contract addresses, creation timestamps, and transaction trace information
- **Arbitrum transaction traces**: Detailed transaction execution data that allows identification of contract creation operations
- **Arbitrum block timestamps**: Block-level timing data used for daily aggregation boundaries

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identifies all contract deployment events on Arbitrum with their associated deployer addresses
- **Logic**: Extracts contract creation records from Arbitrum blockchain data, capturing the `creation_timestamp` when each contract was deployed, the `contract_address` of the newly created contract, and the `deployer_address` of the entity that initiated the deployment. Applies deduplication to ensure each contract creation event is counted only once, even if it appears multiple times in the raw data due to data processing artifacts.
- **Key fields**: `creation_timestamp` for timing, `deployer_address` for identifying the deploying entity, `contract_address` for the deployed contract, and `creation_trace_address` for transaction traceability

### Component B: Daily aggregation and counting
- **Purpose**: Groups contract deployments by day and counts unique deployers per day
- **Logic**: Groups all contract creation events by day using timestamp truncation to daily boundaries. For each day, counts the number of distinct `deployer_address` values using an approximate count distinct function for performance optimization on large datasets. Adds metadata fields including chain identifier as 'arbitrum', market sector as 'blockchains_l2', and business segment as 'blockchain'.
- **Key fields**: `timestamp` truncated to day level, `contract_deployers` as the distinct count of deployer addresses

### Final aggregation
- **Combining components**: The daily aggregated data flows directly from the grouping operation without additional joins
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, ensuring consistent 24-hour periods
- **Final calculation**: The final metric value represents the approximate count of distinct addresses that deployed at least one smart contract on Arbitrum during each calendar day, with gap-filling logic applied to ensure zero values for days with no deployments and data availability filters applied for quality assurance

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

Unique addresses that deployed at least one smart contract.

Arbitrum OneARB

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown