Why Institutions Don't Want Transparency

The biggest blockchain in institutional finance has a feature most crypto developers hate. That's exactly why it's winning.

The Transparency Trap

Every developer who learned blockchain in 2017 absorbed the same gospel: transparency is the point. The whole value proposition was an immutable, public ledger. No hidden transactions. No back-room deals. No trusted third parties. Trust the math, not the institution.

It was a compelling vision. It was also completely incompatible with how institutional finance actually works.

Try explaining to a portfolio manager why her $800 million Treasury position should be visible in a public mempool. Or to a compliance officer why client transaction data should be queryable on a block explorer. Or to a repo desk why their intraday collateral positions should be broadcast to every counterparty on the network in real time.

You can't. And that's been the invisible wall between crypto's infrastructure ambitions and actual institutional adoption for the better part of a decade.

The firms that cracked it didn't build a better transparency layer. They rethought the architecture entirely.

What $8 Trillion Buys You

Canton Network has processed over $8 trillion in tokenized assets. That number deserves to sit for a moment, because it doesn't get nearly enough attention relative to the projects that attract more noise.

The roster of institutions running production workloads on Canton reads like a who's who of global financial market infrastructure:

• Broadridge runs its Distributed Ledger Repo platform on Canton rails. Volumes on that platform jumped from $1 trillion to $5.9 trillion between August 2024 and August 2025 — a 490% year-on-year increase. That's not a proof of concept. That's a live market.
• J.P. Morgan uses JPM Coin for settlement on the Broadridge DLT repo platform, integrating its blockchain payment infrastructure with tokenized repo transactions in production.
• DTCC announced in December 2025 that it is partnering with Canton and Digital Asset to tokenize DTC-custodied U.S. Treasury securities — the first step in a multi-year roadmap to bring the full depth of DTC custody onto a blockchain network. MVP targeted for the first half of 2026.

And just this week, a new product launched on top of Canton's rails: ACME Lend, an institutional credit market offering 24/7 lending and borrowing against tokenized collateral. The pitch is simple — mobilize assets that would otherwise sit idle, earn yield, borrow against positions you'd rather not move. It's the collateral mobility problem, finally addressable on-chain.

Why Canton, and not one of the dozens of other blockchain networks competing for institutional business? The answer is the same as it's always been: privacy.

Verifiable Privacy Is Not a Feature. It's the Architecture.

Most blockchain networks that claim to support "institutional use cases" are really offering permissioned silos — a walled garden where you control who sees what by controlling who's on the network. That's essentially a private database with extra steps. It solves the visibility problem by limiting participation, not by building privacy into the base layer.

Canton's approach is different. It's built on Daml smart contracts, which enforce a "need to know" principle at the protocol level. Participants on the Canton Network can only see the data they're entitled to see — not because an administrator made that decision, but because the smart contract itself enforces it cryptographically. Two counterparties executing a repo trade see their transaction. No one else does.

This distinction — privacy as architecture versus privacy as administration — is what makes Canton viable for institutions that would never accept a truly public ledger but also don't want to trust a single operator to enforce data boundaries correctly.

It's also what allows Canton to be both open and private simultaneously. Any firm can join the Canton Network. Every firm's data is protected by default. The network can have hundreds of participants, and each one operates in a confidential sub-environment with selective disclosure to counterparties as needed.

The crypto community noticed when DTCC chose Canton in December 2025. Some developers criticized the choice specifically because of its privacy architecture — arguing that an $8 trillion network should be transparent. That criticism reveals a genuine values gap. For retail DeFi, transparency is a feature: it allows trustless verification, open auditability, and composability without permission. For institutional finance, transparency at that scale is a liability. Exposing a custodian's full Treasury book to the network isn't auditability. It's a systemic risk.

DTCC's decision wasn't a betrayal of blockchain values. It was an honest recognition that institutional infrastructure has different requirements than retail infrastructure, and that choosing the right architecture matters more than defaulting to the loudest ideology.

The Repo Market as a Case Study in What Works

The repo market is a useful lens for understanding why privacy-first architecture is necessary, not optional.

Repo is the overnight borrowing market underpinning much of fixed income. A dealer borrows cash overnight by pledging Treasuries or agency securities as collateral, then buys them back the next morning. It's how primary dealers fund inventory, how money market funds deploy cash, and how a significant portion of the short-term funding market stays liquid.

It's also a market where exposing positions is commercially catastrophic. If a dealer's overnight borrowing needs are visible to competitors, those competitors will know exactly where funding stress is accumulating before it surfaces in public spreads. That information asymmetry destroys the market's ability to function. Repo depends on counterparty confidentiality in ways that, say, tokenized equity ETFs simply don't.

Broadridge's DLT repo platform understood this from the beginning. When J.P. Morgan's settlement integration went live, it wasn't announced as a transparency play — it was announced as an operational efficiency play. Settlement finality in minutes instead of hours. Reduced reconciliation overhead. Intraday liquidity management without the drag of T+1 or T+2 cycles. The blockchain is the plumbing. The privacy architecture is what made the plumbing acceptable to the institutions using it.

The 490% volume growth in a single year suggests that once the privacy problem is genuinely solved, institutional uptake can move quickly.

What DTCC's Treasury Tokenization Actually Means

The DTCC-Canton partnership is worth understanding in its full context, because the market infrastructure implications extend well beyond a single announcement.

DTC is the central securities depository for U.S. equities and a significant custodian of U.S. debt securities. When DTC tokenizes Treasuries, it's not creating a parallel market for tokenized versions of Treasuries sitting alongside the real thing. It's bringing the actual underlying custody record on-chain.

That matters because the bottleneck in tokenized asset markets has never been the token. It's been the connection between the token and the underlying asset — who holds it, who can enforce rights against it, what happens in a default. If the custodian of record itself is tokenizing the securities, that link is native, not derivative.

The SEC's no-action letter giving DTC the regulatory green light to proceed — issued weeks before the DTCC announcement — is the piece that makes this more than theoretical. The legal question of whether a DTC participant holds tokenized securities with the same legal standing as the traditional book-entry equivalent has been answered, at least provisionally: yes.

Production target is the second half of 2026. The controlled environment MVP is expected in the first half. For context, DTCC handles approximately $2.5 quadrillion in securities transactions annually. Even a small fraction of that moving to tokenized settlement rails would represent the most significant blockchain deployment in capital markets history.

The Architecture Problem Nobody Talks About

There's a framing that has circulated in digital asset circles for years: that institutional adoption of blockchain is slow because banks are conservative, regulators are hostile, and legacy infrastructure has too much inertia.

That framing isn't wrong, exactly, but it misidentifies the primary constraint.

The primary constraint has been architectural. Most blockchain networks were not built for institutional use cases. They were built for permissionless, transparent, retail-accessible finance — and then retrofit, with varying degrees of success, for institutional requirements. Privacy layers were added as afterthoughts. Permissioning was grafted on top of public infrastructure. Compliance tooling was bolted to networks that were designed to resist exactly that kind of oversight.

Canton started from the opposite premise: that institutional finance requires privacy as a base layer, not a feature; interoperability as a design principle, not an integration challenge; and compliance as a native capability, not a retrofit. The $8 trillion in processed volume, the Broadridge repo platform, the DTCC partnership, and the ACME Lend launch this week are all downstream of that architectural decision made years ago.

The lesson for the broader tokenization market is worth stating plainly: the networks that will win institutional adoption aren't necessarily the ones with the most liquidity, the lowest fees, or the most DeFi composability. They're the ones that started with the right architecture for the institutional clients they were trying to serve.

Transparency is a feature. Verifiable privacy is an architecture. For the institutions moving $8 trillion, that's not a subtle distinction.

Sources: Ledger Insights — DTCC to tokenize US Treasuries on Canton Network · The DESK — Broadridge DLT repo platform volumes boom · Ledger Insights — JPM Coin settlement on Broadridge DLT repo · Canton Network · ACME Lend