Node
that uses a custom genesis block to join a private Proof of Authority network using ibft2 consensus configuration in the genesis block.client: besu
, enabling JSON-RPC server rpc: true
so we can query number of peers later in this tutorial, and we're loading the node private key from Kubernetes secretd called besu-ibft2-nodekey
.0xbAa5f05af4A67A467cEcA89085f162aFb4206Aaa
that's corresponding to the node private key is in the initial block validators.4444
as network and chain identifier, and we start the chain with 3 validators as defined by spec.genesis.ibft2.validators
.0x
, and must be stored in secret data field called key
.besu-ibft2-node
and will create all the necessary pods, persistent volumes, services, configmaps, and secrets.Node
using:client: geth
, starting the PoA consensus engine miner: true
, setting the second address in the genesis validators list spec.genesis.ibft2.validators
as the coinbase coinbase: "0xc1381ED43B327e3C7A1ADb21285f1e9cB82Bc00d"
, and loading the validator account private key and password from kubernetes secrets privateKeySecretName: ...
and passwordSecretName: ...
. We're connecting to the first node using staticNodes
option which accepts Node
name or enode url.staticNodes
accept Node
name or enode URL. Node
name has the format of name.namespace
, namespace is optional if Node
is in the same namespace. If the node doesn't exist, or is not up and running yet, Kotal will not raise an error.geth-ibft2-node
and will create all the necessary pods, persistent volumes, services, configmaps, and secrets.Node
s using:net_peerCount
net_peerCount
JSON-RPC methodspec.genesis.ibft2.validators
. Nethermind client is similar to geth, you will import validator account private key and password from kubernetes secrets, and use the same genesis as the other nodes.Node
controller.