Merge pull request #273 from massalabs/update_binary_version_2_1

Update FAQ

docs/node/faq.mdx

@@ -34,7 +34,7 @@ have to use ``pkill -f massa-node``. You can also use [screen](https://help.ubun
 ### What ports does Massa use?
 
 By default, Massa uses TCP port 31244 for protocol communication with other nodes, and 31245 to bootstrap other nodes.
-Massa also uses TCP port 33034 for the new private API, and 33035 for the new public API (API v2).
+Massa also uses TCP port 33034 for the new private API, 33035 for the new public API (API v2), 33037 for public GRPC and 33038 for private GRPC access.
 
 ### How to restart the Node?
 
@@ -57,19 +57,22 @@ message we send (just random bytes).
 
 ### How to migrate from one server to another without losing staked amounts and tokens?
 
-You need to back up the file `wallet.dat` and migrate it to the massa-client folder on your new server. You also need to
+You need to back up the folder `massa-client/wallets` and migrate it to the massa-client folder on your new server. You also need to
 backup and migrate the `node_privkey.key` file in massa-node/config to keep your connectivity stats.
 
 If you have rolls, you also need to register the key used to buy rolls to start staking again.
 
+Note: You should never stake with the same address on two different nodes, don't forget to stop the node on the old server before
+staking on your new server.
+
 ### Why are the balances in the client and the explorer different?
 
 It may mean that your node is desynchronized. Check that your node is running, that the computer meets hardware
 requirements, and try restarting your node.
 
 ### Where are the wallet files located?
 
-By default, in the massa-client directory.
+By default, in the massa-client/wallets directory.
 
 ## Rolls and staking
 
@@ -82,7 +85,7 @@ The most likely reason is that you did not produce some blocks when selected to
 - Node being desynchronized (which can be caused by temporary overload if the specs are insufficient or if other
   programs are using resources on the computer or because of internet connection problems) at some point while you had
   active_rolls \> 0
-- The node does not have the right registered staking keys (type staking_addresses in the client to verify that they
+- The node does not have the right registered staking keys (type `node_get_staking_addresses` in the client to verify that they
   match the addresses in your wallet_info that have active rolls) 100% of the time during which you had active_rolls \>
   0
 - Some hosting providers have Half-duplex connection setting. Contact hosting support and ask to switch you to
@@ -111,7 +114,7 @@ It is not slashing because the funds are reimbursed fully. It's more like an imp
 
 The point is the following: for the network to be healthy, everyone with active rolls needs to produce blocks whenever
 they are selected to do so. If an address misses more than 70% of its block creation opportunities during cycle C, all
-its rolls are implicitly sold at the beginning of cycle C+3.
+its rolls are implicitly sold at the end of cycle C+3.
 
 ### Do I need to register the keys after subsequent purchases of ROLLs, or do they get staked automatically?
 

docs/node/install.mdx

@@ -17,11 +17,11 @@ More info in the [FAQ](/docs/node/faq).
 If you just wish to run a Massa node without compiling it yourself, you can simply download the latest binary below and
 go to the next step: [Running a node](/docs/node/run).
 
-- [Windows executable](https://github.com/massalabs/massa/releases/download/MAIN.2.0/massa_MAIN.2.0_release_windows.zip)
-- [Linux binary](https://github.com/massalabs/massa/releases/download/MAIN.2.0/massa_MAIN.2.0_release_linux.tar.gz) - 
+- [Windows executable](https://github.com/massalabs/massa/releases/download/MAIN.2.1/massa_MAIN.2.1_release_windows.zip)
+- [Linux binary](https://github.com/massalabs/massa/releases/download/MAIN.2.1/massa_MAIN.2.1_release_linux.tar.gz) - 
 only works with libc2.28 and higher (for example Ubuntu 20.04 and higher)
-- [MacOS binary](https://github.com/massalabs/massa/releases/download/MAIN.2.0/massa_MAIN.2.0_release_macos_aarch64.tar.gz)
-- Other binaries can be found on https://github.com/massalabs/massa/releases/tag/MAIN.2.0
+- [MacOS binary](https://github.com/massalabs/massa/releases/download/MAIN.2.1/massa_MAIN.2.1_release_macos_aarch64.tar.gz)
+- Other binaries can be found on https://github.com/massalabs/massa/releases/tag/MAIN.2.1
 
 ## From source code (advanced installation)
 

external/client/mainnet/config-files.txt

@@ -1 +1 @@
-https://raw.githubusercontent.com/massalabs/massa/MAIN.2.0/massa-client/base_config/config.toml
+https://raw.githubusercontent.com/massalabs/massa/MAIN.2.1/massa-client/base_config/config.toml

external/node/mainnet/config-files.txt

@@ -1 +1 @@
-https://raw.githubusercontent.com/massalabs/massa/MAIN.2.0/massa-node/base_config/config.toml
+https://raw.githubusercontent.com/massalabs/massa/MAIN.2.1/massa-node/base_config/config.toml