6) Configure Bootnode Instance

Bootnode
1)  Connect to the Bootnode instance and replace the spec.json file at /home/bootnode/spec.json with the spec.json from the MoC instance.
2) Replace the bootnodes.txt file at /home/bootnode/bootnodes.txt with the bootnodes.txt file from the MoC instance.
3) Open /home/bootnode/node.toml in your favorite editor and add "parity" to the apis option in [rpc] section so that it would look like apis = ["web3","eth","net","parity"]
4) Restart Parity: 
1
sudo systemctl restart poa-parity && sleep 10 && sudo systemctl restart poa-netstats
Copied!
5) Retrieve bootnode's enode with this command:
1
curl --data '{"method":"parity_enode","params":[],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST localhost:8545
Copied!
6) Add the enode from json result to bootnodes.txt file. You will now have 2 entries, one for the MoC and a second for the bootnode. Save the file.
7) Open /home/bootnode/node.toml in your favorite editor and remove "parity" from the apis option in [rpc] section.
8) Restart Parity & Netstats: 
1
sudo systemctl restart poa-parity && sleep 10 && sudo systemctl restart poa-netstats
Copied!
9) Log back into MoC node and replace the /home/moc/bootnodes.txt file with the bootnodes.txt file from the Bootnode. It should contain both enode entries. Save the file and restart MoC node / Netstats with:
1
sudo systemctl restart poa-parity && sleep 10 && sudo systemctl restart poa-netstats
Copied!
10) Go to the Netstat dashboard and make sure MoC node and Bootnode are shown and display the same hashes for each block.
​Next: Call Contract Methods 
​

5) Reconfigure MoC Instance

7) Call Contract Methods using MyCrypto

Last modified 1yr ago

Export as PDF

Copy link