12023-05-02T00:39:54 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
22023-05-02T01:06:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
32023-05-02T01:08:55 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
42023-05-02T01:10:56 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
52023-05-02T01:11:17 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
62023-05-02T01:11:38 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
72023-05-02T01:14:32 *** jarthur_ <jarthur_!~jarthur@user/jarthur> has joined #bitcoin-core-dev
82023-05-02T01:15:23 *** jarthur <jarthur!~jarthur@user/jarthur> has quit IRC (Ping timeout: 260 seconds)
92023-05-02T01:36:37 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 276 seconds)
102023-05-02T01:39:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
112023-05-02T01:44:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 260 seconds)
122023-05-02T02:02:18 *** hsmiths <hsmiths!~Thunderbi@76-240-112-146.lightspeed.irvnca.sbcglobal.net> has quit IRC (Quit: hsmiths)
132023-05-02T02:02:51 *** hsmiths <hsmiths!~Thunderbi@76-240-112-146.lightspeed.irvnca.sbcglobal.net> has joined #bitcoin-core-dev
142023-05-02T02:03:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
152023-05-02T02:06:11 *** hsmiths <hsmiths!~Thunderbi@76-240-112-146.lightspeed.irvnca.sbcglobal.net> has quit IRC (Client Quit)
162023-05-02T02:06:36 *** hsmiths <hsmiths!~Thunderbi@76-240-112-146.lightspeed.irvnca.sbcglobal.net> has joined #bitcoin-core-dev
172023-05-02T02:06:45 *** hsmiths <hsmiths!~Thunderbi@76-240-112-146.lightspeed.irvnca.sbcglobal.net> has left #bitcoin-core-dev
182023-05-02T02:10:23 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
192023-05-02T02:17:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
202023-05-02T02:21:32 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
212023-05-02T02:23:40 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has joined #bitcoin-core-dev
222023-05-02T02:34:19 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
232023-05-02T02:36:14 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
242023-05-02T02:38:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
252023-05-02T02:56:16 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
262023-05-02T03:00:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
272023-05-02T03:07:03 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
282023-05-02T03:12:28 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 265 seconds)
292023-05-02T03:13:02 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
302023-05-02T03:17:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
312023-05-02T03:21:02 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has quit IRC (Ping timeout: 250 seconds)
322023-05-02T03:21:39 *** PaperSword <PaperSword!~Thunderbi@securemail.qrsnap.io> has joined #bitcoin-core-dev
332023-05-02T03:30:22 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
342023-05-02T03:40:18 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
352023-05-02T03:49:43 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
362023-05-02T04:01:01 *** cmirror <cmirror!~cmirror@4.53.92.114> has quit IRC (Remote host closed the connection)
372023-05-02T04:01:34 *** cmirror <cmirror!~cmirror@4.53.92.114> has joined #bitcoin-core-dev
382023-05-02T04:09:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
392023-05-02T04:13:56 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
402023-05-02T04:15:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
412023-05-02T04:20:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
422023-05-02T04:22:17 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 246 seconds)
432023-05-02T04:27:33 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
442023-05-02T04:33:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
452023-05-02T04:39:20 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
462023-05-02T04:44:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 265 seconds)
472023-05-02T04:52:07 *** martinus__ <martinus__!~martinus@046125249096.public.t-mobile.at> has quit IRC (Remote host closed the connection)
482023-05-02T04:52:31 *** martinus <martinus!~martinus@046125249096.public.t-mobile.at> has joined #bitcoin-core-dev
492023-05-02T04:56:53 *** martinus <martinus!~martinus@046125249096.public.t-mobile.at> has quit IRC (Remote host closed the connection)
502023-05-02T04:58:51 *** martinus <martinus!~martinus@046125249096.public.t-mobile.at> has joined #bitcoin-core-dev
512023-05-02T05:03:33 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
522023-05-02T05:07:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
532023-05-02T05:08:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
542023-05-02T05:13:23 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 260 seconds)
552023-05-02T05:19:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
562023-05-02T05:24:15 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 260 seconds)
572023-05-02T05:31:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
582023-05-02T05:35:31 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)
592023-05-02T05:42:11 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
602023-05-02T05:47:20 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 268 seconds)
612023-05-02T06:10:10 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
622023-05-02T06:15:10 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 265 seconds)
632023-05-02T06:15:38 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
642023-05-02T06:20:09 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 256 seconds)
652023-05-02T06:21:16 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
662023-05-02T06:26:25 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
672023-05-02T06:31:01 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)
682023-05-02T06:32:35 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
692023-05-02T06:37:34 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 276 seconds)
702023-05-02T06:38:01 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
712023-05-02T06:38:57 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
722023-05-02T06:42:47 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 264 seconds)
732023-05-02T06:48:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
742023-05-02T06:53:19 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 268 seconds)
752023-05-02T06:55:03 *** gribble <gribble!~gribble@bitcoin/bot/gribble> has quit IRC (Remote host closed the connection)
762023-05-02T07:19:32 *** gribble <gribble!~gribble@bitcoin/bot/gribble> has joined #bitcoin-core-dev
772023-05-02T07:19:32 *** ChanServ sets mode: +o gribble
782023-05-02T07:41:24 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
792023-05-02T07:54:25 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
802023-05-02T08:02:57 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
812023-05-02T08:32:58 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
822023-05-02T08:44:15 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
832023-05-02T09:03:46 *** dberkelmans <dberkelmans!~dberkelma@2001:1c03:530d:8100:71f6:d9c5:3781:fb4b> has joined #bitcoin-core-dev
842023-05-02T09:06:53 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/be0325c6a625...8a373a5c7f94
852023-05-02T09:06:53 <bitcoin-git> bitcoin/master 271c23e Martin Zumsande: blockstorage: Adjust fastprune limit if block exceeds blockfile size
862023-05-02T09:06:53 <bitcoin-git> bitcoin/master 8f14fc8 Matthew Zipkin: test: cover fastprune with excessive block size
872023-05-02T09:06:53 <bitcoin-git> bitcoin/master 8a373a5 fanquake: Merge bitcoin/bitcoin#27191: blockstorage: Adjust fastprune limit if block...
882023-05-02T09:06:58 <bitcoin-git> [bitcoin] fanquake merged pull request #27191: blockstorage: Adjust fastprune limit if block exceeds blockfile size (master...202302_fastprune_oom) https://github.com/bitcoin/bitcoin/pull/27191
892023-05-02T09:17:01 *** dberkelmans <dberkelmans!~dberkelma@2001:1c03:530d:8100:71f6:d9c5:3781:fb4b> has quit IRC (Quit: Client closed)
902023-05-02T09:19:09 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
912023-05-02T09:21:36 <Murch> <BlueMatt[m]> "is there a case where bitcoin..." <- Yes, generally the fee estimation can be unreliable if you were offline. We use only transactions that were in the mempool and then got included in a block, so I think if you e.g. went offline a bit before the mempool got cleared out, then started it later it would reload from the mempool file on startup, see that all these transactions have gotten confirmed, including ones that the node has just
922023-05-02T09:21:36 <Murch> received and then you have no new data after that. I'd imagine that might lead to underestimation.
932023-05-02T09:23:42 <Murch> Also, if the short-term data is entry it would fall back to slightly older data, up to the last couple days or so
942023-05-02T09:24:44 <Murch> I'm not sure whether there is a mechanism in place to ensure it does not provide estimates if it has too little data
952023-05-02T09:25:14 <Murch> It might fall back to the default fee in that case
962023-05-02T09:27:22 <sipa> Yeah, there is a fallback fee setting, IIRC
972023-05-02T09:28:33 <Murch> Anyway, it probably takes at least one blocks to be found for the fee estimation to have local information
982023-05-02T09:34:57 <sipa> IIRC you need at least 2x as many blocks as the window you're aiming for to get a reliable estimate.
992023-05-02T09:38:09 *** aielima <aielima!~aielima@user/aielima> has quit IRC (Quit: Ciao)
1002023-05-02T09:39:27 *** dberkelmans <dberkelmans!~dberkelma@2001:1c03:530d:8100:a47d:5302:7b01:d7f3> has joined #bitcoin-core-dev
1012023-05-02T09:44:48 *** dberkelmans <dberkelmans!~dberkelma@2001:1c03:530d:8100:a47d:5302:7b01:d7f3> has quit IRC (Ping timeout: 245 seconds)
1022023-05-02T09:46:26 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 246 seconds)
1032023-05-02T09:50:59 *** gossie <gossie!~gossie@2001:1c02:109:6a00:df25:6321:8260:d9be> has quit IRC (Quit: = "bye bye")
1042023-05-02T10:00:36 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1052023-05-02T10:04:45 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 240 seconds)
1062023-05-02T10:05:45 *** flooded <flooded!~flooded@146.70.202.142> has quit IRC (Ping timeout: 240 seconds)
1072023-05-02T10:13:09 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
1082023-05-02T10:22:58 <sipa> Though, it shouldn't return 1 sat/vb when not enough data is available...
1092023-05-02T10:24:42 *** achow101 <achow101!~achow101@user/achow101> has quit IRC (Quit: No Ping reply in 180 seconds.)
1102023-05-02T10:26:08 *** achow101 <achow101!~achow101@user/achow101> has joined #bitcoin-core-dev
1112023-05-02T10:29:47 <willcl_ark> glozow / Pieter ref discussion on #19109 (which I can't reply to), just noting here that enabling NODE_BLOOM will permit our node to send peers a response to a `mempool` msg -- it doesn't require additional net permissions on the peer. (h/t b10c)
1122023-05-02T10:29:50 <gribble> https://github.com/bitcoin/bitcoin/issues/19109 | Only allow getdata of recently announced invs by sipa · Pull Request #19109 · bitcoin/bitcoin · GitHub
1132023-05-02T10:33:56 <fanquake> willcl_ark: that thread is now unlocked
1142023-05-02T10:35:41 <willcl_ark> thanks
1152023-05-02T10:37:30 <sipa> @willcl_ark Yeah, good point. Perhaps I wasn't aware when that PR was created, or perhaps it was considered so fringe that we didn't care.
1162023-05-02T10:39:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Remote host closed the connection)
1172023-05-02T10:40:15 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
1182023-05-02T10:44:14 <bitcoin-git> [bitcoin] MarcoFalke reopened pull request #25975: contrib/init: Better systemd integration (master...2022-09-systemd-improve) https://github.com/bitcoin/bitcoin/pull/25975
1192023-05-02T10:45:11 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 264 seconds)
1202023-05-02T10:51:58 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Ping timeout: 268 seconds)
1212023-05-02T10:55:57 <glozow> sipa: thoughts on requiring recently announced invs even when there was a recent mempool message? Based on https://github.com/bitcoin/bitcoin/pull/27426#issuecomment-1529678174, NODE_BLOOM is extremely common and default on in some places today
1222023-05-02T11:02:58 <bitcoin-git> [bitcoin] Bushstar opened pull request #27551: Reduce calls to various SetNull methods (master...reduce-setnull) https://github.com/bitcoin/bitcoin/pull/27551
1232023-05-02T11:03:25 *** stick <stick!sid403625@user/prusnak> has quit IRC (Quit: Connection closed for inactivity)
1242023-05-02T11:03:37 <sipa> @glozow That's crazy... do we know why Umbrel and Raspiblitz are setting peerbloomfilters?
1252023-05-02T11:04:12 <sipa> If we do want to keep support for that, I think it's reasonable to indeed exclude non-yet-announced transactions from the BIP35 response.
1262023-05-02T11:06:54 <glozow> sipa: I agree ð. My best guess is itâs for bisq
1272023-05-02T11:07:11 <sipa> BIP37 (or BIP111 now...) support should really be enabled just for peers trusted not to DoS.
1282023-05-02T11:07:50 <glozow> Yes, unfortunately it seems people do not know this
1292023-05-02T11:09:33 <glozow> I think we could open issues to umbrel and raspiblitz to discourage it and maybe put louder warnings, but for now exclude not recently announced
1302023-05-02T11:09:44 <sipa> That makes sense.
1312023-05-02T11:16:30 <darosior> Murch, BlueMatt[m]: but there is an exponential decay on data points. If all the data we've got is from too long ago we should (and i'm pretty sure do) fail to provide any estimate.
1322023-05-02T11:17:35 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
1332023-05-02T11:19:26 <darosior> About the BIP37 issue i was stunt too so i've asked on Twitter yesterday why do those node-in-a-box set `peerbloomfilters` and a Raspiblitz contributor said it was indeed for Bisq support (as glozow suggested). https://twitter.com/darosior/status/1653037196704727046
1342023-05-02T11:19:47 <darosior> It's even crazier when you think they usually come bundled with a Lightning node...
1352023-05-02T11:19:52 <sipa> If so, shouldn't it suffice to provide it to 127.0.0.1 ?
1362023-05-02T11:20:11 *** flooded <flooded!~flooded@146.70.202.142> has joined #bitcoin-core-dev
1372023-05-02T11:20:55 <darosior> I think they provide it through Tor because they use it to remotely connect to their node at home
1382023-05-02T11:21:14 *** flooded is now known as _flood
1392023-05-02T11:21:28 <sipa> ... do they keep the onion address secret?
1402023-05-02T11:21:56 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
1412023-05-02T11:25:44 <darosior> I don't know but i don't see why they'd share it. It was also an argument from the Raspiblitz contributor: that they only run the bitcoind and lightningd through Tor so it's harder to correlate them... But hey it sounds like a pretty weak protection
1422023-05-02T11:45:21 <emzy> FWIW I run 4 bitcoin core public nodes for Bisq, with peerbloomfilters=1. They are very busy but work fine.
1432023-05-02T11:50:40 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
1442023-05-02T11:55:23 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
1452023-05-02T11:56:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
1462023-05-02T11:58:17 <darosior> emzy: could Bisq technically switch to using something like block filters instead?
1472023-05-02T12:01:30 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 260 seconds)
1482023-05-02T12:02:50 <furszy> most likely it's not bisq issue, it's bitcoinj not supporting client side filtering.
1492023-05-02T12:04:01 <furszy> will check what they have there, been a while since I worked with it.
1502023-05-02T12:13:36 <furszy> ok yep, bitcoinj master doesn't have the node_compact_filters service flag.
1512023-05-02T12:13:58 <bitcoin-git> [bitcoin] sipa opened pull request #27552: Add support for "partial" fuzzers that indicate usefulness (master...202305_partial_fuzzers) https://github.com/bitcoin/bitcoin/pull/27552
1522023-05-02T12:19:00 <bitcoin-git> [bitcoin] MarcoFalke opened pull request #27553: test: Simplify feature_fastprune.py (master...2305-test-fastprune-less-code-) https://github.com/bitcoin/bitcoin/pull/27553
1532023-05-02T12:20:53 <josie> sipa: iirc, they don't keep the onion address secret. the onion address is your "identity" in bisq and how your reputation metric is tracked
1542023-05-02T12:21:42 <sipa> @josie#1745 I mean the onion address of the bitcoind node. Is that the same?
1552023-05-02T12:21:43 <gribble> https://github.com/bitcoin/bitcoin/issues/1745 | Misc IRC fixes. by gmaxwell · Pull Request #1745 · bitcoin/bitcoin · GitHub
1562023-05-02T12:24:33 <josie> sipa: ah good point, the onion address for bisq is completely separate from your bitcoind node afaik
1572023-05-02T12:30:33 *** nintendo1889 <nintendo1889!uid23646@id-23646.tinside.irccloud.com> has joined #bitcoin-core-dev
1582023-05-02T12:30:43 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8a373a5c7f94...cfe5da4c9026
1592023-05-02T12:30:43 <bitcoin-git> bitcoin/master 82e6e3c Sebastian Falbesoner: test: add ripemd160 to test framework modules list
1602023-05-02T12:30:43 <bitcoin-git> bitcoin/master cfe5da4 fanquake: Merge bitcoin/bitcoin#27542: test: add ripemd160 to test framework modules...
1612023-05-02T12:30:48 <bitcoin-git> [bitcoin] fanquake merged pull request #27542: test: add ripemd160 to test framework modules list (master...test-test_runner_add_ripemd160_module) https://github.com/bitcoin/bitcoin/pull/27542
1622023-05-02T12:32:43 *** bitdex <bitdex!~bitdex@gateway/tor-sasl/bitdex> has quit IRC (Quit: = "")
1632023-05-02T12:41:47 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
1642023-05-02T12:45:25 <bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/cfe5da4c9026...d654c762c82d
1652023-05-02T12:45:25 <bitcoin-git> bitcoin/master 24d55fb kevkevin: test: added coverage to rpc_scantxoutset.py
1662023-05-02T12:45:26 <bitcoin-git> bitcoin/master d654c76 fanquake: Merge bitcoin/bitcoin#27453: test: added coverage to rpc_scantxoutset.py
1672023-05-02T12:45:31 <bitcoin-git> [bitcoin] fanquake merged pull request #27453: test: added coverage to rpc_scantxoutset.py (master...test/scantxoutsetInvalid) https://github.com/bitcoin/bitcoin/pull/27453
1682023-05-02T12:46:17 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 246 seconds)
1692023-05-02T12:55:58 <furszy> .
1702023-05-02T12:55:58 <furszy> maybe Bisq, and others, could switch to use core instead of bitcoinj if we provide opt-in client side filtering capabilities.
1712023-05-02T12:55:58 <furszy> which.. shilling a bit, is basically what I have been implementing the past months (itâs not fully ready but, short summary: I have a PoC running with p2p, RPC and wallet support to request filters on-demand and automatically, track in-flight and stale requests and request matching blocks + update the wallet state).
1722023-05-02T12:56:00 <furszy> this was the reason behind #26966, #27006 and #27469..
1732023-05-02T12:56:01 <gribble> https://github.com/bitcoin/bitcoin/issues/26966 | index: blockfilter initial sync speedup, parallelize process by furszy · Pull Request #26966 · bitcoin/bitcoin · GitHub
1742023-05-02T12:56:02 <furszy> so.. will try to get in-touch with Bisq and see what they have planned. Even if this doesnât get into core soon (or never if there is no consensus), itâs a good use case for them and for us to get rid-off bip35 and bip37 net support.
1752023-05-02T12:56:03 <gribble> https://github.com/bitcoin/bitcoin/issues/27006 | reduce cs_main scope, guard block index nFile under a local mutex by furszy · Pull Request #27006 · bitcoin/bitcoin · GitHub
1762023-05-02T12:56:05 <gribble> https://github.com/bitcoin/bitcoin/issues/27469 | wallet: improve IBD sync time by skipping block scanning prior birth time by furszy · Pull Request #27469 · bitcoin/bitcoin · GitHub
1772023-05-02T12:56:25 <sdaftuar> jamesob6: yeah i understand the desire to not special-case the download logic. but i was hoping we can avoid parametrizing data in net_processing based on Chainstate -- it seems like most of the complexity in block download is having to deal with the case that we might need to download a chain that forks from our own chain.
1782023-05-02T12:56:57 <sdaftuar> jamesob6: so i was thinking that if the background chain download logic really is dead-simple, maybe we can just introduce logic that does that simple thing. i'll play with it and see what i get
1792023-05-02T12:59:04 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has joined #bitcoin-core-dev
1802023-05-02T13:04:17 <bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/d654c762c82d...7b45d171f549
1812023-05-02T13:04:17 <bitcoin-git> bitcoin/master 1232c2f fanquake: ci: use LLVM/clang-16 in native_asan job
1822023-05-02T13:04:17 <bitcoin-git> bitcoin/master f952e67 fanquake: ci: remove usage of untrusted bpfcc-tools
1832023-05-02T13:04:18 <bitcoin-git> bitcoin/master 7b45d17 fanquake: Merge bitcoin/bitcoin#27360: ci: use LLVM/clang-16 in native_asan job
1842023-05-02T13:04:23 <bitcoin-git> [bitcoin] fanquake merged pull request #27360: ci: use LLVM/clang-16 in native_asan job (master...asan_llvm_16) https://github.com/bitcoin/bitcoin/pull/27360
1852023-05-02T13:04:32 *** Guyver2 <Guyver2!~Guyver@77-174-98-73.fixed.kpn.net> has left #bitcoin-core-dev (Closing Window)
1862023-05-02T13:08:50 <josie> furszy: sounds cool! so this would be bitcoin core node which asks for blocks on demand based on the wallet / rpc commands?
1872023-05-02T13:09:34 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
1882023-05-02T13:20:24 <furszy> yeah. There are two modes: manual and automatic. The manual mode moves the sync responsibility to any external software (RPC commands to request filters, get the wallet needle set, check if filter matches, request the block, etc). And a automatic mode that follows bip157 client side specs.
1892023-05-02T13:26:37 <josie> furszy: id be interested in testing/playing around with this if you have a branch I can compile and run
1902023-05-02T13:33:00 *** jamesob <jamesob!~jamesob@141.156.173.67> has quit IRC (Quit: The Lounge - https://thelounge.chat)
1912023-05-02T13:33:00 *** jamesob6 <jamesob6!~jamesob@141.156.173.67> has quit IRC (Quit: The Lounge - https://thelounge.chat)
1922023-05-02T13:46:34 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has joined #bitcoin-core-dev
1932023-05-02T13:47:23 <furszy> cool josie :). Iâm not that far from sharing it publicly, being pushing to reach to a point where I'm happy enough with the sources first (have a good number of pending to do). Mainly to not share something that I know that will be changing soon and get a better first review/testing experience.
1942023-05-02T13:47:23 <furszy> Thus why have been decoupling stuff from that branch into smaller PRs, like the ones shared above, so those can be reviewed in parallel and this branch doesn't become a big scary monster.
1952023-05-02T13:48:57 <josie> furszy: cool, looking forward to it!
1962023-05-02T13:50:09 <furszy> <3
1972023-05-02T13:52:21 *** b_101 <b_101!~robert@189.236.59.209> has quit IRC (Ping timeout: 256 seconds)
1982023-05-02T14:02:53 *** jonatack1 <jonatack1!~jonatack@user/jonatack> has joined #bitcoin-core-dev
1992023-05-02T14:04:03 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
2002023-05-02T14:05:35 *** jon_atack <jon_atack!~jonatack@user/jonatack> has quit IRC (Ping timeout: 264 seconds)
2012023-05-02T14:19:25 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2022023-05-02T14:25:49 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
2032023-05-02T14:36:21 <bitcoin-git> [bitcoin] hebasto opened pull request #27554: test: Treat `bitcoin-wallet` binary in the same way as others (master...230502-toolwallet) https://github.com/bitcoin/bitcoin/pull/27554
2042023-05-02T14:38:40 <instagibbs> re:estimatesmartfee, if it's degraded, it shouldn't return garbage, but an error, right?
2052023-05-02T14:39:07 <instagibbs> (or a fallback fee if enabled, which isn't on mainnet?)
2062023-05-02T14:42:01 <Murch> I think if you were just offline for a bit, and the mempool cleared after shut down, the transactions that get loaded with the mempool and the catching up to the chaintip might be the only data to estimate the short-window on
2072023-05-02T14:42:25 <Murch> 1â¯á¹©/vB seems odd though, because it should use the maximum from the short-term, mid-term, and long-term bucket
2082023-05-02T14:42:38 <achow101> there's a fee_estimate.dat file, so presumably we are loading that with possibly outdated data on start
2092023-05-02T14:43:23 <instagibbs> Murch depends on mode, not sure what mode they're using
2102023-05-02T14:46:56 <dergoegge> lightlike: RE https://github.com/bitcoin/bitcoin/pull/27552#pullrequestreview-1409209797
2112023-05-02T14:46:56 <dergoegge> You might be interested in https://mboehme.github.io/paper/FSE20.Entropy.pdf, which is something that libFuzzer implements
2122023-05-02T14:46:56 <dergoegge> Afaiu this is what they do now instead of picking inputs at random from the corpus, to spend more time on "interesting" inputs
2132023-05-02T14:47:59 <sipa> Ah yes, I found that too after looking up what the log message about "entropic power schedule" was about.
2142023-05-02T14:58:21 <BlueMatt[m]> <sipa> "Yeah, there is a fallback fee..." <- Thatâs just for wallet, though, no? The estimator itself should never use that.
2152023-05-02T14:58:43 <instagibbs> the estimator is supposed to barf if it's not confident
2162023-05-02T14:59:11 <BlueMatt[m]> <Murch> "Yes, generally the fee estimatio..." <- Right, but it wonât invent things out of whole cloth, which would be required to explain what I saw.
2172023-05-02T15:00:02 <BlueMatt[m]> instagibbs: Right thatâs what the code I read said, I was mostly checking that (a) I read it right and (b) thereâs not some other known cases where it returns 1s/van
2182023-05-02T15:00:06 <BlueMatt[m]> Vb
2192023-05-02T15:00:17 *** nintendo1889 <nintendo1889!uid23646@id-23646.tinside.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)
2202023-05-02T15:04:01 <instagibbs> Only known case I know of is sometimes mempool fills up(and trims) faster than estimator can catch up, so mempool minfee isn't reflected in it
2212023-05-02T15:08:43 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2222023-05-02T15:14:07 <darosior> Regarding BIP37 being manually enabled by node-in-a-box solutions, i've opened an issue in the Umbrel and Raspiblitz repositories. Just FYI: https://github.com/getumbrel/umbrel/issues/1624 https://github.com/rootzoll/raspiblitz/issues/3781.
2232023-05-02T15:14:25 <instagibbs> BlueMatt[m] https://github.com/bitcoin/bitcoin/issues/11800#issuecomment-349697807 squinting at this issue, maybe it indeed returns "garbage" at lower timeframes
2242023-05-02T15:14:29 <fanquake> darosior: thanks
2252023-05-02T15:15:39 <darosior> re fee estimation. "there's a fee_estimate.dat file, so presumably we are loading that with possibly outdated data on start" -> Yes but we do store the height in this file iirc. And if it's too far from our current best height we won't serve outdated data.
2262023-05-02T15:15:40 <fjahr> I am not sure if this is related to Mattâs issue because we are talking about very different time frames but I just synced a node that wasnât running since early last month, so it had to catch up about 4 weeks. The mempool was cleared and as it was syncing I requested âestimatesmartfee 2â multiple times because I saw the conversation here. The suggested feerate fluctuated between 0.00006167 and 0.00022090. I donât
2272023-05-02T15:15:40 <fjahr> see how the node would be able to make reliable predictions if it hasnât seen the blocks of the last few days and nothing in the mempool. Does anyone know on what basis these values are fluctuating in this case?
2282023-05-02T15:16:08 <BlueMatt[m]> instagibbs: Squinting there it shouldnât happen on mainnet though I think?
2292023-05-02T15:16:44 <instagibbs> I've never seen it, though I don't restart old nodes a lot and use them
2302023-05-02T15:17:22 <BlueMatt[m]> At least the counterparty in one case claimed their node had crashed only a few hours before
2312023-05-02T15:17:42 <BlueMatt[m]> Dunno how often the estimates are written to disk during normal operation
2322023-05-02T15:17:53 <BlueMatt[m]> So unclear how old that file could have been
2332023-05-02T15:17:54 <darosior> BlueMatt[m]: only at shutdown
2342023-05-02T15:18:01 <BlueMatt[m]> Oh thatâs bad
2352023-05-02T15:18:04 <instagibbs> ah, crash
2362023-05-02T15:18:27 <BlueMatt[m]> So maybe that was the bug then - restarted with estimates from a month ago or something stupid
2372023-05-02T15:18:30 <instagibbs> seems like something we could flush every 24 hours? not a huge file
2382023-05-02T15:18:48 <BlueMatt[m]> Yea that plus reject if the estimates havenât caught up with now
2392023-05-02T15:18:54 <BlueMatt[m]> Or otherwise are that old
2402023-05-02T15:19:07 <BlueMatt[m]> Or even persist once an hour
2412023-05-02T15:19:13 <darosior> Then how comes it would serve old data? Maybe it wasn't synced yet and didn't know it was outdated?
2422023-05-02T15:20:06 <BlueMatt[m]> Iâd understood fjahr s point to be that it will happily serve stale data
2432023-05-02T15:20:22 <BlueMatt[m]> As long as it has data
2442023-05-02T15:20:56 <darosior> Yeah we should definitely not serve fee estimation if we are catching up
2452023-05-02T15:26:58 <BlueMatt[m]> https://github.com/bitcoin/bitcoin/issues/27555 okay I think I captured the conversation here
2462023-05-02T15:51:11 <bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/7b45d171f549...da9f62f91229
2472023-05-02T15:51:12 <bitcoin-git> bitcoin/master 710b839 Harris: rpc: return block hash & height in getbalances, gettransaction & getwallet...
2482023-05-02T15:51:12 <bitcoin-git> bitcoin/master da9f62f Andrew Chow: Merge bitcoin/bitcoin#26094: rpc: Return block hash & height in getbalance...
2492023-05-02T15:51:17 <bitcoin-git> [bitcoin] achow101 merged pull request #26094: rpc: Return block hash & height in getbalances, gettransaction and getwalletinfo (master...return-blockhash-with-wallet-calls) https://github.com/bitcoin/bitcoin/pull/26094
2502023-05-02T15:56:36 <instagibbs> fjahr https://github.com/bitcoin/bips/pull/1382#issuecomment-1531716890 I think this might be "generic " vs "ancestor" package relay confusion, which also confuses me as to the purpose of the former
2512023-05-02T15:59:41 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 268 seconds)
2522023-05-02T16:11:56 *** berndj <berndj!~berndj@197.189.254.139> has quit IRC (Quit: ZNC - http://znc.in)
2532023-05-02T16:11:57 <fjahr> instagibbs: hm, possible, I thought I kind of understood that part (narrator: "he didn't") but there is nothing named pkginfo or similar in the generic part. Most likely I would guess the graphics haven't evolved with the text.
2542023-05-02T16:11:58 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
2552023-05-02T16:14:18 <fjahr> But yeah, ancpkginfo is something different and I guess plain pkginfo has been removed at some point (?)
2562023-05-02T16:16:29 *** berndj <berndj!~berndj@197.189.254.139> has joined #bitcoin-core-dev
2572023-05-02T16:17:31 *** jamesob6 <jamesob6!~jamesob@141.156.173.67> has joined #bitcoin-core-dev
2582023-05-02T16:17:31 *** jamesob4 <jamesob4!~jamesob@141.156.173.67> has joined #bitcoin-core-dev
2592023-05-02T16:19:49 <jamesob6> sdaftuar: great! anything that minimizes risk is +1 from me
2602023-05-02T16:20:59 <instagibbs> fjahr it's in the "generic" portion imagery, otherwise not defined
2612023-05-02T16:21:02 <instagibbs> (i think)
2622023-05-02T16:23:27 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2632023-05-02T16:23:56 <fjahr> yepp, that's what I see too, I guess glozow will have to solve that mystery :)
2642023-05-02T16:25:50 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2652023-05-02T16:28:41 *** flooded <flooded!~flooded@146.70.195.35> has joined #bitcoin-core-dev
2662023-05-02T16:30:11 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 264 seconds)
2672023-05-02T16:32:22 *** _flood <_flood!~flooded@146.70.202.142> has quit IRC (Ping timeout: 268 seconds)
2682023-05-02T16:51:47 *** Talkless <Talkless!~Talkless@mail.dargis.net> has joined #bitcoin-core-dev
2692023-05-02T16:57:13 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2702023-05-02T17:02:35 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 268 seconds)
2712023-05-02T17:26:08 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2722023-05-02T17:30:45 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 240 seconds)
2732023-05-02T17:36:31 *** aielima <aielima!~aielima@user/aielima> has joined #bitcoin-core-dev
2742023-05-02T17:38:46 <achow101> 24.1rc2 and 25.0rc1 bins are uploaded
2752023-05-02T17:41:34 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Remote host closed the connection)
2762023-05-02T17:53:17 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2772023-05-02T17:58:29 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 246 seconds)
2782023-05-02T18:03:52 *** Guest55 <Guest55!~Guest55@43.243.193.4> has joined #bitcoin-core-dev
2792023-05-02T18:06:59 *** Guest55 <Guest55!~Guest55@43.243.193.4> has quit IRC (Client Quit)
2802023-05-02T18:09:39 <bitcoin-git> [bitcoin] furszy opened pull request #27556: wallet: fix deadlock in bdb read write operation (master...2023_wallet_db_deadlock) https://github.com/bitcoin/bitcoin/pull/27556
2812023-05-02T18:12:43 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2822023-05-02T18:20:00 *** b_101 <b_101!~robert@189.194.249.94> has joined #bitcoin-core-dev
2832023-05-02T18:28:39 <bitcoin-git> [bitcoin] pinheadmz opened pull request #27557: net: call getaddrinfo() in detachable thread to prevent stalling (master...async-getaddrinfo) https://github.com/bitcoin/bitcoin/pull/27557
2842023-05-02T18:30:12 <bitcoin-git> [bitcoin] pinheadmz closed pull request #27505: net: use interruptible async getaddrinfo wrapper from libevent for DNS (master...dns-libevent) https://github.com/bitcoin/bitcoin/pull/27505
2852023-05-02T18:31:05 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Ping timeout: 240 seconds)
2862023-05-02T18:36:00 <jamesob6> anyone ever have a hard time reproducing threadsanitizer errors locally?
2872023-05-02T18:36:24 *** jamesob6 is now known as jamesob
2882023-05-02T18:57:12 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has joined #bitcoin-core-dev
2892023-05-02T19:10:09 *** test_ <test_!~flooded@146.70.195.35> has joined #bitcoin-core-dev
2902023-05-02T19:13:25 *** flooded <flooded!~flooded@146.70.195.35> has quit IRC (Ping timeout: 240 seconds)
2912023-05-02T19:16:32 <fjahr> FYI: For those that were testing my gitlab instance, Mike and me are making some changes as we discuss the topic with them so it's possible that the instance will not be available at some point in the coming days due to new setup or that your account changes.
2922023-05-02T19:17:39 <fjahr> DM me if there is something you want to test in the meantime
2932023-05-02T19:23:35 *** Talkless <Talkless!~Talkless@mail.dargis.net> has quit IRC (Quit: Konversation terminated!)
2942023-05-02T19:37:52 *** flooded <flooded!flooded@gateway/vpn/protonvpn/flood/x-43489060> has joined #bitcoin-core-dev
2952023-05-02T19:41:22 *** test_ <test_!~flooded@146.70.195.35> has quit IRC (Ping timeout: 252 seconds)
2962023-05-02T20:13:20 *** kch <kch!~kch@45.187.210.56> has joined #bitcoin-core-dev
2972023-05-02T20:15:45 *** b_101 <b_101!~robert@189.194.249.94> has quit IRC (Ping timeout: 240 seconds)
2982023-05-02T20:35:54 *** kch <kch!~kch@45.187.210.56> has quit IRC (Quit: Lost terminal)
2992023-05-02T21:27:44 *** vysn <vysn!~vysn@user/vysn> has quit IRC (Remote host closed the connection)
3002023-05-02T21:37:24 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Remote host closed the connection)
3012023-05-02T21:38:25 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
3022023-05-02T21:40:49 *** vysn <vysn!~vysn@user/vysn> has joined #bitcoin-core-dev
3032023-05-02T21:42:45 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
3042023-05-02T21:52:46 *** bugs_ <bugs_!~bugs@user/bugs/x-5128603> has quit IRC (Quit: Leaving)
3052023-05-02T22:05:33 *** aielima <aielima!~aielima@user/aielima> has quit IRC (Quit: Ciao)
3062023-05-02T22:28:31 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3072023-05-02T22:33:04 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
3082023-05-02T22:39:18 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3092023-05-02T22:40:09 *** AaronvanW <AaronvanW!~AaronvanW@user/AaronvanW> has quit IRC (Quit: Leaving...)
3102023-05-02T22:43:44 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 248 seconds)
3112023-05-02T22:45:22 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3122023-05-02T22:47:32 *** b_101 <b_101!~robert@189.236.59.209> has joined #bitcoin-core-dev
3132023-05-02T22:49:00 <bitcoin-git> [bitcoin] 0xB10C opened pull request #27559: doc: clarify processing of mempool-msgs when NODE_BLOOM (master...2023-05-clarify-mempool-bloom) https://github.com/bitcoin/bitcoin/pull/27559
3142023-05-02T22:49:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)
3152023-05-02T22:56:59 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3162023-05-02T22:57:04 <bitcoin-git> [bitcoin] furszy closed pull request #26644: wallet: bugfix, 'wallet_load_ckey' unit test fails with bdb (master...2022_walletdb_fix_bdb_deadlock) https://github.com/bitcoin/bitcoin/pull/26644
3172023-05-02T23:01:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)
3182023-05-02T23:22:53 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3192023-05-02T23:27:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 246 seconds)
3202023-05-02T23:28:58 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3212023-05-02T23:33:08 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)
3222023-05-02T23:45:23 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has joined #bitcoin-core-dev
3232023-05-02T23:49:45 *** brunoerg <brunoerg!~brunoerg@187.183.43.117> has quit IRC (Ping timeout: 240 seconds)
3242023-05-02T23:51:27 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has joined #bitcoin-core-dev
3252023-05-02T23:55:48 *** brunoerg <brunoerg!~brunoerg@2804:14c:3bfb:8a:dd35:a263:914b:9ff1> has quit IRC (Ping timeout: 240 seconds)