Update 'README.md'

README.md

@@ -1,6 +1,6 @@
 # Initial set up
 
-This page describes all required steps to run SHTcoin, mostly a copy-paste from:
+This page describes all required steps to run testcoin, 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
 
@@ -38,21 +38,21 @@ It is better to have more than 2 nodes, I have 2 free servers to run nodes on, s
 From your NODE1 run:
 
 ```
-./hush-smart-chain -ac_name=SHT -ac_private=1 -ac_blocktime=260 -ac_halving=420000 -ac_reward=2400000000 -ac_supply=987318 -addnode=IP2 &
+./hush-smart-chain -ac_name=test -ac_private=1 -ac_blocktime=260 -ac_halving=420000 -ac_reward=2400000000 -ac_supply=987318 -addnode=IP2 &
 ```
 
 From your NODE2 run:
 
 ```
-./hush-smart-chain -ac_name=SHT -ac_private=1 -ac_blocktime=260 -ac_halving=420000 -ac_reward=2400000000 -ac_supply=987318 -addnode=IP1 &
+./hush-smart-chain -ac_name=test -ac_private=1 -ac_blocktime=260 -ac_halving=420000 -ac_reward=2400000000 -ac_supply=987318 -addnode=IP1 &
 ```
-`-ac_name=SHT` - name
+`-ac_name=test` - name
 
 `-ac_private=1` - full z2z privacy feature, just like Hush or ARRR
 
 `ac_supply=987318` - pre-mined supply
 
-`-ac_blocktime=260` + `-ac_halving=420000` + `-ac_reward=2400000000` makes SHT with block time of 260 seconds and halving every 420000 blocks with initial reward of 24 SHT. 
+`-ac_blocktime=260` + `-ac_halving=420000` + `-ac_reward=2400000000` makes test with block time of 260 seconds and halving every 420000 blocks with initial reward of 24 test. 
 
 # Compare the magic number
 
@@ -66,18 +66,18 @@ To collect all the mining rewards from the node to a single address, execute the
 
 ```
 # Get a new address
-newaddress=$(./hush-cli -ac_name=SHT getnewaddress)
+newaddress=$(./hush-cli -ac_name=test getnewaddress)
 
 # Get the corresponding pubkey
-pubkey=$(./hush-cli -ac_name=SHT validateaddress $newaddress | jq -r '.pubkey' )
+pubkey=$(./hush-cli -ac_name=test validateaddress $newaddress | jq -r '.pubkey' )
 
 # Indicate the pubkey to the daemon
-./hush-cli -ac_name=SHT setpubkey $pubkey
+./hush-cli -ac_name=test setpubkey $pubkey
 ```
 # Enable mining 
 
 ```
-./hush-cli -ac_name=SHT setgenerate true $(nproc)
+./hush-cli -ac_name=test setgenerate true $(nproc)
 ```
 Mining is prohibited by all VPS providers, so in that case it is safer to run with `-j2`(?) option instead of `$(nproc)`, will be updated...
 
@@ -86,7 +86,7 @@ Mining is prohibited by all VPS providers, so in that case it is safer to run wi
 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
+./hush-cli -ac_name=test getinfo | grep connections
 ```
 Must be `"connections": 1`.
 
@@ -97,14 +97,14 @@ All RPC commands for Hush can be used the same way for any HSC. The total list:
 Most useful:
 
 ```
-./hush-cli -ac_name=SHT getinfo
+./hush-cli -ac_name=test getinfo
 ```
 # 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.
+- Change all tickers from HUSH to test.
 - ac_? for the total supply. 
-- Mining, will coolmine and/or luckpool support SHT? solo-mining docs from @jahway603
+- Mining, will coolmine and/or luckpool support test? solo-mining docs from @jahway603
 - Wallets.
 - DPoW?
 - Specify the devReward wallet, so some portion of all mined coins can go to the devReward address.