There was a PR (https://github.com/bitcoin/bitcoin/issues/11045) that sought to change this but never got merged. So the switching can "confuse" the fuzzer and gmaxwell said that by hashing the branch targets, the fuzzer may not take certain code paths. Is this because of the known "edge collision" in AFL?
Hello I asked this question before about fuzzing. Now I'm asking a slightly different question. This q is aimed at anybody well-versed in the fuzzing of bitcoin core and of fuzzing in general (@sipa, @gmaxwell, others?). So bitcoin core currently has a fuzzing harness where a switch is done based on the input to determine the message type to be fuzzed.
either way, #bitcoin is the place for this
similar to jj's attack from breaking bitcoin last year
it is store on disk though, in the undo block data in bitcoin core, for as long as the block itself is stored
Guest14218: try #bitcoin or bitcoin.stackexchange.com
I just want to drop two ideas here, what would make a difference in the future of bitcoin and crypto in general. 1. Solving real world problems through mining, like miners being tied to BOINC projects, so all the computing power is put to good use. 2. Wallets with AI budgeting, that takes care of your money for you, learns your expenses, auto-allocates budgets for economies, has investment schemes for low, medium and hig
These 2 will give bitcoin and crypto the edge it needs over banks.
gmaxwell: after build of the code-signed binaries: creating and signing SHA256sums, uploading the binaries everywhere, seeding the torrent, release annoucements (mail, twitter, etc), PR and merge release metadata on bitcoincore.org and bitcoin.org, copying and committing the historical release notes to master, ehh and probably some other things I forgot :<
why did you recommend splitting the bitcoin fuzz harnesses into one binary per target? I know it’s more efficient but you mentioned also not doing so could “confuse” the fuzzer - what does that mean?
[bitcoin] MarcoFalke closed pull request #10595: Bugfix: RPC/Mining: Use pre-segwit sigops and limits, when working with non-segwit GBT clients (master...gbt_nosegwit_fix) https://github.com/bitcoin/bitcoin/pull/10595