sSNDK, issued by Stablestocks Lab Limited, is a tokenized stock that gives onchain exposure to SanDisk Corp, a U.S.-listed instrument, with each token backed 1:1 by one underlying share held in custody with licensed brokers. [S1][S2]

sSNDK tracks the live market price of SanDisk Corp (SNDK), and if the underlying issues a dividend or distribution and eligibility requirements are met, those economic rights pass through to the tokenholder, though voting rights remain with custodian holders. [S1][S2] Tokenholders may stake into StableVault to receive yield-bearing stStocks combining dividends with DeFi yields. [S3] A Service Fee of 0.1% of the transaction amount applies, alongside upstream broker and trading fees. [S4]

Stablestocks Lab Limited, brand StableStock, is incorporated in the British Virgin Islands and operates from Singapore. [S2][S5] It does not hold financial-services licenses and disclaims being a regulated entity, relying on broker-dealer partners holding an AFSL, a Hong Kong SFC Type 1 license, and U.S. MSB registration. [S5][S2][S6] An sToken is the tokenized representation of a real share; tokens are unregistered under the U.S. Securities Act and offered only to Qualified Investors through affiliated entities. [S5][S1] U.S. persons are barred and KYC and AML verification applies for leverage and IPO access. [S5][S4] Tokenholders may redeem and burn tokens at any time to retrieve the underlying share. [S1][S2]

sTokens are issued natively onchain on Bsc through a liquidity partnership with Native. [S1][S7] Tokens are minted when brokerage-held shares are deposited 1:1 and burned on redemption, with mint, burn, buy, and sell records recorded permanently onchain. [S1][S8] Stablecoin settlement in USDT and USDC funds purchases of real securities, and reserve coverage is published per asset and verified by weekly assurance reports. [S9][S8]

<Sources
  retrievedAt="2026-06-18"
  items={[
    { id: "S1", url: "https://stablestock.gitbook.io/ss/concepts/stokens" },
    { id: "S2", url: "https://stablestock.gitbook.io/ss/llms-full.txt" },
    { id: "S3", url: "https://stablestock.gitbook.io/ss/concepts/stablevault.md" },
    { id: "S4", url: "https://stablestock.gitbook.io/ss/concepts/spot/fee.md" },
    { id: "S5", url: "https://stablestock.gitbook.io/ss/legal/terms_of_use.md" },
    { id: "S6", url: "https://stablestock.gitbook.io/ss/introduction/trust-and-security.md" },
    { id: "S7", url: "https://stablestock.gitbook.io/ss/concepts/stokens.md" },
    { id: "S8", url: "https://stablestock.gitbook.io/ss/concepts/transparency" },
    { id: "S9", url: "https://stablestock.gitbook.io/ss/solution/our-model.md" },
  ]}
/>


# Asset senders (weekly) methodology

## 1. Overview

`Asset senders (weekly)` is defined as the number of unique addresses that initiate asset transfers over a rolling 7-day period. For each tracked asset, outgoing transactions are analyzed to identify the addresses responsible for moving tokens. This metric is utilized as a key indicator of weekly user activity and transactional engagement for tokenized assets across various blockchain networks. By aggregating unique sending addresses within a moving 7-day window, short-term fluctuations are smoothed out to provide a clearer view of active adoption.

## 2. Data sources

- **EVM chain events**: ERC-20 token transfers, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, and others)
- **Solana instructions**: Token transfer instructions
- **Other blockchain data**: Token transfer and withdrawal events from Aptos, Near, Polkadot Asset Hub, Stellar, Sui, Ripple, and others
- **Asset metadata**: Token contract addresses and asset mapping datasets

## 3. Step-by-step calculation

### Component A: Extraction of daily sending addresses

- **Purpose**: Identify and extract unique addresses initiating token transfers on a daily basis for each asset.
- **Logic**: On EVM-compatible chains, sending addresses are extracted from ERC-20 token transfers where the sender address is not the null address. On Solana, sending addresses are identified from token transfer instructions using the authority address. On Aptos, Sui, Cardano, and Stellar Classic, sending addresses are retrieved from token withdrawal events. On Stellar Soroban, transfers are parsed from Soroban token transfer events, excluding mint transactions where the sender address is null. On Polkadot Asset Hub, `Transferred` events from the `assets` pallet are parsed to identify the sender. On Ripple, outgoing transfers are identified where the transaction value is negative. On Near and Injective, sending addresses are extracted from token transfer events where the sender address is populated.
- **Key fields**: `timestamp` (block time truncated to the day), `token_address` (the contract or asset identifier), `sender_address` (the address initiating the transfer)

### Component B: Rolling 7-day window aggregation

- **Purpose**: Aggregate daily active senders into a rolling 7-day window to calculate weekly activity.
- **Logic**: A daily datespine is generated to establish a continuous timeline. For each day in the timeline, a rolling 7-day window is constructed by looking back at the preceding six days. Daily unique sending addresses are mapped to each active window based on their transaction timestamps.
- **Key fields**: `timestamp` (the reference day for the rolling window), `token_address` (the asset identifier), `sender_address` (the address active within the window)

### Component C: Final deduplication and aggregation

- **Purpose**: Calculate the final weekly unique sender count per asset and chain.
- **Logic**: Within each rolling 7-day window, sending addresses are deduplicated to ensure each unique address is counted only once per asset, regardless of transaction frequency. The deduplicated counts are aggregated at both the individual chain level and the global asset level. Missing dates are filled with zero values to maintain a continuous time series.
- **Key fields**: `timestamp` (the reference day), `chain_id` (the blockchain identifier), `token_address` (the asset contract address), `asset_senders_weekly` (the count of unique weekly sending addresses)

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

Unique asset senders over a rolling 7-day window.

Asset senders (weekly)

Tokenized stocks

StableStock earns revenue from transaction fees on sStock issuance and redemption via its StableBroker product, and from the spread between deposit/withdrawal flows. Distribution is direct-to-retail (StableBroker app) and B2B via wallet/exchange integrations on BNB Chain.

StableStock issues sStock tokens — ERC-20 tokens on BNB Chain backed 1:1 by the underlying U.S. equity or ETF held at a licensed custodian. The product catalog spans 500+ tokenized stocks and ETFs (e.g. sAAPL, sNVDA, sTSLA, sQQQ) including newly-IPO'd names like sCRCL (Circle) and sBLSH (Bullish) and leveraged/inverse exposures. All sStocks are deployed as BeaconProxy contracts from a single upgradeable factory.

StableStock is an onchain stock asset platform that lets users buy and trade U.S. stocks and ETFs using stablecoins. StableStock is the issuer of sStock tokens — tokenized representations of equities — and is backed by YZi Labs (formerly Binance Labs) among others.

website

twitter

documentation

Real-world asset (RWA) issuers

StableStock

StableStock SanDisk Corp (sSNDK) is a token tracking SNDK shares, backed by dedicated collateral with HabitTrade as broker.

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

Each token tracks one underlying share, entitles holders to dividends, and carries no voting rights.

Residents of the United States and Hong Kong cannot mint or redeem with StableStock.

sSNDK has been issued on BNB Chain as an ERC-20 token since February 2026.

StableStock SanDisk CorpsSNDK