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

How to discover startup flags or command-line options for bitcoind?

How to discover startup flags or command-line options for bitcoind? I'd like to query the Bitcoin daemon (bitcoind) to find out what startup flags (command-line options) were sent to it on startup (or the current state if it has changed, e.g. -server=0/1 changing). For example, I may want to know if -addresstype, -disablewallet, -rescan, or -uacomment=<cmt> or some other flag has been set. Or for Namecoin, it would be very useful to know if -namehistory has been set. Is there an RPC or any other method to find out? Or, to ask the question a different way... src/bitcoind.cpp's bool AppInit(int argc, char* argv[]) method calls ParseParameters(argc, argv);, which is in src/util.cpp. In src/util.cpp we have: map<string, string> mapArgs; static map<string, vector<string> > _mapMultiArgs; const map<string, vector<string> >& mapMultiArgs = _mapMultiArgs; To store flags/options/args. I'd basically just like to get whatever is in tho...
Read more

How to use Bitssa to your advantage?

How to use Bitssa to your advantage? Bitssa is a global multi-cryptocurrency exchange that provides you the unique opportunity to trade your cryptocurrency with cryptocurrency and also fiat currency with cryptocurrency. All you need to do is sign up on Bitssa , complete the registration formality, create a wallet address and start trading on the market page. Get wallet free of cost as soon as you signup with bitssa . We are not makers and takers our users decide the price on the exchange. Instant execution of your orders as soon as your price matches. Try Bitssa and you will love it. Also, For better experience, try the Bitssa mobile app. https://ift.tt/2LvrgC7
Read more

Bitcoin HD Wallets with hardened derivation and watch-only addresses

Bitcoin HD Wallets with hardened derivation and watch-only addresses I'm learning about the details of how HD wallets work. After reading the BIP32 and BIP44 documents thoroughly and supplementing it with Mastering Bitcoin there's still on aspect that I can't figure out. Say I derive an extended private key with the BIP44 first account, first address path path: m/44'/0'/0'/0/0 and then I convert the extended private key into an extended public key. Based on what I've read so far proper way would be to take the extended public key and work with an entirely non-hardened path like: M/0/1 , M/0/2 ? Is this the correct way to do it ? My problem is that a public key of M/44'/0'/0'/0/1 will not be the same as M/0/1. I'm just trying to make sure I'm using the derivation paths correctly. Thanks a lot! http://bit.ly/2DpBKlI
Read more