Skip to content

#86_running_blockchain_network

AhmadBAmzah edited this page Oct 10, 2019 · 8 revisions

Spike #86 - Running Blockchain Network

Paul Sarda - 11/04/2019

Goals / Deliverables

  • How to start Multichain nodes
  • join Multichain network

Technologies, Tools and Resources Used

Tasks Undertaken

  • Referred to #77
  • Referred to multichain getting started guide
  • Started single node
  • Created script to install Multichain from a blank system
  • Ran script on new instances and connected them to network

What we found out:

System requirements

Installing Multichain on nectar instance

  1. Connect to your nectar node
  2. Copy the bash script located in the repo named InstallMulitchain.sh onto the server
  3. Run script

Creating / Starting a Multichain network

  1. Create Chain multichain-util create testChain
  2. Initialise / Start existing Chain multichaind testChain -daemon

You should see somthing like the following


MultiChain 2.0 Daemon (Community Edition, latest protocol 20009)

Starting up node...

Looking for genesis block...
Genesis block found

Other nodes can connect to this node using:
multichaind testChain@192.168.0.1:25565

This host has multiple IP addresses, so from some networks:
multichaind testChain@172.17.0.1:25564

Listening for API requests on port 25564 (local only - see rpcallowip setting)

Node ready.

Getting to interactive mode

  1. Run this command multichain-cli testChain

Connecting to an existing Multichain network

Notes:

  1. When you created your network you should see a line like this multichaind testChain@192.168.0.1:25565
  2. Copy that command and paste it onto the joining node you should see the below output
MultiChain 2.0 Daemon (Community Edition, latest protocol 20009)

Retrieving blockchain parameters from the seed node 43.240.98.100:6289 ...
Blockchain successfully initialized.

Please ask blockchain admin or user having activate permission to let you connect and/or transact:
multichain-cli testChain grant 11111111111111111111111111111111111111 connect
multichain-cli testChain grant 11111111111111111111111111111111111111 connect,send,receive
  1. The above even gave us suggestions on permissions to apply to given node permissions will be a separate spike so just copy multichain-cli testChain grant 11111111111111111111111111111111111111 connect
  2. Run the multichaind testChain@192.168.0.1:25565 command again on the connecting node
  3. Now on both nodes run getpeerinfo you should see two entires for both nodes

Recommendations:

  • Spike report on nectar ports
  • Spike report on Multichain permissions
  • Spike report using multichian API calls

Clone this wiki locally