updated veruscoin.io to verus.io in all published documents

Oink70 · Nov 10, 2020 · 60af62b · 60af62b
1 parent 2bd21d5
commit 60af62b
Show file tree

Hide file tree

Showing 25 changed files with 195 additions and 111 deletions.
diff --git a/...los/faq-allos15_how_can_i_tell_the_difference_between_staked_and_mined_coins.md b/...los/faq-allos15_how_can_i_tell_the_difference_between_staked_and_mined_coins.md
@@ -2,12 +2,12 @@
 
 ## CLI:
 
-You can check this in the VerusExplorer https://explorer.veruscoin.io/
+You can check this in the VerusExplorer https://explorer.verus.io/
 1. Check last 10 transactions in the </>CLI. Use `listtransactions`.
 2. Copy the blockhash of the received award
-3. Add it at the end of https://explorer.veruscoin.io/api/getblock?
+3. Add it at the end of https://explorer.verus.io/api/getblock?
 
-Hint: An example: https://explorer.veruscoin.io/api/getblock?hash=9e6fa91356211a554c580c90ec9c2067dd420ff74c7d33481775793f7b0e7f03 – so this one is minted....
+Hint: An example: https://explorer.verus.io/api/getblock?hash=9e6fa91356211a554c580c90ec9c2067dd420ff74c7d33481775793f7b0e7f03 – so this one is minted....
 
 ## Verus Desktop:
 
@@ -25,4 +25,4 @@ In the GUI you can also click yourself thru to that information.
 
 (submitted by karero, edited by Oink.vrsc@)
 
-Note: last revision date 2020-04-24.
+Note: last revision date 2020-11-11.
diff --git a/...y_own_fork_because_of_a_network_issue_or_having_an_old_version_of_the_wallet.md b/...y_own_fork_because_of_a_network_issue_or_having_an_old_version_of_the_wallet.md
@@ -18,7 +18,7 @@ For all GUI or CLI users.
     `run getblockhash <suspected blocknumber>` will show you the blockhash for the blocknumber you filled in
     The response shown in the *Native Client Terminal* will be similar to this:
     `5cc7844973fb95ef17f1772ea4aba579f0d8273fb0ee6064cd8e707d1056c646`
-3.  Check the blockhash your command gave you against the blockhash the [explorer](https://explorer.veruscoin.io) shows.
+3.  Check the blockhash your command gave you against the blockhash the [explorer](https://explorer.verus.io) shows.
 4.  If the blockhash from the explorer is different than yours, repeat steps 2 & 3 until you find the earliest block that is different.
 5.  Use the **earliest incorrect blockhash** from your system to invalidate that block:
     `run invalidateblock <earliest incorrect blockhash>`
@@ -34,7 +34,7 @@ For all GUI or CLI users.
     `./verus getblockhash <suspected blocknumber>` will show you the blockhash for the blocknumber you filled in
     The response will be similar to this:
     `5cc7844973fb95ef17f1772ea4aba579f0d8273fb0ee6064cd8e707d1056c646`
-2.  Check the blockhash your command gave you against the blockhash the [explorer](https://explorer.veruscoin.io) shows.
+2.  Check the blockhash your command gave you against the blockhash the [explorer](https://explorer.verus.io) shows.
 3.  If the blockhash from the explorer is different than yours, repeat steps 1 & 2 until you find the earliest block that is different.
 4.  Use the **earliest incorrect blockhash** from your system to invalidate that block:
     `./verus invalidateblock <earliest incorrect blockhash>`
@@ -48,4 +48,4 @@ For all GUI or CLI users.
 
 (submitted by @jimboscott, Edited by Oink.vrsc@)
 
-Note: last revision date 2020-04-24.
+Note: last revision date 2020-11-11.
diff --git a/...followed_the_procedure_in_faq_19_and_am_still_having_problems_with_my_wallet.md b/...followed_the_procedure_in_faq_19_and_am_still_having_problems_with_my_wallet.md
@@ -42,7 +42,7 @@ Note: The filename you replace`<mywalletexport>` with, can only contain letters
 The exported wallet should be a file called `mywalletexport` in the location you set for exportdir in `VRSC.conf`. Keep this file secure, it has your plaintext private keys. Verify that the file is there and isn't empty.
 7. Stop Verus again by closing Verus-Desktop, Agama or running `./verus stop` for the linux CLI or `verus.bat stop` for the windows CLI.
 8. Making ABSOLUTELY SURE you have both the `mywalletexport` file and your `wallet.dat` backup in a safe place, delete your komodo/VRSC directory and everything in it (you can optionally leave your VRSC.conf file, but everything else there should be deleted.
-9. At this point make sure you're on the latest version for your wallet by going to https://veruscoin.io/ and checking the downloads section. If you need to upgrade do so now, before starting your wallet again.
+9. At this point make sure you're on the latest version for your wallet by going to https://verus.io/ and checking the downloads section. If you need to upgrade do so now, before starting your wallet again.
 10. Restart your wallet by launching Verus-Desktop, Agama or running verusd for the CLI. Allow it to start syncing.
 11. Once it has begun syncing, you can import your wallet. In either case, replace <PATHTOWALLETEXPORT with the full path to your wallet export file - on windows this might look like `c:\Users\John\Desktop\mywalletexport` , on linux or mac it would look something like `/home/john/mywalletexport`.
  * Verus-Desktop:
@@ -58,4 +58,4 @@ The exported wallet should be a file called `mywalletexport` in the location you
 
 Depending on the number of addresses in your wallet and how far along you are on re-syncing, this may take several minutes to complete. Your balances will adjust as the chain syncs, as it only knows about the transactions that have happened in the blocks it has received and scanned. That means your balance will adjust as new blocks are scanned and won't reflect an accurate balance until you are fully synced.
 
-Note: last revision date 2020-09-30.
+Note: last revision date 2020-11-11.
diff --git a/faq-allos/faq-allos21_mining_pools.md b/faq-allos/faq-allos21_mining_pools.md
@@ -1,7 +1,7 @@
 # Question: What are the mining pools that I can join?
 
 [luckpool.net](https://luckpool.net/verus)
-[pool.veruscoin.io](https://luckpool.net/verus)
+[pool.verus.io](https://pool.verus.io)
 [zergpool.com](https://zergpool.com/)
 [wattpool.net](https://wattpool.net/ui/verus/stats)
 [vrsc.ciscotech.dk](https://vrsc.ciscotech.dk/)

diff --git a/faq-allos/faq-allos25_wallet_not_synced.md b/faq-allos/faq-allos25_wallet_not_synced.md
@@ -9,8 +9,8 @@ note: Read it completely before use.
  * OS independent through Verus Desktop: Click `help`, `Show Verus data folder (default)`
 
 #### Usefull links:
-Link 1: [Download latest Wallet](https://veruscoin.io/wallet.html)
-Link 2: [Show current blockheight](https://explorer.veruscoin.io/api/getblockcount)
+Link 1: [Download latest Wallet](https://verus.io/wallet.html)
+Link 2: [Show current blockheight](https://explorer.verus.io/api/getblockcount)
 
 ## Procedure:
 In case your wallet is not synchronized with the blockchain and restarting Agama doesn't connect to any peers:
@@ -37,4 +37,4 @@ Then start your wallet as you're used to.
 
 Submitted by Oink.vrsc@ & Thoskk.vrsc@
 
-Note: last revision date 2020-04-24.
+Note: last revision date 2020-11-11.
diff --git a/faq-allos/faq-allos26_sent_funds_to_b-address.md b/faq-allos/faq-allos26_sent_funds_to_b-address.md
@@ -9,7 +9,7 @@ Warning: DO NOT send to a b-address, unless you kow what you're doing.
 ### First you need to determine the **TXID** of the locked funds.
 
 1. The easiest way is to obtain the TXID from the send transaction you did in Verus-Desktop to the b-address. Make a copy of the TXID: you will need it for this procedure
-2. The next easiest way is look up the b-address on the [explorer](https://explorer.veruscoin.io) and examine the transactions to this address. The youngest transaction is usually the one you need. On the explorer the hash in the transaction is the TXID. Make a copy of the TXID: you will need it for this procedure
+2. The next easiest way is look up the b-address on the [explorer](https://explorer.verus.io) and examine the transactions to this address. The youngest transaction is usually the one you need. On the explorer the hash in the transaction is the TXID. Make a copy of the TXID: you will need it for this procedure
 3. In Verus Desktop, go to `Settings` --> `Coin Settings` and make sure `VRSC` is selected in the top right. Run the command:
 ```bash
 run listunspent 0 <BLOCKCOUNT> '["<YOUR-b-ADDRESS"]'
@@ -75,12 +75,12 @@ and your command will show a result similar to this example:
 ```json
 4a5202327e6ed2ce20d3b146155ec92e52fae6c4481362faf6f8a072017b41f1
 ```
-The result of this command is the TXID of the coins moving out of your b-address. You can monitor the progress in your wallet or look up the TXID in the [explorer](https://explorer.veruscoin.io).
+The result of this command is the TXID of the coins moving out of your b-address. You can monitor the progress in your wallet or look up the TXID in the [explorer](https://explorer.verus.io).
 
 note: The above command and its result are examples. ***DO NOT*** use data from it. Use the results from your own wallet!
 
 Some words of advice after succesfully removing funds locked in a b-address:
 * Pay attention to which addresses you send.
 * It may be an idea to import the addresses you use into a fresh wallet, omitting all unused (b-) addresses.
 
-note: Created 2020-02-18 by Oink.vrsc@
+note: Created 2020-11-11 by Oink.vrsc@
diff --git a/faq-cli/clifaq-02_verus_commands.md b/faq-cli/clifaq-02_verus_commands.md
@@ -1689,13 +1689,47 @@ Returns all pending export transfers that are not yet provable with confirmed no
 1. "chainname"                     (string, optional) name of the chain to look for. no parameter returns current chain in daemon.
 ```
 #### Result:
-```
+```json
+[
   {
-  }
+    "blockheight": n,                    (numeric) block height
+    "exportid": "hash",                  (hexstring) transaction ID
+    "description": {
+      "version": n,                      (int) version of this chain definition
+      "exportcurrencyid": "xxxx",        (text) i-address of the currency ID
+      "numinputs": n,                    (numeric) Amount of inputs in this export
+      "totalamounts": {
+        "xxxx": xxx.xxxxxxxx,            (text) i-address of the currency ID, (numeric) the total value of the export
+                                         of the currency
+        ....
+      },
+      "totalfees": {
+        "xxxx": xxx.xxxxxxxx,            (text) i-address of the currency ID, (numeric) the total fees for the export
+                                         of the currency
+        ....
+      }
+    },
+    "transfers": [
+      {
+        "version": n,                    (int) version of this chain definition
+        "currencyid": "xxxx",            (text) i-address of the currency ID
+        "value": n,                      (numeric) the value this transaction
+        "flags": n,                      (hex) flags for the currency
+        "preconvert": true|false,        (boolean) Shows whether the transaction is a preconversion
+        "fees": xxx.xxxxxxxx,            (numeric) the fees for this transaction
+        "destinationcurrencyid": "xxxx", (text) i-address of the currency ID
+        "destination": "xxxx"            (text) address of the transaction
+      },
+      ....
+    ]
+  },
+  {},
+  ...
+]
 ```
 Examples:
 ```bash
-> verus getimports "chainname"
+> verus getexports "chainname"
 > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getexports", "params": ["chainname"] }' -H 'content-type: text/plain;' http://127.0.0.1:27486/
 ```
 
@@ -1706,9 +1740,43 @@ Returns all imports from a specific chain.
 1. "chainname"                     (string, optional) name of the chain to look for. no parameter returns current chain in daemon.
 ```
 #### Result:
-```
+```json
+[
   {
-  }
+    "blockheight": n,                    (numeric) block height
+    "importid": "hash",                  (hexstring) transaction ID
+    "description": {
+      "version":n,                       (int) version of this chain definition
+      "sourcesystemid": "xxxx",          (text) i-address of the source system
+      "importcurrencyid": "xxxx",        (text) i-address of the currency ID
+      "valuein": {
+        "xxxx": xxx.xxxxxxxx,            (text) i-address of the currency ID, (numeric) the total value of the import
+                                         of the currency
+        ....
+      },
+      "tokensout": {
+        "xxxx": xxx.xxxxxxxx,            (text) i-address of the currency ID, (numeric) the total value of the import
+                                         into the currency into this currency
+      }
+    },
+    "transfers": [
+      {
+        "version": n,                    (int) version of this chain definition
+        "currencyid": "xxxx",            (text) i-address of the currency ID
+        "value": n,                      (numeric) the value this transaction
+        "flags": n,                      (hex) flags for the currency
+        "preconvert": true|false,        (boolean) Shows whether the transaction is a preconversion
+        "fees": xxx.xxxxxxxx,            (numeric) the fees for this transaction
+        "destinationcurrencyid": "xxxx", (text) i-address of the currency ID
+        "destination": "xxxx"            (text) address of the transaction
+      },
+      ....
+      }
+    ]
+  },
+  {},
+  ...
+]
 ```
 Examples:
 ```bash
@@ -1727,15 +1795,32 @@ This should be used to get information about chains that are not this chain, but
 #### Result:
 ```json
    [
-       {
-           "flags" : n,
-           "initialratio" : n,
-           "initialsupply" : n,
-           "emitted" : n,
-           "supply" : n,
-           "reserve" : n,
-           "currentratio" : n,
+     {
+       "flags": n,                      (hex) flags for the currency
+       "currencyid": "xxxx",            (text) i-address of the currency ID
+       "reservecurrencies": [
+         {
+     			 "currencyid": "xxxx",        (text) i-address of the currency ID
+     			 "weight": n,                 (numeric) The weight of this currence
+     			 "reserves": xxx.xxxxxxxx,    (numeric) The initial amount of this currency in reserve
+     			 "priceinreserve": n          (numeric) The initial conversion rate of this reserve currency
+     	   },
+       ],
+       "initialsupply" : xxx.xxxxxxxx,  (numeric) The initial supply of this currency
+       "emitted" : xxx.xxxxxxx,         (numeric) The currently emitted coins of this currency
+       "supply" : xxx.xxxxxxxx,         (numeric) The current supply of this currency
+       "currencies": {
+         "xxxx": {                      (text) i-address of the currency ID
+       	 "reservein": xxx.xxxxxxxx,     
+       	 "nativein": 0.00000000,
+       	 "reserveout": 249.99900299,
+       	 "lastconversionprice": 1.00000000,
+       	 "viaconversionprice": 0.99981249,
+       	 "fees": 250.06291562,
+       	 "conversionfees": 250.06251562
+       	 },
        },
+     },
    ]
 ```
 Examples:

diff --git a/faq-linux/faq-lin01_install_linux_cli.md b/faq-linux/faq-lin01_install_linux_cli.md
@@ -8,8 +8,8 @@ Notice: Read it completely before use.
 
 #### Necessary files:
 
-Link 1: [Download latest Wallet](https://veruscoin.io/wallet.html)
-Link 2: [Download Verus Bootstrap](https://bootstrap.veruscoin.io/)
+Link 1: [Download latest Wallet](https://verus.io/wallet)
+Link 2: [Download Verus Bootstrap](https://bootstrap.verus.io/)
 
 ## Procedure:
 
@@ -26,9 +26,9 @@ Link 2: [Download Verus Bootstrap](https://bootstrap.veruscoin.io/)
   You should get some lines like this:
   `drwx------  6 root root 4096 Jul  3 15:56`
 5. Download & install the wallet binaries:
-  `wget https://github.com/VerusCoin/VerusCoin/releases/download/v0.7.0-4/Verus-CLI-Linux-v0.7.0-4-amd64.tgz`
+  `wget https://github.com/VerusCoin/VerusCoin/releases/download/v0.7.0-4/Verus-CLI-Linux-v0.7.2-3-amd64.tgz`
  The downloaded archive contains another archive and a signature text file, enabling the archive within to be verified (You'll need a running wallet to do that)
- Also: Verify the URL to the latest version from the [Download latest Wallet](https://veruscoin.io/wallet.html) above.
+ Also: Verify the URL to the latest version from the [Download latest Wallet](https://verus.io/wallet) above.
   `tar -xvf Verus-CLI-Linux-v0.7.0-4-amd64.tgz`
  Now extract the wallet archive:
   `tar -xvf Verus-CLI-Linux-v0.7.0-4-amd64.tar.gz`
@@ -41,7 +41,7 @@ Creating the chaindata directory
   `mkdir -p .komodo/VRSC`
   `cd ~/.komodo/VRSC`
 Download the block-chain bootstrap, this considerably speeds up synchronisation of the block-chain from days to minutes... (optional)
-  `wget https://bootstrap.veruscoin.io/VRSC-bootstrap.tar.gz`
+  `wget https://bootstrap.verus.io/VRSC-bootstrap.tar.gz`
   `tar -xvf VRSC-bootstrap.tar.gz`
  Install libraries for Verus
   `sudo apt-get install libcurl3 g++-multilib -y`
@@ -69,4 +69,4 @@ Apply no settings:
 
 (submitted by @karero, corrected by @Glennp, edited by Oink.vrsc@)
 
-Note: last revision date 2020-06-30.
+Note: last revision date 2020-11-11.
diff --git a/faq-linux/faq-lin06_compile_ccminer.md b/faq-linux/faq-lin06_compile_ccminer.md
@@ -37,9 +37,9 @@ chmod +x autogen.sh
 ```
 And finally starting the miner (Change pool, address & workername to your own liking):
 ```bash
-./ccminer -a verus -o stratum+tcp://pool.veruscoin.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.donator -p x
+./ccminer -a verus -o stratum+tcp://pool.verus.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.donator -p x
 ```
 
 Info from @Chris - Monkins1010 LOUD Mining.
 
-Note: last revision date 2020-10-05.
+Note: last revision date 2020-11-11.
diff --git a/faq-linux/faq-lin07_PHP_CLI_interface.md b/faq-linux/faq-lin07_PHP_CLI_interface.md
@@ -5,8 +5,8 @@ Attention: Read it completely before using.
 `VRSC Wallet and Data location` on Linux: `~/.Komodo/VRSC`
 
 ### Necessary files:
-Link 1: [Download latest Wallet](https://veruscoin.io/wallet.html)
-Link 2: [Download Bootstrap](https://bootstrap.veruscoin.io/)
+Link 1: [Download latest Wallet](https://verus.io/wallet)
+Link 2: [Download Bootstrap](https://bootstrap.verus.io/)
 Link 3: [Go to Verus-Staking-CLI](https://github.com/kbs1/verus-staking-cli)
 
 ## Procedure:
@@ -25,3 +25,5 @@ Initial Verus daemon configuration
   Do not stake with the same `wallet.dat` on multiple nodes.
 
 Submitted by @kbs1
+
+Note: last revision date 2020-11-11.
diff --git a/faq-linux/faq-lin08_low_priority_mining.html.md b/faq-linux/faq-lin08_low_priority_mining.html.md
@@ -4,7 +4,7 @@ Attention: Read it completely before use.
 
 ### Links to VRSC miners:
 
-[Miners download page](https://veruscoin.io/getVRSC.html#download)
+[Miners download page](https://verus.io/get-vrsc)
 
 ## Procedure:
 
@@ -20,8 +20,8 @@ Now we'll need to adjust the batchfile to run on low priority:
 
   - Run your miner as you normally would, with `nice -n 19 ` placed in front of the command you normally use,
     for example:
-      `nice -n 19 ./nheqminer -v -l pool.veruscoin.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.Donator -p x -t 6`
-  - make sure you replace the pool (`pool.veruscoin.io:9999`) with your prefered pool and the address
+      `nice -n 19 ./nheqminer -v -l pool.verus.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.Donator -p x -t 6`
+  - make sure you replace the pool (`pool.verus.io:9999`) with your prefered pool and the address
     (`RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ`) with your own address. The address shown in this line is the veruscoin
     foundation donation address. If desired change the identifier (`Donator`) to a name that easily identifies the
     miner to you.
@@ -30,13 +30,13 @@ Now we'll need to adjust the batchfile to run on low priority:
 
   - Run your miner as you normally would, with `nice -n 19 ` placed in front of the command you normally use,
     for example:
-      `nice -n 19 ./ccminer -a verus -o stratum+tcp://pool.veruscoin.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.Donator -t 6`
-  - make sure you replace the pool (`stratum+tcp://pool.veruscoin.io:9999`) with your prefered pool and the address
+      `nice -n 19 ./ccminer -a verus -o stratum+tcp://pool.verus.io:9999 -u RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ.Donator -t 6`
+  - make sure you replace the pool (`stratum+tcp://pool.verus.io:9999`) with your prefered pool and the address
     (`RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ`) with your own address. The address shown in this line is the veruscoin
     foundation donation address. If desired change the identifier (`Donator`) to a name that easily identifies the
     miner to you.
 
 
 Created by Oink.vrsc@.
 
-Note: last revision date 2020-02-26.
+Note: last revision date 2020-11-11.
diff --git a/faq-macos/mac-faq03-mining_guide.md b/faq-macos/mac-faq03-mining_guide.md
@@ -6,8 +6,8 @@ Attention: Read it completely before use.
 
 ### Software needed to mine
 
-Prerequisite: [VerusCoin wallets](https://veruscoin.io/wallet.html)
-Needed: [VerusCoin miners](https://veruscoin.io/getVRSC.html)
+Prerequisite: [VerusCoin wallets](https://verus.io/wallet.html)
+Needed: [VerusCoin miners](https://verus.io/getVRSC.html)
 
 ## Prerequisites:
 
@@ -29,7 +29,7 @@ To start mining on your Mac, you should already have a wallet and and access to
 
 Now we need to configure things so the miner connects to a mining pool (listed on the download page, below the miner download) and mines to your address. In the instructions below I will use the VerusCoin community pool and the address for the Veruscoin foundation. make sure to use your own address and if desired the details of a different pool:
   5. click `start.sh` and open with `TextEdit.app`
-  6. On the 2nd line, change `PoolHost=` into `Poolhost=pool.veruscoin.io`
+  6. On the 2nd line, change `PoolHost=` into `Poolhost=pool.verus.io`
   7. On the 3rd line, change `Port=` into 'Port=9999'
   8. On the 4th line, change 'PublicVerusCoinAddress=' into `PublicVerusCoinAddress=RVjvbZuqSGLGDm1B9BFkbHWySPKEx4tfjQ`
         (make sure you use your own address!!!!)