Manta Pacific batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense). Manta Pacific stores call data on Celestia’s modular data availability network.

Manta Pacific is an L2 smart contract platform for decentralized applications on Ethereum. Manta Pacific was founded by Manta Network and launched in 2023.

Manta Network team owns and governs the protocol. Manta Network's investors include Polychain Capital, Qiming Venture Partners, Binance Labs, etc.

github

twitter

discord

etherscan

website

Blockchains (L2)

Manta

# Manta Contract deployers Methodology

## 1. Overview

Contract deployers is defined as the number of unique addresses that have deployed at least one smart contract on Manta Pacific. This metric is utilized as a proxy for the number of independent developers or entities actively publishing code onchain. Developer activity and ecosystem growth are quantified through the tracking of these unique deployer addresses over time.

## 2. Data sources

- **Blockchain events**: Contract creation traces from the Manta Pacific network, covering Manta Pacific

## 3. Step-by-step calculation

### Component A: Contract creation extraction

- **Purpose**: Identify all smart contract deployments on Manta Pacific
- **Logic**: Contract creation records are extracted from the underlying blockchain data. For each contract deployment, the creation timestamp, the deployed contract address, and the deployer address are identified. Only unique contract creations are retained to prevent duplicate counting of the same deployment trace.
- **Key fields**: `block_timestamp`, `contract_address`, `deployer_address`

### Component B: Daily deployer aggregation

- **Purpose**: Aggregate the number of unique deployers on a daily basis
- **Logic**: The contract creation timestamps are truncated to daily granularity. For each day, the number of unique deployer addresses is counted. This ensures that even if a single developer address deploys multiple contracts within a single day, it is only counted once for that day.
- **Key fields**: `block_timestamp`, `deployer_address`

### Component C: Normalization and validation

- **Purpose**: Ensure data consistency and completeness across the time series
- **Logic**: The aggregated daily counts are cast to the correct data types and validated against active chain and project identifiers. Days with no recorded deployments are assigned a value of zero to maintain a continuous daily record. Chain availability filters are applied to align the data with approved reporting periods.
- **Key fields**: `timestamp`, `chain_id`, `product_id`, `contract_deployers`

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

Unique addresses that deployed at least one smart contract.

MantaMANTA

Archived

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown