# Permissioned blockchain

A permissioned blockchain restricts who may operate nodes, validate transactions, or participate, in contrast to public chains open to anyone. Banks use permissioned infrastructure such as Hyperledger Besu and Canton when governance, privacy, and known-participant requirements rule out fully public networks.

## Where permissioned chains fit in bank infrastructure

Interbank settlement, tokenized deposits, and market infrastructure pilots typically run permissioned: participants are identified institutions, data visibility is controlled, and governance is contractual. The custody and tokenization stack must treat these chains as first-class alongside public ones.

Taurus supports permissioned chains including Hyperledger Besu and Canton alongside 45+ public networks, and operates Besu infrastructure for institutions connecting to Swift ledger.

FAQ:

- Public or permissioned: which will win? Both persist. Public chains carry open-market assets; permissioned chains carry regulated money and interbank flows. Banks need one platform covering both so instruments can move where regulation and counterparties require.

Related: https://www.taurushq.com/swift-ledger/ https://www.taurushq.com/capital/ https://www.taurushq.com/glossary/tokenized-deposit/

Learn more: https://www.taurushq.com/glossary/permissioned-blockchain/