To you guys who just got here and wonder what happened:
For a while after the fork everything went smooth, blocks were found and no issues were found. Some pools had forgot to update wallet so they were on their own block chain still finding 77KDC/block.
Then KDC forked and coins that were sent didn't arrive to the other wallet.
Some kind of wallet error was affecting every pool out there. Every pool went down until this was fixed. Criptoepool team started working on it and got it working. THOUGH THERE IS NO GREEN LIGHT FROM DEVELOPERS YET!
Wallets went to several different blockchains and KDC was forked.
Market at coinedup is temporarily halted until everything is fixed.
DO NOT SEND COINS TO ANOTHER WALLET UNTIL DEVELOPERS GIVES US THE GREEN LIGHT! BY SENDING COINS TO ANOTHER WALLET RIGHT NOW YOU CAN LOSE YOUR COINS!
I don't think criptoepool team wants to harm KDC.
Please don't DDOS their pool and start mining there instead.
I have no expertise in this subject but logically I think the right thing to do is to get the longest block chain and by this helping the developers. They will know which block chain is the longest and can pull the data from there and use it.
Can anyone with knowledge in this subject confirm or deny this?
Thanks... we mean no harm!!!
I feel quite responsible for dragging Criptoe into this as I have been the KDC supporter of the group. We have a very vested interest in seeing this resolved ASAP. We gave away over 1800KDC in block finder rewards leading up to the fork... we have invested heavily in the KDC community and pool to ensure success of KDC as a coin.
Causing forks and fracturing the community and blockchain is counterproductive for all of us... miners, pool operators, investors, merchants... everyone.
What we would like to see is another pool grab the fix we pushed to Github and use and create some stability for the time being. It will give all us a breathing space to test and deploy a proper fix.
Thanks!