To be clear the fork needed to happen ASAP, and exchanges were looking for a solution. We knew that doing the update so quickly was not ideal, this was not something we had wanted. However, given the options and the state of the network it was the best way forward to provide stability and allow products and applications to continue functioning normally. Especially given that exchanges were looking for updates.
That's too bad anyway that you let this situation happen and eventually were in position of emergency hard fork.
You should think in advance how to improve network stability and act proactively.
We have actually been working on an update to the network for a while. This update is larger (so more time consuming), but it would have happened in a month or two.
To be clear, our network was stable for a very long time (up until 2 weeks ago). We didn't have any reason to believe that our difficulty algorithm would experience issues so suddenly.
Really? This is what happened:
I'm seeing lots of blocks mined by a third party which then sends out bursts of those blocks to the main chain and causing huge network reorganizations invalidating a lot of legit blocks on my side.. Is that intended behavior during your hardfork ? Maybe you should release the wallets to the public already ?
This happens to every small coin that just forks Bitcoin or Litecoin code and does nothing else. This is called 51% attack. There is a lot of Scrypt hashpower available, but the majority of it mines LTC, and only small fraction of this hashpower mines GAME and other coins. And even small mining pools (maybe even individual farms) have enough hashpower to conduct a 51% attack. This situation could be predicted long ago, especially when the price drops, difficulty falls and it is easier to double spend. GameCredits total hashrate fell to 300 GH/s, this is ridiculously low, only 600 L3+ asics, it is 0.5% of what Litecoin has (160 TH/s). Last summer GameCredits share was about 5% of Litecoin's hashpower. No surprise that it became 10 times easier to double spend and the attack eventually happened. A penalty for that might be delisting from all major exchanges.
You should act proactively and eliminate any possibility to double spend. Digibyte and Verge protect the network against double spending using multi-algo; SYS offers merged mining with Bitcoin; Dash and Decred have hybrid PoW/PoS. You shouldn't think that the network is protected with DGW, in fact it is not.
