aHYPER, issued by Hyperithm and tokenized by Accountable, is a tokenized active-strategy vault interest that provides holders economic exposure to a delta-neutral yield strategy managed by Hyperithm through Accountable's Vault-as-a-Service infrastructure [S1].

Each token represents proportional ownership of the vault's net asset value, expressed as vault shares whose price starts at 1.00 and appreciates as the delta-neutral strategy earns yield [S2]. Returns accrue into the share price rather than as separate distributions, with no rebasing [S2]. Because pricing follows DVN-attested NAV updates, the share price can increase or decrease, and principal is not guaranteed [S3]. Holders bear a performance fee charged on accrued yield, minted as shares [S1][S2].

The vault is operated by Hyperithm as economic issuer, while Accountable provides the tokenization and verification infrastructure and performs KYC and AML on the vault manager [S4][S5]. Holders receive vault shares representing proportional ownership, converted at the prevailing share price on withdrawal to return principal plus accrued yield [S2]. Access is configured per vault across permissionless, whitelisting, and KYC models, with eligible jurisdictions selectable and restricted territories blockable [S5]. Redemption follows an ERC-7540 asynchronous request-and-fulfill queue with FIFO ordering and fulfillment-time pricing [S1][S6]. No deposit insurance or loss-protection mechanism applies [S2].

Vault shares are ERC-4626 tokens extended with ERC-7540 for asynchronous deposit and redemption, issued natively on Monad among supported networks including Ethereum and Arbitrum [S1][S7]. Shares mint on deposit through the AccountableAsyncVault contract and redeem via the withdrawal queue at fulfillment-time NAV, with net asset value published and attested by a DVN publisher [S7][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/introduction.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 (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 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

Hyperithm Delta Neutral Vault (aHYPER) is a tokenized fund share issued by Accountable and managed by Hyperithm.

The fund is open-ended, invests in crypto assets, locks up subscriptions for 0 months, and charges a 0.5% annual management fee.

Retail investors, professional investors, accredited investors, qualified 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.

aHYPER has been issued on Monad as an ERC-4626 token since January 2026.

Hyperithm Delta Neutral VaultaHYPER