Author

Topic: [ANN][SCRYPT] KlondikeCoin ★ Cryptsy.com ★ Prepaid VISA Cards ★ 0% Premine [KDC] - page 180. (Read 554419 times)

member
Activity: 84
Merit: 10
There is a very big fork in KDC... here is the 'getmininginfo" from two separate wallets... the first from CripToe Pools... the second from a private pool...

here is CripToe Pool

{
 "version" : 80601,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 4090.65747894,
    "blocks" : 84787,
    "timeoffset" : -1,
    "connections" : 17,
    "proxy" : "",
    "difficulty" : 0.84905294,
    "testnet" : false,
    "keypoololdest" : 1391924634,
    "keypoolsize" : 102,
    "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."
}

here is the private pool...

{
    "version" : 80601,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 6172.00807219,
    "blocks" : 84808,
    "timeoffset" : -1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 6.13942908,
    "testnet" : false,
    "keypoololdest" : 1393707602,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

same wallet protocol...different blockchain height and difficulty.

I would recommend that no one move any KDC until this is resolved.

We're working on a fix as quick as we can, don't move coins around. If you have moved coins then they should be recoverable once this is sorted.
legendary
Activity: 1120
Merit: 1000
HITLER is gonna be pissed.  Cheesy

 Grin Dev is on it, and let hope that Hitler stay pissed as he lost the war and we want to win it Smiley
legendary
Activity: 1246
Merit: 1000
ARK Team likes to ban and delete posts in reddit.
legendary
Activity: 1582
Merit: 1002
HODL for life.
another oddity is that I cant get to the "pools" page on any of the mining pools I use.

That's a result of MPOS getting the fatal error I posted earlier.  MPOS can't connect to the wallet, so it throws a PHP error that makes the page fail to load.  That's how I knew the other pools were having the same issue.
sr. member
Activity: 245
Merit: 250
Yeah, I learned that the hard way Sad

No one else make the same mistake I just did. Keep your coins in your wallets!
sr. member
Activity: 672
Merit: 250
There is a very big fork in KDC... here is the 'getmininginfo" from two separate wallets... the first from CripToe Pools... the second from a private pool...

here is CripToe Pool

{
 "version" : 80601,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 4090.65747894,
    "blocks" : 84787,
    "timeoffset" : -1,
    "connections" : 17,
    "proxy" : "",
    "difficulty" : 0.84905294,
    "testnet" : false,
    "keypoololdest" : 1391924634,
    "keypoolsize" : 102,
    "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."
}

here is the private pool...

{
    "version" : 80601,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 6172.00807219,
    "blocks" : 84808,
    "timeoffset" : -1,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 6.13942908,
    "testnet" : false,
    "keypoololdest" : 1393707602,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

same wallet protocol...different blockchain height and difficulty.

I would recommend that no one move any KDC until this is resolved.
legendary
Activity: 1582
Merit: 1002
HODL for life.
We are currently checking the seed nodes and code to check for errors.

ny2cafuse - if you have found any errors please suggest fixes on github and we'll take a look.

We'll update you as soon as we can/are sure there is a problem or what the problem may be.

Seed nodes aren't going to matter.

It's an issue with bad clients still being connected.  On some other coins, usually you can set the "badversion" option in the main.cpp file to a version that is known good.  Then any client that submits a block to the chain via that node, and they get locked out.  Without it, I think we've allowed older clients to connect and submit invalid blocks to the blockchain.

Did you update the version and protocol numbers?  If not, you need to do that, release an update with the new version and protocol number, and it will allow us to filter out the old clients via getpeerinfo.

-Fuse
ACQ
member
Activity: 89
Merit: 10
AKA- Drosanx 1Gi2qsybpbkCmxxVEENTVvEW57Jq5HGMTB
Same problem ive been mining a while and not one block found....
legendary
Activity: 1246
Merit: 1000
ARK Team likes to ban and delete posts in reddit.
http://kdc.cryptofountain.com/ is reporting a net hashrate of 0.04 mh/s
http://kdc.coinarmy.com/ is reporting a net hashrate of 184 mh/s
sr. member
Activity: 245
Merit: 250
Just tried to send my KDC to coinedup. 7 confirms in the wallet but nothing on their end yet... :/

Did you download the latest client?

Yessir, I have. Do we know that they did? For now I'd warn against moving any KDC around as I probably just lost my entire stash Sad
legendary
Activity: 1120
Merit: 1000
Just tried to send my KDC to coinedup. 7 confirms in the wallet but nothing on their end yet... :/

Did you download the latest client?
legendary
Activity: 1246
Merit: 1000
ARK Team likes to ban and delete posts in reddit.
My wallet is in sync....

Current block :84786 and moving higher....

Yeah something is gorked up. Pools arent finding any blocks, and network difficulty is at 0.81812394

another oddity is that I cant get to the "pools" page on any of the mining pools I use.
member
Activity: 84
Merit: 10
Looking at the github code, it doesn't show a version change for the V2 code, nor code change to limit connections to only the proper wallet version.  Was this done, or was the block reward the only thing changed?

If this wasn't done, this would cause a major problem on the blockchain.  Can the devs please verify this was done.  If it wasn't, this is going to go downhill really fast until that is resolved.

-Fuse

Lets wait for the answer of DEV, i'm sure that if there is a problem that they will be able to fix it soon.


We are currently checking the seed nodes and code to check for errors.


ny2cafuse - if you have found any errors please suggest fixes on github and we'll take a look.

We'll update you as soon as we can/are sure there is a problem or what the problem may be.
sr. member
Activity: 245
Merit: 250
Just tried to send my KDC to coinedup. 7 confirms in the wallet but nothing on their end yet... :/
legendary
Activity: 1120
Merit: 1000
My wallet is in sync....

Current block :84786 and moving higher....
legendary
Activity: 1120
Merit: 1000
Looking at the github code, it doesn't show a version change for the V2 code, nor code change to limit connections to only the proper wallet version.  Was this done, or was the block reward the only thing changed?

If this wasn't done, this would cause a major problem on the blockchain.  Can the devs please verify this was done.  If it wasn't, this is going to go downhill really fast until that is resolved.

-Fuse

Lets wait for the answer of DEV, i'm sure that if there is a problem that they will be able to fix it soon.
legendary
Activity: 1582
Merit: 1002
HODL for life.
Looking at the github code, it doesn't show a version change for the V2 code, nor code change to limit connections to only the proper wallet version.  Was this done, or was the block reward the only thing changed?

If this wasn't done, this would cause a major problem on the blockchain.  Can the devs please verify this was done.  If it wasn't, this is going to go downhill really fast until that is resolved.

-Fuse

Edit- on second glance, it doesn't appear that anything was changed in the version.h file.  If this wasn't changed, along with the version requirements in the main.cpp file, you just released a client that was bound to fork and break.  There is nothing stopping another client from connecting and inputting invalid blocks into the chain.

Where is the original source located?  I would like to compare the code.
newbie
Activity: 18
Merit: 0
{
"blocks" : 84758,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.84524209,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 280546407,
"pooledtx" : 0,
"testnet" : false
}
I have most definitely updated to the new version.

my wallet is reporting the same info...

{
"blocks" : 84758,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.84524209,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 280546407,
"pooledtx" : 0,
"testnet" : false
}

the dev team needs to clarify...
newbie
Activity: 56
Merit: 0
Top of Coinwarz, again!  Cool Price is going up fast on CoinedUP. We really need a decent exchange
sr. member
Activity: 245
Merit: 250
{
"blocks" : 84758,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.84524209,
"errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 280546407,
"pooledtx" : 0,
"testnet" : false
}
I have most definitely updated to the new version.
Jump to: