[ANN] Restart of Quantumcoin (SUCCESSFULLY RELEASED)

[tyrion70]

 quantumcoind getinfo
{
    "version" : 60400,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 4432,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 0.00945527,
    "testnet" : false,
    "keypoololdest" : 1372090458,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}


06/25/13 09:23:17 received block 5cbb1125b32b302a57eb
06/25/13 09:23:17 ERROR: AcceptBlock() : incorrect proof of work
06/25/13 09:23:17 ERROR: ProcessBlock() : AcceptBlock FAILED
06/25/13 09:23:17 disconnecting node 78.46.164.138:18001
06/25/13 09:23:17 Disconnected 78.46.164.138:18001 for misbehavior (score=100)

Its disconnecting your node due to misbehaviour..

[tyrion70]

Had to delete my whole blockchain and restart. This is the second time it did that btw..

Its actual now, but there's something wrong somewhere in the retargeting it seems..

[Lhunephel]

Will have a look at the retargeting method and fix it. Not sure what it's wrong there at the moment. Think I have to adjust the adjustment parameters.

[tyrion70]

Will have a look at the retargeting method and fix it. Not sure what it's wrong there at the moment. Think I have to adjust the adjustment parameters.

I see you changed something 4 hours ago?? Did you compile that in your client already??

https://github.com/quantumcoin/quantumcoin/commit/5ab5029b8260aa60e6cad3c84f8982bdf436d03a#src/main.cpp

You can't just go around and change things like this without giving ppl proper notice and at least change the version number of the coin... Updates are not pushed automagically to other ppl you know!

[Lhunephel]

This change doesn't change the logic of the code. I just rewrote the code to make it better readable.

[Lhunephel]

Just fixed the adjustment parameters inside the retargeting method. Hope it's now working better. Changes will start with height 10000. Also bumped the version. Will now compile the Windows binary.

[tyrion70]

Hmm strange.. I domt know if i can find the time to recompile though.. At work atm..

[Lhunephel]

Updated Windows binary is now also available. Sources are on GitHub. The version is now 60500. Please update.

[tyrion70]

Done, blockexplorer and p2pool run the new version

[frobley]

what happens to all the last quantumcoins we mined?

[Lhunephel]

They sit in the dead block chain and remain there until the end of the world. How many QCTs have you mined?

[tyrion70]

And again:


06/25/13 16:14:37 received block e9f224bcbbc42f55d763
06/25/13 16:14:37   nActualTimespan = 9  before bounds
06/25/13 16:14:37 GetNextWorkRequired RETARGET
06/25/13 16:14:37 nTargetTimespan = 220    nActualTimespan = 27
06/25/13 16:14:37 Before: 1e00fe6d  000000fe6d000000000000000000000000000000000000000000000000000000
06/25/13 16:14:37 After:  1d7ce661  0000007ce661bed61bed61bed61bed61bed61bed61bed61bed61bed61bed61be
06/25/13 16:14:37 ERROR: AcceptBlock() : incorrect proof of work
06/25/13 16:14:37 ERROR: ProcessBlock() : AcceptBlock FAILED
06/25/13 16:14:37 disconnecting node 78.46.164.138:18001
06/25/13 16:14:37 Disconnected 78.46.164.138:18001 for misbehavior (score=100)

Stuck at block


    "version" : 60500,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 5598.54185919,
    "blocks" : 6743,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00393036,
    "testnet" : false,
    "keypoololdest" : 1372090426,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""

I'm pretty done with this coin now.. 3 releases, and still no joy..

[Tony116]

i'm solo mining. receive 27 block after out of sync!!! what is errror?

[Lhunephel]

Sure not everything is running as expected, because the block chain includes some more modifications as with a normal release And of course Not sure what's wrong. My nodes are all running without issues.

In the sources:

    // Check proof of work
    if (nBits != GetNextWorkRequired(pindexPrev, this))
        return DoS(100, error("AcceptBlock() : incorrect proof of work"));

GetNextWorkRequired() uses the methods GetTargetSpacing() and GetInterval() to calculate the next difficulty. Maybe the issue is that those methods depends on GetNetworkHashPS()? But I think GetNetworkHashPS() should always return the same hashrate.

[MaGNeT]

And again:


06/25/13 16:14:37 received block e9f224bcbbc42f55d763
06/25/13 16:14:37   nActualTimespan = 9  before bounds
06/25/13 16:14:37 GetNextWorkRequired RETARGET
06/25/13 16:14:37 nTargetTimespan = 220    nActualTimespan = 27
06/25/13 16:14:37 Before: 1e00fe6d  000000fe6d000000000000000000000000000000000000000000000000000000
06/25/13 16:14:37 After:  1d7ce661  0000007ce661bed61bed61bed61bed61bed61bed61bed61bed61bed61bed61be
06/25/13 16:14:37 ERROR: AcceptBlock() : incorrect proof of work
06/25/13 16:14:37 ERROR: ProcessBlock() : AcceptBlock FAILED
06/25/13 16:14:37 disconnecting node 78.46.164.138:18001
06/25/13 16:14:37 Disconnected 78.46.164.138:18001 for misbehavior (score=100)

Stuck at block


    "version" : 60500,
    "protocolversion" : 60001,
    "walletversion" : 60000,
    "balance" : 5598.54185919,
    "blocks" : 6743,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 0.00393036,
    "testnet" : false,
    "keypoololdest" : 1372090426,
    "keypoolsize" : 103,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""

I'm pretty done with this coin now.. 3 releases, and still no joy..

Yup, it stays connected to network until I start mining

[tyrion70]

*grin* well u can have it then :-p

[Lhunephel]

Please update your clients to get the latest checkpoints. The DNS seed nodes are in sync and should be used as reference. Looks like the block chain stabilizes after the last change of the retarget method.

[rovchris]

This is very good coin for solo mining for people that have not tried before. As the difficulty is so low you will found out in no time if you have your conf file correctly configured.

The difficulty is so low even CPU mining will deliver a number of blocks in not time at all.

You may get a large number of rejects but you will definitely be solving blocks like there is no tomorrow.

[Lhunephel]

Chain is still active

[Piotrsama]

Not working for me.... can't connect.
Do we have to add a new node to the .conf?