NA

[pijpenstelen]

With all the troubles NLG has had last couple days gives me a big smile for the following reasons.

1. This is obviously the only coin they have which means all focus will be on it. Devs must be new to this.
2. Team worked hard to get problems resolved, this would of killed off a lot of scam coins.

So Well done!

1 suggestion is to try get a dev with some more experience for future updates because when coin has more exchanges and pools it will become harder.

[1714945496]

1714945496

[1714945496]

1714945496

[1714945496]

1714945496

[1714945496]

1714945496

[thsminer]

it looks like nlg.pool.mn updated.

yes changed it at ann

now he only need to do something about the transactions, it show now 0.0000

I see now that my wallet is synced at block 32098.

nlg.hashfever.com is also on block 32098. I see nlg.pool.mn now on block 32080?

Diff is 5.22 on hashfever and 2.88 on nlg.pool.mn at the same time?

Maybe refresh is not active on pool.mn.

pool.mn seems to be on the wrong fork... so if there are peóple mining there their hashes are worthless.

It was ok, until just now.

maybe only their stats are frozen but to be sure I already send pool.mn a message

They where on the wrong fork for days so I doubt you'l ever see those coins...

[bramvnl]

guldencoin.conf


rpcuser=user
rpcpassword=password
rpcport=9232
rpcallowip=127.0.0.1
server=1
daemon=1
listen=1
addnode=192.227.231.34
addnode=192.227.231.43
addnode=72.46.152.82
addnode=94.23.164.74

[thsminer]

With all the troubles NLG has had last couple days gives me a big smile for the following reasons.

1. This is obviously the only coin they have which means all focus will be on it. Devs must be new to this.
2. Team worked hard to get problems resolved, this would of killed off a lot of scam coins.

So Well done!

1 suggestion is to try get a dev with some more experience for future updates because when coin has more exchanges and pools it will become harder.

I totaly agree!

For some strange reason I believe in this coin from the start and despite the problems of the past days my confidence only grew.

[Glen Hoddle]

With all the troubles NLG has had last couple days gives me a big smile for the following reasons.

1. This is obviously the only coin they have which means all focus will be on it. Devs must be new to this.
2. Team worked hard to get problems resolved, this would of killed off a lot of scam coins.

So Well done!

1 suggestion is to try get a dev with some more experience for future updates because when coin has more exchanges and pools it will become harder.

Well this gives us a big smile! Thank you very much for your kind words of encouragement. Our team is extremely dedicated and did not get much sleep, but all of this work is worth it. The community has been absolutely amazing. We have received so much support and I am sure we couldn't have done it without all of you! Your suggestion hits it right on the nose and we are currently working together with a very good and experienced dev. We hope to announce him soon as our new team member.

The last couple of days have been very messy, but we had to do this update to get a stable coin. KGW works as expected now and the crazy difficulty changes are gone. When everybody is on the right chain we will start analyzing the possible damage and make a plan for compensation.

Please contact us (pm, website, twitter, facebook, mail) if you have any questions. Thanks!

I would suggest you contact Bittrex to make sure they are up to date. My coins are still not there (several hours now)

[Glen Hoddle]

My coins are now showing as pending. It seems Bittrex is having a few database connectivity problems at the moment.

[thsminer]

My coins are now showing as pending. It seems Bittrex is having a few database connectivity problems at the moment.

Live was sooo easy 25 years back, no cellphones, no internet, no forks and no exchanges that do not move your funds in and instant... But despite all commotion, I enjoy every minute of this chaos    

[BlackB]

it looks like nlg.pool.mn updated.

yes changed it at ann

now he only need to do something about the transactions, it show now 0.0000

I see now that my wallet is synced at block 32098.

nlg.hashfever.com is also on block 32098. I see nlg.pool.mn now on block 32080?

Diff is 5.22 on hashfever and 2.88 on nlg.pool.mn at the same time?

Maybe refresh is not active on pool.mn.

pool.mn seems to be on the wrong fork... so if there are peóple mining there their hashes are worthless.

It was ok, until just now.

maybe only their stats are frozen but to be sure I already send pool.mn a message

They where on the wrong fork for days so I doubt you'l ever see those coins...

I send those coins to my wallet before the problems started.

[thsminer]

I send those coins to my wallet before the problems started.

Before the 18th in the evening?

[BlackB]

I send those coins to my wallet before the problems started.

Before the 18th in the evening?

No after, last payment was about 19-4 23:01

[veertje]

With all the non-up-to-date pools, it seems about the right time to announce my p2pool node at http://gulden.p2p.0x0a.nl:27100 (0.9% fee), set up with the help of Spekske's source at https://github.com/Spekske/p2pool-rav (thanks Spekske!). It has successfully joined the p2pool network - all are welcome to come revive four centuries of Dutch history!

Sample code:

Code:

minerd -a scrypt -o stratum+tcp://gulden.p2p.0x0a.nl:27100 -u YOURGULDENCOINADDRESSHERE

I see wrong blocknumbers at your stats??? Current blockfind is 33684. Your stats say 42152 on april 14th.  Doesn't seem right.


http://gulden.p2p.0x0a.nl is not ok and on the wrong chain as it seems. Or is it just the stats?

[thsminer]

I send those coins to my wallet before the problems started.

Before the 18th in the evening?

No after, last payment was about 19-4 23:01

At that moment they did send your coins  out on the wrong chain.  
Contact the poolowner and mail him the txids out of the transaction overview. I hope he's able to fix this.

[BlackB]

I send those coins to my wallet before the problems started.

Before the 18th in the evening?

No after, last payment was about 19-4 23:01

At that moment they did send your coins  out on the wrong chain.  
Contact the poolowner and mail him the txids out of the transaction overview. I hope he's able to fix this.

Contact form on their website is not working...anyone know mail adres of nlg.pool.mn

[Svener]

Looks like I missed a lot of stuff this easter weekend, my wallet is now on correct blockchain and all my coins still there, it was bad time for update especially for pool owners who might of been on vocation but good job getting issues resolved.

Lets hope things get better for NLG now, I still think this currency has best chance out of all the country coins with it's supply and what looks to be a dedicated and caring team.

[TamiLee]

I am starting to think NLG is a practical coin to use as a currency. I will keep close eye on this one.

[0btc]

With all the non-up-to-date pools, it seems about the right time to announce my p2pool node at http://gulden.p2p.0x0a.nl:27100 (0.9% fee), set up with the help of Spekske's source at https://github.com/Spekske/p2pool-rav (thanks Spekske!). It has successfully joined the p2pool network - all are welcome to come revive four centuries of Dutch history!

Sample code:

Code:

minerd -a scrypt -o stratum+tcp://gulden.p2p.0x0a.nl:27100 -u YOURGULDENCOINADDRESSHERE

I see wrong blocknumbers at your stats??? Current blockfind is 33684. Your stats say 42152 on april 14th.  Doesn't seem right.


http://gulden.p2p.0x0a.nl is not ok and on the wrong chain as it seems. Or is it just the stats?

Ouch. The stats were (and still are) definitely off as the client showed block 33534 at that time* instead of 42152, but that still indicated a gap of 150 blocks. The node was connected to 9 other nodes, but apparently it was on the wrong chain indeed; now that I've added the seed nodes in the configuration as per page 1 (which I should've done at the beginning), it's successfully getting to block 33737. Interestingly in the other chain block 33535 was the latest at 17:48 GMT, i.e. a long time without a block, and a much shorter chain. I'm not sure how my node got stuck on the wrong chain, but since adding the nodes fixed it for me (and resetting the blocks/chainstate), perhaps they could be hard-coded into the client?

Fortunately in a way, the only other miner on the pool beside me did 1.6 kH/s for well under an hour. My sincere apologies to miner Gebjfv4CbdpqJMqnC8Ajvbt1aoMEQEVd72, and to the Guldencoin team as well. I screwed the pooch!. Big thanks to you veertje - good catch (although the p2pool stats might still be off)!

Having reset the Gulden client and p2pool daemon, I can now actually confirm that the p2pool node is working - addresses mining on http://gulden.p2p.0x0a.nl:27100/ show up successfully on http://dutchpool.org:27100/current_payouts after getting a share.

Additionally, I've now made my node public (addnode=gulden.p2p.0x0a.nl) and upped the maxconnections in the hope that that might help resolve some isolated nodes, particularly those that were connected to gulden.p2p.0x0a.nl earlier and received wrong blocks as well :/

* I've seen the stats problem before with p2pool, but as the only difference between Spekske and my node should be the front-end (same p2pool code for the backend), I might finally be able to find out why this happens - if I can find the functional difference!

[veertje]

Big thanks to you veertje - good catch (although the p2pool stats might still be off)!

You're welcome. Good work and fine you read it on time and made it work! Another one on the good chain.

[bramvnl]

I have change the page on reddit new wallet links to 1.1.4 and set the new .conf

http://www.reddit.com/r/GuldenCoin/comments/234dyi/guldencoin/

[Coincookie]

http://www.guldencoinforum.com

[Glen Hoddle]

Hardcoreminers Block: 33792

Guldencoin miner-pool Block: 33845