Consensus and configuration migrations the Besu docs document for running permissioned networks without rebuilding the chain.
Running the documented live cutover from IBFT 2.0 to QBFT on a permissioned Besu network: choosing the migration block, genesis changes every operator must apply, rolling validator restarts without losing quorum, avoiding forks and verifying the switch.
Moving off GoQuorum now that its repository is archived: what QBFT interoperability allows, why Besu transitions do not work in mixed-client networks, and private transaction and chart dependencies to replace.
Options for networks that relied on Tessera privacy groups once Besu removed Tessera and the EEA and PRIV APIs: staying on older releases versus re-platforming private workflows on Paladin.
What to do when a network used smart-contract permissioning that Besu removed in 25.6.0: moving rules to local allowlists, writing a permissioning plugin, and keeping consortium-wide rules consistent.
Where a Clique-based private network stands after Besu 26.4.0: why upgraded nodes cannot start on pure Clique, the absence of a documented in-place path, and planning a move to a QBFT network.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.