Every participant works from the same ledger state, which can reduce the need to reconcile separate records after each transaction. These networks bring several institutions onto one operating model. Their value depends on whether every member can trust both the rules and the underlying technology. So the technology supporting such a network must reflect how banks operate. Participants need clear roles. Transaction details must remain confidential. The network must also provide certainty about when a transfer is complete.

Besu, formerly known as Hyperledger Besu, was built with these requirements in mind. It is an open-source Ethereum client that can run private and permissioned networks. Banks can use it to share infrastructure while retaining control over participation and governance. This combination makes Besu relevant for interbank payments, tokenized deposits, collateral movement, and other workflows involving several regulated institutions.

Permissioning supports controlled participation

A shared banking network needs a defined membership model. Banks must know which institutions can connect, submit transactions, and operate the infrastructure. Node-level permissioning controls which machines may join the network. Account-level permissioning determines which cryptographic accounts can transact. Banks can manage these rules locally or through on-chain smart contracts. This gives a consortium a practical way to formalize participation. Members can agree on how institutions join, who runs validators, and how changes are approved. Every member follows the same technical rules without giving one bank control of the entire network.

Privacy protects sensitive banking activity

Known participation does not mean every member should see every transaction. A bank may need to share information with a counterparty while keeping the same information hidden from other network members. Besu addresses this need through private transaction groups. Selected institutions can complete a transaction without exposing all its details across the consortium. The common ledger can still coordinate the wider network.

Banks can add a modular privacy layer mandatorily, though, when the wider system requires stronger privacy controls. It can bring selective disclosure kind of features that can give authorized parties the information needed for verification.

Immediate finality creates settlement certainty

Banks need to know when a transaction has become final. That certainty allows treasury, accounting, and settlement processes to continue without waiting for several more blocks. Besu supports IBFT 2.0 and QBFT consensus for networks with known validators. Both mechanisms provide immediate block finality. Once a valid block is committed, participating banks share the same confirmed ledger state. The network can continue operating if a limited number of validators fail or act maliciously. This safeguard matters when several institutions maintain the ledger.

Private Besu networks can also set gas prices to zero. Participants avoid fluctuating fees, while gas accounting still limits the computing work in each block. This creates a more predictable operating model.

Ethereum compatibility strengthens the network

Besu follows the Ethereum specification. Developers can build smart contracts in Solidity and use established Ethereum tools. This reduces dependence on a proprietary technology stack. Teams can use familiar tools from the wider Ethereum ecosystem. Applications built on Besu can also be adapted for other EVM environments with less redevelopment. This flexibility matters as a shared network evolves. Ethereum compatibility gives members a common execution model while leaving room for future connections. Besu also has a modular architecture. The consortium can adjust network components as requirements change. Integrations can connect the ledger with banking systems and other networks.

Institutional projects have proven the model

Besu is already being used in shared financial infrastructure. Swift is developing an EVM-compatible ledger for recording payment commitments and settling value in tokenized commercial bank money. Here, all the participating banks retain control of their own keys and assets. During the European Central Bank DLT trials, transactions used the SWIAT ledger, a private permissioned EVM network built on Besu. The platform supported tokenized collateral in transactions connected with central bank settlement infrastructure.

DTCC has also built a Besu-based platform for tokenized real-time collateral management. These initiatives demonstrate the model across different areas of regulated finance.

Move from technology to reliable operations

A production network requires more than Besu nodes. Members need clear processes for onboarding and incident response. Deployment must also meet their security requirements. Experienced providers support managed infrastructure and bank-owned cloud deployment. Banks may also choose an on-premises or hybrid model deployment with such infrastructure partners. They can bring in added privacy controls through middleware. Integration services can help connect the ledger with existing banking systems.

While Besu provides the shared execution layer and governance foundation, such providers can help institutions deploy and operate that network. Together, they give banks a shared infrastructure for regulated finance. The network remains under institutional control and can adapt as requirements change.