Node Setup

This section covers the detailed process for setting up the nodes in your private blockchain network, including system requirements, installation of Go, and the step-by-step guide for configuring and running both the Boot Node and Sub-Node(s). It also includes instructions for setting up the genesis file and automating the node startup scripts.

System Requirements

Before starting the node setup, ensure that your machines meet the following system requirements:

Operating System: Linux (Ubuntu 18.04 or higher is recommended)
CPU: Minimum 2 cores (4 cores or more recommended for production environments)
Memory: 8GB RAM (16GB or more for higher performance)
Disk Space: 100GB (SSD preferred)
Network: Reliable internet connection (static IP recommended for Boot Node)
Software:
- Go (latest stable version)
- Git
- Build essentials (gcc, make, etc.)

Go Version and Installation

The blockchain runs on a Go-Quorum fork, so you need to install a specific version of Go to build and run the nodes. Here’s how to install Go:

Download the Required Version:
- For this setup, we recommend using Go version 1.21.13 or the latest stable version. You can download it using the following command:
  bashCopy codewget https://golang.org/dl/go1.21.13.linux-amd64.tar.gz

Install Go:

Extract the Go archive and install it:

bashCopy codesudo tar -C /usr/local -xzf go1.21.13.linux-amd64.tar.gz

Set Up Go Environment:
- Add Go binaries to your system's PATH by adding the following lines to your ~/.profile:
  bashCopy codeexport PATH=$PATH:/usr/local/go/bin
- Reload your profile to apply the changes:
  bashCopy codesource ~/.profile
Verify Go Installation:
- To verify that Go is installed correctly, run:
  bashCopy codego version
- You should see the installed version of Go (go version go1.21.13 linux/amd64).

Step-by-Step Guide to Fork and Run Nodes

1. Clone the Go-Quorum Fork

Once Go is installed, you can clone the repository for your customized Go-Quorum fork:

bashCopy codegit clone https://github.com/your-org/go-quorum-fork.git
cd go-quorum-fork

2. Build the Blockchain Nodes

Navigate to the root directory of the cloned repository and build the project using Go:
```
bashCopy codemake all
```

3. Configure the Genesis File

The genesis.json file defines the initial state of the blockchain. It specifies the chain ID, difficulty level, gas limits, pre-allocated accounts, and consensus settings. Below is a sample genesis.json file for your private blockchain:

jsonCopy code{
  "alloc": {
    "0x5cca92b777B792123d538b3954fAB7852C1cf8c1": {
      "balance": "1000000000000000000000000000"
    },
    "0x77aE6E9b57edBF0FF5A3b22158f2C89470326a5A": {
      "balance": "1000000000000000000000000000"
    }
  },
  "coinbase": "0x0000000000000000000000000000000000000000",
  "config": {
    "chainId": 33333,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip155Block": 0,
    "eip158Block": 0,
    "byzantiumBlock": 0,
    "constantinopleBlock": 0,
    "isQuorum": true,
    "maxCodeSizeConfig": [
      { "block": 0, "size": 35 }
    ],
    "raft": {}
  },
  "difficulty": "0x0",
  "gasLimit": "0xE0000000",
  "extraData": "",
  "mixhash": "0x00000000000000000000000000000000000000647572616c65787365646c6578",
  "nonce": "0x0",
  "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "timestamp": "0x00"
}

Save the genesis.json file in the main directory.

Boot Node Configuration

The Boot Node is responsible for handling node discovery and coordination among other nodes.

1. Initialize the Boot Node:

After setting up the genesis file, initialize the boot node with the following command:
```
bashCopy code./build/bin/geth --datadir node1 init genesis.json
```

2. Create the Static-Nodes File:

You need to create a static-nodes.json file to link the Boot Node and Sub-Node(s). This file should be placed inside the node1 directory and contain the enode address of the Boot Node, formatted as follows:
```
jsonCopy code[
  "enode://[BootNodeEnodeAddress]@34.173.46.64:30303?discport=0&raftport=50400"
]
```

3. Create the Boot Node Start Script:

Create a shell script (startBootNode.sh) with the following content to start the Boot Node:

bashCopy code#!/bin/bash
PRIVATE_CONFIG=ignore ./build/bin/geth \
  --datadir node1 \
  --nodiscover \
  --verbosity 5 \
  --networkid 33333 \
  --raft \
  --raftport 50400 \
  --port 30303 \
  --nat extip:34.173.46.64 \
  --http \
  --http.addr "0.0.0.0" \
  --http.port 8545 \
  --http.corsdomain "*" \
  --http.api "admin,eth,net,web3,quorum,raft" \
  --ws \
  --ws.addr "0.0.0.0" \
  --ws.port 8546 \
  --ws.origins "*" \
  --ws.api "admin,eth,net,web3,quorum,raft" \
  --emitcheckpoints \
  --ipcpath node1/geth.ipc \
  >> node1.log 2>&1 &

4. Run the Boot Node:

Make the script executable and run it to start the Boot Node:
```
bashCopy codechmod +x startBootNode.sh
./startBootNode.sh
```

5. Verify the Boot Node:

To check if the boot node is running, you can list the IPC file:
```
bashCopy codels node1/geth.ipc
```

Attach to the Geth console and check the node info:

bashCopy code./build/bin/geth attach node1/geth.ipc
admin.nodeInfo

Sub-Node Configuration

Sub-nodes are validator nodes that join the Raft consensus and participate in transaction validation and block creation.

1. Initialize the Sub-Node:

Repeat the node initialization steps for the sub-node:

bashCopy code./build/bin/geth --datadir node2 init genesis.json

2. Create the Sub-Node Start Script:

Create a script (startSubNode.sh) to start the sub-node, which includes the boot node’s enode address:

bashCopy code#!/bin/bash
PRIVATE_CONFIG=ignore ./build/bin/geth \
  --datadir node2 \
  --nodiscover \
  --verbosity 5 \
  --networkid 33333 \
  --raft \
  --raftjoinexisting 2 \
  --raftport 50401 \
  --port 30304 \
  --nat extip:34.170.1.72 \
  --bootnodes enode://[BootNodeEnodeAddress]@34.173.46.64:30303 \
  --http \
  --http.addr "0.0.0.0" \
  --http.port 8547 \
  --http.corsdomain "*" \
  --http.api "admin,eth,net,web3,quorum,raft" \
  --ws \
  --ws.addr "0.0.0.0" \
  --ws.port 8548 \
  --ws.origins "*" \
  --ws.api "admin,eth,net,web3,quorum,raft" \
  --emitcheckpoints \
  --ipcpath node2/geth.ipc \
  >> node2.log 2>&1 &

3. Run the Sub-Node:

Make the script executable and run it to start the Sub-Node:
```
bashCopy codechmod +x startSubNode.sh
./startSubNode.sh
```

4. Add the Sub-Node to the Raft Cluster:

Attach to the Boot Node console and add the Sub-Node to the Raft cluster:

bashCopy code./build/bin/geth attach node1/geth.ipc
raft.addPeer("enode://[SubNodeEnodeAddress]@34.170.1.72:30304?discport=0&raftport=50401")

With the nodes configured and scripts automated, the blockchain network is now ready to process transactions and participate in the Raft consensus. The next section will focus on interacting with the blockchain using APIs, RPC, and WebSocket.

PreviousNetwork Architecture NextBlockchain Interaction

Last updated 3 months ago

jsonCopy code{ "alloc": { "0x5cca92b777B792123d538b3954fAB7852C1cf8c1": { "balance": "1000000000000000000000000000" }, "0x77aE6E9b57edBF0FF5A3b22158f2C89470326a5A": { "balance": "1000000000000000000000000000" } }, "coinbase": "0x0000000000000000000000000000000000000000", "config": { "chainId": 33333, "homesteadBlock": 0, "eip150Block": 0, "eip155Block": 0, "eip158Block": 0, "byzantiumBlock": 0, "constantinopleBlock": 0, "isQuorum": true, "maxCodeSizeConfig": [ { "block": 0, "size": 35 } ], "raft": {} }, "difficulty": "0x0", "gasLimit": "0xE0000000", "extraData": "", "mixhash": "0x00000000000000000000000000000000000000647572616c65787365646c6578", "nonce": "0x0", "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000", "timestamp": "0x00" }

bashCopy code#!/bin/bash PRIVATE_CONFIG=ignore ./build/bin/geth \ --datadir node1 \ --nodiscover \ --verbosity 5 \ --networkid 33333 \ --raft \ --raftport 50400 \ --port 30303 \ --nat extip:34.173.46.64 \ --http \ --http.addr "0.0.0.0" \ --http.port 8545 \ --http.corsdomain "*" \ --http.api "admin,eth,net,web3,quorum,raft" \ --ws \ --ws.addr "0.0.0.0" \ --ws.port 8546 \ --ws.origins "*" \ --ws.api "admin,eth,net,web3,quorum,raft" \ --emitcheckpoints \ --ipcpath node1/geth.ipc \ >> node1.log 2>&1 &

bashCopy code#!/bin/bash PRIVATE_CONFIG=ignore ./build/bin/geth \ --datadir node2 \ --nodiscover \ --verbosity 5 \ --networkid 33333 \ --raft \ --raftjoinexisting 2 \ --raftport 50401 \ --port 30304 \ --nat extip:34.170.1.72 \ --bootnodes enode://[BootNodeEnodeAddress]@34.173.46.64:30303 \ --http \ --http.addr "0.0.0.0" \ --http.port 8547 \ --http.corsdomain "*" \ --http.api "admin,eth,net,web3,quorum,raft" \ --ws \ --ws.addr "0.0.0.0" \ --ws.port 8548 \ --ws.origins "*" \ --ws.api "admin,eth,net,web3,quorum,raft" \ --emitcheckpoints \ --ipcpath node2/geth.ipc \ >> node2.log 2>&1 &