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 Contracts deployed Methodology

## 1. Overview

The Arbitrum contracts deployed metric measures the daily number of new smart contracts deployed on the Arbitrum blockchain. This metric tracks ecosystem growth by counting each unique contract creation event that occurs on-chain. The calculation aggregates contract deployment transactions by day to provide a time series view of development activity on Arbitrum.

## 2. Data sources

The metric relies on the following raw data sources:

- **Arbitrum blockchain data**: Transaction traces and execution data from the Arbitrum L2 blockchain containing contract deployment information
- **Contract creation events**: Parsed blockchain data identifying when new contracts are deployed, including creation timestamps, deployed contract addresses, and deployer account information  
- **Block timestamp data**: Arbitrum block timestamps used to determine the exact time when contract deployments occurred

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identify and extract all contract deployment events from Arbitrum blockchain data
- **Logic**: The system processes Arbitrum blockchain transaction traces to identify contract creation events. Each record contains the `creation_timestamp` (when the contract was deployed), `contract_address` (address of the newly created contract), `deployer_address` (account that initiated the deployment), and `creation_trace_address` (transaction trace reference). The data uses distinct filtering to ensure each contract creation is counted only once, preventing duplicate counting from multiple trace entries for the same deployment.
- **Key fields**: `creation_timestamp` provides the deployment timing, `contract_address` uniquely identifies each deployed contract, `deployer_address` tracks the deploying account, `creation_trace_address` links to the originating transaction trace

### Component B: Daily aggregation  
- **Purpose**: Group contract deployments by day and count the total number of contracts deployed per day
- **Logic**: Contract creation records are grouped by day using timestamp truncation to day boundaries. The system counts all contract deployments that occurred within each 24-hour period. Standard metadata dimensions are added including `chain_id` set to 'arbitrum', `market_sector_id` set to 'blockchains_l2' (indicating Layer 2 blockchain sector), `business_segment_id` set to 'blockchain', and `product_id` set to null (since this is a chain-level metric rather than product-specific).
- **Key fields**: `timestamp` represents the day boundary, `contracts_deployed` contains the daily count of new contracts

### Final aggregation
- **Combining components**: The daily contract counts flow directly from the aggregation step without additional combining since this is a single-source metric
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day containing the total count of contracts deployed during that 24-hour period
- **Standardization**: The `finalize_metric_contracts_deployed` macro applies standardized formatting and implements a fill-zeros strategy to ensure continuous time series data with zero values for days when no contracts were deployed
- **Data quality**: A chain availability filter ensures only valid time periods with complete blockchain data are included in the final metric, maintaining data quality and consistency across the time series

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

Unique smart contracts published onchain.

Arbitrum OneARB

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown