GoldCoin™ (GLC) Thread - The Gold Standard of Digital Currency [OFFICIAL THREAD]

[BitcoinEXpress]

Our pool got to over 200Mhs and had many problems.  Many successful blocks but now all orphans.
Perhaps this was a contribution to the coin's problem right now? It really needs ...something.  The 51% protection works i suppose since the pool became more than 51% of the mining (i'm guessing)  I don't know what to tell the miners now who are still miming.  Im going to shut it down soon to see what happens.   gld.minepool.net

Your pool never mined on the official chain.

You created a fork instantly and ran with it, hence all the orphans.


~BCX~

Not true.. it was on the same chain as cryptsy's client the whole time.  I did test transactions to cryptsy to check.

It was doing the same thing several other people's clients are doing. Hoping chains.

I'm not knocking GLD, quite the opposite.

Hope they get this solved.


~BCX~

[1714188170]

1714188170

[1714188170]

1714188170

[1714188170]

1714188170

[1714188170]

1714188170

[1714188170]

1714188170

[1714188170]

1714188170

[MarKusRomanus]

Our pool got to over 200Mhs and had many problems.  Many successful blocks but now all orphans.
Perhaps this was a contribution to the coin's problem right now? It really needs ...something.  The 51% protection works i suppose since the pool became more than 51% of the mining (i'm guessing)  I don't know what to tell the miners now who are still miming.  Im going to shut it down soon to see what happens.   gld.minepool.net

Your pool never mined on the official chain.

You created a fork instantly and ran with it, hence all the orphans.


~BCX~

Not true.. it was on the same chain as cryptsy's client the whole time.  I did test transactions to cryptsy to check.

It was doing the same thing several other people's clients are doing. Hoping chains.

I'm not knocking GLD, quite the opposite.

Hope they get this solved.


~BCX~

That sounds about right.  I believe somehow the 51% attack defense eventually led to the pool forking.. maybe all of them.  Solo mining with only 1Mhs on a separate coin client.. i got the same thing.

[MarKusRomanus]

well.. I restarted the gld.minepool.net pool up again and its hitting blocks.  We're still on the same chain as cryptsy.com too.   I set up a new goldcoin pool on another server and network here in hopes of getting some of the miners to disperse!
gld.cryptcoins.net

I'm assuming that if we don't spread out .. its all going to happen all over again...and it then seems to affect the whole hasing network overall, not just the one mining pool.

[MarKusRomanus]

well i spoke too soon.. 30 min later my pool goes up to 70Mhs and the blocks (many with over 10 confirms) turn to orphans. 

[MicroGuy]

There is a slight issue with the difficulty calculation. These problems are being addressed and a patch will be made available soon.

[micax1]

There is a slight issue with the difficulty calculation. These problems are being addressed and a patch will be made available soon.

will it allow solominers with small hashpowers like 2mhash mine?

[MicroGuy]

There is a slight issue with the difficulty calculation. These problems are being addressed and a patch will be made available soon.

will it allow solominers with small hashpowers like 2mhash mine?

At this time mining will yield unpredictable results due to the erroneous difficulty numbers. In a nutshell, the client basically thinks the network hashrate is low, when in fact the network hashrate is medium/high. The developers are in the process of making a minor adjustment to the way the difficulty is calculated which should resolve most of the mining issues. Transactions are unaffected.

We will be providing a comprehensive explanation a little later this afternoon.

[BitcoinEXpress]

At this time mining will yield unpredictable results due to the erroneous difficulty numbers. In a nutshell, the client basically thinks the network hashrate is low, when in fact the network hashrate is medium/high. The developers are in the process of making a minor adjustment to the way the difficulty is calculated which should resolve most of the mining issues. Transactions are unaffected.

We will be providing a comprehensive explanation a little later this afternoon.

@Microguy

I'm not being confrontational here but simply pointing out the fact, that a simple diff issue would not wipe out wallets.

I as well as several others have lost varying amounts of GLD due to syncing and re-syncing with multiple chains. You may very well have a diff issue, but you also have a forking issue I think is related to your defense mechanism.


~BCX~

[akumaburn]

At this time mining will yield unpredictable results due to the erroneous difficulty numbers. In a nutshell, the client basically thinks the network hashrate is low, when in fact the network hashrate is medium/high. The developers are in the process of making a minor adjustment to the way the difficulty is calculated which should resolve most of the mining issues. Transactions are unaffected.

We will be providing a comprehensive explanation a little later this afternoon.

@Microguy

I'm not being confrontational here but simply pointing out the fact, that a simple diff issue would not wipe out wallets.

I as well as several others have lost varying amounts of GLD due to syncing and re-syncing with multiple chains. You may very well have a diff issue, but you also have a forking issue I think is related to your defense mechanism.


~BCX~

The forking issue only exists because the diff isn't adjusting properly, too many competing side chains simply because the low difficulty makes it easy to be as such. (Lower difficulty == easier to compete with network)

I'm working on a fix as we speak,

It'll probably require a forking patch though.

[Tommo_Aus]

Great to hear! Will we get an add node to complement the wallet update to make sure we're on the right chain?

[MicroGuy]

Thanks for these words of encouragement!  

Sorry if I've been a little grumpy today I lit up some Frankincense in my office and became overwhelmed with smoke because I put too much frank on the fire. I kid you not. You know what they say about too much of a good thing.

Anyway that led to a massive migraine type head-thumper and sick stomach. If a hit the delete button too quick today that may have played a role.    I feel better now and my office is finally clear of smoke.

In regards to the update, the guys are still turning a few dials and tightening a couple of screws.

More news to follow........

[micax1]

goldcoin removed from http://www.coinwarz.com/ ?

[MicroGuy]

goldcoin removed from http://www.coinwarz.com/ ?

You would need to ask them. Perhaps they are waiting until the difficulty adjustment is working.

[MicroGuy]

Goldcoin Version 0.7.1.6 release is imminent.

[MarKusRomanus]

upgrading gld.minepool.net and gld.cryptcoins.net right now.

Thanks for the hard work, developers.  crossing my finger that this does the trick!

[MicroGuy]

The Goldcoin development team has just released mandatory software update V 0.7.1.6.

Fixed difficulty code again, added block queuing without client delay (threaded).
Should normalize difficulty in 1-3 days.
Mandatory forking update at block 11700.

Download links: http://gldcoin.com/get-started/

Support forum: https://www.gldtalk.org/index.php?board=22.0

Notes: For those pulling from github you may have to use the following command before your pull will work:
git stash; git fetch origin; git reset –hard origin/master
Thank you for your patience during this time.

The development team is currently on standby in the event you require technical assistance.

[Tommo_Aus]

Many thanks! I've just updated, will let you know how things go

[rocketron]

i too am on the same pool as above, seems to be alot of orphans still, more less every block found ends up a orphan. going to go solo till there is more information.
I was mining all night to wake up and see there was a mandetory update so i was wasting power...but i hope the dev can sort this coin out soon before its too late and its killed, its a good coin when it works

I also noticed in that pool, why am i not getting any shares for my submitted work? i only seem to be getting credited if i find a block..

[Tommo_Aus]

My pools been mining on 0.7.1.6 for about an hour at a consistent 10Mh/s, found 6 blocks and all orphaned

[Thrash]

Hi Guys,

First of all Microguy, Akuma and the team, I do apologize for voicing so much of my anger. I was on the brink of losing a lot of money since I have it all invested in GLD.

Thank you for the update, but are we very certain this works? Lets get all kinks out ASAP. So we do not see another fork down the road. For this to be a mainstream currency, it needs to be at a point where we are not forking this all the time. Looking at the latest update, I am still seeing a butt load of orphans, both in the pools, and in solo mining. I have around 4mhs on this right now, and I see the debug log queing blocks for the appropriate timestamp even though I got blocks found.

Any ideas?

Here is a screenshot of the pool the poster above just updated: http://i39.tinypic.com/2qtffa0.png

You do understand the fork occurs at block 11700? We don't expect mining to normalize for at least 72 hours.

I hope you mean block 117000.