Besu for private (permissioned) networks

You can use Besu to develop enterprise applications requiring secure, high-performance transaction processing in a private network.

A private (also known as permissioned) network is a network not connected to Ethereum Mainnet or an Ethereum testnet. Private networks typically use a different chain ID and proof of authority (PoA) consensus (QBFT, IBFT 2.0, or Clique).

You can also create a local development network using proof of work (PoW) (Deprecated).

Besu supports enterprise features including privacy (Deprecated) and permissioning.

Get started with the Developer Quickstart to rapidly generate local blockchain networks.

If you have any questions about Besu for private (permissioned) networks, ask on the besu-enterprise channel on Discord.

Architecture

The following diagram outlines the high-level architecture of Besu for private networks.