Become a Master Node
Configure
Configure config.json file located in tool directory with data about master node such as account and server info
config.json path : inery-node/inery.setup/tools/config.json
open config.json file
nano tools/config.json
in MASTER_ACCOUNT object replace placeholders with right information
- AccountName : Inery master account name
- PublicKey : Master account public key
- PrivateKey : Master account private key
- IP : Server IP or DNS address
"MASTER_ACCOUNT":
{
"NAME": "AccountName",
"PUBLIC_KEY": "PublicKey",
"PRIVATE_KEY": "PrivateKey",
"PEER_ADDRESS": "IP:9010",
"HTTP_ADDRESS": "0.0.0.0:8888",
"HOST_ADDRESS": "0.0.0.0:9010"
}
You must use credential of existing Inery account
Name can have maximum of 12 characters ASCII lowercase a-z, 1-5 and dot character "." but dot can't be at the end of string
Save it and exit (ctrl + s), "Y", (ctrl + x)
Start Blockchain Protocol
ine.py script will start a blockchain protocol
run ine.py with options "--master"
./ine.py --master
Check everything is setup properly by executing command :
tail -f master.node/blockchain/nodine.log
You should be able to see block replay
Stake INR
In order to stake INR first you must have liquid INR on account
You must have staked 50.000 INR to approve account as a producer
stake inr by executing command :
cline system stake ACCOUNT_NAME "50000.000000 INR"
From this step on you must have your wallet active in order to sign transactions
Bind as Master
You will have to bind your account to master table by providing master account name and master permission (Public Key) and node IP or DNS
bind account to master table by executing command :
cline master bind ACCOUNT_NAME PUBLIC_KEY SERVER_IP
This will register your account as Master node, with that only step left is to approve your account
Approve Master
Approve command will activate your master to start producing blocks by putting master in some of the free stages and give him a chanse for producing everytime it gets his turn
Check latency of blocks you are receiving with tail -f master.node/blockchain/nodine.log
command
if the latency is higher than 500ms its not recommended to start master node, since it will probably miss his chanse to create block
execute command:
cline master approve ACCOUNT_NAME
If master fails to create blocks in 3 full cycles, it is automatecly droped from producing and must approve once again when he wants to return