Public vs Permissioned Blockchains in Institutional Finance

With more than $26 billion in real-world assets now settling on-chain according to RWA.xyz, the question facing institutions is no longer whether blockchain rails belong in capital markets — it is which rails. The public vs permissioned blockchains debate has run for a decade, but it is being settled now, in production, by treasurers, fund sponsors, and market operators choosing where their instruments will actually live. The answer emerging is more nuanced than either camp predicted, and it has direct consequences for anyone issuing or holding digital securities.

Why Institutions Reached for Permissioned Networks First

The first institutional blockchain deployments were almost uniformly permissioned: closed validator sets, known participants, transactions visible only to counterparties. The logic was sound for its moment. Banks and market infrastructures faced unresolved questions about data privacy, transaction finality, and counterparty identity, and a network where every participant is contractually bound and legally identifiable answered all three at once.

Permissioned networks still hold real advantages for specific workloads. Interbank settlement experiments, wholesale central bank money trials, and intragroup treasury movements benefit from guaranteed validator identity and the ability to reverse or amend records under a legal framework all participants have signed. The Bank for International Settlements has framed this vision as the "unified ledger" — a shared, regulated environment where central bank money, commercial bank deposits, and tokenized assets coexist under common governance.

But the permissioned-first era exposed a structural weakness: networks built as closed clubs inherited the economics of closed clubs. Each consortium became its own island, with its own membership process, its own technology stack, and — critically — its own liquidity. An instrument issued on a network with forty members can only ever be distributed to forty members. Several high-profile consortium chains spent years and significant capital discovering that distribution, not technology, is the hard problem in capital markets.

Why Issuance Volume Keeps Moving to Public Rails

Meanwhile, the measurable growth in tokenized real-world assets — treasuries, private credit, funds, commodities — has happened overwhelmingly on public blockchains. The reasons are the mirror image of the consortium problem.

Distribution is native. A public chain is a single global venue. An instrument issued there is technically reachable by any qualified investor on earth without a network membership negotiation. For issuers, that converts distribution from a bilateral integration project into a compliance question — who is allowed to hold this — which is exactly the question issuers already know how to answer.

Neutrality lowers the trust burden. No single institution controls a public network's validator set, which means no counterparty must trust a competitor's infrastructure. For an industry where market participants are also rivals, credible neutrality has proven more valuable than the control that permissioned networks offered.

Composability compounds. Tokenized cash, tokenized collateral, and tokenized securities on the same rails can interact atomically: delivery-versus-payment without an intermediary sequencing the legs. Each new asset class deployed on public rails increases the utility of every asset already there — an effect closed networks structurally cannot replicate.

The cost of these benefits is that public chains do not natively know who anyone is. Raw public rails, uncontrolled, are unusable for regulated securities. Which is why the real institutional architecture emerging is neither side of the old debate.

The Synthesis: Permissioned Assets on Public Rails

The pattern now dominating institutional deployment is permissioned logic at the asset layer running on public infrastructure at the settlement layer. The token itself carries its rulebook: transfer restrictions, investor allowlists, jurisdiction checks, and lockup enforcement are written into the instrument as programmable compliance, executed automatically on every transaction. The network is open; the asset is not.

This inverts where control lives, and the inversion matters. In a permissioned network, compliance is a property of the venue — leave the venue and the controls vanish. In a compliance-embedded asset, the controls travel with the instrument wherever it moves. A tokenized security structured this way cannot be transferred to an unverified wallet regardless of what platform, protocol, or counterparty attempts the transfer, because eligibility verification is a condition of settlement itself.

This is the architecture Commertize is built on: a digital capital markets platform where issuance, investor qualification, and settlement operate as one stack, and where every instrument enforces its own regulatory perimeter at the token level. The public network provides distribution and atomic settlement; programmable compliance provides the boundary that regulators and issuers require. Institutions get the reach of open rails without inheriting their permissionlessness.

What Regulators Are Actually Signaling

Regulatory posture has evolved alongside the architecture. Early guidance implicitly favored permissioned systems because they mapped cleanly onto existing supervisory models — identifiable operators, defined memberships, clear accountability. But supervisors have since engaged directly with compliant activity on public networks. The Monetary Authority of Singapore's Project Guardian has run institutional pilots across foreign exchange, funds, and fixed income using public-chain infrastructure with embedded controls, working with global banks and asset managers under regulatory supervision.

The consistent signal across jurisdictions is that regulators are largely agnostic about the ledger and uncompromising about the controls. What they require is that investor qualification, transfer restrictions, sanctions screening, and recordkeeping demonstrably function — and, increasingly, they recognize that controls enforced in code at the asset layer can be more auditable than controls enforced by manual process at a venue. A compliance officer can inspect a transfer restriction that has executed identically on every transaction since issuance. The equivalent assurance from a manual regime requires sampling and trust.

A Decision Framework for Institutions

For institutions choosing rails today, the question decomposes into three practical tests.

Where does your distribution need to reach? If the use case is closed by nature — intragroup settlement, a bilateral repo facility, a central bank trial — permissioned infrastructure remains a defensible choice. If the instrument needs investors you have not met yet, public rails with asset-level controls are the only architecture that scales distribution without scaling integrations.

Can compliance survive leaving your perimeter? Ask of any proposed design: if this token moves somewhere unexpected, do the controls still bind? If the answer depends on every venue behaving correctly, the compliance model is a hope. If the answer is enforced by the instrument itself, it is architecture.

Who bears the infrastructure burden? Running or governing a permissioned network is an ongoing institutional commitment — validator operations, membership governance, upgrade politics. Public rails externalize that burden but demand rigor at the asset and custody layers instead. Most issuers are better served putting their rigor where their legal obligations actually sit: the instrument, not the plumbing.

The decade-old debate framed public and permissioned as rivals. The market's answer is that they were describing different layers all along. Settlement wants to be open; assets want to be governed. Institutions that build on that synthesis are not choosing a side — they are choosing the part of the stack where control genuinely belongs.

Have an asset you're thinking about tokenizing? See how the platform works and start at commertize.com/tokenize, or contact the team and tell us what the asset is — if it isn’t a fit, that is a useful answer to get in one conversation rather than three.