[KGC] The future is krugercoin and the future is now! [Official Launch]

[Nibiru]

***

5000 KGC prize for new artwork for krugercoin paperwallet .....

wallet.krugercoin.co

***

[Nibiru]

Dear All,

Kimoto Gravity Well has been added to krugercoin please update your wallet from http://krugercoin.co
 
Source Code: https://github.com/Krugercoin/krugercoins


Thanx

[MinersPoolEU]

Thanks,

http://krugercoin.miners-pool.eu is ready!

[UniMatrixZ]

Thanks,

http://krugercoin.miners-pool.eu is ready!

Great, just started mining Krugercoin today at your pool.
Should be interesting to see what happens now after Kimoto Gravity Well implementation.

[UniMatrixZ]

Until cryptsy updates their wallet I'm setting autopay to 0

[MinersPoolEU]

We have to wait block height 1,120,000 to see what happen, until this block height, difficulty continues to be retargeted every 2016 blocks.

[UniMatrixZ]

We are at block 1121306 right now  

hmmm
You have exceeded the pools configured KGC warning threshold. Please initiate a transfer!

Why is max autopay so low as 250 KGC?

[MinersPoolEU]

We are at block 1121306 right now  

hmmm
You have exceeded the pools configured KGC warning threshold. Please initiate a transfer!

Why is max autopay so low as 250 KGC?

Hum, you're right, KGW is active

debug.log

Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.04073

The max autopayout is now set to 5,000 KGC.

[OLX]

error - QtCored4.dll

rename QtCore4.dll -> QtCored4.dll ?

[digitsmith]

good job!

thanks @Nibiru and @MinersPoolEU

[almightyruler]

I have installed the new client, but it has stayed on the same chain, rather than switching to the "official" one.

I restored an older database and restarted, so that my client was more likely to choose the official chain when it reached the fork point, but now syncing has stalled right at that point... block 1,119,999.

KGW should have been set to activate at some time in the future to minimise disruption and people being stuck on the old chain; instead it looks like it became active before the new version was even announced here. That means a lot of people are still going to be mining and transacting on the old chain. You can't fork without notice.

edit: looks like my client (running the newer version) is banning clients that are trying to send through blocks. I guess f686dffe3bf6baa058b0 is probably block 1120000 on the old fork, so it is being rejected.

Code:

received block f686dffe3bf6baa058b0
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.89579
Before: 1d08e4b4  00000008e4b40000000000000000000000000000000000000000000000000000
After:  1d04b0ed  00000004b0ed7810c46a97810c46a97810c46a97810c46a97810c46a97810c46
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 37.139.23.64:8771
Disconnected 37.139.23.64:8771 for misbehavior (score=100)

....

received block f686dffe3bf6baa058b0
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.89579
Before: 1d08e4b4  00000008e4b40000000000000000000000000000000000000000000000000000
After:  1d04b0ed  00000004b0ed7810c46a97810c46a97810c46a97810c46a97810c46a97810c46
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 84.104.23.68:8771
Disconnected 84.104.23.68:8771 for misbehavior (score=100)


...

received block f686dffe3bf6baa058b0
Difficulty Retarget - Kimoto Gravity Well
PastRateAdjustmentRatio = 1.89579
Before: 1d08e4b4  00000008e4b40000000000000000000000000000000000000000000000000000
After:  1d04b0ed  00000004b0ed7810c46a97810c46a97810c46a97810c46a97810c46a97810c46
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 106.186.115.58:59918
Disconnected 106.186.115.58:59918 for misbehavior (score=100)

[MinersPoolEU]

If you have some trouble to sync with the new version, you can add our 212.83.191.197 node

[thrassos]

If you have some trouble to sync with the new version, you can add our 212.83.191.197 node

Hello,

We have tried to add this node (suggested by nibiru) but it does not work. We get the following error:

disconnecting node 212.83.191.197
Disconnected 212.83.191.197 for misbehavior (score=100)

Our stratum wallet info:
{
"version" : 70005,
"protocolversion" : 60001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 1119999,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.11244158,
"testnet" : false,
"keypoololdest" : 1394318190,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

Regards,
Thrassos

[UniMatrixZ]

Hmpf autopay from pool 5000 KGC 8 hours ago, stil nothing on Cryptsy.
I guess they haven't updated their wallet yet.

Edit: Installed the wallet on my PC instead until Cryptsy can get their tumb out of their ass and update the wallet.

[almightyruler]

If you have some trouble to sync with the new version, you can add our 212.83.191.197 node

Your IP is one that my client is banning. Our clients should both be agreeing on the proof of work for block 1120000, but for some reason what yours gives is different to what mine expects.

I even set up a temporary firewall so that your IP was the only one my client could connect to. The behaviour did not change.

I notice that my vers is 70005 yet yours is only 60001 ? Are you absolutely sure you are using the latest version? I downloaded & compiled from github about 6 hours ago.

[almightyruler]

I think that adding KGW immediately rather than at a well defined point in the future may be what is causing problems - everyone is going to end up on their own private fork created at the time they upgrade. If you are past the KGW point when you upgrade (as 99.9% of people will be - there was no advance notice) the client does NOT appear to backtrack to 1120000 to find and follow the correct official chain... it will just extend from whatever block # it happened to be on when you upgrade, and will start banning clients because they disagree about block parameters. There are no checkpoints so there is no way to force the client onto the correct chain.

As a further issue, I also notice that my Krugercoin client has been connected to by Litecoin (~528k blocks) and Worldcoin (~1.1m blocks) clients. It's too late to fix now, but prior to launch the source really should have had the magic numbers set to something unique. Right now the clients cannot tell the difference between the 3 coins.

[MinersPoolEU]

I notice that my vers is 70005 yet yours is only 60001 ? Are you absolutely sure you are using the latest version? I downloaded & compiled from github about 6 hours ago.

60001 is the protocol version

krugercoin getinfo

    "version" : 70005,
    "protocolversion" : 60001,
    "walletversion" : 60000,
...

[MinersPoolEU]

As a further issue, I also notice that my Krugercoin client has been connected to by Litecoin (~528k blocks) and Worldcoin (~1.1m blocks) clients. It's too late to fix now, but prior to launch the source really should have had the magic numbers set to something unique. Right now the clients cannot tell the difference between the 3 coins.

Yes totally agreed!
At least developers can add some checkpoints hash to verify the blockchain.

[UniMatrixZ]

This is getting frustrating, should I continue to mine or what?

Win client is taking forever to sync....

[MinersPoolEU]

Some peer addresses which are on version 7.0.0.5 and connected to our wallet :

54.204.36.33
78.42.83.245
188.6.38.12
81.224.140.225
84.104.23.68
196.215.28.70