12019-03-01T00:00:58  *** promag_ has joined #bitcoin-core-dev
  22019-03-01T00:05:37  *** promag_ has quit IRC
  32019-03-01T00:06:12  *** ctrlbreak_MAD is now known as ctrlbreak
  42019-03-01T00:08:03  *** ariard has joined #bitcoin-core-dev
  52019-03-01T00:08:07  *** dviola has joined #bitcoin-core-dev
  62019-03-01T00:11:23  *** DeanGuss has quit IRC
  72019-03-01T00:13:59  *** schmidty has joined #bitcoin-core-dev
  82019-03-01T00:18:56  *** schmidty has quit IRC
  92019-03-01T00:21:38  *** harrymm has quit IRC
 102019-03-01T00:24:57  *** schmidty has joined #bitcoin-core-dev
 112019-03-01T00:29:32  *** schmidty has quit IRC
 122019-03-01T00:36:00  *** murrayn has quit IRC
 132019-03-01T00:39:35  *** murrayn has joined #bitcoin-core-dev
 142019-03-01T00:41:56  *** jarthur has quit IRC
 152019-03-01T00:47:32  *** DeanGuss has joined #bitcoin-core-dev
 162019-03-01T01:05:52  *** CubicEarth has quit IRC
 172019-03-01T01:07:40  *** CubicEarth has joined #bitcoin-core-dev
 182019-03-01T01:12:35  *** DeanGuss has quit IRC
 192019-03-01T01:12:38  *** captjakk has quit IRC
 202019-03-01T01:13:09  *** dviola has quit IRC
 212019-03-01T01:13:14  *** captjakk has joined #bitcoin-core-dev
 222019-03-01T01:14:31  *** zhangzf has joined #bitcoin-core-dev
 232019-03-01T01:17:53  *** captjakk has quit IRC
 242019-03-01T01:19:23  *** morcos has quit IRC
 252019-03-01T01:19:40  *** harrymm has joined #bitcoin-core-dev
 262019-03-01T01:23:31  *** promag_ has joined #bitcoin-core-dev
 272019-03-01T01:24:09  *** morcos has joined #bitcoin-core-dev
 282019-03-01T01:24:26  *** jarthur has joined #bitcoin-core-dev
 292019-03-01T01:26:52  *** Jackielove4u has quit IRC
 302019-03-01T01:46:40  *** captjakk has joined #bitcoin-core-dev
 312019-03-01T01:46:55  *** captjakk has joined #bitcoin-core-dev
 322019-03-01T02:00:05  *** captjakk has quit IRC
 332019-03-01T02:05:17  *** captjakk has joined #bitcoin-core-dev
 342019-03-01T02:10:18  *** promag_ has quit IRC
 352019-03-01T02:23:07  *** pinheadmz has quit IRC
 362019-03-01T02:42:15  *** schmidty has joined #bitcoin-core-dev
 372019-03-01T02:47:07  *** schmidty has quit IRC
 382019-03-01T02:52:50  *** Aaronvan_ has quit IRC
 392019-03-01T02:53:56  *** DeanGuss has joined #bitcoin-core-dev
 402019-03-01T02:59:46  *** captjakk has quit IRC
 412019-03-01T03:02:43  *** shesek has quit IRC
 422019-03-01T03:17:26  *** shesek has joined #bitcoin-core-dev
 432019-03-01T03:17:26  *** shesek has joined #bitcoin-core-dev
 442019-03-01T03:56:52  *** justinmoon has joined #bitcoin-core-dev
 452019-03-01T04:01:50  *** hebasto has joined #bitcoin-core-dev
 462019-03-01T04:32:07  *** copumpkin has quit IRC
 472019-03-01T04:43:57  *** schmidty has joined #bitcoin-core-dev
 482019-03-01T04:49:09  *** schmidty has quit IRC
 492019-03-01T05:11:31  *** hebasto has quit IRC
 502019-03-01T05:24:45  *** pinheadmz has joined #bitcoin-core-dev
 512019-03-01T05:28:51  *** calfcamel has joined #bitcoin-core-dev
 522019-03-01T06:00:02  *** pinheadmz has quit IRC
 532019-03-01T06:23:14  *** pinheadmz has joined #bitcoin-core-dev
 542019-03-01T06:35:35  *** arubi has quit IRC
 552019-03-01T06:38:25  *** pinheadmz has quit IRC
 562019-03-01T06:42:55  *** arubi has joined #bitcoin-core-dev
 572019-03-01T06:44:41  *** schmidty has joined #bitcoin-core-dev
 582019-03-01T06:49:22  *** schmidty has quit IRC
 592019-03-01T07:04:05  *** jarthur has quit IRC
 602019-03-01T07:04:58  *** Krusty has joined #bitcoin-core-dev
 612019-03-01T07:08:34  *** Krusty has quit IRC
 622019-03-01T07:23:22  *** owowo has quit IRC
 632019-03-01T07:29:18  *** owowo has joined #bitcoin-core-dev
 642019-03-01T07:40:00  *** promag_ has joined #bitcoin-core-dev
 652019-03-01T07:45:28  *** promag_ has quit IRC
 662019-03-01T08:03:22  *** Cory has quit IRC
 672019-03-01T08:09:31  *** Pasha has joined #bitcoin-core-dev
 682019-03-01T08:12:42  *** Pasha is now known as Cory
 692019-03-01T08:13:59  *** promag_ has joined #bitcoin-core-dev
 702019-03-01T08:25:46  *** owowo has quit IRC
 712019-03-01T08:30:29  *** aqquadro has joined #bitcoin-core-dev
 722019-03-01T08:30:29  *** aqquadro has joined #bitcoin-core-dev
 732019-03-01T08:30:31  *** name has joined #bitcoin-core-dev
 742019-03-01T08:32:55  *** promag_ has quit IRC
 752019-03-01T08:35:35  *** bitcoin-git has joined #bitcoin-core-dev
 762019-03-01T08:35:35  <bitcoin-git> [bitcoin] gwillen opened pull request #15508: Refactor analyzepsbt for use outside RPC code (master...feature-separate-analyzepsbt) https://github.com/bitcoin/bitcoin/pull/15508
 772019-03-01T08:35:39  *** bitcoin-git has left #bitcoin-core-dev
 782019-03-01T08:40:10  *** jungly has joined #bitcoin-core-dev
 792019-03-01T08:42:21  *** justinmoon has quit IRC
 802019-03-01T08:43:47  *** justanotheruser has quit IRC
 812019-03-01T08:45:44  *** schmidty has joined #bitcoin-core-dev
 822019-03-01T08:48:25  *** owowo has joined #bitcoin-core-dev
 832019-03-01T08:50:35  *** schmidty has quit IRC
 842019-03-01T09:09:21  *** timothy has joined #bitcoin-core-dev
 852019-03-01T09:13:59  *** aqquadro has quit IRC
 862019-03-01T09:32:51  *** setpill has joined #bitcoin-core-dev
 872019-03-01T09:41:41  <meshcollider> remember the wallet meeting is tomorrow/today
 882019-03-01T09:47:43  *** spinza has quit IRC
 892019-03-01T09:57:39  *** spinza has joined #bitcoin-core-dev
 902019-03-01T10:01:36  *** spinza has quit IRC
 912019-03-01T10:04:34  *** kexkey has quit IRC
 922019-03-01T10:04:51  *** justanotheruser has joined #bitcoin-core-dev
 932019-03-01T10:14:44  *** spinza has joined #bitcoin-core-dev
 942019-03-01T10:14:47  *** rex4539 has quit IRC
 952019-03-01T10:15:57  *** mmgen has joined #bitcoin-core-dev
 962019-03-01T10:23:47  *** jb55 has quit IRC
 972019-03-01T10:23:47  *** whb has joined #bitcoin-core-dev
 982019-03-01T10:26:08  *** whb has quit IRC
 992019-03-01T10:27:53  *** hyperwang has joined #bitcoin-core-dev
1002019-03-01T10:28:43  <hyperwang> f
1012019-03-01T10:35:27  *** hyperwang has quit IRC
1022019-03-01T10:36:05  *** Jackielove4u has joined #bitcoin-core-dev
1032019-03-01T10:40:09  *** aqquadro has joined #bitcoin-core-dev
1042019-03-01T10:46:41  *** schmidty has joined #bitcoin-core-dev
1052019-03-01T10:51:00  *** jb55 has joined #bitcoin-core-dev
1062019-03-01T10:51:07  *** schmidty has quit IRC
1072019-03-01T10:55:17  *** promag_ has joined #bitcoin-core-dev
1082019-03-01T10:58:13  <provoostenator> meshcollider: awesome
1092019-03-01T10:58:56  *** fanquake has joined #bitcoin-core-dev
1102019-03-01T10:59:27  *** promag_ has quit IRC
1112019-03-01T11:01:21  <fanquake> meshcollider how long until that?
1122019-03-01T11:17:55  <provoostenator> fanquake: 19:00 GMT / Iceland time
1132019-03-01T11:18:38  <provoostenator> I like how this is almost an ad for GMT: https://time.is/nl/GMT
1142019-03-01T11:18:54  <provoostenator> "No daylight saving time, same UTC offset all year"
1152019-03-01T11:23:09  <tryphe> provoostenator, Iceland has darkness saving time =p
1162019-03-01T11:25:29  *** schmidty has joined #bitcoin-core-dev
1172019-03-01T11:25:35  <fanquake> provoostenator right, so same as usual meeting time? 3am
1182019-03-01T11:26:16  <fanquake> I played around with the deterministic builds for HWI today, got stuck with wine and page faults.
1192019-03-01T11:53:34  *** promag_ has joined #bitcoin-core-dev
1202019-03-01T11:55:11  *** Deinogalerix21 has joined #bitcoin-core-dev
1212019-03-01T11:55:45  <jonasschnelli> hmm... "bitcoin-addcon invoked oom-killer"
1222019-03-01T11:56:01  <jonasschnelli> Ran current master on a 4GB ARM with -dbache=2000
1232019-03-01T12:04:43  *** zhangzf has quit IRC
1242019-03-01T12:15:16  *** schmidty has quit IRC
1252019-03-01T12:19:47  *** rex4539 has joined #bitcoin-core-dev
1262019-03-01T12:27:22  *** rex4539 has quit IRC
1272019-03-01T12:30:26  *** StopAndDecrypt has quit IRC
1282019-03-01T12:32:31  *** queip has joined #bitcoin-core-dev
1292019-03-01T12:43:30  *** copumpkin has joined #bitcoin-core-dev
1302019-03-01T12:49:20  <fanquake> promag is 15478 part of, or the fix for 15453 ?
1312019-03-01T13:08:59  *** promag_ has quit IRC
1322019-03-01T13:17:11  *** schmidty has joined #bitcoin-core-dev
1332019-03-01T13:21:44  *** schmidty has quit IRC
1342019-03-01T13:29:35  *** darosior has joined #bitcoin-core-dev
1352019-03-01T13:32:49  *** arubi has quit IRC
1362019-03-01T13:33:09  *** arubi has joined #bitcoin-core-dev
1372019-03-01T13:44:05  <jonasschnelli> What could be the reason why bitcoind uses 3GB of ram (RES) when running with -dbcache=2000?
1382019-03-01T13:44:08  <instagibbs> gwillen, TIL we wrapped boost optional in core :)
1392019-03-01T13:44:22  <jonasschnelli> I'm aware that the maxmempool gets added to the cache during IBD
1402019-03-01T13:45:46  <jonasschnelli> 3GB - 300MB mempool - 2GB dbcache makes still 700MB for core without the mempool...
1412019-03-01T13:47:46  <jonasschnelli> OMG... ignore me. I should sleep more, I set the dbcache to 20GB
1422019-03-01T13:48:16  * jonasschnelli blames the stupid and broken MacBookPro keyboard
1432019-03-01T13:56:10  <provoostenator> Why buy a reliable keyboard if you can buy more RAM?
1442019-03-01T14:01:11  <jonasschnelli> heh
1452019-03-01T14:02:34  *** aqquadro has quit IRC
1462019-03-01T14:04:19  *** schmidty has joined #bitcoin-core-dev
1472019-03-01T14:06:00  *** bitcoin-git has joined #bitcoin-core-dev
1482019-03-01T14:06:00  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/29c24b05fb71...e8612adc5d07
1492019-03-01T14:06:01  <bitcoin-git> bitcoin/master fa852f0 MarcoFalke: test: Bump timeout on tests that timeout on windows
1502019-03-01T14:06:01  <bitcoin-git> bitcoin/master e8612ad MarcoFalke: Merge #15507: test: Bump timeout on tests that timeout on windows
1512019-03-01T14:06:03  *** bitcoin-git has left #bitcoin-core-dev
1522019-03-01T14:06:54  *** bitcoin-git has joined #bitcoin-core-dev
1532019-03-01T14:06:54  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15507: test: Bump timeout on tests that timeout on windows (master...1903-testTimeoutWindows) https://github.com/bitcoin/bitcoin/pull/15507
1542019-03-01T14:07:07  *** bitcoin-git has left #bitcoin-core-dev
1552019-03-01T14:09:11  *** schmidty has quit IRC
1562019-03-01T14:11:15  *** schmidty has joined #bitcoin-core-dev
1572019-03-01T14:14:44  *** bitcoin-git has joined #bitcoin-core-dev
1582019-03-01T14:14:44  <bitcoin-git> [bitcoin] MarcoFalke pushed 6 commits to master: https://github.com/bitcoin/bitcoin/compare/e8612adc5d07...a6d7026a45c9
1592019-03-01T14:14:51  <bitcoin-git> bitcoin/master 7aa6a8a Pieter Wuille: Add ParseRange function to parse args of the form int/[int,int]
1602019-03-01T14:14:51  <bitcoin-git> bitcoin/master 6b9f45e Pieter Wuille: Support ranges arguments in RPC help
1612019-03-01T14:14:51  <bitcoin-git> bitcoin/master 4566011 Pieter Wuille: Add support for stop/[start,stop] ranges to scantxoutset
1622019-03-01T14:14:58  *** bitcoin-git has left #bitcoin-core-dev
1632019-03-01T14:15:30  *** bitcoin-git has joined #bitcoin-core-dev
1642019-03-01T14:15:30  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15497: rpc: Consistent range arguments in scantxoutset/importmulti/deriveaddresses (master...201902_rpcconsistentrange) https://github.com/bitcoin/bitcoin/pull/15497
1652019-03-01T14:15:32  *** bitcoin-git has left #bitcoin-core-dev
1662019-03-01T14:15:51  *** schmidty has quit IRC
1672019-03-01T14:19:46  *** Guyver2 has joined #bitcoin-core-dev
1682019-03-01T14:20:53  *** Zenton has quit IRC
1692019-03-01T14:21:00  *** AaronvanW has joined #bitcoin-core-dev
1702019-03-01T14:24:29  *** bitcoin-git has joined #bitcoin-core-dev
1712019-03-01T14:24:29  <bitcoin-git> [bitcoin] MarcoFalke opened pull request #15509: [rpc] deriveaddresses: add range to CRPCConvertParam (master...1903-rpcDeriveAddress) https://github.com/bitcoin/bitcoin/pull/15509
1722019-03-01T14:24:30  *** bitcoin-git has left #bitcoin-core-dev
1732019-03-01T14:24:59  *** bitcoin-git has joined #bitcoin-core-dev
1742019-03-01T14:25:00  <bitcoin-git> [bitcoin] Sjors opened pull request #15510: [rpc] deriveaddresses: add range to CRPCConvertParam (master...2019/02/rpcconsistentrange) https://github.com/bitcoin/bitcoin/pull/15510
1752019-03-01T14:25:07  *** bitcoin-git has left #bitcoin-core-dev
1762019-03-01T14:25:08  <MarcoFalke> lol
1772019-03-01T14:25:14  *** Zenton has joined #bitcoin-core-dev
1782019-03-01T14:25:24  <provoostenator> Oops
1792019-03-01T14:25:34  *** bitcoin-git has joined #bitcoin-core-dev
1802019-03-01T14:25:35  <bitcoin-git> [bitcoin] MarcoFalke closed pull request #15509: [rpc] deriveaddresses: add range to CRPCConvertParam (master...1903-rpcDeriveAddress) https://github.com/bitcoin/bitcoin/pull/15509
1812019-03-01T14:25:41  *** bitcoin-git has left #bitcoin-core-dev
1822019-03-01T14:26:15  <promag> wat!
1832019-03-01T14:27:45  <instagibbs> awkward
1842019-03-01T14:27:59  <promag> provoostenator: MarcoFalke: well played, you don't fool us X)
1852019-03-01T14:28:59  *** rafalcpp has joined #bitcoin-core-dev
1862019-03-01T14:29:57  <MarcoFalke> eh? My pull was opened earlier! xD
1872019-03-01T14:30:24  <fanquake> race
1882019-03-01T14:30:52  * MarcoFalke fixes race in deriveaddress
1892019-03-01T14:31:26  <promag> MarcoFalke: true! then provoostenator commits fast
1902019-03-01T14:31:34  <MarcoFalke> promag: ERROR: deriveaddresses argument 1 is named range in vRPCConvertParams but ['begin'] in dispatch table
1912019-03-01T14:32:03  <MarcoFalke> I guess named args don't work then
1922019-03-01T14:32:42  <promag> where do you get that?
1932019-03-01T14:33:18  <fanquake> promag https://travis-ci.org/bitcoin/bitcoin/jobs/500366793
1942019-03-01T14:33:44  <promag> fanquake: thanks, just saw it too
1952019-03-01T14:34:30  <fanquake> promag you might have missed my question above^. Is 15478 part of, or the fix for 15453 ?
1962019-03-01T14:34:34  *** schmidty has joined #bitcoin-core-dev
1972019-03-01T14:36:38  <promag> yes the goal of that should fix 15453
1982019-03-01T14:39:57  <fanquake> ok
1992019-03-01T14:40:01  *** whb has joined #bitcoin-core-dev
2002019-03-01T14:40:42  *** whb has left #bitcoin-core-dev
2012019-03-01T14:41:32  *** hyperwang has joined #bitcoin-core-dev
2022019-03-01T14:42:09  *** hyperwang has joined #bitcoin-core-dev
2032019-03-01T14:44:06  *** Deinogalerix21 has quit IRC
2042019-03-01T14:45:14  *** hyperwang has left #bitcoin-core-dev
2052019-03-01T14:49:14  *** bitcoin-git has joined #bitcoin-core-dev
2062019-03-01T14:49:15  <bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/a6d7026a45c9...dc251de6a5c4
2072019-03-01T14:49:15  <bitcoin-git> bitcoin/master aeb7fbf Chun Kuan Lee: appveyor: Don't build debug libraries instead of "build and delete"
2082019-03-01T14:49:15  <bitcoin-git> bitcoin/master dc251de MarcoFalke: Merge #15506: appveyor: fix cache issue and reduce dependencies build time...
2092019-03-01T14:49:22  *** bitcoin-git has left #bitcoin-core-dev
2102019-03-01T14:49:57  *** bitcoin-git has joined #bitcoin-core-dev
2112019-03-01T14:49:57  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15506: appveyor: fix cache issue and reduce dependencies build time (master...appveyor-release-only) https://github.com/bitcoin/bitcoin/pull/15506
2122019-03-01T14:49:59  *** bitcoin-git has left #bitcoin-core-dev
2132019-03-01T14:52:42  *** kabaum has quit IRC
2142019-03-01T15:00:37  *** nullptr| has quit IRC
2152019-03-01T15:02:07  *** nullptr| has joined #bitcoin-core-dev
2162019-03-01T15:03:25  <darosior> Hi, I saw that in init.cpp the service NODE_NETWORK_LIMITED is set with NODE_NETWORK at the begining, but I wonder why it is not reset if we did not pruned the block chain ? (https://github.com/bitcoin/bitcoin/blob/b4fc5257b7dc106ff210d170397d4ce0e024f2c0/src/init.cpp#L1652)
2172019-03-01T15:04:14  <provoostenator> Surprising how many testnet peers are still stuck at the CVE-2018-17144 exploit block. https://bitcoin.stackexchange.com/questions/79662/solving-bitcoin-cores-activatebestchain-failed
2182019-03-01T15:04:38  <gmaxwell> darosior: limited means the node can ALSO serve recent blocks, services are additive.
2192019-03-01T15:05:00  <provoostenator> My node shows lots of "Disconnecting outbound peer 5 for old chain, best known block = 00000000210004840364b52bc5e455d888f164e4264a4fec06a514b67e9d5722"
2202019-03-01T15:05:11  <darosior> gmaxwell : Thank you.
2212019-03-01T15:05:48  <gmaxwell> provoostenator: most testnet nodes are just forgotten old software, this has more or less always been true. :)
2222019-03-01T15:06:17  <darosior> gmaxwell : It is indicated "only" instead of "also" in the comment https://github.com/bitcoin/bitcoin/blob/a6d7026a45c915794338c178b7f95d5c1f8e977f/src/protocol.h#L267
2232019-03-01T15:07:28  <gmaxwell> darosior: you're misunderstanding the comment.
2242019-03-01T15:07:28  <provoostenator> getchaintips shows this particular block as  "headers-only", which I guess is why it doesn't immediately disconnect from nodes with this block?
2252019-03-01T15:07:56  <gmaxwell> darosior: limited = NETWORK-old_blocks    so NETWORK + LIMITED = NETWORK
2262019-03-01T15:09:52  <darosior> gmaxwell : Ok, thank you.
2272019-03-01T15:11:20  <provoostenator> (it took 22 minutes from connecting to disconnecting)
2282019-03-01T15:12:16  <gmaxwell> provoostenator: it won't attempt to fetch it because its clearly a losing chaintip.
2292019-03-01T15:12:53  <gmaxwell> provoostenator: it also wouldn't be good to disconnect immediately because that would prevent the peer getting blocks from you and reorging to your chain (if it could)
2302019-03-01T15:13:43  <provoostenator> Ah ok, so it's altruistic intended behavior then. That also applies even if we did know it was invalid?
2312019-03-01T15:15:40  <gmaxwell> provoostenator: it's incorrect to call that altruistic, as getting the rest of the network on to your chain is very much in your interest... but the getting other people part is mostly accomplished by not doing that kind of strict behavior on inbound.
2322019-03-01T15:16:10  <gmaxwell> if they actually send something invalid, we'll punt right away.
2332019-03-01T15:20:57  *** DougieBot5000_ has joined #bitcoin-core-dev
2342019-03-01T15:23:56  *** DougieBot5000 has quit IRC
2352019-03-01T15:25:12  *** bitcoin-git has joined #bitcoin-core-dev
2362019-03-01T15:25:12  <bitcoin-git> [bitcoin] darosior opened pull request #15511: RPC : More user-friendly services field in getnetworkinfo and getpeerinfo (master...services_for_humans) https://github.com/bitcoin/bitcoin/pull/15511
2372019-03-01T15:25:23  *** bitcoin-git has left #bitcoin-core-dev
2382019-03-01T15:52:30  *** zivl has quit IRC
2392019-03-01T15:52:49  *** captjakk has joined #bitcoin-core-dev
2402019-03-01T15:53:06  <MarcoFalke> I got the "lists.linuxfoundation.org mailing list memberships reminder", so at least it is not all-down
2412019-03-01T15:53:16  *** zivl has joined #bitcoin-core-dev
2422019-03-01T15:57:39  <gmaxwell> lol
2432019-03-01T15:57:55  <gmaxwell> I suspect the list itself works, but it's all moderated and the moderation interface is down...
2442019-03-01T16:08:18  *** hebasto has joined #bitcoin-core-dev
2452019-03-01T16:13:14  *** bitcoin-git has joined #bitcoin-core-dev
2462019-03-01T16:13:14  <bitcoin-git> [bitcoin] jonasschnelli opened pull request #15512: Add ChaCha20 encryption option (XOR) (master...2019/03/chacha) https://github.com/bitcoin/bitcoin/pull/15512
2472019-03-01T16:13:15  *** bitcoin-git has left #bitcoin-core-dev
2482019-03-01T16:17:11  *** darosior has quit IRC
2492019-03-01T16:18:28  *** spinza has quit IRC
2502019-03-01T16:33:38  *** spinza has joined #bitcoin-core-dev
2512019-03-01T16:37:59  *** justinmoon has joined #bitcoin-core-dev
2522019-03-01T16:44:11  *** schmidty has quit IRC
2532019-03-01T16:46:05  *** schmidty has joined #bitcoin-core-dev
2542019-03-01T16:50:39  *** schmidty has quit IRC
2552019-03-01T16:50:44  *** schmidty_ has joined #bitcoin-core-dev
2562019-03-01T16:52:04  *** pinheadmz has joined #bitcoin-core-dev
2572019-03-01T16:56:27  *** jarthur has joined #bitcoin-core-dev
2582019-03-01T17:17:37  *** morcos has quit IRC
2592019-03-01T17:17:53  *** morcos has joined #bitcoin-core-dev
2602019-03-01T17:40:05  *** jungly has quit IRC
2612019-03-01T17:40:29  <gwillen> instagibbs: yeah, I assume we wrap boost::optional so we can replace it with the std one when the time comes
2622019-03-01T17:40:50  <sipa> indeed
2632019-03-01T17:40:57  <instagibbs> roger that
2642019-03-01T17:41:06  *** setpill has quit IRC
2652019-03-01T17:42:03  <sipa> the source code says "
2662019-03-01T17:42:10  <sipa> //! Substitute for C++17 std::optional"
2672019-03-01T17:49:02  <gwillen> although I noticed when I was messing around in psbt.h that PartiallySignedTransaction has a boost::optional in it
2682019-03-01T17:49:07  <gwillen> I left it alone but I'll change it if someone complains
2692019-03-01T18:03:25  *** owowo has quit IRC
2702019-03-01T18:08:21  *** owowo has joined #bitcoin-core-dev
2712019-03-01T18:27:19  *** DeanGuss has quit IRC
2722019-03-01T18:35:28  *** justanotheruser has quit IRC
2732019-03-01T18:43:12  *** justanotheruser has joined #bitcoin-core-dev
2742019-03-01T18:54:33  *** hebasto has quit IRC
2752019-03-01T18:55:57  *** bitcoin-git has joined #bitcoin-core-dev
2762019-03-01T18:55:58  <bitcoin-git> [bitcoin] MarcoFalke pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/dc251de6a5c4...f9dbb319d26f
2772019-03-01T18:55:58  <bitcoin-git> bitcoin/master 2fa85eb Adam Jonas: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo
2782019-03-01T18:55:59  <bitcoin-git> bitcoin/master f13ad1c Adam Jonas: modify test for memory locked in case locking pages failed at some point
2792019-03-01T18:55:59  <bitcoin-git> bitcoin/master f9dbb31 MarcoFalke: Merge #15485: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo
2802019-03-01T18:56:08  *** bitcoin-git has left #bitcoin-core-dev
2812019-03-01T18:56:43  *** bitcoin-git has joined #bitcoin-core-dev
2822019-03-01T18:56:43  <bitcoin-git> [bitcoin] MarcoFalke merged pull request #15485: add rpc_misc.py, mv test getmemoryinfo, add test mallocinfo (master...test_rpc_misc) https://github.com/bitcoin/bitcoin/pull/15485
2832019-03-01T18:56:47  *** bitcoin-git has left #bitcoin-core-dev
2842019-03-01T19:00:39  <meshcollider> wallet meeting time :)
2852019-03-01T19:00:45  <meshcollider> #startmeeting
2862019-03-01T19:00:45  <lightningbot> Meeting started Fri Mar  1 19:00:45 2019 UTC.  The chair is meshcollider. Information about MeetBot at http://wiki.debian.org/MeetBot.
2872019-03-01T19:00:45  <lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
2882019-03-01T19:00:47  <provoostenator> hi
2892019-03-01T19:00:48  <sipa> present
2902019-03-01T19:00:51  <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
2912019-03-01T19:00:58  <instagibbs> hi
2922019-03-01T19:01:17  <meshcollider> Topics for this week?
2932019-03-01T19:01:31  <achow101> Hi
2942019-03-01T19:01:50  <sipa> i guess there isn't anything wallet-related for 0.18
2952019-03-01T19:02:27  <provoostenator> #15453
2962019-03-01T19:02:29  <gribble> https://github.com/bitcoin/bitcoin/issues/15453 | Starting bitcoin-qt with -nowallet and then opening a wallet does not show the wallet · Issue #15453 · bitcoin/bitcoin · GitHub
2972019-03-01T19:02:36  <provoostenator> Is tagged with 0.18 anyway
2982019-03-01T19:03:02  <provoostenator> With a cliff-hanger from promag
2992019-03-01T19:03:23  <meshcollider> That's a Qt issue though right
3002019-03-01T19:03:59  <achow101> It only effects people who self compile
3012019-03-01T19:04:26  <achow101> As the issue is with qt versions
3022019-03-01T19:06:21  <provoostenator> It seems so, in which case it should be OK as long as we backport the fix onto the 0.18 branch.
3032019-03-01T19:07:17  <meshcollider> Mhm
3042019-03-01T19:07:35  <meshcollider> Other than that, yeah, we managed to get all the wallet PRs for 0.18 reviewed and merged pretty efficiently so nice work
3052019-03-01T19:09:11  <provoostenator> Proposed topic: descriptor based wallets
3062019-03-01T19:09:36  <provoostenator> (briefly anyway, since everyone is focussed on 0.18)
3072019-03-01T19:11:30  <provoostenator> sipa: one thing we talked about before that would be useful for my HWW PR is away to compose descriptors in code
3082019-03-01T19:12:01  <provoostenator> If you're able to whip up an example for e.g. sh(wpkh(xpub)) I can probably figure out the rest
3092019-03-01T19:12:25  <provoostenator> It's just my C++ is a bit rusty when it comes to unique_ptr and abstract classes.
3102019-03-01T19:12:38  <sipa> provoostenator: it's not that trivial anymore in the current code
3112019-03-01T19:12:56  <sipa> i briefly had a look, but it would need some restructuring
3122019-03-01T19:13:07  <provoostenator> Ok, glad to know it's not just me :-)
3132019-03-01T19:13:15  *** rex4539 has joined #bitcoin-core-dev
3142019-03-01T19:14:33  <provoostenator> The use case here is that we fetch an xpub from a hardware wallet and then construct a descriptor with that.
3152019-03-01T19:14:45  <sipa> with the 0.18 things out of the way, i'll try to find time to do the ismine/keypool abstraction i've talked about before
3162019-03-01T19:15:13  <provoostenator> ismine/keypool stuff also very useful.
3172019-03-01T19:16:12  <provoostenator> An alternative approach would be to be require the hardware wallet (driver) to give a full descriptor, or a set of potential desrciptors from which we pick one or more.
3182019-03-01T19:16:39  <meshcollider> #topic descriptor based wallets
3192019-03-01T19:16:47  <provoostenator> But that choice shouldn't be determined by implementation details such as this I think.
3202019-03-01T19:17:02  <sipa> provoostenator: you can always construct the descriptor in string form
3212019-03-01T19:17:25  <sipa> i agree that's suboptimal, but it means having an API to construct descriptors shouldn't be a blocker
3222019-03-01T19:17:47  <provoostenator> That's what I'm doing in the prototype.
3232019-03-01T19:18:15  <instagibbs> I've done this previously as well, constructing manually
3242019-03-01T19:18:18  <provoostenator> There's not really any blockers left in that PR, so I'm mostly focussing on getting it merge-worthy.
3252019-03-01T19:18:34  *** _Sam-- has quit IRC
3262019-03-01T19:19:19  <provoostenator> Although it would be safer when combined with native-descriptor wallets, because the behavior of getnewaddress doesn't jive well with BIP44/49/84 that wallets use.
3272019-03-01T19:19:45  <provoostenator> (that hardware wallets tend to use)
3282019-03-01T19:19:55  <instagibbs> provoostenator, you're safe as long as you don't use getnewaddress with a watchonly wallet :D
3292019-03-01T19:20:24  <meshcollider> are hardware wallets working on implementing things like returning descriptors?
3302019-03-01T19:20:26  <provoostenator> instagibbs: so you use deriveaddresses?
3312019-03-01T19:20:43  <instagibbs> provoostenator, no I just assume people aren't going to dust my cold wallet :P
3322019-03-01T19:20:49  <provoostenator> meshcollider: not that I know, but HWI python coud easiliy do that.
3332019-03-01T19:20:56  <instagibbs> meshcollider, unlikely to get that standardized, no
3342019-03-01T19:21:15  <meshcollider> Mhm
3352019-03-01T19:21:30  <instagibbs> ledger has basically said they won't bother supporting PSBT like ever
3362019-03-01T19:21:42  <meshcollider> Oh, thats a shame
3372019-03-01T19:21:43  <instagibbs> I can't imagine they'd do descriptors
3382019-03-01T19:21:46  <sipa> well they don't need to
3392019-03-01T19:21:52  <instagibbs> sipa, right, it's fine
3402019-03-01T19:22:07  <instagibbs> just giving context
3412019-03-01T19:22:09  <sipa> i mean: i wouldn't even recommend that hw wallets directly implement psbt
3422019-03-01T19:22:18  <sipa> all you need is a software driver that supports it
3432019-03-01T19:22:25  <sipa> same with descriptors
3442019-03-01T19:22:36  <sipa> they're a software (and bitcoin core specifically...) kinda thing
3452019-03-01T19:22:58  <provoostenator> Basically Bitcoin Core could give an account number and then HWI would, if the device supports SegWit return three descriptors: "pkh([44'/0'/account]xpub/0/*])", "sh(wpkh([49'/0'/account]xpub/0/*]))" and "wpkh([84'/0'/account]xpub/0/*])" (plus change), and then our wallet imports one or all
3462019-03-01T19:23:10  <achow101> hwi already uses descriptors
3472019-03-01T19:24:04  <provoostenator> But the current importmulti logic doesn't handle the above correctly, native descriptor wallets would.
3482019-03-01T19:24:30  <provoostenator> So then you can get a bech32 address and it will grab it from the wpkh(84' tree, or fail if that's absent.
3492019-03-01T19:25:45  <provoostenator> We probably only need two address types: default and wrapped-segwit. Default is either legacy pkh() or native segwith (wpkh or script hash).
3502019-03-01T19:25:46  *** pinheadmz has quit IRC
3512019-03-01T19:26:17  <sipa> you'd mark certain records as the provider for certain types of addresses
3522019-03-01T19:27:05  *** pinheadmz has joined #bitcoin-core-dev
3532019-03-01T19:27:43  <sipa> if you don't have one for native segwit addresses, then requesting a native segwit address will fail
3542019-03-01T19:28:15  <provoostenator> Right, I guess it's fine to hold on to the current address_type concept then.
3552019-03-01T19:28:29  <provoostenator> legacy, p2sh_segwit and bech32
3562019-03-01T19:28:48  <provoostenator> But simply fail if the right descriptor isn't available.
3572019-03-01T19:28:52  *** pinheadmz has quit IRC
3582019-03-01T19:29:11  *** pinheadmz has joined #bitcoin-core-dev
3592019-03-01T19:29:27  <provoostenator> Do descriptors needs to "marked" for that? Or can you just infer it?
3602019-03-01T19:29:50  <meshcollider> The default ones would need to be marked in case you have others too
3612019-03-01T19:29:58  <sipa> well i'm imagining you can have multiple records
3622019-03-01T19:32:13  <provoostenator> One default record in case there's multiple records of the same address type.
3632019-03-01T19:32:13  <sipa> (especially if you have a wallet that at some point switched over to a new key/descriptor/hwwallet for whatever reason, but still want to keep access to old transaction history with the previous ones)
3642019-03-01T19:32:13  <provoostenator> I was thinking of adding a purpose enum: receive, change, other
3652019-03-01T19:32:13  <sipa> yes
3662019-03-01T19:32:14  <provoostenator> For each address type there can only be one descriptor with receive/change
3672019-03-01T19:32:16  *** jarthur has quit IRC
3682019-03-01T19:32:23  <sipa> why?
3692019-03-01T19:32:32  <provoostenator> Because that indicates the default
3702019-03-01T19:32:47  <sipa> what a descriptor is used for should be independent of whether it's the default imo
3712019-03-01T19:32:54  <provoostenator> That makes sense
3722019-03-01T19:33:06  <provoostenator> So then in addition to purpose, we also need to track the default descriptors.
3732019-03-01T19:33:11  <sipa> if you transition to a new one, the one you used for change before doesn't stop being change
3742019-03-01T19:33:52  <sipa> i think that's all in https://gist.github.com/sipa/125cfa1615946d0c3f3eec2ad7f250a2 already
3752019-03-01T19:34:11  <provoostenator> How do we identify descriptors if there's more than one? Just an increasing int as we add them, or by their checksum (seems brittle) or something else?
3762019-03-01T19:34:48  <sipa> seems like an implementation detail
3772019-03-01T19:35:38  <provoostenator> Well, it matters for RPC arguments, but for now I'm avoiding that problem by not allowing more than one of each purpose :-)
3782019-03-01T19:36:11  <sipa> do you need to expose internal identifiers?
3792019-03-01T19:36:44  <sipa> (i haven't thought much about this)
3802019-03-01T19:36:51  <meshcollider> Identify them by checksum :p
3812019-03-01T19:37:28  <sipa> if so, it seems best that records have a unique user-provided name, and you use that name in rpc to refer to them
3822019-03-01T19:37:31  <provoostenator> sipa: getnewaddress "Buy new cow" bech32 [how do I tell which non-default descriptor to use]
3832019-03-01T19:37:48  <instagibbs> why not force them to switch first, then call getnewaddress
3842019-03-01T19:37:50  <sipa> provoostenator: is that necessary?
3852019-03-01T19:38:00  <provoostenator> Name makes sense
3862019-03-01T19:38:08  <sipa> provoostenator: you can't getnewaddress from an old keypool now either
3872019-03-01T19:38:21  <meshcollider> Other records are more for things like watch-only, etc
3882019-03-01T19:38:38  <meshcollider> Internal stuff
3892019-03-01T19:38:42  <provoostenator> True, if non-default descriptors can only be used for archival purposes then there's no need to support them in getnewaddress
3902019-03-01T19:39:03  <sipa> that's what i was thinking yes; they're just there to not lose old transaction history
3912019-03-01T19:39:07  <sipa> or to watch
3922019-03-01T19:39:12  <provoostenator> It also depends on how much we want to push for 1-wallet-1-goal
3932019-03-01T19:39:23  <provoostenator> Rather than put-whatever-you-want-in-a-single-walllet
3942019-03-01T19:40:09  <sipa> right; but in a pure watch-only wallet (where "watch only" truly means you're watching someone else's wallet, not just "i don't have the private key right here"), you probably don't want to have any "default newaddress provider"
3952019-03-01T19:40:15  <provoostenator> I also prefer keeping wallets simple in that sense, especially to keep the GUI sane.
3962019-03-01T19:40:19  <sipa> because there shouldn't be a way to create new addresses
3972019-03-01T19:41:01  *** pinheadmz has quit IRC
3982019-03-01T19:41:19  *** pinheadmz has joined #bitcoin-core-dev
3992019-03-01T19:41:29  <provoostenator> Agree that getnewaddress should require >= IsSolveable
4002019-03-01T19:41:40  <sipa> descriptors are always solvable
4012019-03-01T19:41:59  <sipa> (except the "raw" and "script" ones, but those can't be used to derive anything anyway)
4022019-03-01T19:42:06  <provoostenator> Ah yes
4032019-03-01T19:42:12  <sipa> solvability is not the point
4042019-03-01T19:42:37  <meshcollider> thats the difference between is "mine" and is "spendable"
4052019-03-01T19:43:04  <sipa> so right now "watchonly" means "i don't happen to have the private key in my wallet.dat file"
4062019-03-01T19:43:10  <sipa> i think that's a mistake
4072019-03-01T19:43:44  <meshcollider> Agree, this rework is the perfect time to tighten up definition of things like that too
4082019-03-01T19:43:45  <sipa> the distinction between "my money" and "watched money" is useful, but it's somewhat independent from where the private keys live
4092019-03-01T19:44:23  <sipa> especially in a hwwallet/offline storage/... kinda world... the case where the private key is actually in your wallet.dat file (even for your own coins) should be the exception
4102019-03-01T19:45:34  <sipa> oh, i guess i should bring this up here, i did a talk at SBC19 about miniscript, and i'll work on getting support for it in core
4112019-03-01T19:45:53  <sipa> so that our signer (including psbt, etc) can deal with more complicated scripts than just single key and multisig
4122019-03-01T19:46:46  <provoostenator> So we can do things like GreenAddress style multisig or timeout & single sig?
4132019-03-01T19:46:50  <sipa> yeah
4142019-03-01T19:47:16  <meshcollider> Was the talk recorded
4152019-03-01T19:47:28  <sipa> https://www.youtube.com/watch?v=XM1lzN4Zfks
4162019-03-01T19:47:34  <meshcollider> Thanks
4172019-03-01T19:47:38  <provoostenator> I wonder what the setup UX would look like if e.g. you had two hardware wallets and wanted such a 2-of-2 or timeout & 1-of-2.
4182019-03-01T19:47:53  <sipa> provoostenator: that's a question for you :)
4192019-03-01T19:48:00  <sipa> i'm perfectly fine with psbt rpcs :P
4202019-03-01T19:48:20  <instagibbs> gui coin control tho
4212019-03-01T19:48:20  <achow101> sipa: replacing the signer with miniscript would probably be a good time to also distinguish between signing and finalizing
4222019-03-01T19:48:32  <sipa> achow101: hmm?
4232019-03-01T19:48:55  <provoostenator> Right, I guess there would be an RPC where you give it a meta-descriptor or miniscript, then it goes and fetches xpubs from both devices in sequence and imports the right descriptors
4242019-03-01T19:49:11  <provoostenator> Plus asking some sanity check questions to the driver like "can you sign stuff with nlocktime"
4252019-03-01T19:49:20  <achow101> ProduceSignature makes both the signature and scriptSig/witness
4262019-03-01T19:49:20  <instagibbs> provoostenator, the descriptor will be parsed into miniscript, afaik
4272019-03-01T19:49:25  <sipa> provoostenator: the workflow is that you'd use the miniscript compiler to convert a policy to a descriptor
4282019-03-01T19:49:28  <instagibbs> ^
4292019-03-01T19:49:29  <sipa> and then import the descriptor
4302019-03-01T19:49:30  <instagibbs> yeah
4312019-03-01T19:49:42  <sipa> the compiler could be built-in, but doesn't need to be
4322019-03-01T19:49:51  <provoostenator> Do you put xpubs in the miniscript or does that happen later?
4332019-03-01T19:50:00  <achow101> But under the psbt model, those should be distinct.
4342019-03-01T19:50:06  <sipa> provoostenator: yeah
4352019-03-01T19:50:17  <sipa> the compiler just passes those though, i imagine
4362019-03-01T19:50:58  <sipa> (miniscript is just the name of the subset of script; i use "policy" language to refer to the input of the compiler)
4372019-03-01T19:51:06  <sipa> i know, i suck at naming things
4382019-03-01T19:51:21  <sipa> and this is genuinely confusing because there are several things that look kinda similar
4392019-03-01T19:51:47  <provoostenator> signerfetchkeys "miniscript with rules $device_fingerprint_1  $device_fingerprint_1"
4402019-03-01T19:51:50  <sipa> achow101: yeah, i guess it can simplify things if we split up the signer and finalizer in the code too
4412019-03-01T19:51:53  <provoostenator> Piece of cake
4422019-03-01T19:54:48  <meshcollider> Is there anything else anyone wants to talk about in the last few minutes
4432019-03-01T19:58:53  <meshcollider> #endmeeting
4442019-03-01T19:58:53  <lightningbot> Meeting ended Fri Mar  1 19:58:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
4452019-03-01T19:58:53  <lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.html
4462019-03-01T19:58:53  <lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.txt
4472019-03-01T19:58:53  <lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2019/bitcoin-core-dev.2019-03-01-19.00.log.html
4482019-03-01T20:01:50  *** ExtraCrispy has quit IRC
4492019-03-01T20:02:20  *** ExtraCrispy has joined #bitcoin-core-dev
4502019-03-01T20:12:40  *** dqx has quit IRC
4512019-03-01T20:13:43  *** dqx has joined #bitcoin-core-dev
4522019-03-01T20:21:19  *** mmgen has quit IRC
4532019-03-01T20:48:48  *** AaronvanW has quit IRC
4542019-03-01T20:55:02  *** AaronvanW has joined #bitcoin-core-dev
4552019-03-01T20:59:07  *** jarthur has joined #bitcoin-core-dev
4562019-03-01T20:59:35  *** AaronvanW has quit IRC
4572019-03-01T21:11:30  *** ccxp has joined #bitcoin-core-dev
4582019-03-01T21:11:54  *** dqx has quit IRC
4592019-03-01T21:13:03  *** dqx has joined #bitcoin-core-dev
4602019-03-01T21:34:46  *** schmidty_ has quit IRC
4612019-03-01T21:37:16  *** baldur has quit IRC
4622019-03-01T21:37:28  *** AaronvanW has joined #bitcoin-core-dev
4632019-03-01T21:38:00  *** baldur has joined #bitcoin-core-dev
4642019-03-01T21:41:08  *** schmidty has joined #bitcoin-core-dev
4652019-03-01T21:41:08  *** schmidty has joined #bitcoin-core-dev
4662019-03-01T21:45:40  *** schmidty has quit IRC
4672019-03-01T21:50:14  *** mn949588 has joined #bitcoin-core-dev
4682019-03-01T21:56:26  *** Aaronvan_ has joined #bitcoin-core-dev
4692019-03-01T21:56:31  *** AaronvanW has quit IRC
4702019-03-01T21:58:33  *** Guyver2 has quit IRC
4712019-03-01T22:12:27  *** kexkey has joined #bitcoin-core-dev
4722019-03-01T22:12:29  *** schmidty has joined #bitcoin-core-dev
4732019-03-01T22:16:54  *** schmidty has quit IRC
4742019-03-01T22:19:17  *** DougieBot5000_ is now known as DougieBot5000
4752019-03-01T22:19:57  *** DeanGuss has joined #bitcoin-core-dev
4762019-03-01T22:30:06  *** schmidty has joined #bitcoin-core-dev
4772019-03-01T22:34:37  *** schmidty has quit IRC
4782019-03-01T22:34:52  *** AaronvanW has joined #bitcoin-core-dev
4792019-03-01T22:36:45  *** spinza has quit IRC
4802019-03-01T22:37:50  *** Aaronvan_ has quit IRC
4812019-03-01T22:44:26  *** mariorz_ has joined #bitcoin-core-dev
4822019-03-01T22:44:50  *** noganoo_ has joined #bitcoin-core-dev
4832019-03-01T22:44:51  *** gleb_ has joined #bitcoin-core-dev
4842019-03-01T22:45:16  *** bosma_ has joined #bitcoin-core-dev
4852019-03-01T22:45:56  *** nejon_ has joined #bitcoin-core-dev
4862019-03-01T22:46:18  *** pierre_rochard_ has joined #bitcoin-core-dev
4872019-03-01T22:46:58  *** kallewoof_ has joined #bitcoin-core-dev
4882019-03-01T22:47:04  *** spinza has joined #bitcoin-core-dev
4892019-03-01T22:51:28  *** cncr04s_ has joined #bitcoin-core-dev
4902019-03-01T22:52:10  *** BlueMatt_ has joined #bitcoin-core-dev
4912019-03-01T22:52:37  *** kallewoof has quit IRC
4922019-03-01T22:52:42  *** noganoo has quit IRC
4932019-03-01T22:52:43  *** pierre_rochard has quit IRC
4942019-03-01T22:52:43  *** x4b1d has quit IRC
4952019-03-01T22:52:43  *** BlueMatt has quit IRC
4962019-03-01T22:52:43  *** mariorz has quit IRC
4972019-03-01T22:52:45  *** nejon has quit IRC
4982019-03-01T22:52:45  *** bosma has quit IRC
4992019-03-01T22:52:45  *** cncr04s has quit IRC
5002019-03-01T22:52:45  *** gleb has quit IRC
5012019-03-01T22:52:45  *** pierre_rochard_ is now known as pierre_rochard
5022019-03-01T22:52:45  *** noganoo_ is now known as noganoo
5032019-03-01T22:52:46  *** nejon_ is now known as nejon
5042019-03-01T22:52:46  *** mariorz_ is now known as mariorz
5052019-03-01T22:52:48  *** bosma_ is now known as bosma
5062019-03-01T22:55:14  *** CubicEarth has quit IRC
5072019-03-01T22:55:29  *** cncr04s_ has quit IRC
5082019-03-01T22:57:12  *** cncr04s has joined #bitcoin-core-dev
5092019-03-01T22:57:12  *** owowo has quit IRC
5102019-03-01T22:57:12  *** nullptr| has quit IRC
5112019-03-01T22:57:49  *** owowo has joined #bitcoin-core-dev
5122019-03-01T22:57:52  *** nullptr| has joined #bitcoin-core-dev
5132019-03-01T22:59:05  *** CubicEarth has joined #bitcoin-core-dev
5142019-03-01T22:59:16  *** x4b1d has joined #bitcoin-core-dev
5152019-03-01T23:03:58  *** timothy has quit IRC
5162019-03-01T23:17:37  *** mn949588 has quit IRC
5172019-03-01T23:18:38  *** mn949588 has joined #bitcoin-core-dev
5182019-03-01T23:20:19  *** kexkey has quit IRC
5192019-03-01T23:37:27  *** dviola has joined #bitcoin-core-dev
5202019-03-01T23:39:35  *** jarthur has quit IRC
5212019-03-01T23:40:24  *** schmidty has joined #bitcoin-core-dev
5222019-03-01T23:43:14  *** zhangzf has joined #bitcoin-core-dev
5232019-03-01T23:45:01  *** schmidty has quit IRC