Merging better near-shell commands, and BetaNet update retro (nearpro…

…tocol#142)

* Prettified VALIDATORS.md
* updating README.md and updates.md

README.md

@@ -123,7 +123,7 @@ export NODE_ENV=betanet
 
 Then, issue this command to stake:
 ```bash
-near stake <YOUR_ACCOUNT_ID> <VALIDATOR_KEYS_PUBLIC_KEY> <AMOUNT>
+near stake <YOUR_ACCOUNT_ID> <VALIDATOR_KEYS_PUBLIC_KEY> <AMOUNT> --walletUrl https://wallet.betanet.nearprotocol.com --helperUrl https://helper.betanet.nearprotocol.com --nodeUrl https://rpc.betanet.nearprotocol.com
 ```
 **HEADS UP:** `<AMOUNT>` must be set in NEAR, and you should have enough tokens in your account. Don't stake 100% of your account holdings: please leave enough tokens to issue smart contracts and pay your account storage (100 $NEAR will do great).
 
@@ -246,7 +246,7 @@ Staking 70000 (70000000000000000000000000000) on nearkat with public key = ed255
 
 ![alt text](media/stake_tx_explorer.png "Explorer successful transaction")
 
-3. Run `near state <YOUR_ACCOUNT_ID>` and see if the amount you've staked is marked as locked, similar to the content below:
+3. Run `near state <YOUR_ACCOUNT_ID> --walletUrl https://wallet.betanet.nearprotocol.com --helperUrl https://helper.betanet.nearprotocol.com --nodeUrl https://rpc.betanet.nearprotocol.com` and see if the amount you've staked is marked as locked, similar to the content below:
 ```
 nearkat@nearkat ~ $ near state nearkat
 Using options: {
@@ -556,7 +556,7 @@ Be sure that `num_produced_blocks` is the same of `num_expected_blocks`, otherwi
 ## Stop your node
 First, release your funds, by setting to zero your stake:
 ```bash
-near stake <YOUR_ACCOUNT_ID> <VALIDATOR_KEYS_PUBLIC_KEY> 0
+near stake <YOUR_ACCOUNT_ID> <VALIDATOR_KEYS_PUBLIC_KEY> 0 --walletUrl https://wallet.betanet.nearprotocol.com --helperUrl https://helper.betanet.nearprotocol.com --nodeUrl https://rpc.betanet.nearprotocol.com
 ```
 Wait for two epochs (6 hours) and shut down your node. You may kill the validator process straight away, but it will have an impact on the network performance (less throughput) and other users will not be happy!
 

updates.md

@@ -1,5 +1,32 @@
 # UPDATES
 
+## UPDATE Apr 29th
+
+* New `near-shell`
+* New `nearcore`, improved consensus and networking for higher stability
+* BetaNet Incident #0002
+
+**Incident Abstract:**
+
+NEAR's planned weekly update of BetaNet failed, the network didn't produce new blocks from 00:55 GMT to 7:10 GMT
+
+**Incident Description:**
+
+- NEAR began the scheduled weekly update of its `nearcore` node at 00:00 GMT
+- The deployment pipeline completed successfully at 00:55 GMT, with the release `Version: 0.4.13, Build: 38d54ba7-modified`
+- This update needed a hard-fork, with a new `genesis.json` file containing `"genesis_height": "3818145"`. Previous releases were not able to sync to any block higher than `3818145`
+- As planned, all NEAR's BetaNet nodes switched to this new release, and the new genesis block was broadcasted through NEAR's `boot nodes`
+- At 00:56 GM the Core Team informed NEAR Validators on Telegram and Discord that all nodes had to be updated and restarted asap
+- This update could be automatically triggered by stopping and starting `nearup` (only for `nearup` users), or in case of automated deployment pipeline, by downloading and compiling `nearcore` from the branch `beta`
+- Multiple nodes were correctly updated, however the network reached 66% of the total stake only at 7:10 GMT, after 6 hours and 20 minutes from the advertised release messages
+- At 7:10 GMT the network reached a quorum, with a throughput between `0.10 bps` and `0.20 bps (blocks per second)`
+- At 10:49 GMT, with block 3822000, the protocol unstaked the validators which failed to update on time and the ones that were running the old release, bringing back BetaNet in its normal state
+
+**Remediation:**
+
+- An investigation is in progress: NEAR's Core Team is contacting all the node operators that were validators at 00:00 GMT, to troubleshoot the upgrade process and identify the issues encountered
+- As soon as the investigation is complete, this remediation will be extended with the introduced measures in terms of bug fixes, new features, documentation and communication
+
 ## UPDATE Apr 21st
 
 * Released [Road to Mainnet](https://near.ai/mainnet-roadmap)