jamesob: I think a way would be: start in your own personal account (or a new entity), find (a) capable maintainer(s), find contributors. If there is acceptable development performance, migrate it to the bitcoin-core github organization.
jonasschnelli: yeah, I agree - just might be good to have one that's clearly maintained by the bitcoin github org
Curious - is there a compelling reason against pulling out all the indexes into a separate codebase/runtime, perhaps also in a repo under the bitcoin org? Only exception I can think of would be that `getrawtransaction` rpc would need to be moved into that codebase for txindex=1, but is there any other instance where existing core behavior relies on the existence of those indexes?
Hi, is there some consensus regarding migration from c++11 to c++17 in Bitcoin core? I mean it seems that c++17 is not as widespread as I thought. So the migration will happen in medium term horizon, right? Like maybe in a year or two, right?
[bitcoin] hebasto opened pull request #19251: [Do Not Merge] ci: Temporary Test Case for negative capabilities in the Clang Thread Safety annotations (master...200611-dnm-test) https://github.com/bitcoin/bitcoin/pull/19251
I like using sqlite, to be honest, I don't think rolling a new database just for bitcoin core's database is a good idea, yes a dumb store would be enough for key storage, but for transactions it's likely that some more advanced query functionality would be useful at some point
wumpus, Hi, I have been investigating std::filesystem in c++17 a bit (see https://github.com/bitcoin/bitcoin/pull/19183#issuecomment-641321318) and I would like to lay the groundwork for a worthy PR. I'm just wondering whether you would be willing to answer a few questions along the way - given that you know the old issues with boost::filesystem.