Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Darwinia Network is a decentralized blockchain for cross-chain interoperability and decentralized finance infrastructure powered by Polkadot Relay chain.

RING holders own and govern the protocol. Darwinia Network’s investors include HashKey, Waterdrip Capital, SevenX Ventures, etc.

website

twitter

discord

Blockchains (L2)

Darwinia Network

# Darwinia Network Average revenue per user (ARPU) Methodology

## 1. Overview

Average Revenue Per User (ARPU) measures the average daily revenue generated per active user on the Darwinia network. This metric is calculated by dividing total daily revenue by the number of daily active users. Darwinia operates as a dual-layer blockchain with both substrate-based transactions and an EVM-compatible layer, requiring comprehensive tracking across both execution environments to capture complete user activity and fee revenue.

## 2. Data sources

The calculation draws from several raw blockchain data sources:

- **Darwinia substrate events**: Parsed `TransactionFeePaid` events capturing transaction fees and tips, and `NewAccount` system events for address mapping
- **Darwinia EVM events**: Parsed `Executed` events from the `ethereum` pallet indicating EVM transaction execution
- **Darwinia balance events**: `Withdraw` and `Deposit` events from the `balances` pallet tracking fee payments for EVM transactions
- **Substrate extrinsic records**: Transaction records from Darwinia's substrate layer containing sender addresses and execution details
- **End-of-day price feeds**: CoinGecko price data for Darwinia Network Native Token (RING) used for USD conversion
- **Account mapping data**: System-generated account relationships between substrate SS58 addresses and derived EVM addresses

## 3. Step-by-step calculation

### Component A: Daily active users calculation

- **Purpose**: Count distinct users who executed transactions on either Darwinia's substrate or EVM layers
- **Logic**: Extract transaction senders from substrate extrinsic records, identifying them as `Transaction sender` user types. Additionally, capture EVM transaction executors from ethereum Executed events. The system tracks users across both chains (`darwinia` for substrate transactions and `Darwinia EVM` for EVM transactions), ensuring comprehensive coverage of network activity. Users are deduplicated using HyperLogLog aggregation to efficiently count distinct addresses per day
- **Key fields**: `user_address` from extrinsics and event data, `block_timestamp` for daily aggregation, `chain` to distinguish between substrate and EVM layers

### Component B: Address mapping and normalization  

- **Purpose**: Enable cross-layer tracking between substrate and EVM addresses for the same user
- **Logic**: Process `NewAccount` system events to extract substrate account addresses. Convert substrate SS58 addresses to hex format using base58 decoding, then derive corresponding EVM addresses using keccak256 hashing of the substrate address prefixed with "evm:". This mapping ensures that fees paid on the EVM layer can be correctly attributed to substrate account holders
- **Key fields**: `parachain_account` (original substrate address), `evm_account` (derived EVM address), substrate hex representation for conversion

### Component C: Substrate layer revenue collection

- **Purpose**: Capture transaction fees from native substrate transactions  
- **Logic**: Extract `TransactionFeePaid` events from successful transactions, parsing the `amount` and `tip` fields from event data. Convert raw token amounts from the smallest unit by dividing by 1e18 (Darwinia's token decimals). Aggregate daily totals of fees plus tips for all successful substrate transactions
- **Key fields**: `amount` (base transaction fee), `tip` (additional fee), `block_timestamp` for daily aggregation, success status for filtering

### Component D: EVM layer revenue collection

- **Purpose**: Calculate net fees paid for EVM transactions through balance movements
- **Logic**: Track EVM transaction fees by monitoring balances Withdraw and balances Deposit events within the EVM pallet context. Match these balance movements to `evm.Executed` events using extrinsic IDs to ensure fees are attributed to actual EVM transaction execution. Use the address mapping to verify that withdrawal/deposit signers match the EVM transaction executors. Calculate net fees as withdrawals minus deposits per transaction, then aggregate daily totals
- **Key fields**: `transaction_fee` (net balance movement), `extrinsic_id` for transaction matching, `signer_address` for attribution verification

### Component E: Fee aggregation and USD conversion

- **Purpose**: Combine fees from both layers and convert to USD for standardized reporting
- **Logic**: Sum substrate fees (amount plus tip) and EVM layer net fees to get total daily fee revenue. Convert the aggregate native token amounts to USD using end-of-day Darwinia token prices from CoinGecko. Apply the conversion at the daily level to ensure consistent pricing across all transactions within each day
- **Key fields**: Combined `fees` from both layers, `timestamp` for price lookup, converted USD amounts

### Final aggregation

- **Combining components**: Join the daily active user counts with daily revenue totals by matching on date timestamps. Both components are aggregated to daily granularity using timestamp truncation to day boundaries
- **Currency conversion**: USD conversion happens at the revenue aggregation step using end-of-day CoinGecko prices for the Darwinia Network Native Token
- **Time aggregation**: All data is grouped by calendar day using timestamp truncation, ensuring consistent daily boundaries across user counts and revenue calculations
- **Final calculation**: Calculate ARPU by dividing the total daily USD revenue by the count of distinct daily active users. The result represents the average revenue generated per user on each day across both Darwinia's substrate and EVM execution layers

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

Darwinia NetworkRING

Archived

Average revenue per user (ARPU)

Average revenue per user (ARPU)

Competitive landscape