< bitcoin-git>
bitcoin/master 2580ff8 Wladimir J. van der Laan: Merge #10314: Remove unused forward declaration for non-existent ScriptPubKeyToJSON(...)...
< bitcoin-git>
[bitcoin] kallewoof opened pull request #10310: [doc] Add hint about getmempoolentry to getrawmempool help. (master...doc-getrawmempool-getmempoolentry) https://github.com/bitcoin/bitcoin/pull/10310
< bitcoin-git>
[bitcoin] kallewoof closed pull request #10304: [rpc] Allow a txid param in getrawmempool (master...getrawmempool-include-txid) https://github.com/bitcoin/bitcoin/pull/10304
< bitcoin-git>
[bitcoin] jnewbery opened pull request #10307: [tests] allow zmq test to be run in out-of-tree builds (master...fix_zmq_test_out_of_tree) https://github.com/bitcoin/bitcoin/pull/10307
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #10305: Fix potential NPD introduced in b297426c (master...2017-05-fix-10290-npd) https://github.com/bitcoin/bitcoin/pull/10305
< bitcoin-git>
[bitcoin] laanwj closed pull request #10294: [Wallet] unset change position when there is no change (master...fixchangepos) https://github.com/bitcoin/bitcoin/pull/10294
< bitcoin-git>
bitcoin/master e2b99b1 Wladimir J. van der Laan: Merge #10294: [Wallet] unset change position when there is no change...
< bitcoin-git>
bitcoin/master 7c58863 Gregory Sanders: [Wallet] unset change position when there is no change on exact match
< bitcoin-git>
[bitcoin] kallewoof opened pull request #10304: [rpc] Allow a txid param in getrawmempool (master...getrawmempool-include-txid) https://github.com/bitcoin/bitcoin/pull/10304
< kallewoof>
Maybe bitcoin could use libgcrypt (GnuPG uses it for keys, I think; it has a bunch of random things) instead of OpenSSL. Though it seems to be LGPL. Some parts of it are dual MPL-compat though, like random-drbg.c
< gmaxwell>
okay we could do something that would perhaps mostly only be used by other bitcoin things.
< wumpus>
but someone else cooporating on it outside the context of bitcoin core (which is pretty narrow) isn't necessarily bad
<@wumpus>
gmaxwell: sipa: I'm just worried that taking up the concern of doing proper seeding in bitcoin core itself, without anyone else looking at it or using it, will result in a worse outcome for us. Allthe platform specific stuff is a hell to maintain, and it forces us to stay up to date in developments in that area
< bitcoin-git>
bitcoin/master 9c33ffd Wladimir J. van der Laan: Merge #8824: Refactor TxToJSON() and ScriptPubKeyToJSON()...
< bitcoin-git>
bitcoin/master 0ff9320 jonnynewbs: refactor TxToJSON() and ScriptPubKeyToJSON()
< bitcoin-git>
[bitcoin] kallewoof opened pull request #10303: [bench] Include ms/blk stats in Connect* benchmarks. (master...bench-add-per-block-stats) https://github.com/bitcoin/bitcoin/pull/10303
2017-04-30
< NicolasDorier>
well yes I will cache the address on the server side, and just make a request to bitcoin core to know if it was used before returning it to the server
< SopaXorzTaker>
banned me from #bitcoin for posting a malware link, explicitly marked like this and obsured: [https://]malware[.]coin.stealer
< sipa>
bitcoin core doesn't support gaps or reconstruction from a seed at all
< NicolasDorier>
is there a way in Bitcoin Core to get an unused address ? I am tempted to call getnewaddress everytimes, but doing so would create big gap in by BIP32 path, which would make rescanning fail
< afk11>
if this should be in #bitcoin-dev please someone let me know
< afk11>
keeping in mind most bitcoin libraries only sign scripts that don't have any degrees of freedom with the pathway that's executed.. I'm starting out by iterating over script opcodes and making a tree out of possible execution pathways as they come
< bitcoin-git>
[bitcoin] jameshilliard opened pull request #10301: Check if sys/random.h is required for getentropy. (master...getentropy-rand) https://github.com/bitcoin/bitcoin/pull/10301
2017-04-29
< gmaxwell>
I posted about it before, rng is seeded based on a collection of different pointers and timestamps. And in Bitcoin on windows, based on a screenshot.
< bitcoin-git>
[bitcoin] ryanofsky opened pull request #10295: [qt] Move some WalletModel functions into CWallet (master...pr/ipc-move) https://github.com/bitcoin/bitcoin/pull/10295
< bitcoin-git>
[bitcoin] instagibbs opened pull request #10294: [Wallet] unset change position when there is no change (master...fixchangepos) https://github.com/bitcoin/bitcoin/pull/10294
< bitcoin-git>
[bitcoin] practicalswift reopened pull request #9544: [trivial] Add end of namespace comments. Improve consistency. (master...consistent-use-of-end-of-namespace-comments) https://github.com/bitcoin/bitcoin/pull/9544
< bitcoin-git>
[bitcoin] practicalswift closed pull request #9544: [trivial] Add end of namespace comments. Improve consistency. (master...consistent-use-of-end-of-namespace-comments) https://github.com/bitcoin/bitcoin/pull/9544
< jtimon>
btw BlueMatt thanks for https://github.com/bitcoin/bitcoin/pull/771 I shouldn't look at it much and look at the new things instead but like these things if I find the time
< jtimon>
wumpus: btw, it would be nice to put BlueMatt 's libconsensus-related PRs in https://github.com/bitcoin/bitcoin/projects/6 (and always tag anything there with "consensus")
< BlueMatt>
luke-jr: thats ridiculous, you're living in a world where people have the time go read a ton of bitcoin core docs/code before running it, and do...neither of which are true
< petertodd>
gmaxwell: btw, re: your comment in the meeting, no-one's funding me to do any work on Bitcoin Core these days
< BlueMatt>
jtimon: conf flag seems neater, no one checks their bitcoin datadir
< jtimon>
it should still be relatively easy for users to get out of the stuck situation in case they can't upgrade in the same system or something, like maybe deleting a filed named ~/.bitcoin/DELETE_ME_ONLY_IF_YOU_CANT_UPGRADE_IN_THIS_SYSTEM or something
< luke-jr>
BlueMatt: it's only slightly shorter than Bitcoin's current lifetime
< jtimon>
or shouldn't I recommend bitcoin core for a wallet?
< jtimon>
luke-jr: let's say my friend remembers what I told him about being up to date 6 years and 11 months after I helped him install bitcoin core
< BlueMatt>
luke-jr: 110% sends the wrong message. if i expected any reasonable person to see that and think "I need to think for myself about what consensus of the network is" I'd be happy with it, but realistically the only people reading that will think "oh, I have to switch to the latest thing from Bitcoin Core, for whatever Bitcoin Core is according to my local google server"
< jtimon>
I think if it's optional and disabled by default it kind of defeats the point, but I certainly don't want that for myself or the users I recommend to use bitcoin core
< gribble>
https://github.com/bitcoin/bitcoin/issues/10279 | Add a CChainState class to validation.cpp to take another step towards clarifying internal interfaces by TheBlueMatt · Pull Request #10279 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] jimmysong opened pull request #10287: [tests] Update Unit Test for addrman.h/addrman.cpp (master...test_addrman) https://github.com/bitcoin/bitcoin/pull/10287
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #10286: Call wallet notify callbacks in scheduler thread (without cs_main) (master...2017-01-wallet-cache-inmempool-4) https://github.com/bitcoin/bitcoin/pull/10286
< bitcoin-git>
[bitcoin] morcos opened pull request #10284: Always log debug information for fee calculation in CreateTransaction (master...debugEstimates) https://github.com/bitcoin/bitcoin/pull/10284
< bitcoin-git>
[bitcoin] morcos opened pull request #10283: Cleanup: reduce to one GetMinimumFee call signature (master...oneGetMinimumFee) https://github.com/bitcoin/bitcoin/pull/10283
< bitcoin-git>
[bitcoin] luke-jr opened pull request #10282: Expire bitcoind & bitcoin-qt 7-8 years after its last change (master...timebomb) https://github.com/bitcoin/bitcoin/pull/10282
< bitcoin-git>
[bitcoin] TheBlueMatt opened pull request #10279: Add a CChainState class to validation.cpp to take another step towards clarifying internal interfaces (master...2016-12-cconsensus) https://github.com/bitcoin/bitcoin/pull/10279
2017-04-25
< jonasschnelli>
testnet-seed.bitcoin.jonasschnelli.ch should be up and running... do you use tor?
< ryan-c>
host testnet-seed.bitcoin.jonasschnelli.ch | grep ' has address ' | awk '{print$4}' | xargs -n1 -I IP bitcoin-cli -testnet addnode IP add
< BlueMatt>
can we close #10209 now that we fixed the "regenerate bitcoin-config.h" issue and #10210 now that #10215 is merged?
< ryan-c>
BlueMatt: It's the binary release from bitcoin.org, sha256sum 860a046514961aeead8b640f1a321da8eb575d727fd8c37de5a4cee5908bbd9d
< ryan-c>
I told bitcoind 0.14.0 to shutdown via bitcoin-cli over four hours ago, and it's still running. strace shows it waiting on a futex call. Is there anything I should do before sending it a kill -9? The system is not low on memory.
< sipa>
that doesn't mean there is no advantage for HT cores in bitcoin block validation, as ECDSA verification isn't the only thing involved
< bitcoin-git>
bitcoin/master c29a0d4 Wladimir J. van der Laan: Merge #10265: [wallet] [moveonly] Check non-null pindex before potentially referencing...
<@wumpus>
unless someone implements https://github.com/bitcoin/bitcoin/issues/8973 to make onion connections come in on either an alternative port or a unix socket, it's unsafe to whitelist 127.0.0.1 [by default]
< bitcoin-git>
[bitcoin] practicalswift closed pull request #10212: Make sure parameter names in .cpp and .h files are in sync (master...make-doxygen-happy-by-using-consistent-parameter-names) https://github.com/bitcoin/bitcoin/pull/10212
< bitcoin-git>
[bitcoin] paveljanik opened pull request #10272: [Tests] Prevent warning: variable 'x' is uninitialized (master...20170425_FastRandomContext_test_warnings) https://github.com/bitcoin/bitcoin/pull/10272
< bitcoin-git>
[bitcoin] fanquake opened pull request #10271: Use std::thread::hardware_concurrency, instead of Boost, to determine available cores (master...replace-boost-getnumcores) https://github.com/bitcoin/bitcoin/pull/10271
< bitcoin-git>
[bitcoin] fanquake opened pull request #10270: Remove Clang workaround for Boost 1.46 (master...remove-boost-clang-workaround) https://github.com/bitcoin/bitcoin/pull/10270
<@wumpus>
BlueMatt: ah yes the "apply all the buzzwords to bitcoin mining, see what sticks" approach
< BlueMatt>
wumpus: the same bottom-of-the-barrel buzzword bingo that came up with "using normal computers to simulate quantum computers to do bitcoin mining"
<@wumpus>
"using deep learning frameworks in bitcoin mining", that's hilarious, what bottom-of-the-barrel buzzword factory did that come out of
< bitcoin-git>
[bitcoin] kallewoof opened pull request #10267: New -readconfig argument for including external configuration files (master...feature-config-readconfig) https://github.com/bitcoin/bitcoin/pull/10267