Share article

Bloomberg just made a pretty loud move into on-chain markets, partnering with Kaiko to push licensed, terminal-grade pricing into blockchain environments. [1] The immediate catalyst is simple: tokenized Treasurys and repo products are now a roughly $25 billion corner of crypto, and the data plumbing is still a bit dodgy.
Instead of asking institutions to pull prices from off-chain terminals and then manually reconcile what is happening on-chain, Bloomberg and Kaiko say they want to make Bloomberg's licensed datasets accessible within blockchain networks. [2] If they pull it off, this is less "nice to have" and more "required infrastructure" for tokenized real world assets (RWAs) to trade like grown-ups.

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What Bloomberg and Kaiko are actually building

The headline is not "Bloomberg now covers crypto." That ship sailed ages ago. The shift here is delivery: Bloomberg's licensed financial data is being positioned for on-chain consumption, using Kaiko as the digital asset market data layer. [3]

Per the announcement, the focus is on tokenized markets that institutions actually care about, notably: [1]

  • Tokenized US Treasurys
  • Repo-style on-chain markets (where funding and collateral mechanics matter a lot)

That "on-chain access" phrasing is doing heavy lifting. It implies a world where pricing, reference rates, and related market data can be used by smart contracts, market makers, custodians, and risk systems without everything routing through the usual off-chain pipes.

Kaiko is a logical pick for this job. They already sit in the "market data is a product" lane, with infrastructure designed around aggregating venues, standardising feeds, and distributing them in a way that institutions can plug into. Bloomberg brings the licensed datasets and distribution muscle. Kaiko brings crypto-native rails and the ability to meet chains where they live.

The real problem: tokenization is on-chain, pricing is not

Tokenized assets are "on-chain" in the sense that ownership and transfers are visible. Pricing is where things get messy.

A lot of RWA tokens do not trade with deep, continuous liquidity on open venues. Even when they do trade, you can get:
  • Thin order books that make the last price basically a suggestion
  • Stale prices because trading is intermittent
  • Permissioned transfer logic, which reduces the usefulness of public market signals
  • NAV-driven products, where the meaningful price is calculated off-chain and posted later
That's why "terminal-grade" matters. For institutions, the game is not vibes, it is mark-to-market, risk limits, collateral haircuts, and audit trails. If tokenized Treasurys are going to be used as collateral in repo-like structures on-chain, then pricing and reference data becomes systemically important. Bad data equals bad liquidations, incorrect margin, or mispriced collateral. That is how you end up with a proper mess.
Bloomberg and Kaiko are effectively saying: let's make the same calibre of data institutions already trust available where the assets actually settle.

Why this matters for the $25B tokenized asset market

The $25B figure is the key context. Tokenized "risk-free" yield products and short-duration collateral instruments have become one of the few RWA segments with repeatable demand. Not because CT (Crypto Twitter) suddenly became a fixed income desk, but because stable yields and on-chain settlement are useful when the rest of the market is rotating.
To scale from "interesting pilot" to "institutional market," tokenized assets need three things that TradFi takes for granted:
  1. Reliable pricing and reference rates
  2. Clear rules around data licensing and redistribution
  3. Distribution into the systems that people already use (risk, treasury, settlement, reporting)

Bloomberg can plausibly help with all three, especially the first and third. Kaiko's role suggests the implementation is meant to be more than a PDF of prices posted once per day. The stated ambition is data that can be embedded into blockchain workflows, not bolted on later.

The on-chain angle: what improves, and what stays opaque

As a degen-turned-journalist, I care about what we can verify on-chain, not what sounds good in a press release.

What this partnership can improve:

  • Price discovery inputs for smart contracts: If protocols are using tokenized Treasurys as collateral, they need robust price references. Cleaner feeds reduce oracle games and manipulation risk.
  • Operational workflows: Funds and desks that already live in Bloomberg's ecosystem can bridge into on-chain settlement with fewer manual steps.
  • Standardisation across venues: One chronic issue in crypto is fragmented price sources. A unified, licensed feed can reduce "pick your favourite exchange print" nonsense.

What still will not magically become transparent:

  • True liquidity: Data does not create liquidity. If tokenized assets are mostly held in a few wallets and only move in chunky transfers, the market can still be lumpy.
  • Permissioned market structure: Many tokenized products restrict who can hold and transfer. That can limit secondary trading, which limits organic price discovery.
  • Issuer mechanics: The real risk in tokenized Treasurys is often operational, legal, or redemption-related. Pricing feeds do not solve redemption gates, settlement cutoffs, or issuer-specific terms.

So yes, better data rails are bullish for market structure. No, it does not automatically mean a free-for-all on-chain bond market with infinite depth.

Who benefits first: not the apes

This is an institutional upgrade, full stop.

The first beneficiaries are likely to be:

  • Tokenized cash management products that need credible daily pricing and reporting
  • On-chain collateralised lending and repo-like venues that need robust marks
  • Prime brokers, custodians, and fund admins that hate recon breaks more than they hate volatility

Retail "apes" (defined: traders who pile into a narrative trade without much diligence) probably will not feel this directly, at least not immediately. The more realistic impact is indirect: better data makes it easier for serious players to deploy size, which can eventually improve liquidity and reduce the spread tax everyone pays.

What to watch next (the evidence checklist)

If Bloomberg and Kaiko are serious about "on-chain access," the proof will show up in implementation details. Here's what I will be watching for:

  • Which chains and standards are supported first: Public chain integrations versus private or permissioned deployments will tell you who the target user really is.
  • How licensing works on-chain: Publishing data into environments where it can be copied is non-trivial. Expect permissioning, access control, or cryptographic gating.
  • Whether protocols actually use it: The win condition is not a press release, it is adoption in collateral engines, settlement flows, and risk systems.

Risks, and what would invalidate the bullish take

Risk box:

  • Distribution risk: If the data is only accessible to a closed set of participants, it may not improve broad market transparency, just internal workflows.
  • Liquidity risk: Tokenized markets can still be thin. Great prices do not help if no one is quoting size.
  • Oracle and integration risk: On-chain usage lives or dies by how feeds are integrated, monitored, and failsafed.

Invalidation level: if this stays as "Bloomberg data, but now with a blockchain wrapper," without real on-chain consumption by major tokenized Treasury and repo venues, then it is mostly marketing. The moment we see live integrations that protocols and institutions actually settle against, that is when the $25B market starts looking like it can handle the next order of magnitude.