12017-11-09T00:00:45 *** AaronvanW has joined #bitcoin-core-dev
22017-11-09T00:03:55 *** Chris_Stewart_5 has joined #bitcoin-core-dev
32017-11-09T00:10:02 *** bule has quit IRC
42017-11-09T00:10:30 *** bule has joined #bitcoin-core-dev
52017-11-09T00:16:14 *** bule has quit IRC
62017-11-09T00:16:36 *** bule has joined #bitcoin-core-dev
72017-11-09T00:16:53 *** mxg has joined #bitcoin-core-dev
82017-11-09T00:19:57 *** AaronvanW has quit IRC
92017-11-09T00:21:24 *** tux3do has joined #bitcoin-core-dev
102017-11-09T00:24:40 *** AaronvanW has joined #bitcoin-core-dev
112017-11-09T00:26:37 *** Aaronvan_ has joined #bitcoin-core-dev
122017-11-09T00:28:05 *** ekrion has quit IRC
132017-11-09T00:29:14 *** Aaronvan_ has quit IRC
142017-11-09T00:29:56 *** Aaronvan_ has joined #bitcoin-core-dev
152017-11-09T00:30:27 *** AaronvanW has quit IRC
162017-11-09T00:30:39 *** promag has quit IRC
172017-11-09T00:30:53 *** promag has joined #bitcoin-core-dev
182017-11-09T00:32:56 *** NielsvG has quit IRC
192017-11-09T00:33:03 *** Chris_Stewart_5 has quit IRC
202017-11-09T00:40:22 *** ekrion has joined #bitcoin-core-dev
212017-11-09T00:47:40 *** esotericnonsense is now known as zombocoin
222017-11-09T00:50:44 *** NielsvG has joined #bitcoin-core-dev
232017-11-09T00:50:48 *** NielsvG has joined #bitcoin-core-dev
242017-11-09T00:51:43 *** jb55 has quit IRC
252017-11-09T00:52:49 *** Aaronvan_ is now known as AaronvanW
262017-11-09T00:52:57 *** zombocoin is now known as esotericnonsense
272017-11-09T00:54:26 *** meshcollider has joined #bitcoin-core-dev
282017-11-09T01:07:05 *** lxer has quit IRC
292017-11-09T01:09:23 *** AndBobsYourUncle has joined #bitcoin-core-dev
302017-11-09T01:12:22 *** ula has quit IRC
312017-11-09T01:23:17 *** promag has quit IRC
322017-11-09T01:32:35 *** tux3do has quit IRC
332017-11-09T01:35:52 *** Ylbam has quit IRC
342017-11-09T01:36:09 *** AaronvanW has quit IRC
352017-11-09T01:37:09 *** AaronvanW has joined #bitcoin-core-dev
362017-11-09T01:37:31 *** jb55 has joined #bitcoin-core-dev
372017-11-09T01:41:07 *** btcdrak has joined #bitcoin-core-dev
382017-11-09T01:53:02 *** jtimon has joined #bitcoin-core-dev
392017-11-09T01:53:27 *** kexkey has joined #bitcoin-core-dev
402017-11-09T02:20:22 *** goatpig has quit IRC
412017-11-09T02:23:20 *** hnfgns has quit IRC
422017-11-09T02:24:39 *** jb55 has quit IRC
432017-11-09T02:25:08 *** jb55 has joined #bitcoin-core-dev
442017-11-09T02:30:05 *** LumberCartel has quit IRC
452017-11-09T02:31:33 *** hnfgns has joined #bitcoin-core-dev
462017-11-09T02:32:27 *** ekrion has quit IRC
472017-11-09T02:33:34 *** AndBobsYourUncle has quit IRC
482017-11-09T02:39:33 *** ekrion has joined #bitcoin-core-dev
492017-11-09T02:47:41 *** ekrion has quit IRC
502017-11-09T02:49:03 *** ekrion has joined #bitcoin-core-dev
512017-11-09T02:50:08 *** Dyaheon has quit IRC
522017-11-09T02:50:40 *** instagibbs has quit IRC
532017-11-09T02:50:40 *** LeMiner2 has quit IRC
542017-11-09T02:50:40 *** atroxes has quit IRC
552017-11-09T02:50:50 *** Dyaheon has joined #bitcoin-core-dev
562017-11-09T02:51:08 *** hello5678 has joined #bitcoin-core-dev
572017-11-09T02:51:12 *** Soligor has quit IRC
582017-11-09T02:51:12 *** andytoshi has quit IRC
592017-11-09T02:51:12 *** lvmbdv has quit IRC
602017-11-09T02:51:12 *** newbie-- has quit IRC
612017-11-09T02:51:12 *** TD-Linux has quit IRC
622017-11-09T02:51:12 *** kakobrekla has quit IRC
632017-11-09T02:51:29 *** lvmbdv has joined #bitcoin-core-dev
642017-11-09T02:51:44 *** roadcrap has quit IRC
652017-11-09T02:51:44 *** Lauda has quit IRC
662017-11-09T02:51:44 *** cluelessperson has quit IRC
672017-11-09T02:51:44 *** ryan-c has quit IRC
682017-11-09T02:52:11 *** twistedline has joined #bitcoin-core-dev
692017-11-09T02:52:52 *** andytoshi has joined #bitcoin-core-dev
702017-11-09T02:56:49 *** TD-Linux has joined #bitcoin-core-dev
712017-11-09T02:57:01 *** ryan-c has joined #bitcoin-core-dev
722017-11-09T02:57:01 *** atroxes has joined #bitcoin-core-dev
732017-11-09T02:57:06 *** cluelessperson has joined #bitcoin-core-dev
742017-11-09T02:57:42 *** instagibbs has joined #bitcoin-core-dev
752017-11-09T02:57:52 *** newbie-- has joined #bitcoin-core-dev
762017-11-09T02:58:20 *** hnfgns has quit IRC
772017-11-09T03:02:35 *** hello5678 has quit IRC
782017-11-09T03:02:53 *** kakobrekla has joined #bitcoin-core-dev
792017-11-09T03:14:04 *** hsmiths has quit IRC
802017-11-09T03:14:29 *** btcdrak has quit IRC
812017-11-09T03:14:30 *** NielsvG has quit IRC
822017-11-09T03:14:30 *** kewde[m] has quit IRC
832017-11-09T03:14:42 *** NielsvG has joined #bitcoin-core-dev
842017-11-09T03:14:43 *** NielsvG has joined #bitcoin-core-dev
852017-11-09T03:14:48 *** btcdrak has joined #bitcoin-core-dev
862017-11-09T03:15:44 *** griswaalt[m] has quit IRC
872017-11-09T03:16:26 *** herzmeister[m] has quit IRC
882017-11-09T03:16:53 *** Masaomi[m] has quit IRC
892017-11-09T03:20:27 *** AaronvanW has quit IRC
902017-11-09T03:26:21 *** uneeb has joined #bitcoin-core-dev
912017-11-09T03:30:42 *** uneeb has quit IRC
922017-11-09T03:32:49 *** AndBobsYourUncle has joined #bitcoin-core-dev
932017-11-09T03:44:23 *** bule has quit IRC
942017-11-09T03:44:39 *** bule has joined #bitcoin-core-dev
952017-11-09T03:44:41 *** AndBobsYourUncle has quit IRC
962017-11-09T03:45:36 *** StopAndDecrypt has quit IRC
972017-11-09T03:47:27 *** bule has quit IRC
982017-11-09T03:49:37 *** LeMiner2 has joined #bitcoin-core-dev
992017-11-09T03:55:01 *** Emcy_ has joined #bitcoin-core-dev
1002017-11-09T03:56:39 *** Emcy has quit IRC
1012017-11-09T03:56:39 *** phantomcircuit has quit IRC
1022017-11-09T03:56:45 *** phantomcircuit has joined #bitcoin-core-dev
1032017-11-09T03:59:57 *** atroxes has quit IRC
1042017-11-09T04:01:39 *** atroxes has joined #bitcoin-core-dev
1052017-11-09T04:21:59 *** MrPaz has quit IRC
1062017-11-09T04:23:03 *** qrestlove has quit IRC
1072017-11-09T04:26:32 *** BlackCow27 has joined #bitcoin-core-dev
1082017-11-09T04:30:27 *** qrestlove has joined #bitcoin-core-dev
1092017-11-09T04:34:08 *** roasbeef has joined #bitcoin-core-dev
1102017-11-09T04:36:45 *** bule has joined #bitcoin-core-dev
1112017-11-09T04:49:49 *** tripleslash has quit IRC
1122017-11-09T04:54:33 *** roadcrap has joined #bitcoin-core-dev
1132017-11-09T04:55:04 *** qrestlove has quit IRC
1142017-11-09T04:58:58 *** qrestlove has joined #bitcoin-core-dev
1152017-11-09T04:59:59 *** qrestlove has quit IRC
1162017-11-09T05:00:28 *** qrestlove has joined #bitcoin-core-dev
1172017-11-09T05:04:21 *** chjj has quit IRC
1182017-11-09T05:05:21 *** AndBobsYourUncle has joined #bitcoin-core-dev
1192017-11-09T05:08:32 *** qrestlove has quit IRC
1202017-11-09T05:09:40 *** AndBobsYourUncle has left #bitcoin-core-dev
1212017-11-09T05:10:25 *** chjj has joined #bitcoin-core-dev
1222017-11-09T05:12:08 *** qrestlove has joined #bitcoin-core-dev
1232017-11-09T05:13:41 *** hsmiths has joined #bitcoin-core-dev
1242017-11-09T05:15:34 *** chjj has quit IRC
1252017-11-09T05:21:22 *** LumberCartel has joined #bitcoin-core-dev
1262017-11-09T05:21:41 *** StopAndDecrypt has joined #bitcoin-core-dev
1272017-11-09T05:32:17 *** bule2 has joined #bitcoin-core-dev
1282017-11-09T05:35:08 *** bule has quit IRC
1292017-11-09T05:36:37 *** bule2 has quit IRC
1302017-11-09T05:37:13 *** herzmeister[m] has joined #bitcoin-core-dev
1312017-11-09T05:45:59 *** kewde[m] has joined #bitcoin-core-dev
1322017-11-09T05:45:59 *** griswaalt[m] has joined #bitcoin-core-dev
1332017-11-09T05:46:01 *** Masaomi[m] has joined #bitcoin-core-dev
1342017-11-09T05:46:32 *** justanotheruser has quit IRC
1352017-11-09T05:46:49 *** justanotheruser has joined #bitcoin-core-dev
1362017-11-09T05:47:00 *** Guest4 has joined #bitcoin-core-dev
1372017-11-09T05:53:47 *** justanotheruser has quit IRC
1382017-11-09T05:54:05 *** justanotheruser has joined #bitcoin-core-dev
1392017-11-09T06:01:32 *** qrestlove has quit IRC
1402017-11-09T06:13:33 *** trippysa1mon has joined #bitcoin-core-dev
1412017-11-09T06:13:36 *** pigeons_ has joined #bitcoin-core-dev
1422017-11-09T06:13:40 *** aj_ has joined #bitcoin-core-dev
1432017-11-09T06:14:03 *** harding_ has joined #bitcoin-core-dev
1442017-11-09T06:14:47 *** Emcy has joined #bitcoin-core-dev
1452017-11-09T06:15:02 *** pigeons has quit IRC
1462017-11-09T06:15:02 *** [b__b] has quit IRC
1472017-11-09T06:15:02 *** aj has quit IRC
1482017-11-09T06:15:02 *** trippysalmon has quit IRC
1492017-11-09T06:15:02 *** harding has quit IRC
1502017-11-09T06:15:03 *** LumberCartel_ has joined #bitcoin-core-dev
1512017-11-09T06:15:03 *** victorSN has quit IRC
1522017-11-09T06:15:33 *** qrestlove has joined #bitcoin-core-dev
1532017-11-09T06:15:46 *** sjums_ has joined #bitcoin-core-dev
1542017-11-09T06:16:44 *** arubi has quit IRC
1552017-11-09T06:16:53 *** Taek42 has joined #bitcoin-core-dev
1562017-11-09T06:22:50 *** LumberCartel has quit IRC
1572017-11-09T06:22:50 *** Emcy_ has quit IRC
1582017-11-09T06:22:50 *** nsh has quit IRC
1592017-11-09T06:22:50 *** Taek has quit IRC
1602017-11-09T06:22:50 *** sjums has quit IRC
1612017-11-09T06:24:17 *** [b__b] has joined #bitcoin-core-dev
1622017-11-09T06:25:21 *** victorSN has joined #bitcoin-core-dev
1632017-11-09T06:26:24 *** arubi has joined #bitcoin-core-dev
1642017-11-09T06:27:02 *** lukedashjr has joined #bitcoin-core-dev
1652017-11-09T06:27:57 *** luke-jr has quit IRC
1662017-11-09T06:29:27 *** nsh has joined #bitcoin-core-dev
1672017-11-09T06:31:26 *** lukedashjr is now known as luke-jr
1682017-11-09T06:41:50 *** LumberCartel_ has quit IRC
1692017-11-09T06:42:09 *** LumberCartel has joined #bitcoin-core-dev
1702017-11-09T06:42:36 *** chjj has joined #bitcoin-core-dev
1712017-11-09T06:43:55 *** arubi has quit IRC
1722017-11-09T06:44:16 *** arubi has joined #bitcoin-core-dev
1732017-11-09T06:46:59 *** Lauda has joined #bitcoin-core-dev
1742017-11-09T06:49:15 *** Guest4 has quit IRC
1752017-11-09T06:58:46 *** Ylbam has joined #bitcoin-core-dev
1762017-11-09T07:07:44 *** Victor_sueca has joined #bitcoin-core-dev
1772017-11-09T07:09:10 *** sjums_ has quit IRC
1782017-11-09T07:09:45 *** ensign_ has quit IRC
1792017-11-09T07:09:52 *** nsh has quit IRC
1802017-11-09T07:10:05 *** ghost43 has quit IRC
1812017-11-09T07:10:12 *** Taek42 has quit IRC
1822017-11-09T07:11:01 *** Victorsueca has quit IRC
1832017-11-09T07:11:17 *** alephzero has quit IRC
1842017-11-09T07:15:24 *** ghost43 has joined #bitcoin-core-dev
1852017-11-09T07:19:35 *** chjj has quit IRC
1862017-11-09T07:25:56 *** alephzero has joined #bitcoin-core-dev
1872017-11-09T07:48:48 *** brianhoffman has quit IRC
1882017-11-09T07:54:06 *** BashCo has quit IRC
1892017-11-09T07:56:29 *** promag has joined #bitcoin-core-dev
1902017-11-09T08:06:08 *** gribble has quit IRC
1912017-11-09T08:15:09 *** JackH has quit IRC
1922017-11-09T08:17:13 *** gribble has joined #bitcoin-core-dev
1932017-11-09T08:22:10 *** BashCo has joined #bitcoin-core-dev
1942017-11-09T08:23:30 *** lxer has joined #bitcoin-core-dev
1952017-11-09T08:26:26 *** Victor_sueca is now known as Victorsueca
1962017-11-09T08:34:41 *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
1972017-11-09T08:34:44 *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
1982017-11-09T08:41:35 *** JackH has joined #bitcoin-core-dev
1992017-11-09T08:45:29 *** btcdrak has quit IRC
2002017-11-09T08:48:38 *** CubicEarth has joined #bitcoin-core-dev
2012017-11-09T08:53:18 *** Soligor has joined #bitcoin-core-dev
2022017-11-09T08:58:02 *** Khunbish has joined #bitcoin-core-dev
2032017-11-09T09:03:45 *** kexkey has quit IRC
2042017-11-09T09:07:58 *** laurentmt has joined #bitcoin-core-dev
2052017-11-09T09:23:59 *** puff has quit IRC
2062017-11-09T09:24:55 *** promag has joined #bitcoin-core-dev
2072017-11-09T09:24:58 *** puff has joined #bitcoin-core-dev
2082017-11-09T09:26:51 *** Khunbish has quit IRC
2092017-11-09T09:29:00 *** CubicEar_ has joined #bitcoin-core-dev
2102017-11-09T09:30:02 *** berndj has quit IRC
2112017-11-09T09:30:16 *** berndj has joined #bitcoin-core-dev
2122017-11-09T09:31:34 *** clarkmoody has quit IRC
2132017-11-09T09:31:36 *** CubicEarth has quit IRC
2142017-11-09T09:31:58 *** clarkmoody has joined #bitcoin-core-dev
2152017-11-09T09:32:35 *** shesek has joined #bitcoin-core-dev
2162017-11-09T09:32:35 *** shesek has joined #bitcoin-core-dev
2172017-11-09T09:35:18 *** sjums has joined #bitcoin-core-dev
2182017-11-09T09:37:07 *** Khunbish has joined #bitcoin-core-dev
2192017-11-09T09:37:48 *** promag has quit IRC
2202017-11-09T09:38:06 *** ensign has joined #bitcoin-core-dev
2212017-11-09T09:38:19 *** promag has joined #bitcoin-core-dev
2222017-11-09T09:39:15 *** nsh has joined #bitcoin-core-dev
2232017-11-09T09:47:53 *** timothy has joined #bitcoin-core-dev
2242017-11-09T10:01:10 *** Ylbam has quit IRC
2252017-11-09T10:21:21 *** laurentmt1 has joined #bitcoin-core-dev
2262017-11-09T10:21:33 *** laurentmt has quit IRC
2272017-11-09T10:21:33 *** laurentmt1 is now known as laurentmt
2282017-11-09T10:29:22 *** dermoth has joined #bitcoin-core-dev
2292017-11-09T10:58:30 *** moctos has joined #bitcoin-core-dev
2302017-11-09T11:02:31 *** btcdrak has joined #bitcoin-core-dev
2312017-11-09T11:05:52 *** shesek has quit IRC
2322017-11-09T11:18:19 *** adetate has joined #bitcoin-core-dev
2332017-11-09T11:18:57 <luke-jr> I wonder if split HD should have had a 3rd category for refund addresses :x
2342017-11-09T11:19:15 *** moctos has quit IRC
2352017-11-09T11:31:04 *** Khunbish has quit IRC
2362017-11-09T11:37:56 *** dermoth has quit IRC
2372017-11-09T11:38:18 *** dermoth has joined #bitcoin-core-dev
2382017-11-09T12:00:03 *** promag has quit IRC
2392017-11-09T12:11:46 *** promag has joined #bitcoin-core-dev
2402017-11-09T12:13:29 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f7388e93d3dd...b5f9f025fef0
2412017-11-09T12:13:29 <bitcoin-git> bitcoin/master bc9c0a7 Russell Yanofsky: Improve wallet-accounts test...
2422017-11-09T12:13:30 <bitcoin-git> bitcoin/master b5f9f02 Wladimir J. van der Laan: Merge #11552: Improve wallet-accounts test...
2432017-11-09T12:14:01 <bitcoin-git> [bitcoin] laanwj closed pull request #11552: Improve wallet-accounts test (master...pr/acctt) https://github.com/bitcoin/bitcoin/pull/11552
2442017-11-09T12:16:29 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b5f9f025fef0...0dec4cc30044
2452017-11-09T12:16:29 <bitcoin-git> bitcoin/master 9db9d62 gnuser: Refactor: make the read function simpler
2462017-11-09T12:16:30 <bitcoin-git> bitcoin/master 0dec4cc Wladimir J. van der Laan: Merge #11221: Refactor: simpler read...
2472017-11-09T12:16:51 <bitcoin-git> [bitcoin] laanwj closed pull request #11221: Refactor: simpler read (master...refactor-streams) https://github.com/bitcoin/bitcoin/pull/11221
2482017-11-09T12:17:29 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0dec4cc30044...331352f99f23
2492017-11-09T12:17:29 <bitcoin-git> bitcoin/master 16be7dd Florian Schmaus: Improve bitcoind systemd service file...
2502017-11-09T12:17:29 <bitcoin-git> bitcoin/master 331352f Wladimir J. van der Laan: Merge #10529: Improve bitcoind systemd service file...
2512017-11-09T12:17:43 <bitcoin-git> [bitcoin] laanwj closed pull request #10529: Improve bitcoind systemd service file (master...systemd-service) https://github.com/bitcoin/bitcoin/pull/10529
2522017-11-09T12:17:46 *** bsm117532 has quit IRC
2532017-11-09T12:33:07 <bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/331352f99f23...0ecc6305f464
2542017-11-09T12:33:08 <bitcoin-git> bitcoin/master b411c2a João Barbosa: Improve -disablewallet parameter interaction
2552017-11-09T12:33:08 <bitcoin-git> bitcoin/master 7963335 João Barbosa: Fix -disablewallet default value
2562017-11-09T12:33:09 <bitcoin-git> bitcoin/master 0ecc630 Wladimir J. van der Laan: Merge #11594: Improve -disablewallet parameter interaction...
2572017-11-09T12:33:35 <bitcoin-git> [bitcoin] laanwj closed pull request #11594: Improve -disablewallet parameter interaction (master...2017-11-disable-wallet) https://github.com/bitcoin/bitcoin/pull/11594
2582017-11-09T12:34:33 *** adetate has quit IRC
2592017-11-09T12:39:17 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0ecc6305f464...ef3758d1ef73
2602017-11-09T12:39:17 <bitcoin-git> bitcoin/master b109a1c practicalswift: Remove redundant nullptr checks before deallocation...
2612017-11-09T12:39:18 <bitcoin-git> bitcoin/master ef3758d Wladimir J. van der Laan: Merge #10696: Remove redundant nullptr checks before deallocation...
2622017-11-09T12:39:31 <bitcoin-git> [bitcoin] laanwj closed pull request #10696: Remove redundant nullptr checks before deallocation (master...delete-nullptr) https://github.com/bitcoin/bitcoin/pull/10696
2632017-11-09T12:43:35 *** Khunbish has joined #bitcoin-core-dev
2642017-11-09T12:44:25 *** SopaXorzTaker has joined #bitcoin-core-dev
2652017-11-09T12:49:10 <bitcoin-git> [bitcoin] laanwj closed pull request #9716: [Net] Clarity TIMEOUT_INTERVAL constant meaning. (master...2017-02-07-ping-timeout-interval) https://github.com/bitcoin/bitcoin/pull/9716
2662017-11-09T12:54:33 *** promag has quit IRC
2672017-11-09T13:13:25 *** wxss_ has joined #bitcoin-core-dev
2682017-11-09T13:15:05 *** wxss has quit IRC
2692017-11-09T13:15:19 *** wxss_ is now known as wxss
2702017-11-09T13:19:28 <bitcoin-git> [bitcoin] laanwj closed pull request #10890: libbitcoinconsensus: Add version field to pkg-config info file (master...master) https://github.com/bitcoin/bitcoin/pull/10890
2712017-11-09T13:23:51 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/ef3758d1ef73...77ba4bf960d3
2722017-11-09T13:23:51 <bitcoin-git> bitcoin/master 5a5e4e9 Karl-Johan Alm: [wallet] Remove CTransaction&() helper conversion operator from wallet implementation.
2732017-11-09T13:23:52 <bitcoin-git> bitcoin/master 77ba4bf Wladimir J. van der Laan: Merge #10368: [wallet] Remove helper conversion operator from wallet...
2742017-11-09T13:23:57 *** meshcollider has quit IRC
2752017-11-09T13:24:01 <bitcoin-git> [bitcoin] laanwj closed pull request #10368: [wallet] Remove helper conversion operator from wallet (master...wallet-refactor-remove-ctrans-helper) https://github.com/bitcoin/bitcoin/pull/10368
2762017-11-09T13:24:24 *** m8tion has joined #bitcoin-core-dev
2772017-11-09T13:36:22 *** ExtraCrispy has joined #bitcoin-core-dev
2782017-11-09T13:54:32 *** StopAndDecrypt has quit IRC
2792017-11-09T13:55:50 *** StopAndDecrypt has joined #bitcoin-core-dev
2802017-11-09T14:03:51 *** promag has joined #bitcoin-core-dev
2812017-11-09T14:19:03 *** nemgun has joined #bitcoin-core-dev
2822017-11-09T14:19:11 *** nemgun has quit IRC
2832017-11-09T14:20:42 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/77ba4bf960d3...99ec12666ba7
2842017-11-09T14:20:42 <bitcoin-git> bitcoin/master 6c4042a Eelis: Assert that CWallet::SyncMetaData finds oldest transaction....
2852017-11-09T14:20:43 <bitcoin-git> bitcoin/master 99ec126 Wladimir J. van der Laan: Merge #11074: Assert that CWallet::SyncMetaData finds oldest transaction....
2862017-11-09T14:21:08 <bitcoin-git> [bitcoin] laanwj closed pull request #11074: Assert that CWallet::SyncMetaData finds oldest transaction. (master...syncassert) https://github.com/bitcoin/bitcoin/pull/11074
2872017-11-09T14:27:50 *** promag has quit IRC
2882017-11-09T14:30:11 *** quantbot_ has joined #bitcoin-core-dev
2892017-11-09T14:30:11 *** shesek has joined #bitcoin-core-dev
2902017-11-09T14:30:11 *** quantbot has quit IRC
2912017-11-09T14:30:11 *** shesek has quit IRC
2922017-11-09T14:30:11 *** shesek has joined #bitcoin-core-dev
2932017-11-09T14:31:35 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2942017-11-09T14:40:41 *** Drakon_ has joined #bitcoin-core-dev
2952017-11-09T14:41:55 <bitcoin-git> [bitcoin] morcos closed pull request #9447: Allow 2 simultaneous block downloads (master...doubledownload) https://github.com/bitcoin/bitcoin/pull/9447
2962017-11-09T14:42:12 <Drakon_> I'd like to provide a (feature) suggestion. Should I address at #bitcoin in order to do so?
2972017-11-09T14:43:31 <luke-jr> sounds like a good place to start
2982017-11-09T14:43:52 *** CubicEar_ has quit IRC
2992017-11-09T14:45:44 <wumpus> yes, this is not the place for feature suggestions, unless you're planning to implement it yourself and having questions about how to do so
3002017-11-09T14:51:38 <Drakon_> This isn't my current intention, at least not at the moment. So where to address my suggestion?
3012017-11-09T14:52:01 *** vicenteH has quit IRC
3022017-11-09T14:52:09 *** vicenteH has joined #bitcoin-core-dev
3032017-11-09T14:54:33 <wumpus> #bitcoin as suggested
3042017-11-09T14:57:26 <Drakon_> Well sorry, but I'm a little bit confuse since you wrote "this is not the place for feature suggestions ..."
3052017-11-09T14:58:17 <luke-jr> this isn't #bitcoin
3062017-11-09T14:58:46 <Drakon_> Well sorry, I messed this up.
3072017-11-09T15:02:21 <bitcoin-git> [bitcoin] BitonicEelis opened pull request #11643: Remove dead store in secp256k1_ecmult_gen. (master...deadstore) https://github.com/bitcoin/bitcoin/pull/11643
3082017-11-09T15:07:31 <bitcoin-git> [bitcoin] fanquake closed pull request #11643: Remove dead store in secp256k1_ecmult_gen. (master...deadstore) https://github.com/bitcoin/bitcoin/pull/11643
3092017-11-09T15:09:54 *** clarkmoody has quit IRC
3102017-11-09T15:30:06 *** btcdrak has quit IRC
3112017-11-09T15:34:41 <BlueMatt> cfields: re: #11562: I believe using high_resolution_clock is incorrect - seems like high_resolution_clock::is_steady is rarely true
3122017-11-09T15:34:43 <gribble> https://github.com/bitcoin/bitcoin/issues/11562 | bench: use std::chrono rather than gettimeofday by theuni · Pull Request #11562 · bitcoin/bitcoin · GitHub
3132017-11-09T15:35:11 <BlueMatt> I mean or we can do something like this: https://gist.github.com/kballard/3549291#file-benchmark-hpp-L8
3142017-11-09T15:37:51 <BlueMatt> cfields: we should be preferring steady_clock over high_resolution, I think, and then we can static_assert something about the resolution being at least microsecond or so...
3152017-11-09T15:39:12 <BlueMatt> also, master dont build, yo
3162017-11-09T15:39:54 *** Drakon_ has quit IRC
3172017-11-09T15:43:46 <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11644: Fix qt build broken by 5a5e4e9 (master...2017-11-fix-build) https://github.com/bitcoin/bitcoin/pull/11644
3182017-11-09T15:51:02 *** Chris_Stewart_5 has quit IRC
3192017-11-09T15:52:43 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3202017-11-09T15:54:16 *** StopAndDecrypt_ has joined #bitcoin-core-dev
3212017-11-09T15:55:07 *** StopAndDecrypt has quit IRC
3222017-11-09T15:58:48 <wumpus> BlueMatt: I also commented about that on the original PR
3232017-11-09T15:59:09 <wumpus> apparently the steady clock is usually the same resolution as the high resolution clock
3242017-11-09T16:00:08 <wumpus> this just handles the rare case where the high resolution clock is higher resolution (but not steady) in which case a higher resolution is probably preferred
3252017-11-09T16:00:12 <BlueMatt> wumpus: indeed, but it seems nonsense to prefer high_resolution over steady *unless* their resolution is the same
3262017-11-09T16:00:26 <BlueMatt> really? I mean its not like any of our runs require *that* much precision
3272017-11-09T16:00:36 <wumpus> I don't think I agree on that, for benchmarks precision is always preferred
3282017-11-09T16:00:43 <BlueMatt> microsecond is more than enough, even millisecond is probably fine especially after the next pr
3292017-11-09T16:01:13 <wumpus> I mean the difference is that the steady clock isn't affected by time changes, but those should be rare anyhow right?
3302017-11-09T16:01:27 <BlueMatt> but precision is nonsense if you're running ntp - the chance that your clock is running fast/slow randomly is not 0 and the gain you get from microsecond to something smaller is ~0
3312017-11-09T16:01:57 *** JackH has quit IRC
3322017-11-09T16:02:16 <wumpus> running benchmarks on a system where the time is jumping crazy around sounds like a stupid idea to me
3332017-11-09T16:02:35 <BlueMatt> most systems have ntpd, though....
3342017-11-09T16:02:43 <BlueMatt> I think its like built-in to systemd or some batshit insane shit now
3352017-11-09T16:02:45 <wumpus> ntp is supposed to increase time precision, not decrease it
3362017-11-09T16:03:25 <wumpus> e.g. it explicitly doesn't do any large sudden corrections
3372017-11-09T16:03:53 <BlueMatt> but it does corrections by making your clock run fast/slow when it detects your clock to be off (or your network path to have changed.....)
3382017-11-09T16:04:04 <wumpus> that's the point, yes
3392017-11-09T16:04:52 <MarcoFalke> I read that as a point for the steady_clock
3402017-11-09T16:05:14 <Victorsueca> Came here to say it, but seems like you already noticed master is failing a lot lately
3412017-11-09T16:05:35 <wumpus> Victorsueca: a lot?
3422017-11-09T16:05:44 <BlueMatt> Victorsueca: usually master travis failures are cause travis will cancel a job if you push something new on top of it, so github shows them as failed
3432017-11-09T16:05:51 <MarcoFalke> what do you mean? The tests?
3442017-11-09T16:05:54 <BlueMatt> though master is actually failing right now, but its the first I've seen that in months
3452017-11-09T16:05:57 <wumpus> these kind of merge conficts are incredibly rare
3462017-11-09T16:06:11 <Victorsueca> BlueMatt: ahh that explains it
3472017-11-09T16:06:13 <wumpus> currently testing BlueMatt's change
3482017-11-09T16:06:49 <sipa> far better to have it fail to compile/test than have bugs
3492017-11-09T16:07:01 <BlueMatt> Victorsueca: I often restart them cause I'm super ocd, though I should probably stop doing that cause it stops testing other things......
3502017-11-09T16:07:15 <wumpus> absolutely
3512017-11-09T16:08:21 <MarcoFalke> I mean we have a backlog anyway and that motivates people to compile and run locally
3522017-11-09T16:08:30 <MarcoFalke> So I don't see huge issues with that
3532017-11-09T16:08:34 <BlueMatt> yea, we almost always have a backlog during business hours :/
3542017-11-09T16:08:43 * BlueMatt works on weekends, suckers :p
3552017-11-09T16:10:28 <BlueMatt> wumpus: eg https://github.com/coreos/bugs/issues/391 which talks about how, yet again, systemd be breaking shit, in this case cause its timesyncd (which will now be default, I guess, on most hosts) is not accurate enough for ceph
3562017-11-09T16:10:46 <wumpus> BlueMatt: yes thinking about it some more I agree with you
3572017-11-09T16:10:57 <BlueMatt> given steady_clock usually has very good precision and the point of benchmarks is usually to figure out if things changed from one commit to another, not to compare between hosts, I think we should prefer that
3582017-11-09T16:13:51 <wumpus> yes, indeed
3592017-11-09T16:14:07 <BlueMatt> k, willfix
3602017-11-09T16:14:29 <wumpus> it also simplifies the code if we always use the same clock
3612017-11-09T16:15:21 *** JackH has joined #bitcoin-core-dev
3622017-11-09T16:17:34 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/99ec12666ba7...045a80923419
3632017-11-09T16:17:34 <bitcoin-git> bitcoin/master 9e9e31a Matt Corallo: Fix qt build broken by 5a5e4e9
3642017-11-09T16:17:34 <bitcoin-git> bitcoin/master 045a809 Wladimir J. van der Laan: Merge #11644: Fix qt build broken by 5a5e4e9...
3652017-11-09T16:18:08 <bitcoin-git> [bitcoin] laanwj closed pull request #11644: Fix qt build broken by 5a5e4e9 (master...2017-11-fix-build) https://github.com/bitcoin/bitcoin/pull/11644
3662017-11-09T16:21:01 *** jb55 has quit IRC
3672017-11-09T16:33:19 *** ghost43 has quit IRC
3682017-11-09T16:33:51 *** ghost43 has joined #bitcoin-core-dev
3692017-11-09T16:36:56 *** jimmymow has joined #bitcoin-core-dev
3702017-11-09T16:39:02 *** quantbot_ has quit IRC
3712017-11-09T16:40:58 *** jimmymow has quit IRC
3722017-11-09T16:44:24 *** Giszmo has quit IRC
3732017-11-09T16:45:01 *** lukedashjr has joined #bitcoin-core-dev
3742017-11-09T16:46:05 *** luke-jr has quit IRC
3752017-11-09T16:49:30 *** lukedashjr is now known as luke-jr
3762017-11-09T16:50:14 <bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11646: Require a steady clock for bench with at least micro precision (master...2017-11-11562-cleanups) https://github.com/bitcoin/bitcoin/pull/11646
3772017-11-09T16:51:17 *** Chris_Stewart_5 has quit IRC
3782017-11-09T16:52:35 *** nickler has quit IRC
3792017-11-09T16:54:05 *** LumberCartel has quit IRC
3802017-11-09T16:57:57 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3812017-11-09T16:59:18 *** nickler has joined #bitcoin-core-dev
3822017-11-09T17:03:48 *** Giszmo has joined #bitcoin-core-dev
3832017-11-09T17:10:18 *** BashCo has quit IRC
3842017-11-09T17:10:57 *** BashCo has joined #bitcoin-core-dev
3852017-11-09T17:12:19 <BlueMatt> wumpus: hmmm, re: #11583 I kinda feel yucky adding a BCLog category that just means "ALWAYS log" - would you be ok with a #define function which does the LogPrint/LogPrintf call based on pnode->fInbound?
3862017-11-09T17:12:20 <gribble> https://github.com/bitcoin/bitcoin/issues/11583 | Do not make it trivial for inbound peers to generate log entries by TheBlueMatt · Pull Request #11583 · bitcoin/bitcoin · GitHub
3872017-11-09T17:13:45 <wumpus> BlueMatt: I kind of like the idea of having a always-log category
3882017-11-09T17:14:08 <wumpus> BlueMatt: it means LogPrintf could be defined in terms of it, and at some point only one log function would be needed anymore
3892017-11-09T17:14:35 <wumpus> myself I always get confused between Logprint and Logprintf also because they are named so similarly
3902017-11-09T17:14:44 <BlueMatt> true.....
3912017-11-09T17:14:57 <BlueMatt> man i hate having a one-of-these-things-is-not-like-the-other enum :(
3922017-11-09T17:15:05 *** BashCo has quit IRC
3932017-11-09T17:15:14 <wumpus> well there is already a ::ALL
3942017-11-09T17:15:38 <BlueMatt> yea, but at least thats just defined to ~0
3952017-11-09T17:15:40 <wumpus> maybe we could use that as "log always"?
3962017-11-09T17:16:16 <wumpus> it doesn't really matter what it's defined to, just how it's handled :)
3972017-11-09T17:16:19 <BlueMatt> hmmmm, I thought about that briefly but decided I prefer an ::ALWAYS cause then you're even more confused....-debug=0 means ~0 still logs?
3982017-11-09T17:16:30 <BlueMatt> even though ~0 & 1 doesnt?
3992017-11-09T17:16:38 <BlueMatt> errr, ~0 ^ 1
4002017-11-09T17:16:48 <wumpus> hrm yeah
4012017-11-09T17:17:10 <wumpus> can't we just move those messages always to ::NET :-)
4022017-11-09T17:17:11 <BlueMatt> alright, I'll take a dive down the ::ALWAYS rabbit hole and see where I end up
4032017-11-09T17:17:19 <wumpus> that would remove this entire issue
4042017-11-09T17:17:36 <BlueMatt> I mean its nice to know when your outbound peers succeed in connecting
4052017-11-09T17:17:37 <wumpus> I mean they *are* net messages
4062017-11-09T17:17:41 <BlueMatt> I could add a second log for that
4072017-11-09T17:17:50 <wumpus> yes
4082017-11-09T17:17:53 <wumpus> maybe that's better
4092017-11-09T17:18:01 <BlueMatt> ok, fine, will table the ::ALWAYS discussion
4102017-11-09T17:18:11 *** jb55 has joined #bitcoin-core-dev
4112017-11-09T17:19:04 <wumpus> the root issue really is that we confound log class and log priority
4122017-11-09T17:19:36 <wumpus> but I don't think we need to make logging perfect before merging your PR :)
4132017-11-09T17:21:39 <wumpus> but I agree with you that BCLog::ALWAYS is ugly
4142017-11-09T17:22:08 <wumpus> would prefer to add BCLog::ERROR BCLog::WARNING BCLog::DEBUG
4152017-11-09T17:22:47 <wumpus> then the log system would show messages based on a threshold
4162017-11-09T17:23:10 <wumpus> and it's not decided at the site of logigng whether something should always show
4172017-11-09T17:23:23 <BlueMatt> I mean I dunno, I kinda like the idea of logging based on subsystem, especially with rpc to turn them on and off - it lets you debug just the subsystem that is acting up
4182017-11-09T17:23:34 <wumpus> the subsystem should certainly stay
4192017-11-09T17:23:34 <BlueMatt> we could add both
4202017-11-09T17:23:36 * BlueMatt ducks
4212017-11-09T17:23:57 <wumpus> common is to have a combination of both
4222017-11-09T17:24:08 <BlueMatt> that sounds overcomplex
4232017-11-09T17:24:13 <BlueMatt> but, eh...whatever
4242017-11-09T17:24:23 <wumpus> it's pretty much how it's done in all software
4252017-11-09T17:24:24 <BlueMatt> a discussion for when someone actually goes and writes the code to change it :p
4262017-11-09T17:24:32 <wumpus> so you can select by category or by priority
4272017-11-09T17:25:10 <wumpus> so this would be either a low priority or high priority net message based on incoming/outgoing
4282017-11-09T17:26:40 <wumpus> it also means that the log output can show the category, so you can grep for it later
4292017-11-09T17:30:08 *** laurentmt has quit IRC
4302017-11-09T17:31:04 <wumpus> (because all log messages will have a category, not just the debug priority ones)
4312017-11-09T17:32:54 *** xinxi has quit IRC
4322017-11-09T17:33:27 *** xinxi has joined #bitcoin-core-dev
4332017-11-09T17:43:37 *** Giszmo has quit IRC
4342017-11-09T17:53:04 *** Giszmo has joined #bitcoin-core-dev
4352017-11-09T17:54:43 *** timothy has quit IRC
4362017-11-09T17:57:52 *** Provoostenator has joined #bitcoin-core-dev
4372017-11-09T18:06:57 *** m8tion has quit IRC
4382017-11-09T18:11:23 *** laurentmt has joined #bitcoin-core-dev
4392017-11-09T18:11:29 *** laurentmt has quit IRC
4402017-11-09T18:14:36 *** Deacydal has joined #bitcoin-core-dev
4412017-11-09T18:15:33 *** Deacyde has quit IRC
4422017-11-09T18:21:04 *** LumberCartel has joined #bitcoin-core-dev
4432017-11-09T18:27:27 *** jb55 has quit IRC
4442017-11-09T18:29:48 <cfields> BlueMatt / wumpus: after thinking on it a bit, i agree with the clock change.
4452017-11-09T18:35:06 *** ExtraCrispy has quit IRC
4462017-11-09T18:35:54 *** bule has joined #bitcoin-core-dev
4472017-11-09T18:41:28 <wumpus> cfields: awesome
4482017-11-09T18:45:06 <Chris_Stewart_5> meeting in 15 right?
4492017-11-09T18:45:23 *** jb55 has joined #bitcoin-core-dev
4502017-11-09T18:46:56 <wumpus> yes
4512017-11-09T18:51:57 <bitcoin-git> [bitcoin] MarcoFalke pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/045a80923419...5e3f5e4f25b6
4522017-11-09T18:51:58 <bitcoin-git> bitcoin/master 2904e30 John Newbery: [tests] Remove dead code from mininode.py...
4532017-11-09T18:51:58 <bitcoin-git> bitcoin/master c0b1274 John Newbery: [tests] Remove support for bre-BIP31 ping messages...
4542017-11-09T18:51:59 <bitcoin-git> bitcoin/master 3858aab John Newbery: [tests] Remove support for p2p alert messages...
4552017-11-09T18:52:27 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #11638: [tests] Dead mininode code (master...dead_mininode_code) https://github.com/bitcoin/bitcoin/pull/11638
4562017-11-09T18:55:05 *** meshcollider has joined #bitcoin-core-dev
4572017-11-09T18:56:12 *** promag has joined #bitcoin-core-dev
4582017-11-09T18:57:27 <promag> hi
4592017-11-09T18:57:45 <jonasschnelli> o/
4602017-11-09T18:58:27 <bitcoin-git> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/5e3f5e4f25b6...1f4375f8e75f
4612017-11-09T18:58:28 <bitcoin-git> bitcoin/master 3788a84 Matt Corallo: Do not send (potentially) invalid headers in response to getheaders...
4622017-11-09T18:58:28 <bitcoin-git> bitcoin/master 725b79a Russell Yanofsky: [test] Verify node doesn't send headers that haven't been fully validated
4632017-11-09T18:58:29 <bitcoin-git> bitcoin/master 1f4375f Wladimir J. van der Laan: Merge #11580: Do not send (potentially) invalid headers in response to getheaders...
4642017-11-09T18:58:53 <bitcoin-git> [bitcoin] laanwj closed pull request #11580: Do not send (potentially) invalid headers in response to getheaders (master...2017-10-getheaders-valid-only) https://github.com/bitcoin/bitcoin/pull/11580
4652017-11-09T19:01:20 <sipa> meetung?
4662017-11-09T19:01:30 <jonasschnelli> jup
4672017-11-09T19:01:35 <achow101> meeting
4682017-11-09T19:02:18 <wumpus> #startmeeting
4692017-11-09T19:02:18 <lightningbot> Meeting started Thu Nov 9 19:02:18 2017 UTC. The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot.
4702017-11-09T19:02:18 <lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
4712017-11-09T19:02:21 <MarcoFalke> proposed short topic "Signing key for gitian executables"
4722017-11-09T19:02:27 <meshcollider> Hi
4732017-11-09T19:02:31 <achow101> hi
4742017-11-09T19:02:34 <wumpus> #bitcoin-core-dev Meeting: wumpus sipa gmaxwell jonasschnelli morcos luke-jr btcdrak sdaftuar jtimon cfields petertodd kanzure bluematt instagibbs phantomcircuit codeshark michagogo marcofalke paveljanik NicolasDorier jl2012 achow101 meshcollider jnewbery maaku fanquake promag
4752017-11-09T19:02:34 <Provoostenator> Hi
4762017-11-09T19:02:42 <sdaftuar> oh hi
4772017-11-09T19:02:50 <cfields> hi
4782017-11-09T19:02:52 <morcos> hi
4792017-11-09T19:03:04 <wumpus> #topic 0.15.1
4802017-11-09T19:03:05 <instagibbs> hi
4812017-11-09T19:03:13 <morcos> Release!
4822017-11-09T19:03:15 <sdaftuar> does it work?
4832017-11-09T19:03:15 <wumpus> anyone had any bug reports regarding the rc?
4842017-11-09T19:03:22 <BlueMatt> Release!
4852017-11-09T19:03:25 <instagibbs> I have not seen any...
4862017-11-09T19:03:33 <MarcoFalke> release notes missing?
4872017-11-09T19:03:36 *** promag has quit IRC
4882017-11-09T19:03:38 <wumpus> seems that was a short rc cycle then
4892017-11-09T19:03:43 <achow101> I haven't seen any, but I also don't know how many people are testing it out
4902017-11-09T19:03:50 <sipa> yes, i think we need a writeup on the P2P changes at least
4912017-11-09T19:03:50 <wumpus> MarcoFalke: no? I think we have them?
4922017-11-09T19:03:57 <meshcollider> MarcoFalke I wrote release notes and wumpus already merged
4932017-11-09T19:04:02 *** promag has joined #bitcoin-core-dev
4942017-11-09T19:04:03 <MarcoFalke> great
4952017-11-09T19:04:09 <MarcoFalke> Tag and release?
4962017-11-09T19:04:16 <BlueMatt> there's no release notes on the p2p changes, I think
4972017-11-09T19:04:18 <BlueMatt> as sipa points out
4982017-11-09T19:04:21 <sdaftuar> yes there are some
4992017-11-09T19:04:22 <morcos> yeah i think actually we might as well not release yet, there is no big rush now, so might as well see if any bugs pop up?
5002017-11-09T19:04:22 <BlueMatt> though that may be fine
5012017-11-09T19:04:28 <cfields> i suspect many of the people who might've usually been testing rc1 got stuck dealing with drama instead :(
5022017-11-09T19:04:32 <wumpus> I don't think we should hold up a minor on release notes tbh, unless something really important is missing\
5032017-11-09T19:05:21 <luke-jr> morcos: I'm not sure we should drop our guard so easily
5042017-11-09T19:05:23 <achow101> morcos: there's still a possibility that some miner goes ahead and forks anyways
5052017-11-09T19:05:28 <BlueMatt> we can tag an rc2 with no changes to encourage testing :p
5062017-11-09T19:05:29 <wumpus> if it's ready we should just release and move on
5072017-11-09T19:05:38 <achow101> like these guys: https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000689.html
5082017-11-09T19:05:39 <BlueMatt> but, yea, I think we should release
5092017-11-09T19:05:42 <jonasschnelli> ack
5102017-11-09T19:05:44 <meshcollider> Hmm did I miss something? I thought I wrote up
5112017-11-09T19:05:52 <BlueMatt> even the idiots running a few hundred btc1 nodes may cause disruption and 15.1 can help
5122017-11-09T19:05:55 <luke-jr> achow101: in fact, at least one mining pool has announced they intend to
5132017-11-09T19:06:09 <meshcollider> ACK on release though, can just do 0.15.1.1 if it's got a bug ;)
5142017-11-09T19:06:13 <sdaftuar> lol
5152017-11-09T19:06:15 <wumpus> yes would be a waste if we get disruption anyway
5162017-11-09T19:06:20 <BlueMatt> meshcollider: god damn it
5172017-11-09T19:06:23 <wumpus> because some people fork anyway
5182017-11-09T19:06:24 <sipa> meshcollider: oh, i missed those notes!
5192017-11-09T19:06:37 <Provoostenator> This being Bitcoin, _someone_ is going to fork...
5202017-11-09T19:06:38 * BlueMatt proposes from here on out all version numbers must be majorversion.some.series.of.0s.and.1s :p
5212017-11-09T19:06:41 <wumpus> and we have a release ready but decide to delay it because 'no rush'
5222017-11-09T19:06:42 <morcos> ok ok.. i have no problem releasing
5232017-11-09T19:06:50 <luke-jr> meshcollider: if we make 0.15.2 another bugfix-only, we can do segwit wallet in 0.15.pi
5242017-11-09T19:06:55 <sdaftuar> release!
5252017-11-09T19:06:59 <kanzure> hi.
5262017-11-09T19:06:59 <wumpus> ok!
5272017-11-09T19:07:01 <BlueMatt> Relese!
5282017-11-09T19:07:04 <BlueMatt> e
5292017-11-09T19:07:08 <wumpus> #action release 0.15.1
5302017-11-09T19:07:11 <achow101> ack release
5312017-11-09T19:07:18 <wumpus> #topic HIgh priority for review
5322017-11-09T19:07:32 <wumpus> I think https://github.com/bitcoin/bitcoin/projects/8 is stale now
5332017-11-09T19:07:55 *** BashCo has joined #bitcoin-core-dev
5342017-11-09T19:08:02 <achow101> so back to doing segwit wallet stuff?
5352017-11-09T19:08:07 *** Deacydal has quit IRC
5362017-11-09T19:08:07 <wumpus> the blockers were those that were already there before we started working on 0.15.1, so probably needs a update
5372017-11-09T19:08:14 <wumpus> achow101: yes
5382017-11-09T19:08:25 <wumpus> we should at least have segwit wallet in 0.16.0
5392017-11-09T19:08:34 *** Deacydal has joined #bitcoin-core-dev
5402017-11-09T19:08:40 <sipa> yes
5412017-11-09T19:08:49 <jonasschnelli> Yes. SW wallet support should be in projects/8
5422017-11-09T19:08:54 <morcos> sipa: did you ever write up that document?
5432017-11-09T19:08:54 <meshcollider> C.f. #11403
5442017-11-09T19:08:57 <gribble> https://github.com/bitcoin/bitcoin/issues/11403 | SegWit wallet support by sipa · Pull Request #11403 · bitcoin/bitcoin · GitHub
5452017-11-09T19:08:57 <BlueMatt> speaking of segwit wallet......sipa where are we?
5462017-11-09T19:09:01 <sipa> no, sorry, distracted
5472017-11-09T19:09:07 <sipa> been thinking a lot about it though...
5482017-11-09T19:09:12 <morcos> i don't think i had any concerns about the last plan as i understood it.. but would be nice to sort of have it written out
5492017-11-09T19:09:22 <wumpus> added
5502017-11-09T19:09:26 <sipa> agree, i'll try to write things up today
5512017-11-09T19:09:49 <morcos> have we decided that barring bugs, the next release will be 0.16 with segwit wallet?
5522017-11-09T19:09:51 <achow101> is 11403 all that's left for segwit wallet? (besides the fact that it is the segwit wallet PR)
5532017-11-09T19:10:01 <morcos> and then the new and improved segwit wallet will be left for 0.1&?
5542017-11-09T19:10:04 <morcos> 0.17
5552017-11-09T19:10:05 <sipa> achow101: there are some TODOs left
5562017-11-09T19:10:20 <wumpus> morcos: I think that's sensible
5572017-11-09T19:10:21 <sipa> morcos: i'm going to stop thinking in terms of specific releases
5582017-11-09T19:10:25 <jonasschnelli> morcos: makes sense
5592017-11-09T19:10:31 * BlueMatt was concerned about the approach but there's lots of tradeoffs, so really wanted to see the aforementioned doc
5602017-11-09T19:10:32 <wumpus> just do an early 0.16 release if it's finished early
5612017-11-09T19:10:47 <sipa> but short term, 11403 + its todos
5622017-11-09T19:10:52 <morcos> wumpus: yes thats what i mean.. ok good.
5632017-11-09T19:10:52 <wumpus> I'm kind of tired of holding off changes because backports to 0.15 need to be easier
5642017-11-09T19:10:55 <sipa> long term, rework ismine etc
5652017-11-09T19:11:08 <sipa> and release whatever is ready
5662017-11-09T19:11:32 <MarcoFalke> wumpus: Are we still doing a 0.15 with segwit wallet?
5672017-11-09T19:11:49 <wumpus> MarcoFalke: no, I don't think so (or at least that's what we discussed last meeting)
5682017-11-09T19:11:52 <cfields> ack 0.16 whenever segwit wallet is ready
5692017-11-09T19:11:56 <promag> sorry, multi wallet also for 0.16?
5702017-11-09T19:12:04 <sipa> multiwallet is in 0.15, no?
5712017-11-09T19:12:09 <meshcollider> Dynamic multiwallet?
5722017-11-09T19:12:11 <jonasschnelli> promag: if it's ready... you mean dynamic loading/unloading?
5732017-11-09T19:12:17 <promag> yes
5742017-11-09T19:12:24 <luke-jr> MarcoFalke: same plan, different versioning
5752017-11-09T19:12:25 <wumpus> if it's ready in time, sure
5762017-11-09T19:12:26 <jonasschnelli> promag: Should be possible
5772017-11-09T19:12:36 <wumpus> not going to hold it up on that though, if the explicit goal is segwit wallet
5782017-11-09T19:12:44 <promag> not project 8 thou?
5792017-11-09T19:12:49 <jonasschnelli> Indeed
5802017-11-09T19:12:54 <jonasschnelli> promag: it is there
5812017-11-09T19:13:02 <MarcoFalke> #action put segwit wallet in the next major release
5822017-11-09T19:13:21 <wumpus> yes, anything else for high priority for review?
5832017-11-09T19:13:44 <BlueMatt> #10286 :(
5842017-11-09T19:13:48 <gribble> https://github.com/bitcoin/bitcoin/issues/10286 | Call wallet notify callbacks in scheduler thread (without cs_main) by TheBlueMatt · Pull Request #10286 · bitcoin/bitcoin · GitHub
5852017-11-09T19:13:56 <jonasschnelli> I'd like to see BIP159 in 0.16... but it's already in the HP list
5862017-11-09T19:14:09 <BlueMatt> jonasschnelli: needs rebase and I left you comments :p
5872017-11-09T19:14:14 <wumpus> 10286 is already on there
5882017-11-09T19:14:34 <meshcollider> Any label stuff to replace accounts in there?
5892017-11-09T19:14:35 <sipa> bip159 would be nice, indeed
5902017-11-09T19:14:37 <jonasschnelli> BlueMatt: yes. Saw that.. will work on it asap
5912017-11-09T19:14:56 * jonasschnelli has 14.4k connection this week
5922017-11-09T19:15:22 <promag> btw, I think it would be cool to have some diagram of the current thread model and what should be the ideal model
5932017-11-09T19:15:36 <wumpus> thread model?
5942017-11-09T19:15:39 <promag> I think BlueMatt has some things in mind
5952017-11-09T19:15:57 <jonasschnelli> I think promag means the general concurrency concept, right?
5962017-11-09T19:16:04 <promag> sure
5972017-11-09T19:16:25 <BlueMatt> promag: my model is CValidationInterface
5982017-11-09T19:16:26 <BlueMatt> :p
5992017-11-09T19:16:32 <promag> well BlueMatt keeps saying he wants to refactor in some way, but would be cool to actually "see" the big picture
6002017-11-09T19:16:37 <jonasschnelli> We move away from topics... MarcoFalke had a proposed topic
6012017-11-09T19:16:43 <BlueMatt> promag: CValidationInterface :p
6022017-11-09T19:16:57 <meshcollider> Signing keys for binaries?
6032017-11-09T19:16:58 <morcos> promag: +1
6042017-11-09T19:17:32 <jonasschnelli> [09:02:17] <MarcoFalke> proposed short topic "Signing key for gitian executables"
6052017-11-09T19:17:38 <wumpus> #topic Signing key for gitian executables (MarcoFalke)
6062017-11-09T19:17:43 <MarcoFalke> Background is that the current key expires Q1 2018, so we should come up with something for the 0.16 release. Someone had the idea to ask MIT to apply for a key, as individuals can not apply AFAICT.
6072017-11-09T19:17:49 <jonasschnelli> can you elaborate MarcoFalke?
6082017-11-09T19:18:04 <jonasschnelli> MarcoFalke: you mean the Apple/WINDOWS code signing keys?
6092017-11-09T19:18:08 <BlueMatt> MarcoFalke: there was some discussion of doing a split rsa key here.... gmaxwell around?
6102017-11-09T19:18:12 <MarcoFalke> jonasschnelli: jup
6112017-11-09T19:18:13 <luke-jr> would be good to have a key that is explicitly used for not only Core releases (eg, Knots too)
6122017-11-09T19:18:15 <jonasschnelli> Apple is still the Bitcoin Foundatiomn, right?
6132017-11-09T19:18:23 <gmaxwell> BlueMatt: I have code for mpc generation of rsa keys and signing.
6142017-11-09T19:18:24 <MarcoFalke> BlueMatt: That would require some more time?
6152017-11-09T19:18:30 <jonasschnelli> luke-jr: no, only Core
6162017-11-09T19:18:34 <luke-jr> jonasschnelli: why?
6172017-11-09T19:18:41 <cfields> yes, both are btcf atm
6182017-11-09T19:18:42 <BlueMatt> luke-jr: no
6192017-11-09T19:18:49 <gmaxwell> BlueMatt: (by I have, I mean it's on github, and I've used it... works fine)
6202017-11-09T19:19:07 <jonasschnelli> luke-jr: its about trust... I don't know if I would sign something I havev't reviewd
6212017-11-09T19:19:31 <cfields> gmaxwell: deals well with csr? I have no idea if that complicates things.
6222017-11-09T19:19:55 <achow101> the windows cert expires in 2019
6232017-11-09T19:19:57 <jonasschnelli> MarcoFalke: individuals can apply for keys (Apple and Windows)
6242017-11-09T19:20:02 <jonasschnelli> But not sure if we should do individuals...
6252017-11-09T19:20:03 <instagibbs> jonasschnelli, mmm not sure if gitian is about you "trusting" the binary, so much as it matches others'?
6262017-11-09T19:20:06 <gmaxwell> cfields: it deals with RSA numbers, someone would need to do the hacking to stuff the rsa number it generates into a CSR and whatnot.
6272017-11-09T19:20:27 <cfields> gmaxwell: ok
6282017-11-09T19:20:48 <luke-jr> jonasschnelli: I see it as dealing with backward OS policies that make it hard for users to run stuff.
6292017-11-09T19:20:55 <morcos> Does anyone think its best to just get BTCF to renew for now?
6302017-11-09T19:21:02 <gmaxwell> I think it's _really_ unfortunate to have any name except the project name on the binaries, causes a drama and stupidity. There are still people that think the bitcoin foundation controls bitcoin just because of that existing cert. :(
6312017-11-09T19:21:02 <wumpus> luke-jr: it basically is
6322017-11-09T19:21:02 <BlueMatt> todo: cfields creates an rsa # -> csr program :p
6332017-11-09T19:21:12 <gmaxwell> morcos: thats the obvious thing to do.
6342017-11-09T19:21:18 <jonasschnelli> luke-jr: yes. But applying for you own key is maybe 300USD/year,.... so possible IMO
6352017-11-09T19:21:33 <BlueMatt> gmaxwell: so can I just legally change my name to Bitcoin Core, get a cert, and then change it back?
6362017-11-09T19:21:34 <BlueMatt> :p
6372017-11-09T19:21:40 <jonasschnelli> morcos: renaming with the APPLE Developer Portal is almost impossible
6382017-11-09T19:21:43 <achow101> BlueMatt: lol
6392017-11-09T19:21:45 <meshcollider> lol
6402017-11-09T19:21:57 <morcos> jonasschnelli: huh?
6412017-11-09T19:21:58 <jonasschnelli> changing name requires legal documents, etc.
6422017-11-09T19:22:03 <gmaxwell> BlueMatt: well the other option is that we just register a bitcoin core org someplace and have it get the key. But I wouldn't want to suggest that for a key that is expiring soon.
6432017-11-09T19:22:11 <jonasschnelli> It's all by approval basis through apple
6442017-11-09T19:22:16 <gmaxwell> it's not terribly hard, just requires a bit of money.
6452017-11-09T19:22:19 <jonasschnelli> you need a D.U.N.S number as well
6462017-11-09T19:22:21 <BlueMatt> I mean it doesnt take long to create an LLC that holds $0
6472017-11-09T19:22:34 <kanzure> would chaincode do it?
6482017-11-09T19:22:44 <jonasschnelli> But plase... don't set up an orga called "Bitcoin Core"
6492017-11-09T19:22:57 <meshcollider> Then bitcoin core really would be a company and you'd set off all the conspiracy theorists
6502017-11-09T19:22:57 <wumpus> jonasschnelli: agree
6512017-11-09T19:22:58 <gmaxwell> Bitcoin Core Code Signing Key inc.
6522017-11-09T19:22:58 <morcos> I'm happy to have an official Bitcoin Core org established if we want that, but it does seem like there are downsides to that
6532017-11-09T19:23:07 <wumpus> gmaxwell: yeah
6542017-11-09T19:23:12 <jonasschnelli> Id rather use an individual then ChainCodeLabs for it's own protection
6552017-11-09T19:23:13 <morcos> unless we specifically limited its purpose very narrowly
6562017-11-09T19:23:18 <cfields> ugh
6572017-11-09T19:23:23 <kanzure> yes if it's a "bitoin core org" then it should be named "bitcoin core code signing key holding only and nothing else, llc."
6582017-11-09T19:23:24 <luke-jr> wumpus: jonasschnelli: then I see no reason not to use a common key for both Core and Knots..
6592017-11-09T19:23:24 <wumpus> CoreSign
6602017-11-09T19:23:40 <jonasschnelli> I could provide my own personal APPL key...
6612017-11-09T19:23:43 * BlueMatt votes for someone to just create Bitcoin Core Code Signing, LLC
6622017-11-09T19:23:44 <gmaxwell> Bitcoin Release signing key incorporated.
6632017-11-09T19:23:46 <achow101> BTW the apple key expires Jan 11 2018, Windows March 5 2019, so we would need to do this soon
6642017-11-09T19:23:50 <morcos> luke-jr: stop.. please bring up knots later . it has nothing to do with the Core meeting
6652017-11-09T19:23:56 <jonasschnelli> (OSX only)
6662017-11-09T19:24:11 <jonasschnelli> heh
6672017-11-09T19:24:17 <gmaxwell> achow101: or just renew the apple one then, and continue on with doing something sensible.
6682017-11-09T19:24:32 <cfields> ok, in parallel to whatever else, I'll work on trying to get our current apple cert renewed
6692017-11-09T19:24:41 <wumpus> makes sense
6702017-11-09T19:24:43 <morcos> cfields: i think it makes most sense to do that.
6712017-11-09T19:25:11 <wumpus> any name would give conspiracy theories anyway, I don't really think it's so bad to have TBF as signing organization
6722017-11-09T19:25:14 <Provoostenator> Or Gitan Code Signing LLC, if other projects want their stuff signed too?
6732017-11-09T19:25:19 <gmaxwell> If someone wants to work on stuffing rsa numbers into CSRs, I can show them out to use the RSA MPC code (have to remember it myself first, but it's not hard)
6742017-11-09T19:25:22 <cfields> but i think we need a plan b. no clue if the resources/accounts/etc. are still live and available
6752017-11-09T19:25:25 <luke-jr> Provoostenator: good idea
6762017-11-09T19:25:33 <jonasschnelli> I kinda like the idea of a "Bitcoin Core Code Signing Assoc."
6772017-11-09T19:25:37 <cfields> gmaxwell: yes, i'd very very much like to do that
6782017-11-09T19:25:42 <cfields> so i'll volunteer for that
6792017-11-09T19:25:49 <achow101> do we really need code signed binaries though?
6802017-11-09T19:25:55 <cfields> tired of 10hr builds and signing on my damn laptop
6812017-11-09T19:26:11 <gmaxwell> wumpus: well at least TBF isn't any _new_ conspiracy theories... though it does kinda suck. :)
6822017-11-09T19:26:19 <cfields> achow101: yea. necessary evil, im afraid
6832017-11-09T19:26:29 <luke-jr> achow101: some variants of Mac and Windows won't let users run unsigned stuff or something like that
6842017-11-09T19:26:33 <wumpus> yes, otherwise all virus scanners will trigger on it and such
6852017-11-09T19:26:37 <achow101> luke-jr: well that's annoying
6862017-11-09T19:26:49 <Provoostenator> As an aside: has any one ever tried submitting to the Mac App Store?
6872017-11-09T19:27:03 *** chjj has joined #bitcoin-core-dev
6882017-11-09T19:27:08 <jonasschnelli> Provoostenator: no.. we won't
6892017-11-09T19:27:35 <jonasschnelli> This means the binaries are under APPLs control
6902017-11-09T19:27:35 <jonasschnelli> Would someone disagree on founding a "Bitcoin Core Code Signing Association" based in Switzerland?...
6912017-11-09T19:27:44 <jonasschnelli> (we could just try and also follow the path of renewing the current cert)
6922017-11-09T19:27:49 <wumpus> jonasschnelli: no, would be great
6932017-11-09T19:27:58 <luke-jr> jonasschnelli: "Gitian Code Signing" would be better as Provoostenator suggested
6942017-11-09T19:28:05 <gmaxwell> jonasschnelli: sounds fine to me, whatever is the path of least resistance.
6952017-11-09T19:28:08 <wumpus> luke-jr: I think that makes the scope too wide
6962017-11-09T19:28:13 <gmaxwell> I'd rather not introduce a new word 'gitian' to users.
6972017-11-09T19:28:15 <morcos> Let's please leave whatever we do focused on Bitcoin Core
6982017-11-09T19:28:17 <BlueMatt> it should probably have "Bitcoin Core" in the name
6992017-11-09T19:28:25 <BlueMatt> jonasschnelli: yes, please register, thanks!
7002017-11-09T19:28:41 <MarcoFalke> #action Register "Bitcoin Core Code Signing Association"
7012017-11-09T19:28:44 <luke-jr> BlueMatt: then you'll whine that it can't be shared
7022017-11-09T19:28:51 <wumpus> luke-jr: I don't personally have a problem with signing knots executables, but making it soo general means we'll have a bureaucracy about what to sign blabla, and btw devrandom owns the name gitian :)
7032017-11-09T19:28:52 <sipa> and then we'd apply for code signing keys under that association's name, using the MPC RSA scheme?
7042017-11-09T19:28:53 <meshcollider> jonasschnelli: sounds good to me
7052017-11-09T19:29:05 <jonasschnelli> Okay... I'll let that happen and register with apple
7062017-11-09T19:29:05 <sipa> (or at least eventually)
7072017-11-09T19:29:13 <Provoostenator> Decentralized Code Signers LLC?
7082017-11-09T19:29:16 <wumpus> sipa: yes, at least eventually
7092017-11-09T19:29:17 <BlueMatt> luke-jr: I object to it being shared, it is not *that* hard for you to get your own cert for your own project.....
7102017-11-09T19:29:17 <gmaxwell> sipa: yes, thats the idea.
7112017-11-09T19:29:20 <jonasschnelli> sipa: not sure it that is possible with apples key enrolling process
7122017-11-09T19:29:27 <sipa> jonasschnelli: i don't see why not
7132017-11-09T19:29:27 <BlueMatt> sipa: yes
7142017-11-09T19:29:30 <cfields> wumpus: exactly. The question to ask is: would we want btc1 signed with the same key?
7152017-11-09T19:29:45 <jonasschnelli> I'll focus on the legal association stuff maybe someone can try to look into the MPC RSA sheme with apple OSX signing keys
7162017-11-09T19:29:45 <sipa> jonasschnelli: assuming all the plumbing work is done
7172017-11-09T19:29:46 <wumpus> cfields: right, no we don't :)
7182017-11-09T19:29:52 <luke-jr> BlueMatt: it's a waste of money to a bad corp and a waste of time, at the very least
7192017-11-09T19:29:52 <achow101> does anyone have a link to the rsa mpc thing?
7202017-11-09T19:29:54 <gmaxwell> I wouldn't want any of us us wasting time helping with an adversarial project.
7212017-11-09T19:29:57 <morcos> Guys, if you are signing code, you are responsible for that code. If we are signing it in the name of Bitcoin Core we are all taking responsibility. Please let's limit this discussion to the code we all work on together
7222017-11-09T19:30:09 <Provoostenator> Makes sense
7232017-11-09T19:30:13 <sipa> well, in the MPC setting, the group of signers would be fixed
7242017-11-09T19:30:17 <morcos> someone can always separately create a more general entity to sign other projects, but thats not related to Core
7252017-11-09T19:30:30 <sipa> the project should be signing the things that group of signers is jointly interested in signing
7262017-11-09T19:30:32 <wumpus> yeah it's typical scope creep
7272017-11-09T19:30:37 <gmaxwell> achow101: I'll give you the link after the meeting.
7282017-11-09T19:30:40 <kanzure> or bike shedding on name
7292017-11-09T19:30:42 <wumpus> let's sign the entire world :p
7302017-11-09T19:30:42 <cfields> gmaxwell: right. I was making the point that it would be impossible to draw the line unless core-specific.
7312017-11-09T19:30:45 <achow101> gmaxwell: k, thanks
7322017-11-09T19:31:14 <MarcoFalke> Any other topics?
7332017-11-09T19:31:21 <BlueMatt> promag: CValidationInterface is where you learn things from consensus code (ie from CChainState after 10279 or validation.cpp otherwise) - its also where you learn about mempool things but I have a branch which comes after 10286 that splits the interface up between the two to differentiate a little bit....wrt threading, CValidationInterface listeners all move into the scheduler, which means you dont have any deadlocking issues since
7342017-11-09T19:31:22 <BlueMatt> they're all just called async, this is mostly complete in 10286, but cleaning up the remaining few isnt too hard...thats pretty much it, there's not much to it...net/net_processing is a different issue, and is mostly around moving things from CNode to CNodeState and disconnecting those two things being so closely joined, but the threading issues there are less of the primary concern (except for cs_main being too heavily shared between
7352017-11-09T19:31:22 <BlueMatt> net_processing for mapNodeState and everything else)
7362017-11-09T19:31:28 <gmaxwell> it is unfortunate that e.g. knots has an uphill time there, it's a barrier to entry that shouldn't exist. But it's also not one we created.
7372017-11-09T19:31:37 <luke-jr> cfields: except Knots and Core have the same developers
7382017-11-09T19:31:38 <wumpus> gmaxwell: I agree
7392017-11-09T19:31:53 <cfields> luke-jr: as does btc1...
7402017-11-09T19:31:56 <sipa> luke-jr: they don't have the same maintainers
7412017-11-09T19:31:58 <luke-jr> cfields: hardly
7422017-11-09T19:32:35 <sipa> i don't think everyone who is interested in signing off on core releases is interested in doing the same work for knots - and perhaps the other way around
7432017-11-09T19:32:58 <cfields> luke-jr: i hope it's clear that I'm not trying to lump you in with an adversarial fork. Just making the point that the distinction in terms of signing is hard to draw.
7442017-11-09T19:32:59 <luke-jr> "We Just Codesign Stuff We Want, LLC" XD
7452017-11-09T19:33:15 <cfields> luke-jr: that's my end goal, actually
7462017-11-09T19:33:15 <jonasschnelli> Indeed
7472017-11-09T19:33:16 <jonasschnelli> It's one entity luke-jr
7482017-11-09T19:33:22 <wumpus> well adversarial versus consensus-compatible is easy to draw
7492017-11-09T19:33:24 <gmaxwell> there is another issue, I'm pretty sure that apple will not grant a key to "I sign random shit LLC"
7502017-11-09T19:33:35 <jonasschnelli> You can found a "Knots Code Signing Assoc"
7512017-11-09T19:33:36 <promag> thanks BlueMatt, I'll read that in a bit
7522017-11-09T19:33:38 <cfields> to create a body like Let's Encrypt, which attests to the fact that code -> binary.
7532017-11-09T19:34:04 <wumpus> cfields: that would be awesome
7542017-11-09T19:34:06 <luke-jr> cfields: well, how to stop malware from using it?
7552017-11-09T19:34:13 <achow101> cfields: well that's a whole separate thing which we can join once it exists :)
7562017-11-09T19:34:20 <wumpus> but it's outside the scope of the bitcoin core project
7572017-11-09T19:34:23 <wumpus> any other topics?
7582017-11-09T19:34:24 <cfields> luke-jr: deterministic malware would have to be welcome, unfortunately
7592017-11-09T19:34:51 <luke-jr> that'd just get the key revoked
7602017-11-09T19:34:55 <gmaxwell> not like this stuff actually stops malware, snake oil security. alas.
7612017-11-09T19:35:07 <gmaxwell> in any case, a discussion for another time.
7622017-11-09T19:36:11 <wumpus> ok, no other topics
7632017-11-09T19:36:19 <wumpus> #endmeeting
7642017-11-09T19:36:19 <lightningbot> Meeting ended Thu Nov 9 19:36:19 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
7652017-11-09T19:36:19 <lightningbot> Minutes: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-11-09-19.02.html
7662017-11-09T19:36:19 <lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-11-09-19.02.txt
7672017-11-09T19:36:19 <lightningbot> Log: http://www.erisian.com.au/meetbot/bitcoin-core-dev/2017/bitcoin-core-dev.2017-11-09-19.02.log.html
7682017-11-09T19:37:32 <achow101> well that was short
7692017-11-09T19:37:48 *** bule has quit IRC
7702017-11-09T19:38:06 <gmaxwell> achow101: the links are here https://github.com/kljensen/viff/blob/master/doc/applications.txt#L59
7712017-11-09T19:38:28 <wumpus> achow101: very efficient, can spent the rest of the time on reviewing high-priority PRs if you want :)
7722017-11-09T19:39:19 <promag> guys, what do you think about implicit sharing (or copy on write) for some structures, like cchain?
7732017-11-09T19:39:27 <meshcollider> jonasschnelli: Is it true that an LLC in Switzerland needs at least CHF 20,000 capital?
7742017-11-09T19:39:40 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #11647: 0.15: Backports (0.15...Mf1711-0152backports) https://github.com/bitcoin/bitcoin/pull/11647
7752017-11-09T19:39:48 <wumpus> meshcollider: that's the case here in the netherlands
7762017-11-09T19:40:01 <gmaxwell> achow101: the key gen is really slow, but who cares... signing is fast.
7772017-11-09T19:40:07 *** Deacydal has quit IRC
7782017-11-09T19:40:12 <sipa> meshcollider: 3 BTC doesn't *sound* like much at all :p
7792017-11-09T19:40:25 <BlueMatt> if thats the case might as well just create a US LLC
7802017-11-09T19:40:29 <BlueMatt> cost is trivial
7812017-11-09T19:40:33 <gmaxwell> achow101: IIRC that implementation is setup for three parties, but it would be relatively straight forward to adjust it for more.
7822017-11-09T19:40:35 <jonasschnelli> meshcollider: 10k for a GmbH
7832017-11-09T19:40:51 <jonasschnelli> jonasschnelli: but we do an association.. which is almost free (maybe 1k)
7842017-11-09T19:40:57 <sipa> promag: cchain is pretty big
7852017-11-09T19:41:00 <meshcollider> Heh yeah sounds like quite a lot for a code signing only company
7862017-11-09T19:41:05 <BlueMatt> jonasschnelli: i believe us is like 50$
7872017-11-09T19:41:36 *** Deacydal has joined #bitcoin-core-dev
7882017-11-09T19:41:44 <promag> sipa: you don't have to copy everything
7892017-11-09T19:41:45 <BlueMatt> (but I think in most states yearly to file tax returns)
7902017-11-09T19:42:10 <achow101> gmaxwell: thanks. I'm going to try taking a look at it
7912017-11-09T19:42:10 <sipa> promag: not without introducing massive granularity
7922017-11-09T19:42:23 <jonasschnelli> BlueMatt: that's why people trust swiss companies more then US. :)
7932017-11-09T19:42:45 <BlueMatt> jonasschnelli: would you prefer I do something in .us?
7942017-11-09T19:42:53 <sipa> promag: if there is ever a point where concurrency is hurt by needing a consistent CChain, i think the solution is to stop using CChain for that purpose (CChain is just an optimized-for-seeking copy of CBlockIndex)
7952017-11-09T19:43:04 <jonasschnelli> For the simplest form of a registered non-single-person company, the GmbH, you need to deposit 10k and have liability (personal) for 20k
7962017-11-09T19:43:10 <jonasschnelli> BlueMatt: no.. please not US
7972017-11-09T19:43:29 <BlueMatt> I mean its not like the company will even hold the cert
7982017-11-09T19:43:29 <meshcollider> jonasschnelli is there any difference between an association and an LLC in terms of getting the certs
7992017-11-09T19:43:36 <BlueMatt> only exist as a legal entity to exist
8002017-11-09T19:43:42 <jonasschnelli> Or the association member may have troubles getting a US visa. :()
8012017-11-09T19:43:57 <BlueMatt> jonasschnelli: I presume there will be no "members"
8022017-11-09T19:44:14 <meshcollider> Or wumpus will be so he gets the cert?
8032017-11-09T19:44:33 <gmaxwell> the only concern about the entity is that it could get more certs but I don't think we care, since the fact that apple et. al. can issue as many as they want regardless.
8042017-11-09T19:44:53 <gmaxwell> meshcollider: we're hopefully going to use multiparty computation so no one person has the cert.'
8052017-11-09T19:44:55 <morcos> i think it makes sense for it to be jonas or someone not related to the Blockstream/Chaincode conspiracy who does this
8062017-11-09T19:44:58 <BlueMatt> gmaxwell: I'm gonna go out on a limb and bet that almost anyone would claim to be a representative of the company and apple would buy it
8072017-11-09T19:45:03 *** chjj has quit IRC
8082017-11-09T19:45:17 <jonasschnelli> BlueMatt: an official assiciation needs to have member
8092017-11-09T19:45:19 <jonasschnelli> (but only in the background)
8102017-11-09T19:45:23 <jonasschnelli> LLC is US imo
8112017-11-09T19:45:33 * luke-jr wonders if a non-developer should do this
8122017-11-09T19:45:48 <cfields> my original suggestion was the DCI, but that got drowned out in the discussion
8132017-11-09T19:45:50 <gmaxwell> lol please, no more non-developers.
8142017-11-09T19:45:55 <BlueMatt> jonasschnelli: I mean ok, if you hate the idea of a us LLC, fine, I just figure its not worth wasting 1k on it, but....ok
8152017-11-09T19:45:58 <cfields> (also, i realize that everyone is just suggesting their own org :p )
8162017-11-09T19:46:00 <BlueMatt> gmaxwell: yea...that
8172017-11-09T19:46:10 <wumpus> cfields: DCI would be fine with me too
8182017-11-09T19:46:14 <sdaftuar> cfields: i am not suggesting my own org! :)
8192017-11-09T19:46:18 <luke-jr> cfields: everyone else is suggesting not-our-org it sounds like
8202017-11-09T19:46:20 <wumpus> cfields: this is just to have alternatives
8212017-11-09T19:46:35 * BlueMatt doesnt care, I was trying to save jonasschnelli 1000$, but the purpose is to exist, not do *do* anything
8222017-11-09T19:46:36 <jonasschnelli> I'm not really familiar with US legal company/association constructs....
8232017-11-09T19:47:01 <BlueMatt> jonasschnelli: all that matters is its cheaper :p
8242017-11-09T19:47:11 <gmaxwell> I would rather not use DCI simply because we really have suffered from people using that stupid message as proof BCF controls bitcoin. I'd rather the name be more benign. (the "foo code signing" sort).
8252017-11-09T19:47:19 <promag> sipa: consider a long rpc call, it locks cs_main and replies a big json - how can it avoid the cs_main lock?
8262017-11-09T19:47:20 <jonasschnelli> DCI would be fine for me as well, though I prefer "Bitcoin Core Code Signing Assocation" over "DCI" (which is a private owned company) in the signing details
8272017-11-09T19:47:47 <wumpus> yes on the longer term having our own signing org would certainly be preferable, I agree
8282017-11-09T19:47:51 <gmaxwell> "Orginization which does not control Bitcoin. LLC"
8292017-11-09T19:48:16 <gmaxwell> yea, for a stopgap, whatever works. hopefully we can just.
8302017-11-09T19:48:18 <jonasschnelli> BlueMatt: I guess the 1000$ is for the lawyers setup,... I guess I would need the same for the LLC process (or someone needs to fill out the application form which then leads to lost 1000$ in development ressources)
8312017-11-09T19:48:19 <cfields> well, this may shortcut the discussion a bit...
8322017-11-09T19:48:28 <BlueMatt> ok, are there any remaining questions aside from "does jonasschnelli want to register it as a swiss org, or do we want someone in .us to spend the 35$ to make it happen here"
8332017-11-09T19:48:28 <wumpus> DCI sounds sufficiently neutral to me though
8342017-11-09T19:48:54 <cfields> from a quick glance, looks pretty possible that I can renew with the current cert
8352017-11-09T19:49:02 <gmaxwell> lol
8362017-11-09T19:49:03 <achow101> who would be the named members/officers/whatever of said organization/association/llc
8372017-11-09T19:49:05 <wumpus> cfields: nice!
8382017-11-09T19:49:06 <sipa> promag: accessing CBlockIndex entries does not require a lock to access most fields (as they are immutable)
8392017-11-09T19:49:07 <BlueMatt> jonasschnelli: the registration process for an org in the us can be pretty easily diy-d, especially if you're never going to *use* the org
8402017-11-09T19:49:07 <luke-jr> why does it need to be Core-specific? just a redundant waste of money and time to then get another one for Knots, when it could just as easily be a shared effort. sigh.
8412017-11-09T19:49:18 <BlueMatt> achow101: who cares?
8422017-11-09T19:49:18 <gmaxwell> achow101: we should create a UK org, you can name anyone you want as the officers.
8432017-11-09T19:49:22 <jonasschnelli> BlueMatt: let me first check the real costs here in CH
8442017-11-09T19:49:22 <jonasschnelli> I know it's basically free... but someone needs to do the paperwork...
8452017-11-09T19:49:29 <jonasschnelli> Which is the significant costs IMO
8462017-11-09T19:49:33 <luke-jr> gmaxwell: even without their consent? XD
8472017-11-09T19:49:33 <gmaxwell> achow101: and the registrations are visible online. :P
8482017-11-09T19:49:34 <jonasschnelli> Which *are
8492017-11-09T19:49:36 <meshcollider> BlueMatt does a US LLC need a bank account and everything?
8502017-11-09T19:49:36 <gmaxwell> luke-jr: yes.
8512017-11-09T19:49:40 <BlueMatt> meshcollider: no
8522017-11-09T19:49:41 <gmaxwell> meshcollider: no.
8532017-11-09T19:49:42 <BlueMatt> why would it?
8542017-11-09T19:49:46 <achow101> BlueMatt: people who want to look at the paperwork and then go "X controls bitcoin blarg" conspiracy
8552017-11-09T19:49:58 <meshcollider> Idk, some countries do dont they
8562017-11-09T19:50:04 <BlueMatt> all you have to do is file paperwork to create it, then file a tax return every year....some nominal cost to doing so, but IIRC 35$ for delaware
8572017-11-09T19:50:05 <luke-jr> gmaxwell: Satoshi Nakamoto, John Doe, Jane Doe, â¦
8582017-11-09T19:50:09 <gmaxwell> achow101: so e.g. we can list satoshi nakamoto, bill gates, donald trump...
8592017-11-09T19:50:17 <achow101> gmaxwell: lol
8602017-11-09T19:50:18 <BlueMatt> achow101: hence why its called "Code Signing, LLC" :p
8612017-11-09T19:50:27 *** Deacydal has quit IRC
8622017-11-09T19:50:50 <achow101> meshcollider: it varies in the us by state. IIRC it costs almost nothing to register an LLC. pay the fee and submit paperwork and thats just about it
8632017-11-09T19:51:05 <BlueMatt> yea, that ^
8642017-11-09T19:51:24 <meshcollider> Ok sweet as
8652017-11-09T19:51:26 <gmaxwell> it does take a bit of time.
8662017-11-09T19:51:37 <jonasschnelli> I guess an US LLC is always tied to an individual, a person who found/owns the LLC?
8672017-11-09T19:51:48 <achow101> jonasschnelli: yes
8682017-11-09T19:51:58 <meshcollider> According to cagi.ch, "The creation of an association does not entail any administrative cost."
8692017-11-09T19:52:11 <achow101> that person also has to file taxes for the llc every year. but for something that does nothing and makes no money, that shouldn't be a problem
8702017-11-09T19:52:16 <sipa> promag: so if you want consistent but just read-only access to CChain, you could ibstead just briefly lock main, get a copy of chainActive.Tip() pointer, unlock, and then use the resulting CBlockIndex without any locks
8712017-11-09T19:52:16 <jonasschnelli> Where an association (in Switzerland at least) has no owner,... it just has members (which have different / exchangable roles)
8722017-11-09T19:52:41 <luke-jr> jonasschnelli: does Apple definitely recognise it?
8732017-11-09T19:52:45 <meshcollider> Association in Switzerland sounds cleaner than LLC in us imo
8742017-11-09T19:53:04 <jonasschnelli> meshcollider: "costs" are a wide term... fill out paperwork/forms for 2-3 can have costs...
8752017-11-09T19:53:14 <sipa> promag: CBlockIndex has efficient Ancestor function yo query at any height... not quite as efficient as looking up in CChain, but probably sufficient for almost anything
8762017-11-09T19:53:35 <jonasschnelli> luke-jr: just checking... but I know other swiss Assocaitions having an App in the App store... so it should work
8772017-11-09T19:53:49 <promag> right, only lacks Next
8782017-11-09T19:53:54 <BlueMatt> jonasschnelli: I dont think we care about ownership here - it literally will not even hold the keys
8792017-11-09T19:54:03 *** Deacyde has joined #bitcoin-core-dev
8802017-11-09T19:54:05 *** bule has joined #bitcoin-core-dev
8812017-11-09T19:54:36 <meshcollider> Jonasschnelli it also says "A Committee (comprising at least a president, a secretary, and a treasurer)." Not just members, irrelevant point though
8822017-11-09T19:54:46 <achow101> I guess the cost here is "how much money does someone need to pay for this thing to exist"
8832017-11-09T19:55:04 <jonasschnelli> A committee is required,.. yes. But it's flexible...
8842017-11-09T19:55:18 <jonasschnelli> achow101: + how much work does he need to spend
8852017-11-09T19:55:19 <meshcollider> Yep
8862017-11-09T19:56:15 <jonasschnelli> BlueMatt: The ownership can have some sideeffects... I personally don't want to be in a register with my Name tied to a company that have "Bitcoin" in it's name. For travel purposes...
8872017-11-09T19:56:18 <wumpus> wasn't it that you can put other companies as officers? :)
8882017-11-09T19:56:24 *** Murch has joined #bitcoin-core-dev
8892017-11-09T19:56:31 <wumpus> and create a recursive organization
8902017-11-09T19:56:44 <jonasschnelli> wumpus: I guess not for an association
8912017-11-09T19:56:51 <jonasschnelli> (for other companies that would work)
8922017-11-09T19:57:05 <jonasschnelli> although I may be wrong
8932017-11-09T19:57:41 <BlueMatt> jonasschnelli: heh, I'm not too worried, if they google any of us they'll find bitcoin faster than if they look at what companies we are connected to :p
8942017-11-09T19:57:48 <achow101> jonasschnelli: in the US, you could register in like Delaware where the business registrations are not public and can only be revealed by subpoena (or the like)
8952017-11-09T19:58:15 <wumpus> jonasschnelli: yes maybe that's only true in Panama :p
8962017-11-09T19:58:39 <wumpus> BlueMatt: I'm not really worried either, they know we're connected to the software project anyhow
8972017-11-09T19:59:34 <jonasschnelli> Yes... probably... though I'm always suprised how entering the country depends on the officers (and the little surface info he has) you have in front of you
8982017-11-09T20:00:02 <meshcollider> "LLCs in Delaware donât file annual reports"
8992017-11-09T20:00:45 <wumpus> meshcollider: that's another popular location for shell companies right?
9002017-11-09T20:01:09 <jonasschnelli> However, next week i should have more bandwidth then 14.4kbds so I'll can check the details... and report in next weeks meeting
9012017-11-09T20:01:18 <meshcollider> I'd expect so, achow101 suggested it
9022017-11-09T20:01:38 <sipa> promag: but next is easy to implement as tip->Ancestor(prev->nHeight + 1) :)
9032017-11-09T20:01:41 <achow101> wumpus: a lot of big US companies are registered in delaware, e.g. Google
9042017-11-09T20:01:44 <luke-jr> TIL achow101 is well-known for suggesting shell company locations
9052017-11-09T20:02:34 <wumpus> luke-jr: hah
9062017-11-09T20:02:46 <achow101> there's also a few other states too
9072017-11-09T20:02:55 <sipa> unfortunately, someone would just need to know the information was suggested by achow101, to guess
9082017-11-09T20:03:17 <meshcollider> Sounds like delaware is good for avoiding lots of tax too, not that that matters here ;)
9092017-11-09T20:03:22 <achow101> luke-jr: well right now I'm taking a course about fraud and scams, and we came to the topic of shell companies and the panama papers recently :p
9102017-11-09T20:03:58 <luke-jr> i c
9112017-11-09T20:04:33 <meshcollider> Oh, "Delaware LLCs do not file annual reports; instead, LLCs in Delaware file annual taxes. The annual tax is a flat $300."
9122017-11-09T20:04:37 *** deadlysin has joined #bitcoin-core-dev
9132017-11-09T20:06:26 <promag> cya later
9142017-11-09T20:07:29 *** tripleslash has joined #bitcoin-core-dev
9152017-11-09T20:07:35 *** dcousens has quit IRC
9162017-11-09T20:08:01 *** dcousens has joined #bitcoin-core-dev
9172017-11-09T20:08:34 *** Murch has quit IRC
9182017-11-09T20:11:02 *** Murch has joined #bitcoin-core-dev
9192017-11-09T20:11:05 *** promag has quit IRC
9202017-11-09T20:11:42 *** Cheeseo has joined #bitcoin-core-dev
9212017-11-09T20:12:31 <bitcoin-git> [bitcoin] laanwj pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/1f4375f8e75f...e6e3fc39518b
9222017-11-09T20:12:32 <bitcoin-git> bitcoin/master 3155fd2 Jonas Schnelli: CKeystore: move relevant implementation out of the header
9232017-11-09T20:12:33 <bitcoin-git> bitcoin/master 208fda6 Jonas Schnelli: CCrypter: move relevant implementation out of the header
9242017-11-09T20:12:33 <bitcoin-git> bitcoin/master dd9bb25 Jonas Schnelli: Fix code style in keystore.cpp/crypter.cpp
9252017-11-09T20:12:58 <bitcoin-git> [bitcoin] laanwj closed pull request #11272: CKeystore/CCrypter: move relevant implementation out of the header (master...2017/09/wallet_refact) https://github.com/bitcoin/bitcoin/pull/11272
9262017-11-09T20:16:37 *** Provoostenator has quit IRC
9272017-11-09T20:19:34 *** deadlysin is now known as deadlysin_
9282017-11-09T20:20:52 <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/e6e3fc39518b...23e9074e0a36
9292017-11-09T20:20:52 <bitcoin-git> bitcoin/master ab8e8b9 practicalswift: Remove unused variables in shell scripts.
9302017-11-09T20:20:53 <bitcoin-git> bitcoin/master 23e9074 Wladimir J. van der Laan: Merge #10771: Remove unused variables in shell scripts...
9312017-11-09T20:21:12 <bitcoin-git> [bitcoin] laanwj closed pull request #10771: Remove unused variables in shell scripts (master...unused-shell-variables) https://github.com/bitcoin/bitcoin/pull/10771
9322017-11-09T20:22:14 *** Khunbish has quit IRC
9332017-11-09T20:22:20 *** Murch has quit IRC
9342017-11-09T20:25:16 *** cl0uding has quit IRC
9352017-11-09T20:25:56 <wumpus> * [new tag] v0.15.1 -> v0.15.1
9362017-11-09T20:26:38 <BlueMatt> !
9372017-11-09T20:27:49 <wumpus> congrats everyone on the 0.15.1 release :)
9382017-11-09T20:34:26 <achow101> yay!
9392017-11-09T20:34:51 <bitcoin-git> [bitcoin] laanwj pushed 14 new commits to master: https://github.com/bitcoin/bitcoin/compare/23e9074e0a36...5e9be169e430
9402017-11-09T20:34:53 <bitcoin-git> bitcoin/master 860e912 practicalswift: Use unique_ptr for pwalletMain (CWallet)
9412017-11-09T20:34:53 <bitcoin-git> bitcoin/master 5a6f768 practicalswift: Use unique_ptr for httpRPCTimerInterface (HTTPRPCTimerInterface)
9422017-11-09T20:34:53 <bitcoin-git> bitcoin/master fa6d122 practicalswift: Use unique_ptr:s for {fee,short,long}Stats (TxConfirmStats)
9432017-11-09T20:35:11 <bitcoin-git> [bitcoin] laanwj closed pull request #11043: Use std::unique_ptr (C++11) where possible (master...unique-pointers) https://github.com/bitcoin/bitcoin/pull/11043
9442017-11-09T20:38:30 *** cl0uding has joined #bitcoin-core-dev
9452017-11-09T20:40:15 *** aj_ is now known as aj
9462017-11-09T20:45:50 <meshcollider> I'll write a release page for bitcoincore.org later if no one else does
9472017-11-09T20:52:48 <bitcoin-git> [bitcoin] jnewbery opened pull request #11648: [tests] Add primitives.py (master...add_primitives_py) https://github.com/bitcoin/bitcoin/pull/11648
9482017-11-09T20:53:05 *** RealM9 has joined #bitcoin-core-dev
9492017-11-09T20:53:43 <RealM9> Hello, which paper wallet generator can be trusted?
9502017-11-09T20:53:58 <RealM9> (Asking it here, because i trust core devs)
9512017-11-09T20:54:21 <RealM9> Is bit address safe?
9522017-11-09T20:56:26 *** RealM9 has quit IRC
9532017-11-09T20:57:52 <aj> jonasschnelli: is there really a question about #8550 being qt only or having a non-qt stats collector? having non-qt access to info always seems better, at a minimum for tests and the like...
9542017-11-09T20:57:55 <gribble> https://github.com/bitcoin/bitcoin/issues/8550 | [Qt] Add interactive mempool graph by jonasschnelli · Pull Request #8550 · bitcoin/bitcoin · GitHub
9552017-11-09T20:59:28 *** arubi has quit IRC
9562017-11-09T20:59:52 *** arubi has joined #bitcoin-core-dev
9572017-11-09T21:00:13 *** bule has quit IRC
9582017-11-09T21:05:06 *** Murch has joined #bitcoin-core-dev
9592017-11-09T21:05:17 <wumpus> aj jonasschnelli I tend to agree, though getting things merged w/ the GUI tends to be easier than JSON API changes
9602017-11-09T21:05:32 <wumpus> in any case the end goal is to have both
9612017-11-09T21:05:47 <aj> wumpus: (loving watching all the commits going through today)
9622017-11-09T21:06:22 <wumpus> I really want the GUI interactive mempool graph in, because it is appealing to people
9632017-11-09T21:07:01 <wumpus> aj: yes, much progress today
9642017-11-09T21:08:25 *** bule has joined #bitcoin-core-dev
9652017-11-09T21:09:56 <cfields> meshcollider: that reminds me, anyone else getting a cert issue for bitcoincore.org ?
9662017-11-09T21:12:03 <cfields> wumpus: and, looks like i was wrong about an easy cert renewal. going deeper now.
9672017-11-09T21:13:44 <aj> cfields: bitcoincore.org seems fine here (firefox sees a let's encrypt cert)
9682017-11-09T21:14:24 <wumpus> cfields: uh oh
9692017-11-09T21:14:43 <wumpus> aj: he means the code signing cert, web certs are much easier luckily
9702017-11-09T21:14:50 <cfields> aj: ah right, thanks for confirming
9712017-11-09T21:15:09 <cfields> wumpus: nah, i meant the site. forgot i had a dns hack in place
9722017-11-09T21:15:11 <cfields> damn you BlueMatt!
9732017-11-09T21:15:15 <wumpus> oh
9742017-11-09T21:15:30 *** arubi has quit IRC
9752017-11-09T21:15:52 *** arubi has joined #bitcoin-core-dev
9762017-11-09T21:17:22 *** Murch has quit IRC
9772017-11-09T21:23:43 *** marcoagner has joined #bitcoin-core-dev
9782017-11-09T21:25:09 <BlueMatt> cfields: lol, uhhhh, I have no idea what server you were accessing that had an old cert
9792017-11-09T21:25:11 <BlueMatt> thats...strange
9802017-11-09T21:25:42 <cfields> BlueMatt: it was pointed at bitcoin.org for some experiment
9812017-11-09T21:25:48 <BlueMatt> lolk
9822017-11-09T21:25:50 *** Murch has joined #bitcoin-core-dev
9832017-11-09T21:26:05 *** Murch has quit IRC
9842017-11-09T21:26:30 <cfields> no worries, all good now
9852017-11-09T21:29:48 *** marcoagner has quit IRC
9862017-11-09T21:32:14 *** Murch has joined #bitcoin-core-dev
9872017-11-09T21:37:49 *** zshlyk is now known as intcat
9882017-11-09T21:40:35 *** adetate has joined #bitcoin-core-dev
9892017-11-09T21:40:49 *** jb55 has quit IRC
9902017-11-09T21:41:28 <luke-jr> â[21:06:22] â<âwumpusâ>â I really want the GUI interactive mempool graph in, because it is appealing to people <-- it conflicts with its dependency nowadays :x
9912017-11-09T21:41:40 <luke-jr> although I have it in Knots with an older version of the dep
9922017-11-09T21:43:57 *** marcoagner has joined #bitcoin-core-dev
9932017-11-09T21:46:41 <gmaxwell> luke-jr: what dependency
9942017-11-09T21:46:54 <luke-jr> gmaxwell: the stats collection stuff
9952017-11-09T21:48:28 *** marcoagner has quit IRC
9962017-11-09T21:49:57 <aj> luke-jr: i did a rebase of the qt bit in a PR against jonas's repo fwiw, https://github.com/btc1/bitcoin/issues/140
9972017-11-09T21:50:32 <aj> luke-jr: (rebased on top of jonas's repo for the json bit)
9982017-11-09T21:51:32 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #11649: Revert "Remove unused variable in shell script" (master...Mf1711-revertRemove) https://github.com/bitcoin/bitcoin/pull/11649
9992017-11-09T21:54:35 *** deadlysin_ has quit IRC
10002017-11-09T21:57:15 *** jb55 has joined #bitcoin-core-dev
10012017-11-09T22:03:51 <luke-jr> aj: did you link the wrong thing?
10022017-11-09T22:04:17 *** Chris_Stewart_5 has quit IRC
10032017-11-09T22:05:41 <bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5e9be169e430...c838283ecdfb
10042017-11-09T22:05:42 <bitcoin-git> bitcoin/master fa0025d MarcoFalke: Revert "Remove unused variable in shell script"...
10052017-11-09T22:05:42 <bitcoin-git> bitcoin/master c838283 MarcoFalke: Merge #11649: Revert "Remove unused variable in shell script"...
10062017-11-09T22:05:49 *** BGL has quit IRC
10072017-11-09T22:06:12 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #11649: Revert "Remove unused variable in shell script" (master...Mf1711-revertRemove) https://github.com/bitcoin/bitcoin/pull/11649
10082017-11-09T22:09:56 <bitcoin-git> [bitcoin] MarcoFalke pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/c838283ecdfb...6e4e98ee8ce2
10092017-11-09T22:09:57 <bitcoin-git> bitcoin/master e1d0cc2 Pieter Wuille: Improve git-subtree-check.sh...
10102017-11-09T22:09:58 <bitcoin-git> bitcoin/master 487aff4 Pieter Wuille: Check subtree consistency in Travis
10112017-11-09T22:09:58 <bitcoin-git> bitcoin/master 6e4e98e MarcoFalke: Merge #11394: Perform a weaker subtree check in Travis...
10122017-11-09T22:09:59 <wumpus> MarcoFalke: huh, I'm 100% sure I checked all the variables
10132017-11-09T22:10:15 <wumpus> no match for $old in that script
10142017-11-09T22:10:21 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #11394: Perform a weaker subtree check in Travis (master...201709_travis_subtree) https://github.com/bitcoin/bitcoin/pull/11394
10152017-11-09T22:10:28 *** okele has joined #bitcoin-core-dev
10162017-11-09T22:10:28 <MarcoFalke> wumpus: Not your fault :)
10172017-11-09T22:10:54 <MarcoFalke> It was only used in one of the sipa/bitcoin.git branches
10182017-11-09T22:11:05 <MarcoFalke> I guess you didn't check them
10192017-11-09T22:11:19 <sipa> hmm, did i miss something?
10202017-11-09T22:11:19 <wumpus> no, I checked our own repository only
10212017-11-09T22:11:44 <MarcoFalke> sipa: no
10222017-11-09T22:11:53 <MarcoFalke> all should be fine now
10232017-11-09T22:13:30 <wumpus> ok
10242017-11-09T22:16:22 <bitcoin-git> [bitcoin] MarcoFalke closed pull request #11582: wallet: Restore -usehd=0 option (master...usehd) https://github.com/bitcoin/bitcoin/pull/11582
10252017-11-09T22:20:31 *** adetate has quit IRC
10262017-11-09T22:22:05 <aj> luke-jr: yes, yes i did. https://github.com/jonasschnelli/bitcoin/pull/9
10272017-11-09T22:22:18 *** adetate has joined #bitcoin-core-dev
10282017-11-09T22:26:27 *** okele has quit IRC
10292017-11-09T22:31:25 *** adetate has quit IRC
10302017-11-09T22:36:43 *** chjj has joined #bitcoin-core-dev
10312017-11-09T22:48:41 *** Murch has quit IRC
10322017-11-09T22:56:13 *** StopAndDecrypt has joined #bitcoin-core-dev
10332017-11-09T22:56:21 *** StopAndDecrypt_ has quit IRC
10342017-11-09T23:01:54 *** chjj has quit IRC
10352017-11-09T23:12:36 *** chjj has joined #bitcoin-core-dev
10362017-11-09T23:15:57 *** Murch has joined #bitcoin-core-dev
10372017-11-09T23:19:33 *** BGL has joined #bitcoin-core-dev
10382017-11-09T23:22:43 *** Cheeseo has quit IRC
10392017-11-09T23:25:57 *** chjj has quit IRC
10402017-11-09T23:26:12 *** StopAndDecrypt has quit IRC
10412017-11-09T23:27:13 *** StopAndDecrypt has joined #bitcoin-core-dev
10422017-11-09T23:45:47 *** Cogito_Ergo_Sum has quit IRC
10432017-11-09T23:46:35 *** moctos has joined #bitcoin-core-dev
10442017-11-09T23:47:14 *** Murch has quit IRC
10452017-11-09T23:50:57 *** vicenteH has quit IRC
10462017-11-09T23:53:44 *** btcdrak has joined #bitcoin-core-dev
10472017-11-09T23:54:36 *** Murch has joined #bitcoin-core-dev
10482017-11-09T23:54:51 *** adetate has joined #bitcoin-core-dev
10492017-11-09T23:55:32 *** moctos has quit IRC