< 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
< wumpus>
I'm not sure what to do with "leveldb: generate lib independent of locale sort" https://github.com/bitcoin/bitcoin/pull/8575 it's a change to leveldb,and we no longer need it since 0.13.0, and we likely won't do a leveldb subtree update anymore for 0.12.x.
< GitHub197>
[bitcoin] laanwj closed pull request #8459: [0.13] release-notes: Do not encourage changing blockmaxsize to blockmaxweight (0.13...0.13_relnotes_remove_bad_advice) https://github.com/bitcoin/bitcoin/pull/8459
< GitHub71>
[bitcoin] laanwj closed pull request #8282: net: Feeler connections to increase online addrs in the tried table. (master...feelers3) https://github.com/bitcoin/bitcoin/pull/8282
< GitHub189>
bitcoin/master 026c6ed Wladimir J. van der Laan: Merge #8282: net: Feeler connections to increase online addrs in the tried table....
< GitHub189>
bitcoin/master dbb1f64 Ethan Heilman: Added feeler connections increasing good addrs in the tried table....
< gmaxwell>
jonasschnelli: re, service bit comment, that was my thinking too but I didn't make that argument because I didn't want to encourage another bitcoin classic like sybil attack. :)
< wumpus>
does anyone happen to have the digest mail from bitcoin-dev or core-dev containing the 0.13.0 announcement?
< wumpus>
people without GPG can't read it anymore, but who cares, they don't take security seriously so shouldn't be using bitcoin in the first place right :)
< paveljanik>
I think we should abandon GPG and Bitcoin sign everything...
< GitHub124>
[bitcoin] pstratem opened pull request #8585: Remove last caller of IncOrderPosNext (master...2016-08-24-cwallet-incorderposnext) https://github.com/bitcoin/bitcoin/pull/8585
< wumpus>
should probably update my key at bitcoin.org with all the new signatures though
< gmaxwell>
someone in #bitcoin said it didn't, which primed me to conclude it didn't when I looked. :)
< wumpus>
gmaxwell: do I need to do anything special for that? I just did gpg --export --armor 0x90C8019E36C2E964 > ../websites/bitcoin.org/laanwj-releases.asc and git sees no difference
< gmaxwell>
wumpus: https://bitcoin.org/laanwj-releases.asc should probably come with the signature of that key by your personal key. Keyserver retention of keys that are leafs isn't always all that good.
< GitHub112>
[bitcoin] laanwj closed pull request #8450: [Test] Replace rpc_wallet_tests.cpp with python RPC unit tests (master...2016-08-03-remove-rpc-wallet-tests) https://github.com/bitcoin/bitcoin/pull/8450
< GitHub65>
bitcoin/master 21857d2 Wladimir J. van der Laan: Merge #8450: [Test] Replace rpc_wallet_tests.cpp with python RPC unit tests...
< GitHub65>
bitcoin/master 9578333 Patrick Strateman: Remove rpc_wallet_tests.cpp
< gmaxwell>
wumpus: fyi there was a thread on bitcointalk recently where someone profiled bitcoin core, and was asking why we weren't using faster sha2 because it was 35% in their benchmarks. I pointed them to your work with the SIMD sha2. They seemed to think that there would be 10x speedups, so I was sad to have to disappoint them. :)
< GitHub188>
[bitcoin] sipa closed pull request #8560: Trivial: Fix two VarInt examples in serialize.h (master...fix_varint_examples) https://github.com/bitcoin/bitcoin/pull/8560
< GitHub15>
bitcoin/master f12d2b5 Pieter Wuille: Merge #8560: Trivial: Fix two VarInt examples in serialize.h...
< GitHub15>
bitcoin/master 7bd5ff4 Christian Barcenas: Trivial: Fix two VarInt examples in serialize.h
< GitHub193>
[bitcoin] jonasschnelli opened pull request #8573: Set jonasschnellis dns-seeder filter flag (master...2016/08/filter_seed) https://github.com/bitcoin/bitcoin/pull/8573
< GitHub121>
[bitcoin] rebroad opened pull request #8571: Don't disconnect just because a node's services have changed. (master...UnexpectedServicesNoDisconnect) https://github.com/bitcoin/bitcoin/pull/8571
< luke-jr>
midnightmagic: it makes me more confident Bitcoin in general can gain user awareness and security needed to succeed
< GitHub117>
[bitcoin] nomnombtc opened pull request #8568: new var DIST_CONTRIB adds useful things for packagers from contrib (master...DIST_CONTRIB) https://github.com/bitcoin/bitcoin/pull/8568
< GitHub129>
[bitcoin] rebroad opened pull request #8561: Show "end" instead of many zros when getheaders request received with… (master...LessGetheadersZeros) https://github.com/bitcoin/bitcoin/pull/8561
< GitHub27>
[bitcoin] laanwj closed pull request #8548: [wallet] Use __func__ to get function name for output printing (master...Mf1608-walletFunc) https://github.com/bitcoin/bitcoin/pull/8548
< GitHub157>
[bitcoin] laanwj closed pull request #8376: [Wallet][Trivial] Fix exception message to reference actual thrower. (master...2016-07-19-cwallet-sethmasterkey) https://github.com/bitcoin/bitcoin/pull/8376
< GitHub30>
bitcoin/master a55a018 Wladimir J. van der Laan: Merge #8548: [wallet] Use __func__ to get function name for output printing...
< GitHub30>
bitcoin/master fa785d1 MarcoFalke: Use __func__ to get function name for output printing
< c0der0>
so this is where the developers that sign bitcoin core reside? I saw the message at bitcoin.org and needed to verify if 01EA5486DE18A882D4C2684590C8019E36C2E964 is the right key