Now we have all basic requirements ready to launch our validating nodes. In the first shell, run this command to launch the first validating node:

parity  --chain spec.json -d ./validator0 --force-sealing --engine-signer "0x831647ec69be4ca44ea4bd1b9909debfbaaef55c" --port 30300 --jsonrpc-port 8540 --ui-port 8180 --dapps-port 8080 --ws-port 8546 --jsonrpc-apis web3,eth,net,personal,parity,parity_set,traces,rpc,parity_accounts --password "node.pwds"

Here is how the preceding command works:

• --chain is used to specify the path of the specification file.
• -d is used to specify the data directory.
• --force-sealing ensures that blocks are produced even if there are no transactions.
• --engine-signer is used to specify the address using which the node will sign blocks, that is, the address of the validator. If malicious authorities are possible, then --force-sealing is advised; this will ensure that the correct chain is the longest. Make sure you change the address to the one you generated, that is, the first address generated on this shell.
• --password is used to specify the password file.

In the second shell, run this command to launch second validating node:

parity  --chain spec.json -d ./validator1 --force-sealing --engine-signer "0x12a6bda0d5f58538167b2efce5519e316863f9fd" --port 30301 --jsonrpc-port 8541 --ui-port 8181 --dapps-port 8081 --ws-port 8547 --jsonrpc-apis web3,eth,net,personal,parity,parity_set,traces,rpc,parity_accounts --password "/Users/narayanprusty/Desktop/node.pwds"  

Here, make sure you change the address to the one you generated that is, the address generated on this shell.