12024-05-01T00:01:46  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
  22024-05-01T00:06:28  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 260 seconds)
  32024-05-01T00:15:03  <bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/063072b86abc...4df2d0c4ce76
  42024-05-01T00:15:04  <bitcoin-git> bitcoin/master 85f50a4 Hennadii Stepanov: refactor: Fix "error C2248: cannot access private member" on MSVC
  52024-05-01T00:15:06  <bitcoin-git> bitcoin/master 774359b Hennadii Stepanov: build, msvc: Compile `test\fuzz\bitdeque.cpp`
  62024-05-01T00:15:07  <bitcoin-git> bitcoin/master 4df2d0c Ava Chow: Merge bitcoin/bitcoin#29983: msvc: Compile `test\fuzz\bitdeque.cpp`
  72024-05-01T00:15:09  <bitcoin-git> [bitcoin] achow101 merged pull request #29983: msvc: Compile `test\fuzz\bitdeque.cpp` (master...240428-msvc-fuzz-bitdeque) https://github.com/bitcoin/bitcoin/pull/29983
  82024-05-01T00:16:12  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
  92024-05-01T00:17:21  <bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4df2d0c4ce76...842f7fdf786f
 102024-05-01T00:17:22  <bitcoin-git> bitcoin/master 1ea8674 glozow: [doc] update release-process.md and backports section of CONTRIBUTING
 112024-05-01T00:17:24  <bitcoin-git> bitcoin/master 842f7fd Ava Chow: Merge bitcoin/bitcoin#29645: doc: update release-process.md
 122024-05-01T00:17:31  <bitcoin-git> [bitcoin] achow101 merged pull request #29645: doc: update release-process.md (master...2024-02-release-docs) https://github.com/bitcoin/bitcoin/pull/29645
 132024-05-01T00:20:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 142024-05-01T00:27:14  *** midnight <midnight!~midnight@user/midnight> has joined #bitcoin-core-dev
 152024-05-01T00:31:26  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 162024-05-01T00:37:03  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 260 seconds)
 172024-05-01T00:51:03  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 182024-05-01T00:56:31  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 268 seconds)
 192024-05-01T01:04:00  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has quit IRC (Quit: leaving)
 202024-05-01T01:09:42  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 212024-05-01T01:14:35  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 256 seconds)
 222024-05-01T01:26:45  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 232024-05-01T01:32:20  *** VonNaturAustreVe <VonNaturAustreVe!~ne0h_@user/vonnaturaustreve> has joined #bitcoin-core-dev
 242024-05-01T01:39:17  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Quit: bye)
 252024-05-01T01:40:52  *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
 262024-05-01T02:31:39  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 255 seconds)
 272024-05-01T02:34:21  *** pablomartin4btc <pablomartin4btc!~pablomart@185.216.146.250> has quit IRC (Ping timeout: 252 seconds)
 282024-05-01T02:34:50  *** mcey_ <mcey_!~emcy@85.255.233.75> has joined #bitcoin-core-dev
 292024-05-01T02:36:13  *** mcey_ <mcey_!~emcy@85.255.233.75> has quit IRC (Remote host closed the connection)
 302024-05-01T02:36:31  *** mcey_ <mcey_!~emcy@85.255.233.75> has joined #bitcoin-core-dev
 312024-05-01T02:38:01  *** mcey <mcey!~emcy@148.252.129.60> has quit IRC (Ping timeout: 272 seconds)
 322024-05-01T02:54:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 332024-05-01T02:59:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 342024-05-01T03:00:24  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 352024-05-01T03:05:25  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 255 seconds)
 362024-05-01T03:18:39  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has joined #bitcoin-core-dev
 372024-05-01T03:30:05  *** Saloframes <Saloframes!~Saloframe@user/Saloframes> has joined #bitcoin-core-dev
 382024-05-01T03:43:32  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:3cf1:dd4d:430:a95b> has quit IRC (Ping timeout: 256 seconds)
 392024-05-01T03:52:32  *** mcey <mcey!~emcy@92.40.199.119.threembb.co.uk> has joined #bitcoin-core-dev
 402024-05-01T03:52:53  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
 412024-05-01T03:53:03  *** mcey_ <mcey_!~emcy@85.255.233.75> has quit IRC (Ping timeout: 260 seconds)
 422024-05-01T03:55:22  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 432024-05-01T03:59:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 442024-05-01T03:59:56  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Remote host closed the connection)
 452024-05-01T04:00:35  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
 462024-05-01T04:01:01  *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
 472024-05-01T04:01:31  *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
 482024-05-01T04:56:20  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 492024-05-01T05:00:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 502024-05-01T05:07:19  *** abubakarsadiq <abubakarsadiq!uid602234@id-602234.hampstead.irccloud.com> has joined #bitcoin-core-dev
 512024-05-01T05:10:34  *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has quit IRC (Quit: PaperSword)
 522024-05-01T05:25:10  *** johnzweng <johnzweng!~johnzweng@zweng.at> has quit IRC (Ping timeout: 246 seconds)
 532024-05-01T05:57:23  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 542024-05-01T06:01:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 552024-05-01T06:08:52  <glozow> 🚀
 562024-05-01T06:13:58  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
 572024-05-01T06:14:55  <bitcoin-git> [bitcoin] maflcko opened pull request #30010: lint: [doc] Clarify Windows line endings (CR LF) not to be used (master...2405-lint-win-crlf-) https://github.com/bitcoin/bitcoin/pull/30010
 582024-05-01T06:26:46  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Ping timeout: 246 seconds)
 592024-05-01T06:36:28  *** ape <ape!~ape@103.166.150.118> has joined #bitcoin-core-dev
 602024-05-01T06:46:02  *** ape <ape!~ape@103.166.150.118> has quit IRC (Ping timeout: 250 seconds)
 612024-05-01T06:58:23  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 622024-05-01T07:03:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 632024-05-01T07:59:24  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 642024-05-01T08:03:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 652024-05-01T08:04:51  *** kexkey <kexkey!~kexkey@static-198-54-132-113.cust.tzulo.com> has quit IRC (Ping timeout: 256 seconds)
 662024-05-01T08:06:04  *** kexkey <kexkey!~kexkey@static-198-44-140-177.cust.tzulo.com> has joined #bitcoin-core-dev
 672024-05-01T08:18:03  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 268 seconds)
 682024-05-01T08:44:39  <bitcoin-git> [bitcoin] willcl-ark closed pull request #27912: net: disconnect inside AttemptToEvictConnection (master...27843-i2p-thread) https://github.com/bitcoin/bitcoin/pull/27912
 692024-05-01T09:00:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 702024-05-01T09:01:08  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has joined #bitcoin-core-dev
 712024-05-01T09:04:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 722024-05-01T09:11:35  *** the_mariner <the_mariner!~Thunderbi@179.180.141.11> has joined #bitcoin-core-dev
 732024-05-01T09:17:36  *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
 742024-05-01T09:33:16  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 752024-05-01T09:34:15  *** johnzweng <johnzweng!~johnzweng@zweng.at> has joined #bitcoin-core-dev
 762024-05-01T09:34:15  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 772024-05-01T09:38:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 782024-05-01T09:39:05  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 792024-05-01T09:42:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 802024-05-01T09:44:56  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 812024-05-01T09:47:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 822024-05-01T09:49:09  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 832024-05-01T09:52:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 842024-05-01T09:54:03  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 852024-05-01T09:58:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 862024-05-01T09:59:08  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 872024-05-01T10:02:15  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
 882024-05-01T10:02:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 892024-05-01T10:03:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 902024-05-01T10:04:05  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 912024-05-01T10:08:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 922024-05-01T10:09:05  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 932024-05-01T10:12:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 942024-05-01T10:14:28  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 952024-05-01T10:17:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 962024-05-01T10:19:11  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
 972024-05-01T10:22:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
 982024-05-01T10:24:16  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
 992024-05-01T10:27:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1002024-05-01T10:29:36  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1012024-05-01T10:32:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1022024-05-01T10:34:07  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1032024-05-01T10:36:38  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
1042024-05-01T10:39:13  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1052024-05-01T10:42:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1062024-05-01T10:44:16  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1072024-05-01T10:47:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1082024-05-01T10:49:14  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1092024-05-01T10:52:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1102024-05-01T10:54:24  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1112024-05-01T10:57:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1122024-05-01T10:59:21  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1132024-05-01T11:02:52  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
1142024-05-01T11:08:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1152024-05-01T11:09:24  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1162024-05-01T11:13:04  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
1172024-05-01T11:13:36  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1182024-05-01T11:14:16  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1192024-05-01T11:17:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1202024-05-01T11:19:05  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1212024-05-01T11:23:02  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1222024-05-01T11:24:12  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1232024-05-01T11:27:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1242024-05-01T11:29:07  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1252024-05-01T11:31:41  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
1262024-05-01T11:32:34  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1272024-05-01T11:32:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1282024-05-01T11:34:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1292024-05-01T11:37:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1302024-05-01T11:39:28  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1312024-05-01T11:42:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1322024-05-01T11:43:59  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1332024-05-01T11:48:14  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1342024-05-01T11:49:19  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1352024-05-01T11:52:26  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1362024-05-01T11:54:09  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has joined #bitcoin-core-dev
1372024-05-01T11:55:38  *** cygnet3 <cygnet3!~cygnet3@82.102.19.91> has joined #bitcoin-core-dev
1382024-05-01T11:58:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1392024-05-01T11:58:28  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1402024-05-01T11:59:05  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1412024-05-01T12:03:10  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1422024-05-01T12:04:16  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1432024-05-01T12:07:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
1442024-05-01T12:09:26  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1452024-05-01T12:12:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1462024-05-01T12:14:46  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1472024-05-01T12:18:06  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1482024-05-01T12:19:31  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1492024-05-01T12:22:18  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1502024-05-01T12:23:10  *** cygnet3 <cygnet3!~cygnet3@82.102.19.91> has quit IRC (Ping timeout: 256 seconds)
1512024-05-01T12:23:29  *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:37:a90d:ac1f:c195:a0> has joined #bitcoin-core-dev
1522024-05-01T12:24:22  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1532024-05-01T12:27:22  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
1542024-05-01T12:27:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1552024-05-01T12:28:00  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1562024-05-01T12:29:15  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1572024-05-01T12:32:59  *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1582024-05-01T12:33:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1592024-05-01T12:34:13  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1602024-05-01T12:37:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1612024-05-01T12:39:08  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1622024-05-01T12:42:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1632024-05-01T12:43:16  <bitcoin-git> [bitcoin] glozow opened pull request #30012: opportunistic 1p1c followups (master...2024-05-1p1c-followups) https://github.com/bitcoin/bitcoin/pull/30012
1642024-05-01T12:44:13  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1652024-05-01T12:47:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1662024-05-01T12:49:13  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1672024-05-01T12:52:38  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1682024-05-01T12:53:04  *** Jadi <Jadi!~Jadi@2001:19f0:5001:72:5400:2ff:fe0b:e8bb> has quit IRC (Quit: Jadi)
1692024-05-01T12:53:17  <instagibbs> now that #28970 is in ( 🚀 earned), I'd like to see if people are interested in doing a WG for the remaining couple items for mempool policy pre-cluster mempool, starting with #28984 .  Useful for LN and other cases today.
1702024-05-01T12:53:19  <gribble> https://github.com/bitcoin/bitcoin/issues/28984 | Cluster size 2 package rbf by instagibbs · Pull Request #28984 · bitcoin/bitcoin · GitHub
1712024-05-01T12:53:21  <gribble> https://github.com/bitcoin/bitcoin/issues/28970 | p2p: opportunistically accept 1-parent-1-child packages by glozow · Pull Request #28970 · bitcoin/bitcoin · GitHub
1722024-05-01T12:53:22  <instagibbs> PM me if interested thanks
1732024-05-01T12:54:08  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1742024-05-01T12:56:13  *** jadi <jadi!~jadi@209.250.252.205> has joined #bitcoin-core-dev
1752024-05-01T12:57:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1762024-05-01T12:59:12  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1772024-05-01T13:02:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1782024-05-01T13:04:54  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1792024-05-01T13:06:09  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has quit IRC (Quit: My iMac has gone to sleep. ZZZzzz…)
1802024-05-01T13:07:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1812024-05-01T13:08:38  *** jadi <jadi!~jadi@209.250.252.205> has quit IRC (Quit: leaving)
1822024-05-01T13:09:31  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1832024-05-01T13:10:26  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
1842024-05-01T13:12:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1852024-05-01T13:15:24  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1862024-05-01T13:17:54  *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1872024-05-01T13:18:10  *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev
1882024-05-01T13:19:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1892024-05-01T13:20:12  *** jadi <jadi!~jadi@209.250.252.205> has joined #bitcoin-core-dev
1902024-05-01T13:22:12  *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
1912024-05-01T13:22:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1922024-05-01T13:24:09  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1932024-05-01T13:28:06  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1942024-05-01T13:29:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
1952024-05-01T13:29:56  <instagibbs> (WG == working group, apologies for acronyms)
1962024-05-01T13:32:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
1972024-05-01T13:34:21  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
1982024-05-01T13:34:38  <gmaxwell> "Greg proposes to create a Walled Garden around the mempool"
1992024-05-01T13:35:57  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
2002024-05-01T13:37:29  <sdaftuar> i'm trying to put them *in* the mempool myself...
2012024-05-01T13:37:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2022024-05-01T13:39:07  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2032024-05-01T13:41:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
2042024-05-01T13:42:15  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2052024-05-01T13:42:47  <instagibbs> sdaftuar says the guy who is trying to ban unconfirmed spends
2062024-05-01T13:43:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2072024-05-01T13:43:35  <bitcoin-git> [bitcoin] shinghim opened pull request #30014: doc: Remove outdated description for --port argument (master...master) https://github.com/bitcoin/bitcoin/pull/30014
2082024-05-01T13:44:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2092024-05-01T13:46:16  <sdaftuar> wen limitclustercount=1 hats?
2102024-05-01T13:47:10  <instagibbs> optimal linearization of size 1, finally someone who cares about speed
2112024-05-01T13:48:10  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2122024-05-01T13:49:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2132024-05-01T13:49:44  <gmaxwell> If you then also bound transaction weight to be a small fraction of the limit, it then because easy to prove that the mining algrorithim has a small and tight approximation error bound.
2142024-05-01T13:50:55  <gmaxwell> (cause include by feerate sort absent dependences obviously cannot be worse than optimal by more than leaving out the next transaction in the sort order after the last one that fit.)
2152024-05-01T13:52:06  <sdaftuar> yep, part of the motivation to start making progress towards lower limits on tx size, eg #29873
2162024-05-01T13:52:07  <gribble> https://github.com/bitcoin/bitcoin/issues/29873 | policy: restrict all TRUC (v3) transactions to 25KvB by glozow · Pull Request #29873 · bitcoin/bitcoin · GitHub
2172024-05-01T13:52:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2182024-05-01T13:52:46  <sdaftuar> seems like maybe a long road though to get people on board with lower limits in general
2192024-05-01T13:53:49  <bitcoin-git> [bitcoin-maintainer-tools] laanwj opened pull request #163: Remove guix-verify tool (main...2024-05-remove-guix-verify) https://github.com/bitcoin-core/bitcoin-maintainer-tools/pull/163
2202024-05-01T13:54:09  <gmaxwell> oh wow, I wasn't aware.  Yeah, had the limits never been set very high it would probably be a mostly non-issue but it's always hard to restrict.
2212024-05-01T13:54:09  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
2222024-05-01T13:54:35  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2232024-05-01T13:55:10  <bitcoin-git> [bitcoin-maintainer-tools] laanwj opened pull request #164: Fix "SyntaxWarning: invalid escape sequence" (main...2024-04-unescaped-re) https://github.com/bitcoin-core/bitcoin-maintainer-tools/pull/164
2242024-05-01T13:57:35  <instagibbs> policy is kind of the opposite of consensus: easy to relax, hard to restrict
2252024-05-01T13:57:58  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2262024-05-01T13:58:46  *** Digger <Digger!~Digger@207.96.82.156> has joined #bitcoin-core-dev
2272024-05-01T13:59:36  *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
2282024-05-01T13:59:48  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2292024-05-01T14:02:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
2302024-05-01T14:03:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2312024-05-01T14:03:24  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2322024-05-01T14:04:21  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2332024-05-01T14:05:27  *** Digger <Digger!~Digger@207.96.82.156> has quit IRC (Quit: Client closed)
2342024-05-01T14:05:56  *** PennyEther <PennyEther!~PennyEthe@207.96.82.156> has joined #bitcoin-core-dev
2352024-05-01T14:08:07  <PennyEther> Hi
2362024-05-01T14:08:14  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2372024-05-01T14:09:34  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2382024-05-01T14:09:49  <PennyEther> Firstly, I'd like to apologize for any errors in my terminology. I'm looking for the part of the source code that handles when a new block is received from a peer. Presumably, the client will validate the block, and if it's acceptable, will consider it the new "head" block, and start mining off of it. I'd like to know how it handles receiving a
2392024-05-01T14:09:50  <PennyEther> head block that has a height a few blocks higher than the currently known head block, as in this case it must receive all the blocks back until a common ancestor. How does it get these intermediate blocks?
2402024-05-01T14:12:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2412024-05-01T14:13:44  <darosior> PennyEther: hi. this would make for a good https://bitcoin.stackexchange.com/ if it hasn't already been answer there
2422024-05-01T14:13:52  <gmaxwell> in modern bitcoin software it won't obtain the blocks at all unless it's first obtained the block headers and determined that the headers could constutite a best tip if their contained blocks were valid.  In the early software, I believe the behavior, if it got a block where it didn't know the immediate ancestor of the block it would set the block aside and fetch the prior block from the same
2432024-05-01T14:13:57  <darosior> s/if it/question if it/
2442024-05-01T14:13:58  <gmaxwell> source, which it would then keep doing until it got to a common chain.
2452024-05-01T14:14:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2462024-05-01T14:14:10  <gmaxwell> and yeah thats the sort of thing that would probably get some long, useful, researched stack exchange writeup.
2472024-05-01T14:15:00  <PennyEther> It can't determine if the headers could constitute a best tip without evaluating the whole chain, since it needs to determine the total work in the chain
2482024-05-01T14:16:16  <sdaftuar> i think this is answered pretty thoroughly by Pieter here: https://bitcoin.stackexchange.com/a/121293
2492024-05-01T14:16:59  <PennyEther> sdaftuar thanks I'll give it a read
2502024-05-01T14:17:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2512024-05-01T14:17:21  <sipa> gmaxwell: hi!
2522024-05-01T14:18:38  <gmaxwell> sdaftuar: (as I look at sipa's answer:) are unsolicited blocks still processed?
2532024-05-01T14:19:02  <sdaftuar> yes i believe so, if they're at (or build on) the tip
2542024-05-01T14:19:04  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2552024-05-01T14:21:14  <gmaxwell> k, for some reason I thought those had finally gotten nuked (they at least used to get abused by some mass broadcasters that would selfishly send their whole newly found block to everyone they could connect to, ironically probably slowing its propagation)
2562024-05-01T14:21:39  <instagibbs> I think ViatBTC sometimes still does this, very poorly? b10c ?
2572024-05-01T14:22:08  <instagibbs> (they advertise witness stuff, you ask them, and they drop the response)
2582024-05-01T14:22:24  <sdaftuar> i just double checked and i don't believe that logic (in `AcceptBlock()`) has changed since 2017 or so (and that might have just been a refactor)
2592024-05-01T14:22:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2602024-05-01T14:22:59  <gmaxwell> lol still? yeah they were IIRC not just spamming blocks but doing it without the witnesses before.
2612024-05-01T14:23:00  <lightlike> just at the tip? I thought having  MinimumChainWork was sufficient.
2622024-05-01T14:23:03  <gmaxwell> which is obviously useless.
2632024-05-01T14:23:23  <sdaftuar> lightlike: yes you're right, not just at the tip.  MinimumChainWork is not enough by itself though; must have more work than the tip
2642024-05-01T14:23:35  <lightlike> ah, I see.
2652024-05-01T14:23:38  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
2662024-05-01T14:23:42  <instagibbs> wouldn't put it past them, I don't think their code ever actually worked, which is... interesting
2672024-05-01T14:24:12  <PennyEther> Supposing I were reasonably confident I found a problem with Bitcoin Protocol, what would be a responsible way to disclose it? I'm nearly certain of a fundamental issue, related to timestamps.
2682024-05-01T14:24:29  <PennyEther> I am well aware of median time and the 2-hour rule, but this is more existential than that
2692024-05-01T14:25:02  <sdaftuar> PennyEther: please see https://github.com/bitcoin/bitcoin/blob/master/SECURITY.md
2702024-05-01T14:25:08  <PennyEther> Thanks
2712024-05-01T14:25:10  <darosior> PennyEther: lookup if it's not an existing problem but if in doubt an email to https://github.com/bitcoin/bitcoin/blob/master/SECURITY.md is prob worth it
2722024-05-01T14:25:40  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
2732024-05-01T14:25:43  <darosior> s/existing/known/
2742024-05-01T14:26:41  <gmaxwell> I wonder if anyone has ever created a "I think I found a vulnerablity" FAQ that goes over all the things people keep thinking are vulnerablities and aren't, and things that are but are just unaddressed (e.g. becuase they're not 'limiting vulnerablties' -- if you could do that attack you could do much worse, and the worse thing doesn't have a known fix)
2752024-05-01T14:27:23  <PennyEther> I spent hours searching for this last night, couldn't find it. Looked at the code and the way it handles it is insufficient. Trying to come up with the ramifications of it now
2762024-05-01T14:27:45  <gmaxwell> like from PennyEther's questions, I might guess that they are thinking of the issues that header pre-sync solves.
2772024-05-01T14:28:18  <PennyEther> I'll just ask about it here. What if a peer receives a block that is otherwise valid, except that it is 2 hours and 5 minutes in the future?
2782024-05-01T14:28:31  <PennyEther> AFAIK, it is ignored.
2792024-05-01T14:28:34  <gmaxwell> it gets ignored
2802024-05-01T14:28:35  <darosior> PennyEther: then it's refused
2812024-05-01T14:28:39  <PennyEther> Yes, but it shouldn't be.
2822024-05-01T14:28:44  <PennyEther> It will be valid in 5 minutes.
2832024-05-01T14:28:48  <darosior> Try again in 5 minutes :)
2842024-05-01T14:28:55  <gmaxwell> it'll get picked up again later when its offered then and another block comes after it
2852024-05-01T14:29:02  <PennyEther> Consider if it is 2 hours and 1 minute in the future
2862024-05-01T14:29:07  <PennyEther> That's 1 minute of wasted work
2872024-05-01T14:29:09  <sipa> it will not be rejected (as in: it won't be marked permanently invalid), it will just be ignored
2882024-05-01T14:29:11  <instagibbs> as long as it's not permanently rejected(!) should be ok
2892024-05-01T14:29:30  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
2902024-05-01T14:29:43  <PennyEther> If it's 2 hours and 1 minute, then nodes that ignore it will be wasting work. As, in all likelihood, it *will* be the next valid block in just a minutes time
2912024-05-01T14:30:19  <PennyEther> Hence, nodes should *not* simply discard based off the 2 hour rule. They should apply poisson distribution to determine the likelihood that it will become the next valid block
2922024-05-01T14:30:23  <Murch[m]> PennyEther: How is that an issue? It’s no different than two blocks being found at the same height, if someone else happens to find a block before it becomes valid
2932024-05-01T14:30:27  <gmaxwell> it may be or may not be, that will be decided by whomever wins the lottery and gets the next block.
2942024-05-01T14:31:02  <sipa> tracing through the code, i believe the requirements for an unannounced block being processed are (a) either we already have the header, or the header passes min-pow checks (b) don't have the block already (c) has at least as much work as active tip and as minpow (d) height is not more than 288 than active tip's height
2952024-05-01T14:31:25  <PennyEther> sipe, where do you find the 288 rule?
2962024-05-01T14:32:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
2972024-05-01T14:32:07  <sipa> PennyEther: https://github.com/bitcoin/bitcoin/blob/v27.0/src/validation.cpp#L4218
2982024-05-01T14:32:31  <PennyEther> thanks
2992024-05-01T14:33:33  <gmaxwell> PennyEther: assuming (cough) nodes times are synced and the broken miner who created it has insubstantial hash power, the probablity that it will be the next block is zero, because almost everyone will have ignored it as it was from the future at the time it arrived.
3002024-05-01T14:33:34  <sipa> I guess my rule (a) is automatically satisfied if (c) is satisfied, so (a) can be ignored
3012024-05-01T14:33:44  <Murch[m]> I mean, sure if some miners were running with a slightly fast clock, they would accept it, and others would not, and there might temporarily be two active chaintips. But again, it’s not clear to me how that introduces a security issue that is not resolved as soon as either the time passes or one of the chaintips pulls ahead the other in total work.
3022024-05-01T14:33:46  <PennyEther> I was only looking here so far: https://github.com/bitcoin/bitcoin/blob/842f7fdf786fcbbdf3df40522945813404f8a397/src/validation.cpp#L4004
3032024-05-01T14:34:04  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3042024-05-01T14:34:46  <gmaxwell> Murch[m]: I agree. (this is also fwiw, not a new discussion, though I dunno if there is any specific prior one that would be useful to link to)
3052024-05-01T14:34:57  <PennyEther> Yes, I agree, but lets play it out
3062024-05-01T14:35:43  <PennyEther> Murch: two points.  1) a smart miner wouldnt simply discard it. they would hold it, and wait for it to be valid, then mine off of it.
3072024-05-01T14:35:47  <gmaxwell> PennyEther: Are you imagining that if a minute passes then suddenly that block will be best?  nodes don't reprocess it automatically. so the block remains effectively degraded even once its time is valid.
3082024-05-01T14:36:05  <PennyEther> yes, but it shouldnt be degraded, it should be accepted (by smart miners), no?
3092024-05-01T14:36:40  <PennyEther> 2) it would behoove all miners to submit timestamps that get rejected by some (but not all) of their peers.
3102024-05-01T14:36:40  <Murch[m]> Okay, let’s play it though.
3112024-05-01T14:37:00  <gmaxwell> That would be an improved greedy strategy. (less clear if it's rational from a longer perspective since it's harmful to encourage from the future blocks)
3122024-05-01T14:37:10  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
3132024-05-01T14:37:44  <Murch[m]> Current best block is 100 at time T. Mallory mines block 101 with time T+201. When it’s broadcast 90% of the hashrate drops it on the floor, but 10% accepts it because they have skewed clocks or are "smart".
3142024-05-01T14:38:01  <gmaxwell> (2) is why I included the synced times assumption.  Though it is not in your favor to have less than 30% of the hashpower mining on your block.
3152024-05-01T14:38:40  <PennyEther> let me rephrase 2.  2) It would behoove all miners to submit timestamps that get reject by some (but not the majority) of their peers
3162024-05-01T14:38:55  <sipa> What does "submit timestamps" mean?
3172024-05-01T14:38:57  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
3182024-05-01T14:39:03  <PennyEther> timestamp in the other-wise valid new block
3192024-05-01T14:39:06  <gmaxwell> sipa: adopt future timestamps when mining.
3202024-05-01T14:39:41  <Murch[m]> After some time, with 90% likelihood, someone mines block 101' at T+about 11 minutes, with 10% likelihood, someone mines block 102 at time T+100 minutes. If 101' gets found first, there are two active chaintips where 101' is being mined on by 90% of the hashrate and 101 is being mined on by 10% of the hashrate. If 102 is found first, everyone reorgs to 102 and continues.
3212024-05-01T14:40:37  <sipa> I think if you continue that reasoning, you'll end up with miners that just ignore the max-timestamp rule, and can end up heading off on their own, pushing timestamps ever further into the future... not the be accepted by the rest of the network, but hoping that these blocks will eventually be part of the best chain
3222024-05-01T14:41:19  <gmaxwell> evenutally they bring mtp up to that threshold and then cant mine a chain that will be accepted in the present by 'honest' (in the hbar sense) software.
3232024-05-01T14:41:25  <Murch[m]> So, Mallory loses their block if 90% of the hashrate mines two blocks before 10% of the hashrate mines 1 block. Either way that looks not particularly attractive to me. And 10% is pretty generous
3242024-05-01T14:42:15  <gmaxwell> Murch[m]: mallories goal should be accepted by a third, then its essentially the same as 'selfish mining'.
3252024-05-01T14:42:16  <PennyEther> Murch, your example only works because you did a 90/10 split, and because currently, the mining software rather stupidly drops soon-to-be-valid blocks rather than stores them.
3262024-05-01T14:42:39  <instagibbs> gmaxwell yes, seems like the natural analogy is selfish mining?
3272024-05-01T14:42:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
3282024-05-01T14:42:50  <gmaxwell> PennyEther: it's not stupid to behave in a way that keeps the system working. :P but that aside.
3292024-05-01T14:43:07  <PennyEther> It's stupid because it is not in their best incentive
3302024-05-01T14:44:14  <gmaxwell> PennyEther: it's complicated, because if the collusion to behave in a way that undermines convergance breaks the system then they all go bankrupt. but I don't think we need to split these particular hairs.
3312024-05-01T14:44:16  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3322024-05-01T14:44:21  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
3332024-05-01T14:44:21  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
3342024-05-01T14:44:51  <PennyEther> This is not about collusion, it's about financial incentive.. let me make an example
3352024-05-01T14:45:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3362024-05-01T14:45:09  <Murch[m]> PennyEther: Unless it’s a coordinated change in behavior, the chance of losing their block reward seems way higher than them having an advantage.
3372024-05-01T14:45:42  <PennyEther> First, an argument for not ignoring T+>2h blocks.  If it's T+2h1s, then you shouldn't ignore it. It will be valid in just 1s. So you should mine off of it. In fact, an otherwise-valid block with a timestamp of T+2h6m has about a 65% of becoming valid before another block is found.
3382024-05-01T14:45:56  <Murch[m]> If it’s a coordinated change in behavior, miners are undermining rules that keep the network safe. This tends to get some pretty strong reactions from the Bitcoin community.
3392024-05-01T14:45:58  <Murch[m]> Related: https://bitcoin.stackexchange.com/a/121249/5406
3402024-05-01T14:46:33  <gmaxwell> PennyEther: so in the selfish mining case which I think your example is just a special case of, the commonly proposed "fix" is to randomly select the next block in a race based on its hash.  But this has the effect of creating selfish mining gains all the way down to 0 hashpower, so an attack that requires 1/3 hashpower (or participation) turns into a weaker attack that works from zero
3412024-05-01T14:46:39  <Murch[m]> PennyEther: I think you have an adoption gap issue. The first miner to start behaving this way is going to lose money.
3422024-05-01T14:46:39  <gmaxwell> hashpower up.  So that fix is not an obvious win.
3432024-05-01T14:47:16  <instagibbs> Murch[m] a single miner can trigger it, I guess is the point, vs "does this block move MTP up beyond 2 hours" ?
3442024-05-01T14:47:25  <instagibbs> single block*
3452024-05-01T14:47:52  <Murch[m]> instagibbs: But defacto all miners are just gonna drop it on the floor then, and the miner just loses their reward
3462024-05-01T14:47:55  <instagibbs> but if it happens just once, miners will just ignore this game, as they do now
3472024-05-01T14:48:11  <gmaxwell> maybe your variation has an advantage that some would 'accidentally' participate due to clock skew, propagation, etc. but I think that would need an numerical simulation to see if accidental participation mattered.
3482024-05-01T14:49:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
3492024-05-01T14:49:28  <gmaxwell> PennyEther: there are 10001 things that participants could do to increase their income. For example, it would have been rational for miners to try to ignore the halving block and try to replace the block prior to the halving.    But for any sufficiently rare non-optimality, you have to consider the development (and poentially goodwill) cost of exploiting the gain.
3502024-05-01T14:49:29  <PennyEther> So... I'm supposed to rely on "strong reactions" from dissuading behavior which is otherwise financially benificial?
3512024-05-01T14:50:30  <gmaxwell> Maybe? the security in the system ultimately arises from social and economic properties.
3522024-05-01T14:50:33  <Murch[m]> It’s only financially beneficial if a big portion of the hashrate adopts your strategy, and it’s not in the interest for anyone to go first
3532024-05-01T14:51:10  <instagibbs> PennyEther it is pointed out that it looks like a subset of an already-known attack, selfish mining, so it might be a good way forward to research on it? lots of e-ink spilled on the subject
3542024-05-01T14:51:13  <Murch[m]> Sounds mostly like a mexican standoff unless a big portion of the hashrate changes their behavior to your strategy together
3552024-05-01T14:51:30  <PennyEther> Murch, what do you mean by "it" when you say "it is only financially beneficial".  It is financially beneficial to mine off of a block that is T+2h6m regardless of what any other peer is doing.
3562024-05-01T14:51:30  <gmaxwell> Murch[m]: well "multiple equlibrium" is a nicer term than mexican standoff.
3572024-05-01T14:51:31  <instagibbs> (maybe not a subset, but related)
3582024-05-01T14:51:54  <gmaxwell> PennyEther: no because it will get your block ignored too when you're successful.
3592024-05-01T14:52:06  <Murch[m]> PennyEther: But it’s financially detrimental to mine the T+2h6min block
3602024-05-01T14:52:08  <instagibbs> > It is financially beneficial to mine off of a block that is T+2h6m regardless of what any other peer is doing.
3612024-05-01T14:52:08  <instagibbs> you're making assertions that aren't necessarily true
3622024-05-01T14:52:34  <PennyEther> instagibbs, this assertion is true
3632024-05-01T14:52:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
3642024-05-01T14:52:52  <PennyEther> There is a >50% chance that the T+2h6m block will become valid BEFORE another valid block is mined
3652024-05-01T14:52:56  <gmaxwell> PennyEther: say you are mining, you get a T+2h6m block.  Is it in your interest to mine off it right now? no it is not. if you are successful right now, your block will also get ignored/have poor propagation.
3662024-05-01T14:53:09  <gmaxwell> PennyEther: that's a misunderstanding of the mining process.
3672024-05-01T14:53:12  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
3682024-05-01T14:53:45  <PennyEther> No. There is a 51% chance your block will become valid before another block is found, meaning you were allocating work correctly. in the other 49% chance, you will start mining off of the other valid block.
3692024-05-01T14:53:52  <gmaxwell> No.
3702024-05-01T14:53:53  <instagibbs> you're assuming the answer tbh. It's not obvious.
3712024-05-01T14:54:00  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3722024-05-01T14:54:01  <sipa> PennyEther: let's make the example more extreme. You have 1% of the hashrate, and you see a block with a timestamp that's a day into the future. Is it beneficial for you to mine on it, assuming that you know for a fact that 99% of the hashrate will ignore blocks with a timestamp more than 2 hours?
3732024-05-01T14:54:05  <gmaxwell> PennyEther: mining is memoryless.
3742024-05-01T14:54:26  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
3752024-05-01T14:54:28  <PennyEther> instagibbs, the answer is derived from poisson distribution probability. I'm moving on from discussing if the assertion is correct or not, because we can just use T+2h1s and be certain the odds are in your favor
3762024-05-01T14:54:28  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
3772024-05-01T14:55:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3782024-05-01T14:55:20  <gmaxwell> PennyEther: when you attempt a mining operation, it will either find a block or it won't.  Lets assume it doesn't, then you go again,-- this second time your success is independant of any of your desisions at the prior stage.
3792024-05-01T14:56:24  <PennyEther> Regardless of your hashrate, if you receive a block that is T+2h6m, it is to your benefit to hash off of that block, not the old one.  in 6m time, that block will become valid. there is <50% chance that another valid block will be found before then. this is derived from poisson probability.  are we all on the same page?
3802024-05-01T14:56:45  <gmaxwell> PennyEther: so in your example, when the block is T+2h6m if you attempt to mine it and are successful in that attempt you'll just have yourself another block that gets ignored.  Now-- would it be rational to start attempting to extend it once its at T+2h?  Yes, at that point in time.
3812024-05-01T14:56:55  <gmaxwell> no we are not.
3822024-05-01T14:57:44  <Murch[m]> PennyEther: I think the main disconnect is that when the miner publishes their block with a timestamp of T+2h6m, all of their peers will drop it on the floor and nobody will even hear about it.
3832024-05-01T14:58:08  <gmaxwell> PennyEther: you would be best off just attempting to orphan it for some span of time. (perhaps not the full 6 minutes, that would require a careful analysis).
3842024-05-01T14:58:13  <Murch[m]> It’s not like people sit pouring over their debug.log all day and manually accept blocks that are invalid according to network rules.
3852024-05-01T14:58:16  <PennyEther> let me just write out the example very clearly.
3862024-05-01T14:58:18  <instagibbs> It's a question of if they should drop or not, and it's highly dependent on what others are doing
3872024-05-01T14:58:29  <PennyEther> no, its not dependant on others. let me write it out.
3882024-05-01T14:58:58  <sipa> We can simulate this.
3892024-05-01T14:59:07  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
3902024-05-01T15:00:54  <gmaxwell> PennyEther: so say you and I are miners and we see this 2h6m block. You mine on it, I reject it.  a minute passes. I find a block. the network adopts my block and will not be unseated by the delayed block because mine was 'first valid'.
3912024-05-01T15:01:27  *** PennyEther <PennyEther!~PennyEthe@user/PennyEther> has quit IRC (Quit: Client closed)
3922024-05-01T15:02:03  <gmaxwell> There is a hashpower sensitive component to this (because as I said, it's an analog to the selfish mining paper), where this works out for you but only if you have enough hashpower that you can get the future block two ahead by the time its valid.
3932024-05-01T15:02:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
3942024-05-01T15:02:54  <gmaxwell> and I believe that point is at ~30% hashpower participating on the future block.
3952024-05-01T15:04:30  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
3962024-05-01T15:07:17  <Murch[m]> Whoever said it earlier hit the nail on the head. It seems to me that this boils down to a variant of selfish mining
3972024-05-01T15:07:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
3982024-05-01T15:07:37  <gmaxwell> doesn't make it uninteresting.
3992024-05-01T15:09:02  <gmaxwell> I mean it might be the same thing: if you fix by randomizing your acceptance, then you make it immediately interesting to defect from protocol conforming behavior even if you're alone.  ... or the natural skew in acceptance times might make the behavior change reasonable regardless of hashpower.
4002024-05-01T15:12:10  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4012024-05-01T15:12:36  <gmaxwell> Murch[m]: and meanwhile, running a constraint solver against the mempool yields a block that pays $2000 more in fees than the one that is gonna get mined. :P (not really, well didn't try, but it used to be pretty normal when there was backlog)
4022024-05-01T15:13:18  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
4032024-05-01T15:13:25  *** PennyEther <PennyEther!~PennyEthe@207.96.82.156> has joined #bitcoin-core-dev
4042024-05-01T15:14:06  <PennyEther> Is there any way to view chat history? I got DC'd
4052024-05-01T15:14:09  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
4062024-05-01T15:14:44  <gmaxwell> PennyEther: yes. https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2024-05-01
4072024-05-01T15:14:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
4082024-05-01T15:15:00  <gmaxwell> PennyEther: I think sipa is off simulating this right now.
4092024-05-01T15:15:06  <sipa> haha, no
4102024-05-01T15:15:15  <gmaxwell> oh damn getting slow in your old age. lol
4112024-05-01T15:15:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
4122024-05-01T15:15:18  <sipa> gmaxwell: i
4132024-05-01T15:15:26  <sipa> gmaxwell: i'm working on reducing that $2000, ok?!
4142024-05-01T15:15:33  <gmaxwell> haha
4152024-05-01T15:15:33  <sipa> :P
4162024-05-01T15:15:59  <sipa> though, limiting transactions to 25 kvB would really help, kthxbye
4172024-05-01T15:16:05  *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
4182024-05-01T15:17:32  <gmaxwell> sipa: you and sdaftuar will do some heroic work with cluster mempool, then murch can swing in with something that forks and calls some coinor off the shelf solver and produces optimal solutions for the entire block including tail packing in 50ms. :P
4192024-05-01T15:18:14  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4202024-05-01T15:18:14  <PennyEther> Current block is 100, and wall clock is 0.  You receive block 101-f (f for future), with T=2h6m. Most clients (foolishly) drop this block.
4212024-05-01T15:18:15  <PennyEther> However, based on probabilities, there is a >51% chance block 101-f will become active BEFORE block 101-a (another block with prev = block 100) is discovered. To make the example more clear, just imagine block 101-f has T=2h1s. In just 1s, somebody can resubmit the block and it will be taken as the current block.
4222024-05-01T15:18:15  <PennyEther> So, when you receive block 101-f with T=2h6m, you *should* start mining off of it. In all likelihood, it will become the next valid block, and you'll have a head start on the new chain. If in If block 101-a comes in before, then it is up to you which one to work on, it makes no difference. The advantage is in the 6m head start you get.
4232024-05-01T15:18:16  <PennyEther> We can now start to see how hashrate might get forked if miners start mining in this "smart" manner of NOT ignoring valid blocks (with invalid blocktimes). It is in their best incentive to look at future blocks and determine the likelihood they "vest" into the actual blocks. Assuming a poisson distribution with mean of 10m, anything less than ~2h7m
4242024-05-01T15:18:16  <PennyEther> should be temporarily accepted as the head and mined off of. Again, it's far more obvious if we go with 2h1s.
4252024-05-01T15:18:17  <PennyEther> Furthermore, miners are INCENTIVIZED to submit blocks with timestamps that cause their peers to continue hashing off of block 100 rather than 100-f. At present, that would be T=1h59m ... because, the code (at present) foolishly drops future blocks. Regardless, If I submit a block 100-f with T+1h59m, I will cause some % of miners (with slow clocks)
4262024-05-01T15:18:17  <PennyEther> to ignore the block. This effectively forks the hashrate between 100 and 100-f.
4272024-05-01T15:18:18  <PennyEther> This provides further benefit (beyond strictly the probability) to mining off of 100-f rather than 100.. because 40% of your peers are wasting their time on 100-f.
4282024-05-01T15:18:18  <PennyEther> Extending this further.. if we assume miners do start acting rationally and do start mining off of block 100-f with T=2h6m, then I believe there are more severe ramifications other than just some drift.
4292024-05-01T15:18:29  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has joined #bitcoin-core-dev
4302024-05-01T15:18:37  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 268 seconds)
4312024-05-01T15:19:04  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
4322024-05-01T15:19:13  <sipa> gmaxwell: both are great; the point of clustermempool is primarily making relay policy capable of reasoning about what is an improvement, though as a side effect it will improve block building itself too
4332024-05-01T15:19:53  <PennyEther> There's my example. Appreciate your thoughts.
4342024-05-01T15:20:19  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
4352024-05-01T15:20:38  <gmaxwell> PennyEther: I think you are using an overly quantized mental model, and thinking of mining as a choice you make block by block.  As a result there is a superior strategy to what you sugget.
4362024-05-01T15:20:42  <gmaxwell> suggest*
4372024-05-01T15:21:25  <gmaxwell> PennyEther: which is that someone can mine on 100 until 101-f becomes valid, and then instantly switch to that.
4382024-05-01T15:21:41  <PennyEther> You are failing to understand the poisson distribution.
4392024-05-01T15:21:59  <PennyEther> That is not a superior strategy
4402024-05-01T15:22:02  <gmaxwell> and that is superior, I say, to mining on 101-f, unless the 101-f' miners have enough power to get it two ahead before 101-a is found.
4412024-05-01T15:22:23  <PennyEther> No. 101-f will most likely become valid BEFORE 101-a is found.
4422024-05-01T15:22:27  <PennyEther> regardless of hashrate on 101-f
4432024-05-01T15:22:46  <PennyEther> In 6 minutes, it will simply be resubmitted and accepted.
4442024-05-01T15:22:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4452024-05-01T15:23:18  <gmaxwell> PennyEther: perhaps you should not concern yourself so much with what I do or don't understand.
4462024-05-01T15:23:48  <gmaxwell> I know you probably live your life in frustration of people who are completely uncomfortable with statistics, but please trust me for a moment that I am not one of them.
4472024-05-01T15:23:58  <PennyEther> heard.
4482024-05-01T15:24:01  <gmaxwell> :)
4492024-05-01T15:24:05  <PennyEther> So, you agree that 101-f is more likely become valid before 101-a is found?
4502024-05-01T15:24:25  <gmaxwell> Yes.
4512024-05-01T15:24:38  <PennyEther> Ok, I didn't think you understood that, my apologies.
4522024-05-01T15:24:50  <PennyEther> Having that understanding, why do you believe that mining off of 101-f is an inferior strategy?
4532024-05-01T15:24:52  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
4542024-05-01T15:25:05  <gmaxwell> though most blocks will be found in less time than the expectation thanks to the distribution, but I don't think that matters for this discussion)
4552024-05-01T15:26:00  <PennyEther> ~50% of blocks will be found in under 6m57s, which is why I go with T=2h+6m .. to be sure it's >50%
4562024-05-01T15:26:01  <gmaxwell> PennyEther: Lets imagine you and I adopt opposing strategies. I will mine on 100 until 101-f is valid. You will just mine on 101-f.
4572024-05-01T15:26:09  <PennyEther> Sure.
4582024-05-01T15:26:34  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
4592024-05-01T15:27:04  <gmaxwell> PennyEther: so if I find a block anywhere from the arrivial time until 101-f's validity, the network will be working on extending my block.  At 101-f's validity time we become the same.
4602024-05-01T15:27:34  <PennyEther> I would switch to your block if you found it first.
4612024-05-01T15:27:51  <PennyEther> If you find 101-a, I'll switch to 101-a.
4622024-05-01T15:28:02  <PennyEther> Most of the time, you will not find 101-a first
4632024-05-01T15:28:20  <gmaxwell> no but I'm not harmed by trying, and I do sometimes find it first.
4642024-05-01T15:29:05  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
4652024-05-01T15:29:25  <gmaxwell> so I say it's only an advatnage to mine on 101f prematurely if I (and other timestamp ignoring nodes) have enough hashpower that when 101f becomes valid my fork will win even against a tie, e.g. that it'll have a one block advantage.
4662024-05-01T15:30:00  <gmaxwell> and without that I'm better off staying on 100 until 101f is valid and instantly switching when its valid.
4672024-05-01T15:30:21  <PennyEther> Ok, I agree
4682024-05-01T15:30:41  <PennyEther> Actually, I disagree.
4692024-05-01T15:31:06  <PennyEther> LOL ok let me think
4702024-05-01T15:31:29  <gmaxwell> so I think the system has multiple equibrium: 100 and instant switch is a domant strategy until some threshold hashpower is willing to mine in the future.   But I might be reasoning excessively from the selfish mining results, and be incorrect. :)
4712024-05-01T15:32:29  <PennyEther> I think you are correct to mine off of 100.. if you find a block, you 100% keep it. If you find a block on 101-f, you only 51% (but increasing through time) get to keep it.
4722024-05-01T15:33:10  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4732024-05-01T15:33:59  <PennyEther> Now how do things change with 101-f having T+2h1s
4742024-05-01T15:34:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
4752024-05-01T15:35:16  <PennyEther> Do we assume that in 2s everyone will see 101-f again and accept it?
4762024-05-01T15:35:30  <gmaxwell> aside, I think you're also right that in theory miners should be keeping the block (and switching as I suggest) at least when it becomes valid: but so long as no one produces such blocks, there is no reason to implement it. And so long as that logic isn't implemented there is very good reason to not produce such blocks (perhaps still reason to not produce even if miners would switch).
4772024-05-01T15:35:55  <instagibbs> the "attacking" miner can always resend the block as soon as it matures, seems straight forward enough
4782024-05-01T15:36:18  <gmaxwell> PennyEther: well the current behavior in the network is that everyone will continue to ignore 101-f unless at some point after it becomes valid someone relays a child block on 101f and then they'll take both (with somewhat slower propagation)
4792024-05-01T15:36:40  <gmaxwell> yes, and they could resend to make that happem though it doesn't currently happen automatically.
4802024-05-01T15:37:33  <PennyEther> Could you explain to me why a miner would NOT submit 101-f with a timestamp of T+1h59m59s?  It would appear strictly advantageous to "trick" the hashrate with slower clocks to continue on block 100, while the majority will carry on with 101-f
4812024-05-01T15:37:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4822024-05-01T15:38:59  <PennyEther> If the concern is their block might get rejected, they can choose a T+1h59m58s... or "low" enough timestamp that they are certain consensus agrees with them
4832024-05-01T15:39:15  <sipa> PennyEther: i'm not following entirely, but just to make sure this isn't a misunderstanding: miners need to decide on the timestamp of the block template before attempting to mine on it; it can't be changed after the fact
4842024-05-01T15:39:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
4852024-05-01T15:39:30  <gmaxwell> because you want your block to be continued, as your block may be (unknown to you) in a race which is only decided by the next block found after yours.
4862024-05-01T15:39:45  <PennyEther> sipa: yes, I understand. they can adjust the timestamp as they mine, such that if found T= T+1h59m59s
4872024-05-01T15:39:59  <gmaxwell> PennyEther: yeah your use of the word submit was probably causing sipa concern.
4882024-05-01T15:40:26  <sipa> PennyEther: indeed; in that case ignore my comment :)
4892024-05-01T15:41:06  <gmaxwell> PennyEther: so for the same reason the selfish mining paper claims, if you have low hashrate relative to the network you very much wnat everyone else trying to continue your block ASAP to make sure you're the winner in a race.
4902024-05-01T15:41:39  <gmaxwell> For sufficiently high hashpowers this incentive reverses, and you are better off to 'withhold' your block.
4912024-05-01T15:41:48  <PennyEther> I see. Let me play out an example, please correct me where I'm wrong
4922024-05-01T15:42:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
4932024-05-01T15:43:37  <PennyEther> Let's say you mine block 101-f with T such that you think 90% of the hashrate will accept your block (eg: their clocks arent slow).  Eg: T=1h50m. The disadvantage here is that 10% are still hashing on 100, and they might find 101-b. In which case, what happens? 101-f has 90%, 101-b has 10%.
4942024-05-01T15:44:17  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
4952024-05-01T15:44:55  <PennyEther> Still seems to me an incentive to let timestamp drift up to near the T=2h mark.
4962024-05-01T15:45:04  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
4972024-05-01T15:45:29  <gmaxwell> PennyEther: also imagine someone else finds a block effecitvely concurrent with you and that you've done this. They will end up with more hashrate trying to continue their block than you have.
4982024-05-01T15:45:34  *** pablomartin4btc <pablomartin4btc!~pablomart@185.216.146.253> has joined #bitcoin-core-dev
4992024-05-01T15:45:35  <gmaxwell> so they are more likely to win the race.
5002024-05-01T15:47:16  <gmaxwell> But if your hashpower is very great, then you plus the percentage you've carved off with your timestamp and won in propagation, will have more hashpower behind it than the other honestly stampped block.  So in that case it's an advantage.
5012024-05-01T15:48:03  <achow101> oh hey, gmaxwell, long time no see
5022024-05-01T15:48:24  <gmaxwell> Hi Ava!
5032024-05-01T15:51:46  <gmaxwell> PennyEther: considering your example, I think differences in node timesync on that boundary have a similar effect on mining fairness that propagation times do.
5042024-05-01T15:52:37  <gmaxwell> in other works, I think nodes having clocks that differ by 10 seconds is a lot like nodes taking 10 second to propagate a block, -- in the presense of blocks that are right up on the boundary.
5052024-05-01T15:52:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5062024-05-01T15:53:34  <PennyEther> gmaxwell: why would somebody else finding a block end up with more hashrate? I chose a value of T < 2h in this case
5072024-05-01T15:53:54  <PennyEther> block 101-f should be accepted by the vast majority (eg: 90%)
5082024-05-01T15:54:21  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5092024-05-01T15:54:36  <gmaxwell> PennyEther: yeah I understand you've assumed that timestamps are desynced enough on miners such that you can carve off 90% through your timestamp choice.
5102024-05-01T15:55:09  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
5112024-05-01T15:55:41  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5122024-05-01T15:55:44  <gmaxwell> PennyEther: but say I'm mining and then sometime shortly before or shortly after you, I find a block and mine is timed normally. I'm obviously acceptable to the 10% that reject you so I should get all of them.  I'll also get whatever share of other nodes I'd othrewise get in a race with you (so lots of them if I was first, few if you were first).
5132024-05-01T15:56:13  <gmaxwell> so your decision to push your timestamp hurt you in the race with me.
5142024-05-01T15:58:27  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
5152024-05-01T15:59:17  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
5162024-05-01T16:01:29  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
5172024-05-01T16:03:41  <PennyEther> I see. So then it's a question of the costs of losing that race condition (which depends on propagation time distribution), vs the benefits of carving off 10% of hashrate for some period. Correct?
5182024-05-01T16:04:56  <gmaxwell> yeah well also the carving off the hashrate doesn't directly benefit you I think: it causes them a higher orphaning rate. which then only benefits you after it cases a reduction in difficulty.
5192024-05-01T16:05:43  <gmaxwell> (even more than your other situation this one is exactly the pattern discussed in the selfish mining paper, except using the timestamps to cause blocks to be withheld from some miners)
5202024-05-01T16:06:09  *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 252 seconds)
5212024-05-01T16:06:35  <PennyEther> true, it does not directly benefit me if others are hashing less. I am competing against difficulty.
5222024-05-01T16:06:38  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5232024-05-01T16:07:19  <gmaxwell> so essentially you take on more race loss risk in exchange for making some othre miners have higher orphan rates. So this may not look too good if hashrate is increasing overall because you've forgone some lower difficulty income for some higher (but still reduced from what it would have been) difficulty income later.
5242024-05-01T16:08:28  <PennyEther> also the decrease in difficulty would only be a 1 shot deal over all of time, correct?  just an extra ~2h in one difficulty period.
5252024-05-01T16:08:46  <PennyEther> the end result is just a ~2hr forward drift in timestamps, and that's it
5262024-05-01T16:09:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5272024-05-01T16:10:32  <gmaxwell> ah: two things: the forward timestamp thing only lets you get 2hours once (ignoring the timewarp attack which is another matter). Yes, but above I wasn't referring to that.  I mean the result of partitoing off that 10% is that sometimes they get two blocks and win, but more often they get none (no effect) or 1 block, in which case their one block gets orphaned. They have a higher orphan rate.
5282024-05-01T16:10:38  <gmaxwell> This doesn't directly profit you but it means takes longer for the network to mine 2016 blocks and so difficulty is reduced.
5292024-05-01T16:11:40  *** zeropoint <zeropoint!~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net> has joined #bitcoin-core-dev
5302024-05-01T16:13:18  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5312024-05-01T16:14:30  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5322024-05-01T16:17:58  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5332024-05-01T16:18:09  *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
5342024-05-01T16:19:08  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5352024-05-01T16:21:18  <PennyEther> Correct. Thank you for the distinction
5362024-05-01T16:21:29  *** S3RK <S3RK!~S3RK@user/s3rk> has joined #bitcoin-core-dev
5372024-05-01T16:23:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5382024-05-01T16:23:07  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
5392024-05-01T16:24:23  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5402024-05-01T16:24:36  *** S3RK_ <S3RK_!~S3RK@user/s3rk> has quit IRC (Ping timeout: 260 seconds)
5412024-05-01T16:24:48  *** cguida <cguida!~cguida@207.91.133.10> has joined #bitcoin-core-dev
5422024-05-01T16:25:04  <PennyEther> So, to recap:  Choosing 101-f having T=2h5m is not a good strategy simply because most miners will ignore it, and if there's a block 101-a that comes in before hand, they'll switch to that one, and you'll lose the race between 102-f and 102-a
5432024-05-01T16:26:59  <gmaxwell> Yes until it's valid, in which case it would be good to switch. it would be rational for miners to implement that logic today but absent any 2h5m blocks it's not worth the cost to code/test/etc.
5442024-05-01T16:27:20  <PennyEther> Presumably the submitter would resubmit after 5m, anyway
5452024-05-01T16:27:28  <gmaxwell> haha
5462024-05-01T16:27:30  <gmaxwell> they should.
5472024-05-01T16:27:41  <PennyEther> gmaxwell, thank you very much for exploring this with me
5482024-05-01T16:27:52  <gmaxwell> But same kind of logic applies: absent this happening, I bet no one has implemented logic to do that.
5492024-05-01T16:28:21  <PennyEther> I'm sorry I accused you of misunderstanding the poisson distribution, I see that the game theory / consensus impact does indeed outweigh the probability aspect
5502024-05-01T16:28:24  <gmaxwell> (while you were out I quipped that miners routinely leave thousands of dollars in fees on the table that they could have taken with moderately smarter transaction selection code)
5512024-05-01T16:28:31  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has quit IRC (Remote host closed the connection)
5522024-05-01T16:28:56  <instagibbs> I suppose for selfish mining mitigations(DAG ones) you'd aggregate the future blocks into your tip to not have difficulty reduce?
5532024-05-01T16:28:56  <gmaxwell> PennyEther: oh no offense taken. I just wanted to move the discussion over to areas that I was more likely to have misunderstood.
5542024-05-01T16:29:09  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5552024-05-01T16:29:16  <PennyEther> very prudent, it work out. thanks again.
5562024-05-01T16:29:21  <PennyEther> *worked
5572024-05-01T16:29:34  <gmaxwell> PennyEther: and indeed, I thought it was an interesting discussion too.
5582024-05-01T16:29:51  <instagibbs> +1
5592024-05-01T16:29:57  <gmaxwell> instagibbs: well whats your incentive to mine a orphan marker? it'll increase difficulty! :P
5602024-05-01T16:30:18  <instagibbs> non-attacker? same reason as the uncle stuff I'd think
5612024-05-01T16:30:26  <instagibbs> (it's been way too long since ive read hte literature)
5622024-05-01T16:30:31  <gmaxwell> instagibbs: ethereum gave people reward for this and I understand that people gamed it by intentionally maxing out the orphan rate to increase the yield.
5632024-05-01T16:30:47  <gmaxwell> and so they cut back the reward significantly eventually.
5642024-05-01T16:30:57  <instagibbs> it was *really* broken when it didn't add the uncles into the difficulty retarget
5652024-05-01T16:31:19  <instagibbs> sounds plausible :)
5662024-05-01T16:32:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5672024-05-01T16:34:17  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5682024-05-01T16:34:20  *** cguida <cguida!~cguida@207.91.133.10> has quit IRC (Remote host closed the connection)
5692024-05-01T16:34:44  *** cguida <cguida!~cguida@207.91.133.10> has joined #bitcoin-core-dev
5702024-05-01T16:37:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5712024-05-01T16:37:40  *** Guest72 <Guest72!~Guest72@c-98-242-73-156.hsd1.ga.comcast.net> has joined #bitcoin-core-dev
5722024-05-01T16:39:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5732024-05-01T16:43:10  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5742024-05-01T16:44:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5752024-05-01T16:46:31  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has joined #bitcoin-core-dev
5762024-05-01T16:47:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5772024-05-01T16:48:12  *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
5782024-05-01T16:50:22  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5792024-05-01T16:52:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5802024-05-01T16:54:06  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5812024-05-01T16:57:54  *** cguida <cguida!~cguida@207.91.133.10> has quit IRC (Ping timeout: 268 seconds)
5822024-05-01T16:58:06  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5832024-05-01T17:01:50  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
5842024-05-01T17:02:20  *** Guest31 <Guest31!~Guest31@2a01:c23:8ccd:1d00:5ad:c935:190c:1d9c> has joined #bitcoin-core-dev
5852024-05-01T17:02:41  *** Guest72 <Guest72!~Guest72@c-98-242-73-156.hsd1.ga.comcast.net> has quit IRC (Quit: Client closed)
5862024-05-01T17:06:19  *** Guest62 <Guest62!~Guest62@pool-108-56-232-226.washdc.fios.verizon.net> has joined #bitcoin-core-dev
5872024-05-01T17:06:34  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5882024-05-01T17:06:43  *** Guest62 <Guest62!~Guest62@pool-108-56-232-226.washdc.fios.verizon.net> has quit IRC (Client Quit)
5892024-05-01T17:09:26  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5902024-05-01T17:11:56  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
5912024-05-01T17:14:04  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5922024-05-01T17:18:10  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5932024-05-01T17:19:32  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5942024-05-01T17:22:08  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
5952024-05-01T17:22:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5962024-05-01T17:22:45  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
5972024-05-01T17:24:43  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
5982024-05-01T17:27:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
5992024-05-01T17:29:10  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6002024-05-01T17:32:16  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
6012024-05-01T17:32:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6022024-05-01T17:32:49  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6032024-05-01T17:34:12  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6042024-05-01T17:38:14  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6052024-05-01T17:38:39  <bitcoin-git> [bitcoin] Shaxrux1811 opened pull request #30015: Initial commit (master...codespace-opulent-telegram-976vjqwrwgrgh7477) https://github.com/bitcoin/bitcoin/pull/30015
6062024-05-01T17:39:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6072024-05-01T17:42:29  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
6082024-05-01T17:42:29  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
6092024-05-01T17:43:10  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6102024-05-01T17:44:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6112024-05-01T17:48:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6122024-05-01T17:49:07  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6132024-05-01T17:49:42  *** cguida <cguida!~cguida@207.91.133.10> has joined #bitcoin-core-dev
6142024-05-01T17:52:41  <bitcoin-git> [bitcoin] achow101 closed pull request #30015: Initial commit (master...codespace-opulent-telegram-976vjqwrwgrgh7477) https://github.com/bitcoin/bitcoin/pull/30015
6152024-05-01T17:52:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6162024-05-01T17:54:16  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6172024-05-01T17:56:11  *** cguida <cguida!~cguida@207.91.133.10> has quit IRC (Ping timeout: 268 seconds)
6182024-05-01T17:57:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6192024-05-01T17:59:13  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6202024-05-01T18:01:20  *** Guest23 <Guest23!~Guest23@2607:fb90:d72d:cdc8:4959:7f12:4e11:b718> has joined #bitcoin-core-dev
6212024-05-01T18:02:58  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6222024-05-01T18:04:05  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6232024-05-01T18:04:22  *** Guest23 <Guest23!~Guest23@2607:fb90:d72d:cdc8:4959:7f12:4e11:b718> has quit IRC (Client Quit)
6242024-05-01T18:07:38  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6252024-05-01T18:09:09  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6262024-05-01T18:12:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6272024-05-01T18:14:01  *** Guest31 <Guest31!~Guest31@2a01:c23:8ccd:1d00:5ad:c935:190c:1d9c> has quit IRC (Quit: Client closed)
6282024-05-01T18:14:12  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6292024-05-01T18:15:27  *** ion- <ion-!ion-@user/ion-> has quit IRC (Remote host closed the connection)
6302024-05-01T18:17:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6312024-05-01T18:19:07  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6322024-05-01T18:21:19  <bitcoin-git> [bitcoin] laanwj closed pull request #30014: doc: Remove outdated description for --port argument (master...master) https://github.com/bitcoin/bitcoin/pull/30014
6332024-05-01T18:22:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6342024-05-01T18:24:04  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6352024-05-01T18:27:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6362024-05-01T18:28:51  *** mcey_ <mcey_!~emcy@85.255.233.75> has joined #bitcoin-core-dev
6372024-05-01T18:29:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6382024-05-01T18:31:54  *** mcey <mcey!~emcy@92.40.199.119.threembb.co.uk> has quit IRC (Ping timeout: 252 seconds)
6392024-05-01T18:32:22  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6402024-05-01T18:32:41  *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
6412024-05-01T18:34:01  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6422024-05-01T18:37:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6432024-05-01T18:38:56  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6442024-05-01T18:39:38  <bitcoin-git> [bitcoin] kevkevinpal closed pull request #29994: doc: removed help text saying that peers may not connect automatically (master...docsRemoveNetNote) https://github.com/bitcoin/bitcoin/pull/29994
6452024-05-01T18:41:20  *** ion- <ion-!ion-@user/ion-> has quit IRC (Ping timeout: 260 seconds)
6462024-05-01T18:42:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6472024-05-01T18:44:21  <bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/842f7fdf786f...d73245abc703
6482024-05-01T18:44:22  <bitcoin-git> bitcoin/master e504b1f Brandon Odiwuor: test: Add test case for spending bare multisig
6492024-05-01T18:44:23  <bitcoin-git> bitcoin/master d73245a merge-script: Merge bitcoin/bitcoin#29120: test: Add test case for spending bare multisig
6502024-05-01T18:44:29  <bitcoin-git> [bitcoin] achow101 merged pull request #29120: test: Add test case for spending bare multisig (master...spending-bare-multisig) https://github.com/bitcoin/bitcoin/pull/29120
6512024-05-01T18:46:15  *** ion- <ion-!ion-@user/ion-> has joined #bitcoin-core-dev
6522024-05-01T18:47:18  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6532024-05-01T18:51:39  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6542024-05-01T18:54:14  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6552024-05-01T18:55:21  *** ion- <ion-!ion-@user/ion-> has quit IRC ()
6562024-05-01T18:57:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6572024-05-01T19:00:54  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6582024-05-01T19:02:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6592024-05-01T19:04:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6602024-05-01T19:07:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6612024-05-01T19:09:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6622024-05-01T19:11:17  *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
6632024-05-01T19:12:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6642024-05-01T19:14:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6652024-05-01T19:17:38  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6662024-05-01T19:19:16  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6672024-05-01T19:22:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6682024-05-01T19:24:24  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6692024-05-01T19:27:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6702024-05-01T19:29:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6712024-05-01T19:33:02  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6722024-05-01T19:34:03  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6732024-05-01T19:37:29  *** cguida <cguida!~cguida@207.91.133.9> has joined #bitcoin-core-dev
6742024-05-01T19:37:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6752024-05-01T19:39:22  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6762024-05-01T19:40:57  *** cguida_ <cguida_!~cguida@207.91.133.10> has joined #bitcoin-core-dev
6772024-05-01T19:42:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6782024-05-01T19:44:06  *** cguida <cguida!~cguida@207.91.133.9> has quit IRC (Ping timeout: 268 seconds)
6792024-05-01T19:44:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6802024-05-01T19:47:08  *** the_mariner <the_mariner!~Thunderbi@179.180.141.11> has quit IRC (Ping timeout: 260 seconds)
6812024-05-01T19:47:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6822024-05-01T19:49:08  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6832024-05-01T19:50:01  *** cguida_ <cguida_!~cguida@207.91.133.10> has quit IRC (Ping timeout: 246 seconds)
6842024-05-01T19:52:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6852024-05-01T19:54:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6862024-05-01T19:57:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6872024-05-01T19:58:59  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6882024-05-01T20:02:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6892024-05-01T20:04:07  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6902024-05-01T20:07:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6912024-05-01T20:09:04  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6922024-05-01T20:12:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6932024-05-01T20:14:05  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6942024-05-01T20:16:04  *** VonNaturAustreVe <VonNaturAustreVe!~ne0h_@user/vonnaturaustreve> has quit IRC (Quit: Leaving)
6952024-05-01T20:17:50  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6962024-05-01T20:19:07  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
6972024-05-01T20:22:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
6982024-05-01T20:24:16  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
6992024-05-01T20:27:38  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7002024-05-01T20:29:27  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7012024-05-01T20:29:49  *** Guest64 <Guest64!~Guest64@2804:14d:bac1:466d:8f71:bc2c:2e52:4120> has joined #bitcoin-core-dev
7022024-05-01T20:30:18  *** Guest64 <Guest64!~Guest64@2804:14d:bac1:466d:8f71:bc2c:2e52:4120> has quit IRC (Client Quit)
7032024-05-01T20:32:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7042024-05-01T20:34:03  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7052024-05-01T20:36:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7062024-05-01T20:39:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7072024-05-01T20:42:34  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7082024-05-01T20:44:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7092024-05-01T20:44:20  *** PennyEther <PennyEther!~PennyEthe@user/PennyEther> has quit IRC (Quit: Client closed)
7102024-05-01T20:47:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7112024-05-01T20:49:10  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7122024-05-01T20:52:50  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7132024-05-01T20:54:09  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7142024-05-01T20:57:58  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7152024-05-01T20:59:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7162024-05-01T21:02:26  *** blockdyor <blockdyor!~blockdyor@dynamic-adsl-94-34-196-193.clienti.tiscali.it> has quit IRC (Quit: My iMac has gone to sleep. ZZZzzz…)
7172024-05-01T21:02:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7182024-05-01T21:04:04  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7192024-05-01T21:04:34  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
7202024-05-01T21:09:07  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7212024-05-01T21:12:26  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7222024-05-01T21:13:32  *** cguida_ <cguida_!~cguida@207.91.133.10> has joined #bitcoin-core-dev
7232024-05-01T21:14:02  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7242024-05-01T21:17:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7252024-05-01T21:19:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7262024-05-01T21:19:01  *** cguida_ <cguida_!~cguida@207.91.133.10> has quit IRC (Ping timeout: 272 seconds)
7272024-05-01T21:22:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7282024-05-01T21:24:43  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7292024-05-01T21:27:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7302024-05-01T21:29:14  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7312024-05-01T21:31:04  *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
7322024-05-01T21:32:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7332024-05-01T21:32:34  *** nanotube <nanotube!~nanotube@user/nanotube> has quit IRC (Ping timeout: 246 seconds)
7342024-05-01T21:34:10  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7352024-05-01T21:38:06  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7362024-05-01T21:39:22  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7372024-05-01T21:42:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7382024-05-01T21:44:12  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7392024-05-01T21:47:54  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7402024-05-01T21:49:13  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7412024-05-01T21:49:33  *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
7422024-05-01T21:53:02  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7432024-05-01T21:54:02  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7442024-05-01T21:57:30  *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 4.2.2)
7452024-05-01T21:57:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7462024-05-01T21:59:00  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7472024-05-01T22:01:39  *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
7482024-05-01T22:02:22  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7492024-05-01T22:04:00  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7502024-05-01T22:07:07  *** mudsip <mudsip!~mudsip@user/mudsip> has joined #bitcoin-core-dev
7512024-05-01T22:07:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7522024-05-01T22:09:00  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7532024-05-01T22:12:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7542024-05-01T22:14:04  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7552024-05-01T22:17:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7562024-05-01T22:18:06  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has quit IRC (Remote host closed the connection)
7572024-05-01T22:18:44  *** Lockesmith <Lockesmith!~user@gateway/tor-sasl/lockesmith> has joined #bitcoin-core-dev
7582024-05-01T22:18:58  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7592024-05-01T22:22:26  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7602024-05-01T22:24:20  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7612024-05-01T22:27:34  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7622024-05-01T22:29:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7632024-05-01T22:32:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7642024-05-01T22:33:18  *** mudsip <mudsip!~mudsip@user/mudsip> has quit IRC ()
7652024-05-01T22:33:57  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7662024-05-01T22:37:22  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7672024-05-01T22:42:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7682024-05-01T22:43:09  *** Wronsk <Wronsk!~Wronsk@cust-west-par-46-193-0-235.cust.wifirst.net> has joined #bitcoin-core-dev
7692024-05-01T22:45:43  *** cguida_ <cguida_!~cguida@207.91.133.9> has joined #bitcoin-core-dev
7702024-05-01T22:46:29  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7712024-05-01T22:49:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7722024-05-01T22:51:24  <achow101> #proposedmeetingtopic moderation guidelines
7732024-05-01T22:52:46  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7742024-05-01T22:53:18  <bitcoin-git> [gui-qml] johnny9 opened pull request #400: Introduce Tooltip for the BlockClock navbar button (main...tooltip) https://github.com/bitcoin-core/gui-qml/pull/400
7752024-05-01T22:54:26  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7762024-05-01T22:57:54  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7772024-05-01T22:59:06  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7782024-05-01T22:59:15  *** cguida <cguida!~cguida@207.91.133.9> has joined #bitcoin-core-dev
7792024-05-01T23:02:20  *** cguida_ <cguida_!~cguida@207.91.133.9> has quit IRC (Ping timeout: 256 seconds)
7802024-05-01T23:03:02  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7812024-05-01T23:04:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7822024-05-01T23:04:05  *** cguida <cguida!~cguida@207.91.133.9> has quit IRC (Ping timeout: 245 seconds)
7832024-05-01T23:07:36  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
7842024-05-01T23:07:42  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7852024-05-01T23:08:03  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7862024-05-01T23:09:18  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7872024-05-01T23:09:32  *** msc_ <msc_!~msc@user/msc> has quit IRC (Remote host closed the connection)
7882024-05-01T23:10:00  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7892024-05-01T23:13:18  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7902024-05-01T23:14:00  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7912024-05-01T23:17:30  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7922024-05-01T23:19:03  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7932024-05-01T23:22:38  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7942024-05-01T23:24:01  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
7952024-05-01T23:25:59  *** Wronsk <Wronsk!~Wronsk@cust-west-par-46-193-0-235.cust.wifirst.net> has quit IRC (Remote host closed the connection)
7962024-05-01T23:27:46  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7972024-05-01T23:29:25  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
7982024-05-01T23:32:26  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
7992024-05-01T23:34:09  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
8002024-05-01T23:37:09  *** Saloframes <Saloframes!~Saloframe@user/Saloframes> has quit IRC (Quit: Leaving)
8012024-05-01T23:38:02  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
8022024-05-01T23:39:04  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
8032024-05-01T23:42:42  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
8042024-05-01T23:43:42  <bitcoin-git> [bitcoin] hebasto opened pull request #30017: refactor, fuzz: Make 64-bit shift explicit (master...240501-fix-shift) https://github.com/bitcoin/bitcoin/pull/30017
8052024-05-01T23:44:02  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
8062024-05-01T23:47:22  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
8072024-05-01T23:49:04  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev
8082024-05-01T23:52:30  *** msc <msc!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
8092024-05-01T23:54:06  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
8102024-05-01T23:55:17  *** msc <msc!~msc@user/msc> has quit IRC (Remote host closed the connection)
8112024-05-01T23:55:41  *** msc <msc!~msc@user/msc> has joined #bitcoin-core-dev
8122024-05-01T23:57:38  *** msc_ <msc_!~msc@user/msc> has quit IRC (Ping timeout: 260 seconds)
8132024-05-01T23:58:59  *** msc_ <msc_!~msc@user/msc> has joined #bitcoin-core-dev