< superduper> SUPER AMAZING! I can multiply your bitcoin using block-chain exploding technology. Send me some BTC and get MUCH more back! WOW! PM me to begin!
< GitHub29> [bitcoin] NicolasDorier opened pull request #8341: Consensus: Remove calls to error() from ContextualCheckBlock (master...error-calls) https://github.com/bitcoin/bitcoin/pull/8341
< GitHub167> [bitcoin] NicolasDorier opened pull request #8342: Consensus: Trivial transform BOOST_FOREACH into for loop (master...removeforeach) https://github.com/bitcoin/bitcoin/pull/8342
< jonasschnelli> HD: there is an issue when someone load his 0.13 HD wallet in a 0.12 (non HD) Core client and generate some keys,... this will result in a mix of HD/non HD keys. Not sure if we should address this.
< gmaxwell> hm. didn't we advance the wallet version? should prevent 0.12 from opening it.
< jonasschnelli> We could... I'm just trying to write a patch.
< jonasschnelli> This means, FEATURE_HD = 129900?
< jonasschnelli> I guess we can't really use 130000 (would break master)
< jonasschnelli> gmaxwell: I just recognized that the <n> of -upgradewallet=<n> is a secret feature to set the MaxVersion of a wallet
< jonasschnelli> Whats the usecase for this?
< gmaxwell> presumably to go part of the way but not all the way to the current version? I don't recall.
< GitHub55> [bitcoin] jonasschnelli opened pull request #8343: [Wallet] Ensure <0.13 clients can't open HD wallets (master...2016/07/hd_minversion) https://github.com/bitcoin/bitcoin/pull/8343
< jtimon> NicolasDorier: if we could agree on the names of the files we want to move the code to, I think that would be helpful in terms of coordination
< jtimon> please people don't wait to the refactor window to nack #8329 and #8337
< btcdrak> belcher_ opened a ticket about account labels in Joinmarket https://github.com/JoinMarket-Org/joinmarket/issues/592
< instagibbs> btcdrak, there is intent to have labels in place before removing accounts, yes?
< Chris_Stewart_5> when connecting on the p2p network, if the connecting node sends the receiving node a ping message, does the receiving node ignore it? I.e. the receiving node always sends the first ping message
< sipa> pings should never be ignored
< Chris_Stewart_5> ok, thanks
< sipa> i think segwit backport won't be hard
< sipa> the only major conflicts are the p2p relay changes, compact blocks, and cpfp mining
< btcdrak> sipa: quite a long list heh
< sipa> btcdrak: not really
< sipa> the first two are trivial
< sipa> undoing compact blocks: just remove anything that mentions them
< sipa> making the tests work again on python2 will be more work
< luke-jr> there's a PR to change 0.12 to Py3 tests
< luke-jr> but frankly, making Python code that works on Py2 and Py3 both isn't very hard
< sipa> for a python expert, perhaps :)
< sipa> the value of the tests is much higher if tjey don't need to be changed in the backport
< luke-jr> crap, I emailed the old ML address
< gmaxwell> quick, double spend it.
< luke-jr> :x
< MarcoFalke> sipa: Rebased 8187 in case it is easier for you to just use that.