--- Log opened Fri Nov 30 00:00:38 2018 00:02 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Snoozing.] 00:05 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev 00:10 -!- chenpo [~chenpo@125-227-16-37.HINET-IP.hinet.net] has quit [Remote host closed the connection] 00:11 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:11 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has quit [Remote host closed the connection] 00:17 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:23 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has quit [Remote host closed the connection] 00:24 -!- chenpo [~chenpo@125-227-16-37.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:26 -!- chenpo [~chenpo@125-227-16-37.HINET-IP.hinet.net] has quit [Read error: Connection reset by peer] 00:27 -!- chenpo [~chenpo@125-227-20-139.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:33 -!- chenpo [~chenpo@125-227-20-139.HINET-IP.hinet.net] has quit [Remote host closed the connection] 00:33 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:33 -!- hebasto_ [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 00:37 -!- Goldman6021 [~Goldman60@82.178.161.137] has joined #bitcoin-core-dev 00:37 < kallewoof> phantomcircuit: maybe a test in configure.ac around line 1101 for EVENT_SET_MEM_FUNCTIONS_IMPLEMENTED and then use the results of that in Makefile.am to conditionally add raii test cpp file. 00:37 -!- Goldman6021 [~Goldman60@82.178.161.137] has quit [Remote host closed the connection] 00:38 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has quit [Ping timeout: 268 seconds] 00:42 -!- indistylo [~indistylo@49.204.67.58] has quit [Ping timeout: 246 seconds] 00:52 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:54 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has quit [Remote host closed the connection] 00:55 -!- chenpo [~chenpo@59-124-157-80.HINET-IP.hinet.net] has joined #bitcoin-core-dev 00:59 -!- chenpo [~chenpo@59-124-157-80.HINET-IP.hinet.net] has quit [Ping timeout: 246 seconds] 01:14 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has joined #bitcoin-core-dev 01:15 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has quit [Remote host closed the connection] 01:15 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has joined #bitcoin-core-dev 01:17 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has quit [Read error: Connection reset by peer] 01:18 -!- chenpo [~chenpo@220-128-240-242.HINET-IP.hinet.net] has joined #bitcoin-core-dev 01:18 < e4xit> ~ 01:18 < e4xit> \] 01:18 < e4xit> ' 01:19 < sipa> it's not working 01:29 -!- JackH [~laptop@62.232.170.181] has joined #bitcoin-core-dev 01:35 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has joined #bitcoin-core-dev 01:37 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 01:37 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 01:38 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 01:38 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 01:38 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 01:38 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 02:09 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:15 -!- hashist [~hashist@157.157.113.25] has left #bitcoin-core-dev ["Leaving"] 02:17 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 02:21 < provoostenator> luke-jr: we could keep the more abstract variable name, but just explain in the help that that is what it _currently_ does 02:24 -!- promag [~promag@193.126.224.118] has joined #bitcoin-core-dev 02:36 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 02:39 -!- echeveria [~echeveria@unaffiliated/echeveria] has quit [Quit: quit] 02:43 < fanquake> kallewoof thanks 02:44 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-fhuezsxrgftpjher] has joined #bitcoin-core-dev 02:44 < bitcoin-git> [bitcoin] fanquake closed pull request #14846: Docs: Adds development guidelines about Scripts shebang to developer-notes.md. (master...add_scripts_development_guidelines) https://github.com/bitcoin/bitcoin/pull/14846 02:44 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-fhuezsxrgftpjher] has left #bitcoin-core-dev [] 02:50 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 02:50 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 02:50 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 02:58 -!- indistylo [~indistylo@49.204.67.58] has joined #bitcoin-core-dev 02:58 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-bcahofhuehoavdsv] has joined #bitcoin-core-dev 02:58 < bitcoin-git> [bitcoin] Sjors closed pull request #13937: Track best-possible-headers (TheBlueMatt) (master...2018/08/best-header-tracking) https://github.com/bitcoin/bitcoin/pull/13937 02:58 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-bcahofhuehoavdsv] has left #bitcoin-core-dev [] 03:11 < fanquake> hebasto I rebooted that test, failure looks unrelated 03:11 < hebasto> fanquake: thanks 03:12 < fanquake> hebasto Also, apologies for not getting to some of your PRs, like #13998. I will get to them eventually. 03:12 < gribble> https://github.com/bitcoin/bitcoin/issues/13998 | Scripts and tools: gitian-build.py improvements and corrections by hebasto · Pull Request #13998 · bitcoin/bitcoin · GitHub 03:14 < hebasto> fanquake: thank you. I understand the "reviewer bottleneck" of developing process :) 03:15 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection] 03:15 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 03:15 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 03:15 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 03:27 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 03:30 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection] 03:34 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 03:35 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Remote host closed the connection] 03:35 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 03:38 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 03:39 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 03:40 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qsnttbgizocebqux] has joined #bitcoin-core-dev 03:40 < bitcoin-git> [bitcoin] Sjors closed pull request #13470: WIP [bench] CCoinsView(Cache): measure various scenarios (master...2018/06/bench_db_cache) https://github.com/bitcoin/bitcoin/pull/13470 03:40 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qsnttbgizocebqux] has left #bitcoin-core-dev [] 03:43 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 03:44 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 03:44 < provoostenator> Topic suggestion for tonights wallet discussion: #12833 (I'd love to get that over with) 03:44 < gribble> https://github.com/bitcoin/bitcoin/issues/12833 | [qt] move QSettings to bitcoin_rw.conf where possible by Sjors · Pull Request #12833 · bitcoin/bitcoin · GitHub 03:44 -!- chenpo [~chenpo@220-128-240-242.HINET-IP.hinet.net] has quit [Remote host closed the connection] 03:45 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 03:45 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has joined #bitcoin-core-dev 03:46 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 03:46 < provoostenator> (oops, I meant the upstream #11082) 03:46 < gribble> https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub 03:47 < provoostenator> #13676 is a documentation change, hopefully read for a final blessing? 03:47 < gribble> https://github.com/bitcoin/bitcoin/issues/13676 | Explain that mempool memory is added to -dbcache by Sjors · Pull Request #13676 · bitcoin/bitcoin · GitHub 03:49 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has quit [Ping timeout: 268 seconds] 03:53 -!- Alirezakaj [b97b661d@gateway/web/freenode/ip.185.123.102.29] has joined #bitcoin-core-dev 03:55 -!- Alirezakaj [b97b661d@gateway/web/freenode/ip.185.123.102.29] has quit [Client Quit] 03:58 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 03:59 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 03:59 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 03:59 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:02 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 04:27 < provoostenator> Any thoughts on how to add wallet specific configuration? Right now all bitcoind wallet related configs seem to apply to all wallets. 04:29 < provoostenator> Context: WIP for ##hwi to add a -signer config where an external script / RPC can be found that can sign a transaction. But I think it makes sense for preferences like RBF and spendzeroconfchange too. 04:31 < provoostenator> Another approach could be store these preferences in the wallet instead of passing them to bitcoind, similar to setwalletflag in #13756 04:31 < gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub 04:46 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 04:49 -!- promag [~promag@193.126.224.118] has quit [Remote host closed the connection] 05:00 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 05:03 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:05 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 05:05 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 05:05 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:17 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 05:32 -!- ken2812221_ [~ken281222@1.200.219.124] has quit [Ping timeout: 268 seconds] 05:35 -!- indistylo [~indistylo@49.204.67.58] has quit [Ping timeout: 268 seconds] 05:44 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:45 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 05:45 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 05:45 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-icdnudgedffvmwmn] has joined #bitcoin-core-dev 05:52 < bitcoin-git> [bitcoin] cyounkins-bot opened pull request #14848: Fix broken Gmane URLs (master...fix-gmane-urls) https://github.com/bitcoin/bitcoin/pull/14848 05:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-icdnudgedffvmwmn] has left #bitcoin-core-dev [] 06:04 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/] 06:08 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has joined #bitcoin-core-dev 06:08 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-vtyoniasojeoojim] has joined #bitcoin-core-dev 06:08 < bitcoin-git> [bitcoin] fanquake opened pull request #14849: [wip] depends: qt 5.9.7 (master...qt-5-9-7) https://github.com/bitcoin/bitcoin/pull/14849 06:08 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-vtyoniasojeoojim] has left #bitcoin-core-dev [] 06:11 -!- chenpo [~chenpo@61-216-77-164.HINET-IP.hinet.net] has quit [Remote host closed the connection] 06:14 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has joined #bitcoin-core-dev 06:16 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:17 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 06:17 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 06:17 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:20 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:22 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 06:22 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 06:22 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:22 -!- brianhoffman [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has quit [Ping timeout: 272 seconds] 06:22 -!- brianhoffman_ [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has joined #bitcoin-core-dev 06:26 -!- chenpo [~chenpo@61-216-136-90.HINET-IP.hinet.net] has quit [Remote host closed the connection] 06:26 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #bitcoin-core-dev 06:28 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 06:30 -!- kexkey [~kexkey@173.209.61.62] has joined #bitcoin-core-dev 06:30 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:31 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 06:31 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 06:31 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:33 -!- brianhoffman [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has joined #bitcoin-core-dev 06:37 -!- brianhoffman_ [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has quit [Ping timeout: 268 seconds] 06:37 -!- promag [~promag@83.223.251.86] has joined #bitcoin-core-dev 06:38 < achow101> is there a wallet meeting today? 06:38 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:39 < promag> provoostenator: I guess the most reasonable option is to save in the wallet itself. are there cons? 06:39 < promag> achow101: I think so 06:39 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 06:39 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 06:39 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:40 -!- brianhoffman_ [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has joined #bitcoin-core-dev 06:42 -!- brianhoffman [~brianhoff@pool-71-163-147-195.washdc.fios.verizon.net] has quit [Ping timeout: 250 seconds] 06:42 -!- brianhoffman_ is now known as brianhoffman 06:47 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 06:48 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has joined #bitcoin-core-dev 06:49 < provoostenator> promag: I tend to agree. Can't think of cons, but I haven't look into what it takes to add a new string metadata entry to a wallet. 06:49 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:49 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has quit [Remote host closed the connection] 06:50 < hebasto> promag: agree about wallet options. 06:50 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 06:50 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 06:50 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:56 -!- promag [~promag@83.223.251.86] has quit [Remote host closed the connection] 06:57 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has joined #bitcoin-core-dev 07:12 < jnewbery> provoostenator: I tried to classify wallet options in #13044 and propose a plan for how they should be handled in future. 07:12 < gribble> https://github.com/bitcoin/bitcoin/issues/13044 | [RFC] Long term plan for wallet command-line args · Issue #13044 · bitcoin/bitcoin · GitHub 07:12 < jnewbery> Please comment there if you have any better suggestions 07:12 < provoostenator> jnewbery: awesome, I'll study that 07:14 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 07:15 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 07:15 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 07:15 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 07:20 -!- rex4539 [~rex4539@ppp-2-84-161-2.home.otenet.gr] has quit [Quit: rex4539] 07:30 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has quit [Remote host closed the connection] 07:30 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has joined #bitcoin-core-dev 07:31 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-aghcvjfmvmdaxceh] has joined #bitcoin-core-dev 07:32 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/60b20c869f8d...74254fea1ef0 07:32 < bitcoin-git> bitcoin/master 4aabadb James O'Beirne: tests: have combine_logs default to most recent test dir 07:32 < bitcoin-git> bitcoin/master 74254fe MarcoFalke: Merge #14683: tests: better combine_logs.py behavior... 07:32 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-aghcvjfmvmdaxceh] has left #bitcoin-core-dev [] 07:32 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Quit: Leaving] 07:33 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cnlqubuxiuthkwyk] has joined #bitcoin-core-dev 07:33 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14683: tests: better combine_logs.py behavior (master...2018-11-better-cons-log) https://github.com/bitcoin/bitcoin/pull/14683 07:33 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-cnlqubuxiuthkwyk] has left #bitcoin-core-dev [] 07:35 -!- chenpo [~chenpo@60-250-236-43.HINET-IP.hinet.net] has quit [Ping timeout: 250 seconds] 07:37 -!- nkjack [ad4b0f69@gateway/web/freenode/ip.173.75.15.105] has joined #bitcoin-core-dev 07:37 -!- nkjack [ad4b0f69@gateway/web/freenode/ip.173.75.15.105] has quit [Client Quit] 07:39 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-uyqapxolyatvawfo] has joined #bitcoin-core-dev 07:39 < bitcoin-git> [bitcoin] MarcoFalke pushed 9 new commits to 0.17: https://github.com/bitcoin/bitcoin/compare/9f556622c57d...d8bc0ce1da1c 07:39 < bitcoin-git> bitcoin/0.17 df5131b fanquake: gui: explicitly disable "Dark Mode" appearance on macOS... 07:39 < bitcoin-git> bitcoin/0.17 de5e48a Luke Dashjr: Bugfix: RPC: Add address_type named param for createmultisig... 07:39 < bitcoin-git> bitcoin/0.17 5782fdc Gregory Sanders: Throw error if CPubKey is invalid during PSBT keypath serialization... 07:39 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-uyqapxolyatvawfo] has left #bitcoin-core-dev [] 07:46 -!- JackH [~laptop@62.232.170.181] has quit [Ping timeout: 250 seconds] 07:51 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qryvpqqcdkpofzss] has joined #bitcoin-core-dev 07:51 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/74254fea1ef0...13a7454fbdac 07:51 < bitcoin-git> bitcoin/master b06483c Gregory Sanders: Remove stale comment in CalculateMaximumSignedInputSize 07:51 < bitcoin-git> bitcoin/master 0fb2e69 Gregory Sanders: CreateTransaction: Assume minimum p2sh-p2wpkh spend size for unknown change 07:51 < bitcoin-git> bitcoin/master 13a7454 MarcoFalke: Merge #14380: fix assert crash when specified change output spend size is unknown... 07:51 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-qryvpqqcdkpofzss] has left #bitcoin-core-dev [] 07:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-gjspibdnjzkrrbuc] has joined #bitcoin-core-dev 07:52 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14380: fix assert crash when specified change output spend size is unknown (master...unknown_change_size) https://github.com/bitcoin/bitcoin/pull/14380 07:52 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-gjspibdnjzkrrbuc] has left #bitcoin-core-dev [] 07:52 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 246 seconds] 08:02 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 08:07 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-njrglxjeuogfqwpm] has joined #bitcoin-core-dev 08:07 < bitcoin-git> [bitcoin] instagibbs opened pull request #14851: [backport] fix assert crash when specified change output spend size is unknown (0.17...change_crash_backport) https://github.com/bitcoin/bitcoin/pull/14851 08:07 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-njrglxjeuogfqwpm] has left #bitcoin-core-dev [] 08:08 -!- rex4539 [~rex4539@ppp-2-84-161-2.home.otenet.gr] has joined #bitcoin-core-dev 08:15 -!- chenpo [~chenpo@2001-b011-5c0d-1f89-c832-86dc-12aa-0f2c.dynamic-ip6.hinet.net] has joined #bitcoin-core-dev 08:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jbbkvorxwgrkjbee] has joined #bitcoin-core-dev 08:24 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/13a7454fbdac...81bd349c9c8d 08:24 < bitcoin-git> bitcoin/master c1825b9 John Newbery: [tests] Add wallet_balance.py... 08:24 < bitcoin-git> bitcoin/master 81bd349 MarcoFalke: Merge #14845: [tests] Add wallet_balance.py... 08:24 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jbbkvorxwgrkjbee] has left #bitcoin-core-dev [] 08:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-hdbbrhwfndgyjvrm] has joined #bitcoin-core-dev 08:26 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14845: [tests] Add wallet_balance.py (master...balance_tests) https://github.com/bitcoin/bitcoin/pull/14845 08:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-hdbbrhwfndgyjvrm] has left #bitcoin-core-dev [] 08:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tytkafwsnuyvclkm] has joined #bitcoin-core-dev 08:26 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #14852: 0.17 backport: [tests] Add wallet_balance.py (0.17...Mf1811-walletBalanceTestBackport) https://github.com/bitcoin/bitcoin/pull/14852 08:26 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-tytkafwsnuyvclkm] has left #bitcoin-core-dev [] 08:36 -!- zallarak [~zain@c-71-202-100-255.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 08:43 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #bitcoin-core-dev 08:46 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 08:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-twliffudfzcypxeq] has joined #bitcoin-core-dev 08:50 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #14852: 0.17 backport: [tests] Add wallet_balance.py (0.17...Mf1811-walletBalanceTestBackport) https://github.com/bitcoin/bitcoin/pull/14852 08:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-twliffudfzcypxeq] has left #bitcoin-core-dev [] 08:54 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 250 seconds] 09:08 -!- Tralfaz [~none@104.248.145.220] has quit [Remote host closed the connection] 09:10 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:10 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 09:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 09:14 -!- mr_paz [~mr_paz@31.7.57.246] has joined #bitcoin-core-dev 09:16 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 09:21 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 09:21 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:24 -!- rhavar [uid237883@gateway/web/irccloud.com/x-zsekrrtapmugmrew] has joined #bitcoin-core-dev 09:25 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Client Quit] 09:29 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 09:35 -!- JackH [~laptop@host86-175-127-233.range86-175.btcentralplus.com] has joined #bitcoin-core-dev 09:36 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:37 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 09:40 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 09:41 -!- Bullit [~Bullit01@042-236-158-163.dynamic.caiway.nl] has joined #bitcoin-core-dev 09:42 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 09:42 -!- Bullitje [~Bullit01@156-209-158-163.dynamic.caiway.nl] has quit [Ping timeout: 268 seconds] 09:49 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ylukypitpvmjqvmq] has joined #bitcoin-core-dev 09:49 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/81bd349c9c8d...011c42c5bd17 09:49 < bitcoin-git> bitcoin/master bf2e010 Karl-Johan Alm: uint256: Remove unnecessary crypto/common.h use 09:49 < bitcoin-git> bitcoin/master 011c42c Wladimir J. van der Laan: Merge #13258: uint256: Remove unnecessary crypto/common.h dependency... 09:49 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ylukypitpvmjqvmq] has left #bitcoin-core-dev [] 09:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ysdyjltagfkwcyon] has joined #bitcoin-core-dev 09:50 < bitcoin-git> [bitcoin] laanwj closed pull request #13258: uint256: Remove unnecessary crypto/common.h dependency (master...uint256-no-crypto-alt) https://github.com/bitcoin/bitcoin/pull/13258 09:50 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-ysdyjltagfkwcyon] has left #bitcoin-core-dev [] 09:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 09:53 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 09:53 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 09:53 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 09:56 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 09:56 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 09:56 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 09:56 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 09:57 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 10:11 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:12 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection] 10:13 -!- Tralfaz [~none@104.248.145.220] has quit [Ping timeout: 246 seconds] 10:19 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 10:27 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 10:27 -!- echonaut17 [~echonaut@46.101.192.134] has quit [Remote host closed the connection] 10:27 -!- echonaut [~echonaut@46.101.192.134] has joined #bitcoin-core-dev 10:31 < dongcarl> What qualifies a PR to be high priority for review? 10:31 < sipa> dongcarl: nominating it during the weekly meeting 10:31 < jamesob> If it's blocking continuing progress on something; 1 high-prio PR per contributor. 10:32 < dongcarl> Okay I see 10:32 < dongcarl> Btw no one got around to doing libevent right? I know strateman did poll but no libevent? 10:33 < jamesob> it seems like in practice it's sort of a formalized review beg, though :) 10:33 < dongcarl> “Formalized review beg” lol 10:33 < jamesob> poll() is still in progress - needs testing and review on the finalized code. I think that PR is still in a bit of flux 10:34 < dongcarl> Okay, I might rebase cfields’ libevent PR 10:34 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 10:34 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 10:35 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 10:38 -!- Zenton [~user@unaffiliated/vicenteh] has joined #bitcoin-core-dev 10:38 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 10:43 < luke-jr> [18:33:03] it seems like in practice it's sort of a formalized review beg, though ☺ <-- what else would you expect? 10:43 < sipa> an informed review beg? :p 10:47 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 10:53 -!- marpme [5e865840@gateway/web/freenode/ip.94.134.88.64] has joined #bitcoin-core-dev 10:53 -!- cabrasm [~cabrasm@2a02:120b:2c46:5dc0:1157:e13d:7703:9df5] has joined #bitcoin-core-dev 11:00 < provoostenator> Wallet meeting? 11:01 < sipa> no, we had one last week 11:01 < meshcollider> I don't think we did sipa 11:01 < meshcollider> Last week was Thanksgiving 11:01 < provoostenator> I also thought we did one two weeks ago... 11:01 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 11:01 < sipa> oh! 11:01 < meshcollider> I have a repeating event on my calendar :p 11:02 < sipa> indeed, my mind was clouded by turkey 11:02 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has quit [Read error: Connection reset by peer] 11:02 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 11:02 < provoostenator> http://www.erisian.com.au/bitcoin-core-dev/log-2018-11-16.html#l-376 11:02 < sipa> #startmeeting 11:02 < lightningbot> Meeting started Fri Nov 30 19:02:48 2018 UTC. The chair is sipa. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:02 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 11:02 < sipa> topics? :) 11:03 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 11:03 < provoostenator> Two... 11:04 < provoostenator> Topic suggestion: wallet specific configuration (cc jnewbery, has a ticket) 11:04 < provoostenator> Topic suggestion: rw_config progress 11:04 < sipa> #topic wallet specific configuration 11:04 < meshcollider> #bitcoin-core-dev Wallet Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag provoostenator aj Chris_Stewart_5 dongcarl gwillen jamesob ken281221 ryanofsky gleb 11:04 < promag> dongcarl: I'd say that a PR that improves the project health can be in HP too 11:04 < kanzure> hi. 11:04 < promag> hi 11:05 < provoostenator> https://github.com/bitcoin/bitcoin/issues/13044 11:05 < sipa> #13044 11:05 < gribble> https://github.com/bitcoin/bitcoin/issues/13044 | [RFC] Long term plan for wallet command-line args · Issue #13044 · bitcoin/bitcoin · GitHub 11:05 < sipa> actually i'm a bit busy right now; meshcollider, want to lead the meeting? 11:05 < provoostenator> Is a lit of command-line arguments. It makes sense to me to migrate some of that into wallet settings (as suggested there too) 11:06 < meshcollider> Sure, does it work for me if you are the chair though 11:06 < sipa> #endmeeting 11:06 < lightningbot> Meeting ended Fri Nov 30 19:06:18 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 11:06 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.02.html 11:06 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.02.txt 11:06 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.02.log.html 11:06 < meshcollider> #startmeeting 11:06 < lightningbot> Meeting started Fri Nov 30 19:06:29 2018 UTC. The chair is meshcollider. Information about MeetBot at http://wiki.debian.org/MeetBot. 11:06 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 11:06 < sipa> go ahead :) 11:06 < kanzure> hi. 11:06 < provoostenator> hi 11:06 < promag> hi, again 11:07 < meshcollider> #topic wallet specific configuration 11:08 < provoostenator> (to resume from above) some of these settings are booleans which can be built on top of the flag setter/getter added in #13756 11:08 < gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub 11:09 < provoostenator> Other things are strings, so would require a little more work, a new RPC method similar to setwalletflag (or we rename it). 11:10 < meshcollider> jnewbery's issue is #13044 right 11:10 < gribble> https://github.com/bitcoin/bitcoin/issues/13044 | [RFC] Long term plan for wallet command-line args · Issue #13044 · bitcoin/bitcoin · GitHub 11:10 < gmaxwell> Sometimes things that are booleans eventually get more settings, avoid reuse, case in point, is likely to evolve into a treshold of how much extra you're willing to pay to avoid reuse. 11:11 < provoostenator> Which suggests we should rename setwalletflag to something more generic like setwalletconfig? 11:13 < provoostenator> sipa: does your wallet overhaul ambition include completely changing the way data is stored in it, or can we just add this type of setting data without getting in the way of the descriptor refactor? 11:14 < meshcollider> I believe the plan is just to slowly migrate the actual keys and scripts at the moment, no change to the rest 11:15 < meshcollider> Perhaps this config change should be taken out into its own PR though if it's going to become more independent 11:16 < provoostenator> Or we change it later, but before the next release. 11:16 < promag> could start to add support for per-wallet options (which take the global option value) - which affects RPC and UI - then discuss how to load/store them? 11:16 < provoostenator> Though that's always scary 11:16 < sipa> provoostenator: i have no intention of touching anything but keys/scripts 11:17 < provoostenator> promag: storing the settings in the wallet should be great for GUI development, way less tedious than dealing with gArgs 11:17 < promag> dumb question: do old versions destroy unknown records in wallets? 11:17 < provoostenator> We just need a generic way to store a map of settings. 11:18 < provoostenator> Not sure, but you can always bump the wallet version to prevent that AFAIK. 11:19 < sipa> promag: no 11:19 < provoostenator> How old wallets deal with new payloads is the kind of thing we can test with #12134 (shameless plug). 11:19 < gribble> https://github.com/bitcoin/bitcoin/issues/12134 | Build previous releases and run functional tests by Sjors · Pull Request #12134 · bitcoin/bitcoin · GitHub 11:19 < provoostenator> *old clients 11:21 < provoostenator> I might at some point volunteer to write this generic settings stuff, but feel free to beat me to it. 11:21 < meshcollider> Sounds good 11:21 < meshcollider> Ok next topic then? 11:21 < provoostenator> But I think it's the cleanest way to add information about hardware wallets to specific wallets. 11:21 -!- Tralfaz [~none@104.248.145.220] has quit [Read error: Connection reset by peer] 11:22 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 11:22 < achow101> i think jonasschnelli added a bit field of features supported with the privkey disabled stuff, so we could have the per wallet options already 11:23 < provoostenator> achow101 correct, and 13756 ^ adds avoid_reuse as another flag, but flags can only be boolean. 11:24 < provoostenator> In addition that PR adds getters and setters for these flags. 11:24 < promag> #13756 11:24 < gribble> https://github.com/bitcoin/bitcoin/issues/13756 | wallet: "avoid_reuse" wallet flag for improved privacy by kallewoof · Pull Request #13756 · bitcoin/bitcoin · GitHub 11:25 < provoostenator> (next topic works for me) 11:25 < achow101> related to that, we should make the address type and change type a wallet specific setting 11:25 < achow101> but that doesn't work well as a boolean, so it would need it's own field 11:25 < provoostenator> achow101: indeed, plus this whole list: #13044 11:25 < gribble> https://github.com/bitcoin/bitcoin/issues/13044 | [RFC] Long term plan for wallet command-line args · Issue #13044 · bitcoin/bitcoin · GitHub 11:26 < meshcollider> Yeah John's issue covers that 11:26 < provoostenator> Yes, now you're repeating the entire thing above :-) 11:26 -!- Tralfaz [~none@104.248.145.220] has quit [Remote host closed the connection] 11:26 < achow101> ah, there's an issue tracking this 11:26 < achow101> cool 11:26 < meshcollider> Ok let's move on 11:26 < meshcollider> #topic rw_config progress (provoostenator) 11:26 < provoostenator> #11082 11:26 < gribble> https://github.com/bitcoin/bitcoin/issues/11082 | Add new bitcoin_rw.conf file that is used for settings modified by this software itself by luke-jr · Pull Request #11082 · bitcoin/bitcoin · GitHub 11:27 < provoostenator> This is great. I build some QT stuff on top of it, which makes me reluctant to touch any settings related UI until that's merged. 11:28 < provoostenator> Maybe more people can review it before hopefully a final rebase? 11:30 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 11:30 < provoostenator> In ancient version of this PR luke-jr added a whole bunch of settings from Knots along with this. That was too much at once, but the idea of making it easier to add more settings to the GUI is certainly appealing. 11:30 < promag> provoostenator: probably rebasing first is better? 11:31 < promag> provoostenator: but I'll take a look too 11:31 < provoostenator> Well, he already did that two weeks ago. 11:31 < meshcollider> This isn't wallet specific, but I'll take a look too yep 11:31 < achow101> topic suggestion: external signers api (provoostenator's idea mentioned earlier) 11:32 < provoostenator> True, though I'd say 99% of GUI users are using it as a wallet, and it's blocking wallet stuff. 11:33 < meshcollider> Perhaps we can add it to high priority once Luke's getbalance stuff is gone :) 11:33 < meshcollider> #topic externals signers API 11:33 < provoostenator> I wrote a document to describe what hardware wallet signing RPC calls could look like, what the hardware script should do (mostly achow101's HWI already does), and how that all ties together: https://github.com/Sjors/bitcoin/blob/2018/11/rpc-signer/doc/external-signer.md 11:33 < provoostenator> And when I say "hardware" I mean any program that can sign things. 11:34 < provoostenator> So could also be a remote multisig service that sends you a bunch of text messages with a cool down period. But local hardware is the easiest. 11:34 < achow101> if we were to include hwi now, the commands used would have to have a bunch of flags 11:35 < provoostenator> The way I see it we wouldn't include HWI in Core, at least not yet. The user would be expected to download HWI or alternative on their own. 11:35 < achow101> so some genralized api using descriptors would be useful, especially for having other external signers other than hwi. so someone could write their own program for their hardware device drivers and not have to repliacte all of the same options 11:36 < achow101> the only problem i see is that a descriptor requires knowledge of keys, but you may not have knowledge of keys to begin with to get the descriptor 11:36 < provoostenator> I introduced the concept of a pseudo-descriptor (see "Signer API") to get around that. 11:37 < provoostenator> E.g. wpkh(00000000/84h/1h/0h/0/*) means "gimme all the receive keys" 11:37 < provoostenator> The answer to which would be an actual descriptor, or an array of descriptors if the final derivation is hardened. 11:38 < sipa> why is it not an actual descriptor? 11:38 < sipa> (only half following) 11:38 < provoostenator> The flow is as follows: 11:38 < achow101> sipa: you don't have the keys yet, you are trying to get them 11:38 < provoostenator> Wallet asks driver for a list of devices, and their master fingerprin 11:38 < provoostenator> Wallet asks driver for keys given a master fingerprint and derivation hints 11:39 < sipa> the wallet should just ask the driver for a descriptor for its receive addresses? 11:39 < meshcollider> So basically it is a descriptor with a placeholder key which gets replaced? 11:39 < sipa> why does that need to look like a descriptor 11:39 -!- Tralfaz [~none@104.248.145.220] has quit [Ping timeout: 245 seconds] 11:39 < provoostenator> It also needs to ask for change addresses. 11:39 < provoostenator> What it needs depends on the wallet. 11:39 < meshcollider> Is it just to specify the format? 11:39 < provoostenator> So a descriptor keeps it generic. 11:40 < sipa> i think my question is: should it treat HW devices/drivers that deal with arbitrary key trees, and the wallet decides which keys to use for what 11:40 < sipa> or is it the driver that decides which keys to use for what 11:40 < provoostenator> I was thinking both. 11:40 < sipa> that seems like the worst of both worlds :) 11:40 < provoostenator> By default we ask for a standard BIP44/49/84 path 11:41 < provoostenator> But the driver can tell us, via enumerate (the first thing we call), that the device insists on a different structure. 11:41 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 11:41 < provoostenator> But I agree this needs more thought. 11:41 < sipa> yeah, ok, you can see it as a 'hint' from the wallet "hey this key path would seem nice to me, agree?" 11:41 < provoostenator> We could also, like sipa suggests, just require that the driver tells us what the receive and change trees are. 11:41 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 11:42 < provoostenator> But I prefer the hint option, because for example the user may have already set changetype and receivetype for a reason. 11:42 < provoostenator> Whereas the driver might default to something lame backwards compatible like p2sh wrapped segwit. 11:43 < sipa> that makes sense 11:43 -!- Tralfaz [~none@104.248.145.220] has joined #bitcoin-core-dev 11:43 < provoostenator> Also, I wonder if the concept of "change chain" and "receive chain" is abstract enough to allow for more fancy things. For multisig it should be. 11:44 < provoostenator> We probably need some way for the driver to communicate capabilities. 11:45 -!- marpme [5e865840@gateway/web/freenode/ip.94.134.88.64] has quit [Ping timeout: 256 seconds] 11:45 < provoostenator> Which again could look like descriptors for lack anything else, e.g. to indicate which address types and whether multisig is supported. 11:45 < achow101> add a new command "getfeatures"? 11:46 < provoostenator> achow101: or just spit it out as part of the enumerate command, but yes. 11:49 < meshcollider> Alright, any other topics? 11:50 < provoostenator> sipa asked for volunteers write tests for #14565 11:50 < gribble> https://github.com/bitcoin/bitcoin/issues/14565 | Overhaul importmulti logic by sipa · Pull Request #14565 · bitcoin/bitcoin · GitHub 11:50 < provoostenator> (just repeating that here for the log) 11:51 < provoostenator> There's about a dozen PR's built on top, including my (pre)WIP RPC stuff. 11:52 < meshcollider> Yeah I have one built on that too 11:52 < meshcollider> Maybe I'll write the tests to speed things up 11:52 < meshcollider> Alright I guess that's it then :) 11:52 < meshcollider> #endmeeting 11:52 < lightningbot> Meeting ended Fri Nov 30 19:52:53 2018 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 11:52 < lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.06.html 11:52 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.06.txt 11:52 < lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-11-30-19.06.log.html 11:53 < meshcollider> See you in another 2 weeks 11:56 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 12:00 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev 12:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 240 seconds] 12:00 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Read error: Connection reset by peer] 12:00 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:01 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:02 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 12:02 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 12:02 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:05 -!- schmidty_ [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 12:05 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 272 seconds] 12:05 < provoostenator> Definitately good we have this seperate wallet meeting now, otherwise we would have hijacked the whole regular meeting :-) 12:08 < achow101> would it be possible to change the meeting time? 12:09 < achow101> push it back an hour? 12:09 -!- schmidty_ [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Ping timeout: 246 seconds] 12:10 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 12:10 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 12:10 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:10 < jnewbery> The nice thing about having it at 7pm UTC is that it's the same time as the regular meeting 12:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:13 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 12:13 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Read error: Connection reset by peer] 12:13 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:14 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 12:14 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 12:14 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:15 -!- mr_paz [~mr_paz@31.7.57.246] has quit [Ping timeout: 240 seconds] 12:15 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:16 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:18 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 268 seconds] 12:19 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has joined #bitcoin-core-dev 12:19 -!- schmidty [~schmidty@104-7-216-111.lightspeed.austtx.sbcglobal.net] has quit [Changing host] 12:19 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:20 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:20 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Read error: Connection reset by peer] 12:21 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:21 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 12:21 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 12:21 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:24 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 244 seconds] 12:26 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Ping timeout: 268 seconds] 12:26 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:26 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:27 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 12:27 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 12:27 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:31 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 12:31 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Read error: Connection reset by peer] 12:31 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 12:31 -!- schmidty [~schmidty@unaffiliated/schmidty] has joined #bitcoin-core-dev 12:32 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 12:33 -!- mr_paz [~mr_paz@84.39.112.85] has joined #bitcoin-core-dev 12:35 -!- schmidty [~schmidty@unaffiliated/schmidty] has quit [Client Quit] 13:02 -!- cabrasm [~cabrasm@2a02:120b:2c46:5dc0:1157:e13d:7703:9df5] has quit [Quit: Leaving] 13:05 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 13:05 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 13:07 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 13:10 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-pyoxksewwyflpfxs] has joined #bitcoin-core-dev 13:10 < bitcoin-git> [bitcoin] MarcoFalke pushed 3 new commits to 0.17: https://github.com/bitcoin/bitcoin/compare/252844329f17...924cf794e1f4 13:10 < bitcoin-git> bitcoin/0.17 53dcf2b Gregory Sanders: Remove stale comment in CalculateMaximumSignedInputSize 13:10 < bitcoin-git> bitcoin/0.17 2a5cc40 Gregory Sanders: CreateTransaction: Assume minimum p2sh-p2wpkh spend size for unknown change 13:10 < bitcoin-git> bitcoin/0.17 924cf79 MarcoFalke: Merge #14851: [backport] fix assert crash when specified change output spend size is unknown... 13:10 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-pyoxksewwyflpfxs] has left #bitcoin-core-dev [] 13:13 < meshcollider> MarcoFalke: #11551 is RTM 13:13 < gribble> https://github.com/bitcoin/bitcoin/issues/11551 | Fix unsigned integer wrap-around in GetBlockProofEquivalentTime by practicalswift · Pull Request #11551 · bitcoin/bitcoin · GitHub 13:24 -!- mr_paz [~mr_paz@84.39.112.85] has quit [Ping timeout: 250 seconds] 13:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 13:35 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 13:39 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 13:43 -!- mr_paz [~mr_paz@84.39.112.86] has joined #bitcoin-core-dev 13:54 -!- Guyver2_ [~Guyver@2001:985:f3f:1:cde:5996:40f2:c1db] has joined #bitcoin-core-dev 13:57 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Ping timeout: 264 seconds] 14:13 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #bitcoin-core-dev 14:18 -!- ken2812221 [~ken281222@1.200.199.75] has joined #bitcoin-core-dev 14:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 14:28 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 14:32 -!- mr_paz [~mr_paz@84.39.112.86] has quit [Read error: Connection reset by peer] 14:32 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:32 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 250 seconds] 14:32 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 14:33 -!- ap4lmtree_ [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 14:35 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 14:36 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 246 seconds] 14:36 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 246 seconds] 14:37 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 272 seconds] 14:42 -!- Guyver2_ [~Guyver@2001:985:f3f:1:cde:5996:40f2:c1db] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:45 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Remote host closed the connection] 14:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:51 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 14:58 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection] 15:01 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 15:04 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Remote host closed the connection] 15:05 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #bitcoin-core-dev 15:05 -!- michaels_ [~michaelsd@38.126.31.226] has quit [Remote host closed the connection] 15:05 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has quit [Quit: Ping timeout (120 seconds)] 15:06 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Remote host closed the connection] 15:06 -!- rockhouse [~rockhouse@unaffiliated/rockhouse] has joined #bitcoin-core-dev 15:07 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 15:11 -!- dviola [~diego@unaffiliated/dviola] has joined #bitcoin-core-dev 15:15 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 15:18 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 15:20 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 15:22 -!- ap4lmtree_ [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 272 seconds] 15:23 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 250 seconds] 15:31 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 15:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 15:37 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 15:38 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has joined #bitcoin-core-dev 15:38 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 15:41 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 246 seconds] 15:43 -!- ap4lmtree- [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Ping timeout: 250 seconds] 15:58 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 16:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 256 seconds] 16:52 -!- Tralfaz [~none@104.248.145.220] has quit [Remote host closed the connection] 16:58 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev 17:13 -!- phwalkr [~phwalkr@192.32.61.94.rev.vodafone.pt] has quit [Remote host closed the connection] 17:29 < meshcollider> And so is #14733 17:29 < gribble> https://github.com/bitcoin/bitcoin/issues/14733 | P2P: Make peer timeout configurable, speed up very slow test and ensure correct code path tested. by zallarak · Pull Request #14733 · bitcoin/bitcoin · GitHub 17:30 -!- IGHOR [~quassel@93.178.216.72] has quit [Quit: http://quassel-irc.org ? ??????????? ?????????. ????-??.] 17:35 -!- IGHOR [~quassel@93.178.216.72] has joined #bitcoin-core-dev 17:40 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 17:41 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 17:43 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 17:57 -!- aba102 [4b6505f7@gateway/web/freenode/ip.75.101.5.247] has joined #bitcoin-core-dev 17:57 -!- promag [~promag@bl22-246-44.dsl.telepac.pt] has quit [Remote host closed the connection] 18:00 -!- aba102 [4b6505f7@gateway/web/freenode/ip.75.101.5.247] has quit [Client Quit] 18:03 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 18:04 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 18:09 -!- dviola [~diego@unaffiliated/dviola] has quit [Quit: WeeChat 2.3] 18:10 -!- harrymm [~harrymm@69.161.195.103] has quit [Ping timeout: 250 seconds] 18:27 -!- _cryptodesktop_i [~John@91.245.77.21] has joined #bitcoin-core-dev 18:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 18:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 18:48 -!- harrymm [~harrymm@69.161.195.103] has joined #bitcoin-core-dev 18:49 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…] 19:01 -!- _cryptodesktop_i [~John@91.245.77.21] has quit [Ping timeout: 250 seconds] 19:06 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 19:07 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 19:07 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 19:07 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 19:14 -!- rhavar [uid237883@gateway/web/irccloud.com/x-zsekrrtapmugmrew] has quit [Quit: Connection closed for inactivity] 19:14 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 19:15 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 19:20 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 19:21 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 19:21 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 19:21 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 19:24 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 19:25 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 19:25 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 19:25 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 19:26 -!- zallarak [~zain@c-71-202-100-255.hsd1.ca.comcast.net] has quit [Ping timeout: 245 seconds] 19:31 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.] 19:53 -!- zallarak [~zain@c-71-202-100-255.hsd1.ca.comcast.net] has joined #bitcoin-core-dev 20:02 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 20:03 -!- rhavar [uid237883@gateway/web/irccloud.com/x-afldeaustetraitk] has joined #bitcoin-core-dev 20:03 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 20:17 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 20:17 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 20:18 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-kjjxfuhwilvrfeco] has joined #bitcoin-core-dev 20:18 < bitcoin-git> [bitcoin] fanquake opened pull request #14853: depends: latest rapidcheck, enable property based tests on Travis (master...latest-rapidcheck) https://github.com/bitcoin/bitcoin/pull/14853 20:18 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-kjjxfuhwilvrfeco] has left #bitcoin-core-dev [] 20:18 < fanquake> Chris_Stewart_5 hopefully 14853 unblocks your progress in 14430 20:57 -!- wxss [~user@77.243.177.40] has quit [Ping timeout: 240 seconds] 20:57 -!- wxss_ [~user@77.243.177.40] has joined #bitcoin-core-dev 21:00 -!- sleepyblooshy12 [~sleepyblo@175.199.20.217] has joined #bitcoin-core-dev 21:00 < fanquake> Apparently travis can't open .zip files.. ? 21:00 -!- sleepyblooshy12 [~sleepyblo@175.199.20.217] has quit [Remote host closed the connection] 21:08 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has quit [Read error: Connection reset by peer] 21:09 -!- Evel-Knievel [~Evel-Knie@d5152f744.static.telenet.be] has joined #bitcoin-core-dev 21:18 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 21:19 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 21:21 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 21:22 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 21:22 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 21:25 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 21:25 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 21:25 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 21:27 < gmaxwell> sipa: mind giving #14841 a review? 21:27 < gribble> https://github.com/bitcoin/bitcoin/issues/14841 | consensus: Move CheckBlock() call to critical section by hebasto · Pull Request #14841 · bitcoin/bitcoin · GitHub 21:28 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 21:29 -!- shesek [~shesek@5.22.134.170] has joined #bitcoin-core-dev 21:29 -!- shesek [~shesek@5.22.134.170] has quit [Changing host] 21:29 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 21:38 -!- zallarak [~zain@c-71-202-100-255.hsd1.ca.comcast.net] has quit [Quit: leaving] 23:30 < NicolasDorier> gmaxwell, sipa, aj, we talked before yestersday about the "least worst" way to have UTXO Set snapshot and how it would be cool if, as part of the core release, a utxo snapshot hash could be included which contributors can sign against. 23:30 < NicolasDorier> I understand that this can be tricky to do it at core level, so I did it on BTCPay own repos, with proper documentation on this link: https://github.com/btcpayserver/btcpayserver-docker/tree/master/contrib/FastSync 23:30 < NicolasDorier> I tried to explain the downsides and documented the process about how people can verify those UTXO Set by themselves if they have another trusted node somewhere else. 23:30 < NicolasDorier> I also documented how to sign against it. 23:30 < NicolasDorier> I know how much you dislike the idea, but this still solve a problem and can be used responsibly. Please, if you have time, review this doc and let me know if I need to add additional warning or documentation. (or if you feel like to add your signature! :)) 23:43 -!- hgfjkgh [67630f4f@gateway/web/freenode/ip.103.99.15.79] has joined #bitcoin-core-dev 23:44 < hgfjkgh> hello how are you --- Log closed Sat Dec 01 00:00:38 2018