Janus Henderson and Centrifuge have launched JQQQ, an issuer-sponsored blockchain-native fund that seeks exposure to the Nasdaq-100 Index through the Stellar network. The announcement, made on October 27, marks a test of whether asset managers can use blockchain infrastructure to serve qualified investors while maintaining traditional portfolio management and disclosure standards.
Fund Structure and Availability
JQQQ is structured as a British Virgin Islands segregated portfolio company with Anemoy Asset Management serving as investment manager and Janus Henderson Investors US as sub-investment manager. Janus Henderson manages the strategy while Centrifuge provides the infrastructure for public-blockchain issuance and fund operations.
The fund is available only to eligible investors where lawful and is not available to US persons. The Nasdaq-100 index is licensed from Nasdaq, making this an issuer-sponsored fund strategy rather than an unrelated synthetic token. Holdings do not grant shareholders direct rights in the underlying Nasdaq-100 securities.
Operational Considerations
Tokenization through blockchain does not eliminate investment risk, and future lending or collateral uses are not automatically provided by Janus Henderson. The fund may deviate from the reference index and may not trade as freely as an exchange-listed ETF.
For financial institutions using blockchain systems, technical integration represents only the beginning. They must also manage liability, account for funds, control access, and maintain auditable records of fund operations. Institutional adoption typically requires reconciliation processes, internal approvals, liquidity at conversion points, and reliable controls—elements that extend beyond onchain confirmation speed.
What Comes Next
Key indicators to monitor include actual subscription volume, approved distribution channels, custody arrangements, and whether onchain investors can redeem reliably during market stress. Adoption typically progresses from commercial agreement through limited implementation, onboarding, real transaction volume, and eventually routine usage rather than occurring at a single launch moment.
