website

twitter

Infrastructure

Calyx

# Calyx Active users (daily) Methodology

## 1. Overview

The Calyx Daily Active Users (DAU) metric measures the number of distinct users who interact with Calyx launchpads on the NEAR blockchain each day. Calyx is a DeFi protocol that facilitates token launches through launchpad contracts, and this metric captures investor activity through both traditional token transfers and intent-based transactions. The metric answers the business question: "How many unique users are actively participating in Calyx launchpad investments each day?"

## 2. Data sources

The calculation relies on several types of NEAR blockchain data:

- **NEAR blockchain transactions**: Raw transaction data containing user signatures and transaction arguments
- **NEAR blockchain receipts**: Receipt data confirming successful execution of contract function calls
- **Calyx factory contract events**: Events from the `calyx-factory.near` contract that create new launchpad instances
- **Launchpad contract events**: Function calls on individual launchpad contracts for user interactions and configuration
- **Intent-based transaction data**: Base64-encoded signed intent messages that enable complex multi-step transactions
- **Token transfer validation**: Receipt confirmations for `ft_on_transfer` function calls that validate successful token transfers

## 3. Step-by-step calculation

### Component A: Launchpad identification
- **Purpose**: Identifies all valid Calyx launchpad contracts that should be included in user activity calculations
- **Logic**: Parses NEAR blockchain receipts to find successful `finish_create_launchpad` function calls from the `calyx-factory.near` contract. Only includes receipts with successful execution status and extracts the `launchpad_account_id` from the function call arguments. Enhances this data by identifying the associated sale tokens through `new` method calls on the launchpad contracts, which provides the `sale_token_account_id` used for filtering out token distributions
- **Key fields**: `launchpad_address` from factory events, `sale_token_address` from launchpad configuration, `block_timestamp` for temporal filtering

### Component B: Traditional transfer detection
- **Purpose**: Captures user deposits to Calyx launchpads through standard NEAR token transfers
- **Logic**: Analyzes NEAR transaction data starting from October 5, 2025 (when Calyx was created). Decodes base64-encoded transaction arguments to extract the `receiver_id` field, then filters for transactions where the receiver is a valid Calyx launchpad address. Excludes transactions where the signer is the sale token address to avoid counting token distributions as user activity. Validates against receipt data to ensure the transaction resulted in a successful `ft_on_transfer` function call
- **Key fields**: `signer_account_id` as user identifier, `receiver_id` as launchpad address, `transaction_hash` for linkage, execution status validation

### Component C: Intent-based transaction detection  
- **Purpose**: Captures user interactions through NEAR's intent-based transaction system, which allows for more complex multi-step interactions
- **Logic**: Processes NEAR transactions containing base64-encoded signed intent messages. Decodes the `args_base64` field and parses the nested JSON structure to extract individual signed intents. Filters for `ft_withdraw` intent types that target Calyx launchpad addresses. Excludes intents where the signer is the sale token address. Cross-references with receipt data to confirm the intent resulted in successful `ft_on_transfer` execution
- **Key fields**: `signer_account_id` from intent messages, `receiver_id` from intent targets, `intent_type` for filtering, nested JSON parsing of signed messages

### Component D: Transaction aggregation
- **Purpose**: Combines traditional transfers and intent-based transactions into a unified user activity dataset  
- **Logic**: Unions the results from traditional transfer detection and intent-based transaction detection. Standardizes the data structure by mapping `signer_account_id` to `user_address` and classifying all users as `Investor` type regardless of interaction method. Maintains the `launchpad_address` for context and preserves `block_timestamp` for temporal aggregation
- **Key fields**: `user_address` as the standardized user identifier, `user_type` set to "Investor", `launchpad_address` for context, `block_timestamp` for daily aggregation

### Final aggregation
- **Combining components**: The unified transaction dataset serves as the foundation for DAU calculation, with all user interactions treated equally regardless of whether they used traditional transfers or intent-based methods
- **Time aggregation**: Truncates `block_timestamp` to day boundaries using `timestamp_trunc(block_timestamp, day)` to group all activity within each 24-hour period  
- **Final calculation**: Counts distinct `user_address` values per day to determine the number of unique users who interacted with any Calyx launchpad on each day. The result includes metadata fields like chain ("near"), timestamp_grain ("day"), and applies chain availability filtering to ensure data completeness

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

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

Calyx

Active users (daily)

Active users (daily)

Competitive landscape