One of the most common problems with the Ethereum Wallet application is keeping the blockchain te sync with the Ethereum network. This pagina describes some of the common issues users may encounter while attempting to sync the blockchain and potential methods to work around the problems.
Note that Ethereum Wallet will not display your account balance correctly when it is not synced fully or correctly.
Incapable To Sync
Check that your the clock on your laptop is close to real time. Switch your system settings so that your system clock is synced to an NTP (Network Time Protocol) server.
Slow Syncing Inbetween Blocks Two,283,397 And Two,717,576
You may be encountering some problems syncing Ethereum Wallet (or Nevel) to the Mainnet blockchain. A common problem when syncing Ethereum Wallet’s blockchain gegevens is that the syncing slows down inbetween blocks Two,283,397 and Two,620,384 due to the attack on the Ethereum network (reference Why is my knot synchronization stuck/enormously slow at block Two,306,843?).
The syncing also slows down inbetween blocks Two,675,055 and Two,717,576 due to the state clearing process to liquidate the 20 million empty accounts created by the network attack.
How to recover from slow syncing?
If you have a problem with slow syncing, the easiest way to recover from this slowdown is to eliminate your blockchain gegevens and restart Ethereum Wallet. Ethereum Wallet will then perform a rapid sync which skips overheen thesis attack blocks.
WARNING: Make sure you back up your keystore directory so you don’t accidentally delete your account information.
Shut down Ethereum Wallet.
Depending on your operating system, you will find the chaindata subdirectory ter:
- Linux – $Huis/.ethereum/geth
- OS/X – $Huis/Library/Ethereum or $Huis/Library/Ethereum/geth
- Windows – %APPDATA%/Ethereum
Eliminate the chaindata directory.
Alternatively, you can run geth removedb to liquidate the blockchain gegevens.
Embark Ethereum Wallet. It should now embark quick syncing the blockchain gegevens. Alternatively, run geth –syncmode “prompt” –cache 1024 console and then begin Ethereum Wallet.
Refer to Network Ports, Files And Directories for more information on the location of Ethereum software files and directories on your laptop.
Another method to reduce sync-time is to run your copy of the blockchain from a Solid State Drive (SSD) spil rotational drives are much more affected by the I/O generated by the clearing process, if you are running a utter sync.
How can I tell if my knot client is swift syncing or not?
Compare your logging messages with the following logging messages to determine whethere your knot client is swift syncing or normal syncing.
Quick Sync Te Progress
The following messages are displayed on the `geth –syncmode “swift” console` (pre 1.6.0) screen – note the header(s) and receipt(s):
And following is the omschrijving geth 1.6.0 (Testnet) message during a swift sync:
Quick Sync Just Finished, Transitioning To Normal Sync
Here is the transition when the `–syncmode “quick”` syncing (pre 1.6.0) has ended and normal syncing starts:
And following is the omschrijving geth 1.6.0 message during the transition:
Normal Sync Te Progress
And the following messages are displayed on the `geth console` (pre 1.6.0) screen – note the block(s):
And following is the omschrijving geth 1.6.0 message from a utter sync transitioning to incremental single block updates. The blocks will sync ter batches, and when your blockchain gegevens is up to date, single blocks are received approximately every 14 seconds:
Use Parity Knot Client And User Interface
You can use Parity and commence the Parity syncing using the following instruction line parameter for a reasonably quick sync:
You can access the Parity user interface by navigating te your browser to http://localhost:8080 .
Use Parity Knot Client With Ethereum Wallet
You can use Parity spil a back end to Ethereum Wallet. Commence Parity with the following guideline line
You can then commence Ethereum Wallet and it will connect to your Parity example.