< bitcoin-git>
[bitcoin] MarcoFalke closed pull request #14932: ui: Warn the user on file corruption in mempool.dat (master...Mf1812-testFileCorruption) https://github.com/bitcoin/bitcoin/pull/14932
< provoostenator>
timothy: bitcoin-cli could prompt for a password rather than expecting it as an argument
< timothy>
(bitcoin-cli already have -stdin)
< timothy>
provoostenator: it's not a problem of bitcoin-cli, you cannot disable history in called command
< provoostenator>
That would be a change at the bitcoin-cli level.
< bitcoin-git>
[bitcoin] jnewbery opened pull request #15010: [wallet] Fix getbalance with minconf (master...fix_getbalance_with_minconf) https://github.com/bitcoin/bitcoin/pull/15010
< wumpus>
though I don't really like more and more 'business rule' kind of functionality leaking into bitcoin core, it reminds me a bit of the account stuff, it's so specific on your applciation
< wumpus>
bolting it on in a bitcoin specific way seems a bad idea
< bitcoin-git>
[bitcoin] hebasto opened pull request #15007: qt: Notificator class refactoring (master...20181219-notificator-enhancement) https://github.com/bitcoin/bitcoin/pull/15007
< bitcoin-git>
[bitcoin] achow101 opened pull request #15006: Add option to create an encrypted wallet (master...create-encrypted-wallet) https://github.com/bitcoin/bitcoin/pull/15006
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #15005: test: Bump timeout to run tests in travis thread sanitizer (master...Mf1812-testBumpTimeout) https://github.com/bitcoin/bitcoin/pull/15005
< bitcoin-git>
[bitcoin] benthecarman opened pull request #14988: Number of confirmations added to transaction csv export (master...confirmations_in_csv_export) https://github.com/bitcoin/bitcoin/pull/14988
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #14987: [rcp] RPCHelpMan: Require documentation of return value at compile time (master...Mf1812-rpcResultFlat) https://github.com/bitcoin/bitcoin/pull/14987
< bitcoin-git>
[bitcoin] benthecarman opened pull request #14981: Clarifying RPC getrawtransaction's time help text (master...getrawtransaction_help_text_fix) https://github.com/bitcoin/bitcoin/pull/14981
< fanquake>
lambolife Ask in #bitcoin instead, that'll be off-topic here.
< lambolife>
What's the latest update in Bitcoin's development so far. I'm gonna make a video about not to give Hopium but to present facts. So I;m here
< gribble>
https://github.com/bitcoin/bitcoin/issues/14958 | qa: Remove race between conneting and shutdown on separate connections by promag · Pull Request #14958 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] jonasschnelli opened pull request #14979: [Qt] Restore < Qt5.6 compatibility for addAction (master...2018/12/fix_addaction) https://github.com/bitcoin/bitcoin/pull/14979
< bitcoin-git>
[bitcoin] gwillen opened pull request #14978: Factor out PSBT utilities from RPCs for use in GUI code; related refactoring. (master...feature-refactor-psbt-rpcs) https://github.com/bitcoin/bitcoin/pull/14978
< Silb>
How active is the Bitcoin core irc channel?
2018-12-16
< bitcoin-git>
[bitcoin] benthecarman opened pull request #14977: GetKeyOrigin check in getaddressinfo RPC (master...getaddressinfo_rpc_refactor_GetKeyOrigin) https://github.com/bitcoin/bitcoin/pull/14977
< bitcoin-git>
[bitcoin] hebasto opened pull request #14975: qt: Refactoring with QString::toNSString() (master...20181216-macos-shownotification-refactor) https://github.com/bitcoin/bitcoin/pull/14975
< bitcoin-git>
[bitcoin] benthecarman opened pull request #14974: Removing redundant line: "Windows XP not supported" (master...release_notes_doc) https://github.com/bitcoin/bitcoin/pull/14974
< bitcoin-git>
bitcoin/master c84c2b8 practicalswift: tests: Test for expected return values when calling functions returning a success code
< bitcoin-git>
bitcoin/master 9133227 MarcoFalke: Merge #14935: tests: Test for expected return values when calling functions returning a success code...
< gribble>
https://github.com/bitcoin/bitcoin/issues/14075 | Import watch only pubkeys to the keypool if private keys are disabled by achow101 · Pull Request #14075 · bitcoin/bitcoin · GitHub
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] promag opened pull request #14958: qa: Remove race between conneting and shutdown on separate connections (master...2018-12-improve-shutdown-test) https://github.com/bitcoin/bitcoin/pull/14958
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< bitcoin-git>
bitcoin/master 0e75f44 Pieter Wuille: Replace CAffectedKeysVisitor with descriptor based logic
< bitcoin-git>
bitcoin/master 7a30e0f MeshCollider: Merge #14821: Replace CAffectedKeysVisitor with descriptor based logic...
< gmaxwell>
I'm no longer a commiter on bitcoin, I'd be interested in knowing how often commiters are manually resolving conflicts on master. I believe the answer is rarely but not never.
< harding>
lopp: under the default GitHub settings, anyone with commit access can push anything they want, so they could pull a PR into a private branch, modify it, merge it locally, and push it. Some projects enable GitHub settings that prevent direct pushes like that to the master branch, but I'm not sure whether Bitcoin Core uses them. Alternatively, when you open a GitHub PR, a box is checked by default that allows people with commit
2018-12-13
< gmaxwell>
moreover, that data is there-- go use a block explorer, there is no need a bitcoin wallet or node need to provide it.
< gmaxwell>
To actually _use_ bitcoin I need that data... vs history is needed for analysis/auditing/etc purposes.
< gmaxwell>
but like, _ignoring that_ (lol), in terms of actually switching bitcoin to use it, I expect it would be easier than utxotree.
< gmaxwell>
But "oh look spending patterns changed and with no impact in fees, bandwidth needed by bitcoin nodes just went up 5x" isn't the same as saying dbcache works better with more locality.
< gmaxwell>
unless you think that downloading bitcoin node software written by other people and not doing the work of writing it yourself is giving up. :P
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< gmaxwell>
jamesob: and moreover, with the exception of ultra high end commercial installs, few users would have the resources or patience to fetch 15 years of bitcoin history.
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< wumpus>
jamesob: it contains writable settings which override what is in bitcoin.conf
< jamesob>
*bitcoin.conf.qt
< wumpus>
I'm unconfortable with writing to bitcoin.conf directly, as it is specified with -conf, which might point to a read-only configuration file, it should not be assumed it is writable
< gribble>
https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub
< andytoshi>
ok. the reason i ask is that in Elements we are directly using sha2 midstates to get the same speedup (which ofc changes the hash function so is completely incompatible with bitcoin)
< andytoshi>
sipa: i'm confused by https://github.com/bitcoin/bitcoin/pull/13191 ... it seems the new SHA256D64 does not append the sha256 length/padding anywhere, so how can `ComputeMerkleRoot` be consensus-compatible with the old code?
< bitcoin-git>
[bitcoin] ken2812221 opened pull request #14937: travis: fix travis would always be green even if it fail (master...travis-fix-save-cache-2) https://github.com/bitcoin/bitcoin/pull/14937
< timothy>
do you REALLY want to run something like bitcoin on an unsupported OS?
< bitcoin-git>
[bitcoin] practicalswift opened pull request #14935: tests: Test for expected return values when calling functions returning a success code (master...test-return-values) https://github.com/bitcoin/bitcoin/pull/14935
< fanquake>
Would be interested to know if there are many/any? users running Bitcoin-Core on Windows Vista. Could use some more input in #14922.