[bitcoin] theStack opened pull request #17461: test: check custom descedant limit in mempool_packages.py (master...20191112-test-check_custom_descendant_limit_in_mempool-packages) https://github.com/bitcoin/bitcoin/pull/17461
fyi if you have an opinion on OP_SECURETHEBAG naming convention please chime in on https://www.reddit.com/r/Bitcoin/comments/dviy6i/should_op_securethebag_be_renamed/ or the twitter poll. Trying to finalize a name (naming it is difficult as the boring but technically accurate name is OP_CHECKOUTPUTSANDSEQUENCESANDSCRIPTSIGSANDLOCKTIMEANDVERSIONANDNVINVERIFY is a bit too wordy). Hoping to resolve naming concerns so that focus
[bitcoin] achow101 opened pull request #17458: Refactor OutputGroup effective value calculations and filtering to occur within the struct (master...cleanup-outputgroups) https://github.com/bitcoin/bitcoin/pull/17458
pretty sure bitcoin-qt always has warnings for me, too
promag: In release binaries? I'm not sure that's a good idea unless you can guarantee it'll never crash. Otherwise Qt could just through some dumb warning about missing fonts etc, and crash bitcoin-qt
emilengler: I don't have any data on BitcoinCore.org, but back when the binaries were exclusively hosted on Bitcoin.org, there was less than 1% as many downloads of SHA256SUMS.asc than there was of the binary files.
midnight: I don't know, I dont' think *that* is so bad with bitcoin core. I do have experiences like that with things like printer settings though, where the software tries to 'intelligently' guess what your're trying to do, correcting for some settings, so at some point you need to make second-order guesses so that the software will make the correct guess and eventually send the right value to the
bitcoin/master 10b4729 Antoine Riard: Pass block height in Chain::BlockConnected/Chain::BlockDisconnected
bitcoin/master 5aacc3e Antoine Riard: Add m_last_block_processed_height field in CWallet
bitcoin/master 9700fcb Antoine Riard: Replace CWalletTx::SetConf by Confirmation initialization list
wumpus: I actually don't completely on that. for a long time I didn't understood a thing about bitcoin's build system and/or code and I liked that it installed basically everything I could manage (I'm one of those freaks who likes the GUI :) )
BlueMatt: https://github.com/bitcoin/bitcoin/pull/15382#issuecomment-551451359 kind of reminds me what has bothing me about the rust stuff; I think the build system there also needs to focus on features, not "use rust or not", don't group them on programmings language/dependency; if someone wants to enable a feature that happens to be implemented in rust, request them to install a rust compiler :)
We're adding a SECURITY.md file to the bitcoin-core/secp256k1 repo and considered firstname.lastname@example.org as security email address.Would it be possible to add such an email address? How are we making sure that security contacts will actually get emails forwarded to them? Who can see the content of a vulnerability report if it's sent unencrypted?
yes, I can make a forward address on bitcoin-core.org
oh nice, there's a env_windows.cpp in the new upstream leveldb, we might be able to stop maintaining our own env_win https://github.com/bitcoin-core/leveldb/pull/26 this handles the file functions and such, it will be a lot of work to test/investigate the differences though