< bitcoin-git> [bitcoin] gertjaap opened pull request #16192: Catches situations where capping on maxtxfee drops the fee too low (master...issue-10122) https://github.com/bitcoin/bitcoin/pull/16192
< instagibbs> is it really true there are no tests for wallet upgrades :(
< instagibbs> #16193
< gribble> https://github.com/bitcoin/bitcoin/issues/16193 | `-upgradewallet` from pre-HD Split not working · Issue #16193 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] TheBlueMatt closed pull request #16171: Remove -mempoolreplacement to prevent needless block prop slowness. (master...2019-06-fix-tx-prop) https://github.com/bitcoin/bitcoin/pull/16171
< bitcoin-git> [bitcoin] jamesob opened pull request #16194: refactor: share blockmetadata with BlockManager (master...2019-06-au-blockman) https://github.com/bitcoin/bitcoin/pull/16194
< jonasschnelli> sipa: about the CNetMessage serialization split: what do you think about using a CNetBuffer for keeping the buffer & hash state, and once complete, we convert it into a CNetMessage (pure command / payload)?
< jnewbery> instagibbs: it really is true as far as I'm aware :(
< ryanofsky> instagibbs, #12134 adds a nice framework for writing upgrade tests, and i'd like it merged but others think it would complicate testing framework to support old rpc versions, and would prefer to check in binary wallet blobs
< gribble> https://github.com/bitcoin/bitcoin/issues/12134 | Build previous releases and run functional tests by Sjors · Pull Request #12134 · bitcoin/bitcoin · GitHub
< instagibbs> looking
< bitcoin-git> [bitcoin] jkczyz opened pull request #16195: util: Use void* throughout support/lockedpool.h (master...2019-06-arena-key) https://github.com/bitcoin/bitcoin/pull/16195
< promag> why travis didn't pick #16192?
< gribble> https://github.com/bitcoin/bitcoin/issues/16192 | Wallet: Catches situations where capping on maxtxfee drops the fee too low by gertjaap · Pull Request #16192 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke reopened pull request #16171: Remove -mempoolreplacement to prevent needless block prop slowness. (master...2019-06-fix-tx-prop) https://github.com/bitcoin/bitcoin/pull/16171
< bitcoin-git> [bitcoin] MarcoFalke pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/473c6b7c5ab0...f792395d13aa
< bitcoin-git> bitcoin/master 218697b Suhas Daftuar: Improve NOTFOUND comment
< bitcoin-git> bitcoin/master 23163b7 Suhas Daftuar: Add an explicit memory bound to m_tx_process_time
< bitcoin-git> bitcoin/master e32e084 Suhas Daftuar: Remove NOTFOUND transactions from in-flight data structures
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #15834: Fix transaction relay bugs introduced in #14897 and expire transactions from peer in-flight map (master...2019-04-fix-getdata) https://github.com/bitcoin/bitcoin/pull/15834
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16196: doc: Add release notes for 14897 & 15834 (master...1906-docRel) https://github.com/bitcoin/bitcoin/pull/16196
< bitcoin-git> [bitcoin] sdaftuar reopened pull request #15505: [p2p] Request NOTFOUND transactions immediately from other outbound peers, when possible (master...2019-02-notfound-requests) https://github.com/bitcoin/bitcoin/pull/15505
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16197: net: Use mockable time for tx download (master...1906-netMock) https://github.com/bitcoin/bitcoin/pull/16197
< darosior> Hi, with functional tests why do I need to generate >100 blocks to have my wallet knowing about the funds ? `self.nodes[0].generate(1)` then `self.nodes[0].sendtoaddress(` fails while `self.nodes[0].generate(101)` then `self.nodes[0].sendtoaddress(` passes ? Is this a good usage or should I do something else ? Reading other functional tests some seems to use the 101 trick but others don't
< sipa> darosior: maturity rule
< darosior> Thank you
< sipa> coinbase outputs are unspendable until buried 100 blocks deep
< sipa> so the wallet treats them as balance only when those blocks exist
< darosior> Yes did not think to that, thank you for the quick answer !
< jb55> oh nice scantxoutset is decently fast, gave it 100k p2pk descriptors and it finished in around 30 seconds.
< promag> jb55 yeah wallet batch pr from achow101 improved that
< jb55> promag: I thought that slowness was due to saving keys to disk
< sipa> promag: scantxoutset is completely unrelated to the wallet
< sipa> i think you're talking about importmulti
< promag> sipa: oh my bad
< promag> right it was #15741
< gribble> https://github.com/bitcoin/bitcoin/issues/15741 | Batch write imported stuff in importmulti by achow101 · Pull Request #15741 · bitcoin/bitcoin · GitHub
< jb55> I scanned all unspent p2pk outputs in the first 100k blocks, 1692540 btc still in those