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

Frequency is a blockchain specialized for digital identity, data ownership and online presence powered by Polkadot Relay chain.

FRQCY holders own and govern the protocol.

website

github

twitter

discord

Blockchains (L2)

Frequency

# Frequency Token holders Methodology

## 1. Overview

The Token holders metric is used to measure the number of unique addresses holding a non-zero balance of the native asset on Frequency. This metric is utilized by investors to track the growth and distribution of the network's holder base over time. Through the monitoring of holder base expansion or contraction, the long-term adoption and decentralization of the network are evaluated.

## 2. Data sources

- **Blockchain events**: `NewAccount` and `KilledAccount` events, covering Frequency

## 3. Step-by-step calculation

### Component A: Account state change extraction

- **Purpose**: Identify the creation and termination of active accounts on the network
- **Logic**: `NewAccount` and `KilledAccount` events are extracted from the blockchain events database. A daily net change is calculated by assigning a value of `1` to each `NewAccount` event and a value of `-1` to each `KilledAccount` event, which are then summed for each day.
- **Key fields**: `block_timestamp` (timing), `event_method` (event type identification)

### Component B: Cumulative holder calculation

- **Purpose**: Determine the running total of unique addresses with a non-zero balance
- **Logic**: The daily net changes are aggregated chronologically to compute a running cumulative sum of active accounts. For days without recorded events, the last known cumulative value is carried forward to ensure a continuous daily time series. Only days with a cumulative holder count greater than zero are retained.
- **Key fields**: `timestamp` (daily boundary), `tokenholders` (cumulative count)

### Component C: Metric finalization

- **Purpose**: Standardize the schema and filter the final dataset
- **Logic**: The cumulative token holder counts are cast to standardized data types and grouped by day. The dataset is filtered to ensure only valid chain and project identifiers are included, and chain availability filters are applied to align the data with approved freshness limits.
- **Key fields**: `timestamp` (timing), `chain_id` (chain identification), `tokenholders` (final count)

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

Unique addresses holding a non-zero balance of the project's native token.

FrequencyFRQCY

Archived

Token holders

Token holders

Competitive landscape

Chain breakdown