An institution holds to one standard wherever it operates: its own governance, risk, and compliance framework. Bedrock carries that standard onto public networks by putting the controls inside the infrastructure the transaction runs through.

the problem

Public networks don't enforce policy

Banks and other regulated institutions want to use public blockchain networks for payments, tokenized assets, and settlement. But public networks weren't built with a bank's governance, risk, and compliance requirements in mind. Existing tools don't close that gap: platforms lose visibility the moment a transaction leaves the wallet, and generic infrastructure providers don't enforce a bank's own policy at all.

the solution

Enforced from instruction to settlement

Bedrock is operational infrastructure that lets a regulated institution run digital asset activity on public networks inside its own existing governance and compliance framework. Oversight does not stop at the initial screening: checks, approvals, and evidence cascade through the transaction flow, so the institution keeps visibility and auditability from instruction through to settlement.

Enforcement happens at the node

In two proofs of concept with a Tier 1 global bank, we configured an Ethereum node to apply the institution's own compliance and risk rules, and built a component that routes approved transactions through relay services to selected builders for reliable inclusion. Both were tested on the Sepolia test network. The controls sat inside the node rather than in a layer above it, so the record came from infrastructure we operated rather than an external explorer or a vendor's API.

By implementing compliance controls at the infrastructure layer, we have shown that institutional requirements can be met without compromising Ethereum's openness or interoperability

Tomasz Kurowski,
Head of Enterprise Business at Nethermind

Five capabilities, one interface

Five things Bedrock does, from the checks that gate a transaction to the back-office systems the record lands in. All of it runs on the Nethermind Client, the Ethereum execution client we build and maintain, which runs about 32% of the network (Ethernodes, September 2026).

01. Policy clearance

AML, sanctions, and Travel Rule checks run before the transaction is built

02. Node enforcement

The execution client verifies a transaction cleared policy and was not altered

03. Routing control

Cleared transactions broadcast only through approved paths, never the open mempool

04. Golden source

The institution's own node as the record of onchain state

05. Treasury, payments and OMS

ISO 20022 and FIX integration with the message flows you already run

bedrock

Institutional Node Infrastructure

Operating safely on public networks, without leaving your institution's controls behind

Your standard holds onchain

the problem

Public networks don't enforce policy

the solution

Enforced from instruction to settlement

Enforcement happens at the node

Five capabilities, one interface

01.

Policy clearance

02.

Node enforcement

03.

Routing control

04.

Golden source

05.

Treasury, payments and OMS

See Bedrock at Sibos

We're showing an early look at Bedrock at Sibos (Miami, September 28 to October 1). Can't make it there? Get in touch and we'll walk you through it directly.