The control finding
Janus Henderson AAA CLO exposure, tokenised. Credit risk plus issuer control — not a cash equivalent despite the rating.
- Named controller
- Janus Henderson (fund manager) and Centrifuge (tokenization and transfer-agent function)
- Holder’s position
- The holder owns a tokenized claim on a fund holding AAA-rated CLO tranches, not on the loans underlying those CLOs. This is credit risk, not a cash equivalent, despite the AAA rating on the tranche.
- Redemption or exit
- Eligible investors redeem through Centrifuge and Janus Henderson's process under the fund's current terms. There is no permissionless exit and redemption timing can depend on underlying CLO market liquidity.
Dependencies an advisor should record
- Janus Henderson's fund governance and credit selection
- Centrifuge's tokenization and allowlist controls
- Underlying CLO tranche credit risk, separate from issuer risk
- Eligibility and jurisdiction restrictions
- USDC as the settlement rail
- The chain carrying the token
Why this distinction matters
JAAA must never be classified as a cash equivalent for a client's liquidity sleeve. The AAA rating describes tranche seniority within a CLO, not the absence of credit risk, and the tokenization adds issuer and transfer-agent control on top of that risk.
A named organization or administrator controls issuance, transfers, reserves, redemption, or address restrictions. That finding can coexist with a sound reserve, useful product, or appropriate client role. The grade prevents the on-chain wrapper from being mistaken for the absence of an administrator.
Questions before use
- Does the exact contract and chain match the instrument reviewed here?
- Which party can mint, burn, pause, upgrade, block, or redeem?
- Does the client have direct redemption access or only secondary liquidity?
- What protocol, bridge, wallet, and custodian dependencies are added?
- Which event would force review or exit?
Primary sources
Primary documents can change. This profile records the control interpretation reviewed on 2026-08-06; verify current terms before implementation.