Bitcoin Core 0.11.0 slow block sync.

[1Referee]

Since the version before the 0.11.0 I have to deal with very slow block syncing. Downloading 2 hours worth of blocks can literally take 15 to 20 minutes, which is crazy. Never had this problem before.

Active connections to the Bitcoin network seem to be fine as they are between 8-15 on average.

[Newar]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

[Glucose]

Since the version before the 0.11.0 I have to deal with very slow block syncing. Downloading 2 hours worth of blocks can literally take 15 to 20 minutes, which is crazy. Never had this problem before.

Active connections to the Bitcoin network seem to be fine as they are between 8-15 on average.

Same for me. It's really slow.. Not sure if I'll be able to keep using Bitcoin Core wallet for a long time..

[1Referee]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

Yeah, it's the same system. Hardware shouldn't be an issue as it is just a few years old. Checking blocks isn't the problem, it's purely the syncing process.

Since the version before the 0.11.0 I have to deal with very slow block syncing. Downloading 2 hours worth of blocks can literally take 15 to 20 minutes, which is crazy. Never had this problem before.

Active connections to the Bitcoin network seem to be fine as they are between 8-15 on average.

Same for me. It's really slow.. Not sure if I'll be able to keep using Bitcoin Core wallet for a long time..

Well, for me Bitcoin Core is the only pc wallet I will use because it does was what I want, but lately it's quite annoying having to wait so long to just sync a few hours worth of blocks while it only took 2 or 3 minutes with the previous versions.

[Newar]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

Yeah, it's the same system. Hardware shouldn't be an issue as it is just a few years old. Checking blocks isn't the problem, it's purely the syncing process.

There's a small chance that all the peers you're connected to are slow. Close it and delete peers.dat. On the next start it will get fresh peers. Or if you know a quick node you can add it manually with the -addnode=<ip> command. You can submit it on the command line, conf file or debug window.

[1Referee]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

Yeah, it's the same system. Hardware shouldn't be an issue as it is just a few years old. Checking blocks isn't the problem, it's purely the syncing process.

There's a small chance that all the peers you're connected to are slow. Close it and delete peers.dat. On the next start it will get fresh peers. Or if you know a quick node you can add it manually with the -addnode=<ip> command. You can submit it on the command line, conf file or debug window.

Did everything you mentioned but with no success so far. I noticed yesterday that while the wallet showed it is 28 hours behind, an incomming transaction popped up made 2 hours before opening my wallet to sync. Which is quite weird as the wallet was showing it was more than a day behind. Does that mean it does sync properly and the problem is in fact the wallet showing incorrect information?

[lama-hunter]

I really glad to use the v.11 since it updates much faster and my wallet keeps all the Time up to Date

[tommorisonwebdesign]

I am having the exact same problem on OS X.

[achow101]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

Yeah, it's the same system. Hardware shouldn't be an issue as it is just a few years old. Checking blocks isn't the problem, it's purely the syncing process.

There's a small chance that all the peers you're connected to are slow. Close it and delete peers.dat. On the next start it will get fresh peers. Or if you know a quick node you can add it manually with the -addnode=<ip> command. You can submit it on the command line, conf file or debug window.

Did everything you mentioned but with no success so far. I noticed yesterday that while the wallet showed it is 28 hours behind, an incomming transaction popped up made 2 hours before opening my wallet to sync. Which is quite weird as the wallet was showing it was more than a day behind. Does that mean it does sync properly and the problem is in fact the wallet showing incorrect information?

It means that it received the transaction when it was broadcast, but has not synced the blockchain up yet. This is normal as the client will still receive transactions and data from nodes as it syncs. The transaction should still say unconfirmed in your wallet even when it is confirmed because the blockchain is not up to date so it does not know whether the block confirming the transaction is legit or not until it syncs.

[1Referee]

it need not necessarily be a slow download. Checking the blocks takes probably more time these days. This depends on your hardware. Is everything the same system wise if you compare to the system you ran earlier versions on?

Yeah, it's the same system. Hardware shouldn't be an issue as it is just a few years old. Checking blocks isn't the problem, it's purely the syncing process.

There's a small chance that all the peers you're connected to are slow. Close it and delete peers.dat. On the next start it will get fresh peers. Or if you know a quick node you can add it manually with the -addnode=<ip> command. You can submit it on the command line, conf file or debug window.

Did everything you mentioned but with no success so far. I noticed yesterday that while the wallet showed it is 28 hours behind, an incomming transaction popped up made 2 hours before opening my wallet to sync. Which is quite weird as the wallet was showing it was more than a day behind. Does that mean it does sync properly and the problem is in fact the wallet showing incorrect information?

It means that it received the transaction when it was broadcast, but has not synced the blockchain up yet. This is normal as the client will still receive transactions and data from nodes as it syncs. The transaction should still say unconfirmed in your wallet even when it is confirmed because the blockchain is not up to date so it does not know whether the block confirming the transaction is legit or not until it syncs.

Once it popped up it showed it got 2 confirmations while it was 28 hours behind according to the wallet. This makes me think there is a bug active that shows incorrect information while in fact everything works fine in the background.

[achow101]

Once it popped up it showed it got 2 confirmations while it was 28 hours behind according to the wallet. This makes me think there is a bug active that shows incorrect information while in fact everything works fine in the background.

I don't think there is a bug.

Did you check a block explorer to see if that transaction actually just came in and had two confirmations? Sometimes Bitcoin Core shows the notification for transactions that you had received around the time that the or is currently synced up to.

[LFC_Bitcoin]

I really glad to use the v.11 since it updates much faster and my wallet keeps all the Time up to Date

Same here, I upgraded to v.11.0 the other night & it seems a lot better than v.10.2 which is what I had previously, I was having problems even opening my wallet before & sometimes it'd get syncing. It's been perfect since I started using v.11.0 though, haven't encountered any problems so far.