Validators process transactions and receive validator rewards (supply-side fees).

NEAR Protocol is a smart contract platform for decentralized applications (a blockchain). NEAR Protocol was founded by Alexander Skidanov & Ilya Polosukhin and launched in 2017.

NEAR holders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). NEAR Protocol's investors include a16z, Pantera Capital, Libertus, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

NEAR Protocol

# near Active Addresses Daily Methodology

## 1. Overview

Active Addresses Daily measures the number of unique addresses that initiate or participate in on-chain activity on Near. This metric accounts for standard transactions, meta transactions (delegated actions), and interactions within the Near Intents ecosystem. By tracking the daily volume of distinct interacting accounts, a comprehensive view of network adoption and user engagement is provided for both core protocol usage and specialized intent-based applications.

## 2. Data sources

- **Blockchain events**: Transaction data and `DELEGATE_ACTION` instructions from Near Protocol, plus `token_diff` and `transfer` events from Near Intents contracts on Near
- **External data**: Asset metadata for address and product identification

## 3. Step-by-step calculation

### Component A: Near Protocol core activity

- **Purpose**: To identify unique users performing standard and meta transactions on the Near network.
- **Logic**: Signer account IDs are extracted from all transaction data. For transactions involving `DELEGATE_ACTION` types, which represent meta transactions, the receiver account ID is captured to correctly identify the end-user initiating the action rather than the relayer. These addresses are categorized as either transaction senders or meta transaction senders.
- **Key fields**: `signer_account_id`, `receiver_account_id`, and `action_kind`.

### Component B: Near Intents activity

- **Purpose**: To capture unique users interacting specifically with Near Intents products.
- **Logic**: Execution logs from the Near Intents executor are parsed for specific event types. Account IDs are extracted from `token_diff` events to identify participants in intent-based swaps. Furthermore, `transfer` events are analyzed to capture both the account IDs and receiver IDs involved in the settlement of intents.
- **Key fields**: `account_id`, `receiver_id`, and `intent_hash`.

### Component C: Aggregation and deduplication

- **Purpose**: To provide a final daily count of distinct active addresses across the entire ecosystem.
- **Logic**: Addresses identified from both Near Protocol core activity and Near Intents activity are combined into a single dataset. Duplicate addresses are removed within each 24-hour UTC period to ensure each account is counted only once per day. The resulting values are aggregated by day and product.
- **Key fields**: `block_timestamp` and `user_address`.

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

Unique active addresses over a fixed 24-hour window.

NEAR ProtocolNEAR

Active addresses (daily)

Active addresses (daily)

Competitive landscape