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 Revenue Methodology

## 1. Overview

NeuroWeb revenue is measured as the total fees collected by the protocol from its Layer 1 parachain operations and NeuroWeb EVM compatibility layer. Since fees are not distributed to supply-side participants such as validators or stakers, revenue is equivalent to the total fees collected from users. The protocol's ability to generate income from transaction processing across its dual-layer blockchain architecture is measured by this metric.

## 2. Data sources

- **Blockchain events**: `TransactionFeePaid` events from `transactionPayment` pallets, `Executed` events from `ethereum` pallets, and `Withdraw` and `Deposit` events from `balances` pallets, covering NeuroWeb and NeuroWeb EVM
- **External data**: End-of-day price feeds for the NEUROWEBAI asset and account mapping metadata

## 3. Step-by-step calculation

### Component A: L1 parachain fees

- **Purpose**: Captures transaction fees paid on NeuroWeb's Layer 1 parachain for native operations
- **Logic**: `TransactionFeePaid` events are processed from the `transactionPayment` pallet. Transaction fee and tip amounts are extracted from the event data arrays and summed together. Amounts are normalized by decimal precision and grouped by day.
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `timestamp`

### Component B: NeuroWeb EVM fees

- **Purpose**: Captures transaction fees from operations executed on the NeuroWeb EVM layer
- **Logic**: EVM executions are identified through `Executed` events from the `ethereum` pallet to extract the signer address. Corresponding `Withdraw` and `Deposit` events are processed from the `balances` pallet to represent fee collection and refunds. These events are matched by extrinsic ID and validated using an account mapping table to ensure the balance change signer corresponds to the execution signer. Net fees are calculated by summing withdraw amounts and subtracting deposit amounts. Amounts are normalized by decimal precision and grouped by day.
- **Key fields**: `signer_address`, `transaction_fee`, `extrinsic_id`, `event_method`

### Component C: Supply-side fees

- **Purpose**: Represents fees distributed to supply-side participants
- **Logic**: Supply-side fees are set to a constant value of zero. No portion of the collected transaction fees is distributed to validators or other infrastructure providers.
- **Key fields**: `fees_supply_side`

### Component D: USD conversion and aggregation

- **Purpose**: Normalize values to USD and combine protocol layers
- **Logic**: L1 and NeuroWeb EVM fees are combined into a comprehensive dataset. End-of-day price feeds for the NEUROWEBAI asset are applied to convert native units to USD values. Daily aggregation is performed using UTC day boundaries, and gap filling with zeros is applied for any missing days.
- **Key fields**: `revenue`, `timestamp`

*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.

NeuroWebNEURO

Archived

Revenue

Revenue

Competitive landscape

Chain breakdown