JAAA, issued by a fund managed by Anemoy and tokenized by Centrifuge Network Foundation, is tokenized fund interest representing a claim on the Janus Henderson Anemoy AAA CLO Fund, with Janus Henderson acting as sub-investment manager [S1][S2][S3].

Each token represents an interest in the underlying fund, which holds AAA-rated collateralized loan obligation tranches, and tracks the fund's net asset value (NAV) so balances reflect the underlying strategy's economic exposure [S4][S2]. The token is yield-bearing, with deRWA wrapper tokens such as deJAAA letting holders earn the stable yields of the underlying assets while remaining tradable and composable onchain [S5][S6]. Special purpose vehicles supplying services do so for a service fee [S7].

Holders receive ERC-20 share tokens issued from a share class within a vault, representing an interest in a regulated fund structured by Centrifuge's asset-management arm Anemoy [S4][S2]. Centrifuge Network Foundation, the protocol operator, is registered in the Cayman Islands, and its terms state that neither Centrifuge nor any affiliated entity is licensed in the holder's jurisdiction [S8][S9]. Access may be restricted to sophisticated, accredited or qualified investors and requires KYC and AML onboarding, with permissioning rules controlling who may hold or redeem [S7][S9]. Vaults support asynchronous, request-based redemption suited to delayed fulfillment, with requests processed on the hub chain [S4][S10].

Share tokens follow the ERC-20 standard with ERC-1404 permissioning and ERC-4626 and ERC-7540 vaults [S4][S10]. The protocol is deployed across Ethereum, Base, Arbitrum, Avalanche, Plume, BNB Smart Chain, Optimism, HyperEVM, Monad and Pharos [S11]. Cross-chain movement uses a burn-and-mint mechanism for 1:1 transfers, and NAV and price-oracle updates are computed on the hub chain and distributed to all networks [S10].

<Sources
  retrievedAt="2026-06-19"
  items={[
    { id: "S1", url: "https://centrifuge.io/" },
    { id: "S2", url: "https://centrifuge.io/blog/janus-henderson-anemoy-rating" },
    { id: "S3", url: "https://centrifuge.io/blog/centrifuge-launches-spxa" },
    { id: "S4", url: "https://docs.centrifuge.io/user/concepts/tokenization/" },
    { id: "S5", url: "https://centrifuge.io/derwa-tokens" },
    { id: "S6", url: "https://centrifuge.io/blog/centrifuge-derwa-tokens" },
    { id: "S7", url: "https://docs.centrifuge.io/user/issuer/" },
    { id: "S8", url: "https://centrifuge.io/imprint" },
    { id: "S9", url: "https://centrifuge.io/terms" },
    { id: "S10", url: "https://docs.centrifuge.io/developer/protocol/overview/" },
    { id: "S11", url: "https://docs.centrifuge.io/developer/protocol/deployments/" },
  ]}
/>


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

Tokenized funds

Anemoy earns management fees on assets under management. Its funds are tokenized and issued onchain via Centrifuge.

Anemoy manages tokenized, fully onchain funds covering AAA CLOs, US Treasuries, S&P 500 exposure and private credit. Janus Henderson Investors acts as sub-investment manager to the CLO, Treasury and S&P 500 funds; Apollo to the diversified credit fund.

Anemoy Asset Management Limited is a privately held, BVI-regulated fund manager. Its funds are issued through Anemoy Capital SPC Limited.

website

twitter

Real-world asset (RWA) issuers

Anemoy

Janus Henderson Anemoy AAA CLO Fund (JAAA) is a tokenized fund share issued by Centrifuge through Anemoy Capital SPC Limited and managed by Anemoy Asset Management Limited with Janus Henderson Investors as sub-advisor.

Each token is a direct claim on the issuer.

The fund is open-ended, invests in corporate credit, and charges a 0.5% annual management fee.

Its assets sit with J.P. Morgan, administered by Trident Trust Cayman, with MHA Cayman as auditor.

Professional investors can subscribe and redeem in USDC, with a USDC 1 minimum and same- or next-business-day subscription settlement, and holders have a right to redeem at net asset value with same- or next-business-day settlement.

Anemoy Capital SPC Limited is incorporated in the British Virgin Islands, is regulated under the British Virgin Islands securities regime, and is supervised by the BVI Financial Services Commission.

JAAA has been issued on public blockchains since May 2025 and is native to 7 networks, including Ethereum, Base, Avalanche, Solana, BNB Chain, and Arbitrum One.

Janus Henderson Anemoy AAA CLO FundJAAA