Source revision, Assertion `globalChainParams' failed

[wsxdrfv]

So I added 2 lines to bitcoin's newest source for validate & create genesis block.

at chainparams.cpp,

Code:

genesis = CreateGenesisBlock(1519619579, 44453, 0x1f00ffff, 1, 500 * COIN);  
const Consensus::Params& consensusParams = Params().GetConsensus();
while(!CheckProofOfWork(genesis.GetHash(), genesis.nBits, consensusParams)){ ++genesis.nNonce; }

but after compile (by 'make', 'make install'), and run (by './xxxcoind'), following errors.

lee@newlite:~/Desktop/BitcoinEssence/src$ ./bitcoinessenced bitcoinessenced: chainparams.cpp:524: const CChainParams& Params(): Assertion `globalChainParams' failed. Aborted (core dumped)

chainparams.cpp:524 line is,

Code:

const CChainParams &Params() {
    assert(globalChainParams);  // this is 524 line.
    return *globalChainParams;
}

Why and how to solve this? Thanks..

[1714020325]

1714020325

[1714020325]

1714020325

[1714020325]

1714020325

[1714020325]

1714020325

[1714020325]

1714020325

[achow101]

Then instead of using the checkproofofwork function, copy out its code into your while loop and refer to the variables directly from within the ChainParams. This is simple programming debugging and troubleshooting, you should not need hand holding and someone to tell you exactly what to do.


Not gonna lie, the fact that you are constantly asking for people to give you specific, hand holding instructions both here and on Bitcoin Stack Exchange indicates to me that you should not be creating your own cryptocurrency. Even "just for educational purposes", you should understand how to read and write code before doing this. You can learn how cryptocurrencies work without reading the code anyways, there's lots of documentation on the specifics. The things that you are asking are simple programming questions that you should be able to figure out yourself.

[wsxdrfv]

Then instead of using the checkproofofwork function, copy out its code into your while loop and refer to the variables directly from within the ChainParams. This is simple programming debugging and troubleshooting, you should not need hand holding and someone to tell you exactly what to do.

Even after doing that, still debug.log says ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)...

Seems there is no hope...

[AdolfinWolf]

Then instead of using the checkproofofwork function, copy out its code into your while loop and refer to the variables directly from within the ChainParams. This is simple programming debugging and troubleshooting, you should not need hand holding and someone to tell you exactly what to do.

Even after doing that, still debug.log says ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)...

Seems there is no hope...

Note that i am not an expert in coding and debugging, but this error

Code:

CBlockDiskPos(nFile=0, nPos=8)...

might have something to do with you having an invalid hash/nounce..

See this as reference; https://bitcoin.stackexchange.com/questions/60299/altcoin-creation-from-bitcoin-readblockfromdisk-errors-in-block-header-at-cbloc

But it seems that you've already read that answer, assuming you're leegod on SE?

[wsxdrfv]

Then instead of using the checkproofofwork function, copy out its code into your while loop and refer to the variables directly from within the ChainParams. This is simple programming debugging and troubleshooting, you should not need hand holding and someone to tell you exactly what to do.

Even after doing that, still debug.log says ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)...

Seems there is no hope...

Note that i am not an expert in coding and debugging, but this error

Code:

CBlockDiskPos(nFile=0, nPos=8)...

might have something to do with you having an invalid hash/nounce..

See this as reference; https://bitcoin.stackexchange.com/questions/60299/altcoin-creation-from-bitcoin-readblockfromdisk-errors-in-block-header-at-cbloc

But it seems that you've already read that answer, assuming you're leegod on SE?

yes I already read it. leegod is my nickname. And as first reply of that thread said, it doesn't work with new source. Still has CBlockDiskPos error.