Validators process transactions and receive fees from users (supply-side fees).

Conflux is a smart contract platform for decentralized applications (a blockchain). Conflux was founded by David Chow, Fan Long, Ming Wu, and YuanJie Zhang and launched in 2020. Note that this dashboard only includes Conflux Core Space.

CFX holders own and govern the protocol. They currently do not take a cut of the total transaction fees paid by users (revenue).

governance

github

twitter

discord

website

Blockchains (L1)

Conflux Core Space

# Conflux Core Space Revenue Methodology

## 1. Overview

The Conflux revenue metric tracks protocol revenue generated by the Conflux blockchain. Currently, this metric is explicitly set to zero for all time periods, indicating that Conflux does not generate protocol revenue from its operations. The calculation leverages the existing transaction fee infrastructure but sets all revenue values to 0, maintaining the proper data structure and schema while reflecting that Conflux operates without direct revenue streams.

## 2. Data sources

The revenue calculation depends on the following underlying data sources:

- **Conflux blockchain transactions**: Raw transaction records from the Conflux blockchain containing transaction fees and metadata
- **End-of-day price feeds**: CoinGecko price data for CFX token to enable USD conversion of fee amounts
- **Token metadata**: Information about the CFX native token including symbol and CoinGecko identifier

## 3. Step-by-step calculation

### Component A: Transaction fee extraction
- **Purpose**: Extract and process all Conflux blockchain transactions to identify fee amounts
- **Logic**: The system processes raw Conflux transaction data to extract key transaction details including `block_timestamp`, `transaction_hash`, sender address (`from_address`), transaction success status (`is_successful`), and most importantly the `fee_amount` paid for each transaction. Each transaction is labeled with chain identifier 'conflux', token symbol 'CFX', and CoinGecko ID 'conflux-token' for downstream processing
- **Key fields**: `block_timestamp` for temporal analysis, `fee_amount` containing the CFX fee paid, `is_successful` indicating transaction status, and `from_address` identifying the fee payer

### Component B: Daily fee aggregation  
- **Purpose**: Aggregate transaction fees on a daily basis and convert to USD
- **Logic**: Transaction fees are grouped by daily timestamp boundaries using `timestamp_trunc` to create daily aggregations. The system sums all `fee_amount` values for each day, creating total daily fee volumes. Fees are then converted from CFX to USD using end-of-day CoinGecko price feeds for the CFX token. Each daily record is tagged with market sector 'blockchains_l1', business segment 'blockchain', and chain identifier 'conflux'
- **Key fields**: `daily_timestamp` for the aggregation boundary, `fees` containing the USD-converted daily fee total, and various classification fields for data categorization

### Component C: Revenue calculation
- **Purpose**: Generate the final revenue metric based on fee data structure
- **Logic**: The revenue calculation fetches the timestamp, grain, and metadata structure from the processed fees data but explicitly sets the `revenue` field to 0 for all records. This creates a complete revenue dataset with proper temporal coverage and schema compliance while reflecting that Conflux currently generates no protocol revenue. The system maintains the same daily timestamp boundaries and chain classification as the underlying fees data
- **Key fields**: `timestamp` and `timestamp_grain` for temporal structure, `product_id` and `chain_id` for classification, and `revenue` explicitly set to 0

### Final aggregation
- **Combining components**: The revenue metric inherits the temporal and categorical structure from the fees calculation but replaces all fee amounts with zero revenue values
- **Currency conversion**: Not applicable since all revenue values are set to 0
- **Time aggregation**: Daily boundaries are maintained from the underlying fees data structure, ensuring consistent temporal coverage
- **Final calculation**: The final revenue value is always 0 for all time periods, indicating Conflux operates without direct protocol revenue streams. The metric maintains proper schema validation and gap filling through the finalization macro while applying chain availability filters to restrict data to supported time periods

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

fees * take_rate (illustrative — revenue is observed directly per project, not derived from take_rate)

Fee revenue retained after supply-side payouts. Before cost of revenue (e.g. L2 DA fees) and before operating expenses.

Conflux Core SpaceCFX

Archived

Revenue

Revenue

Competitive landscape