< GitHub2>
[bitcoin] sipa closed pull request #8597: Move code from VERACK to VERSION (since VERACK is not requied) (master...NotDependentOnVerack) https://github.com/bitcoin/bitcoin/pull/8597
< warren>
I'm surprised to find that the gitian documentation in the bitcoin repo no longer explains the gitian default qemu-kvm (non-LXC) method of using make-base-vm.
< GitHub53>
[bitcoin] laanwj closed pull request #8612: Check for compatibility with download in FindNextBlocksToDownload (master...fixwitban) https://github.com/bitcoin/bitcoin/pull/8612
< GitHub127>
bitcoin/master 887919c Pieter Wuille: Check for compatibility with download in FindNextBlocksToDownload
< GitHub127>
bitcoin/master 84decb5 Wladimir J. van der Laan: Merge #8612: Check for compatibility with download in FindNextBlocksToDownload...
< murch>
sipa: I didn't get a ticket for Scaling Bitcoin unfortunately. :( I'm now hoping that my proposal will be accepted, otherwise it looks like I might not be able to go. (I'm on the waiting list.)
< murch>
sipa: I had read part of the discussion on the BIP status updates on the dev list. There was a bit about the gap limit there and I assumed that Bitcoin Core also implements BIP44.
< achow101>
the idea is that the user should be able to just start Bitcoin Core with no options (except server=1 I guess) and the software (Armory) would be able to automatically know how to connect to the server without any user input
< GitHub112>
[bitcoin] JeremyRubin opened pull request #8633: Ugly hack to print out tests as they are run to mitigate travis timeouts (master...test-driver-hack) https://github.com/bitcoin/bitcoin/pull/8633
< GitHub111>
[bitcoin] JeremyRubin opened pull request #8632: Speed up prevector tests by parallelization (master...faster_prevector_tests) https://github.com/bitcoin/bitcoin/pull/8632
< GitHub184>
[bitcoin] theuni opened pull request #8631: Nuke boost::thread and boost::thread_group (master...no-interrupt-threads) https://github.com/bitcoin/bitcoin/pull/8631
< GitHub7>
[bitcoin] isle2983 opened pull request #8625: [doc] - clarify statement about parallel jobs in rpc-tests.py (master...rpcTestsDoc) https://github.com/bitcoin/bitcoin/pull/8625
< GitHub24>
[bitcoin] sipa closed pull request #8617: Include instructions to extract Mac OS X SDK on Linux using 7zip and SleuthKit (master...gitian_osx_extractor) https://github.com/bitcoin/bitcoin/pull/8617
< GitHub154>
bitcoin/master de07fdc Pieter Wuille: Merge #8617: Include instructions to extract Mac OS X SDK on Linux using 7zip and SleuthKit...
< GitHub154>
bitcoin/master b729fcd Luke Dashjr: Include instructions to extract Mac OS X SDK on Linux using 7zip and SleuthKit
< GitHub97>
[bitcoin] rebroad closed pull request #8618: [WIP] Erase orphans only when banned (master...EraseOrphansOnlyWhenBanned) https://github.com/bitcoin/bitcoin/pull/8618
2016-08-28
< arubi>
would love if someone took a look at https://github.com/bitcoin/bitcoin/pull/8598 , let me know if it's something folks would find useful or what should I do if not :) (close? leave open?)
< GitHub95>
[bitcoin] rebroad opened pull request #8618: [WIP] Erase orphans only when banned (master...EraseOrphansOnlyWhenBanned) https://github.com/bitcoin/bitcoin/pull/8618
2016-08-27
< sipa>
i'm just pring it to bitcoin already to make testing easier
< GitHub126>
[bitcoin] luke-jr opened pull request #8617: Include instructions to extract Mac OS X SDK on Linux using 7zip and SleuthKit (master...gitian_osx_extractor) https://github.com/bitcoin/bitcoin/pull/8617
< GitHub51>
[bitcoin] sipa opened pull request #8612: Check for compatibility with download in FindNextBlocksToDownload (master...fixwitban) https://github.com/bitcoin/bitcoin/pull/8612
< midnightmagic>
Bitcoin Classic -- DDoS'ing the Bitcoin network since 2016.
< GitHub4>
[bitcoin] nomnombtc opened pull request #8608: Install manpages via make install, also add some autogenerated manpages (master...man_automake2) https://github.com/bitcoin/bitcoin/pull/8608
< sipa>
SyntaxError: Non-ASCII character '\xf0' in file /home/pw/git/bitcoin/qa/rpc-tests/test_framework/util.py on line 180, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details
< GitHub114>
[bitcoin] laanwj closed pull request #8602: [trivial][doc] Mention ++i as preferred over i++ in dev notes (master...trvial-dev-notes) https://github.com/bitcoin/bitcoin/pull/8602
< GitHub182>
bitcoin/master bb56676 Wladimir J. van der Laan: Merge #8602: [trivial][doc] Mention ++i as preferred over i++ in dev notes...
< GitHub182>
bitcoin/master ab53207 fanquake: [trivial][doc] Mention ++i as preferred to i++ in dev notes
< wumpus>
heh, bitcoin can no longer be compiled with gcc 4.9.3 with OpenBSD's default max data segment limit of 1536MB
< GitHub9>
[bitcoin] fanquake opened pull request #8603: [trivial][doc] Mention gpg --refresh-keys in release-process.md (master...release-process-refresh-keys) https://github.com/bitcoin/bitcoin/pull/8603
< GitHub56>
[bitcoin] fanquake opened pull request #8602: [trivial][doc] Mention ++i as preferred over i++ in dev notes (master...trvial-dev-notes) https://github.com/bitcoin/bitcoin/pull/8602
< GitHub44>
[bitcoin] laanwj closed pull request #8227: tests: Re-enable RPC tests for Windows (master...2016_05_win_reenable_rpc_tests) https://github.com/bitcoin/bitcoin/pull/8227
< GitHub138>
[bitcoin] laanwj closed pull request #7132: Add option to opt into full-RBF when sending funds (master...2015-11-opt-into-full-rbf-option) https://github.com/bitcoin/bitcoin/pull/7132
< GitHub161>
[bitcoin] laanwj opened pull request #8601: Add option to opt into full-RBF when sending funds (rebase) (master...2016_08_full_rbf_option) https://github.com/bitcoin/bitcoin/pull/8601
< GitHub65>
[bitcoin] MarcoFalke opened pull request #8600: [0.13.1]: Backport [wallet] rpc: Drop misleading option (0.13...Mf1608-walletRpcDropBackport) https://github.com/bitcoin/bitcoin/pull/8600
< jonasschnelli>
Yes. But IMO is a fact that people have stopped running bitcoin-qt because of its extensive resource consumption. But maybe I'm wrong here.
< gmaxwell>
if you've figured out that bitcoin is the cause you are already more advanced than we should hope for, usually once they've figured that out bitcoin is doomed. :P
< gmaxwell>
then we should fix it so that it doesn't screw up voip, _generally_, even when they don't know bitcoin is the cause, not by finding some obscure option.
< jonasschnelli>
My goal is that people will not shut down bitcoin-qt in order to do a VoIP call (because restarting in pain in the ass).
< gmaxwell>
So for example, bandwidth bursts are distrubing their VoIP, so they ask for a pause. We can provide, but 1% of the users having the problem will find it and use it, the rest will suffer or just remove bitcoin.
< jonasschnelli>
sipa: regarding your profiles idea: https://github.com/bitcoin/bitcoin/issues/8437, how could setting profile values make sense? I guess in bitcoin.conf would be ideal (not another file), this would mean, it must be something like -profile0-par or -profile1-maxconnections, etc.
< GitHub110>
[bitcoin] laanwj closed pull request #8561: Show "end" instead of many zeros when getheaders request received with a hashStop of Null (master...LessGetheadersZeros) https://github.com/bitcoin/bitcoin/pull/8561
< GitHub129>
bitcoin/master 259ee09 R E Broadley: Show "end" instead of many zeros when getheaders request received with a hashStop of Null.
< GitHub129>
bitcoin/master 6c9f1b8 Wladimir J. van der Laan: Merge #8561: Show "end" instead of many zeros when getheaders request received with a hashStop of Null...
< GitHub164>
[bitcoin] laanwj closed pull request #8595: [Wallet] Ensure <0.13 clients can't open HD wallets (master...2016/07/hd_minversion) https://github.com/bitcoin/bitcoin/pull/8595
< GitHub48>
[bitcoin] fivepiece opened pull request #8598: Fix displaying of invalid and non-minimal small pushes as numbers (master...fixasm) https://github.com/bitcoin/bitcoin/pull/8598
< GitHub134>
[bitcoin] jonasschnelli closed pull request #8135: [OSX] fix make deploy when compiling on OSX (master...2016/06/makedeploy) https://github.com/bitcoin/bitcoin/pull/8135
< GitHub61>
[bitcoin] rebroad opened pull request #8597: [WIP] Move code from VERACK to VERSION (since VERACK is not requied) (master...NotDependentOnVerack) https://github.com/bitcoin/bitcoin/pull/8597
< dcousens>
phantomcircuit: nevermind, its just bitcoin-cli being smart :)
< kanzure>
18:53 < kanzure> saurik: bitcoin core just a bunch of people hanging out on irc doing stuff. so i pinged you about it.
< kanzure>
16:54 < saurik> so, I just spent a bunch of time making certain I didn't miss anything via IRC, and I've also checked e-mail. were they intending to tell me anything? I am kind of in shock that of all projects, bitcoin, another open source project, is now continuing the pattern of "we found something mysterious that we fixed that we don't bother mentioning directly to upstream"
< GitHub143>
[bitcoin] rebroad opened pull request #8595: [Wallet] Ensure <0.13 clients can't open HD wallets (master...2016/07/hd_minversion) https://github.com/bitcoin/bitcoin/pull/8595
< gmaxwell>
jonasschnelli: that is going a bit far, ultimately if your computere is totally compromised you probably can't use bitcoin correctly no matter having a hardware wallet or offline signing or what not.. at most you can slow the bleeding.
< gmaxwell>
jonasschnelli: in the case of the detatched signer which I think we should use in the GUI by default, it would be the encrypted master key. But bitcoin-core wouldn't really know or care what it is.
< jonasschnelli>
If we scale and all uses that jump on the nicely scaled bitcoin bus and use webbased or heavy centarlized insecure walltes... we can stop focus on consensus and p2p
< CodeShark>
wallet stuff really needs to be a separate project - bitcoin-core-dev should focus on consensus and p2p stuff :p
< btcdrak>
yes. detached signing is more for the bitcoin-dev ML
< wumpus>
it makes no sense to try to support detached signing in bitcoin core until there is some kind of standard, if every hw vendor is going to hook in their own code in their own way it isgoing to be a mess
< GitHub181>
[bitcoin] rebroad opened pull request #8591: Do not relay or mine excessive sighash transactions (master...NoExcessiveSighashTxs) https://github.com/bitcoin/bitcoin/pull/8591
< GitHub60>
[bitcoin] sipa closed pull request #7984: Optional parameter for rescans to start at a specified height (master...rescan-fromheight) https://github.com/bitcoin/bitcoin/pull/7984
< GitHub152>
[bitcoin] sipa opened pull request #8589: Inline CTxInWitness inside CTxIn (on top of #8580) (master...segwitinlinepain) https://github.com/bitcoin/bitcoin/pull/8589