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 Transaction count Methodology

## 1. Overview

The Gravity Alpha transaction count metric measures the daily number of unique transactions executed on the Gravity Alpha blockchain. This metric provides insight into blockchain usage and activity levels by counting distinct transaction hashes per day. The calculation aggregates all transactions regardless of their type or purpose, providing a comprehensive view of on-chain activity.

## 2. Data sources

- **Gravity Alpha transaction records**: Raw blockchain transaction data including transaction hashes, block timestamps, sender and receiver addresses, gas prices, and gas usage amounts
- **Token metadata**: Hardcoded Gravity Alpha native token information including the token contract address `0xbb859e225ac8fb6be1c7e38d87b767e95fef0ebd` and symbol `G`

## 3. Step-by-step calculation

### Component A: Raw transaction processing
- **Purpose**: Extract and standardize all Gravity Alpha blockchain transactions
- **Logic**: Pull distinct transactions from Gravity Alpha blockchain transaction records, capturing essential transaction details including `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, gas pricing (`receipt_effective_gas_price`), and gas usage (`receipt_gas_used`). Convert gas values to bignumeric type for accurate calculation. Calculate gas fees by multiplying gas used amount by gas price and dividing by 1e18 to convert from wei to native token units.
- **Key fields**: `transaction_hash` for unique identification, `block_timestamp` for time-based aggregation, `to_address` for recipient tracking, calculated `gas_fee_amount` for transaction cost analysis

### Component B: Daily aggregation
- **Purpose**: Group transactions by day and count unique occurrences
- **Logic**: Truncate `block_timestamp` to daily granularity using day-level timestamp truncation. Group transactions by the truncated timestamp and `to_address`. Count distinct `transaction_hash` values within each group to ensure each unique transaction is counted exactly once per day per recipient address. Apply incremental processing logic that processes only recent data based on the maximum partition date plus a configurable lookback window.
- **Key fields**: `timestamp` (daily truncated), `transaction_count` (distinct hash count), `to_address` for recipient-level aggregation

### Component C: Metadata enrichment
- **Purpose**: Add classification and labeling information
- **Logic**: Assign static metadata values to categorize transactions within the Token Terminal taxonomy. Set `chain_id` to 'gravityalpha', `market_sector_id` to 'blockchains_l2' (classifying Gravity Alpha as a Layer 2 blockchain), `business_segment_id` to 'blockchain', and `product_id` to null since this measures overall blockchain activity rather than specific product usage. Apply timestamp grain labeling as 'day' to indicate daily aggregation level.
- **Key fields**: Classification dimensions for data organization and filtering

### Component D: Label application
- **Purpose**: Enrich transaction data with address labeling
- **Logic**: Join aggregated transaction data with address label information to identify known addresses, protocols, or entities. Currently, this step passes through transaction data without applying specific labels, but maintains the framework for future label enrichment.
- **Key fields**: Maintains all transaction metrics while preparing for label-based analysis

### Final aggregation
- **Combining components**: Apply the `finalize_metric_transaction_count` macro which validates the data schema, ensures consistent field types, and implements gap-filling logic using a 'fill_zeros' strategy to create records with zero transaction counts for days without activity
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries determined by timestamp truncation to day level, with incremental processing ensuring recent data updates
- **Final calculation**: The final metric represents the count of distinct transaction hashes per day on Gravity Alpha blockchain, with chain availability filtering applied to exclude data from periods when the blockchain was not operational or data collection was unavailable

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

Confirmed transactions added to the blockchain.

Gravity Alpha MainnetG

Transaction count

Transaction count

Competitive landscape

Chain breakdown