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 User Wau Methodology

## 1. Overview

Active users (weekly) is used to quantify the number of unique addresses that interact with the Near blockchain. This metric encompasses both core network activities and specialized intent-based operations performed through Near Intents. The count of unique participants is utilized to evaluate the growth, adoption, and weekly engagement levels across the Near Protocol ecosystem. This metric represents activity over a 7-day rolling window.

## 2. Data sources

- **Blockchain events**: `token_diff` and `transfer` events from `intents.near` contracts, alongside native transaction records, covering Near

## 3. Step-by-step calculation

### Component A: Near Protocol active user identification

- **Purpose**: Identify unique addresses participating in core blockchain transactions
- **Logic**: Transaction records are parsed to identify the primary participants. For standard transactions, the signer account is identified as the active user. For meta transactions involving `DELEGATE_ACTION` types, the receiver account is extracted as the active user address to correctly attribute activity in delegated execution scenarios.
- **Key fields**: `signer_account_id`, `receiver_account_id`, `action_kind`

### Component B: Near Intents active user identification

- **Purpose**: Capture participants specifically utilizing the Near Intents product for swaps and transfers
- **Logic**: `token_diff` events from `intents.near` contracts are parsed to extract the account IDs associated with intent-based swaps. Additionally, `transfer` events from `intents.near` are analyzed. These transfers are filtered to include only those associated with swap receipt IDs. From these filtered logs, both the account ID and receiver ID are captured as active user addresses.
- **Key fields**: `account_id`, `receiver_id`, `receipt_id`, `event`

### Component C: Weekly aggregation

- **Purpose**: Generate a final weekly count of unique addresses across all monitored products
- **Logic**: User addresses identified from both Near Protocol and Near Intents are combined into a single dataset. A deduplication process is performed to ensure each address is counted only once per 7-day window, regardless of the number of interactions or products used. Timestamps are truncated to 7-day rolling windows to produce the final weekly active user values.
- **Key fields**: `block_timestamp`, `user_address`, `product_id`

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

Unique revenue-generating users over a rolling 7-day window.

NEAR ProtocolNEAR

Active users (weekly)

Active users (weekly)

Competitive landscape