Topic: No Debug.log after first compile of bitcoind (Read 381 times)
Yep, i cloned another coin source :p
I hate to be "that guy" but did you ever get this resolved?
Hey Bitcoin - Community,
im about to create a my own altcoin to learn and to get some experience in the cryptoworld. Yesterday i cloned the newest source of bitcoin (0.14) and edited it with my personal design parameters. Just like i read it in a tutorial i changed the merkelroot and the genesis hash block to "0x" to create my own ones after first compile. Everything was looking pretty good. At least i had no errors with compiling the source.But when i run ./bitcoind -daemon i get this message:
Assertion failed: (consensus.hashGenesisBlock == uint256S ("0x")), function CMainParams, file chainparams.cpp, line 125.
Abort trap: 6
If i get it right, the new hashes and nnonce will be in the debug.log in the application support folder (using osx el capitan).
But there is no debug.log, just the folder which was created after first run.
I hope you can help me. Thank you!
im about to create a my own altcoin to learn and to get some experience in the cryptoworld. Yesterday i cloned the newest source of bitcoin (0.14) and edited it with my personal design parameters. Just like i read it in a tutorial i changed the merkelroot and the genesis hash block to "0x" to create my own ones after first compile. Everything was looking pretty good. At least i had no errors with compiling the source.But when i run ./bitcoind -daemon i get this message:
Assertion failed: (consensus.hashGenesisBlock == uint256S ("0x")), function CMainParams, file chainparams.cpp, line 125.
Abort trap: 6
If i get it right, the new hashes and nnonce will be in the debug.log in the application support folder (using osx el capitan).
But there is no debug.log, just the folder which was created after first run.
I hope you can help me. Thank you!
Jump to: