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 Contract deployers Methodology

## 1. Overview

Contract deployers measures the daily count of unique addresses that deployed smart contracts on the NeuroWeb blockchain. Developer activity and ecosystem growth are tracked by identifying how many distinct entities are publishing code onchain each day. Contract deployments are identified through specific blockchain events and linked to their initiating addresses.

## 2. Data sources

- **Blockchain events**: `NewAccount` events from `system` pallets and `Executed` events from `ethereum` pallets, including extrinsic metadata and execution status, covering NeuroWeb

## 3. Step-by-step calculation

### Component A: Event data extraction

- **Purpose**: Extract and process raw blockchain events from NeuroWeb
- **Logic**: Blockchain events are retrieved with daily timestamp truncation. Events are filtered to include block metadata, event details, and success status. Data is incrementally processed with a lookback period to ensure completeness.
- **Key fields**: `timestamp` (daily truncated), `event_data`, `event_method`, `event_pallet`, `extrinsic_id`, `success`

### Component B: Contract creation identification

- **Purpose**: Identify when new contracts are deployed on the blockchain
- **Logic**: Events are filtered for the `system` pallet and `NewAccount` method, which indicates the creation of new blockchain addresses, including smart contracts. The contract address is extracted from the first element of the `event_data` JSON array. Case normalization is applied to ensure address consistency.
- **Key fields**: `contract_address` (from `event_data[0]`), `extrinsic_id`, `timestamp`

### Component C: Deployer identification

- **Purpose**: Identify which addresses deployed the contracts
- **Logic**: Events are filtered for the `ethereum` pallet and `Executed` method, which captures transaction execution details. The signer address is extracted from the first element of the `event_data` JSON array. This represents the address that initiated the contract deployment transaction.
- **Key fields**: `signer_address` (from `event_data[0]`), `evm_hash` (from `event_data[2]`), `extrinsic_id`

### Component D: Contract-deployer linking

- **Purpose**: Associate each deployed contract with its deploying address
- **Logic**: Contract creation events are joined with deployer events using `extrinsic_id` as the linking key. A left join is used to preserve contract creations even when deployer information might be missing. A complete record of contract deployments is created with associated deployer addresses.
- **Key fields**: `contract_address`, `deployer_address`, `extrinsic_id`, `timestamp`

### Component E: Final aggregation

- **Purpose**: Generate daily counts of unique deploying entities
- **Logic**: Results are grouped by daily timestamps. Distinct deployer addresses are counted per day to handle cases where a single address deploys multiple contracts. A zero-filling strategy is applied for days without activity to maintain a continuous time series. The daily contract deployers metric is calculated as the count of unique `deployer_address` values per day.

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

Unique addresses that deployed at least one smart contract.

NeuroWebNEURO

Archived

Contract deployers

Contract deployers

Competitive landscape

Chain breakdown