Start the node

you have to complete the following processes:

• you have modified the customSpec.json and inserted the new keys

• you have updated the new customSpec.json file onto your instance (via filezilla)

• you have checked that the customSpec.json file in your instance is the updated file

• you have converted the customSpec.json to a raw format

if you have completed the above, you can now proceed to start the node.

there are a few parts to this process:

1. you will start the node01 using the command.

./target/release/node-unitchain --base-path /tmp/node01 --chain ./customSpecRaw.json --port 30333 --rpc-port 9944 --validator --rpc-methods=Unsafe --name MyNode01 --rpc-cors all --rpc-external

1. take note of the BOOT NODE. it should look something like this:

2024-01-23 07:07:59 🏷 Local node identity is: 12D3KooWRtaQqWNEpBAbXy1kc7WVTHvvC6G1pNDgjdmByhSjLgc9

1. If the bootnode shows up, it means that your chain is active.

2. in your local machine, go to the polkadotjs website and check on your node

Polkadot/Substrate Portalpolkadot.js.org

you should see a screen like this:

you will notice that there is no finalized blocks or best blocks produced

After verifying that the node works, Stop the node by Ctrl-C

Insert the 1st set of key to keystore

Add keys to the keystore

AURA:

./target/release/node-unitchain key insert --base-path /tmp/node01
--chain customSpecRaw.json
--scheme Sr25519
--suri  PRIVATE KEY \
--key-type aura

GRANDPA

./target/release/node-unitchain key insert \
  --base-path /tmp/node01 \
  --chain customSpecRaw.json \
  --scheme Ed25519 \
  --suri PRIVATE KEY \
  --key-type gran

To verify that you have inserted the key correctly, use this command:

  ls /tmp/node01/chains/local_testnet/keystore

it will show the key inserted

When you see the keys have been inserted, you can now proceed to run Node 01 again but this time in the background. there will not be any blocks produced yet (because you need 2 nodes to produce blocks!)

nohup ./target/release/node-unitchain --base-path /tmp/node01 --chain ./customSpecRaw.json --port 30333 --rpc-port 9944 --validator --rpc-methods=Unsafe --name MyNode01 --rpc-cors all --rpc-external >/dev/null 2>&1 &

it will seem like nothing is happening but the node is running in the background. you can verify in polkadotjs.

Remember the bootnode that was created when you ran Node 01 ?

2024-01-23 07:07:59 🏷 Local node identity is: 12D3KooWRtaQqWNEpBAbXy1kc7WVTHvvC6G1pNDgjdmByhSjLgc9

you need that now to run Node 02.

this is the command and you need to insert the bootnode into the command for the Node 02

./target/release/node-unitchain --base-path /tmp/node02 --chain ./customSpecRaw.json --port 30334 --rpc-port 9946 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/BOOTNODE --validator --rpc-methods Unsafe --rpc-cors all --rpc-external --name MyNode02

./target/release/node-unitchain   --base-path /tmp/node02   --chain ./customSpecRaw.json   --port 30334   --rpc-port 9946   --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWNhnTwFNrxYxrXinR3YwSufq1Uqk5YzfjdAuUfnscsPUM      --validator   --rpc-methods Unsafe   --rpc-cors all   --rpc-external   --name MyNode02

when you run the command, you will notice that the node detected the boot node 01 but there are no blocks produced. (this is because the 2nd key has not been inserted to the keystore)

Congratulations! you have completed your trusted node setup!