SBC, issued by Stablecoin Inc., is a fiat-backed stablecoin that is presented as exchangeable 1:1 for one U.S. dollar (USD) and is natively issued across multiple blockchain networks for payments use by developers and businesses. [S1]

Each SBC tracks the U.S. dollar (USD) at a 1:1 peg and is described as always fully backed by fiat reserves maintained at that ratio. [S1] SBC is a price-stable payment instrument, not a return-bearing one, and the issuer discloses no yield, interest pass-through, NAV accrual, or rebasing. [S1] The Terms of Service state fees may apply to certain transactions or services and will be disclosed at the time of the transaction, with users bearing applicable taxes and regulatory fees. [S2]

The issuing entity is Stablecoin Inc., operating as Stablecoin.xyz, with a U.S. presence and a California governing-law provision in its Terms of Service. [S2][S3] The Terms characterize SBC as a digital asset pegged to a stable value and provide services as is, while the homepage frames SBC as redeemable 1:1 for USD with reserve management and third-party attestations supplied by partner Brale to support U.S.-regulated backing. [S1][S2] Users must be at least 18 or the legal age in their jurisdiction, hold legal capacity, and comply with applicable laws; SBC smart contracts comply with U.S. Sanctions and BSA requirements. [S1][S2]

SBC moves across blockchains without duplicating supply, using custom multi-party computation (MPC) infrastructure for signing, minting, and burning across chains. [S1] The developer documentation references the Radius network, Radius Testnet, and a Canton Network entry, and emphasizes ERC-4337 account abstraction. [S4] A SBC Token List of multi-chain addresses is referenced. [S4]

<Sources
  retrievedAt="2026-06-23"
  items={[
    { id: "S1", url: "https://stablecoin.xyz/" },
    { id: "S2", url: "https://stablecoin.xyz/legal/terms-of-service" },
    { id: "S3", url: "https://stablecoin.xyz/legal/privacy-policy" },
    { id: "S4", url: "https://docs.stablecoin.xyz/" },
  ]}
/>


# Asset senders (monthly) methodology

## 1. Overview

Asset senders (monthly) is defined as the number of unique addresses from which asset transfers are initiated over a rolling 30-day period. For each tracked asset, outgoing transfer transactions are analyzed across supported blockchains to identify the sending addresses. These addresses are deduplicated over a 30-day window to represent the monthly active sender base. This metric is utilized to evaluate user adoption, transactional activity, and the overall utility of tokenized assets.

## 2. Data sources

- **EVM chain events**: Token transfer events, covering EVM-compatible chains (Ethereum, Arbitrum, Base, Polygon, Optimism, and others)
- **Solana instructions**: Token transfer instructions
- **Aptos, Sui, Cardano, and Stellar Classic data**: Token withdraw transactions
- **Stellar Soroban, Algorand, Near, Injective, and Ripple data**: Token transfer transactions
- **Polkadot Asset Hub events**: `Transferred` events from `assets` pallets
- **Asset metadata**: Token contract addresses and decimal precision

## 3. Step-by-step calculation

### Component A: Extract daily asset senders

- **Purpose**: Identify unique addresses initiating transfers on a daily basis
- **Logic**: On EVM-compatible chains, token transfer events are parsed to extract the sender address from the transaction, excluding the zero address. On Solana, token transfer instructions are parsed to identify the authority address. On Aptos, Sui, Cardano, and Stellar Classic, token withdraw transactions are parsed to extract the account address. On Stellar Soroban, Algorand, Near, and Injective, token transfer transactions are parsed to extract the sender address, excluding null addresses. On Ripple, token transfer transactions with negative values are parsed to identify the sending account address. On Polkadot Asset Hub, `Transferred` events from `assets` pallets are parsed to extract the sender address. For all chains, the extracted addresses are grouped by day and token address to produce a daily record of unique senders.
- **Key fields**: `timestamp` (block day), `token_address` (asset identifier), `sender_address` (initiating address)

### Component B: Aggregate rolling monthly senders

- **Purpose**: Calculate the unique sender count over a rolling 30-day window
- **Logic**: A daily datespine is generated to establish a continuous timeline. For each day in the timeline, a 30-day lookback window is constructed, encompassing the current day and the preceding 29 days. Daily sender addresses collected within this window are aggregated and deduplicated. The total number of unique, deduplicated addresses is then counted for each asset on each day.
- **Key fields**: `timestamp` (calculation day), `token_address` (asset identifier), `asset_senders` (unique monthly sender count)

### Component C: Final aggregation and zero-filling

- **Purpose**: Combine data across chains and fill missing activity days
- **Logic**: The deduplicated monthly sender counts are aggregated at both the individual chain level and the global asset level. For days where no transfer activity is recorded for a tracked asset, the metric is filled with zero values to maintain a continuous time series.
- **Key fields**: `timestamp` (reporting day), `chain_id` (blockchain identifier), `token_address` (asset identifier), `asset_senders` (final monthly unique sender count)

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

Unique asset senders over a rolling 30-day window.

Asset senders (monthly)

Stablecoins

website

twitter

github

etherscan

docs

Stablecoin issuers

Stable Coin

Stable Coin (SBC) is a U.S. dollar stablecoin issued by Stable Coin through Brale Inc.

Institutions can mint and redeem directly with Stable Coin.

SBC has been issued on public blockchains since August 2022 and is native to 8 networks, including Avalanche, Ethereum, Polygon, Stellar, Base, and OP Mainnet, with a bridged version on one more network.

Stable CoinSBC