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 Contracts deployed Methodology

## 1. Overview

The contracts deployed metric measures the daily number of smart contracts deployed on the Neuroweb blockchain. This metric tracks ecosystem growth by counting new contract creations each day. The calculation identifies contract deployments through Neuroweb's substrate-based event system, which generates specific pallet events when new contracts are created and executed.

## 2. Data sources

- **Neuroweb blockchain event logs**: Raw event data from the Neuroweb substrate-based blockchain containing pallet events, methods, and JSON-formatted event data
- **System pallet events**: `NewAccount` events that indicate when new accounts or contracts are created on the network
- **Ethereum pallet events**: `Executed` events that provide execution context and deployer information for EVM-compatible transactions

## 3. Step-by-step calculation

### Component A: Base event processing
- **Purpose**: Structure and prepare raw Neuroweb blockchain events for analysis
- **Logic**: Raw blockchain events are processed and partitioned by day. The `timestamp` field is truncated to day granularity to enable daily aggregations. All event metadata including `event_pallet`, `event_method`, `event_data` (JSON arrays), and `extrinsic_id` are preserved for downstream filtering and processing
- **Key fields**: `timestamp` (truncated to day), `event_pallet`, `event_method`, `event_data`, `extrinsic_id`, `success`

### Component B: Contract creation identification  
- **Purpose**: Identify when new contracts are deployed by parsing system pallet events
- **Logic**: Contract creations are identified by filtering events where `event_pallet` equals 'system' and `event_method` equals 'NewAccount'. Only events with a valid `extrinsic_id` are included, as this indicates the creation was part of a transaction. Contract addresses are extracted from the first element of the JSON `event_data` array and normalized to lowercase for consistency
- **Key fields**: `contract_address` (from `event_data[0]`), `extrinsic_id`, `timestamp`

### Component C: Deployer identification
- **Purpose**: Capture who deployed each contract by linking execution events
- **Logic**: Deployer information is gathered from ethereum pallet events where `event_pallet` equals 'ethereum' and `event_method` equals 'Executed'. The deployer address is extracted from the first element of the `event_data` array, while the EVM transaction hash comes from the third element. These events are linked to contract creations using the matching `extrinsic_id`
- **Key fields**: `signer_address` (deployer from `event_data[0]`), `evm_hash` (from `event_data[2]`)

### Final aggregation
- **Combining components**: Contract creation events are left joined with deployer events using `extrinsic_id` to create complete deployment records that include both contract address and deployer information
- **Time aggregation**: All deployment records are grouped by the day-truncated `timestamp` to produce daily counts
- **Final calculation**: The total number of unique contract deployments per day is calculated using a count aggregation. The `finalize_metric_contracts_deployed` macro applies standardization including metadata assignment (chain_id as 'neuroweb', market_sector as 'blockchains_l1') and gap-filling strategy that inserts zero values for days with no contract deployments to ensure complete time series data

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

Unique smart contracts published onchain.

NeuroWebNEURO

Archived

Contracts deployed

Contracts deployed

Competitive landscape

Chain breakdown