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

Gravity Alpha is an L2 smart contract platform for decentralized applications on Ethereum. Gravity Alpha was founded by Galxe and launched in 2024.

G tokenholders own and govern the protocol. Galxe's investors include Arbitrum Foundation, Multicoin Capital, Dragonfly Capital, etc.

github

twitter

discord

website

Blockchains (L2)

Gravity Alpha Mainnet

# Gravity Alpha Mainnet Contract deployers Methodology

## 1. Overview

The contract deployers metric measures the daily count of unique addresses that deployed smart contracts on the GravityAlpha blockchain. This metric provides insight into developer activity and network adoption by tracking how many distinct entities are creating new smart contracts each day. The calculation uses a simple distinct count approach, grouping contract creation events by day and counting unique deployer addresses.

## 2. Data sources

The metric relies on the following raw data sources:

- **GravityAlpha contract creation records**: Parsed blockchain data containing information about smart contract deployments on the GravityAlpha network, including creation timestamps, deployed contract addresses, deployer addresses, and transaction trace addresses
- **GravityAlpha transaction traces**: Underlying blockchain transaction data that captures contract creation events and their associated metadata

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Identify all contract creation events with their associated deployer addresses and timestamps
- **Logic**: Extract contract creation records from GravityAlpha's parsed contract data, selecting the creation timestamp (when the contract was deployed), the deployed contract address, the deployer address (the account that initiated the contract creation), and the transaction trace address for reference
- **Key fields**: `creation_timestamp` (deployment time), `contract_address` (deployed contract), `deployer_address` (entity creating the contract), `creation_trace_address` (transaction reference)

### Component B: Daily aggregation
- **Purpose**: Group contract creations by day and count unique deployers
- **Logic**: Truncate the creation timestamp to daily boundaries to group all contract creations within each calendar day. Count the number of distinct deployer addresses within each day to identify unique entities deploying contracts, regardless of how many contracts each entity deployed
- **Key fields**: `timestamp` (daily boundary), `contract_deployers` (count of unique deployer addresses)

### Final aggregation
- **Combining components**: The daily aggregation directly produces the final metric values by counting distinct deployers per day
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Contract creation timestamps are truncated to daily boundaries (00:00:00 UTC) to group all deployments within each calendar day
- **Final calculation**: For each day, count the number of unique `deployer_address` values that created at least one contract, producing a daily count of distinct contract deployers on the GravityAlpha network

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

Unique addresses that deployed at least one smart contract.

Gravity Alpha MainnetG

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown