The loudest debates about digital money still circle the same orbit: stablecoins versus CBDCs, public chains versus permissioned ledgers, crypto innovation versus bank-grade compliance. But in a solo episode of BFRR, Michael Blaschke makes a quieter argument—one that feels less like a market call and more like a warning from the engine room. The decisive struggle, he suggests, isn’t over tokens or headlines. It’s over architecture: the layers, protocols, and interfaces that will decide what the next financial system can do, what it cannot do, and—most consequentially—who gets to decide. And at the center of that struggle sits a deceptively technical phrase with outsized consequences: digital asset interoperability.
It is a topic that rarely earns airtime because it resists simple narratives. Architecture is not a product launch. It does not trade on a chart. And yet it is the invisible skeleton of every system that claims to be the future. Blaschke’s thesis is blunt: the architectural choices being made inside central banks, commercial banks, fintechs and protocol teams are likely to shape global finance for the next 30 to 50 years. The risk is that many institutions are drifting into those choices without recognizing them as choices at all.
The IMF’s Question: A “TCP/IP” for Value
Blaschke anchors the episode around a line from an IMF working paper that reads like a technologist’s koan: what is the TCP/IP equivalent for digital assets? In the late 1970s and early 1980s, computer networks were an archipelago of proprietary protocols—IBM’s SNA, DECnet, Xerox’s XNS—each elegant within its own world and brittle outside it. Connecting systems meant custom gateways and manual integration. Complexity grew faster than ambition.
The internet did not win by declaring one proprietary stack the champion. It won by insisting on layers. With a clear separation of concerns, innovation could happen at one layer without breaking another. The infrastructure became boring, almost invisible—precisely because it worked.
Blaschke’s point is that digital financial infrastructure, in 2026, resembles that pre-internet landscape. CBDC pilots multiply. Public blockchains compete. Permissioned networks promise enterprise certainty. Stablecoins “sit awkwardly across all of these.” Corporate platforms—what MIT’s Christian Catalini has described as “corp chains”—extend the stack with proprietary rails. Each ecosystem functions tolerably in isolation. The moment value needs to move across them, the industry is back to point-to-point bridges and bespoke integration, with the same old risk: fragmentation that scales. If there is a single umbrella term for the problem, it is digital asset interoperability—the ability to move value and information cleanly across incompatible systems without rebuilding the world each time.
A Rosetta Stone for a Fragmented Industry
To make the argument operational, Blaschke leans on the IMF’s ASAP model: Access, Service, Asset, Platform. Think of it as a shared map for people who have been speaking different dialects of the same problem, including those charged—often too late—with delivering digital asset interoperability inside institutions that were never designed for it.
At the bottom is the platform layer: ledgers, execution environments, consensus mechanisms—the plumbing. Above it sits the asset layer, where the characteristics of money and financial instruments are defined: issuance, transfer mechanics, redemption logic. Then comes the service layer, where finance actually “happens”—escrow, delivery-versus-payment, FX, lending, collateralization. At the top is access: wallets, APIs, user interfaces, the on-ramps through which people and systems touch everything below.
The elegance of the model is that it clarifies what has been muddled in today’s debates. Central bankers, DeFi developers and bank IT architects often argue past one another because they are talking about different layers without naming them. ASAP gives a vocabulary for disentangling the conversation: this is an asset-layer problem; that is a service-layer interoperability question. In practice, it is a blueprint for approaching digital asset interoperability without collapsing into the false comfort of a single “winning” platform.
Interoperability Without Convergence
The episode’s most counterintuitive claim is also its most useful: interoperability does not require convergence at the platform layer. In other words, the world does not need one chain, one ledger, one consensus mechanism. It needs shared conventions in the middle—and that is where digital asset interoperability becomes possible at scale.
Blaschke points to the Jasper–Ubin experiment, a cross-border CBDC project involving the Bank of Canada and the Monetary Authority of Singapore. The two sides used different DLT stacks—Corda on one end, Quorum on the other—yet achieved atomic payment-versus-payment by standardizing a shared service protocol (HTLC), including parameters and cryptographic assumptions. The platforms did not become compatible. The service did.
This is an architectural shift with political implications. It suggests that sovereignty and competition can remain at the platform layer while coordination and standard-setting happen where it matters most: how assets are described and how services interoperate. It is a way to build bridges without forcing uniformity—digital asset interoperability as diplomacy by design.
The Platform War and the Cost of Convenience
From there, Blaschke turns to what he calls a “great platform war.” On one side is the vertically integrated model: corporate platforms that aim to control platform, asset, service, and access layers—clean, fast to deploy, and comforting for institutions that want a single counterparty to blame or trust. On the other side is the open network model of public, permissionless chains, where the platform is a commons, issuance is open, services are composable, and governance is distributed.
The architectural lens, he argues, reveals what the marketing obscures. Vertical stacks “collapse” the separation that ASAP treats as the source of flexibility and innovation. They offer a turnkey office in a prestigious building—everything works on day one—but the tenant pays in strategic freedom. Take rates can rise. Rules can change. Data can be used to compete against you. Dependency becomes a design feature. And, crucially, digital asset interoperability becomes whatever the platform operator allows it to be—an add-on rather than a property of the ecosystem.
History, Blaschke suggests, is not neutral here. The payment card industry scaled when it embraced open governance and shared rails. The barcode became transformative because it was an open standard. GPS changed the world because permissionless access unleashed experimentation no planning committee could have predicted. In that pattern lies a challenge to today’s architects of financial infrastructure: control may deliver neatness, but openness compounds learning—and accelerates digital asset interoperability by letting the edge innovate faster than the center can command.
Stablecoins as the Stress Test
The episode closes where theory becomes urgent: stablecoins. They are the most tangible bridge between crypto and fiat, and the clearest demonstration of how architectural decisions become systemic risk. Stablecoins have grown into market infrastructure, yet their expansion has often been opportunistic—multi-chain deployments, inconsistent token implementations, and bridges that can become single points of failure. When those bridges fail, losses are not academic.
Mapped onto ASAP, the fragility becomes legible. The asset layer lacks consistent cross-platform standards. The service layer is a patchwork of swapping and bridging mechanisms, often proprietary. The access layer compensates with complexity, pushing friction back onto users. And beneath it all sits a heterogeneous platform layer that is not going to converge. The result is a world where digital asset interoperability is treated as engineering glue—patched in after the fact—rather than as first-order infrastructure.
Blaschke’s argument is not that the industry needs fewer platforms. It is that it needs more boring agreements: shared semantics for assets and shared protocols for services. The “TCP/IP of digital assets,” he suggests, will not be one platform. It will be a family of standards—unexciting in the way foundational infrastructure always is, and transformative for exactly the same reason.
In the end, the choice he places before institutions is as stark as it is architectural: become an architect at the standards table—helping to define digital asset interoperability—or become a tenant adapting to someone else’s design.
IMF Working Paper: ASAP: A Conceptual Model for Digital Asset Platforms
Opinion: The trillion-dollar battle for money’s operating system
Article: The Path to Seamless Blockchain-Based Retail Payments: The Role of Interoperability
ECB Macroprudential Bulletin: Stablecoins‘ role in crypto and beyond: functions, risks and policy
Market Data: Market size of non-USD fiat-backed stablecoins up to September 2025
Bitcoin, Fiat & Rock’n’Roll Website
Bitcoin, Fiat & Rock’n’Roll Telegram Channel
Relai*: Buy Bitcoin with Relai – you can do a one-time purchase or savings plan: Click here. Use the referral code „ROCK“ to reduce transaction fees by 0.1% while supporting Bitcoin, Fiat & Rock’n’Roll.
Value4Value Podcast Streaming: Support our podcast by listening to our episodes on the Fountain Podcast App. This way, if you wish, you can support us „Value4Value“ while listening to the podcast. You can find us on the Fountain Podcast App here: Click here
Disclaimer: The content of this podcast reflects the private opinions of the hosts, serves exclusively for general information purposes and does not constitute investment advice. Always remember: Do your own research – inform yourself before making any investment decisions, such as buying Bitcoin. First try to understand what Bitcoin is and how to store it. This podcast does not provide financial advice. Note that the co-hosts might be invested in crypto assets. Read more on our website: Click here
All links marked with „*“ are affiliate links. If you use these links for purchase, the podcast receives a small share of the revenue without any additional costs to you. On the contrary, affiliate links often include discount promotions, so you can even save money. We would appreciate it if you use these links to support us. Thank you very much!