# Asset senders (daily) methodology

## 1. Overview

Asset senders (daily) is calculated as the number of unique addresses that initiate asset transfers within a fixed 24-hour window. Daily activity is measured from 00:00 UTC to 23:59 UTC for each tracked asset. Active transactors are isolated from passive recipients by identifying only the sending addresses of transactions. This metric is utilized to evaluate the daily active user base and transaction utility of tokenized assets across multiple blockchain networks.

## 2. Data sources

- **EVM chain events**: ERC-20 `Transfer` events, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, and others)
- **Solana instructions**: Token transfer instructions, covering Solana
- **Aptos, Cardano, Stellar Classic, and Sui events**: Token withdraw events, covering Aptos, Cardano, Stellar, and Sui
- **Near, Algorand, Injective, Ripple, and Stellar Soroban events**: Token transfer events, covering Near, Algorand, Injective, Ripple, and Stellar
- **Polkadot Asset Hub events**: `Transferred` events from the `assets` pallet, covering Polkadot Asset Hub
- **Asset metadata**: Token addresses and chain configurations

## 3. Step-by-step calculation

### Component A: Extract sender addresses

- **Purpose**: Identify and extract the unique sending addresses for each asset transfer across all supported chains.
- **Logic**: On EVM-compatible chains, sending addresses are extracted from the `from` field of ERC-20 `Transfer` events, excluding the zero address to filter out mint transactions. On Solana, sending addresses are extracted from the authority address field of token transfer instructions. On Aptos, Cardano, Stellar Classic, and Sui, sending addresses are identified from the account address field of token withdraw events. On Near, Algorand, Injective, and Stellar Soroban, sending addresses are extracted from the sender address field of token transfer events, with null addresses excluded. On Ripple, sending addresses are extracted from token transfer events where the transfer value is negative. On Polkadot Asset Hub, sending addresses are extracted from the event data of `Transferred` events emitted by the `assets` pallet.
- **Key fields**: `timestamp` (block timestamp truncated to daily grain), `token_address` (the contract or asset identifier), `sender_address` (the address initiating the transfer)

### Component B: Consolidate and deduplicate sender data

- **Purpose**: Aggregate sender addresses across all chains and prepare the dataset for daily unique counting.
- **Logic**: Sender records from all individual chains are consolidated into a unified dataset. For each asset on each chain, the sending addresses are grouped by day. To prevent double-counting, duplicate sender addresses for the same asset on the same chain within the same 24-hour window are removed.
- **Key fields**: `timestamp` (daily timestamp), `chain_id` (blockchain identifier), `token_address` (asset address), `sender_address` (unique sending address)

### Component C: Final aggregation

- **Purpose**: Calculate the final daily active sender count per asset and per chain.
- **Logic**: The consolidated dataset is aggregated to compute the daily active senders. Unique sending addresses are counted for each asset on a daily basis, both at the individual chain level and aggregated across all chains for multi-chain assets. If no transfer activity is recorded for a tracked asset on a given day, the daily sender count is filled with zero values.
- **Key fields**: `timestamp` (daily timestamp), `chain_id` (blockchain identifier), `token_address` (asset address), `asset_dau` (daily active senders count)

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

Unique asset senders over a fixed 24-hour window.

Asset senders (daily)

Tokenized stocks

Tokens are deployed from factory contracts as 18-decimal ShareTokens on Arbitrum and whole-unit StockTokens on BSC, minted only against securities the protocol has acquired. Dividends are distributed to holders net of withholding tax rather than reinvested into the token. Offered only to non-U.S. persons under Regulation S after onboarding.

Stove Protocol issues tokenized stocks on Arbitrum One, HashKey Chain, Pharos and BSC covering companies and ETFs listed in the U.S., Hong Kong and Korea. Each token is a debt instrument that gives holders economic exposure to the underlying share, backed 1:1 by securities held with regulated brokers. Tokens carry no shareholder rights.

Stove Finance operates Stove Protocol, an onchain issuance and settlement protocol for tokenized equities. The legal entity behind the issuer is not publicly disclosed; the terms of service are governed by British Virgin Islands law.

website

docs

twitter

Real-world asset (RWA) issuers

Stove

SanDisk (Stove Tokenized Stock) (SNDKs) is a token tracking SNDK shares, backed by dedicated collateral.

The underlying security is listed in the information technology sector in North America.

Each token tracks one underlying share, entitles holders to dividends, which are distributed in cash, and carries no voting rights.

Professional investors, accredited investors, qualified investors, and institutions worldwide can mint and redeem directly with Stove after completing KYC.

Residents of Canada, China, the United States, and jurisdictions under applicable sanctions cannot mint or redeem with Stove.

SNDKs has been issued on public blockchains since July 2026 and is native to BNB Chain and Arbitrum One.

SanDisk (Stove Tokenized Stock)SNDKs