Goldcoin Client Syncing Problems

[tadspoles]

I have ONLY the following lines on my client and it is working with no problems:

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


Having said that, it obviously can't stay this way but with the base being small perhaps it should be this way for now.  I believe these are the pool addresses and/or the addresses to the daemon run by the exchanges.

Hyoshi recommended getting at least 12 trusted nodes up and putting those in.  Sounds like a good game plan to me to start with. 

I can't say for certain though, but just because it WILL be a fully functional p2p system doesn't mean it MUST start that way and if we don't trust the pools or the exchanges as a beginning then what do we have?

It would be nice to have comments beside each addnode line saying who they are.

[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.

I can confirm that so far this is stopped the client resync issue. I have had this running for about 2 hours and normally in this time the client would have tried to re-sync.

This will stop the resync issue, however it also makes it so your client only talks to the nodes you just put in your configuration file.  This means the network is now rather limited and can not grow.  It is also no longer really peer to peer and instead depends on a few nodes. With this configuration there is no need for this to be a blockchain based, p2p currency,  it  could just become a centrally controlled currency instead.    This also will make testing the real fix harder and make it so you have to get people fix their configuration files when any of these nodes ever go down.    Bad suggestion overall.

Only "connect" does this - not "addnode".    With addnode, if a node goes down, another available node is used that's not trusted.  No one runs the wallet with the firewall open so they have 100 connections - most people only use a max of 6 - 12 connections to peers.

Once could easily change the max connections to say 12, and have a 75% change of getting a misbehaving node.

The fix is a larger network.  Its impossible for misbehaving nodes to be eliminated.  You do understand that right?

This is why it hasn't been fixed in Bitcoin, Litecoin, Novacoin, and the list goes on.  the only fix is no wannabe hax0rs trying to force a false blockchain down the network's throat.

Who are you by the way?  which btcointalk troll?  Why not use your real name?

[hyoshi]

I have ONLY the following lines on my client and it is working with no problems:

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


Having said that, it obviously can't stay this way but with the base being small perhaps it should be this way for now.  I believe these are the pool addresses and/or the addresses to the daemon run by the exchanges.

Hyoshi recommended getting at least 12 trusted nodes up and putting those in.  Sounds like a good game plan to me to start with. 

I can't say for certain though, but just because it WILL be a fully functional p2p system doesn't mean it MUST start that way and if we don't trust the pools or the exchanges as a beginning then what do we have?

It would be nice to have comments beside each addnode line saying who they are.

Trust me, its still p2p.  the network is way too small to function without trusted nodes.

He claims it can be fixed - but it can't.  Trust me, if it could, coblee would have done so in Litecoin - same with BTC - and this is Litecoin - with slight modifications to the reward and difficulty systems.

[tadspoles]

I would also very much like to spread some gld to those that honestly help this grow.  I don't need as much gld as I have and my miners keep plugging away making more.

[Marink]

Quoting something from our recent talk in our group:"if there is code that is being used by other coins to resolve these issues, why don't we find it and copy it".
Obviously you can't just copy it, but you can modify it and make it work for gld.

We don't know what's causing syncing problems right?

[tadspoles]

According to Hyoshi the problem is:

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

His solution is in the comments above.  It is working for me and I think should be posted on the default instructions.  He says we should also try to get 12 trusted nodes put up that have the daemon running 24/7 and add those to the gldcoin.conf file.

I agree with him.

[tadspoles]

In other words, the code is solid.  It's just where we are at right now with the state of the network and nodes/miners on it.

[MicroGuy]

Since adding the following configuration file suggested above, my client has remained in sync continuously for several hours. This will serve as the temporary workaround until we have a better solution.

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

I will update the OP of the main bitcointalk thread now.

[AZIZ1977]

maybe i am doing something wrong but changing the conf. file as said didnt help for me. After 5 minutes the client started resyncing.

[tadspoles]

Paste your conf file here without any passwords.  Also, are you solo mining?

If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta.  Paste your version.


Also, what is the full path to your gldcoin.conf file?

Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf    Yes, my real name is tadspoles. 


You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier.  Just make sure you have a good backup.

[AZIZ1977]

Paste your conf file here without any passwords.  Also, are you solo mining?

If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta.  Paste your version.


Also, what is the full path to your gldcoin.conf file?

Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf    Yes, my real name is tadspoles. 


You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier.  Just make sure you have a good backup.

I am not solo mining.

I am running same Client version  v0.6.4.0-gd5eb490-beta.

My full path to gldcoin.conf file is C:\Users\NZXT\AppData\Roaming\GLDcoin\gldcoin.conf 

Conf. file:

rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0

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

[tadspoles]

If it were me, I'd delete the following:

rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0

leaving only:

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


Then I'd save the file, shutdown GLDCoin-QT and restart it.  See how that goes first.  Then we'll go from there.  First we'll get it working with just:

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

[MicroGuy]

Paste your conf file here without any passwords.  Also, are you solo mining?

If I do a help/about within GLDCoin-Qt I am running this version v0.6.4.0-gd5eb490-beta.  Paste your version.


Also, what is the full path to your gldcoin.conf file?

Mine is C:\Users\tadspoles\AppData\Roaming\GLDcoin\gldcoin.conf    Yes, my real name is tadspoles. 


You may have to backup, uninstall, delete all the folders, reinstall, restore wallet.dat and gldcoin.conf if this doesn't work as Hyoshi said earlier.  Just make sure you have a good backup.

I am not solo mining.

I am running same Client version  v0.6.4.0-gd5eb490-beta.

My full path to gldcoin.conf file is C:\Users\NZXT\AppData\Roaming\GLDcoin\gldcoin.conf 

Conf. file:

rpcuser=****
rpcpassword=****
rpcallowip=127.0.0.1
rpcport=8122
port=8121
daemon=1
server=1
gen=0

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

Try commenting out everything except this:

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

Then close and reopen the client.

[AZIZ1977]

conf. file now looks like this.

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

Deleted Gldcoin totally and removed all files. Installed the client again, placed wallet and conf file back. And testing the client to look if it starts to resync. 

[AZIZ1977]

i think the sync problem for me is solved for now and hope it stays so.