Crypto walked so banks could run

The following is a guest post and opinion from Ben Nadareski, Co-founder & CEO of Solstice .

Institutions were never going to arrive in crypto the way crypto wanted them to. No stampede into governance tokens. No CFO proudly announcing that idle treasury had been rotated into volatile assets. No pension fund committee suddenly speaking fluent DeFi. That was always the fantasy version.

The real version is less theatrical and far more important. Institutions will not buy crypto as a belief system. They will instead use it as infrastructure.

Not because banks cannot copy the code. They can. But because they cannot copy the jungle that made the code useful: the speed, failure, pressure, and live-market iteration that web3 has been refining in public for years.

The Code Was Never the Moat

That is the part the institutional crypto debate keeps missing. The advantage of web3 is not that banks are technically incapable of building blockchain infrastructure. Many are perfectly capable. They have capital, engineers, consultants, vendors, internal innovation labs, and enough strategy decks to pave a road from Canary Wharf to Singapore.

A bank can spin up a chain. For example, BlackRock’s BUIDL and DTCC’s tokenization service show that the institutional response is not to recreate crypto as a belief system, but to adopt tokenization as infrastructure. It can fork an execution environment. It can wrap the whole thing in compliance language, add permissioning, bring in a vendor, and present it six months later under soft blue lighting at a financial infrastructure conference. But infrastructure is not only what gets built.

Crypto’s real moat is not decentralisation. It is iteration velocity under pressure. The industry tests financial ideas in the wild, often brutally, sometimes embarrassingly, but quickly. Products launch, break, fork, attract liquidity, lose liquidity, get arbitraged, get exploited, get rebuilt, and then get copied by someone with a better version before the original team has finished the post-mortem.

This looks chaotic from the outside because it is chaotic. A good example is the repeated wave of bridge exploits and protocol failures (take latest Kelp DAO exploit), that forced the market to harden its security assumptions in real time, which is one reason Wall Street is still cautious about adoption. But then again, it is also one of the most efficient financial testing environments ever created.

Traditional finance likes sandboxes. Crypto is the sandbox after someone removed the safety labels, invited the traders, opened the API, connected the liquidity, and let the market decide what deserves to live.

That is why the recent institutional interest in web3 is telling. Stripe’s Bridge acquisition fits that pattern: it points to stablecoins becoming part of the payments stack, not just a speculative asset class. Stripe did not acquire Bridge because stablecoins were a nice ideological accessory; it completed the acquisition because stablecoin infrastructure is becoming part of the payments stack. BlackRock did not launch BUIDL because tokenisation sounds futuristic; it launched a tokenised fund because settlement, access, and collateral movement can be redesigned onchain. J.P. Morgan’s Kinexys, now points in the same direction: the interest is not in crypto, but in what the rails can do once they are made usable inside financial workflows.

Crypto Learns by Bleeding in Public

That jungle is where the real product-market fit is found…not in the white paper. Not in the internal lab. Not in the workshop where everyone agrees that interoperability is important. It happens when capital moves across systems, when liquidity fragments, when bridges introduce new attack surfaces, when users behave badly, when incentives get gamed, and when the elegant architecture meets the swamp.

Crypto has spent years getting punched in the face by reality. That is why the infrastructure is improving.

Every bridge exploit, oracle failure, liquidation cascade, broken incentive loop, governance attack, and over-engineered protocol that died quietly after three months added something to the collective memory of the market. Painful, expensive, often absurd, but useful.

Banks do not work that way. Nor should they, frankly. Banks are designed to preserve trust, minimise risk, protect depositors, obey regulators, and avoid blowing themselves up in search of product-market fit. Their caution is rational. Their processes exist for a reason.

But those same processes make them slow in precisely the domain where speed compounds.

A bank building internally has to solve every problem in sequence: architecture, security, compliance, custody, bridging, reporting, accounting, liquidity, legal treatment, operational risk, internal approval, vendor review, and then the steering committee. Then comes the pilot. Then the pilot is often de-risked until it is no longer quite the thing it was meant to test.

By the time the bank reaches version one, crypto has already built version one, watched it fail, launched version two, discovered the bridge assumption was wrong, rewritten the liquidity model, and found out what users actually do when real money is on the line.

That is not because one side is smarter. It is because one side is built for market-speed experimentation and the other is built for institutional control.

Control Is the Trap

This is especially true in onchain finance, where nothing exists in isolation. A stablecoin is not just a stablecoin. It is collateral, settlement medium, liquidity pair, routing asset, integration layer, and composable building block. Yield is not just an APY. It is a risk profile, a redemption mechanism, a custody question, a reporting issue, a regulatory perimeter, and an operational decision. A bridge is not just a connector. It is a two-sided smart contract with a user interface. The stack is alive. Touch one part of it and six others twitch.

That is why building from inside a bank is so difficult. The challenge is not merely “Can we launch a chain?” Of course they can. The challenge is whether that chain connects cleanly into the messy, liquid, rapidly changing ecosystem where actual usage happens.

The moment you need bridging, integrations, liquidity routing, external protocols, custody rails, and settlement assumptions, the clean internal model starts getting messy.

Trying to recreate crypto-native infrastructure internally means spending years rediscovering problems that open networks have already tripped over: bridge risk, liquidity fragmentation, oracle assumptions, composability failures, smart contract exploits, redemption friction, and incentive loops that look brilliant until someone actually uses them.

Instead of innovation, this can be perceived as institutional archaeology with a budget.

The sharper path is to recognise what web3 has already produced: infrastructure tested under conditions traditional finance rarely allows until much later, if ever. That does not mean every crypto product deserves institutional adoption. Much of the ecosystem is still noisy, fragile, overhyped, or over-financialised.

But the strongest parts of it have survived a level of stress most internal bank pilots will never experience. That matters.

The Smart Money Will Not Rebuild the Stack

The endgame is not a heroic contest between Wall Street and web3. The more likely outcome is quieter: the institutions that matter will stop trying to recreate the entire onchain stack behind closed doors and plug into the parts already tested by live markets.

Every bank, fintech, asset manager, and treasury platform does not need to spend years rebuilding infrastructure just to rediscover problems crypto-native teams have already met in public. The smarter model is to take systems that have survived real liquidity, real volatility, real users, and real adversaries, then add the layers institutions require: custody, reporting, auditability, compliance controls, permissioning where needed, and risk disclosures.

The point is not to make banks behave like DeFi protocols. They cannot, and they shouldn’t either. The point here is to give institutions access to the output of crypto’s speed without forcing them to live inside crypto’s Wild West.

A CFO does not want a more exotic balance sheet for the sake of sounding innovative. A risk committee is not looking for hype. Institutions want capital to move faster, settle more cleanly, earn more intelligently, and remain explainable when auditors, regulators, and board members start asking questions. This is where web3 has something genuinely powerful to offer, I believe. Blockchain offers faster settlement, programmable liquidity, transparent collateral, tokenised yield, composable financial products, and infrastructure that can move, earn, settle, and integrate across applications.

Wall Street’s mistake would be to admire those capabilities, copy the surface, and spend years rebuilding them in a private corner of the old system. Crypto has already paid for many of those mistakes. Expensive, often ridiculous lessons, but we’re learning nonetheless.

So the future of finance will not be built entirely inside banks, nor entirely outside them. The more practical outcome is that banks, fintechs, asset managers, and treasury platforms will plug into crypto-native infrastructure once it becomes reliable enough, legible enough, and compliant enough to use.

They may not call it crypto. They may call it settlement efficiency, treasury optimisation, embedded yield, programmable collateral, real-time liquidity, or simply better rails.

Fine. The prize is that a live market has already done what no internal innovation lab can properly simulate: tested financial infrastructure with real capital, real users, real stress, and real consequences, every hour of every day, for years.

Wall Street can and will replicate the architecture. What it cannot replicate is the years of live market pressure and community anticipation that made the architecture worth using in the first place.