Client and network upgrades on permissioned Besu networks: keeping pace with calendar releases and coordinating protocol milestones across operators.
Planning network upgrades across consortium operators: reviewing the EIPs in a protocol upgrade, agreeing a milestone block, distributing genesis changes, restarting every node in time, and the change records regulators expect.
Moving permissioned Besu nodes onto the 26.x calendar releases: the JDK 25 requirement, Clique removal, one-way Bonsai database upgrades that make pre-upgrade backups essential, rolling validator restarts and staging tests.
Preparing hosts, images and pipelines for Besu's JDK 25 requirement since 26.6.0, including custom images, JVM options and plugin builds that must follow the runtime.
Why the Bonsai database upgrade in Besu 26.10.0 makes rollback depend on a backup, the revert-code-format subcommand, and protecting against accidental downgrades.
A rolling upgrade plan for private Besu networks on Linux, Docker or Kubernetes: release note review, upgrade order, keeping two-thirds of validators online and checking peering between nodes.
Managing plugin risk on Besu upgrades: the plugin API reorganization into feature modules, deprecated services such as BesuEvents, and pinning plugins such as the HSM plugin to tested Besu versions.
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.