[ANN][SCRYPT] KlondikeCoin ★ Cryptsy.com ★ Prepaid VISA Cards ★ 0% Premine [KDC]

[bangomatic]

Working on and testing a fix right now... I will report back.

If only the devs were in irc so we could all help out Seriously, poor show.

Let them work it out instead of people screaming at them at IRC, like they would have time for that now anyway...

I wasn't going to scream at them, I was going to help them fix the issue.

HOPE I DONT GET FLAMED FOR THIS BUT JUST COULDNT RESIST.  

[1714890209]

1714890209

[1714890209]

1714890209

[1714890209]

1714890209

[24Kilo]

Let them work it out instead of people screaming at them at IRC, like they would have time for that now anyway...

We are all on the same team... no one is screaming at anyone... this needs to be fixed as soon as possible for many reasons... and the best way to find a fix is to work with experienced pool operators and community members with expertise. So happens that Criptoe Pools has 2 very experienced and knowledgeable coders, so we are doing everything we can to get KDC back on track again.

And I am sure that 'hash.so' has something to contribute that we may have missed... this is a team effort... and the fork are not going to go away on their own.

[ny2cafuse]

Can someone verify the highest block height known right now?

-Fuse

[Hollowman338]

keeping calm and drinking beer, for snow is coming and work has been shut down for tomorrow.  Cold in the klondike  

[KlondikeCoin]

Contacted coinedup earlier and asked them to halt trades whilst this is sorted, glad to see they have.

Let them work it out instead of people screaming at them at IRC, like they would have time for that now anyway...

We are all on the same team... no one is screaming at anyone... this needs to be fixed as soon as possible for many reasons... and the best way to find a fix is to work with experienced pool operators and community members with expertise. So happens that Criptoe Pools has 2 very experienced and knowledgeable coders, so we are doing everything we can to get KDC
back on track again.

And I am sure that 'hash.so' has something to contribute that we may have missed.

This is a team effort.

Absolutely,

if a community fix can be sorted asap i'm happy to take a look and approve it and push everyone to update - Karl & Dave usually handle the bulk of the code however i cannot get hold of them as they both have work commitments early in the morning and have gone to sleep - as the update seemed to have gone fine. Dave usually wakes up at obscure times so should get my messages in the next few hours.


@fuse, i'll take a look

[24Kilo]

Can someone verify the highest block height known right now?

-Fuse

#84876... according to the wallet on my solomining server.

[Sparkzor]

keeping calm and drinking beer, for snow is coming and work has been shut down for tomorrow.  Cold in the klondike  

Keeping calm, thinking of beer. It's snowing and I dislike it.
Klondike will warm me in a few days, damn Sweden

[Jilixi]

Can someone verify the highest block height known right now?

-Fuse

#84876... according to the wallet on my solomining server.

I can confirm this to be true, I have the same block height in my wallet

[KlondikeCoin]

Can someone verify the highest block height known right now?

-Fuse

#84876... according to the wallet on my solomining server.

I can confirm this to be true, I have the same block height in my wallet

Below is the last block of 16 coins according to abe - before things went awry and it started on the wrong chain.

http://explorer.klondikecoin.com/block/e2c925e708d5def5c62d8b93afcc1d5a8ce5065c57d6c12e502c3c093fa94991

[Sparkzor]

Can someone verify the highest block height known right now?

-Fuse

#84876... according to the wallet on my solomining server.

I can confirm this to be true, I have the same block height in my wallet


{
"blocks" : 84879,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 1.28098124,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 70883039,
"pooledtx" : 0,
"testnet" : false
}


I have this


Placebo and I had #xxx76 22:50 (GMT+1)

[ny2cafuse]

Absolutely,

if a community fix can be sorted asap i'm happy to take a look and approve it and push everyone to update - Karl & Dave usually handle the bulk of the code however i cannot get hold of them as they both have work commitments early in the morning and have gone to sleep - as the update seemed to have gone fine. Dave usually wakes up at obscure times so should get my messages in the next few hours.


@fuse, i'll take a look

Klondike, and others...

https://github.com/ny2cafuse/klondikecoin.  Pull request submitted.

Like I said, it could be a version issue, but without the original code, I can't verify.  However, this is to test that anyway.  It increases the version and protocol number and limits connections to only clients running that version(tested and verified).  Essentially shutting out older clients.  It's a first step to making sure everyone is updated.  It may also solve the issues we are seeing, but I can't tell until we see it large scale.

If you decide to compile and use this code, you will need to connect to another pool or node running it.  But the pool or node will need to be on the correct chain.  I'm reindexing (klondikecoind -reindex) right now to rescan the blocks, and I'm coming back up.  Try the following addnode if you use the code:

Code:

addnode:kdc.criptoe.com

Like I said, it might not work, but it eliminates the variable.

-Fuse

[24Kilo]

personal wallets seem to be on the right blockchain which is the longest... Placebo, Sparkzor and I are on the same blockchain.

I have a solo mined found block with 53 confirms and quite a few more... with no orphans yet.

[rynomite]

My solo mining efforts have never been this good.  Hope I'm on the right chain with this new wallet and get to keep some of them

[hash.so]

Can someone verify the highest block height known right now?

-Fuse

84889

edit: derp, missed the new page

[hash.so]

From a wallet with the fixes:

Code:

{
    "version" : 80602,
    "protocolversion" : 70003,
    "walletversion" : 60000,
    "balance" : 19906.35908113,
    "blocks" : 84892,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 0.86805923,
    "testnet" : false,
    "keypoololdest" : 1391463292,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

and old wallet

Code:

{
    "version" : 80601,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 19938.49485507,
    "blocks" : 84905,
    "timeoffset" : -1,
    "connections" : 54,
    "proxy" : "",
    "difficulty" : 0.86482884,
    "testnet" : false,
    "keypoololdest" : 1393734951,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
}

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

[bentmar]

Shouldnt we wait for dev to announce a new wallet instead of creating new forks?

[ny2cafuse]

KDC.CripToe.Com is running at highest block height with the my code change.  WE ARE MINING, FOLKS.

-Fuse

[Jilixi]

Shouldnt we wait for dev to announce a new wallet instead of creating new forks?

As far as I know this doesnt fork it, it fixes an issue.

[niceman]

You are kidding me?
You make Hard fork and don't even change version in official GitHub sources? All exchanges with 50 coins should monitor this thread to find what you changed rules?

[ny2cafuse]

I don't think it fixed the issue.

edit: new wallet was started with "-rescan -reindex"

Delete everything but your wallet.dat file and restart.  We're pegging blocks on CripToe.

-Fuse