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 Active addresses (daily) Methodology

## 1. Overview

Daily active addresses measures the number of unique addresses that initiated at least one transaction on the GravityAlpha blockchain within a 24-hour period. This metric serves as a proxy for user activity and engagement on the GravityAlpha network. The calculation treats each unique transaction sender address as an active address, using HyperLogLog algorithms for efficient distinct counting across multiple dimensional breakdowns.

## 2. Data sources

- **GravityAlpha blockchain transactions**: Raw transaction records from the GravityAlpha blockchain containing sender addresses, timestamps, gas data, and transaction metadata
- **Transaction sender addresses**: The `from_address` field from each transaction, representing the initiating wallet address
- **Block timestamp data**: Timestamp information for each transaction block to enable daily aggregation
- **Transaction metadata**: Transaction hashes, recipient addresses, gas prices, and gas usage amounts for context

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Extract and standardize all GravityAlpha transaction data
- **Logic**: Retrieves all transactions from the GravityAlpha blockchain source, extracting sender addresses (`from_address`), recipient addresses (`to_address`), block timestamps, transaction hashes, and gas-related fields. Sets the token address to the hardcoded GravityAlpha token contract address `0xbb859e225ac8fb6be1c7e38d87b767e95fef0ebd` and token symbol to `G`. Calculates gas fees by multiplying gas used by gas price and converting from wei to standard units
- **Key fields**: `from_address` (transaction sender), `block_timestamp` (transaction timing), `transaction_hash` (unique identifier), `gas_price` and `gas_used_amount` (fee calculation)

### Component B: User address identification
- **Purpose**: Identify unique daily active addresses from transaction senders
- **Logic**: Takes processed transaction data and focuses on the `from_address` field as the active user address. Truncates block timestamps to daily boundaries using timestamp truncation. Classifies each sender as a "Transaction sender" user type and assigns chain-level metadata including market sector as "blockchains_l2" and business segment as "blockchain". Applies incremental processing logic to handle only new or updated data efficiently
- **Key fields**: `user_dau` (renamed from `from_address`), `timestamp` (daily boundary), `chain` (set to 'gravityalpha'), `user_type` (set to 'Transaction sender')

### Component C: HyperLogLog distinct counting
- **Purpose**: Efficiently count distinct active addresses across multiple dimensions
- **Logic**: Initializes HyperLogLog sketches with precision 15 for each unique address per day, enabling approximate distinct counting with high accuracy. Groups data by timestamp, chain, user type, and product to create separate HyperLogLog sketches. Creates four dimensional breakdowns: project-level aggregation (combining all addresses), chain-level breakdown (by individual chain), user-type-level breakdown (by transaction sender type), and product-level breakdown (by product classification). Merges partial HyperLogLog sketches within each dimension and extracts the final distinct count
- **Key fields**: `hll` (HyperLogLog sketch), `user_dau` (distinct count result), `dimensions` (breakdown type), `chain_id` (chain identifier)

### Final aggregation
- **Combining components**: Unions all dimensional breakdowns (project, chain, user type, product) into a single dataset with consistent schema structure
- **Currency conversion**: No currency conversion required as this metric counts addresses rather than monetary values
- **Time aggregation**: Daily boundaries are established by truncating transaction timestamps to day granularity, ensuring consistent 24-hour periods
- **Final calculation**: Renames the `user_dau` field to `active_addresses_daily` to reflect that for blockchain protocols, active users are equivalent to active addresses. Applies data quality filters including chain availability checks and fills missing days with zero values to maintain continuous time series

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

Unique active addresses over a fixed 24-hour window.

Gravity Alpha MainnetG

Active addresses (daily)

Active addresses (daily)

Competitive landscape

Chain breakdown