Proof of work failed

Proof of work failed

I am trying to create a new coin using Bitcoin code base following this https://bitcointalk.org/index.php?topic=3345808.msg35016844#msg35016844 article. But i am stuck as I received an error:

2018-10-29T15:30:11Z ERROR: AcceptBlock: high-hash, proof of work failed (code 16)

I am guessing the error is in the proof of work parameters?

CMainParams() {
    strNetworkID = "main";
    consensus.nSubsidyHalvingInterval = 210000;
    consensus.BIP16Exception = uint256S("0x00000000000002dc756eebf4f49723ed8d30cc28a5f108eb94b1ba88ac4f9c22");
    consensus.BIP34Height = 227931;
    consensus.BIP34Hash = uint256S("0x000000000000024b89b42a942fe0d9fea3bb44ab7bd1b19115dd6a759c0808b8");
    consensus.BIP65Height = 388381; // 000000000000000004c2b624ed5d7756c508d90fd0da2c7c679febfa6c4735f0
    consensus.BIP66Height = 363725; // 00000000000000000379eaa19dce8c9b722d46ae6a57c2f1a988119488b50931
    consensus.powLimit = uint256S("0x0000ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff");  //  KCoin
    consensus.nPowTargetTimespan = 14 * 24 * 60 * 60; // two weeks
    consensus.nPowTargetSpacing = 10 * 60;
    consensus.fPowAllowMinDifficultyBlocks = false;
    consensus.fPowNoRetargeting = false;
    consensus.nRuleChangeActivationThreshold = 1916; // 95% of 2016
    consensus.nMinerConfirmationWindow = 2016; // nPowTargetTimespan / nPowTargetSpacing
    consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].bit = 28;
    consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nStartTime = 1199145601; // January 1, 2008
    consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nTimeout = 1230767999; // December 31, 2008

    // Deployment of BIP68, BIP112, and BIP113.
    consensus.vDeployments[Consensus::DEPLOYMENT_CSV].bit = 0;
    consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nStartTime = 1462060800; // May 1st, 2016
    consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nTimeout = 1493596800; // May 1st, 2017

    // Deployment of SegWit (BIP141, BIP143, and BIP147)
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].bit = 1;
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nStartTime = 1479168000; // November 15th, 2016.
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 1510704000; // November 15th, 2017.

    // The best chain should have at least this much work.
    consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000000000000000000100010001");  //  Kcoin:
    //  This is the minimum chain work required to consider the blockchain is updated

    // By default assume that the signatures in ancestors of this block are valid.
    consensus.defaultAssumeValid = uint256S("0x0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8"); //534292
https://ift.tt/2zblrWE

Comments

Post a Comment

Popular posts from this blog

bitcoin node: what is the difference between simnet and regtest?

bitcoin node: what is the difference between simnet and regtest? btcd, and presumably other bitcoin node implementations, seem to have 4 network options: mainnet testnet regtest simnet. I get that mainnet and testnet both are "public" in that your node will communicate with other nodes and that both have an existing blockchain and genesis block. However, from what I can tell, both simenet and regtest both create a local only blockchain, and both will create a new genesis block. I this case, what is the difference, and which is better (easier) for developing bitcoin applications? This is what the documentation has to say: --regtest Use the regression test network --simnet Use the simulation test network https://ift.tt/2TAMkwe
Read more

How to check if Electrum is masking my IP with the Tor proxy?

How to check if Electrum is masking my IP with the Tor proxy? When i start Electrum from the command line i see this mensage: (python3:7069): dbind-WARNING **: 14:09:58.452: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken What does it mean? I just installed Electrum following this tutorial: http://docs.electrum.org/en/latest/tor.html I followed the instructions from this topic " Option 2: Multiple servers but Tor Main ". I installed Electrum using the command line on Ubuntu, check the " Installation from Python sources " on this link https://electrum.org/#download if you want to see the codes. And i used this code bellow to download the Signatue keys: $ gpg --keyserver pool.sks-keyservers.net --recv-keys 2BD5824B7F9470E6 I checked the both checkbox: 1)...
Read more

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password I used btcrecover to extract the wallet file (wallet.aes.json) from a blockchain account and I have been running btcrecover with dictionaries of my making but it has been going on for weeks and I am running out of ideas on how to permutate what my wife and I think the password could have been. Is there a way to just manually transfer the btc from the old wallet into a new wallet we do have access to or is there any way to extract the password or private keys directly from the wallet file? We have: the phone with the original wallet app installed, the wallet file pulled using btcrecover, access to the email to allow authorization to access, the wallet identifier that was sent to her email when she first signed up, the phone which has the wallet, the pin that was used for the wallet, and we know how much btc is in the account. We do not have: The pri...
Read more