probably depends on the hardware, on my laptop I think it's IO. on systems with faster IO, I think its cpu inside leveldb code... at least with default dbcache. with dbcache cranked, its likely cpu elsewhere in bitcoin.
There is a cellphone game called spaceteam where you have to call out instructions for other people to punch in to jointly fly a fictional spacecraft. Manually setting consensus normative flags in bitcoin makes me think of spaceteam.
And the release cycle distinction we make for bitcoin is that consensus consistency changes are base, mandatory, functionality-- not software features (though sometimes some features must ride along with them)
re: launching testnet it would be useful if the windows installer created a Bitcoin Core (Testnet) link in the menu too, which does nothing but launch bitcoin-qt with -testnet flag. I have no idea how to do that though
it may be the windows machine I'm testing on is just crappy, I also had a strange issue with ldb files: https://github.com/bitcoin/bitcoin/issues/8250 .. possible that the disk is just very slow due to other processes interfering
Chris_Stewart_5: I have no experience with it either, if you can apply it to improve test coverage of bitcoin core, why not try it
sipa: Do you have any thoughts on property based checking? I'm starting to integrate it into a library I'm writing and it seems it would be useful in Bitcoin Core. I was looking at this library for C++
GreenIsMyPepper: yeah, the tl;dr: is Lightning means if Bitcoin breaks, we have deadlines to fix it or all hell breaks loose
Chris_Stewart_5: going back to your earlier comments, per the lifecycle, changes for network consensus exist outside of the bitcoin core release cycle, the reason we're talking about segwit merge in master here is not so much related to deploying segwit in the network, but related to managing the code implementing segwit in core as part of master. This is important to us because of the overhead
GreenIsMyPepper: it's ok for a bit, but given a sufficiently long period of empty blocks being mined eventually lightning users are really screwed over; that's not true for other ways of using Bitcoin
no results from x9.testnet-seed.bitcoin.jonasschnelli.ch :(
at least bitcoin core doesn't change the 'user agent' on such conditions, no
instagibbs: Main goals of the work are a comprehensive overview of the problem, the different parameters and approaches how it could be solved, and an evaluation of said approaches. Whether or not it gets adopted by Bitcoin Core is not part of my thesis, but a personal goal. :)
Yeah, but my overall familiarity with the Bitcoin Core is slightly behind yours. ;) But I guess, I'd count that as an "I haven't seen anything that contradicts Murch". :)