Besu node features that matter for operating a permissioned network in regulated infrastructure: transport security for APIs, cryptographic curve choice and backup and restore of node data.
Encrypting and authenticating application access to Besu nodes with mutual TLS: PKCS12 keystores, the known clients file with certificate fingerprints, CA-signed clients, cipher suite and protocol settings, WebSocket TLS, and Web3Signer connections.
Configuring a private Besu network to use secp256r1 instead of Ethereum's default secp256k1: the genesis ecCurve setting, why every node must match, early access status, and how curve choice interacts with hardware key storage plans.
Backing up what a Besu node cannot recover from peers alone: the genesis file under source control, node keys, configuration and the data directory on a separate volume, restore steps after corruption, and testing restores as part of resilience evidence.
Running a private Besu network with a zero gas price: block gas limit and contract size settings, the per-transaction gas cap, minimum gas price on every node, the balance check and zero base fee after London.
Choosing a world state storage format for private Besu nodes: Bonsai as the default, Forest for archive needs and the enterprise profile, historical query limits and what each means for disk and memory.
What the ENTERPRISE (PRIVATE) configuration profile changes for private network operators, the sync and storage settings it expects, and how profile values interact with your own configuration file.
Picking the transaction pool implementation for a private network: why Besu recommends the sequenced pool for private chains, how the layered default behaves, and the options that change between them.
How Besu's optimistic parallel execution works, the Bonsai requirement, how conflicts are detected and replayed, and when enabling it helps a busy private network.
Using Besu's GraphQL endpoint to read blocks, receipts and sync status in fewer calls than JSON-RPC, its default port, its limits on pending data and how to expose it safely.
Running Besu peers over IPv6 or IPv4 and IPv6 together: discovery v4 and v5, the parallel P2P options and ports, and settings for enterprise networks moving to IPv6.
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.