When the chain reaches a recent state (head - 1024 blocks), geth switches to full sync mode, import the remaining blocks and process them as in the classical sync (full) to obtain a full node. Instead of processing all the transactions that ever happened, fast sync downloads all the transaction receipts and the entire recent state database and perform a PoW verification. At the end of the process, the node is a full node.įast sync: A fast sync also downloads all the data (block headers and block bodies) but exchanges processing power for bandwidth usage. This method is the most traditional and stable but can take a very a long time (up to a few weeks) and would require a more powerful machine. Here is a summary of the different options available to synchronise the Ethereum blockchain with Geth (Go-Ethereum):įull sync: A full sync downloads all the data (block headers and block bodies), processes the entire blockchain one link at a time, and replays all transactions that ever happened in history (transaction processing and PoW verification). Syncing Ethereum has always been a pain point for many people because it's a complex process with multiple options, including different verification modes which requires different setup that can cost a lot of money and takes weeks to sync. So I was really excited to try to sync an Ethereum Full Node on the number one Single-Board Computer (SBC). My wife recently offered me the latest Raspberry Pi 4 (model B) 4GB.
Running an Ethereum Full Node on a RaspberryPi 4 (model B)
0 kommentar(er)
