On February 26, 2026, Bloomberg and Kaiko announced a joint initiative to bring Bloomberg’s Data License on-chain via Kaiko’s infrastructure on Canton Network, initially focused on tokenised US Treasuries and repo workflows.

The announcement received coverage in specialist trade publications — Finadium, A-Team Insight, Securities Finance Times. What it didn’t receive — as far as I can tell — was analysis that applies capital markets thinking to what the move actually means structurally.

That’s what this report is for.

A note on scope before going further: the Bloomberg/Kaiko initiative is still in early stages — described as “a pathway” with controlled access for entitled participants on Canton Network. It is not yet in full production. But the direction is clear, and in institutional data infrastructure, direction matters as much as current state.

The problem nobody solved cleanly

When I analyzed Ondo Finance for the previous Realyld report, I needed to pull data from four separate sources to build a complete institutional picture of their flagship tokenized Treasury product.

rwa.xyz for behavioral metrics — active addresses, fund flows, holder counts. Etherscan for holder concentration and wallet identity. DefiLlama for revenue and fees. Ondo’s own documentation for legal structure, custody arrangements, and access restrictions.

Four sources. Four different formats. None of them integrated.

For a traditional bond, one Bloomberg function covers all of this. You type in an ISIN and your terminal resolves it into price, yield, duration, credit rating, NAV, custody information, and liquidity profile — simultaneously, inside every institutional workflow that needs it.

For tokenized assets in 2026, that identifier layer doesn’t exist. The data exists across multiple providers. The infrastructure that connects it into something an institutional portfolio manager can actually use does not.

This is the problem everyone in the tokenized asset space has been trying to solve. And it turns out Bloomberg was watching.

Seven layers, six fragmented

Before explaining what Bloomberg did, it helps to understand the infrastructure that was being built around them.

The tokenized asset data stack has assembled itself in layers over the last three years:

Oracles deliver off-chain data on-chain. Chainlink remains the clear leader with the majority of Total Value Secured and the broadest institutional integration count — according to 2025 and early 2026 estimates, approximately 70% of TVS, though figures vary by measurement methodology. Chronicle has gained significant traction — and in March 2026 was selected by BlackRock’s BUIDL fund for Proof of Asset verification, providing real-time independently verified attestations of holdings, valuation, and custody. RedStone, one of the fastest-growing providers, acquired Security Token Market’s dataset of 800+ tokenized assets and built the Trusted Single Source Oracle specifically for regulated fund NAV data.

Analytics platforms track on-chain behavior. rwa.xyz is the industry standard for behavioral metrics — active addresses, fund flows, holder counts. Dune Analytics handles custom SQL queries and holder concentration. DefiLlama and Token Terminal cover revenue and fees. Messari provides structured sector classification.

Attestation and verification sits between off-chain fund operations and on-chain representation. Ankura Trust provides daily NAV attestations for OUSG. Chainlink’s Proof of Reserve automates cryptographic verification of off-chain collateral across multiple funds.

Risk intelligence is emerging. Credora scores on-chain credit risk. Gauntlet models parameter risk for lending protocols.

Custody is more mature. BitGo, Hex Trust, Coinbase Custody, Fireblocks, and Copper all serve institutional clients with varying geographic and regulatory footprints.

Token standards embed compliance at the protocol layer. ERC-3643, known as T-REX, now covers over $32 billion in tokenized assets across more than 200 deployments.

Six layers. Each one solving one piece of the problem.

The seventh layer — the integration and identifier layer that connects all six into something an institutional PM can query from their existing workflow — does not exist yet.

That missing piece is also structural: there is no common identifier standard for tokenized assets. Bloomberg’s BBGID resolves traditional instruments across every institutional system simultaneously. For tokenized assets, no equivalent exists. Efforts are underway — DTCC, ISDA, and BIS Innovation Hub have each signaled interest in identifier standardization — but nothing is live at scale. Until that layer exists, even a fully deployed Bloomberg on-chain data license solves only part of the fragmentation problem.

This is the environment Bloomberg walked into — and the gap they are beginning to address.

What Bloomberg actually did

Bloomberg is not building a new terminal for tokenized assets. They are not learning Solidity. They are not integrating with Chainlink.

They made their existing data — security master data, evaluated pricing, reference data — available in a new environment. Kaiko built the data on-ramp. Canton Network is the delivery vehicle: a permissioned, institutional-grade blockchain with participation from Goldman Sachs, BlackRock, Nasdaq, S&P Global, and Citadel Securities among others — through a mix of funding, partnerships, and network membership rather than a single unified ownership structure.

The licensing model is unchanged. The entitlement controls are unchanged. The IP ownership is unchanged. The only thing that changed is where the data can be accessed.

As Emilie Gallagher, Bloomberg’s Global Head of Commodities and FX, said in the announcement: “Institutional clients increasingly expect the same trusted Bloomberg data they utilize in traditional markets to be available on-chain.”

Notice the framing. Not “we’re building something new for blockchain.” Not “we’re disrupting the tokenized asset data space.” The expectation is that Bloomberg data will be available everywhere institutional clients operate. On-chain is just another environment.

This is an extension story, not a disruption story.

Why this matters more than it appears

Three reasons the Bloomberg/Kaiko announcement is more significant than its coverage suggested.

Data trust is not transferable. Institutional portfolio managers trust Bloomberg evaluated pricing because it has been accurate, consistent, and legally defensible for more than four decades. No crypto-native data provider has that track record. When a risk officer needs to defend a valuation in front of a compliance team, they cite Bloomberg — not because alternatives are wrong, but because they haven’t been through enough stress cycles for institutional risk frameworks to accept them as authoritative.

This trust advantage will likely require hybrid validation processes in practice: Bloomberg reference data reconciled against on-chain attestations rather than replacing them. The extension to tokenized assets is directionally clear, but not yet seamless.

The argument here is that the licensing model is the moat, not the data. Much of Bloomberg’s underlying data is aggregated from exchanges, custodians, and issuers — the differentiation lies in the entitlement and verification layer built on top: auditable, licensed, legally defensible, with clear chain of custody from source to delivery. The Kaiko partnership extends that framework on-chain without changing it.

The institutional data problem stated precisely: it’s not “who has the data.” It’s “whose data can I cite in a regulatory filing, a compliance review, or a fund administrator’s report.” Bloomberg’s answer to that question is now available on-chain.

The incumbent wins by doing less — but not nothing. To compete in the tokenized asset data space, a crypto-native provider needs to build credibility from scratch, establish regulatory relationships, prove data accuracy through multiple market cycles, and sell into institutional procurement processes that can take eighteen months. Bloomberg still needs to complete integration work, establish entitlement controls on-chain, and prove client adoption at scale — Kaiko’s on-ramp, launched in August 2025, handles the technical heavy lifting on their behalf. But the commercial and credibility asymmetry is large. Bloomberg enters with its existing institutional footprint. Most crypto-native providers are still in early innings of building comparable credibility.

What Bloomberg does not solve

The Bloomberg/Kaiko initiative is real. It is also limited — at least in its current form.

Bloomberg is providing reference data and evaluated pricing. They are not providing on-chain behavioral analytics. Active address retention, fund flow patterns, holder concentration, and the behavioral signals that distinguish structural adoption from speculative interest — none of this comes from Bloomberg. That layer belongs to rwa.xyz, Dune Analytics, and the on-chain data providers who built their infrastructure directly on public blockchain data.

Bloomberg also cannot provide the common identifier layer. There is no ISIN equivalent for tokenized assets. No Bloomberg BBGID resolves into on-chain behavioral data alongside off-chain reference data. DTCC, ISDA, and BIS Innovation Hub have signaled interest in building this standard — but nothing operates at institutional scale yet. The integration problem — the one that made my Ondo analysis require four separate sources — is not solved by Bloomberg’s on-chain data license, even once it reaches full production.

What Bloomberg solves is the reference data layer for institutional workflows that already have Bloomberg terminals. That’s an important layer. It is not the complete picture.

Three futures

So where does this leave the tokenized asset data infrastructure race?

Three plausible outcomes, and they are not mutually exclusive.

The modular stack persists. Bloomberg for reference data and evaluated pricing. rwa.xyz and Dune for behavioral analytics. RedStone or Chronicle for NAV attestations. Credora for credit risk. Institutions assemble their own stack via APIs, increasingly assisted by AI agents that can query all layers simultaneously. Cost: near zero for on-chain layers, Bloomberg license for off-chain. Downside: requires data engineering capability that most asset managers don’t have internally.

An open identifier standard emerges. Not a company. A protocol. A working group agrees on a common identifier for tokenized assets — the ISIN equivalent — and an open API standard that allows all seven layers to resolve through a single query. Bloomberg wins the reference data layer. rwa.xyz wins behavioral analytics. RedStone wins NAV attestation. They all interoperate through a shared identifier. In my view, this would be the most beneficial outcome for the industry — and paradoxically, the one with the least commercial incentive for any single player to drive.

Bloomberg completes the move. Bloomberg extends from reference data into full tokenized asset coverage — adding behavioral feeds, integrating NAV attestations, building the identifier layer themselves. Institutional adoption is immediate because every asset manager already has a Bloomberg terminal. I’d assign this the highest probability for Segment A institutional clients over a three to five year horizon — and it’s the scenario that should concern every crypto-native data provider most.

What I’ll watch next

Bloomberg/Kaiko expansion beyond Canton Network. The February announcement specified tokenized US Treasuries and repo workflows on Canton Network as the initial focus. The initiative is designed to expand to additional asset classes and communities. The timeline and scope of that expansion will determine how much of the seven-layer stack Bloomberg eventually covers.

The common identifier question. Does any working group — DTCC, ISDA, BIS Innovation Hub, or a crypto-native consortium — move toward a standard tokenized asset identifier in 2026? This is the layer that would make the modular stack genuinely institutional-grade without requiring Bloomberg to build everything.

RedStone and Chronicle. The fastest-growing oracle providers are both serving BlackRock BUIDL — for different functions. As the tokenized asset market matures, the question of which provider wins the NAV attestation layer at scale will determine who occupies the most defensible position in the six crypto-native layers.

rwa.xyz‘s institutional ambitions. The behavioral analytics layer is currently the clearest gap in Bloomberg’s on-chain offering. If rwa.xyz builds institutional-grade API access and establishes data quality standards that compliance teams can cite in regulatory filings, they occupy the one layer Bloomberg cannot easily replicate.

Realyld publishes analysis of tokenized assets and blockchain-based capital markets infrastructure through a traditional finance lens. Subscribe to get each issue.

Subscribe now

Data sources and further reading:

Bloomberg/Kaiko announcement: PRNewswire, February 26, 2026
Bloomberg/Kaiko coverage: Finadium, A-Team Insight, Securities Finance Times (February–March 2026)
Oracle market share: DL News, CoinGecko Research, March 2026
Chronicle/BUIDL integration: Chronicle Protocol blog, March 2026
RedStone Security Token Market acquisition: RedStone blog, 2025
ERC-3643 deployment data: Tokeny, 2026
Canton Network participants: Digital Asset Holdings, 2026
Kaiko on-ramp launch: August 2025

The Bloomberg of Tokenised Real World Asset data might just be ... Bloomberg.