Goldcoin Client Syncing Problems

[MicroGuy]

close the wallet and re-open it

On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.

I made some posts about blockchain stuffing in the past few weeks.. Is this is a different problem ?

There are currently 3 different rogue nodes which intermittently try to sync the wrong chain, but this has been going on for weeks.

Is your wallet still functioning as if up to date ?

If I close the wallet and reopen, it will sync for a few minutes then it goes back out of sync.

We need to get this fixed before we start bringing more users on board. IMO.

[Majormax]

Is this something that cant be hard coded in a new client? Also where is BitcoinFX? didnt he have a lot of ideas in regards to this?

Not being a coder, I don't know what can be done. A determined attacker could always match any new client, I would guess: or attacks may may simply be linked to blockchain code itself (ie new client won't help).

[Majormax]

close the wallet and re-open it

On my machine, this will solve the problem temporarily but then the client goes back out of sync. Also, apparently there is some question as to max coin? Could we get a clarification on these two issues? Thank you.

I made some posts about blockchain stuffing in the past few weeks.. Is this is a different problem ?

There are currently 3 different rogue nodes which intermittently try to sync the wrong chain, but this has been going on for weeks.

Is your wallet still functioning as if up to date ?

If I close the wallet and reopen, it will sync for a few minutes then it goes back out of sync.

We need to get this fixed before we start bringing more users on board. IMO.

What I meant was, you should still be able to send and receive because wallet actually is up to date (the sync. information is fake)

[MicroGuy]

The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?

[hyoshi]

Guys, there is nothing wrong with the client...

Basically nodes need to be added to the conf file (trusted nodes), and you need to limit the # of connections, and set a high ban time.  I'm sure this was in the original thread, because I swapped nodes for this reason with gldcoin.

This occurs when people who offline mined their own large chain try to sync up with the network...

Add this to your conf - if anyone knows of other TRUSTED nodes (If you leave your client/daemon running 24/7 and can forward/open port 8121 on your firewall)

addnode=72.11.149.185
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=6

[hyoshi]

The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?

Its always temporary... Until you have thousands of peers with only a handful being rogue.  When there are only hundreds of peers, and a handful rogue, its likely you will always see this unless you use trusted nodes as above and limit the number of node connections.

[MicroGuy]

The problem is in appearances. Would it be possible to engineer a temporary workaround via a custom config file?

Its always temporary... Until you have thousands of peers with only a handful being rogue.  When there are only hundreds of peers, and a handful rogue, its likely you will always see this unless you use trusted nodes as above and limit the number of node connections.

Thank you for providing us with this invaluable information. I will implement your suggested changes above now. After testing the client using the settings suggested, I will report back with my results.

[MicroGuy]

Okay. That didn't work?

[hyoshi]

did you shut the client and restart?

[MicroGuy]

did you shut the client and restart?

Yes. And I have already tried this configuration or at least variations of it without success. At present, I do not know of a single user with a client that is able to maintain a network sync.

[hyoshi]

I can no problem...  post your config file.  Also, what is the full path/location to your conf file?

[MicroGuy]

I can no problem...  post your config file.  Also, what is the full path/location to your conf file?

Path = /appdata/roaming/GLDcoin

File = gldcoin.conf

gen=0
dns=1
checkpoints=1
listen=0
dnsseed=1
banscore=10
bantime=604800
rescan=1
checkblocks=0
checklevel=6
txindex=1
reindex=1

addnode=72.11.149.185
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=6

[hyoshi]

**addnode=72.11.149.185 DELETE THIS LINE ITS GONE

bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4

Get rid of of all the other lines.  Its not needed.   Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)

If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)

Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.

Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.

[MicroGuy]

**addnode=72.11.149.185 DELETE THIS LINE ITS GONE

bantime=604800
addnode=207.12.89.2
addnode=72.14.178.111
addnode=208.115.109.157
addnode=88.161.131.83
maxconnections=4

Get rid of of all the other lines.  Its not needed.   Its not possible for it to go out of sync if those nodes and pools are legit (1 is mine, the others are pools)

If it does, backup wallet.dat, and gldcoin.conf, and delete all files withing %appdata%/roaming/gldcoin (this is the location you are using right?)

Now, what you need is more public trusted nodes, where people agree to keep their daemon running 24/7/365, and can forward/open port 8121 to the daemon, and have a static IP.

Ideally until the network grows you need a good 12 nodes, and you can then change maxconnections to 12.

I appreciate this information. I'll make these changes tomorrow after I am rested. Goodnight and thank you. 

[hyoshi]

also just to be clear, the path to your conf is %appdata%\roaming\gldcoin\gldcoin.conf and not c:\appdata\roaming\glcoin\glcoin.conf?

let me know tomorrow as I haven't gone out of sync in weeks.