--- Day changed Thu Mar 15 2018 00:00 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 00:00 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-jkoqtawqccnnvtfn] has quit [Quit: Connection closed for inactivity] 00:01 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 00:02 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 00:12 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 00:13 -!- go1111111 [go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #bitcoin-core-dev 00:16 -!- byteideas [9cc5aaf9@gateway/web/freenode/ip.156.197.170.249] has quit [Ping timeout: 260 seconds] 00:19 -!- dx25 [~dx25@174-19-89-235.omah.qwest.net] has quit [Ping timeout: 245 seconds] 00:23 -!- Deacyde [~Deacyde@unaffiliated/deacyde] has quit [Read error: Connection reset by peer] 00:23 -!- dx25 [~dx25@97.119.186.66] has joined #bitcoin-core-dev 00:25 -!- jojeyh [~delphi@2602:306:b8b6:b970:61e9:9d9f:5d9b:d62c] has quit [Ping timeout: 276 seconds] 00:27 -!- schmidty [~schmidty@c-98-212-53-76.hsd1.il.comcast.net] has joined #bitcoin-core-dev 00:28 -!- schmidty is now known as Guest48221 00:29 -!- LeMiner2 [LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has joined #bitcoin-core-dev 00:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:32 -!- Guest48221 [~schmidty@c-98-212-53-76.hsd1.il.comcast.net] has quit [Ping timeout: 268 seconds] 00:32 -!- LeMiner [LeMiner@unaffiliated/leminer] has quit [Ping timeout: 264 seconds] 00:32 -!- LeMiner2 is now known as LeMiner 00:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 00:43 -!- Aliencorpse [~Aliencorp@2605:a601:b024:600:c5b2:3b71:d981:6e13] has quit [Ping timeout: 245 seconds] 00:45 -!- Aliencorpse [~Aliencorp@2605:a601:b024:600:7ce7:61dc:4a2f:4bbc] has joined #bitcoin-core-dev 00:48 -!- Amuza [~Amuza@85.159.207.5] has joined #bitcoin-core-dev 00:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds] 00:56 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 01:01 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 01:46 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Quit: Leaving] 01:51 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:53 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 01:54 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 01:56 -!- drizztbsd [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:56 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 256 seconds] 01:57 -!- drizztbsd is now known as timothy 01:57 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 01:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:59 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-belnpxbihifpwusf] has joined #bitcoin-core-dev 02:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 02:01 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 02:09 -!- Amuza [~Amuza@85.159.207.5] has quit [Quit: Leaving] 02:38 -!- atroxes [~atroxes@unaffiliated/atroxes] has joined #bitcoin-core-dev 02:38 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has joined #bitcoin-core-dev 02:45 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 02:51 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-kyipvhblzzoywsfz] has joined #bitcoin-core-dev 03:07 -!- kryptopraxis [~kryptopra@p200300C853C97E00556FEE6990F1CBFD.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 03:09 -!- kryptopraxis [~kryptopra@p200300C853C97E00BDB3465AE1AEEDDB.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 03:17 -!- harding [~harding@mail.dtrt.org] has joined #bitcoin-core-dev 03:27 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 03:28 < bitcoin-git> [bitcoin] kallewoof closed pull request #10386: [WIP] [wallet] Optional '-avoidreuse' flag which defaults to not reusing addresses in sends (master...feature-white-black-address) https://github.com/bitcoin/bitcoin/pull/10386 03:29 < bitcoin-git> [bitcoin] kallewoof closed pull request #10585: [WIP] PoW connection slots (master...pow-connection-slots) https://github.com/bitcoin/bitcoin/pull/10585 03:30 < bitcoin-git> [bitcoin] kallewoof closed pull request #10877: [rpc] Verbose flags for chaining and scripting (master...verbose-flagging) https://github.com/bitcoin/bitcoin/pull/10877 03:31 -!- pyericz [~pyericz@117.30.212.207] has quit [Quit: This computer has gone to sleep] 03:32 -!- rongze [~rongze@106.38.57.250] has joined #bitcoin-core-dev 03:34 -!- rongze [~rongze@106.38.57.250] has quit [Client Quit] 03:36 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 03:43 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev 04:20 -!- jl2012_ [sid133844@unaffiliated/jl2012] has joined #bitcoin-core-dev 04:21 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 04:21 -!- arowser_ [~quassel@106.120.101.38] has joined #bitcoin-core-dev 04:22 -!- BCBot_ [~BCBot@46.101.246.115] has joined #bitcoin-core-dev 04:22 -!- sjums_ [~nick@hurtig.ninja] has joined #bitcoin-core-dev 04:22 -!- iwkse_ [~iwkse@sinusia.com] has joined #bitcoin-core-dev 04:22 -!- comboy_ [~quassel@tesuji.pl] has joined #bitcoin-core-dev 04:22 -!- earlz_ [~earlz@earlz.net] has joined #bitcoin-core-dev 04:23 -!- Eliel_ [~jojkaart@104-250-47-212.rev.cloud.scaleway.com] has joined #bitcoin-core-dev 04:23 -!- gwollon [~gwillen@unaffiliated/gwillen] has joined #bitcoin-core-dev 04:24 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has joined #bitcoin-core-dev 04:24 -!- delpa^ [~punch@8.12.28.87] has joined #bitcoin-core-dev 04:25 -!- Deadhandd [~deadhand@CPE6038e0be3871-CMf0f249a14e40.cpe.net.cable.rogers.com] has joined #bitcoin-core-dev 04:25 -!- nullptr_ [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev 04:27 -!- jl2012_ is now known as jl2012 04:27 -!- Netsplit *.net <-> *.split quits: BashCo_, so, BCBot, earlz, gwillen, vicenteH, DrFeelGood, iwkse, comboy, Eliel, (+5 more, use /NETSPLIT to show all of them) 04:28 -!- Evel-Knievel [~Evel-Knie@81.82.247.68] has joined #bitcoin-core-dev 04:28 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 260 seconds] 04:28 -!- punch [~punch@8.12.28.87] has quit [Ping timeout: 260 seconds] 04:28 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Ping timeout: 260 seconds] 04:28 -!- vicenteH` [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 04:28 -!- asoltys_ [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 260 seconds] 04:28 -!- jl2012 [sid133844@unaffiliated/jl2012] has quit [Changing host] 04:28 -!- jl2012 [sid133844@gateway/web/irccloud.com/x-cjaoumsvhsiqvsuf] has joined #bitcoin-core-dev 04:29 -!- Netsplit over, joins: so 04:30 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 04:32 -!- Netsplit over, joins: DrFeelGood 04:33 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 04:34 -!- Netsplit over, joins: p3tr 04:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 04:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 04:48 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 04:57 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 04:59 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 05:06 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 05:11 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 05:12 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 05:16 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 05:20 < bitcoin-git> [bitcoin] eklitzke opened pull request #12695: [build] Fix some strange behavior with --enable-debug (master...enabledebug) https://github.com/bitcoin/bitcoin/pull/12695 05:31 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 05:41 -!- LeMiner [LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has quit [Ping timeout: 264 seconds] 05:43 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 05:48 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 05:50 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 06:17 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 06:19 -!- schmidty [~schmidty@c-98-212-53-76.hsd1.il.comcast.net] has joined #bitcoin-core-dev 06:19 -!- schmidty is now known as Guest43997 06:24 -!- Strepsils [~textual@109.87.232.207] has joined #bitcoin-core-dev 06:25 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 06:33 -!- BCBot_ [~BCBot@46.101.246.115] has quit [Remote host closed the connection] 06:34 -!- BCBot [~BCBot@46.101.246.115] has joined #bitcoin-core-dev 06:38 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 246 seconds] 06:39 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 06:39 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 06:40 -!- Samdney [~Samdney@178.162.209.133] has joined #bitcoin-core-dev 06:54 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #bitcoin-core-dev 06:57 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 06:57 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 06:59 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:01 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 07:05 -!- Guest1754 [~jeremy@5.101.172.68] has joined #bitcoin-core-dev 07:05 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 07:13 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 07:15 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 246 seconds] 07:19 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-belnpxbihifpwusf] has quit [Quit: Connection closed for inactivity] 07:19 < GAit> While doing some regtesting I've noticed that the mempool returned by getrawmempool is sometimes a subset of what I expect if core is processing a block while I ask, even if getbestblockhash returns the same blockhash prior and post getting the rawmempool. Is this known/expected behavior? 07:20 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 07:21 < bitcoin-git> [bitcoin] eklitzke opened pull request #12696: Fix possible data race when committing block files (master...fsync) https://github.com/bitcoin/bitcoin/pull/12696 07:22 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 07:25 -!- Strepsils [~textual@109.87.232.207] has quit [Read error: Connection reset by peer] 07:28 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 07:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 07:44 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 07:45 -!- ProfMac_ [~ProfMac@2001:470:b8ac:0:1836:8087:27b1:2fce] has quit [Quit: Leaving] 07:45 -!- ProfMac_ [~ProfMac@2001:470:b8ac:0:5106:b4c:d5e6:6f80] has joined #bitcoin-core-dev 07:52 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 08:10 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 08:14 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 246 seconds] 08:15 -!- grafcaps [~haroldbr@104.137.194.255] has joined #bitcoin-core-dev 08:29 -!- Squidicc [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Quit: Oh no, not again] 08:29 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 08:38 -!- weez17 [~isaac@unaffiliated/weez17] has quit [Quit: leaving] 08:38 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 08:40 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 08:55 -!- Strepsils [~textual@109.87.232.207] has joined #bitcoin-core-dev 08:56 -!- Apex [~none@c-73-221-225-225.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 08:59 -!- HFRadical [~none@103.254.153.99] has quit [Ping timeout: 264 seconds] 09:04 -!- Strepsils [~textual@109.87.232.207] has quit [Read error: Connection reset by peer] 09:06 < bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/e057589dc67f...947c25ead21a 09:06 < bitcoin-git> bitcoin/master 152b7fb James O'Beirne: [tests] Add a (failing) test for waitforblockheight... 09:06 < bitcoin-git> bitcoin/master f98b543 James O'Beirne: Only call NotifyBlockTip when the active chain changes... 09:06 < bitcoin-git> bitcoin/master 947c25e Wladimir J. van der Laan: Merge #12431: Only call NotifyBlockTip when chainActive changes... 09:07 < bitcoin-git> [bitcoin] laanwj closed pull request #12431: Only call NotifyBlockTip when chainActive changes (master...jamesob/2018-02-prevent-bad-latestblock) https://github.com/bitcoin/bitcoin/pull/12431 09:11 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev 09:14 -!- Apex [~none@c-73-221-225-225.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 09:20 < instagibbs> murchandamus, any notion on whether single random draw should prune after hitting it's required value? 09:21 < instagibbs> scan the list again, try to remove items and stay above thresh. I have a hunch that any gain of "more distributed" output values from pure draw are outweighed by spending an addition utxo *now* 09:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 09:34 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:34 -!- Randolf [~randolf@207.81.117.86] has joined #bitcoin-core-dev 09:36 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 09:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 09:41 -!- Lis [4d7d6094@gateway/web/freenode/ip.77.125.96.148] has joined #bitcoin-core-dev 09:54 -!- luxferro [817a11f0@gateway/web/freenode/ip.129.122.17.240] has joined #bitcoin-core-dev 09:57 -!- Randolf [~randolf@207.81.117.86] has quit [Ping timeout: 240 seconds] 10:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:16 -!- rex_4539 [~textual@2a02:587:3513:b600:45ac:2e04:e241:4416] has joined #bitcoin-core-dev 10:18 < promag> wumpus: on #12624 s/0.15/0.17? 10:18 < gribble> https://github.com/bitcoin/bitcoin/issues/12624 | Release schedule for 0.17.0 · Issue #12624 · bitcoin/bitcoin · GitHub 10:19 < wumpus> ? 10:19 < promag> in the issue description 10:19 < promag> "Finalize and close translations for 0.15" 10:19 < wumpus> that's correct 10:19 < promag> oh 10:20 < promag> ok sorry 10:20 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:edd7:b7f1:689e:9581] has joined #bitcoin-core-dev 10:21 < instagibbs> how many hours/minutes until dev meeting? clock change in US... 10:21 -!- d_t [~d_t@108-65-78-188.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev 10:22 < sipa> instagibbs: 98 10:22 < wumpus> $ date -u -> Thu Mar 15 17:22:05 UTC 2018 -> 1 hour and 8 minutes 10:22 < wumpus> eh 38 10:24 -!- luxferro [817a11f0@gateway/web/freenode/ip.129.122.17.240] has quit [Ping timeout: 260 seconds] 10:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 10:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 10:39 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:43 < instagibbs> Core wallet currently orders inputs based on the CInputCoin ordering, which orders in non-descending order via COutPoint... wouldn't it be better to shuffle for privacy? 10:43 < instagibbs> or are other wallets doing this as well 10:44 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:edd7:b7f1:689e:9581] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 10:45 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 10:50 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 260 seconds] 10:53 < sipa> instagibbs: it doesn't shuffle? :o 10:54 < instagibbs> nope, it uses std::set which uses, I believe, the comparator of the underlying type 10:54 < instagibbs> based on my internetting 10:54 < instagibbs> either way it's definitely not shuffled 10:56 < Murch> instagibbs, sipa: Wouldn't it be fine if they were sorted by outpoint? 10:56 < instagibbs> Murch, I'm not particularly bothered, provided it's a standard thing wallets do. I assumed everything was shuffled 10:57 < Murch> The thing that you would want to obfuscate, is the order in which they were picked, or when they come from different wallets and such. If they'd all be ordered by the outpoint that would still be obfuscated 10:57 < instagibbs> it's saying "I'm a Core wallet!" unless others do it as well 10:57 < instagibbs> Slowly hoping we can stop announcing that so much :) 10:57 < gmaxwell> I'd rather it sorted by script pubkey. 10:58 < gmaxwell> (ignoring the consideration of distinguishability vs other software) 10:58 < GAit> please ignore my comment above re: bestblockhash and getrawmempool, looks like i got confused 10:58 < wumpus> instagibbs: as there is no common standard between wallets how to do those things, I suppose all software is pretty distinguishable 10:58 < gmaxwell> (the reason for scriptpubkey is that we came up with a compact encoding that is much smaller when spk's are reused in adjcent outputs) 10:59 < luke-jr> gmaxwell: I would think that encoding would be detrimental since it encourages reuse 11:00 < instagibbs> luke-jr, doesn't make anything cheaper for wallet though 11:00 < luke-jr> at the very least, though, I'd think we should use a std::unordered_set 11:00 < luke-jr> instagibbs: not relevant; it encourages reuse because many people DO care about the health of the network 11:01 < gmaxwell> luke-jr: it doesn't encourage it. 11:01 < gmaxwell> it's not like you pay lower fees due to it. 11:01 < instagibbs> luke-jr, nuking your own privacy is a larger negative :/ 11:01 < instagibbs> imo 11:01 < luke-jr> instagibbs: hopefully 11:01 < instagibbs> own and others* 11:02 < luke-jr> instagibbs: but some people already do it, so apparently not a large enough negative 11:02 < luke-jr> there's no reason to optimise reuse; in the ideal situation, it does nothing useful; in the worse situation, it's harmful 11:02 < sipa> how does it encourage reuse? 11:02 -!- gmaxwell [gmaxwell@wikimedia/KatWalsh/x-0001] has left #bitcoin-core-dev [] 11:02 < instagibbs> anyways, I'll open an issue, since I found it surprising 11:02 -!- Randolf [~randolf@96.53.76.26] has joined #bitcoin-core-dev 11:03 < Randolf> Hello. 11:03 < sipa> i think they should be randomly ordered 11:03 < sipa> we can't guess what other wallets are doing, but a random sort will at least sometimes be indistinguishable from others 11:04 < wumpus> yes, why not 11:04 < wumpus> there seems to be no reason to *not* randomly order inputs, at least with SIGHASH_ALL 11:04 < luke-jr> Randolf: hi (you're an hour early) 11:04 -!- zarez [~Thunderbi@fs-93-93-44-38.fullsave.info] has quit [Ping timeout: 248 seconds] 11:04 < Randolf> I am? 11:05 < sipa> timezones are confusing 11:05 < Randolf> Oh, I'm in Pacific Time. 11:05 < sipa> the meeting is 8pm UTC 11:05 < luke-jr> everyone should switch to tonal time ;) 11:05 < sipa> or 7pm? 11:05 < wumpus> 7 11:05 < Randolf> I've heard that Decimal Time is quite good -- only 10 hours in a day, 100 minutes per hours, but the seconds are a bit strange. 11:05 < luke-jr> Randolf: that's pretty insane, not good :P 11:06 < instagibbs> I can PR, it seems strictly better to shuffle imo, I've never heard of this COutPoint ordering used anywhere else 11:07 < wumpus> instagibbs: ok 11:08 < Murch> Randolf: If your calendar supports it, you can just set the event's time to the 7pm UTC, and it'll automatically fix weird shifts like that for you. ;) 11:09 < sipa> Protip: Iceland is always on UTC 11:09 < luke-jr> Murch: (and put the meeting overlapping with picking kids up at school, it seems) 11:09 < jcorgan> protip: if your calendar doesn't support UTC as a time zone, setting it to Iceland 11:09 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 11:09 < jcorgan> heh 11:10 < sipa> !hi5 jcorgan 11:10 < luke-jr> sadly, Florida just voted to make DST permanent/year-round, so this is going to be a persistent issue for me :x 11:10 < gribble> Error: "hi5" is not a valid command. 11:10 < sipa> luke-jr: which apprently violates federal law 11:10 < Randolf> Murch: Thanks. 11:10 < luke-jr> sipa: ⁈ 11:10 < Murch> Getting rid of summertime would be great. 11:10 < jcorgan> getting rid of timezones would be great 11:10 < sipa> luke-jr: states apparently have a right to choose whether they adopt DST or not, but not what timezone they are in 11:11 < luke-jr> sipa: so how does choosing to adopt DST year-round violate federal law? :P 11:11 < CubicEarths> Obviously solution - Set the meeting for a block height :) 11:12 < luke-jr> CubicEarths: that would be a bit chaotic, but maybe fun for a few meetings 11:12 -!- moneyball [49df4995@gateway/web/freenode/ip.73.223.73.149] has joined #bitcoin-core-dev 11:12 < luke-jr> (and probably super annoying after a few) 11:12 < jcorgan> miner incentives to delay or advance core mtgs :) 11:13 < luke-jr> perhaps I'll learn to go to school early with a laptop, and join the meeting from there ;) 11:14 < instagibbs> yes you creeping around the school parking lot with a laptop wont sound any alarms 11:14 < luke-jr> lol 11:15 < luke-jr> I'll need to get the wifi password from them first anyway 11:15 < wumpus> I wouldn't mind moving it an hour earlier or later, but whatever time is chosen it's probably inconvenient to someone, and for the people in aus/asia it won't help 11:16 < wumpus> CubicEarths: I guess that would be 'fair' for some definitions of fair, but hard to plan for :) 11:17 < luke-jr> if we had more eastern devs, it might be "fair" to just shift it by 8 hours every week 11:18 < wumpus> yes 11:18 < sipa> how about shifting by 7 hours every week? that would over long periods of time uniformly distribute meetings :) 11:19 < sipa> (no, not a serious suggestion) 11:20 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #bitcoin-core-dev 11:20 < luke-jr> anyhow, topic for meeting hopefully we can cover in the first ~10 minutes: multiwallet GUI, finally getting it merged? 11:21 < luke-jr> jonasschnelli: will you be here? XD 11:22 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 11:23 -!- moneyball [49df4995@gateway/web/freenode/ip.73.223.73.149] has quit [Quit: Page closed] 11:27 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 11:28 -!- jtimon [~quassel@142.29.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 11:29 -!- Randolf [~randolf@96.53.76.26] has quit [Ping timeout: 248 seconds] 11:30 -!- HFRadical [~none@103.254.153.99] has joined #bitcoin-core-dev 11:30 -!- HFRadical [~none@103.254.153.99] has quit [Max SendQ exceeded] 11:31 -!- HFRadical [~none@103.254.153.99] has joined #bitcoin-core-dev 11:39 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 11:41 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-kyipvhblzzoywsfz] has quit [Quit: Connection closed for inactivity] 11:42 -!- blackjarvis [~jarvis@110.93.85.112] has joined #bitcoin-core-dev 11:42 -!- Apex [~none@c-73-221-225-225.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 11:42 -!- blackjarvis [~jarvis@110.93.85.112] has quit [Read error: Connection reset by peer] 11:44 -!- HFRadical [~none@103.254.153.99] has quit [Ping timeout: 240 seconds] 11:45 -!- blackjarvis [~blackjarv@110.93.85.112] has joined #bitcoin-core-dev 11:47 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 11:49 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit] 11:51 < bitcoin-git> [bitcoin] instagibbs opened pull request #12699: Shuffle transaction inputs before returning from SelectCoins (master...shuffleinputs) https://github.com/bitcoin/bitcoin/pull/12699 11:51 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hqeqbkgcreeabdai] has joined #bitcoin-core-dev 11:52 -!- HFRadical [~none@103.254.153.99] has joined #bitcoin-core-dev 11:52 -!- Lis [4d7d6094@gateway/web/freenode/ip.77.125.96.148] has quit [Ping timeout: 260 seconds] 11:53 -!- Apex [~none@c-73-221-225-225.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 11:58 -!- Guest1754 [~jeremy@5.101.172.68] has quit [Ping timeout: 240 seconds] 11:59 -!- rex_4539 [~textual@2a02:587:3513:b600:45ac:2e04:e241:4416] has quit [Ping timeout: 246 seconds] 12:00 < wumpus> meeting? 12:01 < provoostenator> hi 12:01 < wumpus> #startmeeting 12:01 < lightningbot> Meeting started Thu Mar 15 19:01:22 2018 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:01 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:01 < wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator 12:01 < meshcollider> eHi 12:01 < meshcollider> Hi* 12:01 < cfields> hi 12:01 -!- Randolf [~randolf@72.143.234.26] has joined #bitcoin-core-dev 12:01 < wumpus> any topics? 12:02 < wumpus> #topic high priority for review 12:02 < luke-jr> GUI multiwallet 12:02 < wumpus> only 5 things left: https://github.com/bitcoin/bitcoin/projects/8 12:02 < achow101> hi 12:02 < luke-jr> wumpus: the wrong multiwallet PR is included in that :/ 12:02 < wumpus> cfields should probably rebase the banman 12:03 < cfields> nobody rebases banman! 12:03 < Randolf> Hello. 12:03 < cfields> (will do) 12:03 < achow101> #12560 please 12:03 < gribble> https://github.com/bitcoin/bitcoin/issues/12560 | [wallet][RPC] Set or generate a new HD seed by achow101 · Pull Request #12560 · bitcoin/bitcoin · GitHub 12:03 < wumpus> cfields: was already afraid the banman wouldn't agree with that :) 12:03 < luke-jr> #11383 12:03 < gribble> https://github.com/bitcoin/bitcoin/issues/11383 | Basic Multiwallet GUI support by luke-jr · Pull Request #11383 · bitcoin/bitcoin · GitHub 12:03 < cfields> heh 12:03 < wumpus> chainhead: added 12:04 < wumpus> achow101: added, I mean, sorry chainhead 12:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:04 -!- moneyball [49df4995@gateway/web/freenode/ip.73.223.73.149] has joined #bitcoin-core-dev 12:04 < wumpus> as jonasschnelli isn't here, I don't think discussing multiwallet GUI makes much sense :/ 12:04 < meshcollider> I'd like to see #12254 on there 12:04 < gribble> https://github.com/bitcoin/bitcoin/issues/12254 | BIP 158: Compact Block Filters for Light Clients by jimpo · Pull Request #12254 · bitcoin/bitcoin · GitHub 12:05 < promag> hi 12:05 < wumpus> ok 12:05 < luke-jr> wumpus: ok 12:05 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 12:06 < kanzure> hi. 12:06 -!- qrest [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Remote host closed the connection] 12:06 < wumpus> so apart from that, we have two PRs by BlueMatt on there 12:07 < BlueMatt> yea, those should be removed as they have not yet beedn rebased (I think) 12:07 < BlueMatt> also I dont recall how two ended up on there...thats clearly cheating 12:07 < kanzure> http://diyhpl.us/wiki/transcripts/bitcoin-core-dev-tech/2018-03-07-priorities/ 12:07 < wumpus> ok 12:08 < cfields> feel free to remove banman for being non-rebased as well. I'll try to get to it today/tomorrow, but I *think* that's in fitting with the discussion we had 12:08 < achow101> +1 on removing things that need rebasing 12:08 < wumpus> cfields: ok, done 12:08 < wumpus> can always be readded 12:09 < Randolf> I suspect that more people would do rebasing if the web-interface provided an option for that. 12:09 < wumpus> and yes, it's consistent and fair with BlueMatt 12:09 < wumpus> Randolf: not all rebases are trivial one-click affairs 12:09 < Randolf> That's true. 12:10 < wumpus> other topics? 12:10 < meshcollider> luke's multiwallet stuff 12:10 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 12:10 < Randolf> There seems to be confusion about whether Lightning Network is supported in Bitcoin 0.16. 12:10 < sipa> ... 12:10 < BlueMatt> wut 12:10 < wumpus> I don't think discussing GUI multiwallet makes sense without jonasschnelli here, but if you really want to discuss it meshcollider we could 12:10 < sipa> there is no such thing as "Bitcoin 0.16" 12:11 < promag> I would like some feedback here https://github.com/bitcoin/bitcoin/pull/12507#issuecomment-372367647 12:11 < Randolf> I meant v0.16. 12:11 < sipa> and if you mean Bitcoin Core, that has nothing to do with Lightning 12:11 < achow101> Randolf: from who? 12:11 < wumpus> lightning is 'supported' since segwit was activated 12:11 < meshcollider> wumpus: true I'm indifferent, I'd just like to see a decision be made lol 12:11 < Randolf> achow101: Well, I see the question come up from time-to-time in the #bitcoin channel, and in other IRC channels there's disagreement about whether it's fully implemented or at all. 12:11 < BlueMatt> Randolf: please take this after the meeting 12:11 < Randolf> I'm thinking that it may be good to indicate it prominently on the bitcoin.org web site or a readme file clearly. 12:12 < Randolf> Okay. 12:12 < promag> regarding multiwallet gui, IMO both still have some things to fix 12:12 < provoostenator> I'd also like the multiwallet stuff to go forward, but does it get in the way of the RPC Interface stuff? 12:12 < promag> provoostenator: you mean #10740? 12:12 < gribble> https://github.com/bitcoin/bitcoin/issues/10740 | [WIP] [wallet] dynamic loading/unloading of wallets by jnewbery · Pull Request #10740 · bitcoin/bitcoin · GitHub 12:13 < wumpus> #topic Multiwallet GUI 12:13 < wumpus> ok 12:13 < luke-jr> promag: there's nothing left to fix in #11383; just needs a rebasing since a day or so ago 12:13 < gribble> https://github.com/bitcoin/bitcoin/issues/11383 | Basic Multiwallet GUI support by luke-jr · Pull Request #11383 · bitcoin/bitcoin · GitHub 12:14 < promag> luke-jr: receiving address and sending addresses dialogs should mention the wallet name in some place 12:14 < promag> in the title for instance 12:14 < luke-jr> I could add that, but it seems okay to wait for a later PR to add those, and would invalidate the ACKs already received :/ 12:14 < promag> also test with -disablewallet, the wallet selection should be invisible? 12:15 < promag> luke-jr: well that also works, just saying that it could be more complete 12:16 -!- arbitrary_guy [~arbitrary@c-67-183-30-122.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 12:16 < luke-jr> yes, there is much room to improve on it; but I fear causing further delays 12:16 < provoostenator> promag: no I mean #10244 12:16 < gribble> https://github.com/bitcoin/bitcoin/issues/10244 | Refactor: separate gui from wallet and node by ryanofsky · Pull Request #10244 · bitcoin/bitcoin · GitHub 12:17 < wumpus> luke-jr: I agree, at some point, if it's an improvement we should merge it, it doesn't have to do every single thing people can think of 12:17 < provoostenator> luke-jr: and there's the issue of putting model state in UI elements, which makes future changes to the design needlessly hard 12:17 < promag> provoostenator: oh I still have to see that one 12:17 < wumpus> collaboration works better on the master branch 12:17 < wumpus> but jonasschnelli had some problems with your approach 12:18 < provoostenator> E.g. if I want to change the dropdown into a menu, I now need to figure out where to keep the wallet array. The other PR handles that more elegantly (but maybe it's worse in other ways, I can't tell). 12:18 < wumpus> provoostenator: agree 12:18 < promag> well the way I see both build on top of a weak support of multiwallets 12:18 < ryanofsky> fwiw, i haven't looked at jonas pr yet, but i think luke's approach is fine. if jonas has improvements, no reason they can't go in later 12:19 < promag> maybe we should focus also on #12587, adding signals etc 12:19 < gribble> https://github.com/bitcoin/bitcoin/issues/12587 | Introduce g_wallet_manager, prepare for better dynamic wallet loading/unloading by jonasschnelli · Pull Request #12587 · bitcoin/bitcoin · GitHub 12:19 < luke-jr> wumpus: I don't think we can discuss that fairly without him, unfortunately 12:19 -!- sneakerhax [~sneakers@unaffiliated/sneakerhead] has joined #bitcoin-core-dev 12:19 < promag> I also think we should consider something like #11402 12:19 < gribble> https://github.com/bitcoin/bitcoin/issues/11402 | [wallet] Use shared pointer for wallet instances by promag · Pull Request #11402 · bitcoin/bitcoin · GitHub 12:19 < wumpus> luke-jr: I agree, I think it's a bit single sided like this 12:20 < luke-jr> promag: yes, that's one plan I had for down the road 12:20 < luke-jr> promag: which is partly why it's important we use a CWalletRef instead of wallet name string ;) 12:21 < wumpus> any other topics? 12:21 < sipa> lunch? 12:21 < luke-jr> XD 12:21 < promag> dinner? 12:21 < instagibbs> coin selection next steps? 12:22 < wumpus> already had both lunch and dinner xD 12:22 < instagibbs> a few of us had discussions during coredev, we may want to socialize those ideas? 12:22 < Randolf> Just finished lunch. 12:22 < wumpus> #topic coin selection next steps 12:22 < jtimon> is it still breakfast if it's dinner time? 12:22 < luke-jr> kallewoof's stuff, or something else? 12:22 < sipa> breakfast is defined as the first meal after waking up; the time of day is irrelevant 12:23 < luke-jr> I gotta run :x bbl 12:23 < wumpus> later luke-jr 12:23 < achow101> #12605 12:23 < gribble> https://github.com/bitcoin/bitcoin/issues/12605 | High level road map for coin selection changes · Issue #12605 · bitcoin/bitcoin · GitHub 12:23 < instagibbs> so, Branch and Bound was merged(yay), which leaves us with what to do when we cannot find an exact match. Current strategy is to fallback to Single Random Draw as per murchandamus thesis 12:23 < instagibbs> with some *, if achow101 wants to continue 12:23 < achow101> *current plannned strategy is to use SRD 12:24 * Randolf notes that SRD means Single Random Draw 12:24 < instagibbs> morcos had any idea to only SRD on coins smaller than target, to slightly bias towards spending smaller coins, for utxo set reasons 12:24 < instagibbs> debate as to whether that is even necessary were had 12:24 -!- blackjarvis [~blackjarv@110.93.85.112] has quit [Remote host closed the connection] 12:25 < instagibbs> pure SRD gives the wallet a nice distribution of utxos, which likely feeds to better BnB exact match rates 12:26 < instagibbs> that's... about it. 12:26 * jtimon wonders if that slight bias could hurt privacy somehow 12:26 < sipa> i think SRD may be a privacy issue too 12:26 < instagibbs> jtimon, might mark as Core, but right now we hoover tiny inputs 12:27 < instagibbs> sipa, versus what? 12:27 < sipa> ideally you end up with a strategy that is hard to distinguish from BnB 12:27 < jtimon> instagibbs: yeah, I'm not opposed to the idea in principle, just launching questions to the air to see what other people think 12:28 < jtimon> what was BnB? 12:28 < instagibbs> #10637 12:28 < gribble> https://github.com/bitcoin/bitcoin/issues/10637 | Coin Selection with Murchs algorithm by achow101 · Pull Request #10637 · bitcoin/bitcoin · GitHub 12:28 < meshcollider> BnB stands for Branch and bound 12:29 < sipa> instagibbs: if you have 80% of UTXO very close to 1 BTC, then SRD will be very likely to include such outputs, revealing something about your UTXO size distribution 12:29 < jtimon> thanks! 12:29 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:29 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 12:29 < instagibbs> sipa, with a 1BTC target? As oppose to BnB? 12:30 < instagibbs> Maybe we can continue post-meeting... 12:30 < sipa> yeah 12:31 * instagibbs will continue post meeting 12:32 < wumpus> ok, anything else for the meeting? 12:33 < wumpus> #endmeeting 12:33 < lightningbot> Meeting ended Thu Mar 15 19:33:01 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 12:33 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-03-15-19.01.html 12:33 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-03-15-19.01.txt 12:33 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-03-15-19.01.log.html 12:34 -!- gwollon is now known as gwillen 12:35 < achow101> instagibbs: post meeting continue? 12:35 < instagibbs> yeah, formulating thoughts 12:36 < instagibbs> sipa, I see what you mean, but I don't think other strategies are much(any?) better 12:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:36 < instagibbs> aside from quite advanced coin control 12:36 < sipa> Randolf: Lightning is implemented by software like c-lightning and lnd. Bitcoin is implemented by software like Bitcoin Core and btcd. They are otherwise unrelated. 12:37 < sipa> Particular implementations of lightning may or may not require you to run particular bitcoin implementations, but that depends heavily on what software is involved. 12:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 12:37 -!- Randolf [~randolf@72.143.234.26] has quit [Ping timeout: 240 seconds] 12:38 < meshcollider> e.g. lnd requires either core or btcd, c-lightning and eclair both requires core 12:39 < sipa> he left 12:39 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:39 -!- Guest1754 [~jeremy@94.229.76.45] has joined #bitcoin-core-dev 12:40 < instagibbs> BnB dodges this issue I think by 1) not having change 2) "over fitting" to the exact target. Once we have change, we have to make decisions about how big that change should be. Right now it's 1 bitcent, and ends up with Core hoovering tiny inputs to hit that. 12:41 < Murch> sorry, I was at lunch. 12:42 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:42 < Murch> BnB strictly only includes inputs smaller or equal than the target, so limiting SRD to inputs smaller than the target might make the input set more like a BnB one. 12:42 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 12:43 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 12:43 < achow101> The fact that there will be change indicates that BnB wasn't used at all though 12:44 < achow101> so I don't think it really needs to look like BnB 12:44 < instagibbs> its more about revealing stuff about the rest of your utxo set 12:44 < sipa> well ideally the chabge isn't recognizable 12:44 < instagibbs> typically it will mean a single output 12:44 < sipa> but leaking BNB or not isn't as bad as leaking information about your utxo size distribution 12:44 < Murch> sipa: with random selection, change might be bigger or smaller than the sending output, isn't that good? 12:45 < sipa> there are so many aspects to privacy, it's hard :) 12:45 < instagibbs> if you can name a counter-proposal, it may help 12:46 < instagibbs> not putting on spot, for my own imagination 12:46 < Murch> Largest first would probably also work well in combination with BnB 12:46 < Murch> :p 12:46 < instagibbs> lol 12:46 < Murch> FIFO is pretty decent all around, might leak less information about composition, but more about time distribution 12:47 < sipa> i was wondering if you could do something like randomly adding change of a particular size, and then run BnB again 12:47 < instagibbs> sipa, me too, if you can engineer a target 12:47 < sipa> but there are so many design parameters, and risk becoming very slow 12:47 < Murch> Then we'd waste all the computational work to hit something that is actually arbitrary 12:47 < instagibbs> i think picking the "right" change size using expert rules is foolhardy unless we really know more 12:48 < sipa> agree 12:48 < Murch> instagibbs: I mean you could fill buckets of change sizes, to spread combination space for BnB 12:48 < sipa> Murch: yes, absolutely - though it could run with lower computational limits or so 12:48 < Murch> but that seems overly optimistic in regard to how well we understand the overall effect 12:48 -!- moneyball [49df4995@gateway/web/freenode/ip.73.223.73.149] has quit [Quit: Page closed] 12:48 < instagibbs> Murch, wallet history to know targets, etc :) 12:49 < instagibbs> like, maybe Coinbase needs a 2 BTC utxo for daily payments, i dont! 12:49 < instagibbs> but again this leaks info if used 12:49 < instagibbs> ack on hard :( 12:49 < sipa> use change = your previous payment output amount :p 12:50 < Murch> sipa then you leak a connection to a previous tx 12:50 < sipa> oh. duh. 12:51 < Murch> It's been suggested to target the average amount of the last x spents from the wallet, to make sure the change is a useful size 12:51 < Murch> but then again we're reducing the UTXO pool's variance 12:51 < Murch> which is bad for the combination space of BnB 12:52 < Murch> so, yes, random leaks information about the distribution of the wallet's utxo pool, but only if you create a large transaction target in the first place 12:52 < Murch> otherwise the information is spread out over potentially unrelated tx in the first place 12:53 < Murch> and if you're creating a large transaction, you'd be leaking information about your wallet's utxo pool composition with most strategies 12:57 < instagibbs> sipa, i thought you were joking :P 12:58 < Murch> we could have multiple fallback algorithms that switch off. :p 12:58 < Murch> But that would be terrible to analyze 13:01 < Murch> Largest first smaller than the target might actually also be an option. 13:02 < achow101> Murch: sipa: btw started doing SRD here: https://github.com/achow101/bitcoin/tree/srd-fallback 13:03 < Murch> achow101: I've been thinking. We might want to do SRD first, since it is computationally much cheaper than BnB, and then use the waste result of the SRD as an upper bound for BnB. 13:03 < Murch> only switch to the BnB result if it has less waste. 13:04 < achow101> Murch: i don't think that it is likely for SRD to find a result that has less waste than BnB. Furthermore, that would mean we do both SRD and BnB for every selection 13:05 < Murch> Yeah, but shuffle pick from front is super cheap. 13:05 < Murch> *"Yeah, but shuffle, then pick from front is super cheap." 13:05 < instagibbs> BnB being preferred has the nice property that it ends transaction chaining in the wallet for good 13:06 < Murch> mhkay, just an idea 13:06 < instagibbs> not saying it's a bad idea, just saying it was one considering iirc 13:07 -!- rex_4539 [~textual@2a02:587:3513:b600:a9c5:865a:7961:a71] has joined #bitcoin-core-dev 13:07 < Murch> In the end it's always a question of tradeoffs. Do you want to minimize costs, maximize privacy, minimize UTXO pool, …, or some mix thereoff. ;) 13:10 < instagibbs> code complexity, transaction chaining limits... 13:14 -!- sanada [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has quit [] 13:15 -!- ProfMac_ [~ProfMac@2001:470:b8ac:0:5106:b4c:d5e6:6f80] has quit [Quit: Leaving] 13:18 -!- ProfMac [~ProfMac@2001:470:b8ac:0:5106:b4c:d5e6:6f80] has joined #bitcoin-core-dev 13:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 13:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 13:41 -!- mrannanay [uid222022@gateway/web/irccloud.com/x-luwjlsewvvpboycv] has quit [Quit: Connection closed for inactivity] 13:41 < bitcoin-git> [bitcoin] ryanofsky opened pull request #12700: Document RPC method aliasing (master...pr/alias) https://github.com/bitcoin/bitcoin/pull/12700 13:46 -!- cryptojanitor [uid278088@gateway/web/irccloud.com/x-lbocmxomimdtcrhb] has joined #bitcoin-core-dev 13:50 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:51 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 13:56 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has quit [Ping timeout: 264 seconds] 13:56 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Quit: Oh no, not again] 13:57 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 14:02 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:05 < Murch> yeah 14:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 14:06 -!- xyxxy [~nickname@c-73-206-4-43.hsd1.tx.comcast.net] has quit [Ping timeout: 245 seconds] 14:07 < Murch> instagibbs: I think that SRD or FIFO would probably be a contender for decent mix of tradeoffs, and would use one of those as a baseline to compare against. But then suggest that we compare with concrete other proposals. 14:09 < sipa> Murch: i wonder if a good strategy (perhaps only when the utxo set is large) is use a pre filtering that trims the UTXO set down, biasing in favor of amounts that are further away from other amounts 14:09 < Murch> That would definitely help BnB, and also spread out selection for SRD. Isn't that computationally intensive, though? 14:10 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 14:10 < sipa> why would it? 14:10 < sipa> it seems like it can be done with a single pass 14:10 < Murch> How would you do it? Logarithmic bucketing? 14:11 < sipa> i'll think about it 14:15 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 14:16 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 260 seconds] 14:27 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 14:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:33 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 14:35 -!- znd [d5e96074@gateway/web/freenode/session] has joined #bitcoin-core-dev 14:35 -!- znd [d5e96074@gateway/web/freenode/session] has quit [Client Quit] 14:47 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has joined #bitcoin-core-dev 14:54 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 14:56 -!- sneakerhax [~sneakers@unaffiliated/sneakerhead] has quit [Quit: Back later] 14:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 14:59 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 14:59 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 14:59 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev 15:01 -!- ula [~ula@b2b-78-94-9-226.unitymedia.biz] has joined #bitcoin-core-dev 15:07 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:edd7:b7f1:689e:9581] has joined #bitcoin-core-dev 15:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 15:14 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds] 15:20 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:edd7:b7f1:689e:9581] has quit [Ping timeout: 256 seconds] 15:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 15:29 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 15:30 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 15:31 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 15:32 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:9867:a0b1:73a3:35b8] has joined #bitcoin-core-dev 15:34 -!- tknp [~tknp@unaffiliated/tknp] has joined #bitcoin-core-dev 15:37 -!- TheCharlatan [~drgrid@109.236.87.57] has joined #bitcoin-core-dev 15:38 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 15:40 < promag> https://github.com/bitcoin/bitcoin/pull/12650#issuecomment-373538129 wut 15:42 < sipa> yeah... 15:43 < sipa> i think i can guess what you're linking to 15:44 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 15:46 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 256 seconds] 15:50 < meshcollider> Looks like spam, it's nonsense 15:52 -!- Guest1754 [~jeremy@94.229.76.45] has quit [Ping timeout: 248 seconds] 15:56 -!- rex_4539 [~textual@2a02:587:3513:b600:a9c5:865a:7961:a71] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 16:01 -!- qu4ku [~qu4ku@2a01:110f:f73:1b00:9867:a0b1:73a3:35b8] has quit [Ping timeout: 246 seconds] 16:07 < luke-jr> looks like it wants to be human :x 16:08 < sipa> i think it may be human 16:08 < midnightmagic> that's charitable 16:18 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 16:23 -!- Murch [~murch@96.74.120.81] has joined #bitcoin-core-dev 16:24 -!- dafunkiz_ [~dafunkizd@174.127.143.202] has quit [Quit: probably someone interrupted me] 16:31 < bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/947c25ead21a...df529dcc65e8 16:31 < bitcoin-git> bitcoin/master bb079a0 Drew Rasmussen: Remove unused variable in SortForBlock 16:31 < bitcoin-git> bitcoin/master df529dc Pieter Wuille: Merge #12693: Remove unused variable in SortForBlock... 16:32 < bitcoin-git> [bitcoin] sipa closed pull request #12693: Remove unused variable in SortForBlock (master...unused-sort-for-block-param) https://github.com/bitcoin/bitcoin/pull/12693 16:34 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 16:35 -!- jojeyh [~delphi@2602:306:b8b6:b970:c06a:8087:7a8:9c8f] has joined #bitcoin-core-dev 16:36 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has quit [Ping timeout: 256 seconds] 16:38 < promag> sipa: don't stop there, here is another :P #12621 16:38 < gribble> https://github.com/bitcoin/bitcoin/issues/12621 | Avoid querying unnecessary model data when filtering transactions by promag · Pull Request #12621 · bitcoin/bitcoin · GitHub 16:45 < bitcoin-git> [bitcoin] sipa pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/df529dcc65e8...2bac3e484114 16:45 < bitcoin-git> bitcoin/master 1ee72a8 João Barbosa: qt: Avoid querying unnecessary model data when filtering transactions 16:45 < bitcoin-git> bitcoin/master 2bac3e4 Pieter Wuille: Merge #12621: Avoid querying unnecessary model data when filtering transactions... 16:46 < bitcoin-git> [bitcoin] sipa closed pull request #12621: Avoid querying unnecessary model data when filtering transactions (master...2018-03-transaction-filter-avoid-querying) https://github.com/bitcoin/bitcoin/pull/12621 16:51 -!- Chris_Stewart_5 [chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 16:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 16:53 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 264 seconds] 16:54 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #bitcoin-core-dev 16:57 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Ping timeout: 252 seconds] 16:58 < bitcoin-git> [bitcoin] sipa pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/2bac3e484114...7be9a9a570c1 16:58 < bitcoin-git> bitcoin/master 2761bca Pieter Wuille: Merge READWRITEMANY into READWRITE 16:58 < bitcoin-git> bitcoin/master 172f5fa Pieter Wuille: Support deserializing into temporaries... 16:58 < bitcoin-git> bitcoin/master 7be9a9a Pieter Wuille: Merge #12683: Fix more constness violations in serialization code... 16:59 < bitcoin-git> [bitcoin] sipa closed pull request #12683: Fix more constness violations in serialization code (master...201803_moreser) https://github.com/bitcoin/bitcoin/pull/12683 17:00 -!- hirish [~hirish@hirish.cloudns.org] has quit [Ping timeout: 250 seconds] 17:00 -!- hirish [~hirish@hirish.cloudns.org] has joined #bitcoin-core-dev 17:00 < promag> sipa: I was reading that one, are you going to remove the remaining REF usages? 17:00 -!- weez17 [~isaac@unaffiliated/weez17] has joined #bitcoin-core-dev 17:01 < sipa> promag: i'm going to remove all casts from the serialization code, see #10785 17:01 < gribble> https://github.com/bitcoin/bitcoin/issues/10785 | Serialization improvements by sipa · Pull Request #10785 · bitcoin/bitcoin · GitHub 17:02 -!- harrymm [~harrymm@104.207.83.40] has quit [Ping timeout: 246 seconds] 17:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 17:05 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 17:15 -!- harrymm [~harrymm@104.207.83.40] has joined #bitcoin-core-dev 17:16 < kallewoof> I'm a little confused by luke-jr's comment on {sign/verify}message replacement thread. He is saying not specific UTXO's but prove that funds are available. How would you do that, if you didn't sign for specific UTXO's? 17:17 < kallewoof> Basically, he wants to be able to prove that funds are available using a signature, since that's often what people do with signmessage today. 17:21 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 17:29 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 17:29 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 17:30 -!- YellowSphere [~YellowSph@31.204.108.190] has joined #bitcoin-core-dev 17:30 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Max SendQ exceeded] 17:30 -!- YellowSphere [~YellowSph@31.204.108.190] has quit [Client Quit] 17:31 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 17:31 -!- YellowSphere [~YellowSph@31.204.108.190] has joined #bitcoin-core-dev 17:32 -!- YellowSphere [~YellowSph@31.204.108.190] has quit [Client Quit] 17:34 -!- YellowSphere [~YellowSph@31.204.108.190] has joined #bitcoin-core-dev 17:37 -!- rootreddragon [~rootreddr@5.164.217.165] has joined #bitcoin-core-dev 17:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 17:41 -!- vicenteH` [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 260 seconds] 17:43 -!- YellowSphere [~YellowSph@31.204.108.190] has quit [Quit: Leaving] 17:51 < bitcoin-git> [bitcoin] kallewoof opened pull request #12701: [wallet] importprivkey: explicit rescan for known key (master...importprivkey-explicit-rescan) https://github.com/bitcoin/bitcoin/pull/12701 17:52 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 246 seconds] 17:54 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 17:56 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 17:57 -!- Murch [~murch@96.74.120.81] has quit [Quit: Snoozing.] 17:59 < bitcoin-git> [bitcoin] kallewoof opened pull request #12702: [wallet] [rpc] [doc] importprivkey: hint about importmulti (master...importprivkey-importmulti-hint) https://github.com/bitcoin/bitcoin/pull/12702 17:59 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 18:01 < bitcoin-git> [bitcoin] kallewoof closed pull request #12701: [wallet] importprivkey: explicit rescan for known key (master...importprivkey-explicit-rescan) https://github.com/bitcoin/bitcoin/pull/12701 18:02 < promag> kallewoof: IMO all RPC that are a subset of importmulti should be deprecated 18:02 < sipa> well not right now 18:02 < sipa> importmulti can't deal with P2SH-P2WPKH addresses yet 18:03 * sipa adds to TODO list 18:03 < promag> sipa maybe never (so it doesn't break anything) 18:03 < sipa> ? 18:04 < promag> I mean, existing software would have to change if we deprecated those calls 18:04 < sipa> deprecating doesn't mean removing 18:04 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 18:04 < promag> sipa: means it will be removed 18:04 < promag> no? 18:04 < promag> eventually.. :P 18:04 < sipa> yes, at some point in the future 18:04 < sipa> exactly 18:04 < sipa> we're deprecating and removing things all the time 18:05 -!- pyericz [~pyericz@117.30.146.190] has joined #bitcoin-core-dev 18:05 < promag> anyway, IMO the note should be "use importmulti instead, even for 1 entry" 18:06 < kallewoof> promag: I'm fine with that, but sipa noted that there are cases where you cannot use importmulti. 18:06 -!- tecneecs [~tecneecs@ool-44c1c00f.dyn.optonline.net] has joined #bitcoin-core-dev 18:06 < sipa> well we should fix that :) 18:06 < kallewoof> promag: So I'm keeping it as is. To be updated once P2SH-P2WPKH support is added to importmulti. 18:07 < kallewoof> sipa: Yeah that would be ideal, I suppose 18:07 < promag> is there a plan for that sipa? 18:08 < sipa> I hereby instate such a plan. 18:08 < sipa> (it's listed as a future TODO in #11403 18:08 < gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub 18:14 < kallewoof> Weird that the importmulti says `"rescan": (boolean, optional, default: true)`. Sending mixed signals there lol... 18:15 < sipa> lol 18:15 < sipa> that should be fixed 18:15 < kallewoof> Yeah, it's no biggie, but it had me scratching my head for a sec. 18:17 < kallewoof> Also feels like "scriptPubKey": "