website

twitter

Infrastructure

Calyx

# Calyx Trade count Methodology

## 1. Overview

The Calyx trade count metric measures the daily number of unique funding transactions on Calyx launchpads deployed on the NEAR blockchain. This metric captures trading activity by counting distinct token transfer events where users send tokens to launchpad contracts to participate in token sales or fundraising campaigns. The calculation identifies legitimate launchpad contracts through factory contract events and tracks funding transactions via NEAR's standardized token transfer protocol.

## 2. Data sources

The calculation relies on several types of NEAR blockchain data:

- **NEAR transaction receipts**: Complete transaction data including method calls, arguments, and execution status from the NEAR blockchain
- **Calyx factory contract events**: Successful launchpad creation events from the `calyx-factory.near` contract containing launchpad configuration data
- **Function call data**: Base64-encoded JSON arguments from NEAR function calls containing launchpad addresses, token configurations, and transfer details
- **Token transfer events**: NEAR protocol `ft_on_transfer` method calls representing standardized token transfers between accounts
- **Launchpad contract interactions**: Method calls to individual launchpad contracts for configuration and funding operations

## 3. Step-by-step calculation

### Component A: Launchpad identification
- **Purpose**: Identify all legitimate Calyx launchpad contracts deployed through the official factory
- **Logic**: Filter NEAR transaction receipts for successful `finish_create_launchpad` method calls originating from the `calyx-factory.near` contract. Parse the base64-encoded function call arguments to extract the `launchpad_account_id` field, which contains the deployed launchpad contract address. Only include transactions with successful execution status and timestamps after October 5, 2025 (Calyx protocol launch date).
- **Key fields**: `launchpad_address` extracted from decoded function arguments, `block_timestamp` for temporal filtering, `receipt_id` for transaction identification

### Component B: Token configuration mapping
- **Purpose**: Associate each launchpad with its designated sale token to distinguish funding transactions from other token transfers
- **Logic**: For each identified launchpad contract, capture `new` method calls that configure the launchpad settings. Parse the base64-encoded function call arguments to extract the `sale_token_account_id` from the configuration object. This creates a mapping between launchpad contracts and their respective sale tokens, enabling proper transaction classification.
- **Key fields**: `sale_token_address` from launchpad configuration, `launchpad_address` as the foreign key linking to component A

### Component C: Trade event capture
- **Purpose**: Identify individual funding/trading transactions where users send tokens to launchpad contracts
- **Logic**: Filter NEAR receipts for successful `ft_on_transfer` method calls where the `receiver_account_id` matches a known launchpad address from component A. Extract the `amount` field from decoded function arguments to capture transaction value. Exclude transfers where the `predecessor_account_id` (sender) matches the launchpad's designated sale token address to avoid counting token distribution events as trades. Only include successful transactions after the Calyx launch date.
- **Key fields**: `receipt_id` as unique transaction identifier, `token_address` (predecessor), `receiver_id` (launchpad), `amount` of tokens transferred, `launchpad_token` for filtering logic

### Final aggregation
- **Combining components**: Join trade events with launchpad identification data using launchpad addresses as the key, ensuring only legitimate launchpad transactions are counted
- **Time aggregation**: Truncate `block_timestamp` to daily boundaries using day-level precision, grouping all transactions within each 24-hour period
- **Trade counting**: Apply `approx_count_distinct` function to `receipt_id` values within each day to count unique transactions, providing efficient computation for large datasets while maintaining accuracy
- **Final calculation**: The daily trade count represents the number of distinct funding transactions to Calyx launchpads, processed through the `finalize_metric_trade_count` macro with 'fill_zeros' strategy to ensure consistent time series data with zero values for days without trading activity

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

Number of trades executed on a decentralized exchange.

Calyx

Trade count

Trade count

Competitive landscape