UBS and Nethermind Push Blockchain Compliance Below the Smart Contract Layer

UBS and Nethermind have completed two proofs of concept on the Ethereum Sepolia test network that could shift how banks, auditors, and regulators think about compliance on permissionless blockchains. Rather than relying solely on smart-contract-level controls, the work embeds compliance directly into Ethereum's block production pipeline. That is a meaningful architectural step, and the timing matters: the Basel Committee on Banking Supervision currently treats tokenized securities on permissionless blockchains the same as cryptocurrencies, triggering punitive capital requirements for any bank that touches them.

Why Smart-Contract Compliance Is Not Enough

Most institutional activity on permissionless chains today sits at the application layer. Token contracts use allow lists to restrict holders and transfer counterparties. Issuers can freeze tokens and reassign ownership. Platforms build migration paths so tokens can move to a different network if something breaks. These controls are real, but they leave several regulatory gaps untouched.

Three problems sit below the application layer and cannot be solved by smart contracts alone:

• Chain governance: Banks have no say in the rules that govern the underlying network they are transacting on.
• MEV and front-running: Maximal extractable value strategies allow block producers to reorder, insert, or censor transactions. In most jurisdictions, that constitutes illegal market manipulation, yet standard token contracts have no remedy for it.
• Counterparty control over transaction processing: When a bank submits a transaction to Ethereum, it cannot control which validator processes it or receives the associated gas fee. For regulated institutions, that raises serious AML and sanctions-screening questions.

These are the gaps the UBS and Nethermind work is designed to close.

What the Proofs of Concept Actually Tested

The two proofs of concept ran on Ethereum's Sepolia test network. The architecture moves compliance logic into the block production pipeline itself, meaning controls operate before a transaction is finalized on-chain rather than after. The source does not disclose the precise technical mechanisms beyond that framing, so specifics of the implementation remain limited at this stage.

This is not an isolated experiment. Nethermind published a joint whitepaper with Deutsche Bank in May 2025 covering the same architectural territory. Two major global banks working with the same infrastructure provider on the same class of problem, within roughly a year of each other, signals something beyond exploratory research.

The Basel Capital Treatment Problem

The regulatory stakes here are high. The Basel Committee's current position equates tokenized securities on permissionless blockchains with cryptocurrencies for capital purposes. That means a bank holding or facilitating trades in tokenized bonds or equities on Ethereum faces the same punitive capital charges as one holding Bitcoin. For most banks, that makes permissionless-chain activity economically unviable regardless of the underlying asset's credit quality.

The argument that UBS, Deutsche Bank, and Nethermind appear to be building toward is that if compliance can be enforced at the infrastructure level, permissionless blockchains are not categorically equivalent to uncontrolled crypto networks. Whether Basel supervisors accept that argument is an open question, but the proofs of concept are part of building the evidentiary case.

Implications for Accounting Firms and CFOs

For accounting professionals and CFOs advising on or auditing tokenized-asset positions, this development raises several practical questions worth tracking.

First, capital treatment. If the Basel Committee revises its position on permissionless chains in response to this kind of infrastructure-level compliance demonstration, the risk-weighting and capital disclosures for clients holding tokenized securities could change materially. Audit files and internal models built on current Basel guidance may need updating.

Second, AML and sanctions documentation. Infrastructure-level controls that determine which validators process a bank's transactions could eventually produce a new category of compliance evidence. Auditors and compliance teams should watch whether regulators begin to recognise block-production-layer controls in their AML frameworks.

Third, MEV as a financial crime risk. The explicit framing of MEV and front-running as illegal market manipulation in most jurisdictions is significant. If your clients are transacting on permissionless chains and cannot demonstrate that their transactions were not subject to MEV extraction, that is a potential audit and regulatory exposure. Infrastructure-level controls are one proposed answer, but they are not yet standard.

Where This Sits in the Broader Institutional Blockchain Landscape

The Ethereum ecosystem has seen significant investment in permissioned and private variants, partly because compliance on the public mainnet has seemed intractable at the infrastructure level. This UBS and Nethermind work, alongside the Deutsche Bank whitepaper, suggests a different path: keep the permissionless network but add a compliance layer that regulators and auditors can actually inspect and rely on.

That approach has real advantages. Permissionless networks carry deeper liquidity and broader interoperability than any private chain. If compliance can be credibly demonstrated at the block-production level, the case for institutional activity on public Ethereum becomes substantially stronger.

The proofs of concept are on a test network. Production deployment, regulatory recognition, and Basel guidance revisions all remain ahead. But the directional signal from two of the world's largest banks is clear: infrastructure-level compliance is now a live area of institutional R&D, not a theoretical exercise.

For accounting and audit professionals, the right response is to understand the architecture well enough to assess its compliance claims when clients begin to reference it, and to monitor Basel Committee commentary for any shift in how permissionless chains are treated for capital purposes.

Source: Ledger Insights