< achow101> any plans on 0.12.1 for wily in the ubuntu ppa?
< GitHub98> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/115735d547fd...005d3b643009
< GitHub98> bitcoin/master 4fbdc43 Gregory Maxwell: Revert "net: Avoid duplicate getheaders requests." PR #8054...
< GitHub98> bitcoin/master 005d3b6 Wladimir J. van der Laan: Merge #8306: Revert "net: Avoid duplicate getheaders requests." PR #8054...
< GitHub0> [bitcoin] laanwj closed pull request #8306: Revert "net: Avoid duplicate getheaders requests." PR #8054 (master...revert_8054) https://github.com/bitcoin/bitcoin/pull/8306
< GitHub88> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/005d3b643009...aef381161f3b
< GitHub88> bitcoin/master 20f3cd7 Wladimir J. van der Laan: wallet: Revert input selection post-pruning...
< GitHub88> bitcoin/master aef3811 Wladimir J. van der Laan: Merge #8298: wallet: Revert input selection post-pruning...
< GitHub158> [bitcoin] laanwj closed pull request #8298: wallet: Revert input selection post-pruning (master...2016_06_revert_wallet_input_postprune) https://github.com/bitcoin/bitcoin/pull/8298
< GitHub108> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/aef381161f3b...042c323922fc
< GitHub108> bitcoin/master ab8be98 BtcDrak: Remove bad chain alert partition check...
< GitHub108> bitcoin/master 042c323 Wladimir J. van der Laan: Merge #8275: Remove bad chain alert partition check...
< GitHub195> [bitcoin] laanwj closed pull request #8275: Remove bad chain alert partition check (master...partitionalerts) https://github.com/bitcoin/bitcoin/pull/8275
< GitHub172> [bitcoin] laanwj closed pull request #8241: 0.13: Disable bad chain alerts (master...2016_06_alexit) https://github.com/bitcoin/bitcoin/pull/8241
< GitHub154> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/042c323922fc...396f9d629662
< GitHub154> bitcoin/master 32cab91 Wladimir J. van der Laan: Bump `-dbcache` default to 300MiB...
< GitHub154> bitcoin/master efd1d83 Wladimir J. van der Laan: doc: Mention dbcache increase in release notes
< GitHub154> bitcoin/master 396f9d6 Wladimir J. van der Laan: Merge #8273: Bump `-dbcache` default to 300MiB...
< GitHub138> [bitcoin] laanwj closed pull request #8273: Bump `-dbcache` default to 300MiB (master...2016_06_dbcache) https://github.com/bitcoin/bitcoin/pull/8273
< GitHub108> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/b978701ba1822140452d35f037ce776fdcba0175
< GitHub108> bitcoin/master b978701 Wladimir J. van der Laan: qt: periodic translations update
< gmaxwell> lannwj: thanks.
< GitHub153> [bitcoin] jonasschnelli pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b978701ba182...91abb77970f4
< GitHub153> bitcoin/master 4f44cb6 Wladimir J. van der Laan: qt: Network-specific example address...
< GitHub153> bitcoin/master 91abb77 Jonas Schnelli: Merge #8288: qt: Network-specific example address...
< GitHub142> [bitcoin] jonasschnelli closed pull request #8288: qt: Network-specific example address (master...2016_06_network_based_example_address) https://github.com/bitcoin/bitcoin/pull/8288
< cfields> jonasschnelli: fyi, #8085 allows for pausing/stopping the network in a way that should point out any possible side-effects
< jonasschnelli> cfields: Nice. Thanks for the info. The concern (IIRC) with my previous pause/stop PR was that it should still allow broadcasting transaction during this mode.
< cfields> jonasschnelli: i see. i suppose it'd be possible to create a state for that within CConnman.
< jtimon> why "-par" Set the number of script verification threads (%u to %d, 0 = auto, <0 = leave that many cores free ? sounds like a terrible name
< MarcoFalke> luke-jr: (Re my comment on the pull)
< MarcoFalke> We don't run on native OSX, so we don't have IP's, I guess
< MarcoFalke> Also sudo is required in .travis.yml
< MarcoFalke> jtimon, When I hear '-par' I always think of parity checks
< luke-jr> MarcoFalke: I think it's jsut the "Container-based (travis-ci.org)" that we need to cover
< bsm1175321> Does there exist any UTXO set commitment implementation as a patch/PR to bitcoin? I'm interested in running some benchmarks and comparisons of ways we might do it.
< luke-jr> I wonder if we can just use a password instead of IP whitelisting; or maybe port knocking or similar
< Chris_Stewart_5> Why is there a 'Transaction Count' inside of the Headers message? https://bitcoin.org/en/developer-reference#getheaders
< Chris_Stewart_5> Isn't it just headers that are transmitted? Seems like a transaction count would be irrelevant..
< MarcoFalke> anyone tested the hd wallet yet?
< MarcoFalke> I lost 5k regcoins :(
< MarcoFalke> I don't want to reset; It is back from august last year :3
< MarcoFalke> I am assuming, when I restore a wallet I need to derive all keys and rescan?
< MarcoFalke> jonasschnelli: ^?
< GitHub123> [bitcoin] MarcoFalke opened pull request #8309: [qa] Add wallet-hd test (master...Mf1607-qaHD) https://github.com/bitcoin/bitcoin/pull/8309
< cfields> luke-jr: can you kick that knots build again? I think i might've nailed down the problem
< GitHub112> [bitcoin] theuni opened pull request #8310: build: require boost for bench (master...fix-bench-boost) https://github.com/bitcoin/bitcoin/pull/8310
< phantomcircuit> I prefer that tests be separate commits in the same PR
< phantomcircuit> is this just me?
< sipa> phantomcircuit: seems reasonable to me
< bsm117532> It seems that the rawtransaction* calls are not yet instrumented for segwit, no? I'm trying to create a transaction that *spends* a segwit output, and having trouble shoving it into bitcoind. I suppose sipa has some tools for manipulating segwit transactions somewhere?
< sipa> rawtransaction should just work
< sipa> there are even rpc tests using it
< sipa> but likely not all calls have been tested
< sipa> so feel free to report bugs
< bsm117532> Oh ok I'll look at the tests. I'm unsure how to serialize the witness data. I mistakenly put it in the scriptSig thinking bitcoind would remove it...
< sipa> no you need to put it in the witnesz
< sipa> not the scriptsig :)
< sipa> how to serialize the witness data, read bip144
< bsm117532> Obviously. ;-)
< bsm117532> Yeah petertodd's python-bitcoinlib doesn't know about witness data or how to serialize it. Looks like I'm going to be adding it. :-)
< sipa> Good.
< sipa> also, bitcoin core's qa/rpc/test_framework already supports it