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

NeuroWeb is a decentralized Artificial Intelligence blockchain powered by Polkadot Relay chain.

NEURO holders own and govern the protocol.

website

github

twitter

etherscan

Blockchains (L2)

NeuroWeb

# NeuroWeb Fees Methodology

## 1. Overview

Fees measures the total transaction fees paid by users on the NeuroWeb blockchain, which operates as a dual-layer system with both parachain (L1) and NeuroWeb EVM (L2) components. Direct parachain transaction fees as well as EVM layer fees flowing through the balance system are captured to provide a comprehensive view of user costs for interacting with the network. All fees are converted to USD using end-of-day price feeds.

## 2. Data sources

- **Blockchain events**: `TransactionFeePaid` events from `transactionPayment` contracts, `Executed` events from `ethereum` contracts, and `Withdraw` and `Deposit` events from `balances` contracts, covering NeuroWeb and NeuroWeb EVM
- **Account mapping data**: Cross-reference data linking EVM addresses to corresponding parachain account addresses for proper fee attribution across layers
- **External data**: End-of-day price feeds for native assets

## 3. Step-by-step calculation

### Component A: L1 parachain fees

- **Purpose**: Capture direct transaction fees paid for parachain operations
- **Logic**: Blockchain events are filtered for `TransactionFeePaid` events from `transactionPayment` contracts. The `transaction_fee` and `transaction_tip` values are extracted from the structured event data and summed together to calculate the total cost per transaction. Amounts are normalized by decimal precision.
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `timestamp`

### Component B: NeuroWeb EVM layer fees

- **Purpose**: Capture fees associated with EVM transactions processed through the balance system
- **Logic**: EVM execution events are identified from `Executed` events in `ethereum` contracts to determine transactions involving EVM operations and to extract EVM signer addresses. Balance change events, specifically `Withdraw` and `Deposit` events from `balances` contracts, are captured within these transactions. Account mappings are used to match EVM addresses with their corresponding parachain addresses. Data is filtered to include only balance changes where the signer address matches across both layers, ensuring proper fee attribution. `Withdraw` events are treated as positive fees and `Deposit` events are treated as negative values (refunds) to determine the net fee per transaction. Amounts are normalized by decimal precision.
- **Key fields**: `transaction_fee`, `signer_address`, `extrinsic_id`, `event_method`

### Component C: USD conversion and aggregation

- **Purpose**: Combine components and normalize to USD
- **Logic**: L1 and L2 fees are combined using a union operation to create a unified dataset. Native asset amounts are converted to USD using end-of-day price feeds. All fees are aggregated at the daily level using UTC day boundaries. Zero-filling is applied for days with no fee activity to maintain a complete time series.

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

Total value users pay to use a protocol (gross fees, user-paid fees).

NeuroWebNEURO

Archived

Fees

Fees

Competitive landscape

Chain breakdown