--- Day changed Thu Jun 14 2018 00:05 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds] 00:05 -!- jamesob [~james@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev 00:18 < GitHub85> [bitcoin-detached-sigs] jonasschnelli opened pull request #8: 0.16.1: osx signatures for 0.16.1 (0.16...0.16) https://github.com/bitcoin-core/bitcoin-detached-sigs/pull/8 00:50 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Ping timeout: 264 seconds] 00:50 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #bitcoin-core-dev 01:02 -!- ula [~ula@b2b-78-94-9-226.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/] 01:07 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 01:08 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 01:19 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has quit [Ping timeout: 240 seconds] 01:21 -!- davec [~davec@cpe-24-243-249-218.hot.res.rr.com] has joined #bitcoin-core-dev 01:24 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #bitcoin-core-dev 01:26 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:29 -!- vicenteH [~user@97.red-83-50-45.dynamicip.rima-tde.net] has joined #bitcoin-core-dev 01:39 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 01:45 -!- jhfrontz [~Adium@c-73-23-68-28.hsd1.fl.comcast.net] has quit [Ping timeout: 276 seconds] 01:45 -!- jhfrontz [~Adium@c-73-23-68-28.hsd1.fl.comcast.net] has joined #bitcoin-core-dev 02:03 < bitcoin-git> [bitcoin] Empact closed pull request #13239: [moveonly] Fix CConnman template methods to be fully-defined in net.h (master...net-template-methods) https://github.com/bitcoin/bitcoin/pull/13239 02:13 -!- satwo [~textual@2602:306:378a:6fb0:914f:5dfe:f468:8d5d] has quit [Ping timeout: 245 seconds] 02:14 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 245 seconds] 02:22 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 02:24 -!- gagarine [~gagarine@129.194.245.222] has joined #bitcoin-core-dev 02:27 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 268 seconds] 02:29 < jonasschnelli> sipa: you may want to review the Bech32X python ref impl. https://github.com/jonasschnelli/Bech32X/blob/master/ref/python/bech32x.py 02:29 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 02:29 < jonasschnelli> It's still WIP, I added the HRP handling 02:30 < jonasschnelli> Not sure if it should have decode and correct or only correct 02:30 < promag> jonasschnelli: can you explain how is the progress calculated in FindScriptPubKey* 02:31 < promag> I don't understand lines 42-43 02:33 < jonasschnelli> promag: let me check... 02:34 < jonasschnelli> promag: hases are stored ordered, ... so we calculate the progress from the hash in relation to 0xFFFF IIRC 02:34 < jonasschnelli> Not to 0xFFFF but similar 02:35 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 02:36 -!- gagarine [~gagarine@129.194.245.222] has quit [Remote host closed the connection] 02:45 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 02:47 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 02:53 < promag> jonasschnelli: I think I get it, still it's an approximation right? 02:53 < promag> I mean, it's not linear 02:54 < jonasschnelli> yes. its approx 02:59 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has quit [Ping timeout: 260 seconds] 03:11 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev 03:14 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 276 seconds] 03:26 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:27 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 03:38 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 03:40 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 03:46 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 248 seconds] 03:56 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 265 seconds] 03:58 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 04:00 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 04:01 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 04:05 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 04:15 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 264 seconds] 04:19 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 04:20 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-gytkefztlgshihgz] has quit [Quit: Connection closed for inactivity] 04:23 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:24 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 04:29 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 04:34 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 255 seconds] 04:36 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 04:45 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 265 seconds] 04:48 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 04:49 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 04:52 -!- m8tion [~Agence@abo-134-110-68.mrs.modulonet.fr] has joined #bitcoin-core-dev 04:52 -!- SpYoGsee [4dde683d@gateway/web/freenode/ip.77.222.104.61] has quit [Ping timeout: 260 seconds] 05:10 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 05:14 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 248 seconds] 05:15 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 05:19 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 05:35 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 05:39 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 245 seconds] 05:55 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 06:00 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds] 06:02 -!- Miya [46712ef6@gateway/web/freenode/ip.70.113.46.246] has joined #bitcoin-core-dev 06:09 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 06:11 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 06:13 < ken2812221> wumpus: Can I add #13426 to High priority for review? The meeting time is 3 am for me. 06:13 < gribble> https://github.com/bitcoin/bitcoin/issues/13426 | [bugfix] Add u8path and u8string to fix #13103 by ken2812221 · Pull Request #13426 · bitcoin/bitcoin · GitHub 06:13 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 256 seconds] 06:16 -!- Miya [46712ef6@gateway/web/freenode/ip.70.113.46.246] has quit [Ping timeout: 260 seconds] 06:16 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 06:26 -!- Kvaciral [~Kvaciral@5ED6B9A2.cm-7-7c.dynamic.ziggo.nl] has joined #bitcoin-core-dev 06:47 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 06:47 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 06:52 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 276 seconds] 06:52 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 06:58 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 268 seconds] 06:59 < instagibbs> was there ever any resolution to the release notes conflict-a-thon 07:00 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 07:04 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 245 seconds] 07:12 < ken2812221> instagibbs: You can create release-notes-prXXXXX.md to avoid it. Also see #12819 07:12 < gribble> https://github.com/bitcoin/bitcoin/issues/12819 | Avoid release-notes.md conflicts · Issue #12819 · bitcoin/bitcoin · GitHub 07:27 < bitcoin-git> [bitcoin] Sjors opened pull request #13470: WIP [bench] CCoinsView(Cache): measure various scenarios (master...2018/06/bench_db_cache) https://github.com/bitcoin/bitcoin/pull/13470 07:35 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 07:40 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 07:47 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 07:51 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 08:02 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:06 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 08:11 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 08:12 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 256 seconds] 08:12 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:12 < bitcoin-git> [bitcoin] Sjors closed pull request #12404: Prune more aggressively during IBD (master...2018/02/ibd_prune_extra) https://github.com/bitcoin/bitcoin/pull/12404 08:17 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 08:20 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 08:20 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:21 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 245 seconds] 08:30 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 08:32 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 245 seconds] 08:32 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:33 -!- JRob [171fe329@gateway/web/freenode/ip.23.31.227.41] has quit [Quit: Page closed] 08:39 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 08:40 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 08:41 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 08:43 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:43 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 08:45 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 08:47 -!- ExtraCrispy [~ExtraCris@185.9.18.150] has quit [Remote host closed the connection] 08:48 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 08:50 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 08:50 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 256 seconds] 08:51 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 08:51 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 08:51 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 08:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 264 seconds] 08:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:59 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 09:00 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 09:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 09:00 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 09:03 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds] 09:05 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 09:05 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 09:10 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 09:15 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 09:16 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 09:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 09:18 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 09:22 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 248 seconds] 09:23 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 09:28 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 09:32 -!- promag [~promag@83.223.234.95] has joined #bitcoin-core-dev 09:33 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 260 seconds] 09:34 -!- timothy [~tredaelli@redhat/timothy] has quit [Read error: Connection reset by peer] 09:41 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 09:41 -!- grafcaps [~haroldbr@107.147.175.194] has joined #bitcoin-core-dev 09:51 -!- grafcaps [~haroldbr@107.147.175.194] has quit [Ping timeout: 264 seconds] 09:54 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 09:59 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 264 seconds] 10:03 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 10:05 -!- grafcaps [~haroldbr@104.137.194.255] has joined #bitcoin-core-dev 10:06 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 10:07 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 10:09 < promag> do we lock files? 10:09 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 264 seconds] 10:10 < sipa> we lock a lockfile 10:13 -!- grafcaps [~haroldbr@104.137.194.255] has joined #bitcoin-core-dev 10:14 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 10:14 < promag> is that what luke-jr means in https://github.com/bitcoin/bitcoin/pull/12842#issuecomment-396686016? 10:18 -!- m8tion [~Agence@abo-134-110-68.mrs.modulonet.fr] has quit [Read error: Connection reset by peer] 10:18 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 256 seconds] 10:19 < sipa> perhaps 10:19 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 10:24 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 260 seconds] 10:29 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 10:32 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 10:32 -!- promag [~promag@83.223.234.95] has quit [Remote host closed the connection] 10:33 -!- vicenteH [~user@97.red-83-50-45.dynamicip.rima-tde.net] has quit [Ping timeout: 260 seconds] 10:34 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 248 seconds] 10:37 < jnewbery> promag: what is https://github.com/bitcoin/bitcoin/pull/13111/files#diff-2e3836af182cfb375329c3463ffd91f8R370 suppposed to be doing? It's invoking a method called "unload" which I can't find 10:39 -!- laurentmt [~Thunderbi@185.94.189.190] has joined #bitcoin-core-dev 10:40 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4a7e64fc8546...cc7cbd756acd 10:40 < bitcoin-git> bitcoin/master 86edf4a Gregory Sanders: expose CBlockIndex::nTx in getblock(header) 10:40 < bitcoin-git> bitcoin/master cc7cbd7 Wladimir J. van der Laan: Merge #13451: rpc: expose CBlockIndex::nTx in getblock(header)... 10:40 -!- razamobin [~razamobin@64.13.143.107] has joined #bitcoin-core-dev 10:40 -!- IGHOR [~ighor@194.71.5.8] has joined #bitcoin-core-dev 10:41 < bitcoin-git> [bitcoin] laanwj closed pull request #13451: rpc: expose CBlockIndex::nTx in getblock(header) (master...expose_nTx) https://github.com/bitcoin/bitcoin/pull/13451 10:41 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 10:45 < bitcoin-git> [bitcoin] sipa opened pull request #13471: For AVX2 code, also check for AVX, XSAVE, and OS support (master...201806_avxossupport) https://github.com/bitcoin/bitcoin/pull/13471 10:46 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 10:52 < kanzure> wom 3 10:52 < kanzure> error. hm. 10:56 -!- IGHOR [~ighor@194.71.5.8] has quit [] 10:57 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 11:02 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 265 seconds] 11:13 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 11:17 -!- GoldenBear [~gb@104.223.31.252] has quit [Quit: ZNC 1.6.3+deb1 - http://znc.in] 11:18 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 268 seconds] 11:18 -!- goatpig [56f75200@gateway/web/freenode/ip.86.247.82.0] has joined #bitcoin-core-dev 11:20 < jonasschnelli> sipa: The polynominal operation in Bech32X requires 256bit bitwise AND operation, right? 11:20 -!- GoldenBear [~gb@104.223.31.252] has joined #bitcoin-core-dev 11:20 < sipa> jonasschnelli: 135 bit XOR 11:20 < jonasschnelli> okay.. I see 11:21 < sipa> on languages that don't support big integers, split it up in 3 64-bit integers 11:21 < jonasschnelli> Yes. Will do 11:21 < sipa> what language? 11:22 < jonasschnelli> sipa: the python impl. is "done" (draft) https://github.com/jonasschnelli/Bech32X/blob/master/ref/python/bech32x.py ... now working on C 11:22 < jonasschnelli> sipa: I guess it makes sense to have a straight decode() _and_ a correct() in case decode fails? 11:23 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 11:23 < sipa> jonasschnelli: the correction code is less efficient in realizing there are no errors 11:24 < jonasschnelli> okay 11:24 < sipa> it could have a short circuit check if all syndromes are 0, and in that case just straight decode 11:24 < sipa> (the syn variable, after the "for v" loop) 11:25 < jonasschnelli> Okay. That makes sense... 11:25 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:25 < bitcoin-git> [bitcoin] kristapsk closed pull request #13464: RPC: Allow to specify rescan start timestamp for importaddress, importprivkey and importpubkey (master...rescan-from) https://github.com/bitcoin/bitcoin/pull/13464 11:25 < sipa> no need to invoke solver etc in that case 11:26 < jonasschnelli> Also, what made me think a bit: dropping a char will not be detected which seems like a likely (error) case 11:26 < jonasschnelli> s/detected/corrected 11:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 11:27 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 11:27 < sipa> huh 11:28 < sipa> that should be detected 11:28 < gmaxwell> sipa: he means a frameshift, and correction, not detection. 11:28 < gmaxwell> i think for these things its useful if the length is explicit and known, so then you can trigger dropped character repair more usefully. 11:29 < jonasschnelli> Yes. Length is known,.. but the correction would need to be different 11:31 < gmaxwell> yes, there isn't a simple algebraic correction for that, but you can insert a dummy at each position and run the normal correction. I think it's sufficient to know it's possible to do that. 11:31 < jonasschnelli> agree 11:32 < sipa> i wonder if ability to detect such errors is something we can optimize the code for 11:32 < gmaxwell> even placing two characters in a 64 character string is only about 2k possibilities. 11:34 < gmaxwell> sipa: I started to write a fancy bech32 hinter with the idea of list decoding out to 3 errors, including searching for patterns of up to a couple drop and inserts, then using that recent data base of password entry error probablities (which include probabilities for dropped, transposed, and inserted characters) and ranking a probablity for each option. 11:34 < jonasschnelli> I'm manly worried about that people will think with "it can correct up to X characters", it does include missing chars 11:34 -!- dariusmaximus [~dario@12.8.180.242] has quit [Ping timeout: 256 seconds] 11:35 < sipa> it's hamming distance, not levenshtein distance :) 11:35 < gmaxwell> well it does correct up to missing characters with unknown positions, assuming a sutiable decoder. 11:36 -!- dariusmaximus [~dario@12.8.180.242] has joined #bitcoin-core-dev 11:36 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 11:36 < sipa> jonasschnelli: oh, something that i haven't mentioned - that bech32x code can correct up to 14 errors if you know their positions 11:36 < sipa> jonasschnelli: which means that if you have explicitly unreadable characters (as opposed to characters that may be wrong), its error correction ability is much stronger 11:37 < sipa> this is called erasure, not correction 11:37 < gmaxwell> by 'correct up to' sipa means "with no more remaining error detection power" 11:37 < sipa> or in general, you can correct with M known erasures and N addition errors in unknown places as long as M+2*N <= 14 11:37 < sipa> that's not implemented in that demo 11:37 < jonasschnelli> I see... 11:37 < sipa> but it's not very hard to do 11:38 < sipa> M+2*N < 15 is why this is called a distance 15 code 11:38 < gmaxwell> sipa: are those figures really all that useful for this application? e.g. if you can't externally tell that the key is correct (by checking against the blockchain) you can't go safely to that bound, and if you can tell via external information, you can go further. 11:39 < sipa> why can't you safely go to that bound? 11:39 < gmaxwell> because you can't tell if the result is right or not. 11:40 -!- belcher [~belcher@unaffiliated/belcher] has joined #bitcoin-core-dev 11:40 < gmaxwell> if you corrupt 15 characters, but think you have corrupted 14, you'll "recover" something but it'll be the wrong one. 11:41 < gmaxwell> Of course, if you can check against the blockchain you're good to go, but in that case in we could go beyond 15 errors. 11:41 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 260 seconds] 11:41 < sipa> right 11:41 < sipa> in practice you always have both, i guess 11:41 < sipa> but the without-the-blockchain inner "loop" is much more efficient 11:47 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 11:49 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 11:54 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 264 seconds] 11:55 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-kcugzpvimvmusnqp] has joined #bitcoin-core-dev 11:57 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:00 < wumpus> meeting time? 12:00 < jonasschnelli> jup 12:00 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 12:00 < wumpus> #startmeeting 12:00 < lightningbot> Meeting started Thu Jun 14 19:00:32 2018 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00 < jonasschnelli> hi 12:00 < sipa> aye 12:00 < 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:00 < meshcollider> hi 12:00 < cfields> hi 12:00 < kanzure> hi. 12:01 < meshcollider> Sorry I haven't been around for the last few weeks, swamped with assignments and exams 12:01 < achow101> hi 12:01 < promag> hi 12:01 -!- Miya [46712ef6@gateway/web/freenode/ip.70.113.46.246] has joined #bitcoin-core-dev 12:01 < wumpus> meshcollider: np! 12:01 < wumpus> topic proposals? 12:02 < wumpus> #topic high priority for review 12:02 < promag> jnewbery: after qt4 is dropped, I'll replace qt connections with the new sintax 12:02 < wumpus> currently on the list: #13425 #13111 #13062 #12196 #12136 12:02 < achow101> topic proposal: srd fallback coin selection 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/13425 | Moving final scriptSig construction from CombineSignatures to ProduceSignature (PSBT signer logic) by achow101 · Pull Request #13425 · bitcoin/bitcoin · GitHub 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/13111 | Add unloadwallet RPC by promag · Pull Request #13111 · bitcoin/bitcoin · GitHub 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/13062 | Make script interpreter independent from storage type CScript by sipa · Pull Request #13062 · bitcoin/bitcoin · GitHub 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/12196 | Add scantxoutset RPC method by jonasschnelli · Pull Request #12196 · bitcoin/bitcoin · GitHub 12:02 < bitcoin-git> [bitcoin] HashUnlimited opened pull request #13472: [devtools translations] catch invalid specifiers (master...HashUnlimited-translate-1) https://github.com/bitcoin/bitcoin/pull/13472 12:02 < gribble> https://github.com/bitcoin/bitcoin/issues/12136 | Implement BIP 174 Partially Signed Bitcoin Transactions serialization and RPCs by achow101 · Pull Request #12136 · bitcoin/bitcoin · GitHub 12:03 < wumpus> unloadwallet from promag seems almost ready for merge 12:03 < achow101> 12136 can be removed for now 12:03 < wumpus> achow101: ok 12:03 < achow101> it depends on 13425 12:03 < wumpus> dropped 12:04 < promag> wumpus: I think so, I have to fix last jnewbery points 12:04 < sipa> #13425 is pretty much all of the PSBT internal changes that are needed, excluding serialization and RPCs 12:04 < wumpus> it was unfair for you to have two entires on the list, anyway 12:04 < gribble> https://github.com/bitcoin/bitcoin/issues/13425 | Moving final scriptSig construction from CombineSignatures to ProduceSignature (PSBT signer logic) by achow101 · Pull Request #13425 · bitcoin/bitcoin · GitHub 12:04 < jnewbery> I think since the last change, unloadwallet no longer removes the unloaded wallet from the dropdown menu 12:04 < wumpus> (just kidding, no idea how it came that way) 12:05 < promag> jnewbery: you are right 12:05 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 12:05 < promag> needs signal unload 12:05 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev 12:05 < wumpus> right 12:05 < jnewbery> yep. Seems to work with that method declaration readded 12:07 < wumpus> should we add anything to the list this week? 12:07 < promag> #13160 12:07 < gribble> https://github.com/bitcoin/bitcoin/issues/13160 | wallet: Unlock spent outputs by promag · Pull Request #13160 · bitcoin/bitcoin · GitHub 12:07 < wumpus> you already have one 12:07 < meshcollider> Lol 12:07 < promag> there was a behaviour change since 0,15 iirc, that fixes it 12:07 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 12:08 < wumpus> promag: but I agree it needs more attention, FWIW 12:09 < promag> it's one line change 12:09 < sipa> the high-priority list is for things that block other work 12:09 < wumpus> yes 12:09 < sipa> not just "this needs attention" 12:09 < wumpus> that's what the meeting is for 12:10 < wumpus> #action look at #13160 12:10 < gribble> https://github.com/bitcoin/bitcoin/issues/13160 | wallet: Unlock spent outputs by promag · Pull Request #13160 · bitcoin/bitcoin · GitHub 12:10 < wumpus> other topics? 12:11 < meshcollider> I just reviewed it fwiw promag 12:11 < wumpus> meshcollider: thanks! 12:11 < achow101> topic proposal: srd fallback coin selection 12:11 < wumpus> #topic srd fallback coin selection (achow101) 12:12 < wumpus> srd = Single Random Draw? 12:12 < achow101> yes 12:12 < wumpus> #13307 12:12 < gribble> https://github.com/bitcoin/bitcoin/issues/13307 | Replace coin selection fallback strategy with Single Random Draw by achow101 · Pull Request #13307 · bitcoin/bitcoin · GitHub 12:12 < achow101> I think we should discuss instagibbs's point here: https://github.com/bitcoin/bitcoin/pull/13307#discussion_r192899180 12:12 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 240 seconds] 12:12 < instagibbs> oh, I said something eh 12:13 < achow101> the basic point is that in the current coin selection, we prefer exact matches over confirmations. However the current implementation of srd fallback is that we prefer confirmations over exact matches 12:13 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 12:13 < instagibbs> altnernating between BnB(Exact match) and then fallback, rather than Bnb of all sorts then fallback 12:14 < sipa> so this is a bit of a question on what our coin selection algorithm should prioritize 12:14 < achow101> yes 12:14 < sipa> confirmed coins, or (immediate) fee 12:14 < instagibbs> and privacy 12:14 -!- dariusmaximus [~dario@12.8.180.242] has quit [Quit: Leaving] 12:14 -!- dariusmaximus [~dario@12.8.180.242] has joined #bitcoin-core-dev 12:14 < instagibbs> imo privacy puts it over the top and we should try really hard to do it 12:14 < instagibbs> but obviously it's not a slam dunk 12:14 < sipa> hmm, unclear how privacy is affect here? 12:15 < instagibbs> change-less outputs mess with coin analysis 12:15 < instagibbs> to a large degree 12:15 < sipa> that's a good point 12:16 < sipa> sdaftuar, morcos: present, opinions? 12:17 < sipa> gmaxwell: ? 12:17 < instagibbs> IIRC we converged on being ok with current behavior, because it breaks the long chains if it works 12:17 < achow101> I also did a simulation (so take it with a grain of salt) that showed that the number of utxos with exact match over confirmations was higher than not 12:17 < instagibbs> was an intentional design decision 12:19 < sipa> what do you mean by "current behaviour"? 12:19 < instagibbs> in master 12:19 < sipa> master or the SRD PR? 12:19 < sipa> ok 12:20 < sipa> there is another question here on what the criteria for SRD merge should be 12:20 < sipa> because it seems it results in somewhat higher average UTXOs per wallet in simulations 12:21 < instagibbs> merge as in code? or? 12:21 < achow101> merge as in merge the pr 12:21 < instagibbs> ah 12:22 < sipa> yes, i'm wondering what our bar for deciding to change tbe logic should be 12:22 < achow101> it doesn't seem to perform as well as the current coin selection in master w.r.t mean number of utxos in the wallet in my simulations 12:22 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 268 seconds] 12:22 < meshcollider> Significantly higher? 12:22 < instagibbs> did you try filtering for using only coins lower than target value? using coins with negative effective value? 12:22 < achow101> from ~20 utxos to ~90 utxos 12:22 < instagibbs> allowing a single negative effective value? 12:23 < instagibbs> Core is an extreme UTXO cop currently. I don't think we're going to be able to match it. 12:23 < achow101> these are the results so far https://gist.github.com/achow101/242470486265d3f21adab08f65b9102c 12:23 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 12:24 < achow101> I have tried filtering for inputs smaller than the target value and doing srd on that. if that fails, srd on all inputs 12:24 < achow101> I have also done that but instead of srd on all inputs on failure, choosing the input that is immediately larger than the target value 12:25 < sipa> also, these numbers are just for a single simulation, right? 12:25 < achow101> yes, those are all for the same scenario 12:25 < sipa> on different workloads differents effects may be preswnt 12:26 < achow101> I'm running simulations for the other scenarios right now, but that will take a while to finish 12:26 < sipa> i guess more to discuss in the PR 12:28 < instagibbs> achow101, you can also test not filtering for -EV 12:28 < instagibbs> to see how big an effect that is 12:29 < achow101> so we could be spending dust? 12:29 < instagibbs> Like we do now yes 12:29 < achow101> hmm.. ok, I can try that too 12:29 < instagibbs> And "allow 1 negative EV output" type logic 12:30 < instagibbs> anyways, more to discuss on PR 12:30 < sipa> EV filtering is probably the biggest reason for increased UTXO 12:33 < MarcoFalke> Sorry for being late, but I'd like to propose #13439 for high priority for review 12:33 < instagibbs> "allow 1" might be nice in that you won't blow up way past what is actually sane, while containing the bloat 12:33 < gribble> https://github.com/bitcoin/bitcoin/issues/13439 | rpc: Avoid "duplicate" return value for invalid submitblock by TheBlueMatt · Pull Request #13439 · bitcoin/bitcoin · GitHub 12:35 < wumpus> MarcoFalke: sure 12:35 < MarcoFalke> thx 12:36 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 265 seconds] 12:36 < wumpus> MarcoFalke: done 12:36 < wumpus> any other topics? 12:39 < sipa> i have 4 PRs open relating to optimized hardware SHA256... should I combine them into 1, or leave like this? 12:39 < wumpus> let me see 12:39 < sipa> #13471 #13386 #13442 #13438 12:39 < gribble> https://github.com/bitcoin/bitcoin/issues/13471 | For AVX2 code, also check for AVX, XSAVE, and OS support by sipa · Pull Request #13471 · bitcoin/bitcoin · GitHub 12:39 < gribble> https://github.com/bitcoin/bitcoin/issues/13386 | SHA256 implementations based on Intel SHA Extensions by sipa · Pull Request #13386 · bitcoin/bitcoin · GitHub 12:39 < gribble> https://github.com/bitcoin/bitcoin/issues/13442 | Convert the 1-way SSE4 SHA256 code from asm to intrinsics by sipa · Pull Request #13442 · bitcoin/bitcoin · GitHub 12:39 < gribble> https://github.com/bitcoin/bitcoin/issues/13438 | Improve coverage of SHA256 SelfTest code by sipa · Pull Request #13438 · bitcoin/bitcoin · GitHub 12:39 < wumpus> it's good for the selftest one to be seperate, I think that one can be merged 12:40 < wumpus> I haven't really looked at the other ones yet in detail yet 12:40 < cfields> sipa: I have a follow-up PR as well to build a lib-for-each-arch 12:40 < sipa> cfields: ah yes 12:40 < sipa> i'll leave things like this 12:40 < cfields> I figured I'd just wait until everything settled for that one, but let me know if you'd prefer something else 12:40 < wumpus> re: 13442, didn't you first say that made things a few % *slower* on 64 bit? 12:41 < sipa> wumpus: i made more changes, it's faster now 12:41 < wumpus> great, no problems with it anymore then 12:41 < sipa> but it's very heavily compiler dependent... rearranging two lines can have 5% effect on speed 12:41 < wumpus> seems preferable in every way then 12:41 < sipa> or making a constant static 12:41 < sipa> how so? 12:42 < wumpus> both more readable and faster 12:42 < sipa> ah yes, but probably less reliably faster 12:42 < sipa> perhaps on clang it's slower 12:42 < cfields> sipa: also worth considering (I read this just yesterday), apparently gcc switched the way that 256bit loads are done, somewhere around gcc6, I believe. 12:42 < sipa> or with particular gcc versions 12:42 < cfields> so, worth considering compiler age as well. 12:42 < wumpus> right 12:43 < wumpus> if it becomes faster with new compilers it's good 12:43 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:43 < wumpus> if slower, not :) 12:43 < cfields> (see gcc's "mavx256-split-unaligned-load" option, which had its default value changed) 12:44 < ryanofsky> cd 12:44 < sipa> wumpus: another benefit is that this lets us compile the exact same code with -mavx, and get a slightly faster version for AVX capable machines 12:44 < cfields> ~$ 12:44 < wumpus> sipa: that's really nice 12:45 < wumpus> sipa: so we compile it twice, the same code? 12:45 < sipa> wumpus: yup 12:45 -!- jtimon [~quassel@40.28.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 12:45 < sipa> cfields is working on build system changes for that 12:45 < wumpus> almost for free 12:45 < sipa> i wonder what percentage of our binary will be SHA256 implementations... 12:46 < wumpus> a very small part 12:46 < cfields> heh 12:46 < wumpus> though I understand the sentiment :) 12:47 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 12:47 < wumpus> as for the source code, a larger part, which reminds me I still need to add ARM 12:47 < wumpus> POWER8 one needs review #13203 12:47 < gribble> https://github.com/bitcoin/bitcoin/issues/13203 | Add POWER8 ASM for 4-way SHA256 by TheBlueMatt · Pull Request #13203 · bitcoin/bitcoin · GitHub 12:48 < sipa> cfields: we should also try with things like -mmovbe, -mbmi1, -mbmi2, ... 12:48 < wumpus> that's really an instruction set I have no clue about 12:48 < sipa> cfields: i think these may not be implied by -mavx / -mavx2 12:48 < sipa> but generally available on the same systems 12:49 < cfields> sipa: yes. IIRC bmi provides some useful things. 12:49 < cfields> yea, rorx 12:49 < cfields> sorry, that's bmi2 12:52 < wumpus> I'm lost 12:52 < sipa> don't worry :) 12:53 < wumpus> :) 12:53 < wumpus> any quick topic? 12:53 < achow101> when 0.16.1 detached sigs? 12:54 < cfields> achow101: soon, building now 12:54 < cfields> jonasschnelli: ^^ ping for other half 12:54 < jonasschnelli> already made 12:54 < jonasschnelli> https://github.com/bitcoin-core/bitcoin-detached-sigs/pull/8 12:54 < wumpus> cfields: jonasschnelli: thanks 12:55 < cfields> jonasschnelli: ah, I missed the pr! You beat me to it :) 12:55 < jonasschnelli> :-) 12:55 < GitHub133> [bitcoin-detached-sigs] laanwj closed pull request #8: 0.16.1: osx signatures for 0.16.1 (0.16...0.16) https://github.com/bitcoin-core/bitcoin-detached-sigs/pull/8 12:57 < luke-jr> hi 12:57 < wumpus> jonasschnelli: you should probably be able to merge your own stuff there 12:57 < jonasschnelli> wumpus: Yes. I did create the PR because I wasn't sure if we did hit the threshold or required non code-signed signatures 12:58 < wumpus> right, good point 12:58 < luke-jr> well, as soon as the signatures exist, someone could potentially use them 12:58 < luke-jr> so if the threshold isn't met, even a PR could be problematic 12:58 < wumpus> 5 signers for every platform so that seems ok 12:59 < cfields> yea, it'd only be an issue if there were 2 competing "correct" gitian outputs 12:59 < wumpus> agree that for a -final relaese it's better to wait for a few more 12:59 < cfields> I think that's happened in the past due to timezones 12:59 < luke-jr> 5 is fine 12:59 < wumpus> cfields: yes, that's worrying 12:59 < luke-jr> IIRC threshold was 3 anyway 13:00 < wumpus> meeting ending in 1 minute 13:00 < wumpus> oh no, now 13:00 < wumpus> #endmeeting 13:00 < lightningbot> Meeting ended Thu Jun 14 20:00:09 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 13:00 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-06-14-19.00.html 13:00 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-06-14-19.00.txt 13:00 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-06-14-19.00.log.html 13:02 < jamesob> maybe not meeting-worthy, but something I've been curious about is whether there are other indexes people'd like to see (now that we have this nice framework for building them) 13:02 < jamesob> I was thinking address-to-related-txns might be nice 13:02 < luke-jr> AFAIK the goal was to move indexes out of Core 13:02 < jamesob> I think in some cases there can be a compelling argument for additional opt-in indexes 13:03 < jonasschnelli> jamesob: I also started an experimental external indexing daemon: https://github.com/jonasschnelli/bitcoincore-indexd 13:03 < wumpus> at least the indexing functionality has been factored to a generic class now 13:03 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds] 13:03 < jamesob> jonasschnelli: cool, I'll take a look 13:04 < jonasschnelli> jamesob: I tried to build an address-to-related-txns,... but figured out its a source for general evil things like "central validation". :) 13:04 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 13:04 < jamesob> hah 13:05 < jonasschnelli> I think using the wallet more for "selective indexing" makes more sense. 13:05 < jonasschnelli> But IMO an address-to-related-txns is probably better kept external... 13:06 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 13:06 < jamesob> it'd be nice to, e.g., back trezor's web interface with your own bitcoind node instead of a bitcore instance and afaik part of that is because bitcore maintains indexes that bitcoind doesn't 13:06 < jonasschnelli> I understand this use case... but indexing everything for this is just silly.. 13:07 < jonasschnelli> You only want to index a certain xpub or range of keys 13:07 < jamesob> yeah, makes sense 13:07 < jonasschnelli> The only use case is probably if you want to recover a backup... 13:08 < jonasschnelli> But even for that, my new scantxoutset PR makes more sense and works also with pruned peers... 13:08 < jonasschnelli> it just can't reproduce the transaction history,... just recover the funds. 13:08 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 13:09 < jonasschnelli> For bitcore / Trezor,... I'm pretty sure one can do the same thing belcher did with stratum (his personal electrum server) 13:09 < jonasschnelli> Create a bitcoin interface where only a defined set of keys (or xpubs) are indexed. 13:09 < jonasschnelli> In the background, you could use a watch-only core wallet for this... 13:09 < jonasschnelli> If you don't need backup-recovery, it would work with pruned peers as well 13:10 < gmaxwell> instagibbs: I don't think it would be hard to beat bitcoin core in terms of tx out cleanup. 13:10 -!- IGHOR_ [~ighor@194.71.5.8] has joined #bitcoin-core-dev 13:11 < gmaxwell> For example, if it agressively spent all outputs to a scriptpubkey when it spent from any, it would likely sweep more txouts than the current code, AND improve privacy. 13:11 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 13:13 -!- IGHOR_ [~ighor@194.71.5.8] has quit [Client Quit] 13:13 < jamesob> jonasschnelli: interesting, thanks 13:14 < instagibbs> gmaxwell, yeah yeah i meant within the constraints of the discussion, but agreed! 13:16 < gmaxwell> instagibbs: my thought on it was that we'd offset more txout prolific behavior with explicit txo consuming behavior. 13:16 < instagibbs> gotcha 13:17 -!- treyzania [~treyzania@troy.tr3y.io] has quit [Quit: ZNC 1.6.6 - http://znc.in] 13:19 < gmaxwell> the two kinds of extra consuming behavior I know of are (1) grouping by scriptpubkey (which helps privacy), (2) spending more small inputs when fees are low. 13:19 -!- treyzania [~treyzania@troy.tr3y.io] has joined #bitcoin-core-dev 13:21 -!- bitconner [~conner@136.24.175.89] has quit [Ping timeout: 248 seconds] 13:28 -!- opdenkamp [~opdenkamp@kodi/staff/dushmaniac] has quit [Quit: ZNC 1.6.5+deb1 - http://znc.in] 13:29 < sipa> gmaxwell: #12257 13:29 < gribble> https://github.com/bitcoin/bitcoin/issues/12257 | [wallet] Use destination groups instead of coins in coin select by kallewoof · Pull Request #12257 · bitcoin/bitcoin · GitHub 13:31 -!- dcousens [~dcousens@110.140.174.10] has quit [Ping timeout: 256 seconds] 13:33 -!- opdenkamp [~opdenkamp@kodi/staff/dushmaniac] has joined #bitcoin-core-dev 13:38 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11604: [net] Remove ForNode/ForEachNode (master...2017-11-no-foreachnode) https://github.com/bitcoin/bitcoin/pull/11604 13:38 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #12138: Track best-possible-headers (master...2017-10-best-header-tracking) https://github.com/bitcoin/bitcoin/pull/12138 13:38 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/cc7cbd756acd...1939536eea7a 13:38 < bitcoin-git> bitcoin/master fa3d39e MarcoFalke: doc: Remove note to install all boost dev packages 13:38 < bitcoin-git> bitcoin/master 1939536 MarcoFalke: Merge #13460: doc: Remove note to install all boost dev packages... 13:38 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #13233: Skip PrecomputedTransactionData hashing for cache hits. (master...2018-05-no-needless-precompute) https://github.com/bitcoin/bitcoin/pull/13233 13:39 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #13460: doc: Remove note to install all boost dev packages (master...Mf1806-docBuildUbuntu) https://github.com/bitcoin/bitcoin/pull/13460 13:39 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11775: Move fee estimator into validationinterface/cscheduler thread (master...2017-09-background-feeest) https://github.com/bitcoin/bitcoin/pull/11775 13:40 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11856: [RFC] I Have a Hammer! (Replace parts of ui_interface with validationinterface) (master...2017-12-remove-cvblockchange) https://github.com/bitcoin/bitcoin/pull/11856 13:40 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #10984: Allow 2 simultaneous (compact-)block downloads (master...2017-08-paralell-block-downloads) https://github.com/bitcoin/bitcoin/pull/10984 13:41 < BlueMatt> phew, now I dont have so many prs to rebase, and none that conflict with each other 13:41 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11913: Avoid cs_main during ReadBlockFromDisk Calls (master...2017-12-no-readblockfromdisk-csmain) https://github.com/bitcoin/bitcoin/pull/11913 13:48 < wumpus> whoa 13:48 < BlueMatt> heh, havent had time to rebase anything in a while :( 13:48 < BlueMatt> maybe I'll get back to them in a few weeks or so 13:49 < promag> \o/ < 270 prs! 13:50 < sipa> MarcoFalke: feature request: in the conflict checker, if one PR is just a prefix of another one's commits, don't call it a conflict 13:54 < sipa> BlueMatt: :( 13:54 < sipa> BlueMatt: oh, some are still open 13:55 < BlueMatt> lol ffs, I was just closing stale crap I'm not gonna have a chance to rebase for a month 13:55 < BlueMatt> or, more likely, longer 13:57 < sipa> okay! 14:00 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:06 < bitcoin-git> [bitcoin] Empact closed pull request #13462: scripted-diff: Simplify common case of CHashWriter and drop SER_GETHASH & SerializeHash (master...serialize-hash-type) https://github.com/bitcoin/bitcoin/pull/13462 14:09 -!- Miya [46712ef6@gateway/web/freenode/ip.70.113.46.246] has quit [Ping timeout: 260 seconds] 14:18 < bitcoin-git> [bitcoin] TheBlueMatt closed pull request #11639: Rewrite the interface between validation and net_processing wrt DoS (master...2017-10-dos-rewrite) https://github.com/bitcoin/bitcoin/pull/11639 14:18 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 14:24 < cfields> gitian builders: v0.16.1 detached sigs are pushed 14:24 < cfields> achow101: ^^ 14:34 < wumpus> thanks 14:36 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has quit [Ping timeout: 248 seconds] 14:39 -!- laurentmt1 [~Thunderbi@185.94.189.190] has joined #bitcoin-core-dev 14:41 -!- laurentmt [~Thunderbi@185.94.189.190] has quit [Ping timeout: 256 seconds] 14:41 -!- laurentmt1 is now known as laurentmt 14:48 < bitcoin-git> [bitcoin] Empact reopened pull request #13462: scripted-diff: Simplify common case of CHashWriter and drop SER_GETHASH & SerializeHash (master...serialize-hash-type) https://github.com/bitcoin/bitcoin/pull/13462 14:49 < bitcoin-git> [bitcoin] Empact closed pull request #13462: scripted-diff: Simplify common case of CHashWriter and drop SER_GETHASH & SerializeHash (master...serialize-hash-type) https://github.com/bitcoin/bitcoin/pull/13462 14:51 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 250 seconds] 14:51 -!- dariusmaximus [~dario@12.8.180.242] has quit [Ping timeout: 264 seconds] 14:55 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-kcugzpvimvmusnqp] has quit [Quit: Connection closed for inactivity] 14:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 14:59 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 15:09 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 15:10 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 15:22 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 15:40 -!- laurentmt [~Thunderbi@185.94.189.190] has quit [Quit: laurentmt] 15:55 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 16:11 -!- zautomata [~zautomata@unaffiliated/zautomata] has quit [Ping timeout: 256 seconds] 16:14 -!- zautomata [~zautomata@41.232.204.111] has joined #bitcoin-core-dev 16:18 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wgmwvlicczwpnohr] has joined #bitcoin-core-dev 16:24 -!- nmnkgl [~nmnkgl@c-73-189-35-88.hsd1.ca.comcast.net] has quit [Remote host closed the connection] 16:32 -!- snickerfritz_ [~snickerfr@184.75.213.134] has joined #bitcoin-core-dev 16:32 -!- snickerfritz [~snickerfr@unaffiliated/snickerfritz] has quit [Ping timeout: 264 seconds] 16:39 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 16:40 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 16:49 -!- zautomata1 [~zautomata@41.232.210.93] has joined #bitcoin-core-dev 16:51 -!- zautomata [~zautomata@41.232.204.111] has quit [Ping timeout: 260 seconds] 16:52 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 260 seconds] 16:53 -!- bitconner [~conner@64-71-8-130.static.wiline.com] has joined #bitcoin-core-dev 17:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 17:20 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 17:21 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 17:46 -!- goatpig [56f75200@gateway/web/freenode/ip.86.247.82.0] has quit [Ping timeout: 260 seconds] 17:50 -!- murrayn [~dafuq@unaffiliated/murrayn] has quit [Ping timeout: 255 seconds] 17:51 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has joined #bitcoin-core-dev 17:51 -!- murrayn [~dafuq@S01061cabc0b054b3.ok.shawcable.net] has quit [Changing host] 17:51 -!- murrayn [~dafuq@unaffiliated/murrayn] has joined #bitcoin-core-dev 18:13 -!- snickerfritz_ [~snickerfr@184.75.213.134] has quit [Quit: Leaving] 18:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev 18:35 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1939536eea7a...2b770080a49f 18:35 < bitcoin-git> bitcoin/master abd2678 Ben Woosley: Drop ParseHashUV in favor of calling ParseHashStr... 18:35 < bitcoin-git> bitcoin/master 2b77008 MarcoFalke: Merge #13422: Drop ParseHashUV in favor of calling ParseHashStr... 18:36 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #13422: Drop ParseHashUV in favor of calling ParseHashStr (master...parse-hash-uv) https://github.com/bitcoin/bitcoin/pull/13422 18:49 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 18:53 -!- Krellan_ [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 18:53 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 18:56 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Ping timeout: 248 seconds] 19:19 -!- Krellan_ [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection] 20:00 -!- bitless [~Mutter@223.71.229.3] has joined #bitcoin-core-dev 20:04 -!- bitless [~Mutter@223.71.229.3] has quit [Client Quit] 20:05 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 20:11 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 20:19 -!- jtimon [~quassel@40.28.134.37.dynamic.jazztel.es] has quit [Ping timeout: 260 seconds] 20:52 -!- bitconner [~conner@64-71-8-130.static.wiline.com] has quit [Ping timeout: 245 seconds] 21:02 -!- kallewoof [~karl@fp96f94c66.tkyc515.ap.nuro.jp] has quit [Quit: WeeChat 1.9.1] 21:06 -!- kallewoof [~karl@240d:1a:759:6000:a7b1:451a:8874:e1ac] has joined #bitcoin-core-dev 21:16 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 21:30 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 21:38 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 21:44 -!- razamobin [~razamobin@64.13.143.107] has quit [Remote host closed the connection] 21:45 -!- bitconner [~conner@136.24.175.89] has joined #bitcoin-core-dev 22:04 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.0] 22:05 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 22:31 < jojeyh> in regards to moving over to libevent, is the goal to replace ALL networking functionality to use libevent? 22:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 22:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 22:49 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 23:27 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 23:44 -!- grafcaps [~haroldbr@50.90.83.229] has joined #bitcoin-core-dev 23:46 -!- Krellan [~Krellan@2601:640:4000:9258:f9e1:c5a2:64e8:6db2] has joined #bitcoin-core-dev 23:49 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 23:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 23:56 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Read error: Connection reset by peer] 23:57 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev