https://tech.uvoo.io/index.php?action=history&feed=atom&title=Ethereum_Node_RequirementsEthereum Node Requirements - Revision history2026-05-10T15:54:25ZRevision history for this page on the wikiMediaWiki 1.35.2https://tech.uvoo.io/index.php?title=Ethereum_Node_Requirements&diff=150&oldid=previmported>Jeremy-busk at 20:23, 27 February 20192019-02-27T20:23:06Z<p></p>
<p><b>New page</b></p><div><br />
# Parity<br />
<br />
https://wiki.parity.io/FAQ#what-are-the-parity-ethereum-disk-space-needs-and-overall-hardware-requirements<br />
<br />
Dec 2018<br />
```<br />
Client / Mode | Block Number | Disk Space | CLI flags |<br />
=========================|================|============|==============================|<br />
parity +light +hardcoded | 6_850_000 | 14M | --light |<br />
parity +light | 5_600_000 | 89M | --light ---no-hardcoded-sync |<br />
parity +warp -ancient | 6_850_000 | 29G | --no-ancient-blocks |<br />
parity +warp | 6_850_000 | 133G | |<br />
parity -warp | 6_850_000 | 133G | --no-warp |<br />
parity -warp +archive | 6_850_000 | 1.8T | --pruning archive |<br />
```<br />
<br />
# Geth<br />
<br />
<br />
```<br />
3 ways you can do sync to network:<br />
<br />
--syncmode full: Geth client will download Block header + Block data + full Validation [Is called eth full node]<br />
<br />
--syncmode fast: Geth client will download Block header + Block data + validate for last 1k transactions.<br />
<br />
--syncmode light: Geth client will download Current state + Asks nodes for as its need. [Light node [It will request missing blocks from full nodes]<br />
<br />
You can change syncmode my specifying --syncmode along with command prompt. fast is good. But if you dont have time and space try to use light.<br />
<br />
```<br />
<br />
<br />
https://medium.com/coinmonks/analyzing-the-hardware-requirements-to-be-an-ethereum-full-validated-node-dc064f167902<br />
<br />
https://ethereum.stackexchange.com/questions/65509/2019-specs-for-running-geth-full-node<br />
```<br />
<br />
62<br />
<br />
I'll take my shot. Experts, please correct me.<br />
<br />
"Full" Sync: Gets the block headers, the block bodies, and validates every element from genesis block.<br />
<br />
Fast Sync: Gets the block headers, the block bodies, it processes no transactions until current block - 64(*). Then it gets a snapshot state and goes like a full synchronization.<br />
<br />
Light Sync: Gets only the current state. To verify elements, it needs to ask to full (archive) nodes for the corresponding tree leaves.<br />
<br />
EDIT (*) in newer version of geth it's -64<br />
<br />
fsMinFullBlocks = 64 // Number of blocks to retrieve fully even in fast sync<br />
<br />
<br />
A Geth node with Fast sync is around 130GB (source). <br />
However, according to this article, once Geth is done with Fast sync, it switches to full (archive) sync. <br />
With a Parity Archive node approaching 2TB (source) you can expect at least that much in disk-space (SSD with high i/o). <br />
Running a stable node is a challenge, so you may want to look into a service like QuikNode (cloud node-as-a-service), which offers Archive nodes w/ full chain data since genesis block.<br />
```</div>imported>Jeremy-busk