Added additional slasher documentation, and changed TESTNET to NETWORK.

SETUP.md

@@ -98,6 +98,7 @@ geth with `:` between the file names.
 - `lh-grafana.yml` - grafana dashboard for Lighthouse
 - `prysm-grafana.yml` - grafana dashboard for Prysm. Not encrypted, do not expose to Internet.
 - `prysm-web.yml` - Prysm experimental Web UI. Not encrypted, do not expose to Internet.
+- `prysm-slasher.yml` - Prysm experimental Web UI. Not encrypted, do not expose to Internet.
 - `nimbus-grafana.yml` - grafana dashboard for Nimbus
 - `teku-grafana.yml` - grafana dashboard for Teku
 
@@ -113,6 +114,12 @@ clients each in their own directory.
 If you want to run multiple isolated clients, just clone this project into a new directory for
 each. This is great for running medalla and zinken in parallel, for example.
 
+### `SLASHER`   
+Running [slasher](https://docs.prylabs.network/docs/prysm-usage/slasher/) is an optional client compose file, but helps secure the chain and may result in additional earnings.
+```
+Slasher can be a huge resource hog during times of no chain finality, which can manifest as massive RAM usage. Please make sure you understand the risks of this, especially if you want high uptime for your beacon nodes. Slasher places significant stress on beacon nodes when the chain has no finality, and might be the reason why your validators are underperforming if your beacon node is under this much stress.
+```
+
 ## Firewalling
 
 You'll want to forward ports to the services of your eth2 node, and on Linux, enable a host firewall.

prysm-slasher.yml

@@ -20,7 +20,7 @@ services:
       - beacon:4000
       - --verbosity
       - ${LOG_LEVEL}
-      - --${TESTNET}
+      - --${NETWORK}
       - --accept-terms-of-use
     depends_on:
       - validator