Hyperledger Besu is an open-source, Java-based Ethereum client built for both public mainnet participation and private enterprise networks. It's the only Ethereum execution client designed from the ground up for enterprise use -- supporting permissioning, privacy through Tessera, and multiple consensus mechanisms including QBFT, IBFT 2.0, and Clique.
Besu currently runs 9.5-16% of Ethereum mainnet nodes, making it the third-largest execution client behind Geth and Nethermind (clientdiversity.org, Q1 2026). On the enterprise side, it powers Nigeria's eNaira CBDC and the mBridge cross-border payment project connecting Hong Kong, Thailand, China, and the UAE (Atlantic Council CBDC Tracker, 2025).
I've spent six years building blockchain infrastructure tooling, including the Bevel Operator Fabric under the Hyperledger Foundation, and I've deployed dozens of Besu networks in production. This guide covers everything you need to evaluate Besu for your next project -- architecture, consensus, privacy, deployment, and real-world use cases -- with current 2025-2026 data that no other guide provides.
TL;DR: Hyperledger Besu is an enterprise-grade Ethereum client running 9.5-16% of mainnet nodes, with QBFT consensus handling ~1,000 TPS for permissioned networks. It powers CBDCs in Nigeria and the UAE, shipped 15 releases and 811 commits in 2025, and can be deployed in under 5 minutes with managed tooling vs. days of manual configuration (LF Decentralized Trust, 2026).
The global blockchain market reached $31.18 billion in 2025 and is projected to hit $47.96 billion in 2026, with private blockchains holding 42.47% of the market (Fortune Business Insights, 2026). Besu sits at the center of this growth -- bridging the gap between Ethereum's public ecosystem and enterprise requirements.
Besu started life as "Pantheon," built by Pegasys (a Consensys engineering team) in 2018. It joined the Hyperledger project family in 2019, becoming the first public blockchain client in an ecosystem previously dominated by permissioned-only frameworks like Fabric. That dual identity -- public mainnet client and enterprise platform -- is what makes Besu unique.
In 2025 alone, Besu shipped 3 hard forks (Pectra, Fusaka, and BPO1), 15 releases, and 811 commits. The block gas limit doubled from 30 million to 60 million, with a 2026 target of 70 million (LF Decentralized Trust, 2026). That's not a dormant project. That's one of the most actively developed Ethereum clients in existence.
Why this matters for enterprise teams: When you build on Besu, you're building on the same client that processes real transactions on Ethereum mainnet. That means battle-tested networking, storage, and execution -- not a theoretical framework that only runs in test environments.
Besu holds 9.5-16% of Ethereum's execution layer client share, ranking third behind Geth (41-50%) and Nethermind (25-38%) (clientdiversity.org, Q1 2026). But raw market share doesn't tell the whole story. What sets Besu apart is its dual-mode architecture: a single codebase that runs on both public mainnet and private permissioned networks.
Every Solidity smart contract, every Ethereum tool -- MetaMask, Hardhat, Foundry, Web3.js, ethers.js -- works with Besu out of the box. You don't need a separate SDK. You don't need to learn a new programming language. If your developers know Ethereum, they know Besu.
This is Besu's biggest advantage over Hyperledger Fabric, which requires Go, Java, or JavaScript chaincode and custom SDKs. With Besu, your existing Ethereum toolchain transfers directly.
QBFT (Quorum Byzantine Fault Tolerant) is the recommended consensus protocol for all new permissioned Besu deployments, handling approximately 1,000 TPS in enterprise configurations (LF Decentralized Trust, 2025). It replaced IBFT 2.0 as the default after the Enterprise Ethereum Alliance finalized the QBFT specification in 2023.
The protocol works on a simple guarantee: a network with 3f+1 validators tolerates up to f Byzantine (malicious or faulty) validators. So a 4-validator network tolerates 1 failure, a 7-validator network tolerates 2, and a 10-validator network tolerates 3.
What makes QBFT suitable for enterprise use:
Immediate finality: Once a block is committed, it's final. No reorgs. Non-negotiable for financial transactions.
Known validators: Every block producer is identified and accountable -- unlike proof-of-work or public proof-of-stake.
Deterministic block times: Configurable block periods (typically 2-5 seconds) with consistent throughput.
Dynamic validator management: Add or remove validators via smart contract votes without network downtime.
The round-change mechanism is QBFT's key improvement over IBFT 2.0. When the current block proposer fails, QBFT recovers faster and more reliably, reducing the risk of network stalls during validator outages.
For a deep technical walkthrough of genesis configuration, validator management, and performance tuning, see our QBFT consensus guide.
Financial services account for 41% of blockchain revenue, with payments driving 42% of application revenues (Fortune Business Insights, 2026). Besu captures a disproportionate share of financial use cases because of its EVM compatibility and enterprise permissioning. Here are the use cases where Besu has real production deployments -- not just whitepapers.
137 countries representing 98% of global GDP are exploring CBDCs, with 49 active pilot projects worldwide (Atlantic Council CBDC Tracker, 2025). Besu is the blockchain platform behind several of the most advanced:
Nigeria's eNaira: The first African CBDC, launched on Hyperledger Besu in October 2021. Still operational and processing retail payments.
mBridge: A cross-border CBDC project connecting Hong Kong, Thailand, China, and the UAE, built on Besu. The UAE's Digital Dirham pilot launched in November 2025.
Indonesia's Digital Rupiah: Bank Indonesia has been testing Besu as one of the underlying platforms.
Why do central banks choose Besu? Three reasons: permissioning (they control who participates), privacy (Tessera handles confidential transactions), and Ethereum compatibility (massive developer ecosystem for building applications on top).
Besu's full ERC standard support makes it the natural fit for tokenizing real-world assets -- securities, real estate, commodities, and carbon credits. ERC-1400 (security tokens) and ERC-3643 (regulated tokens with identity verification) run natively on Besu's EVM.
Supply chain remains one of the highest-ROI blockchain use cases. Besu's permissioned networks let supply chain consortiums control participant access while Tessera's privacy groups keep competitive data confidential between specific trading partners.
Enterprise DeFi -- lending protocols, liquidity pools, and decentralized exchanges on permissioned infrastructure -- is an emerging category. Because Besu runs the same EVM as public Ethereum, teams can fork DeFi protocols (Uniswap, Aave, Compound) and deploy them on private Besu networks with regulatory controls.
This is the most common question enterprise teams ask. Fabric processes roughly 3,000 TPS through channel-based isolation, while Besu handles approximately 1,000 TPS with QBFT -- but raw throughput isn't the deciding factor. The right choice depends on your programming model, privacy requirements, and team expertise.
Criteria
Hyperledger Besu
Hyperledger Fabric
Smart contracts
Solidity (EVM)
Go, Java, JavaScript
Developer ecosystem
Massive (all Ethereum tools)
Smaller, specialized
Consensus
QBFT, IBFT 2.0, Clique, PoS
Raft, Kafka, SmartBFT
Throughput
~1,000 TPS (QBFT)
~3,000 TPS (channels)
Privacy model
Tessera (encrypted off-chain)
Private data collections
Token standards
Native (ERC-20, 721, 1155, 1400)
Requires custom chaincode
Public network
Yes (Ethereum mainnet)
No
Permissioning
Node + account level
MSP + channel ACLs
Choose Besu when: You need EVM compatibility, your team knows Solidity, you want native token standards, or you need a bridge between private and public Ethereum.
Choose Fabric when: You need channel-based data isolation between consortium members, higher throughput is critical, or your use case requires complex multi-party endorsement policies.
Deploying a production Besu network manually involves configuring genesis files, generating validator keys, setting up P2P networking, enabling JSON-RPC APIs, and configuring monitoring. For most teams, this takes 40-200+ hours depending on Kubernetes experience.
There are faster paths. Here's what the options look like in 2026:
ChainLaunch deploys a 4-node QBFT Besu network in under 5 minutes. It handles validator key generation, genesis block creation, node networking, and monitoring setup automatically. There's a free self-hosted tier and managed cloud options starting at $99/month.
# Install ChainLaunchcurl -sSL https://get.chainlaunch.dev | bash# Start ChainLaunchchainlaunch serve# Create a 4-node Besu network via the web UI or API# Validators, genesis, and networking configured automatically
Production teams running Kubernetes can use Helm charts to deploy Besu. This is the right approach for organizations that already have Kubernetes infrastructure and want Besu to fit into their existing deployment pipeline.
eth/70 protocol support: Updated Ethereum wire protocol for better performance
Bonsai Archive production readiness: Full archival node support with Bonsai's storage-efficient trie structure
Glamsterdam hard fork: Next Ethereum mainnet upgrade, including ePBS (enshrined Proposer-Builder Separation) and Block Level Access Lists
For enterprise users, the most impactful changes are Bonsai Archive (enabling full historical queries on private networks with lower storage costs) and the continued gas limit increases (directly improving throughput for high-volume permissioned networks).
Ethereum's security depends on no single client controlling a supermajority of nodes. If one client has a consensus bug, a diverse validator set limits the blast radius. Besu's 9.5-16% market share is a direct contribution to network resilience (clientdiversity.org, Q1 2026).
For enterprise teams, this matters beyond altruism. Running a minority client means:
Lower correlation risk: If Geth has a critical bug, your Besu nodes keep producing blocks normally
Foundation support: The LF Decentralized Trust (formerly Hyperledger Foundation) actively funds Besu development -- 811 commits and 15 releases in 2025 alone
Enterprise governance: Besu's development is governed by an open-source foundation, not a single company
The Ethereum Foundation has consistently called for client diversity improvements. Besu is the primary enterprise-grade alternative to Geth, and its market share has been growing as staking operators diversify their infrastructure.
The fastest path from zero to a running Besu network depends on your goals:
Just exploring? Deploy a 4-node QBFT network in under 5 minutes with ChainLaunch's free self-hosted tier. No Kubernetes required. One command gets you validators, genesis, networking, and monitoring.
Building a PoC? Follow our Besu supply chain PoC tutorial -- it walks through deploying a network, writing a Solidity contract, and testing the full lifecycle in under 10 minutes.
Evaluating deployment tools? Read our 5 best Besu deployment tools ranking for a hands-on comparison of ChainLaunch, Kubernetes, Kaleido, Chainstack, and AWS Managed Blockchain.
Need privacy features? Our Besu + Tessera privacy guide covers enclave architecture, privacy groups, and multi-tenancy configuration.
Deep-diving into consensus? The QBFT consensus technical guide covers genesis configuration, validator management, round-change mechanics, and performance tuning.
Yes. Besu is open-source under the Apache 2.0 license -- free for commercial and non-commercial use. The software itself has no licensing fees. Your costs are infrastructure (servers to run nodes) and engineering time for deployment and operations. Managed platforms like ChainLaunch offer free self-hosted tiers and paid managed cloud options starting at $99/month.
Yes. Besu is a fully compliant Ethereum execution client. It runs on Ethereum mainnet, testnets (Hoodi, Sepolia, Ephemery), and private networks. It currently powers 9.5-16% of Ethereum mainnet nodes (clientdiversity.org, Q1 2026), making it the third-largest execution client.
Besu uses Tessera as a private transaction manager. Tessera encrypts transaction payloads off-chain and only shares them with specified participants via privacy groups. The public Besu chain records a privacy marker transaction (a hash reference), while the actual transaction data remains encrypted and accessible only to authorized parties. See our Tessera privacy guide for setup details.
Solidity -- the same language used on public Ethereum. Any Solidity contract that runs on Ethereum mainnet runs on a private Besu network without modification. You can also use Vyper or any language that compiles to EVM bytecode. Development tools like Hardhat, Foundry, Remix, and Truffle all work natively with Besu.
Both are BFT consensus protocols with immediate finality, but QBFT improves on IBFT 2.0's round-change mechanism -- recovering faster when a block proposer fails. QBFT also fully implements the Enterprise Ethereum Alliance's QBFT specification, while IBFT 2.0 predates the standard. For new deployments, always use QBFT. See our QBFT technical guide for the full breakdown.
Besu is production-grade: 9.5-16% of Ethereum mainnet, 811 commits in 2025, 3 hard forks shipped
Enterprise features built in: Permissioning, Tessera privacy, QBFT consensus with immediate finality
Real-world adoption: Powers Nigeria's eNaira CBDC and the mBridge cross-border payment project
Full EVM compatibility: Every Ethereum tool and Solidity contract works out of the box
Active development: 2026 roadmap includes 70M gas target, discv5, Bonsai Archive, and Glamsterdam hard fork
Multiple deployment paths: From 5-minute managed deploys to full Kubernetes control
The blockchain market is projected to reach $47.96 billion in 2026 (Fortune Business Insights, 2026), with private blockchains holding 42% of the market. Besu is the Ethereum client purpose-built for this segment. Whether you're exploring a proof of concept or scaling to production, the tooling and ecosystem are mature enough to support real workloads.
David Viejo is the founder of ChainLaunch and a Hyperledger Foundation contributor. He created the Bevel Operator Fabric project and has been building blockchain infrastructure tooling since 2020.
Deploy a Besu network in minutes
Skip the manual setup. ChainLaunch handles validator keys, genesis, and QBFT consensus — launch in the cloud or self-host for free.
