--- Log opened Thu Jul 17 00:00:44 2025 00:04 -!- f321x [~f321x@user/f321x] has joined #bitcoin-core-dev 00:04 -!- Christoph_ [~Christoph@host-88-217-174-126.customer.m-online.net] has quit [Quit: Christoph_] 00:15 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 00:29 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds] 00:38 < bitcoin-git> [bitcoin-maintainer-tools] BrandonOdiwuor opened pull request #185: update-translations: Generate ts_files.cmake with explicit .ts files list (main...ts-files-cmake) https://github.com/bitcoin-core/bitcoin-maintainer-tools/pull/185 00:42 -!- Holz [~Holz@user/Holz] has quit [Ping timeout: 244 seconds] 00:43 -!- conman [~con@180-150-21-3.b49615.mel.static.aussiebb.net] has quit [Remote host closed the connection] 00:46 -!- Holz [~Holz@user/Holz] has joined #bitcoin-core-dev 00:46 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev 00:48 -!- jespada [~jespada@2800:a4:2283:2700:4d56:5313:eb6:35c4] has quit [Ping timeout: 276 seconds] 00:49 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev 00:49 -!- jespada [~jespada@2800:a4:223f:1a00:1833:e9a3:3f1f:2d7a] has joined #bitcoin-core-dev 00:56 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 00:58 < bitcoin-git> [bitcoin] maflcko opened pull request #32999: ci: Use APT_LLVM_V in msan task (master...2507-msan-ci-apt) https://github.com/bitcoin/bitcoin/pull/32999 01:04 -!- Christoph_ [~Christoph@host-88-217-174-126.customer.m-online.net] has joined #bitcoin-core-dev 01:05 < phantomcircuit> laanwj: yes but there's inherently a race condition with that right? 01:06 < phantomcircuit> like no way can i run all of the tests that github actions ci does just because it's testing on a bunch of platforms i do not have 01:10 -!- Holz [~Holz@user/Holz] has quit [Ping timeout: 252 seconds] 01:12 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 248 seconds] 01:17 < phantomcircuit> so when we merge into master we're at least a little bit relying on ci results for some of the weirder tests 01:26 < phantomcircuit> or im still hilariously wrong, always a possibility 01:39 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 01:56 -!- ScannerBot [~ScannerBo@154.59.111.253] has joined #bitcoin-core-dev 01:57 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 244 seconds] 02:01 -!- ScannerBot [~ScannerBo@154.59.111.253] has quit [Ping timeout: 276 seconds] 02:06 -!- Holz [~Holz@user/Holz] has joined #bitcoin-core-dev 02:08 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window] 02:31 -!- f321x [~f321x@user/f321x] has quit [Quit: f321x] 02:36 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 02:45 -!- janb84 [~janb84@user/janb84] has quit [Ping timeout: 265 seconds] 02:46 -!- janb84 [~janb84@user/janb84] has joined #bitcoin-core-dev 02:47 -!- f321x [~f321x@user/f321x] has joined #bitcoin-core-dev 02:55 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 260 seconds] 03:35 -!- PaperSword1 [~Thunderbi@50.126.92.170] has joined #bitcoin-core-dev 03:36 -!- PaperSword [~Thunderbi@50.126.92.170] has quit [Ping timeout: 248 seconds] 03:36 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 03:36 -!- PaperSword1 is now known as PaperSword 03:37 < bitcoin-git> [bitcoin] maflcko opened pull request #33000: ci: Run unit test parallel with functional tests (master...2507-ci-fun) https://github.com/bitcoin/bitcoin/pull/33000 03:43 < bitcoin-git> [bitcoin] maflcko opened pull request #33001: test: Do not pass tests on unhandled exceptions (master...2507-test-actually-fail-on-failure) https://github.com/bitcoin/bitcoin/pull/33001 03:47 -!- robszarka [~szarka@2603:3003:4eac:100:58ef:f779:9e5:d0e] has quit [Quit: Leaving] 03:48 -!- szarka [~szarka@2603:3003:4eac:100:58ef:f779:9e5:d0e] has joined #bitcoin-core-dev 03:58 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 252 seconds] 03:58 -!- Christoph_ [~Christoph@host-88-217-174-126.customer.m-online.net] has quit [Quit: Christoph_] 03:59 -!- jerryf_ [~jerryf@user/jerryf] has joined #bitcoin-core-dev 03:59 -!- jerryf [~jerryf@user/jerryf] has quit [Ping timeout: 244 seconds] 04:26 -!- jerryf_ is now known as jerryf 04:34 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev 04:35 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Ping timeout: 244 seconds] 04:37 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 04:42 -!- TheRec_ [~toto@84-74-100-31.dclient.hispeed.ch] has quit [Ping timeout: 272 seconds] 04:59 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 248 seconds] 05:07 -!- instagibbs [~instagibb@pool-100-15-116-202.washdc.fios.verizon.net] has joined #bitcoin-core-dev 05:09 -!- Christoph_ [~Christoph@host-88-217-174-126.customer.m-online.net] has joined #bitcoin-core-dev 05:10 -!- Guest44 [~Guest44@2804:1b1:e503:26a0:a2aa:ba83:63a7:99ba] has joined #bitcoin-core-dev 05:11 -!- Guest44 [~Guest44@2804:1b1:e503:26a0:a2aa:ba83:63a7:99ba] has left #bitcoin-core-dev [] 05:26 < bitcoin-git> [bitcoin] maflcko opened pull request #33002: ci: Only pass documented env vars (master...2507-ci-doc-env) https://github.com/bitcoin/bitcoin/pull/33002 05:39 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 05:41 < darosior> #proposedmeetingtopic Turn -natpmp on by default 05:41 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 05:57 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 248 seconds] 06:00 < maflcko> phantomcircuit: It is due to intermittent and non-intermittent CI issues that are fixed later in master. If you run the CI on the pull with one of those, you may never/rarely get a green CI, even though the code changes are usually perfectly fine. 06:02 < maflcko> So merging master is the easiest workaround (the alternative would be to have devs rebase for basically no reason). Also, with any mutable CI logic in yaml files, it is actually impossible to not merge with with master, see https://github.com/bitcoin/bitcoin/pull/32203#issue-2967008670 06:13 -!- flooded [~flooded@149.102.226.200] has joined #bitcoin-core-dev 06:23 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 06:25 -!- enochazariah [~enochazar@102.91.93.182] has quit [Quit: Client closed] 06:26 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 06:41 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:eda0:ce41:a924:549e] has quit [Ping timeout: 272 seconds] 06:47 -!- TheRec [~toto@84-74-100-31.dclient.hispeed.ch] has joined #bitcoin-core-dev 06:47 -!- TheRec [~toto@user/therec] has changed host 06:56 -!- Guest42 [~Guest33@186.153.253.236] has joined #bitcoin-core-dev 06:57 < bitcoin-git> [bitcoin] brunoerg opened pull request #33003: test: add option to skip large re-org test in feature_block (master...2025-07-test-featureblock-skiplargereorg) https://github.com/bitcoin/bitcoin/pull/33003 06:57 -!- Guest42 [~Guest33@186.153.253.236] has quit [Client Quit] 06:58 -!- joetor5 [~Thunderbi@user/joetor5] has joined #bitcoin-core-dev 07:00 -!- enochazariah [~enochazar@102.91.93.182] has quit [Quit: Client closed] 07:03 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 07:04 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev 07:04 -!- SpellChecker_ [~SpellChec@user/SpellChecker] has quit [Ping timeout: 244 seconds] 07:05 -!- eremitah [~int@user/eremitah] has quit [Ping timeout: 272 seconds] 07:10 -!- joetor5 [~Thunderbi@user/joetor5] has quit [Quit: joetor5] 07:13 -!- enochazariah [~enochazar@102.91.93.182] has quit [Quit: Client closed] 07:14 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 07:15 -!- enochazariah53 [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 07:15 -!- enochazariah53 [~enochazar@102.91.93.182] has quit [Client Quit] 07:24 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 07:28 -!- Guest48 [~Guest48@2600:387:f:b31::1] has joined #bitcoin-core-dev 07:37 -!- Guest48 [~Guest48@2600:387:f:b31::1] has quit [Quit: Client closed] 07:49 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev 08:03 -!- Cory70 [~Cory70@user/pasha] has quit [Quit: Client closed] 08:03 -!- Cory70 [~Cory70@user/pasha] has joined #bitcoin-core-dev 08:08 -!- enochazariah [~enochazar@102.91.93.182] has quit [Remote host closed the connection] 08:13 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 08:21 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:19b4:8175:c68e:22c9] has joined #bitcoin-core-dev 08:22 -!- Christoph_ [~Christoph@host-88-217-174-126.customer.m-online.net] has quit [Quit: Christoph_] 08:27 -!- jarthur [~jarthur@user/jarthur] has joined #bitcoin-core-dev 08:39 -!- enochazariah [~enochazar@102.91.93.182] has quit [Remote host closed the connection] 08:39 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 08:55 < fanquake> #proposedmeetingtopic 29.1 08:57 -!- Emc99 [~Emc99@212.129.76.162] has joined #bitcoin-core-dev 08:59 -!- Cory70 [~Cory70@user/pasha] has quit [Quit: Client closed] 09:00 < glozow> hi 09:00 -!- Cory70 [~Cory70@user/pasha] has joined #bitcoin-core-dev 09:00 < glozow> #startmeeting 09:00 < corebot> glozow: Meeting started at 2025-07-17T16:00+0000 09:00 < corebot> glozow: Current chairs: glozow 09:00 < corebot> glozow: Useful commands: #action #info #idea #link #topic #motion #vote #close #endmeeting 09:00 < corebot> glozow: See also: https://hcoop-meetbot.readthedocs.io/en/stable/ 09:00 < corebot> glozow: Participants should now identify themselves with '#here' or with an alias like '#here FirstLast' 09:00 < glozow> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge fanquake fjahr furszy gleb glozow hebasto hodlinator instagibbs jarolrod jonatack josibake kanzure laanwj LarryRuane lightlike luke-jr maflcko marcofleon maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi tdb3 theStack TheCharlatan vasild willcl-ark 09:00 < hebasto> hi 09:00 < maxedw> hi 09:00 < darosior> hi 09:00 < stickies-v> hi 09:00 < theStack> hi 09:00 < lightlike> Hi 09:00 < abubakarsadiq> hi 09:00 < sr_gi[m]1> hi 09:00 < glozow> I see 2 preproposed topics from darosior and fanquake - anything else to add / am I missing any? 09:00 < brunoerg> hi 09:01 < glozow> #topic Erlay WG Update (sr_gi, gleb) 09:02 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has joined #bitcoin-core-dev 09:02 -!- f321x [~f321x@user/f321x] has quit [Quit: f321x] 09:02 < laanwj> hi 09:03 < sr_gi[m]1> I've been working on a small patch to Core so its easier to track propagation times. Opened a PR earlier this week but ended up closing it and going for a considerably smaller change that can just by patch on top of any branch to simulate, given the change seemed not to be useful outside that context. 09:03 < glozow> sr_gi? 09:03 < glozow> (nvm, I see your message now) 09:03 < sr_gi[m]1> I've reworked the Warnet simulations to use this, which have made them way less flaky 09:03 < sr_gi[m]1> PR to review remains the same #30116 09:03 < corebot> https://github.com/bitcoin/bitcoin/issues/30116 | p2p: Fill reconciliation sets (Erlay) attempt 2 by sr-gi · Pull Request #30116 · bitcoin/bitcoin · GitHub 09:04 < sr_gi[m]1> That it on my end 09:04 < johnny9dev> hi 09:05 < glozow> #topic QML GUI WG Update (jarolrod, johnny9dev) 09:09 < johnny9dev> We created a new branch in the gui-qml project called "qt6" that is seeded with just the history of the qml folder. The pinhead did a PR into that branch with his CMake work to build it against a sub-module. bitcoin-core/gui-qml#475. The PR is quite comprehensive even including some github workflows for CI. I started reviewing it and found somethings to workthrough so thats my top priority going into the weekend. Afterwards I plan to 09:09 < johnny9dev> rebase all of my current work on top. 09:09 < johnny9dev> That is all from me. 09:09 < corebot> https://github.com/bitcoin-core/gui-qml/issues/475 | Add cmake, qt6, and bitcoin core submodule by pinheadmz · Pull Request #475 · bitcoin-core/gui-qml · GitHub 09:10 < glozow> #topic orphan resolution WG Update (glozow) 09:10 < glozow> #31829 is close, and will collect followups in #32941 09:10 < corebot> https://github.com/bitcoin/bitcoin/issues/31829 | p2p: improve TxOrphanage denial of service bounds by glozow · Pull Request #31829 · bitcoin/bitcoin · GitHub 09:10 < corebot> https://github.com/bitcoin/bitcoin/issues/32941 | p2p: TxOrphanage revamp cleanups by glozow · Pull Request #32941 · bitcoin/bitcoin · GitHub 09:11 < glozow> Does anybody else want to give WG updates? I skipped most of them based on attendance 09:12 < glozow> #topic Turn -natpmp on by default (darosior) 09:12 < darosior> Hi everyone, so very early on Bitcoin Core started shipping with NAT hole punching enabled by default with UPnP. This was disabled in 2015 following a discovery of an RCE in miniupnpc, the dependency Core used for UPnP, by laanwj present here. Disabled by default, NAT hole punching is not quite useful, and we eventually got rid of UPnP altogether 09:12 < darosior> due to the low quality of the miniupnpc dependency. NAT hole punching was re-implemented properly directly in Core for 29.0 by laanwj, using the PCP protocol with a NAT-PMP fallback. It was still disabled by default in 29. This is a higher quality implementation (properly reviewed, tested and fuzzed) of saner protocols. In comparison, our UPnP 09:12 < darosior> implementation involved parsing XML in C (and this was not fuzzed). Following 29, a number of contributors and power users helped in testing the feature. Testing demonstrated a reduction in functionality (unfortunately the less sane UPnP protocol is still much more widely supported than PCP and NAT-PMP). However it did not raise any concern with 09:12 < darosior> regard to our implementation. Because NAT hole punching is not really useful unless enabled by default, and because i think our implementation is now vetted enough i propose that we enable it by default in 30.0. What do you think? 09:13 < fanquake> #31663 09:13 < corebot> https://github.com/bitcoin/bitcoin/issues/31663 | Enable PCP by default? · Issue #31663 · bitcoin/bitcoin · GitHub 09:14 < laanwj> Yes-In 29.0 we introduced our own NAT-PMP/PCP implementation, replacing often insecure miniupnp. To have more connectable nodes outside of datacenters, we'd eventually like to enable it by default. During the release cycle we've had people test it on many routers (see #31663), though it doesn't work on all, no real issues came up. So the proposal is to enable it by default for 30.0. 09:14 < corebot> https://github.com/bitcoin/bitcoin/issues/31663 | Enable PCP by default? · Issue #31663 · bitcoin/bitcoin · GitHub 09:15 < fanquake> #32159 also related 09:15 < corebot> https://github.com/bitcoin/bitcoin/issues/32159 | net, pcp: handle multi-part responses and filter for default route while querying default gateway by willcl-ark · Pull Request #32159 · bitcoin/bitcoin · GitHub 09:15 < laanwj> it's very possible to delay this by another version, if there's a good reason, but i think we have enough confidence in it now 09:16 < glozow> Seems pretty well-tested 09:16 -!- Cory70 [~Cory70@user/pasha] has quit [Quit: Client closed] 09:16 < darosior> I agree. I think the benefits outweigh the risk now. 09:16 -!- Cory70 [~Cory70@user/pasha] has joined #bitcoin-core-dev 09:16 < laanwj> #32159 helps to parse very large routing tables on linux, which helps in the case of compelx routing (on the machine that runs bitcoind, not the router), but is not a requirement/real bugfix 09:16 < corebot> https://github.com/bitcoin/bitcoin/issues/32159 | net, pcp: handle multi-part responses and filter for default route while querying default gateway by willcl-ark · Pull Request #32159 · bitcoin/bitcoin · GitHub 09:17 < stickies-v> why is it "not really useful unless enabled by default"? 09:17 < darosior> Yeah it seems to be an improvement of the feature but not a requirement for 30. 09:17 < laanwj> if it can't find the default router, it'll default to not using it, which is the safe choice 09:18 < darosior> stickies-v: because it's useful only for users that can't play with the settings of their router to forward a port to their node. So if it is off by default, then it only helps user technical enough to tweak their bitcoind settings but not technical enough to be able to forward a port. I think the set of such users is very small. 09:18 < laanwj> stickies-v: because the idea is that it's effortless; if it requires people to set things up, it's less useful 09:19 < laanwj> e.g. if yu have to enable settings, it's slightly more work to forward a port yourself 09:19 -!- enochazariah [~enochazar@102.91.93.182] has quit [Read error: Connection reset by peer] 09:19 < stickies-v> i think there's a huge gap between a user toggling a bitcoind setting vs playing with their router settings, so in my view this is still very useful even if disabled by default 09:19 < stickies-v> (note: i'm not arguing against disabling it by default) 09:19 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 09:19 < laanwj> okay, yes, probably 09:19 < laanwj> that's true 09:20 < stickies-v> s/disabling it by default/enabling it by default/ 09:20 < darosior> I don't think so. I'd even think more people know about NAT traversal than about the specific NAT hole-punching protocols 09:20 < laanwj> also note that PCP/NATPMP only communicates with the default gateway (so, the closest router). Unlike UPNP it doesn't broadcast to the entire LAN 09:21 < sipa> +1 enabling by default; i think it's an obvious end goal of having nat traversal included in the software, and i don't think more testing will at this point change our understanding anymore 09:21 < laanwj> so it's private in that sense. if the router doesn't support it, it'll ignore the packet or return an error, both cases are handled. 09:22 -!- naiyoma [~ubuntu@user/naiyoma] has joined #bitcoin-core-dev 09:23 < darosior> Ok, i think i'll make a PR and we can follow-up there? 09:23 < stickies-v> i haven't reviewed the code (or the reviewed or the review), but if we feel comfortable it's been tested enough then enabling it by default makes sense to me too 09:23 < laanwj> as i see it, the only reason to not enable it by default is that it could increase bandwidth usage for users that don't have -nolisten but rely on their IPv4 NAT router to shield the port. This is a brittle setup, though. E.g. they might already be automatically listening on Tor in that case 09:24 < laanwj> yes, let's do that 09:24 < sipa> if anything, i think the biggest concern might be large-scale emergent effects, like what happens if the set of reafhable nodes beces drawn from a very different distribution/topology (more home users, ...), but those are also effects that appear slowly following adoption, and there is little we can do to analyse them ahead of tr 09:25 < sipa> (phone typing, sorry for typos) 09:25 < jonatack> hi 09:25 < laanwj> more home users is a good thing for decentralization, anyhow. but yes, it could have unexpected effects. 09:26 < sipa> right, obviouslu! 09:27 < laanwj> also i'm confident it won't break the network. but it might, say, result in different choices to have to be made to get e.g. fastest download performance 09:27 < sipa> right 09:27 < laanwj> that's all i think-let's open a PR and continue discussion there 09:28 < darosior> Yeah 09:28 < sipa> sgtm 09:28 < glozow> #topic 29.1 fanquake 09:29 < fanquake> We are at ~3 months post 29.0; so about time to do a .1. 09:29 < fanquake> What should be the final round of backports are in #32863, which are ready for review. 09:29 < corebot> https://github.com/bitcoin/bitcoin/issues/32863 | [29.x] Backports by fanquake · Pull Request #32863 · bitcoin/bitcoin · GitHub 09:29 < fanquake> Prior backports also done in #32292, #32589 & #32810. 09:29 < corebot> https://github.com/bitcoin/bitcoin/issues/32292 | [29.x] Backports by fanquake · Pull Request #32292 · bitcoin/bitcoin · GitHub 09:29 < corebot> https://github.com/bitcoin/bitcoin/issues/32589 | [29.x] More backports by fanquake · Pull Request #32589 · bitcoin/bitcoin · GitHub 09:29 < corebot> https://github.com/bitcoin/bitcoin/issues/32810 | [29.x] More backports by fanquake · Pull Request #32810 · bitcoin/bitcoin · GitHub 09:29 < laanwj> will take a look 09:29 < fanquake> I think darosior has a suggestion for somethign to backport 09:29 < darosior> I'd like to get #32521. I think it's close to be merged in master (been through a few rounds of re-ACKing) 09:30 < corebot> https://github.com/bitcoin/bitcoin/issues/32521 | policy: make pathological transactions packed with legacy sigops non-standard by darosior · Pull Request #32521 · bitcoin/bitcoin · GitHub 09:30 < glozow> thanks, will review 09:31 < darosior> We see that people upgrade to .1 more than to .2 etc.. And i think adoption of this patch is important for the network to be upgraded if an activation of CC is attempted in the next few years 09:31 < darosior> And i'm afraid people will play shenanigans to slow down the upgrade to 30.0 09:34 -!- entropyx [~blackbox@user/entropyx] has quit [Ping timeout: 276 seconds] 09:35 < glozow> Anything else to discuss? 09:37 < glozow> #endmeeting 09:37 < corebot> glozow: Meeting ended at 2025-07-17T16:37+0000 09:37 < corebot> glozow: Raw log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-07-17_16_00.log.json 09:37 < corebot> glozow: Formatted log: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-07-17_16_00.log.html 09:37 < corebot> glozow: Minutes: https://achow101.com/ircmeetings/2025/bitcoin-core-dev.2025-07-17_16_00.html 09:37 -!- Emc99 [~Emc99@212.129.76.162] has quit [Quit: Client closed] 09:43 -!- eugenesiegel [~eugenesie@user/eugenesiegel] has quit [Quit: Client closed] 10:03 < bitcoin-git> [bitcoin] darosior opened pull request #33004: Enable `-natpmp` by default (master...2507_natpmp_on_default) https://github.com/bitcoin/bitcoin/pull/33004 10:08 < vasild> Just a note - I am in semi-vacation mode in the next weeks. 10:09 -!- SpellChecker [~SpellChec@user/SpellChecker] has quit [Remote host closed the connection] 10:10 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev 10:11 -!- Guest3324 [~Guest3324@2a02:3032:60:b4a8:239c:3375:3c49:e2db] has joined #bitcoin-core-dev 10:12 -!- Guest3324 [~Guest3324@2a02:3032:60:b4a8:239c:3375:3c49:e2db] has quit [Client Quit] 10:14 -!- Talkless [~Talkless@138.199.6.197] has joined #bitcoin-core-dev 10:16 -!- entropyx [~blackbox@user/entropyx] has joined #bitcoin-core-dev 10:20 -!- naiyoma [~ubuntu@user/naiyoma] has quit [Ping timeout: 272 seconds] 10:27 -!- Guest2436 [~ubuntu@197.237.117.94] has joined #bitcoin-core-dev 10:42 -!- enochazariah [~enochazar@102.91.93.182] has quit [Ping timeout: 260 seconds] 11:07 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds] 11:50 < bitcoin-git> [bitcoin] marcofleon opened pull request #33005: refactor: GenTxid type safety followups (master...2025/07/gentxid-followups) https://github.com/bitcoin/bitcoin/pull/33005 12:16 -!- Talkless [~Talkless@138.199.6.197] has quit [Quit: Konversation terminated!] 12:19 -!- sliv3r__ [~sliv3r__@user/sliv3r-:76883] has quit [Ping timeout: 260 seconds] 12:19 -!- sliv3r__ [~sliv3r__@user/sliv3r-:76883] has joined #bitcoin-core-dev 12:25 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 12:27 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 12:35 -!- enochazariah [~enochazar@102.91.93.182] has quit [Ping timeout: 260 seconds] 12:43 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:19b4:8175:c68e:22c9] has quit [Ping timeout: 252 seconds] 12:57 -!- jespada [~jespada@2800:a4:223f:1a00:1833:e9a3:3f1f:2d7a] has quit [Ping timeout: 248 seconds] 12:57 -!- Guest2436 [~ubuntu@197.237.117.94] has quit [Quit: WeeChat 4.1.1] 12:59 -!- jespada [~jespada@2800:a4:2241:e00:148b:4fe7:cf88:14bf] has joined #bitcoin-core-dev 13:06 -!- Christoph_ [~Christoph@2a02:810d:1399:b700:d06f:2a2d:9306:b9c8] has joined #bitcoin-core-dev 13:29 -!- Christoph_ [~Christoph@2a02:810d:1399:b700:d06f:2a2d:9306:b9c8] has quit [Quit: Christoph_] 13:31 -!- enochazariah [~enochazar@102.91.93.182] has joined #bitcoin-core-dev 13:40 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:286a:183a:4281:3770] has joined #bitcoin-core-dev 13:46 -!- jespada [~jespada@2800:a4:2241:e00:148b:4fe7:cf88:14bf] has quit [Ping timeout: 276 seconds] 14:03 -!- dviola [~diego@user/dviola] has quit [Ping timeout: 245 seconds] 14:05 -!- diego [~diego@177.34.235.126] has joined #bitcoin-core-dev 14:06 -!- diego is now known as Guest8600 14:07 -!- Gamja [~Gamja@179.0.56.210] has joined #bitcoin-core-dev 14:09 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:286a:183a:4281:3770] has quit [Ping timeout: 260 seconds] 14:10 -!- Gamja [~Gamja@179.0.56.210] has quit [Client Quit] 14:21 -!- jespada [~jespada@2800:a4:2241:e00:28ff:528c:7960:1491] has joined #bitcoin-core-dev 14:31 -!- joetor5 [~Thunderbi@user/joetor5] has joined #bitcoin-core-dev 14:37 -!- _Sam-- [~sam-@user/-Sam-:39802] has joined #bitcoin-core-dev 14:44 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev 14:46 -!- conman [~con@180-150-21-3.b49615.mel.static.aussiebb.net] has joined #bitcoin-core-dev 14:47 -!- luke-jr_ [~luke-jr@user/luke-jr] has quit [Ping timeout: 272 seconds] 14:50 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving] 15:01 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:ad02:79a8:c1f1:31b1] has joined #bitcoin-core-dev 15:05 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:ad02:79a8:c1f1:31b1] has quit [Ping timeout: 244 seconds] 15:07 -!- joetor5 [~Thunderbi@user/joetor5] has quit [Remote host closed the connection] 15:07 -!- joetor5 [~Thunderbi@user/joetor5] has joined #bitcoin-core-dev 15:11 -!- enochazariah [~enochazar@102.91.93.182] has quit [Remote host closed the connection] 15:12 -!- flag [~flag@81.56.46.144] has quit [Ping timeout: 244 seconds] 15:13 -!- flag [~flag@81.56.46.144] has joined #bitcoin-core-dev 15:22 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:5cb9:c0b0:f5dc:65c4] has joined #bitcoin-core-dev 15:41 -!- mcey_ [~emcy@148.252.129.85] has quit [Remote host closed the connection] 15:41 -!- mcey_ [~emcy@148.252.129.85] has joined #bitcoin-core-dev 16:00 -!- bcdarc [~bcdarc@4.53.92.114] has quit [Server closed connection] 16:01 -!- bcdarc [~bcdarc@4.53.92.114] has joined #bitcoin-core-dev 16:05 -!- sdaftuar [~sdaftuar@user/sdaftuar] has quit [Server closed connection] 16:06 -!- sdaftuar [~sdaftuar@user/sdaftuar] has joined #bitcoin-core-dev 16:07 -!- joetor5 [~Thunderbi@user/joetor5] has quit [Quit: joetor5] 16:07 -!- mudsip [~mudsip@user/mudsip] has joined #bitcoin-core-dev 16:09 -!- gossie [~gossie@2001:1c02:105:3500:852c:d422:a612:e394] has quit [Ping timeout: 252 seconds] 16:11 -!- gossie [~gossie@2001:1c02:105:3500:852c:d422:a612:e394] has joined #bitcoin-core-dev 16:37 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 248 seconds] 16:45 -!- mudsip [~mudsip@user/mudsip] has quit [] 16:48 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:5cb9:c0b0:f5dc:65c4] has quit [Ping timeout: 272 seconds] 16:59 -!- Guest8 [~Guest69@102.90.100.37] has joined #bitcoin-core-dev 17:00 -!- Guest8 [~Guest69@102.90.100.37] has quit [Client Quit] 17:01 -!- yusuf4396 [~yusuf4396@102.90.100.37] has joined #bitcoin-core-dev 17:05 -!- yusuf4396 [~yusuf4396@102.90.100.37] has quit [Client Quit] 17:39 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Remote host closed the connection] 18:10 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 18:11 -!- PaperSword [~Thunderbi@50.126.92.170] has quit [Quit: PaperSword] 18:11 -!- PaperSword [~Thunderbi@50.126.92.170] has joined #bitcoin-core-dev 18:24 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 252 seconds] 18:29 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity] 18:52 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 19:10 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 276 seconds] 19:16 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 19:37 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev 19:47 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:98df:14c:f12a:69b9] has joined #bitcoin-core-dev 19:52 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 265 seconds] 19:52 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:98df:14c:f12a:69b9] has quit [Ping timeout: 265 seconds] 20:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev 20:13 -!- robszarka [~szarka@2603:3003:4eac:100:cd7b:2cab:f98a:4a5b] has joined #bitcoin-core-dev 20:16 -!- szarka [~szarka@2603:3003:4eac:100:58ef:f779:9e5:d0e] has quit [Ping timeout: 260 seconds] 21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection] 21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev 21:14 -!- jarthur [~jarthur@user/jarthur] has quit [Ping timeout: 276 seconds] 21:46 -!- vasild [~vd@user/vasild] has quit [Remote host closed the connection] 21:46 -!- jerryf [~jerryf@user/jerryf] has quit [Remote host closed the connection] 21:47 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev 21:47 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-core-dev 21:50 -!- Christoph_ [~Christoph@2a02:810d:1399:b700:d06f:2a2d:9306:b9c8] has joined #bitcoin-core-dev 21:50 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:b4aa:7f5e:e6c8:5405] has joined #bitcoin-core-dev 21:55 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:b4aa:7f5e:e6c8:5405] has quit [Ping timeout: 276 seconds] 22:28 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Remote host closed the connection] 22:51 -!- eremitah [~int@191.23.19.78] has joined #bitcoin-core-dev 22:51 -!- eremitah [~int@user/eremitah] has changed host 22:59 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 23:04 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:7810:18c2:e3a3:1f7d] has joined #bitcoin-core-dev 23:08 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:7810:18c2:e3a3:1f7d] has quit [Ping timeout: 248 seconds] 23:15 -!- kevkevin [~kevkevin@209.242.39.30] has quit [Ping timeout: 248 seconds] 23:35 -!- eremitah [~int@user/eremitah] has quit [Quit: quit] 23:35 -!- eremitah [~int@user/eremitah] has joined #bitcoin-core-dev 23:36 -!- mcey_ [~emcy@148.252.129.85] has quit [Ping timeout: 245 seconds] 23:40 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:801c:21af:a3f5:6508] has joined #bitcoin-core-dev 23:43 -!- kevkevin [~kevkevin@209.242.39.30] has joined #bitcoin-core-dev 23:59 -!- fgarau [~fgarau@2a00:23c5:cfb4:2c01:801c:21af:a3f5:6508] has quit [Ping timeout: 272 seconds] --- Log closed Fri Jul 18 00:00:45 2025