twitter

discord

website

Blockchains (L1)

Movement

# Movement Token holders Methodology

## 1. Overview

The Movement tokenholders metric measures the number of unique addresses holding Movement's native APT token at daily intervals. This metric provides insight into the distribution and adoption of Movement's native token by counting distinct wallet addresses that maintain non-zero balances. The calculation aggregates tokenholder data from Movement blockchain state and applies Token Terminal's standardized metric formatting.

## 2. Data sources

The metric relies on several key data sources:

- **Movement blockchain state data**: Account balance snapshots and state information from the Movement blockchain to identify addresses with token holdings
- **Movement transaction logs**: Blockchain transaction records that show token transfers and balance changes over time  
- **Native token metadata**: Information about Movement's native APT token including decimal precision and token contract details
- **Chain availability data**: Information about Movement network status and data availability periods

## 3. Step-by-step calculation

### Component A: Native tokenholder aggregation
- **Purpose**: Identifies and counts unique addresses holding Movement's native APT token
- **Logic**: The upstream `movement_native_tokenholders` model processes Movement blockchain data to determine unique addresses with non-zero native token balances. This involves analyzing account states or balance snapshots to identify all addresses holding the native APT token above zero amounts. The data is aggregated at daily intervals using the `timestamp` and `timestamp_grain` fields to provide time-series tokenholder counts.
- **Key fields**: The `tokenholders` field contains the count of unique addresses, `chain` identifies the Movement network, and `timestamp` provides daily granularity for the measurement

### Component B: Data standardization and type conversion  
- **Purpose**: Converts and standardizes the tokenholder data for consistent processing
- **Logic**: The raw tokenholder counts are cast to `bignumeric` data type to ensure numerical precision in downstream calculations. The `chain` field is mapped to `chain_id` to align with Token Terminal's standard field naming conventions. Timestamp fields are preserved to maintain daily granularity.
- **Key fields**: `tokenholders` is converted to `bignumeric` type, `chain_id` replaces the original `chain` field, and `timestamp_grain` maintains the daily aggregation level

### Component C: Incremental processing
- **Purpose**: Efficiently processes only recent data changes while maintaining historical accuracy
- **Logic**: When running incrementally, the model applies date filtering to process only recent data based on the maximum existing partition date. The logic includes a lookback period defined by `incremental_lookback_days` to ensure data completeness and handle any late-arriving or updated tokenholder information from the Movement blockchain.
- **Key fields**: Uses `timestamp` field for date-based filtering and partition management

### Final aggregation
- **Combining components**: The processed tokenholder data flows through the `finalize_metric_tokenholders` macro which applies Token Terminal's standardized metric formatting
- **Metric finalization**: The finalization macro adds standard metadata fields including `project_id`, `data_id` (set to 'movement'), `metric_id`, and other Token Terminal schema requirements. This ensures consistency across all tokenholder metrics in the platform
- **Chain availability filtering**: A final filter excludes any data from periods when the Movement chain was not available or supported, using the `chain_id` field to apply appropriate availability rules
- **Final calculation**: The final metric represents the daily count of unique addresses holding Movement's native APT token, expressed as a precise numerical value with standardized metadata for time-series analysis and cross-protocol comparisons

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

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

MovementMOVE

Archived

Token holders

Token holders

Competitive landscape