Merge remote-tracking branch 'origin/master' into devel

.github/ISSUE_TEMPLATE/security-assessment-issue.md

@@ -2,7 +2,7 @@
 name: Security-assessment-issue
 about: File a Nimbus Security Assessment issue
 title: "[SEC]"
-labels: nbc-audit-2020-0 :passport_control:, status:reported
+labels: nbc-audit-2020-2 :passport_control:, status:reported
 assignees: ''
 
 ---

docs/the_nimbus_book/src/.medalla-troubleshooting.md

@@ -0,0 +1 @@
+# Troubleshooting Medalla

docs/the_nimbus_book/src/medalla-troubleshooting.md

@@ -38,7 +38,7 @@ This will create `nbc_pruned.sqlite3` files in `build/data/shared_medalla_0/db`,
 Options:
 - `--keepOldStates` (boolean):  Keep pre-finalisation states; defaults to `true`.
 - `--verbose` (boolean): Print a more verbose output to the console; defaults to `false`.
-  
+
 
 ### Keeping up with the head of the chain
 
@@ -60,5 +60,3 @@ make NODE_PARAMS="--nat:\"extip:35.124.65.104\"" medalla
 ### Resource leaks
 
 If you're experiencing RAM related resource leaks, try restarting your client (**we recommend restarting every 6 hours** until we get to the bottom of this issue). If you have a [local Grafana setup](https://github.com/status-im/nim-beacon-chain#getting-metrics-from-a-local-testnet-client), you can try monitoring the severity of these leaks and playing around with the restart interval.
-
-

docs/the_nimbus_book/src/medalla.md

@@ -74,17 +74,17 @@ INF 2020-08-03 16:24:17.958+02:00 Starting beacon node                       top
 
 If you deposited after the [genesis](https://hackmd.io/@benjaminion/genesis) state was decided (August 2nd 1300 UTC), your validators will have been put in a queue based on deposit time, and will slowly be inducted into the validator set after genesis. Getting through the queue may take a few hours or days.
 
-The best way to keep track of your validator's status is [medalla.beaconcha.in](https://medalla.beaconcha.in) (click on the orange magnifying glass at the very top and paste in its public key). 
+The best way to keep track of your validator's status is [medalla.beaconcha.in](https://medalla.beaconcha.in) (click on the orange magnifying glass at the very top and paste in its public key).
 
 You can even [create an account](https://medalla.beaconcha.in/register) to add alerts and keep track of your validator's [performance](https://medalla.beaconcha.in/dashboard).
 
 To keep track of your syncing progress, have a look at the output at the very bottom of the terminal window in which your validator is running. You should see something like:
 
 ```
-peers: 35 ❯ finalized: ada7228a:8765 ❯ head: b2fe11cd:8767:2 ❯ time: 9900:7 (316807) ❯ sync: wPwwwwwDwwDPwPPPwwww:7:4.0627 (280512) 
+peers: 35 ❯ finalized: ada7228a:8765 ❯ head: b2fe11cd:8767:2 ❯ time: 9900:7 (316807) ❯ sync: wPwwwwwDwwDPwPPPwwww:7:4.0627 (280512)
 ```
 
-Where: 
+Where:
 - `peers` tells you how many peers you're currently connected to (in the above case, 35 peers)
 - `finalized` tells you the most recent finalized epoch you've synced to so far (the 8765th epoch)
 - `head` tells you the most recent slot you've synced to so far (the 2nd slot of the 8767th epoch)
@@ -207,4 +207,3 @@ If you are comfortable reading [Makefiles](https://en.wikipedia.org/wiki/Makefil
 Some of the provided options (such as `--network=medalla`) are essential while others (such as the ones controlling logging, metrics, ports, and the RPC service) are there for convenience.
 
 The Goerli testnet parameters (`$(GOERLI_TESTNETS_PARAMS`), are defined higher up in the Makefile, [here](https://github.com/status-im/nim-beacon-chain/blob/devel/Makefile#L158-L165).
-