pUSD, the Plume USD stablecoin recorded in this registry against a U.S. dollar (USD) reference asset, is listed for tokenization on Ethereum, but its issuer legal entity, backing, and structural terms cannot be sourced under the constraints applied to this generation call.

The registry classifies pUSD as a stablecoin referencing the U.S. dollar (USD) on a one-to-one basis according to the asset metadata. The reserve composition, reserve custodian or fund manager, attestation provider and cadence, fees borne by the holder, and the accrual or payout mechanism are not present in any citable dossier source and are therefore not asserted in this entry.

The issuer legal name, jurisdiction of formation, applicable regulator or license regime, the legal form of the tokenholder claim, eligibility and offering restrictions, the redemption right and any minimums, and the security interest or custodial arrangement protecting tokenholders cannot be stated. The sole permitted source domain returned HTTP 301 permanent redirects to a different registrable domain that is not authorized for this call, so no page resolved and served content that could be fetched and cited for these structural facts. No legal-structure claim is made in the absence of a citable issuer source.

The token standard, the full set of supported and natively issued versus bridged blockchain networks, the mint and burn mechanics, settlement timing, and any NAV or oracle publication mechanism cannot be sourced for this entry. The registry records listing on Ethereum, but no fetched issuer page supports specific technical claims, so none are asserted here.

<Sources
  retrievedAt="2026-06-24"
  items={[

  ]}
/>


# 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)

Stablecoins

website

twitter

discord

github

Blockchains (L1)

Plume Network

Plume USD (pUSD) is a U.S. dollar stablecoin issued by Plume Network.

Retail investors, professional investors, accredited investors, qualified investors, qualified purchasers, and institutions can mint and redeem directly with Plume Network in USDC, and holders have a contractual right to redeem at par.

pUSD has been issued on Ethereum as an ERC-20 token since December 2024.

Plume USDpUSD