12023-05-08T00:02:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
22023-05-08T00:06:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 246 seconds)
32023-05-08T00:21:44 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
42023-05-08T00:40:59 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
52023-05-08T00:45:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
62023-05-08T00:50:12 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
72023-05-08T00:56:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 256 seconds)
82023-05-08T01:07:50 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
92023-05-08T01:26:33 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
102023-05-08T01:30:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 240 seconds)
112023-05-08T01:32:43 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
122023-05-08T01:39:57 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 256 seconds)
132023-05-08T01:45:36 *** test_ <test_!~flooded@146.70.174.163> has joined #bitcoin-core-dev
142023-05-08T01:49:25 *** flooded <flooded!~flooded@146.70.195.83> has quit IRC (Ping timeout: 268 seconds)
152023-05-08T01:58:03 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
162023-05-08T02:02:45 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
172023-05-08T02:14:38 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
182023-05-08T02:19:12 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
192023-05-08T02:36:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
202023-05-08T02:41:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 240 seconds)
212023-05-08T02:48:26 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
222023-05-08T02:52:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
232023-05-08T02:59:12 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
242023-05-08T03:04:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
252023-05-08T03:08:09 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
262023-05-08T03:18:13 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
272023-05-08T03:36:07 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
282023-05-08T03:40:51 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
292023-05-08T03:42:11 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
302023-05-08T03:46:55 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
312023-05-08T03:53:04 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
322023-05-08T03:57:41 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
332023-05-08T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
342023-05-08T04:01:34 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
352023-05-08T04:32:09 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has joined #bitcoin-core-dev
362023-05-08T04:32:25 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
372023-05-08T04:32:56 *** SpellChecker <SpellChecker!~SpellChec@user/SpellChecker> has quit IRC (Ping timeout: 240 seconds)
382023-05-08T04:33:03 *** jonatack <jonatack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
392023-05-08T04:34:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
402023-05-08T04:39:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
412023-05-08T04:41:03 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
422023-05-08T04:45:25 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
432023-05-08T05:05:23 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
442023-05-08T05:09:59 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 265 seconds)
452023-05-08T05:39:10 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
462023-05-08T05:43:37 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 256 seconds)
472023-05-08T05:50:03 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
482023-05-08T05:58:33 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
492023-05-08T06:21:34 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
502023-05-08T06:26:21 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 256 seconds)
512023-05-08T06:43:50 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
522023-05-08T06:48:30 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
532023-05-08T07:05:45 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
542023-05-08T07:10:23 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 264 seconds)
552023-05-08T07:11:50 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
562023-05-08T07:16:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
572023-05-08T07:18:40 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
582023-05-08T07:22:37 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
592023-05-08T07:27:11 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
602023-05-08T07:37:45 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
612023-05-08T08:03:58 *** flooded <flooded!~flooded@146.70.202.51> has joined #bitcoin-core-dev
622023-05-08T08:07:25 *** test_ <test_!~flooded@146.70.174.163> has quit IRC (Ping timeout: 240 seconds)
632023-05-08T08:08:02 *** Guest30 <Guest30!~Guest30@202.134.8.142> has joined #bitcoin-core-dev
642023-05-08T08:11:22 *** Guest30 <Guest30!~Guest30@202.134.8.142> has quit IRC (Client Quit)
652023-05-08T08:12:14 *** Guest30 <Guest30!~Guest30@202.134.8.142> has joined #bitcoin-core-dev
662023-05-08T08:12:39 *** Guest30 <Guest30!~Guest30@202.134.8.142> has left #bitcoin-core-dev
672023-05-08T08:12:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
682023-05-08T08:13:29 *** Guest30 <Guest30!~Guest30@202.134.8.142> has joined #bitcoin-core-dev
692023-05-08T08:14:08 *** Guest30 <Guest30!~Guest30@202.134.8.142> has quit IRC (Client Quit)
702023-05-08T08:17:29 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 265 seconds)
712023-05-08T08:34:44 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
722023-05-08T08:34:48 *** puchka <puchka!~puchka@185.203.122.57> has quit IRC (Ping timeout: 240 seconds)
732023-05-08T08:36:56 *** Guest98 <Guest98!~Guest98@103.152.220.44> has joined #bitcoin-core-dev
742023-05-08T08:40:26 *** Guest98 <Guest98!~Guest98@103.152.220.44> has quit IRC (Client Quit)
752023-05-08T08:40:39 *** Guest98 <Guest98!~Guest98@103.152.220.44> has joined #bitcoin-core-dev
762023-05-08T08:44:10 *** scg <scg!~scg@84.252.114.5> has joined #bitcoin-core-dev
772023-05-08T08:46:39 *** szarka <szarka!~szarka@24-124-20-18-static.midco.net> has joined #bitcoin-core-dev
782023-05-08T08:46:45 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
792023-05-08T08:48:52 *** robszarka <robszarka!~szarka@24-124-20-18-static.midco.net> has quit IRC (Ping timeout: 250 seconds)
802023-05-08T08:51:11 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 264 seconds)
812023-05-08T08:53:51 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has joined #bitcoin-core-dev
822023-05-08T09:05:50 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
832023-05-08T09:11:09 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
842023-05-08T09:12:08 *** puchka <puchka!~puchka@185.203.122.57> has joined #bitcoin-core-dev
852023-05-08T09:19:17 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has quit IRC (Remote host closed the connection)
862023-05-08T09:19:38 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has joined #bitcoin-core-dev
872023-05-08T09:19:52 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has quit IRC (Remote host closed the connection)
882023-05-08T09:20:10 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has joined #bitcoin-core-dev
892023-05-08T09:27:37 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
902023-05-08T09:32:11 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 246 seconds)
912023-05-08T09:39:05 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 240 seconds)
922023-05-08T09:44:26 *** Guest98 <Guest98!~Guest98@103.152.220.44> has quit IRC (Quit: Client closed)
932023-05-08T09:44:59 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
942023-05-08T09:49:50 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 265 seconds)
952023-05-08T09:50:41 *** puchka <puchka!~puchka@185.203.122.57> has quit IRC (Ping timeout: 256 seconds)
962023-05-08T09:55:16 *** puchka <puchka!~puchka@185.203.122.42> has joined #bitcoin-core-dev
972023-05-08T10:01:31 *** jonatack <jonatack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 268 seconds)
982023-05-08T10:01:34 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
992023-05-08T10:03:00 *** Guest98 <Guest98!~Guest98@103.152.220.44> has joined #bitcoin-core-dev
1002023-05-08T10:05:05 *** Guest98 <Guest98!~Guest98@103.152.220.44> has quit IRC (Client Quit)
1012023-05-08T10:06:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1022023-05-08T10:10:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
1032023-05-08T10:17:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1042023-05-08T10:25:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 240 seconds)
1052023-05-08T10:27:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1062023-05-08T10:30:50 *** vyHamii <vyHamii!~vyHamii@27.72.98.102> has quit IRC (Remote host closed the connection)
1072023-05-08T10:32:00 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
1082023-05-08T10:43:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1092023-05-08T10:43:53 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #27594: refactor: Remove unused GetTimeMillis (master...2305-remove-GetTimeMillis-) https://github.com/bitcoin/bitcoin/pull/27594
1102023-05-08T10:48:19 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 260 seconds)
1112023-05-08T10:49:31 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1122023-05-08T10:53:52 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
1132023-05-08T10:54:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1142023-05-08T10:57:37 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1152023-05-08T11:00:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
1162023-05-08T11:06:46 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
1172023-05-08T11:06:48 *** pablomartin4btc_ <pablomartin4btc_!~pablomart@217.146.83.239> has joined #bitcoin-core-dev
1182023-05-08T11:11:39 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 260 seconds)
1192023-05-08T11:13:12 *** test_ <test_!~flooded@146.70.195.83> has joined #bitcoin-core-dev
1202023-05-08T11:16:45 *** flooded <flooded!~flooded@146.70.202.51> has quit IRC (Ping timeout: 268 seconds)
1212023-05-08T11:21:17 *** scg <scg!~scg@84.252.114.5> has quit IRC (Quit: Client closed)
1222023-05-08T11:28:42 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1232023-05-08T11:30:54 *** scg <scg!~scg@84.252.114.5> has joined #bitcoin-core-dev
1242023-05-08T11:31:49 *** AlexandreFerreir <AlexandreFerreir!~alex10ama@2001:470:69fc:105::1:1976> has joined #bitcoin-core-dev
1252023-05-08T11:34:42 <scg> Is my understanding correct?: parity encoded in TapLeaf version is only needed in witness? Seems to me that You do not need to care about it when constructing or signing PSBT. Only when one builds witness is properly encoded parity flag required in TapLeaf version.
1262023-05-08T11:35:05 *** Guest36 <Guest36!~Guest36@85.255.20.235> has joined #bitcoin-core-dev
1272023-05-08T11:35:42 *** Guest36 <Guest36!~Guest36@85.255.20.235> has quit IRC (Client Quit)
1282023-05-08T11:37:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 248 seconds)
1292023-05-08T11:49:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1302023-05-08T11:53:56 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has quit IRC (Ping timeout: 246 seconds)
1312023-05-08T11:57:37 *** puchka <puchka!~puchka@185.203.122.42> has quit IRC (Ping timeout: 256 seconds)
1322023-05-08T12:09:47 *** b_101 <b_101!~robert@216.144.236.70> has quit IRC (Ping timeout: 268 seconds)
1332023-05-08T12:12:45 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
1342023-05-08T12:13:01 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1352023-05-08T12:14:38 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1362023-05-08T12:19:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:b100:c01b:1bc1:a6fb> has joined #bitcoin-core-dev
1372023-05-08T12:20:03 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has quit IRC (Remote host closed the connection)
1382023-05-08T12:20:30 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has joined #bitcoin-core-dev
1392023-05-08T12:37:45 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 240 seconds)
1402023-05-08T12:38:19 *** jon_atack <jon_atack!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1412023-05-08T12:44:19 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 268 seconds)
1422023-05-08T12:47:25 *** pablomartin4btc_ <pablomartin4btc_!~pablomart@217.146.83.239> has quit IRC (Quit: Leaving)
1432023-05-08T12:47:43 *** pablomartin <pablomartin!~pablomart@217.146.83.239> has joined #bitcoin-core-dev
1442023-05-08T13:03:17 *** puchka <puchka!~puchka@185.203.122.49> has joined #bitcoin-core-dev
1452023-05-08T13:05:56 *** Guest98 <Guest98!~Guest98@2a0d:6fc2:5420:6e00:4847:b953:71e7:61e4> has joined #bitcoin-core-dev
1462023-05-08T13:06:56 *** Guest98 <Guest98!~Guest98@2a0d:6fc2:5420:6e00:4847:b953:71e7:61e4> has quit IRC (Client Quit)
1472023-05-08T13:32:42 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has quit IRC (Read error: Connection reset by peer)
1482023-05-08T13:33:44 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has joined #bitcoin-core-dev
1492023-05-08T13:38:54 *** scg <scg!~scg@84.252.114.5> has quit IRC (Quit: Client closed)
1502023-05-08T13:39:42 *** scg <scg!~scg@84.252.114.5> has joined #bitcoin-core-dev
1512023-05-08T13:39:44 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has quit IRC (Read error: Connection reset by peer)
1522023-05-08T13:40:56 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has joined #bitcoin-core-dev
1532023-05-08T13:53:18 *** Guest7550 <Guest7550!~Guest75@cpe-70-119-23-177.tx.res.rr.com> has joined #bitcoin-core-dev
1542023-05-08T13:54:22 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has quit IRC (Ping timeout: 265 seconds)
1552023-05-08T14:01:19 *** ZeroMaster_ <ZeroMaster_!~webirc@87-126-6-81.ip.btc-net.bg> has joined #bitcoin-core-dev
1562023-05-08T14:11:07 *** Guest7550 <Guest7550!~Guest75@cpe-70-119-23-177.tx.res.rr.com> has quit IRC (Quit: Client closed)
1572023-05-08T14:13:16 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/322ec63b0149...26cb32c02d76
1582023-05-08T14:13:17 <bitcoin-git> bitcoin/master d9b54c4 Hennadii Stepanov: msvc: Cleanup after upgrading libsecp256k1 up to 0.3.0
1592023-05-08T14:13:17 <bitcoin-git> bitcoin/master 26cb32c fanquake: Merge bitcoin/bitcoin#27580: msvc: Cleanup after upgrading libsecp256k1 up...
1602023-05-08T14:13:22 <bitcoin-git> [bitcoin] fanquake merged pull request #27580: msvc: Cleanup after upgrading libsecp256k1 up to 0.3.0 (master...230505-cleanup) https://github.com/bitcoin/bitcoin/pull/27580
1612023-05-08T14:21:16 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
1622023-05-08T14:22:22 *** flooded <flooded!~flooded@146.70.202.99> has joined #bitcoin-core-dev
1632023-05-08T14:26:15 *** test_ <test_!~flooded@146.70.195.83> has quit IRC (Ping timeout: 260 seconds)
1642023-05-08T14:45:05 *** scg <scg!~scg@84.252.114.5> has quit IRC (Quit: Client closed)
1652023-05-08T14:48:25 *** preimage <preimage!~halosghos@user/halosghost> has joined #bitcoin-core-dev
1662023-05-08T14:53:22 *** stevenwy37 <stevenwy37!~stevenwy3@103.152.220.44> has quit IRC (Quit: Leaving...)
1672023-05-08T14:56:03 <jamesob> hey, there's no way we can do Github access just to maintain a particular project is there? The assumeutxo board is out of date: https://github.com/bitcoin/bitcoin/projects/11
1682023-05-08T14:57:26 <achow101> jamesob: I can add just you to maintain that
1692023-05-08T14:58:01 <achow101> we can add individuals to each project board's access
1702023-05-08T14:58:16 <achow101> I think
1712023-05-08T14:58:25 <_aj_> need to convert to an org project first, i think?
1722023-05-08T14:59:29 <_aj_> or a non-classic project or whatever
1732023-05-08T14:59:48 <fanquake> yea a couple there we should probably migrate or close
1742023-05-08T15:02:53 *** scg <scg!~scg@84.252.114.5> has joined #bitcoin-core-dev
1752023-05-08T15:07:00 <achow101> migrated the project to https://github.com/orgs/bitcoin/projects/7 and added jamesob to write to it
1762023-05-08T15:08:37 <bitcoin-git> [bitcoin] jamesob opened pull request #27596: assumeutxo (2) (master...assumeutxo) https://github.com/bitcoin/bitcoin/pull/27596
1772023-05-08T15:09:31 <bitcoin-git> [bitcoin] jamesob closed pull request #15606: assumeutxo (master...utxo-dumpload-compressed) https://github.com/bitcoin/bitcoin/pull/15606
1782023-05-08T15:17:05 <instagibbs> https://github.com/bitcoin/bitcoin/issues/27555#issuecomment-1538504504 seems suboptimal, and partially my fault. Looks like fee estimator is returning obviously bogus rates(below min relay), then being over-ridden by mempoolminfee, which gets blown away on restart
1792023-05-08T15:17:24 <instagibbs> (I ack'd the PR that changed the behavior that hid the issue)
1802023-05-08T15:17:40 <jamesob> achow101: thanks
1812023-05-08T15:17:42 *** julien <julien!~julien@2a01:e0a:ab1:22c0:8c06:1816:743f:e9f7> has joined #bitcoin-core-dev
1822023-05-08T15:17:56 <bitcoin-git> [bitcoin] hebasto opened pull request #27598: bench: Add `-sha-implementation` command-line option (master...230508-bench) https://github.com/bitcoin/bitcoin/pull/27598
1832023-05-08T15:18:05 *** julien <julien!~julien@2a01:e0a:ab1:22c0:8c06:1816:743f:e9f7> has quit IRC (Client Quit)
1842023-05-08T15:21:02 *** puchka <puchka!~puchka@185.203.122.49> has quit IRC (Ping timeout: 250 seconds)
1852023-05-08T15:21:40 *** infernix <infernix!nix@spirit.infernix.net> has quit IRC (Quit: ZNC - http://znc.sourceforge.net)
1862023-05-08T15:33:28 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
1872023-05-08T15:51:26 *** jb55 <jb55!~jb55@user/jb55> has joined #bitcoin-core-dev
1882023-05-08T15:53:16 <jb55> my core node was getting spammed with "Cache size (23509456) exceeds total space (15701232)" yesterday and then eventually just stopped working/got stale tip errors until I restarted. first time this has happened, has anyone experienced this?
1892023-05-08T15:57:50 <fjahr> jb55: What do you mean by getting spammed? The log message isn't a big issue by itself afaict. It just means that the cache will need to be flushed to disk. But that doesn't mean we shouldn't look into this of course. What disk do you run this node on?
1902023-05-08T15:59:29 <jb55> fjahr: means it was repeated 100 times or so. slow disk (HDD)
1912023-05-08T16:00:06 <jb55> then it just stopped and started to get stale tip warnings.
1922023-05-08T16:00:23 <jb55> a bit concerning if mempool activity could bring down my node :(
1932023-05-08T16:00:38 <jb55> I assumed that's what the message was about, not sure
1942023-05-08T16:00:47 *** infernix <infernix!nix@spirit.infernix.net> has joined #bitcoin-core-dev
1952023-05-08T16:01:21 <instagibbs> it means it should flush to disk immediately, seeing it repeated that much is sketchy
1962023-05-08T16:02:40 <fjahr> Hmm, yeah, absolutely. Could it be that the cache is growing so fast that it fills up the memory and renders core unable to flush on a slow disk?
1972023-05-08T16:03:54 <ghost43> one of my nodes just got stuck, apparently, 3 blocks ago. https://0bin.net/paste/ErHctHfs#yHXnmymeDKmBdLpqr7IYFZsV3IoX4vrV0UNiLQAB+Tu
1982023-05-08T16:05:21 <instagibbs> "bad-witness-nonce-size" ooh nice
1992023-05-08T16:05:45 <fjahr> summoning cache all stars jamesob, ryanofsky :)
2002023-05-08T16:07:26 <instagibbs> ghost43 looks like you're having repeated timeouts from peers. I've seen more lately, but nothing like that 3 times in a row
2012023-05-08T16:08:58 <provoostenator> ghost43: does getchaintips tell you which block triggered the bad-witness-nonce-size?
2022023-05-08T16:09:03 <ghost43> I have another node I am running addnoded bidirectionally with this one, which is not stuck. I would have hoped they can get blocks from each other :/
2032023-05-08T16:10:12 <ghost43> getchaintips: https://0bin.net/paste/ZmAGjdGW#RIakIpTB+qpdFnyHoxJ+gI2d7QvmvjfVtqH1nnekquI
2042023-05-08T16:10:30 <ghost43> that output looks weird, I doubt there is a branch of len=3
2052023-05-08T16:10:51 <instagibbs> no, your node is trying peers and not getting the block from any of them
2062023-05-08T16:10:53 <sipa> I have the 788807 block as active tio.
2072023-05-08T16:11:00 <sipa> So does forkmonitor.
2082023-05-08T16:11:08 <darosior> Same here. I'm at 78807 on multiple nodes
2092023-05-08T16:11:12 <fanquake> same
2102023-05-08T16:11:12 <darosior> 00000000000000000000f99758df6d2d29953344b4c52749f4b5d8442b4f5b36
2112023-05-08T16:11:24 <instagibbs> miner either made a stoopid block, or someone relayed a malleated block witness data for some reason
2122023-05-08T16:11:38 <sdaftuar> instagibbs: or hardware failure i think?
2132023-05-08T16:11:52 <instagibbs> sdaftuar always a possibility sure
2142023-05-08T16:12:28 <jb55> same
2152023-05-08T16:12:30 <sdaftuar> i'd have to guess hardware failure as most likely. can try to submitblock the hex of what we all think is valid and see if the node takes it
2162023-05-08T16:13:09 <instagibbs> ^ good idea, shove the next block in, see if it takes
2172023-05-08T16:14:09 <sipa> It says headers-only, not invalid.
2182023-05-08T16:14:17 <sdaftuar> malleation would cause that though
2192023-05-08T16:14:22 <sdaftuar> er, what was detected as malleation
2202023-05-08T16:14:25 <sipa> So it has never received the block (except perhaps malleated versions of it).
2212023-05-08T16:14:30 <instagibbs> MUTATED
2222023-05-08T16:14:33 <darosior> I was trying to send you the output of getblock so you can submitblock but i can't find a paste site that accepts such large data
2232023-05-08T16:14:36 <instagibbs> "BLOCK_MUTATED,"
2242023-05-08T16:14:36 <sipa> Mutated.
2252023-05-08T16:14:41 <sipa> Yes.
2262023-05-08T16:14:52 <sipa> But why are all copies mutated?
2272023-05-08T16:15:10 <sipa> Of all the versions ghost43 is receiving?
2282023-05-08T16:15:18 *** MatrixBot123456 <MatrixBot123456!~matrixbot@2001:bc8:1824:bc3::1> has joined #bitcoin-core-dev
2292023-05-08T16:15:20 <provoostenator> So there's no recent invalid block in that getchaintips output. I guess we don't store failures related to maleation?
2302023-05-08T16:15:21 <instagibbs> I'm seeing "Timeout" from his log, not rejection again
2312023-05-08T16:15:25 <provoostenator> (since we want to try again)
2322023-05-08T16:15:43 <instagibbs> provoostenator a peer could stuff logs/state cheaply with BLOCK_MUTATED I think
2332023-05-08T16:15:54 <sdaftuar> instagibbs: oops
2342023-05-08T16:16:19 <provoostenator> Sounds like we should add the block hash to log messages when this happens for easier debugging later.
2352023-05-08T16:16:54 <instagibbs> only behind verbose logging, otherwise it's free to trigger
2362023-05-08T16:17:06 <instagibbs> (IIUC)
2372023-05-08T16:17:27 <instagibbs> sdaftuar what's the oops
2382023-05-08T16:17:43 <sdaftuar> your logging observation!
2392023-05-08T16:17:46 <provoostenator> instagibbs: good poin
2402023-05-08T16:18:30 <provoostenator> But we're already logging this rejection, so adding the hash wouldn't make it worse :-)
2412023-05-08T16:19:05 <instagibbs> ruh roh
2422023-05-08T16:19:07 <instagibbs> ;P
2432023-05-08T16:19:18 <darosior> ghost43: so you can `submitblock`: http://download.darosior.ninja/blocks_for_ghost/
2442023-05-08T16:20:55 <provoostenator> I do not understand the code comment above that check by the way: "The malleation check is ignored; as the transaction tree itself already does not permit it, it is impossible to trigger in the witness tree."
2452023-05-08T16:21:26 <sdaftuar> we don't need to look for transaction duplicates there
2462023-05-08T16:21:42 <provoostenator> In particular what is being "ignored" here.
2472023-05-08T16:22:17 <provoostenator> Oh it's the malleated result from the previous call that we ignore.
2482023-05-08T16:23:36 <sdaftuar> provoostenator: right we don't have to worry about merkle root malleation like we do in CheckBlock, because we've already done those checks
2492023-05-08T16:25:34 <darosior> 2023-04-15T09:27:44Z ERROR: ProcessNewBlock: AcceptBlock FAILED (bad-witness-nonce-size, ContextualCheckBlock : invalid witness reserved value size)
2502023-05-08T16:27:28 <sdaftuar> jb55: how far apart (in timestamps) were you seeing those "cache size" log messages?
2512023-05-08T16:27:33 <jb55> https://jb55.com/s/58818ccccfb21d95.txt
2522023-05-08T16:27:45 <ghost43> can I get some shell help? :D # bitcoin-cli submitblock $(cat block-788803-hex.txt)
2532023-05-08T16:27:45 <ghost43> bash: /usr/local/bin/bitcoin-cli: Argument list too long
2542023-05-08T16:28:26 <provoostenator> I get a couple of those per day too.
2552023-05-08T16:29:15 <sdaftuar> ghost43: oof, you might need to use a different rpc client? someone else here will know better than me
2562023-05-08T16:29:27 <ghost43> I will try curl
2572023-05-08T16:29:37 <instagibbs> ghost43 think the block is too chonky for your shell
2582023-05-08T16:29:58 <provoostenator> ghost43: cat block.txt | bitcoin-cli -stdin submitblock
2592023-05-08T16:30:20 <sipa> cat block | bitcoin-cli -stdin submitblock ?
2602023-05-08T16:30:26 <sipa> Or something like that
2612023-05-08T16:33:17 <ghost43> it accepted 788803 and ~instantly processed the next two blocks on top as well
2622023-05-08T16:33:38 <ghost43> but it is still only on 788805, not sure what it is doing atm
2632023-05-08T16:33:57 <ghost43> (as in it obtained 788804 and 788805 from the p2p network)
2642023-05-08T16:33:59 <provoostenator> I'm guessing we don't hold on to the non-witness part of the block when this happens?
2652023-05-08T16:34:12 <sdaftuar> provoostenator: we don't write the block to disk at all when this happens
2662023-05-08T16:34:36 <instagibbs> ghost43 "Timeout"s I think are mostly unrelated to that
2672023-05-08T16:34:52 <b10c> does it know the headers for the ones after 788805? (see getchaintips)
2682023-05-08T16:34:54 <provoostenator> So it wastes a bit of bandwidth (but so does ping) and a few (cheap) checks each time?
2692023-05-08T16:35:19 <cfields> sdaftuar: sure about that? By my read we would?
2702023-05-08T16:35:20 <sdaftuar> ghost43: did you submitblock for the later blocks as well?
2712023-05-08T16:35:28 <ghost43> oh wait, it is now stuck on the stale chain, the legit fork that happened at 788805
2722023-05-08T16:35:39 <ghost43> sdaftuar: no, I only did it for just 788803
2732023-05-08T16:35:39 <sdaftuar> cfields: hmm, checking
2742023-05-08T16:35:44 <cfields> sdaftuar: admittedly it's been a while since I've dug around in here though :)
2752023-05-08T16:36:13 <b10c> ghost34: on 0000000000000000000313dae7541b4c58e93832ddeaf96f8d6a5b5f8157d494?
2762023-05-08T16:36:27 <ghost43> b10c: yes
2772023-05-08T16:36:54 <ghost43> I can feed it the blocks on the other branch manually I guess
2782023-05-08T16:37:04 <b10c> do you have headers for the other branch?
2792023-05-08T16:37:13 <ghost43> # bitcoin-cli getchaintips
2802023-05-08T16:37:14 <ghost43> [ { "height": 788809, "hash": "00000000000000000003bd977a4ea6978a47d9a88e9adf8be244bc60ed7cd793", "branchlen": 5, "status": "headers-only" },
2812023-05-08T16:37:14 <ghost43> { "height": 788805, "hash": "0000000000000000000313dae7541b4c58e93832ddeaf96f8d6a5b5f8157d494", "branchlen": 0, "status": "active" },
2822023-05-08T16:37:16 <instagibbs> it might fix itself on next block peers get
2832023-05-08T16:37:17 <ghost43> yes it has the headers
2842023-05-08T16:37:20 <instagibbs> oh
2852023-05-08T16:37:45 <instagibbs> check getpeerinfo for "inflight"s? would that be the place?
2862023-05-08T16:37:55 <provoostenator> cfields: SaveBlockToDisk is called after ContextualCheckBlock
2872023-05-08T16:38:23 <b10c> then I had the same issue. It knew the headers but kept timing out while downloading the blocks.
2882023-05-08T16:38:31 *** Guest80 <Guest80!~Guest80@86.121.142.207> has joined #bitcoin-core-dev
2892023-05-08T16:38:33 <sdaftuar> cfields: AcceptBlock is where we store to disk; in that function we invoke ContextualCheckBlock which is what reported the bad-witness-nonce-size error that ghost43 reported. so i don't see how the block could have been stored after that?
2902023-05-08T16:38:34 <fjahr> what, 788805 is still considered active?
2912023-05-08T16:38:46 <instagibbs> one of them is :)
2922023-05-08T16:38:55 <fjahr> ah, because it didn't get the blocks yet
2932023-05-08T16:38:59 <b10c> fjahr: see https://fork.observer/ maybe
2942023-05-08T16:40:14 <cfields> sdaftuar / provoostenator: yep, you're right, I see. thanks to both of you.
2952023-05-08T16:41:29 <fjahr> b10c: I misread "headers-only" for "valid-headers" and that would have been confusing
2962023-05-08T16:41:43 <instagibbs> b10c ghost43 are the stuck nodes listening nodes?
2972023-05-08T16:42:11 <ghost43> yes, it is listening on ipv4 and onion
2982023-05-08T16:43:50 <ghost43> "Timeout downloading block 00000000000000000001081dd49ade1108f0b5415605249804a0a95a8e63a3f6 from peer" in log :/
2992023-05-08T16:43:51 *** Guest80 <Guest80!~Guest80@86.121.142.207> has left #bitcoin-core-dev
3002023-05-08T16:43:54 <instagibbs> I've had no timeouts on my non-listening nodes, anecdotally
3012023-05-08T16:43:55 <sdaftuar> jb55: do you have the last UpdateTip line your node saw before the cache size messages? the end of those UpdateTip lines shows how big your coins cache was at the end of block validation
3022023-05-08T16:43:59 <b10c> instagibbs: yes
3032023-05-08T16:46:07 <ghost43> well, ok, I've restarted bitcoind and it instantly caught up to the tip
3042023-05-08T16:46:21 <sdaftuar> interesting!
3052023-05-08T16:47:05 <fjahr> jb55: do you have a custom maxmempool setting?
3062023-05-08T16:57:22 *** puchka <puchka!~puchka@185.203.122.42> has joined #bitcoin-core-dev
3072023-05-08T16:59:44 <sdaftuar> i'll be afk for a bit, but if someone can open an issue and log some of this i think it's worth more investigation
3082023-05-08T17:02:04 <fjahr> jb55: also, I would be curious if this happened around the time when we had the 2 block reorg ~20h ago, i.e. around 788685-788688
3092023-05-08T17:02:34 <fjahr> I can open an issue if nobody else has started it already
3102023-05-08T17:02:48 <instagibbs> fjahr go ahead
3112023-05-08T17:16:30 *** learner-monad <learner-monad!~ehanneken@user/learner-monad> has joined #bitcoin-core-dev
3122023-05-08T17:18:17 <fjahr> #27599, moving conversation there
3132023-05-08T17:18:18 <gribble> https://github.com/bitcoin/bitcoin/issues/27599 | Node stuck with repeated "Cache size exceeds total space" log message · Issue #27599 · bitcoin/bitcoin · GitHub
3142023-05-08T17:29:56 <ghost43> my bitcoind got stuck again on 788809, due to "Timeout downloading block", so basically after the restart it caught up to tip fast and then it failed to download any subsequent blocks. (now tip is 788812) now I've restarted and again it caught up very fast to current tip...
3152023-05-08T17:31:33 *** test_ <test_!~flooded@146.70.195.35> has joined #bitcoin-core-dev
3162023-05-08T17:32:08 *** b_101 <b_101!~robert@189.131.30.152> has joined #bitcoin-core-dev
3172023-05-08T17:32:12 <bitcoin-git> [bitcoin] achow101 pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/26cb32c02d76...fa53611cf1b2
3182023-05-08T17:32:13 <bitcoin-git> bitcoin/master bd13dc2 Sjors Provoost: Switch hardened derivation marker to h in descriptors
3192023-05-08T17:32:13 <bitcoin-git> bitcoin/master fe49f06 Sjors Provoost: doc: clarify PR 26076 release note
3202023-05-08T17:32:13 <bitcoin-git> bitcoin/master fa53611 Andrew Chow: Merge bitcoin/bitcoin#26076: Switch hardened derivation marker to h
3212023-05-08T17:32:18 <bitcoin-git> [bitcoin] achow101 merged pull request #26076: Switch hardened derivation marker to h (master...2022/09/descriptors_h) https://github.com/bitcoin/bitcoin/pull/26076
3222023-05-08T17:32:43 <bugs_> hopefully its just network bandwidth problems and not a new sybil
3232023-05-08T17:34:15 <achow101> ghost43: are you seeing a lot of cpu usage?
3242023-05-08T17:34:48 *** flooded <flooded!~flooded@146.70.202.99> has quit IRC (Ping timeout: 240 seconds)
3252023-05-08T17:36:58 <fjahr> ghost43: please take note of the peers you are connected to. Have you tried to connect to a new, public node to see if that changes anything?
3262023-05-08T17:37:06 <ghost43> achow101: not really. server has 8 virtual cpus (I think 4 real cores, times two SMT), load averages below 2.0
3272023-05-08T17:38:11 <ghost43> bugs_: it cannot be sybilled in the naive sense because I have addnoded other nodes I control and they are running fine
3282023-05-08T17:38:29 <ghost43> btw it logged "ERROR: AcceptBlock: bad-witness-nonce-size, ContextualCheckBlock : invalid witness reserved value size" again
3292023-05-08T17:38:51 <achow101> just on the block you got stuck on?
3302023-05-08T17:39:57 <bugs_> ah it might have gotten stuck on an ht core
3312023-05-08T17:40:37 <bugs_> ht core gets no cycles if the real cores are running sufficiently optimized code
3322023-05-08T17:40:38 <fjahr> ghost43: could it be that the server host or their providers are blocking bitcoin traffic? Or do you have other nodes on servers in the same infra that don't have the issue?
3332023-05-08T17:40:41 <ghost43> achow101: I think so because the tip was 788812 and it had header for 788813, and it logged that line then; however the log does not say which block height or hash the error is for
3342023-05-08T17:40:48 <bugs_> i always disable HT
3352023-05-08T17:41:38 <ghost43> this is a hetzner server with 1810 days uptime; I doubt its peering issues. last time I restarted it was when I dist-upgraded to ubuntu 18.04 when that got released :D
3362023-05-08T17:41:44 <instagibbs> that sounds like hardware failure or a sybil attacker which has figured out how to stall you out by mutating a tx (sounds like hardware ...)
3372023-05-08T17:41:44 <achow101> was it the same peer as before?
3382023-05-08T17:41:54 <instagibbs> mutating a block*
3392023-05-08T17:42:45 <bugs_> i had heard heztner decided to become crypto unfriendly a few months ago
3402023-05-08T17:43:02 <achow101> being able to see the block itself would also be interesting
3412023-05-08T17:43:04 <fjahr> ok, I mean hetzner has said that they don't want crypto stuff but if they had started to block traffic widely we would hear more complaints
3422023-05-08T17:43:13 <bugs_> but i'd definetly try turning off ht thats my bet
3432023-05-08T17:43:28 <bugs_> there is a way to do it in linux without rebooting
3442023-05-08T17:43:51 <sipa> @bugs_ That really seems unrelated.
3452023-05-08T17:43:59 <bugs_> but turning it off in the vbios is best
3462023-05-08T17:44:33 <bugs_> if something that owns a lock gets scheduled on an ht core bad things can happen
3472023-05-08T17:44:40 <bugs_> like an nfs lock
3482023-05-08T17:44:44 <ghost43> but it's been running like this for *years*, it cannot be ht :P
3492023-05-08T17:44:59 <ghost43> anyway, I am running the unreleased 24.0.0, if that matters; so I'll just upgrade to the v25.0rc1 tag, and also do a dist-upgrade from this ancient ubuntu (though that's only the host, the docker container running bitcoind is modern), and see if the hang reappears after that
3502023-05-08T17:46:24 <instagibbs> run in non-listening mode
3512023-05-08T17:46:51 <achow101> maybe also run tcpdump to catch the block data?
3522023-05-08T17:47:00 <jb55> sdaftuar: unfortunately no this is just a tmux backbuffer since I was rebuilding my utxo due to some kind of leveldb corruption. wasn't my main systemd logs. @fjahr: I don't have any custom maxmempool settings. This started happening 20hrs ago yes when mempool was hot
3532023-05-08T17:49:59 <jb55> sdaftuar: earliest log line I have of the cache spam thing is 2023-05-07T17:21:08Z
3542023-05-08T17:55:25 <fjahr> ghost43: I don't think the 24.0.1 fixes are related (#26616 if anyone else wants to check)
3552023-05-08T17:55:27 <gribble> https://github.com/bitcoin/bitcoin/issues/26616 | [24.x] Backports for 24.0.1 by fanquake · Pull Request #26616 · bitcoin/bitcoin · GitHub
3562023-05-08T18:04:15 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
3572023-05-08T18:13:23 *** pablomartin <pablomartin!~pablomart@217.146.83.239> has quit IRC (Ping timeout: 264 seconds)
3582023-05-08T18:44:12 <jamesob> One thought for jb55's issue: FlushStateToDisk ultimately issues the log he's getting spammed with, and the coins cache flush there is gated `by if (fDoFullFlush && !CoinsTip().GetBestBlock().IsNull())` (with no corresponding log in the `else`), so his coinstip's bestblock somehow got nullified, he'd be in a position where the cache gets critical
3592023-05-08T18:44:13 <jamesob> but doesn't get flushed
3602023-05-08T18:44:46 <jamesob> *so if his coinstip's bestblock
3612023-05-08T18:46:10 <jamesob> but the only way I can see that happening is exceptionally unlucky memory fault?
3622023-05-08T18:51:04 <jamesob> I forgot that every ATMP call also calls FlushStateToDisk(..., PERIODIC)
3632023-05-08T19:02:03 *** test_ <test_!~flooded@146.70.195.35> has quit IRC (Ping timeout: 256 seconds)
3642023-05-08T19:08:43 *** vincenzopalazzo <vincenzopalazzo!~vincenzop@2001:470:69fc:105::a67> has joined #bitcoin-core-dev
3652023-05-08T19:25:06 *** scg <scg!~scg@84.252.114.5> has quit IRC (Quit: Client closed)
3662023-05-08T19:33:06 *** Dionysus <Dionysus!~dio_ny_su@c-24-34-165-90.hsd1.ma.comcast.net> has joined #bitcoin-core-dev
3672023-05-08T19:35:18 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
3682023-05-08T19:39:06 *** Dionysus <Dionysus!~dio_ny_su@c-24-34-165-90.hsd1.ma.comcast.net> has quit IRC ()
3692023-05-08T19:59:42 <bitcoin-git> [bitcoin] pinheadmz opened pull request #27600: Make peer eviction slightly more aggresive to make room for whitelisted inbound connections (master...whitebind-evict) https://github.com/bitcoin/bitcoin/pull/27600
3702023-05-08T20:16:18 *** jarthur <jarthur!~jarthur@user/jarthur> has joined #bitcoin-core-dev
3712023-05-08T20:59:18 <jb55> jamesob: what is ATMP
3722023-05-08T21:02:06 *** chutner <chutner!~chutner@128-092-219-162.biz.spectrum.com> has joined #bitcoin-core-dev
3732023-05-08T21:02:53 <instagibbs> AcceptToMemPool
3742023-05-08T21:02:58 <jb55> ah k
3752023-05-08T21:03:58 <bitcoin-git> [bitcoin] furszy opened pull request #27601: wallet: don't duplicate change output if already exist (master...2023_wallet_double_change_output) https://github.com/bitcoin/bitcoin/pull/27601
3762023-05-08T21:06:14 *** chutner <chutner!~chutner@128-092-219-162.biz.spectrum.com> has quit IRC (Client Quit)
3772023-05-08T21:23:45 <bitcoin-git> [bitcoin] sr-gi opened pull request #27602: net: avoid serving non-announced txs as a result of a MEMPOOL message (master...mempool-not-inved) https://github.com/bitcoin/bitcoin/pull/27602
3782023-05-08T22:02:51 *** preimage <preimage!~halosghos@user/halosghost> has quit IRC (Quit: WeeChat 3.8)
3792023-05-08T22:09:29 *** jackjack <jackjack!~jack@31-209-196-73.dsl.dynamic.simnet.is> has joined #bitcoin-core-dev
3802023-05-08T22:16:25 *** jackjack <jackjack!~jack@31-209-196-73.dsl.dynamic.simnet.is> has quit IRC (Ping timeout: 256 seconds)
3812023-05-08T22:26:53 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
3822023-05-08T22:52:16 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
3832023-05-08T23:05:51 *** andytosh1 <andytosh1!~apoelstra@user/andytoshi> has quit IRC (Quit: leaving)
3842023-05-08T23:12:12 *** Guest9 <Guest9!~Guest9@2600:6c64:7e40:ee8:714d:231a:6207:3349> has joined #bitcoin-core-dev
3852023-05-08T23:12:46 *** Guest9 <Guest9!~Guest9@2600:6c64:7e40:ee8:714d:231a:6207:3349> has quit IRC (Client Quit)
3862023-05-08T23:17:37 *** aielima <aielima!~aielima@user/aielima> has quit IRC (Quit: Ciao)
3872023-05-08T23:20:51 *** SpellChecker_ <SpellChecker_!~SpellChec@user/SpellChecker> has quit IRC (Remote host closed the connection)
3882023-05-08T23:20:51 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has quit IRC (Remote host closed the connection)
3892023-05-08T23:20:52 *** yanmaani1 <yanmaani1!~yanmaani@gateway/tor-sasl/yanmaani> has quit IRC (Remote host closed the connection)
3902023-05-08T23:21:16 *** yanmaani1 <yanmaani1!~yanmaani@gateway/tor-sasl/yanmaani> has joined #bitcoin-core-dev
3912023-05-08T23:21:41 *** ghost43 <ghost43!~ghost43@gateway/tor-sasl/ghost43> has joined #bitcoin-core-dev
3922023-05-08T23:33:08 *** andytoshi <andytoshi!~apoelstra@user/andytoshi> has joined #bitcoin-core-dev