
UBS and Nethermind ran PoCs showing banks can run compliant Ethereum nodes without changing the protocol. Two-stage compliance controls validated on Sepolia testnet.
UBS and Nethermind finished two proofs of concept this week, showing that a public Ethereum node can be configured to enforce bank-grade compliance rules without changing the underlying protocol. The testing happened on Sepolia, a test network, and used no real funds.
The first piece of the setup: the teams modified an Ethereum node to apply custom risk filters. Those filters restricted outbound transactions to pre-approved addresses and blocked specific smart contract interactions. The second piece: a separate component routed approved transaction bundles to selected builders through relay services, giving the bank control over which blocks its transactions land in.
Andreas Kubli, Group Head of Digital Assets at UBS, said the results show that institutions can achieve controls while keeping the network open. Tomasz Kurowski from Nethermind added that putting compliance at the infrastructure layer does not require sacrificing Ethereum's interoperability.
For traders and allocators watching the institutional pipeline, this is a concrete step. The question has always been whether a public, permissionless chain can satisfy the same risk standards that a bank applies to its own private systems. This PoC suggests the answer is yes, at least on testnet.
The simple read: banks can now run Ethereum nodes that block bad transactions and pick their block builders. The better read is that the real test will come when these controls are exposed to a live adversarial environment. A Sepolia test is not a mainnet with sophisticated attackers trying to game the filters. The mechanism that matters is how the node handles edge cases – a legitimate smart contract interaction that looks suspicious, or a relay that fails to include an approved bundle. UBS and Nethermind have not published a timeline for mainnet deployment.
The confirming factor would be a live pilot with real transaction value, where the node processes thousands of daily transactions and the compliance filter catches the intended set without false positives. The weakening signal would be a case where the filter blocks a legitimate transaction or a relay drops out, forcing the bank to manually override the system. Neither has happened yet.
For anyone following Ethereum's institutional path, the PoC closes one open question: whether a bank can touch a public chain at all without demanding a fork. The next question is whether the controls hold up under scale.
Prepared with AlphaScala editorial tooling from the source reporting linked above. Indexable analysis may include a cited Alpha Score value. Publishing checks screen each story before release. Educational coverage, not personalized advice.