Inside Hyperledger Besu: Private QBFT Chains, Plugins, Security, and Why Enterprises Choose It

From Zanyuk Morning Digest · 52:34

Show by Alexey Zanyuk

Read the companion post: https://zanyuk.com/post/hyperledger-besu/ An engineer's tour of a four-company permissioned Ethereum network on Hyperledger Besu. Why Besu became the enterprise default: Apache 2.0, the JVM, LF Decentralized Trust governance, mainnet-grade EVM, QBFT. What changed recently: Clique, on-chain permissioning and Tessera privacy are gone, GoQuorum is archived, and privacy moved to Paladin. The real alternatives, EVM and non-EVM, with honest trade-offs. Then the internals: following a transaction through QBFT and the EVM, storage slots versus event logs, embedded plugins for event capture and replay tracing, encryption at rest and what it cannot hide, peer transport versus mutual TLS, and header-preserving history pruning for a 124-day retention rule. It ends with whether one private chain can mix different EVM clients. Show notes and sources: - Besu releases and changelog: https://github.com/besu-eth/besu/releases - Besu 26.4.0 (repo move, Clique removed): https://github.com/besu-eth/besu/releases/tag/26.4.0 - Besu 25.6.0 (Tessera privacy and on-chain permissioning removed): https://github.com/hyperledger/besu/releases/tag/25.6.0 - Besu 25.7.0 (EEA/PRIV APIs removed, snap sync for BFT): https://github.com/hyperledger/besu/releases/tag/25.7.0 - Besu 24.12.0 (P2P TLS removed): https://github.com/hyperledger/besu/releases/tag/24.12.0 - LFDT 2026 mid-year Besu report: https://lf-decentralized-trust.github.io/governance/project-updates/2026/2026-MidYear-Besu/ - Besu consensus, QBFT and permissioning docs: https://docs.besu-eth.org/private-networks/how-to/configure/consensus/qbft , https://docs.besu-eth.org/private-networks/concepts/permissioning - Privacy with Paladin: https://docs.besu-eth.org/private-networks/concepts/privacy-with-paladin - Paladin becomes an LFDT project: https://www.lfdecentralizedtrust.org/blog/paladin-a-unified-programmable-privacy-framework-for-evm-becomes-newest-lf-decentralized-trust-project - GoQuorum (archived): https://github.com/ConsenSys/quorum - Geth v1.14.0 (Clique signing removed): https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0 - Erigon v3.5.0 (Clique removed): https://github.com/erigontech/erigon/releases/tag/v3.5.0 - Nethermind AuRa docs: https://github.com/NethermindEth/docs/blob/main/docs/validators/aura.md - EBSI node operators: https://ec.europa.eu/digital-building-blocks/sites/spaces/EBSI/pages/609583364/Node+Operators - Brazil's Drex platform shutdown (Exame): https://exame.com/future-of-money/banco-central-anuncia-desligamento-da-plataforma-do-drex-e-nova-infraestrutura/ - Avalanche permissioned L1s: https://build.avax.network/academy/permissioned-l1s/XX-poa-manager-deployment/03-deploy-poa-manager - Besu ChainDataPruner source: https://github.com/besu-eth/besu/blob/main/ethereum/core/src/main/java/org/hyperledger/besu/ethereum/chain/ChainDataPruner.java About 53 minutes. Voice: Rex. Chapters: 00:00 Intro 01:55 Why Besu won the enterprise, and what else is out there 13:31 The five layers of a Besu node 14:55 Following a transaction to a final block 18:31 Contract storage, traces, and event logs 21:27 The plugin framework 23:23 Example one: capturing every event 26:00 Example two: tracing every storage read and write 28:43 Encryption at rest, and what it cannot hide 32:21 Simplifying Besu for a private network 34:16 The network boundary 37:33 Deleting history after one hundred and twenty-four days 45:57 Can one private chain mix different EVM clients? 49:31 Putting it all together

More episodes of Zanyuk Morning Digest

More episodes

PodSearch is a free, independent podcast search engine. Read about PodSearch, the privacy policy or contact us.