Nethermind as of January 2023 takes about 860 GiB of space on a snap sync, and then grows by ~ 30 GiB/week.
When it starts to fill its disk, it can be online pruned to free up space again.
Caveat that while several folx have used online pruning successfully, there is risk associated with it. The two failure modes that have been reported are:
A typical user of eth-docker is someone who wants to become a validator on the Ethereum network, also known as staking or staker, or someone who is already a validator on the Ethereum network and wants to add more validators to their setup. They can be someone who is going to setup their machine at home, someone who is going to use some kind of VPS to host their setup, or some kind of institutional staker working for large staking services or large investors.
eth-docker is an automation wrapper to run an "Ethereum node", consisting of a consensus layer client, execution layer client, and validator client.
Geth 1.10.23 fixes a bug in 1.10.22, which would have resulted in missing state in its database. The Go-Ethereum team recommends to roll the chain back and let Geth catch up again, if and only if you had updated to 1.10.22. If you did not, just update to 1.10.23 now and call it done.
This is how to roll back to a previous block when using eth-docker.
./ethd update and ./ethd up should do it.
As of August 2022, a 1TB SSD is getting tight to run an Ethereum node in. The recommendation now is for 2TB of space. I wanted to see what it takes to still fit into 1TB.
EIP-4844 will increase space need by another 34 GiB or so. This is a 2023 discussion however.
Syncing an Ethereum node is largely reliant on IOPS, I/O Per Second. Budget SSDs will struggle to an extent, and some won't be able to sync at all.
This document aims to snapshot some known good and known bad models.
For size, 2TB come recommended as of mid-2022. 1TB can work for now but is getting tight.
High-level, QLC and DRAMless are far slower than "mainstream" SSDs.
It's July 2022, Ethereum is preparing for merge. There are plenty of guides on how to get merge-ready for validators, but few for people running RPC nodes now.
| #! /bin/bash | |
| # http://linuxcommand.org/wss0150.php | |
| function error_exit | |
| { | |
| echo "$1" 1>&2 | |
| exit 1 | |
| } | |
| # http://unix.stackexchange.com/questions/70859/why-doesnt-sudo-su-in-a-shell-script-run-the-rest-of-the-script-as-root |
Last updated: 02/7/2022
As of 2022/7/6, Sepolia has switched to PoS. The window to do some mining has closed.
It's mid 2022, Ethereum is still PoW and motoring towards merge / PoS. Surviving testnets will be Sepolia - currently PoW - and Goerli. Ropsten will be merged and then deprecated, Rinkeby and Kovan won't be merged.
I want to "get ready" for some Sepolia testing pre- and post-merge. Sepolia will not have a public validator set; testing post-merge will be limited to running applications on it. As Sepolia is PoW, I can actually go mine myself some SepplETH. Here's how.
| #! /bin/bash | |
| # http://linuxcommand.org/wss0150.php | |
| function error_exit | |
| { | |
| echo "$1" 1>&2 | |
| exit 1 | |
| } | |
| # http://unix.stackexchange.com/questions/70859/why-doesnt-sudo-su-in-a-shell-script-run-the-rest-of-the-script-as-root |