From b9ed48d42b17426ea749beb0715b2fe1e3cf1ea2 Mon Sep 17 00:00:00 2001 From: yslcrypto Date: Mon, 30 Nov 2020 12:05:02 +0100 Subject: [PATCH] Pi guide: mainnet advice update --- docs/the_nimbus_book/src/pi-guide-mainnet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/the_nimbus_book/src/pi-guide-mainnet.md b/docs/the_nimbus_book/src/pi-guide-mainnet.md index 08f313d66..1f3e2d8b0 100644 --- a/docs/the_nimbus_book/src/pi-guide-mainnet.md +++ b/docs/the_nimbus_book/src/pi-guide-mainnet.md @@ -2,7 +2,7 @@ Whether or not your Pi is up to the task will depend on a number of factors such as SSD speed, network connectivity, etc. So it's best to verify performance on a testnet first. -The best thing you can do is to set your Pi to run Pyrmont. If you have no trouble syncing Pyrmont, your setup should be more than good enough for mainnet as well (Mainnet is expected to use fewer resources). +The best thing you can do is to set your Pi to run Pyrmont. **If you have no trouble syncing and attesting on Pyrmont, your setup should be more than good enough for mainnet** as well (Mainnet is expected to use fewer resources).

We've been running lots of PIs and NanoPCs 24/7 for 3 years and never got a hardware fail. It is easy (and cheap) to get redundancy of components (even spare PIs in different locations, more of this to come).

— Ethereum on ARM (@EthereumOnARM) November 28, 2020