YZM, issued by Yuzu Money and tokenized by Accountable, is a tokenized active-strategy vault interest whose shares represent proportional ownership of the vault's net asset value and rise in price as the underlying yield strategy earns returns [S1][S2].

Each YZM share tracks the Yuzu Money Vault yield strategy, whose deposited assets are deployed to external yield sources and returned when liquidity is needed [S3]. Returns accrue into the share price rather than as separate distributions, with no rebasing; share price starts at 1.00 and rises as yield is earned, and withdrawal returns principal plus accrued yield together [S2][S3]. Holders bear a performance fee on accrued yield above a high-water mark, plus any configured management, establishment, or prepayment fees, all minted as shares [S1][S2].

Holders receive vault shares representing proportional ownership of the vault [S2]. Backing is verified through Accountable's Data Verification Network attestations rather than held by Accountable, with total assets computed as vault assets plus deployed assets plus accrued penalties [S3][S4]. Access is configurable per vault across permissionless, whitelisting, and KYC models, the latter implemented as gasless EIP-712 signature verification, and vaults can select eligible jurisdictions and block restricted territories [S5][S2]. Redemption uses the withdrawal queue with FIFO ordering, fulfillment-time pricing, and a maximum wait of cycle end plus seven days [S6][S2]. There is no deposit insurance and principal is not guaranteed [S2][S3].

Vault shares are ERC-4626 tokens extended with ERC-7540 for asynchronous deposit and redemption, issued natively on Monad among supported networks including Ethereum, Arbitrum, and Citrea [S7][S1][S2]. Shares are minted on deposit through the vault contract and redeemed via the request-and-fulfill queue at fulfillment-time NAV, published and attested by a DVN publisher [S7][S1][S3].

<Sources
  retrievedAt="2026-07-06"
  items={[
    { id: "S1", url: "https://docs.accountable.capital/accountable-documentation/vault-as-a-service.md" },
    { id: "S2", url: "https://docs.accountable.capital/accountable-documentation/yieldapp/yieldapp-faqs.md" },
    { id: "S3", url: "https://docs.accountable.capital/accountable-documentation/vault-as-a-service/accountable-nav.md" },
    { id: "S4", url: "https://docs.accountable.capital/accountable-documentation/yieldapp.md" },
    { id: "S5", url: "https://docs.accountable.capital/accountable-documentation/vault-as-a-service/getting-started/quickstart/whitelisting-and-kyc.md" },
    { id: "S6", url: "https://docs.accountable.capital/accountable-documentation/vault-as-a-service/accountable-withdrawal-queue.md" },
    { id: "S7", url: "https://docs.accountable.capital/accountable-documentation/vault-as-a-service/architecture-overview.md" },
  ]}
/>


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

Counterparties use the platform to demonstrate assets and liabilities privately, enabling real-time financial verification across traditional and crypto-native markets

Accountable is the new standard for real-time financial verification that allows institutions to prove assets and liabilities privately. Built for both traditional and crypto-native markets, the platform enables counterparties to demonstrate financial health without exposing sensitive details like API keys, wallet addresses or trading strategies.

Institutions and counterparties seeking to prove financial health without exposing sensitive details such as API keys, wallet addresses, or trading strategies

website

twitter

discord

telegram

Lending

Accountable

Yuzu Money Vault (YZM) is a tokenized fund share issued by Accountable.

Each token is a direct claim on the issuer.

The fund is open-ended, invests in private credit, and locks up subscriptions for 0 months.

Professional investors, accredited investors, qualified purchasers, and institutions can subscribe and redeem in USDC, with a USDC 1,000 minimum, and holders have a right to redeem at net asset value.

YZM has been issued on Monad as an ERC-4626 token since December 2025.

Yuzu Money VaultYZM