From e0f7739d0537ed7e67c0bad0334bf066e358be9e Mon Sep 17 00:00:00 2001 From: onryo Date: Sun, 18 Jul 2021 03:31:12 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 0b7581d..c875fe5 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,10 @@ # Initial set up -This page describes all requried steps to run a HSC, mostly a copy-paste from: +This page describes all required steps to run a HSC, mostly a copy-paste from: https://git.hush.is/hush/hsc-creator/src/branch/master/docs.md and https://hush.is/hsc-creator and https://git.hush.is/hush/hush-smart-chains -2 static IPs are needed, we can use `sudo ufw allow from IP2` on a first node and `sudo ufw allow from IP1` on a second node to make sure servers can ping each other. To verify use `ping IP2` and `ping IP1` +2 static IPs are needed, we can use `sudo ufw allow from IP2` on a first node and `sudo ufw allow from IP1` on a second node to make sure nodes can ping each other. To verify use `ping IP2` and `ping IP1` # Install hush3 @@ -28,7 +28,7 @@ We do not want to lose our process and break our chain. So we can run the follow `tmux new-session -t NODE1` and `tmux new-session -t NODE2` on our second node -it is better to have more than 2 nodes, I have 2 free servers to run nodes on, so it can be 4 already +It is better to have more than 2 nodes, I have 2 free servers to run nodes on, so it can be 4 already. # Running a HSC @@ -76,11 +76,11 @@ pubkey=$(./hush-cli -ac_name=SHT validateaddress $newaddress | jq -r '.pubkey' ) ``` ./hush-cli -ac_name=SHT setgenerate true $(nproc) ``` -mining is prohibited with any VPS providers, so if you're planning to use one it is safe to run with `-j 2`(?) option instead of `$(nproc)`, will be updated... +Mining is prohibited by all VPS providers, so in that case it is safer to run with `-j 2`(?) option instead of `$(nproc)`, will be updated... -# verify if mining is working +# Verify if mining is working -After enabling mining, you can check that the two nodes are connected by using the following command: +After mining was enabled, you can check if the two nodes are connected by using the following command: ``` ./hush-cli -ac_name=SHT getinfo | grep connections @@ -98,13 +98,13 @@ Most useful: ``` # TO-DO list -- figure out how to properly publish the source code of the new chain created. (can be very confused about this one) -- change all tickers from HUSH to SHT. +- Figure out how to properly publish the source code of the new chain created. (can be very confused about this one) +- Change all tickers from HUSH to SHT. - ac_? for the total supply. -- mining, will coolmine and/or luckpool support SHT? solo-mining docs from @jahway603 -- wallets. -- dPoW? -- specify the devReward wallet, so some portion of all mined coins can go to the devReward address. +- Mining, will coolmine and/or luckpool support SHT? solo-mining docs from @jahway603 +- Wallets. +- DPoW? +- Specify the devReward wallet, so some portion of all mined coins can go to the devReward address. The last response from @Duke regarding the last to-do mentioned above: