UBS Tests Ethereum for Regulated Banking: What the Nethermind Compliance PoC Means for Web3 Developers

On June 23, 2026, UBS -- the Swiss banking giant that manages $6.9 trillion in invested assets -- and Nethermind, one of the core engineering teams behind the Ethereum execution client, announced they had successfully completed two joint proofs of concept. The goal: determine whether the public Ethereum network can support the operational and compliance requirements of regulated financial institutions. The answer, tested on Ethereum's Sepolia testnet, was yes.

This is not another private blockchain pilot. UBS and Nethermind deliberately chose the public Ethereum mainnet-equivalent environment. They wanted to show that a bank can apply strong compliance checks through the systems it operates on top of Ethereum, without changing how Ethereum itself works. For developers building in web3, this is one of the clearest signals yet that institutional capital is preparing to move on-chain, on public infrastructure, on the same networks where your smart contracts live.

Why UBS on Ethereum is Different

The financial industry has been running blockchain proofs of concept for nearly a decade. Most of them followed a familiar pattern: a consortium of banks builds a permissioned ledger, tests it for a year, and quietly shelves it. What makes the UBS-Nethermind collaboration different is the deliberate choice to use public Ethereum infrastructure rather than a walled-garden alternative.

UBS is not a crypto-native firm dabbling in DeFi. It is a systemically important bank operating across more than 50 markets, subject to anti-money laundering (AML) regulations, know-your-customer (KYC) requirements, sanctions screening, and the full weight of Swiss, European, and international financial regulation. If a bank of this size can satisfy its compliance obligations on Ethereum, the argument that public blockchains are incompatible with regulated finance starts to collapse.

Andreas Kubli, Group Head of Digital Assets at UBS, framed the work as part of a broader strategy: "We are building the core infrastructure to support tokenized assets and digital assets, always guided by a client-led and responsible approach." The key word is infrastructure. UBS is not experimenting with a side project. It is laying groundwork for the tokenized asset markets it expects to serve at scale.

The Two-Stage Compliance Architecture

The proofs of concept target two critical stages of Ethereum transaction broadcasting, and together they form a complete pipeline for compliant transaction processing on a public network.

Stage one operates at the node level. UBS and Nethermind configured an Ethereum node to apply customizable compliance and risk rules before a transaction ever leaves the bank's infrastructure. The rules are programmable: restrict transactions to pre-approved wallet addresses, block interactions with sanctioned smart contracts, enforce whitelists for counterparties. This happens at the execution client layer, meaning the node itself acts as a compliance gatekeeper before transactions are broadcast to the mempool.

This is significant because it shifts compliance from an application-layer concern to an infrastructure-layer concern. Today, most on-chain compliance is handled by smart contracts -- token whitelists, transfer restrictions, blacklist mappings. But those are opt-in. A determined actor can always deploy a new contract that ignores them. Node-level enforcement, by contrast, operates before transactions reach the network. It is a hard gate, not a suggestion.

Stage two addresses a subtler problem: transaction inclusion. Even if a bank's node produces compliant transactions, those transactions still need to be picked up by block builders and included on-chain. UBS and Nethermind built a routing component that bundles approved transactions and sends them through relay services directly to selected builders. This ensures reliable inclusion without requiring the bank to run its own builder infrastructure or trust the public mempool.

The entire end-to-end flow -- compliance-checked at the node, routed through trusted relays, included by selected builders -- was tested and verified on the Sepolia testnet. Compliant transactions were consistently processed and recorded. Non-compliant transactions never made it past the node.

Preserving Ethereum's Openness

A recurring tension in institutional blockchain adoption is the trade-off between compliance and decentralization. Private chains solve compliance by locking down access, but they sacrifice the network effects, composability, and censorship-resistance that make public blockchains valuable. Public chains preserve openness, but they make it harder to enforce regulatory requirements.

The UBS-Nethermind approach sidesteps this trade-off. Compliance rules are enforced at the infrastructure layer that the bank controls -- its own nodes, its own relay connections -- while the underlying Ethereum protocol remains unchanged. The network itself stays permissionless and neutral. Any developer, protocol, or user can still deploy contracts, submit transactions, and interact with the chain as they always have. The compliance layer is additive, not subtractive.

Tomasz Kurowski, Head of Enterprise Business at Nethermind, described the philosophy clearly: "By implementing compliance controls at the infrastructure layer, we have shown that institutional requirements can be met without compromising Ethereum's openness or interoperability." This is the design pattern that could unlock institutional participation at scale: compliance on the edge, openness at the core.

The Broader Trend: Institutions Are Coming to Public Networks

The UBS announcement does not exist in isolation. It is part of a broader shift in how traditional financial institutions think about blockchain infrastructure. For years, the default assumption was that regulated institutions would need private, permissioned networks. That assumption is eroding.

In recent months, we have seen Morgan Stanley file for an Ethereum staking ETF, Goldman Sachs expand its tokenized real estate fund on public infrastructure, and multiple European banks secure MiCA licenses to offer crypto asset services. The Ripple announcement of preliminary MiCA approval from Luxembourg's CSSF on the same day as the UBS news underscores how quickly the regulatory landscape is maturing. Institutions are not waiting for a bespoke blockchain. They are learning to work with the one that already exists.

The UBS work is particularly important because it addresses the last major objection: compliance. If a bank can programmatically enforce sanctions screening, counterparty whitelisting, and transaction restrictions at the node level, the argument that public blockchains are inherently non-compliant stops holding weight.

What This Means for Web3 Developers

If you are building a DeFi protocol, a tokenized real-world asset platform, or an on-chain compliance tool, the UBS-Nethermind PoC should change how you think about your addressable market. The institutions are not coming. They are already here, testing the same networks you deploy on.

This creates concrete opportunities. Protocols that design for institutional participation from day one -- with interface-level compliance hooks, audit trails, and counterparty-aware architecture -- will be better positioned when regulated capital begins moving on-chain at scale. The compliance layer UBS demonstrated is infrastructure-side, but the applications that interact with compliant transactions will need to be ready for them.

There is also a more immediate takeaway: the Ethereum ecosystem's core infrastructure is being stress-tested by some of the most demanding users in the world. Every bug fixed, every edge case handled, every performance improvement made to support institutional use cases also benefits the broader developer community. When Nethermind optimizes its client for a bank's compliance node, those optimizations flow into the open-source client that powers the network.

What Comes Next

UBS and Nethermind have stated they plan to build on this work as both the technology and regulatory environment continue to evolve. The proofs of concept were run on Sepolia testnet and did not involve live transactions, so the next logical steps include production-grade hardening, integration with live compliance databases, and eventually, a mainnet deployment with real value at stake.

The timing is also notable. The European Union's Markets in Crypto Assets (MiCA) regulation is now in full effect, creating a clear legal framework for crypto asset services. The U.S. Clarity Act is making its way through the Senate. Regulatory clarity is arriving just as the technical infrastructure reaches maturity. The conditions for institutional Ethereum adoption have never been stronger.

For developers, the message is straightforward: the infrastructure that institutions need to participate on public Ethereum exists and has been validated by one of the world's largest banks. The gap between traditional finance and web3 is closing at the protocol level. The question is no longer whether institutions can use public blockchains, but how quickly they will.

If you are ready to build on the same infrastructure that institutions are betting on, thirdweb offers developer plans that scale from your first smart contract to enterprise-grade deployments. The networks are ready. The tooling is ready. The compliance architecture is being proven as we speak.