Pre-General Availability: 2026-03-13

Deployment Model

A Besu network consists of multiple Besu nodes connected via peer-to-peer (P2P) networking. Nodes run transactions in the Ethereum Virtual Machine (EVM), persist the blockchain ledger and state, and expose client access through RPC endpoints.

A Besu network includes the following node types.
  • Validator nodes: Consensus-participating nodes that propose and validate blocks. Validator nodes must stay current with the canonical chain state to sign and vote correctly.
  • Boot nodes: Nodes that support peer discovery so that other nodes can find and join the network.
  • RPC nodes: Nodes that serve application traffic via JSON-RPC.
  • Archive nodes: Nodes that retain all historical blockchain data and state (no pruning) to support deep queries, audits, and analytics. Archive nodes are not supported in this release of Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu.

Founder/Participant Model

Oracle Blockchain Platform Enterprise Edition for Hyperledger Besu supports two instance types: founder and participant.

A founder instance has the following capabilities.
  • Creates and starts the private, permissioned Besu network.
  • Operates in a single organization with independent authentication and administrative controls provided by Oracle Blockchain Platform Enterprise Edition.
  • Establishes the initial network configuration and provides the baseline network endpoints used to add participants.

Other organizations can create participant instances and join the founder's network. The participant instance contains RPC nodes that connect to and join the founder's Besu network, so that the participant organization can submit transactions and query ledger data using standard Ethereum and RPC APIs. The participant instance operates in its own Oracle Blockchain Platform Enterprise Edition environment, and can be located in the same OCI tenancy or in a different OCI tenancy. In the current release, participant instances use RPC nodes to interact with the founder instance.

The following steps describe the basic operations you complete to work in the founder/participant model.
  1. Create the founder network. The founding organization creates a founder Besu instance in Oracle Blockchain Platform Enterprise Edition, which initializes the private permissioned network.
  2. Export genesis and node information from the founder. In the instance list in OCI, use the Actions menu to export the genesis and node information in .zip format.
  3. Create a participant instance. The participating organization creates a participant Besu instance in Oracle Blockchain Platform Enterprise Edition by using the exported .zip file.
  4. Check connectivity and synchronization between the instances. After both instances are running and network connectivity is in place between nodes, the RPC nodes connect and synchronize the ledger. After synchronization, transactions and blockchain data are visible in the participant's service console.
  5. Independently administer the instances. Both organizations submit transactions to the same underlying ledger and interact with the same smart contracts, but each retains independent administrative control, which is enforced through the authentication and authorization implemented in their respective blockchain platform manager environments.