SHARE
TWEET

Untitled

a guest Aug 19th, 2018 68 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. simplest and totally manual procedure to write inside config.json the encrypted passphrase, soon after fork, and then enable forging:
  2.  
  3. ## install jq:
  4. sudo apt-get install jq
  5.  
  6.  
  7. ## encrypt the passphrase:
  8. 1. install npm, n and lisk-commander (to encrypt your passphrase)
  9.  
  10.  
  11. curl -sL  https://deb.nodesource.com/setup_8.x | sudo -E bash -
  12. sudo apt-get install -y nodejs
  13. sudo npm install -g n
  14. sudo n 6.14.1
  15. sudo apt-get install git
  16. sudo npm install lisk-commander@v1.0.0-rc.0 -g
  17. ##then type
  18. lisk "encrypt passphrase --output-public-key"
  19.  
  20.  
  21.  ## then you will be prompted for
  22.   Please enter your secret passphrase: ****
  23.   Please re-enter your secret passphrase: ****
  24.   Please enter your password: ****
  25.   Please re-enter your password: ****
  26.  
  27. ##In the first step, type in your passphrase and then type in the password you want to use for encryption.
  28. ##Afterwards you will get an encryptedPassphrase, publickey key value pair.
  29. ## you will have a JSON object output like this example:
  30.  
  31. {"encryptedPassphrase":"salt=67a33e926e7f530f63e82d3b8747c26e&cipherText=fceaabc2&iv=917ea94def16180160d06eb5&tag=9c28fda8afbd963c65cd9befedceeb6c&version=1","publicKey":"f350cbaa65b438a90082555c57f6347b6ee10b35c0bd5995b4cecd0b291989d8"}
  32.  
  33. ### use this in all the following points when appropriate
  34.  
  35.  
  36.  
  37. 2. launch lisk hq fork script
  38.  
  39. cd $home
  40. rm lisk_bridge.sh
  41. wget https://raw.githubusercontent.com/LiskHQ/lisk-scripts/development/downloaded/lisk_bridge.sh
  42. screen bash lisk_bridge.sh -h 6901027 -n main
  43.  
  44.  
  45.  
  46.  
  47. 3. when fork is done, and lisk_bridge.sh ended, let's modify "config.json"
  48. ## as soon as fork script ends, and fork happened, launch the following:
  49.  
  50. cd $home/lisk-main
  51. nano config.json
  52.  
  53. ## Add this JSON object to your config.json under forging.delegates. like the following example:
  54.  
  55.  
  56. "forging": {
  57.   "force": false,
  58.   "delegates": [{"encryptedPassphrase": "salt=67a33e926e7f530f63e82d3b8747c26e&cipherText=fceaabc2&iv=917ea94def16180160d06eb5&tag=9c28fda8afbd963c65cd9befedceeb6c&version=1",
  59.                 "publicKey": "f350cbaa65b438a90082555c57f6347b6ee10b35c0bd5995b4cecd0b291989d8"}],
  60.     "access": {
  61.             "whiteList": [
  62.                 "127.0.0.1"
  63.            ]
  64.         }
  65.     },
  66.  
  67. ## save and do a lisk reload
  68. bash lisk.sh reload
  69.  
  70.  
  71.  
  72. 4. let's enable forging
  73.  
  74. curl -H 'Content-Type: application/json' -X PUT -d '{"publicKey":"f350cbaa65b438a90082555c57f6347b6ee10b35c0bd5995b4cecd0b291989d8", "forging":true, "password":"your_password_used_at_point_1"}' http://127.0.0.1:8000/api/node/status/forging
  75.  
  76.  
  77. ## use 'history -c' and 'clear' at the end
  78.  
  79.  
  80. That's all, folks!
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Top