website

twitter

Infrastructure

Helio

# Helio Active users (daily) Methodology

## 1. Overview

This metric measures the daily count of unique active users for Heliopay, a payment processing service on Solana. A user is considered active on a given day if they initiated a transaction that resulted in a fee payment to Heliopay's fee collection address. The calculation identifies unique transaction signers (users) per day across both native SOL payments and SPL token payments.

## 2. Data sources

The calculation relies on the following raw blockchain data sources:

- **Solana native transfers**: Parsed native SOL transfer events that capture when SOL is moved between addresses, including the transaction signer, recipient address, transfer amount, and block timestamp
- **Solana SPL token transfers**: Parsed SPL token transfer events that capture when SPL tokens are moved between addresses, including token address, recipient owner, transaction signer, transfer amount, and block timestamp  
- **Solana transaction metadata**: Transaction-level data including transaction signatures, signers, and block timestamps that provide the context for identifying users and timing

## 3. Step-by-step calculation

### Component A: SOL fee payment tracking
- **Purpose**: Identifies users who paid fees to Heliopay using native SOL
- **Logic**: Filters native SOL transfer events to include only transfers where the recipient address is Heliopay's fee collection account `FudPMePeNqmnjMX19zEKDfGXpbp6HAdW6ZGprB5gYRTZ`. Excludes transactions where the transaction signer is also the fee account address to avoid counting internal fee account operations. Captures the `transaction_signer` as the user, `block_timestamp` for timing, and `amount` for the fee paid
- **Key fields**: `transaction_signer` (user address), `block_timestamp` (transaction timing), `amount` (fee amount), hardcoded `token_address` as SOL's address

### Component B: SPL token fee payment tracking  
- **Purpose**: Identifies users who paid fees to Heliopay using SPL tokens
- **Logic**: Filters SPL token transfer events to include only transfers where the recipient owner address is Heliopay's fee collection account. Uses the same exclusion logic to avoid internal fee account transactions. Captures the `transaction_signer` as the user, actual `token_address` of the SPL token used, and transaction details
- **Key fields**: `transaction_signer` (user address), `block_timestamp` (transaction timing), `token_address` (SPL token used), `amount` (fee amount in token units)

### Final aggregation
- **Combining components**: The SOL and SPL fee data are combined using a union operation to create a unified dataset of all fee-generating transactions
- **Time aggregation**: Block timestamps are truncated to day boundaries using day-level truncation, with all transactions grouped by the resulting daily timestamp
- **User identification**: For each day, the calculation counts distinct `transaction_signer` addresses across both SOL and SPL transactions
- **Final calculation**: The result is the count of unique users per day who initiated transactions resulting in fee payments to Heliopay, with each user counted only once per day regardless of how many fee transactions they made or whether they used SOL, SPL tokens, or both

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

Unique revenue-generating users over a fixed 24-hour window.

Helio

Active users (daily)

Active users (daily)

Competitive landscape