-
Notifications
You must be signed in to change notification settings - Fork 1
#86_running_blockchain_network
AhmadBAmzah edited this page Oct 10, 2019
·
8 revisions
Paul Sarda - 11/04/2019
- How to start Multichain nodes
- join Multichain network
- 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
- https://www.Multichain.com/download-install/
- 512MB RAM
- 1GB Disk space
- Connect to your nectar node
- Copy the bash script located in the repo named
InstallMulitchain.shonto the server - Run script
- Create Chain
multichain-util create testChain - 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.
- Run this command
multichain-cli testChain
Notes:
- You will Have to open the port on nectar
- When you created your network you should see a line like this
multichaind testChain@192.168.0.1:25565 - 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
- 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 - Run the
multichaind testChain@192.168.0.1:25565command again on the connecting node - Now on both nodes run
getpeerinfoyou should see two entires for both nodes
- Spike report on nectar ports
- Spike report on Multichain permissions
- Spike report using multichian API calls
About
Documents
-
AWS
-
Other
-
REST
-
Nectar
-
Rancher
-
ASP.NET
-
Data
-
Blockchains
-
Processes