Network Info

Canonical parameters and artifacts to run your own Umotu QBFT node and participate on-chain.

Exposure policy: On testnet, validator enodes may be published for convenience. On mainnet, only bootnodes/RPC sentries will be public; validators must run behind static/permissioned peer sets.

Chain Parameters

Consensus: QBFT (2s blocks). Slot mapping: 1 block = 1 slot.

Chain ID: —

Downloads

Run your node (Besu)

besu   --data-path=/var/lib/besu   --genesis-file=$(pwd)/docs/network/genesis.json   --rpc-http-enabled --rpc-http-host=0.0.0.0 --rpc-http-port=8545   --rpc-ws-enabled  --rpc-ws-host=0.0.0.0 --rpc-ws-port=8546   --rpc-http-api=ETH,NET,WEB3,QBFT --rpc-ws-api=ETH,NET,WEB3,QBFT   --host-allowlist=*   --sync-mode=FULL

Then validate:

RPC_URL=http://localhost:8080/rpc node ops/scripts/validate-rpc.mjs

Bootnodes, Static Peers & Permissioning

See docs/network/NETWORK-INFO.md for bootnodes. You can pin peers by placing a static-nodes.json in your data dir. For stricter peer control (e.g., validators), enable Besu node permissioning with a permissioned-nodes.json file.