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 fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average transaction fees paid per active user on the Darwinia network on a daily basis. This metric answers the business question: "How much does each active user contribute in transaction fees per day?" The calculation divides total daily fees (in USD) by the number of distinct daily active users across both Darwinia's native Substrate chain and its EVM-compatible layer.

## 2. Data sources

- **Darwinia blockchain events**: Parsed event logs from the Darwinia Substrate blockchain, including `TransactionFeePaid`, `NewAccount`, `Executed`, and balance events
- **Darwinia extrinsic data**: Native Substrate transaction records containing extrinsic signers and execution details  
- **EVM execution events**: Events from Darwinia's EVM compatibility layer, tracking `Withdraw` and `Deposit` balance changes related to EVM transactions
- **End-of-day price feeds**: Daily USD price data for RING tokens from CoinGecko API using the identifier 'darwinia-network-native-token'
- **Account mapping data**: Address conversion data between Substrate SS58 format and EVM hex format addresses

## 3. Step-by-step calculation

### Component A: Daily active user tracking
- **Purpose**: Count distinct users who perform transactions on either the native Substrate chain or EVM layer
- **Logic**: Extract transaction senders from Darwinia extrinsic records as active users on the native chain. For the EVM layer, identify users from `Executed` events in the ethereum pallet where EVM transactions are processed. All users are classified as 'Transaction sender' user type. Aggregate using HyperLogLog to count distinct users per day across both chains while avoiding double-counting users active on multiple layers.
- **Key fields**: `block_timestamp` for daily aggregation, `id` from extrinsics as user addresses, `event_data` from EVM execution events containing user addresses

### Component B: Layer 1 (Substrate) fee collection  
- **Purpose**: Calculate fees paid on the native Darwinia Substrate chain
- **Logic**: Extract fee payments from `TransactionFeePaid` events in successful extrinsics. Sum the base `amount` and `tip` components for each transaction. Convert from native token decimals by dividing by 1e18. Aggregate fees by day.
- **Key fields**: `amount` and `tip` from event data, `block_timestamp` for daily aggregation, `success` flag to filter only completed transactions

### Component C: Layer 2 (EVM) fee collection
- **Purpose**: Calculate fees paid through EVM-compatible transactions on Darwinia
- **Logic**: Track EVM transaction fees by monitoring balance `Withdraw` and `Deposit` events in the balances pallet that are associated with EVM execution. Match these balance changes to EVM `Executed` events by `extrinsic_id`. Use address mapping between Substrate and EVM formats to ensure the signer of balance events matches the EVM transaction executor. Sum positive withdrawals and negative deposits to determine net fees. Convert from native decimals and aggregate daily.
- **Key fields**: `transaction_fee` from balance events, `extrinsic_id` for matching, `signer_address` for validation, `timestamp` for daily grouping

### Component D: Address mapping
- **Purpose**: Convert between Substrate SS58 and EVM hex address formats for cross-layer validation
- **Logic**: Extract account creation events from the system pallet `NewAccount` events. Use a custom JavaScript function to decode SS58 addresses to hex format. Generate corresponding EVM addresses using keccak256 hash of the concatenated string "evm:" + substrate_hex, taking bytes 12-32 of the hash result. This mapping ensures proper attribution of EVM fees to the correct Substrate account.
- **Key fields**: `parachain_account` in SS58 format, `evm_account` in hex format derived through cryptographic transformation

### Final aggregation
- **Combining components**: Sum L1 and L2 fees for each day to get total daily fees. Count distinct users across both layers using HyperLogLog to get daily active users without double-counting.
- **Currency conversion**: Convert native RING token fees to USD using end-of-day prices from CoinGecko API for 'darwinia-network-native-token' identifier
- **Time aggregation**: Truncate all timestamps to daily boundaries using `timestamp_trunc` with 'day' granularity
- **Final calculation**: Divide total daily fees (USD) by daily active user count using the `calculate_arpu` macro, which handles the division and applies appropriate null handling for days with zero users or fees. Missing data is filled with zeros using the 'fill_zeros' strategy.

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

Darwinia NetworkRING

Archived

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape