Quote from: mineru on February 06, 2017, 07:27:16 AM

Quote from: chrysophylax on February 06, 2017, 05:14:23 AM

Quote from: darkgold on February 05, 2017, 02:36:04 PM

Quote from: mineru on February 05, 2017, 08:12:23 AM

Hello!
My wallet is having issues syncing. Using version 1.1. Around 12 hours behind and growing. Yesterday it was just 3 hours behind. It is syncing but so slow blocks are being created faster than the wallet is downloading the blocks. All this with almost 100% disk resources and heavy CPU use.
Any suggestions?

Here is current bootstrap.dat file util block height: 713848, close wallet application, copy bootstrap.dat to roaming/goldblocks folder, delete everything except wallet.dat , then start and resync wallet.
It will take some time, but you will have synced Goldblocks wallet on correct chain. When POW is over in about 4 months that will not happen any more.

https://drive.google.com/open?id=0B9CsT1LO8rRUMjQ3a2R6ZFBsUk0

name of file: goldblocks.conf
rpcuser=User@
rpcpassword=Pass@
rpcport=26920
port=27920
server=1
listen=1
daemon=1
rescan=0
reindex=0
defaultkey=1
logtimestamps=1
maxconnections=100
verifychain=1
dns=1
rpcthreads=100
addnode=node1.goldblocks.eu
addnode=node2.goldblocks.eu
addnode=node3.goldblocks.eu
addnode=node4.goldblocks.eu
addnode=node5.goldblocks.eu
addnode=node6.goldblocks.eu
addnode=node7.goldblocks.eu

config file download

bootstrap.dat download
~block 713,848

the bootstrap is a copy of the blocks that are in the current blockchain ...

the wallet still has to download the rest of the components - but the blocks are always available via the bootstrap ...

for this reason - it still takes a while for the sync to happen - but its a lot faster than the wallet continuously looking for peers ...

the fastest way is obviously have a complete copy of the blockchain - but that is a bigger download again ...

as for the cpu usage - that is a code optimization issue and needs to be looked at IF it becomes a major problem ...

#crysx

Cool. It is slowly rebuilding now. Thanks darkgold! Thanks crysx!

all good ...

just remember - that the pool daemon is setup as a full node also ( without staking ) ...

so you could also use the pool address as a node to add also - with or without the p2p port ...

Code:

addnode=pool.chainworksindustries.com ...

or ...

addnode=pool.chainworksindustries.com:27920 ...

using the p2p port will help the wallet you have running to access the blockchain - even when starting a new wallet or blockchain sync ...

hope that helps a little more also Wink

...

i dont understand why the wallet / daemon doesnt just auto-sync - as the seednodes that have been setup are hardcoded in the wallet / daemon ... but anyway - it is what it is ...

#crysx