BTW... is there a bootstrap available for direct download? I want to download it to a server via plain old HTTP/HTTPS. Mega only works in a browser (javascript decryption), and an older bootstrap I found on Google Drive just downloads a few thousand bytes of HTML.
Can sync via the network of course, but it's going to take some time (and strain on the peers of a small network) to sync ~2GB of blockchain.
Topic: [KGC] New Krugercoin wallet released including leveldb (Read 8078 times)
Just noticed that this new vers expects the config for krugercoind to be called bitcoin.conf
Simple fix, but (unfortunately) I have no idea how to push an update someone else's repo on github. Hopefully OP can update the source?
any alive pool?
solo mining!
any alive pool?
Okay, just one question, is the old wallet still valid?
I've installed Version 70005 and I've picked up at least two peers using versions 60001 and 70002.
I've installed Version 70005 and I've picked up at least two peers using versions 60001 and 70002.
The wallet is locking up on that error now every few minutes. Was there not a patch available to solve the time warp attack?
So this is what is happening now it happened 2 times already.
Code:
2015-05-16 12:17:39 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 3500386 (02c5ed03a36b76ce56fe746c047f2ce7592645d7265224ae67f2579d41eee8dc)
lasting to height 3500394 (1949114e98e794fb0947154b3057ac61c9727c1e783e7f5397cb0b3efb0ed84d).
Chain state database corruption likely.
So this is what is happening now it happened 2 times already.
Yes, there is a patch. But any fix would create a fork of the blockchain. All old clients would be mining the old chain and all new clients the new one. A fork like this can only work if everyone is upgrading to the new version.
The best way to do it would be to remove the KGW at a block somewhere in the future and spread the new client to everyone. By the time the block is reached everyone must have upgraded!
I could do that tomorrow. But I need to know how far in the future the "block of change" should be
What do you think?And I need some support in telling the major "Krugercoin-players" to upgrade
Nibiru seems to have vanished and he owns the Krugercoin Website.
I agree we should move all together to a new fork, but I think we need to take it seriously
Now we are in Cryptsy, and we cant lose it.
If we are making a new fork, they must see there is a dev team they can contact with. and now, we dont have that.
so, i would say no to the fork until we have a bigger community and someone's is ready to manage that
Is this information still valid? How can I know
The wallet is locking up on that error now every few minutes. Was there not a patch available to solve the time warp attack?
So this is what is happening now it happened 2 times already.
Code:
2015-05-16 12:17:39 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 3500386 (02c5ed03a36b76ce56fe746c047f2ce7592645d7265224ae67f2579d41eee8dc)
lasting to height 3500394 (1949114e98e794fb0947154b3057ac61c9727c1e783e7f5397cb0b3efb0ed84d).
Chain state database corruption likely.
So this is what is happening now it happened 2 times already.
Yes, there is a patch. But any fix would create a fork of the blockchain. All old clients would be mining the old chain and all new clients the new one. A fork like this can only work if everyone is upgrading to the new version.
The best way to do it would be to remove the KGW at a block somewhere in the future and spread the new client to everyone. By the time the block is reached everyone must have upgraded!
I could do that tomorrow. But I need to know how far in the future the "block of change" should be
What do you think?And I need some support in telling the major "Krugercoin-players" to upgrade
Nibiru seems to have vanished and he owns the Krugercoin Website.
I agree we should move all together to a new fork, but I think we need to take it seriously
Now we are in Cryptsy, and we cant lose it.
If we are making a new fork, they must see there is a dev team they can contact with. and now, we dont have that.
so, i would say no to the fork until we have a bigger community and someone's is ready to manage that
The wallet is locking up on that error now every few minutes. Was there not a patch available to solve the time warp attack?
So this is what is happening now it happened 2 times already.
Code:
2015-05-16 12:17:39 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 3500386 (02c5ed03a36b76ce56fe746c047f2ce7592645d7265224ae67f2579d41eee8dc)
lasting to height 3500394 (1949114e98e794fb0947154b3057ac61c9727c1e783e7f5397cb0b3efb0ed84d).
Chain state database corruption likely.
So this is what is happening now it happened 2 times already.
Yes, there is a patch. But any fix would create a fork of the blockchain. All old clients would be mining the old chain and all new clients the new one. A fork like this can only work if everyone is upgrading to the new version.
The best way to do it would be to remove the KGW at a block somewhere in the future and spread the new client to everyone. By the time the block is reached everyone must have upgraded!
I could do that tomorrow. But I need to know how far in the future the "block of change" should be
What do you think?And I need some support in telling the major "Krugercoin-players" to upgrade
Nibiru seems to have vanished and he owns the Krugercoin Website.
The wallet is locking up on that error now every few minutes. Was there not a patch available to solve the time warp attack?
So this is what is happening now it happened 2 times already.
Code:
2015-05-16 12:17:39 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 3500386 (02c5ed03a36b76ce56fe746c047f2ce7592645d7265224ae67f2579d41eee8dc)
lasting to height 3500394 (1949114e98e794fb0947154b3057ac61c9727c1e783e7f5397cb0b3efb0ed84d).
Chain state database corruption likely.
So this is what is happening now it happened 2 times already.
I've check the block explorer and it seems every few blocks there is a fork. I checked through the debug log and there is a rollback of sometimes 2 blocks on another fork. it's very strange I have not seen this before on any other blockchain.
Yes, I see it too. My guess is someone is attacking the chain. I know the Kimoto Gravity Well is vulnerable to the timewarp attack. I guess I'll have to remove it. But then everyone will have to upgrade to the new client.
I've check the block explorer and it seems every few blocks there is a fork. I checked through the debug log and there is a rollback of sometimes 2 blocks on another fork. it's very strange I have not seen this before on any other blockchain.
And now this.....
I did not see the error message last time but it noticed something was very wrong and restarted the daemon.
Code:
{
"version" : 90300,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 1487.18640000,
"blocks" : 3499062,
"timeoffset" : -1,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.20412772,
"testnet" : false,
"keypoololdest" : 1405392075,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}I did not see the error message last time but it noticed something was very wrong and restarted the daemon.
same here. Maybe someone is attacking the coin via timewarp. I think I will have to implement a protection against that. But that would mean old clients would be on another blockchain and wouldn't be able to connect to the new clients anymore.
By the way. Cryptsy wrote back:
Code:
Thank you for the information. We have escalated this issue to our technical team. We will update you soon as issue is resolved and once your deposit has posted. Thank you for your patience.
And now this.....
I did not see the error message last time but it noticed something was very wrong and restarted the daemon.
Code:
{
"version" : 90300,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 1487.18640000,
"blocks" : 3499062,
"timeoffset" : -1,
"connections" : 12,
"proxy" : "",
"difficulty" : 0.20412772,
"testnet" : false,
"keypoololdest" : 1405392075,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : "Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."
}I did not see the error message last time but it noticed something was very wrong and restarted the daemon.
This is the last one I did
http://kgc.blockexp.info/tx/77ae1dedcb5f659da0976ee4a5fd82ab77150a058a008c608bb23ae27f6da340
But I have transactions from the 12th May that did not make it to cryptsy.
http://kgc.blockexp.info/tx/77ae1dedcb5f659da0976ee4a5fd82ab77150a058a008c608bb23ae27f6da340
But I have transactions from the 12th May that did not make it to cryptsy.
I think the blockchain forked again. The blockexplorer at http://kgc.blockexp.info is the same as my wallet but all sends to cryptsy don't arrive and the diff is 0.02 normally it's around 0.25.
So how do I get back on the correct fork?
So how do I get back on the correct fork?
KGC-blockchain seems fine. My deposit to cryptsy isn't showing up too. So I think it's a problem with cryptsy. I opened a ticket at their support site. If you can tell me your transaction-ID I can add that to my support request.
I think the blockchain forked again. The blockexplorer at http://kgc.blockexp.info is the same as my wallet but all sends to cryptsy don't arrive and the diff is 0.02 normally it's around 0.25.
So how do I get back on the correct fork?
So how do I get back on the correct fork?
Go KGC go!!
Any recent update from the .......... dev?
Any recent update from the .......... dev?
Please provide another way to download the bootstrap.dat mega is really not usable on headless servers.
http://www.blockexp.info/kgc/Archive-2a9b.zip
Please provide another way to download the bootstrap.dat mega is really not usable on headless servers.
Jump to: