add mainnet preparation guide (#2022)

docs/the_nimbus_book/src/SUMMARY.md

@@ -10,6 +10,7 @@
 - [Connect your validator to eth2](./connect-eth2.md)
 - [Keep an eye on your validator](./keep-an-eye.md)
 - [Keep Nimbus updated](./keep-updated.md)
+- [Mainnet preparations](./preparation.md)
 # Volume 2
 - [Command line options](./options.md)
 - [Troubleshooting](./troubleshooting.md)

docs/the_nimbus_book/src/graffiti.md

@@ -1,6 +1,9 @@
 # Graffiti
 
-*Todo*
+You can use your validator client's graffiti flag to add a personal touch to your proposed blocks (some text of your choice). You will be able to see it using the block explorer.
+
+To do so on Medalla, run:
+
 ```
 ./run-medalla-beacon-node.sh --graffiti="<YOUR_GRAFFITI>"
 ```

docs/the_nimbus_book/src/hardware.md

@@ -0,0 +1,15 @@
+# Hardware
+
+In order to process incoming validator deposits from the eth1 chain, you will need to run an eth1 client in parallel to your eth2 client. While it is possible to use a third-party service like Infura, we recommend running your own client in order to ensure the network stays as decentralised as possible.
+For example, you need at least 140 GB SSD to run geth fast sync on mainnet...
+
+Is there a recommend AWS machine to run Nimbus on? Struggling to find the right balance between expense and ease of running. Have crashed due to memory a few times, and now due to a full / Any direction would be appreciated for a genuine newbie...
+
+> Stefan: I'm comfortable with 4 GiB of RAM, on another VPS provider. 2 GiB would be a theoretical minimum for building the software, but if you're trying to build a new version while running a beacon node, you're pushing the limits.
+So look at "t3.medium".
+
+What about storage requirements?
+
+> Stefan: I'm starting with 160 GiB of block storage for the beacon node alone. If you're also running Geth on that server, you'll want more.
+
+> Tersec: there's a tool to prune the database, which keeps it smaller, but for the moment that's active maintenance which requires a bit of downtime. So it's a tradeoff.

docs/the_nimbus_book/src/preparation.md

@@ -0,0 +1,34 @@
+# Mainnet preparations
+
+## Genesis
+
+eth2 will have a `MIN_GENESIS_TIME` of `1606824000` (or for those of you who don’t think in unix time – **December 1, 2020, 12pm UTC**).
+
+To trigger genesis at this time, there must be at least `16,384` validator deposits 7 days prior to December 1. If not, genesis will be triggered 7 days after this threshold has been met (whenever that may be). For a more detailed discussion of how genesis is kicked off, see Ben Edgington’s genesis [excellent writeup](https://hackmd.io/@benjaminion/genesis).
+
+To summarize the above, although Genesis may occur after December 1st, you should be prepared for it to occur on the first. Which means, you should make your deposit no later than **November 24, 2020, 12pm UTC** if you wish to be included in the Genesis block.
+
+> **Tip:** You can keep track of how many deposits are still needed in order for Genesis to be triggered on the [Launchpad homepage](https://launchpad.ethereum.org/).
+
+## Latest software
+
+Please check that you are running the latest stable [Nimbus software release](https://github.com/status-im/nimbus-eth2/releases).
+
+> **Note:** If you are setting up your client before launch, it is your responsibility  to check for any new software releases in the run up to launch. At the minimum you should check the [release page](https://github.com/status-im/nimbus-eth2/releases) weekly.
+
+## More than 20 peers
+
+Please check that your node has at least 20 peers. See [the footer](keep-an-eye.md#keep-track-of-your-syncing-progress) at the bottom of the terminal window for your peer count.
+
+## Validator attached
+
+Please check that your [validator is attached](keep-an-eye.md#make-sure-your-validator-is-attached) to your node.
+
+## VPN
+
+To avoid exposing your validator identity to the network, we recommend you use a trustworthy VPN such as [protonmail](https://protonmail.com/).. This help reduce the risk of revealing your IP address to the network.
+
+## Ethereum Foundation's Checklist
+
+Ad a final check, we recommend you also go through the EF'S [staker checklist](https://launchpad.ethereum.org/checklist).
+