--- Log opened Thu Jan 11 00:00:26 2024
00:08 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
00:26 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
00:35 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
00:38 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
00:59 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:05 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
01:05 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
01:15 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:19 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds]
01:20 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
01:21 < bitcoin-git> [bitcoin] BrandonOdiwuor opened pull request #29223: wallet: Refactor DumpWallet function to accept -dumpfile path argument (master...dumpwallet-refactor) https://github.com/bitcoin/bitcoin/pull/29223
01:22 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:25 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 264 seconds]
01:33 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
01:44 -!- Chris_Stewart_5 [~Chris_Ste@87.249.134.5] has quit [Ping timeout: 245 seconds]
01:46 -!- Chris_Stewart_5 [~Chris_Ste@87.249.134.17] has joined #bitcoin-core-dev
01:47 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has quit [Ping timeout: 240 seconds]
01:49 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has joined #bitcoin-core-dev
01:54 -!- thodg [~thodg@2a01:e0a:26a:3152:ded6:107e:e927:4320] has quit [Read error: Connection reset by peer]
01:56 -!- thodg [~thodg@2a01:e0a:26a:3152:664:20aa:2926:add5] has joined #bitcoin-core-dev
01:56 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
02:03 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/fcacbab4878e...522b8370d92a
02:03 < bitcoin-git> bitcoin/master 4fdd836 Mark Friedenbach: Use hardened runtime on macOS release builds.
02:03 < bitcoin-git> bitcoin/master 522b837 fanquake: Merge bitcoin/bitcoin#29127: Use hardened runtime on macOS release builds.
02:03 < bitcoin-git> [bitcoin] fanquake merged pull request #29127: Use hardened runtime on macOS release builds. (master...hardened-macos-runtime) https://github.com/bitcoin/bitcoin/pull/29127
02:06 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
02:07 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
02:12 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 256 seconds]
02:18 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
02:23 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
02:27 -!- Guest6 [~Guest6@203.205.141.89] has joined #bitcoin-core-dev
02:40 -!- Guest6 [~Guest6@203.205.141.89] has quit [Quit: Client closed]
02:54 -!- puchka [~puchka@185.203.122.162] has quit [Ping timeout: 260 seconds]
02:56 -!- puchka [~puchka@185.203.122.158] has joined #bitcoin-core-dev
02:58 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
03:05 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 276 seconds]
03:15 < bitcoin-git> [bitcoin] fanquake opened pull request #29225: ci: move CMake into base packages (master...add_cmake_base_packages) https://github.com/bitcoin/bitcoin/pull/29225
03:29 -!- Guest98 [~Guest98@84.54.94.125] has joined #bitcoin-core-dev
03:30 -!- Guest98 [~Guest98@84.54.94.125] has left #bitcoin-core-dev []
03:30 -!- abdul2004 [~abdul2004@84.54.94.125] has joined #bitcoin-core-dev
03:36 < bitcoin-git> [bitcoin] dergoegge opened pull request #29226: Revert "build: Fix regression in "ARMv8 CRC32 intrinsics" test" (master...2024-01-revert-228d6a29) https://github.com/bitcoin/bitcoin/pull/29226
03:41 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
03:46 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
03:49 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has joined #bitcoin-core-dev
03:50 < bitcoin-git> [bitcoin] glozow opened pull request #29227: log mempool loading progress (master...2024-01-mempool-load-logs) https://github.com/bitcoin/bitcoin/pull/29227
03:52 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/522b8370d92a...4ae5171d42bd
03:52 < bitcoin-git> bitcoin/master 154fcce dergoegge: [fuzz] Improve fuzzing stability for ellswift_roundtrip harness
03:52 < bitcoin-git> bitcoin/master 4ae5171 fanquake: Merge bitcoin/bitcoin#29219: fuzz: Improve fuzzing stability for ellswift_...
03:52 < bitcoin-git> [bitcoin] fanquake merged pull request #29219: fuzz: Improve fuzzing stability for ellswift_roundtrip harness (master...2024-01-fuzz-stability-ellswift_roundtrip) https://github.com/bitcoin/bitcoin/pull/29219
03:52 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:02 -!- abdul2004 [~abdul2004@84.54.94.125] has quit [Quit: Client closed]
04:09 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
04:10 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:13 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has quit [Quit: Client closed]
04:13 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has joined #bitcoin-core-dev
04:14 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
04:52 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:57 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
04:57 -!- JesterHodl [~JesterHod@147.161.248.89] has joined #bitcoin-core-dev
05:07 -!- Leo11 [~Leo@2a09:bac3:3322:150f::219:b5] has joined #bitcoin-core-dev
05:07 -!- instagibbs8 [~instagibb@pool-100-15-116-202.washdc.fios.verizon.net] has joined #bitcoin-core-dev
05:08 -!- instagibbs [~instagibb@pool-100-15-116-202.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds]
05:08 -!- instagibbs8 is now known as instagibbs
05:09 -!- Leo11 [~Leo@2a09:bac3:3322:150f::219:b5] has quit [Client Quit]
05:09 -!- Leo57 [~Leo@2a09:bac3:3322:150f::219:b5] has joined #bitcoin-core-dev
05:09 -!- Guest55 [~Guest55@125.red-79-159-75.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
05:10 -!- Guest55 [~Guest55@125.red-79-159-75.dynamicip.rima-tde.net] has quit [Client Quit]
05:10 -!- Leo57 [~Leo@2a09:bac3:3322:150f::219:b5] has quit [Client Quit]
05:10 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
05:11 -!- darosior1 [~darosior@109.205.214.46] has joined #bitcoin-core-dev
05:11 -!- JesterHodl [~JesterHod@147.161.248.89] has quit [Quit: Client closed]
05:11 -!- JesterHodl [~JesterHod@147.161.248.89] has joined #bitcoin-core-dev
05:12 -!- darosior [~darosior@109.205.214.46] has quit [Ping timeout: 276 seconds]
05:12 -!- darosior1 is now known as darosior
05:13 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has quit [Ping timeout: 250 seconds]
05:15 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
05:17 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has joined #bitcoin-core-dev
05:18 -!- angusp [9e8eed9774@2604:bf00:561:2000::1048] has joined #bitcoin-core-dev
05:20 -!- utzig [d5d7f726e3@2604:bf00:561:2000::71] has joined #bitcoin-core-dev
05:21 -!- pablomartin4btc [~pablomart@89.40.212.238] has joined #bitcoin-core-dev
05:21 -!- Guest66 [~Guest66@c-24-125-96-34.hsd1.ga.comcast.net] has joined #bitcoin-core-dev
05:25 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
05:25 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
05:25 -!- Leo12 [~Leo@185.93.3.195.adsl.inet-telecom.org] has joined #bitcoin-core-dev
05:32 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has quit [Quit: Client closed]
05:32 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
05:33 < bitcoin-git> [bitcoin] maflcko opened pull request #29228: test: Remove all-lint.py script (master...2401-test-rm-wrap-wrap-) https://github.com/bitcoin/bitcoin/pull/29228
05:35 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
05:38 -!- GregTonoski [~GregTonos@46.205.194.198.nat.ftth.dynamic.t-mobile.pl] has joined #bitcoin-core-dev
05:38 -!- Guest66 [~Guest66@c-24-125-96-34.hsd1.ga.comcast.net] has quit [Quit: Client closed]
05:39 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
05:40 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
05:41 -!- mudsip [~mudsip@user/mudsip] has joined #bitcoin-core-dev
05:41 -!- angusp [9e8eed9774@2604:bf00:561:2000::1048] has quit [Ping timeout: 260 seconds]
05:42 -!- utzig [d5d7f726e3@2604:bf00:561:2000::71] has quit [Ping timeout: 260 seconds]
05:44 -!- mudsip [~mudsip@user/mudsip] has quit [Client Quit]
05:44 -!- Leo75 [~Leo@2a09:bac2:34c6:be::13:2a8] has joined #bitcoin-core-dev
05:45 -!- Leo75 [~Leo@2a09:bac2:34c6:be::13:2a8] has quit [Client Quit]
05:50 < maflcko> jamesob: I guess it is a question of how much the "local" docker image should mirror the CI task behavior. Currently compilation is cached locally, but that can be changed to just compile every time, because it is fast.
05:50 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 256 seconds]
05:50 < maflcko> Also, you should be able to move RUN install.sh up to right after COPY install.sh, to get the same speedup
05:51 -!- GregTonoski [~GregTonos@46.205.194.198.nat.ftth.dynamic.t-mobile.pl] has quit [Quit: Client closed]
05:51 -!- utzig [d5d7f726e3@2604:bf00:561:2000::71] has joined #bitcoin-core-dev
05:53 -!- JozefH [~JozefH@ip-89-176-231-149.bb.vodafone.cz] has quit [Ping timeout: 250 seconds]
05:53 < maflcko> Ok, that'd also require splitting up install.sh into two steps
05:53 -!- Retropex [~Retropex@2a09:bac2:34c6:be::13:2a8] has joined #bitcoin-core-dev
05:53 -!- mode/#bitcoin-core-dev [+o achow101] by ChanServ
05:56 -!- utzig [d5d7f726e3@2604:bf00:561:2000::71] has quit [Ping timeout: 276 seconds]
05:56 -!- ns-xvrn [~ns-xvrn@c-24-125-96-34.hsd1.ga.comcast.net] has joined #bitcoin-core-dev
05:58 -!- wk057 [wizkid@tsarbo.mba] has joined #bitcoin-core-dev
05:59 < reardencode> if there's any discussion of lnhance at today's meeting, I'm available.
06:00 -!- ns-xvrn [~ns-xvrn@c-24-125-96-34.hsd1.ga.comcast.net] has quit [Client Quit]
06:00 <@achow101> #startmeeting
06:00 < dergoegge> hi
06:00 < glozow> hi
06:00 <@achow101> #bitcoin-core-dev Meeting: achow101 _aj_ amiti ariard aureleoules b10c BlueMatt brunoerg cfields darosior dergoegge dongcarl fanquake fjahr furszy gleb glozow hebasto instagibbs jamesob jarolrod jonatack josibake kallewoof kanzure kouloumos kvaciral laanwj LarryRuane lightlike luke-jr MacroFake Murch phantomcircuit pinheadmz promag provoostenator ryanofsky sdaftuar S3RK stickies-v sipa theStack TheCharlatan vasild
06:00 < Murch[m]> Hi
06:00 < furszy> hi
06:00 <@achow101> There are 2 preproposed meeting topics this week. Any last minute ones to add?
06:00 < LarryRuane> Hi
06:00 < lightlike> Hi
06:01 < josie> hi
06:01 < stickies-v> hi
06:01 < luke-jr_> hi
06:01 < Sjors[m]> hi
06:01 <@achow101> #topic package relay updates (glozow)
06:01 < glozow> #28948 still the PR to review. Still working on implementing your comments achow101 (thanks!).
06:01 <@gribble> https://github.com/bitcoin/bitcoin/issues/28948 | v3 transaction policy for anti-pinning by glozow · Pull Request #28948 · bitcoin/bitcoin · GitHub
06:02 < glozow> I'm also writing a doc (bip?) and trying to index all the discussion comments / questions / answers.
06:02 -!- GregTonoski [~GregTonos@46.205.194.198.nat.ftth.dynamic.t-mobile.pl] has joined #bitcoin-core-dev
06:02 -!- wk057 [wizkid@user/wk057] has changed host
06:03 < instagibbs> I think it'd be helpful for #28984 if I split off the cluster mempool-y diagram checking parts, if no one objects I'll open that part only?
06:03 <@gribble> https://github.com/bitcoin/bitcoin/issues/28984 | Cluster size 2 package rbf by instagibbs · Pull Request #28984 · bitcoin/bitcoin · GitHub
06:03 < instagibbs> infrastructure + unit/fuzz tests?
06:03 -!- Guest73 [~Guest29@c-24-125-96-34.hsd1.ga.comcast.net] has joined #bitcoin-core-dev
06:03 < TheCharlatan> hi
06:04 <@achow101> instagibbs: seems reasonable
06:04 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
06:04 < glozow> instagibbs: I think it's a good idea. would help reduce the complexity
06:04 < instagibbs> ok, will open the "first cluster mempool PR" to nerd snipe some folks
06:05 < kanzure> hi
06:05 < gleb> hi
06:05 < GregTonoski> hi
06:05 < glozow> also: https://delvingbitcoin.org/t/an-overview-of-the-cluster-mempool-proposal/393
06:06 < pinheadmz> hi
06:06 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has joined #bitcoin-core-dev
06:06 < GregTonoski> Can we talk about spam in Bitcoin and the scope of datacarriersize scope, perhaps?
06:06 <@achow101> GregTonoski: please wait until your topic is announced
06:06 < luke-jr_> GregTonoski: we're on package relay topic right now
06:06 -!- luke-jr_ is now known as luke-jr
06:07 <@achow101> #topic silent payments updates (josie)
06:07 < josie> review happening on #28560
06:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/28560 | wallet, rpc: `FundTransaction` refactor by josibake · Pull Request #28560 · bitcoin/bitcoin · GitHub
06:07 < josie> also had several rounds of review on the BIP and was able to finalize the input hashing
06:08 < josie> i updated the BIP and will be working on #28122 to match the BIP 
06:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/28122 | Silent Payments: Implement BIP352 by josibake · Pull Request #28122 · bitcoin/bitcoin · GitHub
06:08 < josie> thats all for me! 
06:08 <@achow101> is the bip ready to be merged?
06:09 <@achow101> kinda annoying to have to look through the prs list to find it
06:09 < josie> id like to have at least RubenSomsen take a look and sign off after my most recent push 
06:09 < josie> but id say its pretty close to merge
06:09 < josie> but yes, it is v annoying 
06:10 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
06:10 < RubenSomsen> will do
06:10 < josie> ty!
06:10 <@achow101> #topic multiprocess updates (ryanofsky)
06:12 <@achow101> #28921 is the current pr, still waiting on review
06:12 <@gribble> https://github.com/bitcoin/bitcoin/issues/28921 | multiprocess: Add basic type conversion hooks by ryanofsky · Pull Request #28921 · bitcoin/bitcoin · GitHub
06:13 <@achow101> #topic Ad-hoc high priority for review
06:13 <@achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
06:13 < Murch[m]> achow101: Could you please add CoinGrinder?
06:14 < Murch[m]> The code is pretty mature now and I’d love to get it merged before 27, in case the fees shoot up again
06:14 <@achow101> Murch[m]: added
06:14 < Murch[m]> Thanks!
06:16 <@achow101> #topic spam threats and protection in Bitcoin Core (GregTonoski)
06:17 < GregTonoski> Is there any plan to harden anti-spam measures in Bitcoin Core in the next version, perhaps?
06:17 < reardencode> I'd suggest removing all limits on OP_RETURN size/count to reduce impacts on the UTXO set and mitigate long term consequences of the current scamtoken craze.
06:18 < luke-jr> that's the wrong direction
06:18 <@achow101> probably not. as has been stated many times, many contributors do not think that changing policy rules will have an effect
06:18 < luke-jr> I've listed several possible options here FWIW: https://github.com/bitcoin/bitcoin/issues/29187
06:18 < wk057> It doesn't seem to make sense to increase limits for OP_RETURN beyond the original scope of why OP_RETURN was made standard in the first place.
06:18 < luke-jr> achow101: which is nonsense
06:19 <@achow101> it's clearly a controversial topic, I don't think rehashing the same argument here is going to be useful
06:19 < Murch[m]> OP_RETURN was introduced to give a valve for people using more detrimental ways of putting data in the blockchain such as bare multisig
06:19 <@achow101> unless there is something new to say, I would suggest that we move on from this topic
06:19 < luke-jr> achow101: intentionally leaving a vulnerability being actively exploited in, is not acceptable
06:19 < wk057> achow101: there have been serveral new suggestions in #29187 that merit consideration
06:19 <@gribble> https://github.com/bitcoin/bitcoin/issues/29187 | Witness scripts being abused to bypass datacarriersize limit (CVE-2023-50428) · Issue #29187 · bitcoin/bitcoin · GitHub
06:20 < GregTonoski> 2023 was a year of spam in Bitcoin. Isn't it important topic to discuss?
06:20 -!- pB6102 [~pB6102@38.15.96.75] has joined #bitcoin-core-dev
06:20 < dergoegge> not everyone considers it a vulnerability
06:20 < instagibbs> ok we're aware that a PR exists, that's all that's required here 
06:20 <@achow101> wk057: they can be discussed if/when such PRs are opened
06:20 < luke-jr> dergoegge: objectively it is
06:20 < Earnestly> (It's a tad disingenuous to shut down discussion merely because it's controversial; if there is genuine misunderstanding those need to be surfaced. Lots of people are watching and want resolution on this.)
06:20 < josie> what is the goal of bringing this topic? calling other peoples opinions on the matter nonsense and continuing to claim there is a vulnerability (when others dont share that view) is not a discussion 
06:20 < _aj_> instagibbs: the above was an issue, the prior PR is closed, there hasn't been a new PR filed yet, aiui
06:21 < luke-jr> josie: if you disagree, you can set datacarriersize=4000000; it's not an excuse to deny others a fix
06:21 < Murch[m]> I don’t think a policy change by default is going to get merged
06:21 < instagibbs> _aj_ tracking issue even better
06:21 -!- pB6102 [~pB6102@38.15.96.75] has quit [Client Quit]
06:21 < Murch[m]> I could see a new option that makes your node treat inscriptions as non-standard that is off by default be considered
06:21 < _aj_> achow101: (off-topic: tnx for the merge)
06:21 < Murch[m]> Then people who want that can gimp their own node
06:21 -!- pB6102 [~pB6102@38.15.96.75] has joined #bitcoin-core-dev
06:22 < wk057> it's objectively a vulnerability.  the ability to inject data into a system in an unintended way is pretty much the most common exploit in existence. saying it's not a vulnerability is odd.
06:22 < Earnestly> achow101: If the filters are behind a flag, and people can choose to use it, why would that necessarily be a blocker? Does there need to be more robust evidence that the filters prevent the behaviour it's designed to stop?
06:22 < _aj_> wk057: "unintended" is not an objective criterion
06:22 <@achow101> Earnestly: never said that it was
06:22 < instagibbs> again, this is nothing new, there is nothing to discuss here
06:22 < Earnestly> I see, so a PR adding such a feature would be fine
06:23 -!- jkjkjk [~jkjkjk@77.119.197.214.wireless.dyn.drei.com] has joined #bitcoin-core-dev
06:23 < wk057> instagibbs: it merits discussion.  since the original PR was closed for being "controverial", then finding a solution that checks all the boxes would merit discussion for an obvious issue.
06:23 < GregTonoski> Pieter Wuille said that 4MB block is ""pathological" . It occurred in 2023.
06:23 < luke-jr> _aj_: it pretty much is, at least in this case; pretending it was intended is dishonest
06:23 < instagibbs> And I'm done engaging with this. thanks.
06:24 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
06:24 < _aj_> luke-jr: the people sending the spam certainly intend it
06:24 < GregTonoski> 4MB block: 0301e0480b374b32851a9462db29dc19fe830a7f7d7a88b81612b9d42099c0ae
06:24 <@achow101> wk057: since there is an issue open, discussing in that issue should be sufficient
06:24 < luke-jr> _aj_: pfft, so does every attacker
06:24 < Earnestly> I certainly don't want to store this data on my node, is there anything I can do to mitigate it?
06:24 < sipa> Earnestly: run a pruned node
06:24 <@achow101> especially since discussion here is transient
06:24 < Earnestly> sipa: I do, but I don't want to process it (I also want to keep historical nodes as well)
06:25 < instagibbs> Is this the last topic? 
06:25 <@achow101> instagibbs: no
06:25 < reardencode> Earnestly: rot13maxi made a script to invalidate blocks containing inscriptions. it'll put you on your own fork of bitcoin.
06:25 < wk057> achow101: seems this is a broad enough topic to warrant at least some realtime developer discussion to make the solutions that would be acceptable for merge more obvious before dev effort is expended on something that has no hope of merging
06:25 < Murch[m]> Suggestion:... (full message at <https://matrix.bitcoin.ninja/_matrix/media/v3/download/bitcoin.ninja/EVtcNPNYvjzsBmTKCrJgoTdP>)
06:25 <@achow101> Murch[m]: your message was too long
06:26 <@achow101> (matrix bridge elided it)
06:26 < brunoerg> next topic?
06:26 < glozow> fwiw I disagree that this is a vulnerability. I already reviewed 28408 and summarized all of the arguments for/against it, concluding it shouldn't be merged. I have a writeup on my notes repo. I plan on reviewing and opening PRs that I think are important, and this discussion isn't changing that.
06:26 < glozow> #proposedmeetingtopic note to use new logging macros (#28318)
06:26 <@gribble> https://github.com/bitcoin/bitcoin/issues/28318 | logging: Simplify API for level based logging by ajtowns · Pull Request #28318 · bitcoin/bitcoin · GitHub
06:27 < luke-jr> glozow: every argument against it, has been amply refuted already
06:27 < sipa> luke-jr: people clearly disagree with you here
06:27 < Earnestly> glozow: Why wouldn't be considered as such if a specific sequence of operators are selected specifically to bypass OP_RETURN, why don't they just use op_return?
06:27 < wk057> glozow: you seem to have conveniently skipped over some key points in your summary, but that PR is closed, so the discussion is to determine the best way forward from here without wasting additional developer resources
06:27 < glozow> luke-jr: having read through all of the comments and mailing list posts and a lot of twitter, I disagree.
06:27 < reardencode> Earnestly: they don't use OP_RETURN because it is limited to 80 bytes - hence my suggestion.
06:27 < Earnestly> reardencode: Why was it limited?
06:28 <@achow101> wk057: from the existing discussions on the topic, there generally seems to be agreement that a default off option to enable such filters may be acceptable, at least more so than the datacarriersize change
06:28 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 256 seconds]
06:28 < Murch[m]> achow101: Thanks, it was just a summary of above: Make it a default-off optional new configuration option that only applies to inscriptions, and I could see it get merge.
06:28 <@achow101> wk057: does that sufficiently resolve your desire to have a discussion here?
06:28 < wk057> achow101: default off option doesn't address the issue.  I agree it should be an option, but default off doesn't actually solve anything.
06:29 < luke-jr> achow101: Murch[m]: so we add a new option for every new spam scheme?
06:29 < _aj_> luke-jr: for any that are controversial, certainly
06:29 < Murch[m]> If you think that is a useful way of spending your time, be my guest
06:29 < luke-jr> refusing to admit it's a vulnerability, and making such crazy suggestions, just strikes me as dishonesty, sorry
06:29 < Earnestly> luke-jr: Would it be possible to provide a more generic mechanism that reads in a set of rules, in some DSL format, that can be used to filter?
06:29 < _aj_> luke-jr: (and spammers will naturally try to make them all controversial, so...)
06:29 < wk057> that was what I was writing.  so everyone who wants to address a vulnerability needs to get a PR approved for a new option that defaults to allowing exploitation of that vulnerability? that doesn't seem reasonable.
06:30 < Earnestly> In that manner you can then add new rules to this file to catch any new mechanisms used to bypass the original limit
06:30 < wk057> The people exploiting a bug shouldn't really get a say in whether or not the bug is fixed.
06:30 < Murch[m]> I think the topic is now "note to use new logging macros (#28318)", though
06:30 <@gribble> https://github.com/bitcoin/bitcoin/issues/28318 | logging: Simplify API for level based logging by ajtowns · Pull Request #28318 · bitcoin/bitcoin · GitHub
06:30 <@achow101> Murch[m]: not yet
06:30 < Earnestly> luke-jr: So instead of having to hardcode a set of rules directly in the codebase they can be expressed as a file
06:31 < _aj_> Murch[m]: that was proposed, not switched to
06:31 < Murch[m]> ah, you’re right
06:31 <@achow101> I think the specific details regarding the implementation of such a flag can be discussed in its PR, once open
06:31 < sipa> sigh, there is economic demand for block space, whether you like it or not - the buyers and sellers of that space both want the transaction to occur, i don't see what anyone thinks they can do about that
06:31 < dergoegge> can we move on?
06:31 < instagibbs> dergoegge +1
06:31 < kevkevin> dergoegge +1
06:31 < brunoerg> dergoegge +1
06:31 < josie> dergoegge +1 
06:31 < glozow> dergoegge +1
06:31 <@achow101> #topic bip324 defaults for 27.0 (achow101)
06:31 < Murch[m]> dergoegge: +1
06:32 < wk057> achow101: since there's been development time on the original PR that's been "spinning wheels", it would make sense to try to limit further wasted efforts
06:32 <@achow101> The 27.0 feature freeze is in a month, so what defaults should we try to get for bip324 in before then?
06:32 < instagibbs> re:bip324, did all the open testing PRs get merged? it seems t obe getting reasonable runtime as I've seen both incoming and outgoing v3 connections
06:32 < instagibbs> v2
06:32 < sipa> there is the big functional test PR, #24748
06:32 <@gribble> https://github.com/bitcoin/bitcoin/issues/24748 | test/BIP324: functional tests for v2 P2P encryption by stratospher · Pull Request #24748 · bitcoin/bitcoin · GitHub
06:33 < sipa> which i consider the one blocker to enabling bip324 b
06:33 < sipa> y default
06:33 < instagibbs> that was my impression as well
06:33 <@achow101> I think it would be good to have v2transport enable trying v2 for all outbound connections. as it is now, people don't seem to fully get that the only way to have a v2 outbound is with the addnode rpc
06:34 < _aj_> sipa: so it should go on the high-pri list?
06:34 < sipa> achow101: not anymore since #29058
06:34 <@gribble> https://github.com/bitcoin/bitcoin/issues/29058 | net, cli: use v2transport for manual/addrfetch connections, add to -netinfo by mzumsande · Pull Request #29058 · bitcoin/bitcoin · GitHub
06:34 <@achow101> -addnode is still needed though
06:34 < josie> _aj_ +1, was surprised the func test PR was still open
06:34 -!- PatBoy [~viva.el-b@cryption.cn] has joined #bitcoin-core-dev
06:34 < lightlike> achow101: -connect also works now
06:35 -!- Guest59 [~Guest59@12.220.59.2] has joined #bitcoin-core-dev
06:35 < instagibbs> i have a non-manual outbound v2 on v26, did I previously -connect it or something?
06:35 < sipa> achow101: for automatic connections, if both sides run with `-v2transport`, and the service flag propagated ahead of time, a bip324 connection will be used
06:35 < instagibbs> sipa ah ok 👍
06:35 -!- Guest19 [~Guest34@2a00:20:c012:92e8:b168:7c06:a120:5c0] has joined #bitcoin-core-dev
06:35 -!- pB6102 [~pB6102@38.15.96.75] has quit [Quit: Client closed]
06:36 < glozow> _aj_: added
06:36 <@achow101> sipa: really? my previously addnode'd connections don't seem to use v2 after I restart
06:37 < sipa> achow101: i was talking about automatic connections, not manual ones
06:37 < sipa> manual ones will all be v2 since 29058
06:37 < sipa> i think?
06:38 -!- Guest19 [~Guest34@2a00:20:c012:92e8:b168:7c06:a120:5c0] has quit [Client Quit]
06:38 -!- jamesob [~jamesob@108.44.248.162] has quit [Quit: The Lounge - https://thelounge.chat]
06:38 -!- jamesob443688173 [~jamesob@108.44.248.162] has joined #bitcoin-core-dev
06:38 -!- Retropex [~Retropex@2a09:bac2:34c6:be::13:2a8] has quit [Quit: Client closed]
06:38 -!- jamesob [~jamesob@108.44.248.162] has joined #bitcoin-core-dev
06:39 -!- Guest73 [~Guest29@c-24-125-96-34.hsd1.ga.comcast.net] has quit [Quit: Client closed]
06:39 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has joined #bitcoin-core-dev
06:39 < lightlike> yes, if specified with the -addnode bitcoind command. if you use the addnode rpc, you have to use the option.
06:39 <@achow101> not sure. will try to test a bit more then
06:39 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has quit [Client Quit]
06:40 <@achow101> anyways, I think we should try to get #24748 in to take a look at defaults for 27.0
06:40 <@gribble> https://github.com/bitcoin/bitcoin/issues/24748 | test/BIP324: functional tests for v2 P2P encryption by stratospher · Pull Request #24748 · bitcoin/bitcoin · GitHub
06:41 <@achow101> #topic note to use new logging macros (#28318) (glozow)
06:41 <@gribble> https://github.com/bitcoin/bitcoin/issues/28318 | logging: Simplify API for level based logging by ajtowns · Pull Request #28318 · bitcoin/bitcoin · GitHub
06:41 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has joined #bitcoin-core-dev
06:41 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has quit [Quit: Client closed]
06:41 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
06:41 < glozow> Just want to bring it to people's attention, please use the new macros in new code.
06:42 <@achow101> Can the old ones be scripted-diff'd away?
06:42 < _aj_> probably should do a scripted diff at least for net_processing; https://github.com/bitcoin/bitcoin/pull/28318#issuecomment-1701170263
06:42 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has quit [Client Quit]
06:42 < jonatack> Hi
06:42 < glozow> I think that's a good idea. Would be nice to have more unified logging across the codebase
06:42 < stickies-v> see https://github.com/bitcoin/bitcoin/blob/master/doc/developer-notes.md#logging for how to use the new macros
06:42 -!- Leo12 [~Leo@185.93.3.195.adsl.inet-telecom.org] has quit [Ping timeout: 250 seconds]
06:43 < josie> glozow: +1 
06:43 < jonatack> Would be good for someone to open a PR to simplify the API for level based logging after that merge
06:43 < lightlike> there will be tons of conflicts. maybe do it after the branch-off or something?
06:43 <@achow101> lightlike: good point
06:43 < _aj_> lightlike: it's a scripted diff so should be easy to maintain until the branch off
06:44 -!- Chris_Stewart_5 [~Chris_Ste@87.249.134.17] has quit [Ping timeout: 264 seconds]
06:45 <@achow101> Any other topics to discuss?
06:45 < fanquake> Why is after branch off better?
06:45 < fanquake> There's still the same number of conflicts
06:45 < fanquake> and backports are now just harder to do
06:45 -!- itme_brain [~bryan@74.199.203.78] has joined #bitcoin-core-dev
06:45 < jonatack> The goal and review feedback I gave was to have a unified interface of one single Log() macro.
06:45 < _aj_> after feature freeze maybe
06:45 < maflcko> It will be a scripted-diff, but not a refactor, right? The log output will change slightly, to include "warning" or "error" prefixes?
06:46 < _aj_> maflcko: a refactor, log output won't change
06:46 < lightlike> fanquake: so that higher-prioritised projects that still need to get into v27 are not delayed by this.
06:46 < glozow> jonatack: hm, I don't really think that'd be better. This way we use the same macro the vast majority of the time, and don't need to pass in an arg for all of them.
06:46 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has joined #bitcoin-core-dev
06:46 < jamesob> #proposedmeetingtopic assumeutxo chainparams merge when?
06:46 < glozow> I'm not a fan of the verbosity of that approach
06:46 < dergoegge> glozow: +1
06:46 < maflcko> _aj_: A right
06:46 < jonatack> Also, that merge invalidated the 2 ACKs for a bugfix open since almost a year now https://github.com/bitcoin/bitcoin/pull/27231
06:47 < glozow> after feature freeze seems fine
06:47 < fanquake> lightlike: right, not sure there would be "tons" of conflicts in the high-prio PRs though? I'll take a look
06:47 < jonatack> on the blockers list. Oh well :)
06:47 <@achow101> jonatack: there's only one ack, and (althought not explicitly said) a nack
06:47 < _aj_> jonatack: that PR had unaddressed feedback since september...
06:47 <@achow101> and no activity for a long time
06:48 < maflcko> jonatack: Is it still relevant after the merge?
06:48 < maflcko> Wasn't "NONE" removed anyway?
06:48 < _aj_> maflcko: aspects of it are, yes
06:48 < maflcko> ok
06:48 < glozow> ISTM the project ended up choosing an alternate approach maybe just close that PR? we don't need more logging fragmentation
06:48 -!- test__ is now known as _flood
06:48 < jonatack> glozow: a single Log(level, category) is a simple as it gets.  Multiple macros with differing APIs requires developers to remember more context, and necessitates more code, docs, and test coverage
06:49 < stickies-v> a single function doesn't equal a simple interface though
06:49 -!- Guest44 [~Guest44@2a00:20:c012:92e8:b168:7c06:a120:5c0] has quit [Client Quit]
06:49 < lightlike> fanquake: I think there is no PR yet with the scripted diff, so probably best to open that and look just how many conflicts threre actually are.
06:49 < jonatack> The new APIs don't all take the same arguments. Devs will have to remember which macros take which parameters. Etc.
06:50 <@achow101> I already don't remember what macros take which parameters, so that's nothing new
06:50 < _aj_> lightlike: +1
06:50 -!- Guest59 [~Guest59@12.220.59.2] has quit [Quit: Client closed]
06:50 < jamesob> jonatack: yeah, that I do have beef with - left some commentary in the recent PR
06:50 < jonatack> jamesob: yes
06:51 <@achow101> anyways, open prs and let's discuss there
06:51 <@achow101> #topic assumeutxo chainparams merge when? (jamesob)
06:51 < maflcko> Seems a bit early when there are still outstanding bugs and crashes, no?
06:51 < jamesob> So it's not really clear to me what the criteria is for when we're ready to merge the assumeutxo PRs. IMO it's pretty low risk to do so and let "expert users" start calling the RPC to make use of it
06:52 < sipa> shouldn't we figure out distribution/P2P fetching of chainstates before nailing that down, as it may mean we need to change serialization format?
06:52 < jamesob> Are there bugs and crashes?
06:52 < maflcko> Yes
06:52 < sipa> i guess it's fair that there is no problem changing the format afterwards
06:52 < jamesob> sipa: I think that will take a very long time to do
06:53 < jamesob> maflcko: mind actually referencing the bugs and crashes?
06:53 < jonatack> glozow: just close which PR, please?  The bugfix is still relevant.
06:53 < fanquake> also need to decide about things like #28598
06:53 <@gribble> https://github.com/bitcoin/bitcoin/issues/28598 | assumeutxo: Ensure transactions are not presented as confirmed until background sync is complete · Issue #28598 · bitcoin/bitcoin · GitHub
06:53 < jamesob> I'm aware of a  number of refactoring/cleanup/test PRs that are proposed, some of which IMO are matters of taste
06:54 < maflcko> jamesob: Sorry, I am looking for it ...
06:54 < instagibbs> there should probably(still?) be a tracking issue sounds like
06:55 < jamesob> Anyway, I'm not saying we should merge the params now - but it would be nice to develop an understanding of when we're ready for expert users to start trying it out for real
06:55 < maflcko> #28791 
06:55 <@gribble> https://github.com/bitcoin/bitcoin/issues/28791 | snapshots: dont core dump when running -checkblockindex after `loadtxoutset` by maaku · Pull Request #28791 · bitcoin/bitcoin · GitHub
06:55 < jamesob> I really don't think it should just hang out waiting for a P2P scheme to come along, or for the dump format to change
06:55 < _aj_> i don't see any "bugs and crashes" in the open issues list under a search for assumeutxo? be good to add an issue if there's not one already
06:55 < sipa> jamesob: i'm not saying wait for it, i'm saying work on it!
06:56 < jamesob> sipa: ain't gonna be me!
06:56 < maflcko> _aj_: "crash" -> "core dump"
06:56 < sipa> but fair enough, if we expect that not to happen anytime soon, it may be reasonable to go for a "experts use only" deployment before that part is fleshed out
06:56 < jamesob> maflcko: thanks for the link
06:57 <@achow101> I think enabling it for the rpc should be fine to do prior to figuring out distribution
06:57 -!- sliv3r__ [~sliv3r__@125.red-79-159-75.dynamicip.rima-tde.net] has quit [Quit: Client closed]
06:57 <@achow101> but also crashes should be fixed first
06:57 < fanquake> #28616 the PR for above
06:57 < jamesob> achow101: agreed
06:57 <@gribble> https://github.com/bitcoin/bitcoin/issues/28616 | Show transactions as not fully confirmed during background validation by Sjors · Pull Request #28616 · bitcoin/bitcoin · GitHub
06:57 <@achow101> Anything else to discuss in our last few minutes today?
06:57 < jamesob> I'll review that Sjors wallet PR
06:59 < _aj_> so fix known crash bugs, then add mainnet params/update testnet/signet params?
06:59 <@achow101> sounds like it
06:59 < fanquake> then decide on how to represent this to users. if anything needs changing or not
06:59 < instagibbs> experimental "add footgun here", let pre-packaged node distros try it out, seems natural
07:00 <@achow101> #endmeeting
07:00 < _aj_> maflcko: "assumeutxo" -> "loadtxoutset" was what i actually needed
07:00 < jamesob> instagibbs: right
07:00 < jonatack> achow101: "I already don't remember what macros take which parameters, so that's nothing new" -> right, the idea was to fix that.
07:01 < _aj_> unconditional logging just takes the message, conditional logging takes a category. unconditional levels are Error, Warning and Info
07:01 < _aj_> which levels are unconditional is something you need to know anyway, or you'll flood people's logs
07:02 < jonatack> unconditional logging depends on what level the user specifies
07:02 < _aj_> right, so we should fix that too
07:03 < jonatack> yes. but not hardcode it into moar macros ;)
07:06 -!- puchka [~puchka@185.203.122.158] has quit [Ping timeout: 276 seconds]
07:06 < jonatack> I do appreciate that you added the -loglevelalways option
07:08 < jonatack> as that option is the default I expected the logging to take, but I can at least still use the logging that way
07:11 < bitcoin-git> [bitcoin] Sjors opened pull request #29229: Make (Read/Write)BinaryFile work with char vector (master...2024/01/rw-binary-file) https://github.com/bitcoin/bitcoin/pull/29229
07:11 < jonatack> I don't think a scripted-diff to update all the macros is a good idea until the API is finished and simpler.
07:13 -!- puchka [~puchka@185.203.122.160] has joined #bitcoin-core-dev
07:14 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
07:14 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
07:16 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
07:16 -!- pietre [~pietre@dynamic-095-114-054-006.95.114.pool.telefonica.de] has joined #bitcoin-core-dev
07:17 -!- itme_brain [~bryan@74.199.203.78] has left #bitcoin-core-dev [WeeChat 4.0.4]
07:17 -!- JesterHodl [~JesterHod@147.161.248.89] has quit [Quit: Client closed]
07:20 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
07:23 < Sjors[m]> I've been focused on Stratum v2 stuff, but I'll try to keep my other PR's up to date as well.
07:24 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
07:27 -!- pietre [~pietre@dynamic-095-114-054-006.95.114.pool.telefonica.de] has quit [Quit: Client closed]
07:28 -!- wk057 [wizkid@user/wk057] has quit [Remote host closed the connection]
07:30 < _aj_> jonatack: "unconditional logging depends on what level the user specifies" -- i don't believe that is correct now: https://github.com/bitcoin/bitcoin/pull/28318/commits/ab34dc6012351e7b8aab871dd9d2b38ade1cd9bc . it also doesn't make sense; "unconditional" things aren't conditional...
07:37 -!- itme_brain [~bryan@user/itme-brain/x-8379419] has joined #bitcoin-core-dev
07:38 < jonatack> _aj_: that commit was a buggy copy of this one from the Severity Level parent PR, am opening a pull to fix https://github.com/bitcoin/bitcoin/pull/25203/commits/118c7567f62df2b882877590f232242d7c627a05
07:42 -!- itme_brain [~bryan@user/itme-brain/x-8379419] has left #bitcoin-core-dev []
07:46 < jonatack> s/buggy/incomplete/
07:49 < bitcoin-git> [bitcoin] jonatack opened pull request #29230: doc: update -loglevel help following merge of PR 28318 (master...2024-01-fix-loglevel-help) https://github.com/bitcoin/bitcoin/pull/29230
07:59 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
08:02 < bitcoin-git> [bitcoin] ajtowns opened pull request #29231: Update to new logging API (master...202401-logscripted) https://github.com/bitcoin/bitcoin/pull/29231
08:15 < bitcoin-git> [bitcoin] theuni opened pull request #29232: depends: remove dependency on Darwin libtool (master...depends-no-libtool) https://github.com/bitcoin/bitcoin/pull/29232
08:17 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4ae5171d42bd...12865d21ef6c
08:17 < bitcoin-git> bitcoin/master f3ca6db fanquake: ci: move CMake into base packages
08:18 < bitcoin-git> bitcoin/master 12865d2 fanquake: Merge bitcoin/bitcoin#29225: ci: move CMake into base packages
08:18 < bitcoin-git> [bitcoin] fanquake merged pull request #29225: ci: move CMake into base packages (master...add_cmake_base_packages) https://github.com/bitcoin/bitcoin/pull/29225
08:18 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/12865d21ef6c...014f52550bb1
08:18 < bitcoin-git> bitcoin/master a395218 Hennadii Stepanov: ci, iwyu: Drop backported mappings
08:18 < bitcoin-git> bitcoin/master 014f525 fanquake: Merge bitcoin/bitcoin#29186: ci, iwyu: Drop backported mappings
08:18 < bitcoin-git> [bitcoin] fanquake merged pull request #29186: ci, iwyu: Drop backported mappings (master...240105-iwyu) https://github.com/bitcoin/bitcoin/pull/29186
08:20 -!- Chris_Stewart_5 [~Chris_Ste@68.235.43.136] has joined #bitcoin-core-dev
08:29 < sipa> achow101, lightlike: would it make sense to change `addnode` so that the "v2transport" parameter's default equals the -v2transport setting?
08:29 < sipa> that means for all practical purposes users won't need to set it, but for testing it's still possible to forcibly set it to false
08:29 < achow101> sipa: that makes sense to me
08:30 < sipa> that also makes it practically equivalent to the -addnode setting
08:30 < lightlike> yes, I've also had that thought recently!
08:30 < bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/014f52550bb1...4e104e23816a
08:30 < bitcoin-git> bitcoin/master 997b9a7 Sjors Provoost: test: add assumeutxo wallet test
08:30 < bitcoin-git> bitcoin/master 4e104e2 Ava Chow: Merge bitcoin/bitcoin#28838: test: add assumeutxo wallet test
08:30 < bitcoin-git> [bitcoin] achow101 merged pull request #28838: test: add assumeutxo wallet test (master...2023/11/test-wallet-assume) https://github.com/bitcoin/bitcoin/pull/28838
08:33 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/4e104e23816a...131dd11ffd87
08:33 < bitcoin-git> bitcoin/master ff3f51b Hennadii Stepanov: depends: Include `config.guess` and `config.sub` into `meta_depends`
08:33 < bitcoin-git> bitcoin/master 131dd11 fanquake: Merge bitcoin/bitcoin#28870: depends: Include `config.guess` and `config.s...
08:33 < bitcoin-git> [bitcoin] fanquake merged pull request #28870: depends: Include `config.guess` and `config.sub` into `meta_depends` (master...231114-config) https://github.com/bitcoin/bitcoin/pull/28870
08:41 -!- jkjkjk [~jkjkjk@77.119.197.214.wireless.dyn.drei.com] has quit [Quit: Connection closed]
08:42 -!- GregTonoski [~GregTonos@46.205.194.198.nat.ftth.dynamic.t-mobile.pl] has quit [Quit: Client closed]
08:43 -!- zato [~zato@user/zato] has joined #bitcoin-core-dev
08:48 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/131dd11ffd87...dff6d1884a8e
08:48 < bitcoin-git> bitcoin/master 1f8450f 22388o⚡️: doc: upgrade Bitcoin Core license to 2024
08:48 < bitcoin-git> bitcoin/master dff6d18 fanquake: Merge bitcoin/bitcoin#29222: doc: update Bitcoin Core license to 2024
08:48 < bitcoin-git> [bitcoin] fanquake merged pull request #29222: doc: update Bitcoin Core license to 2024 (master...updateBitcoinLicense2024) https://github.com/bitcoin/bitcoin/pull/29222
08:48 -!- puchka [~puchka@185.203.122.160] has quit [Ping timeout: 264 seconds]
08:52 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 264 seconds]
08:55 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
08:59 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 245 seconds]
09:03 -!- not_reserved [~not_reser@185.153.177.185] has joined #bitcoin-core-dev
09:06 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
09:07 < fanquake> lightlike: see #29231. Conflict list looking minor
09:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/29231 | Update to new logging API by ajtowns · Pull Request #29231 · bitcoin/bitcoin · GitHub
09:08 < lightlike> fanquake: But it only applies it to init? Earlier I thought the idea was to adjust every single log statement in our codebase. 
09:08 < lightlike> (i mean the last commit)
09:10 < fanquake> I think it's also fine to do a handful of scripted diffs now
09:15 < lightlike> yes, no objections.
09:16 < _aj_> lightlike: i picked init because it had a few hits, and seemed unlikely to introduce many conflicts (unlike net or net_processing say)
09:17 < _aj_> lightlike: can just tweak the scripted diff for that commit to apply to other files in future PRs, or whatever
09:17 < bitcoin-git> [bitcoin] achow101 pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/dff6d1884a8e...bb6de1befb9f
09:17 < bitcoin-git> bitcoin/master 37324ae Sebastian Falbesoner: test: use `skip_if_platform_not_linux` helper where possible
09:17 < bitcoin-git> bitcoin/master 4c65ac9 Sebastian Falbesoner: test: detect OS consistently using `platform.system()`
09:17 < bitcoin-git> bitcoin/master 878d914 Sebastian Falbesoner: doc: test: mention OS detection preferences in style guideline
09:17 < bitcoin-git> [bitcoin] achow101 merged pull request #29034: test: detect OS in functional tests consistently using `platform.system()` (master...202312-test-consolidate_os_detection_in_python) https://github.com/bitcoin/bitcoin/pull/29034
09:18 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has joined #bitcoin-core-dev
09:21 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
09:21 < bitcoin-git> [bitcoin] fanquake opened pull request #29233: build: depends move macOS C(XX) FLAGS out of C & CXX (master...dedup_macos_flags) https://github.com/bitcoin/bitcoin/pull/29233
09:21 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
09:24 -!- Aaronvan_ [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
09:26 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Ping timeout: 256 seconds]
09:27 -!- Aaronvan_ is now known as AaronvanW
09:40 < jamesob> fanquake maflcko: can't really grok that msvc wallet failure... don't understand why windows would be unique there
09:42 < fanquake> Yea it's rare for Windows to ever behave uniquely 
09:42 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has quit [Quit: Connection closed for inactivity]
09:42 < jamesob> oh hm, maybe something about windows doesn't permit multiple readers on the same wallet file
09:44 < jamesob> any clue why it wouldn't have failed in the PR's CI run?
10:04 < bitcoin-git> [bitcoin] achow101 pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/bb6de1befb9f...4baa162dbb3c
10:04 < bitcoin-git> bitcoin/master 5fa7460 Jon Atack: Fix -netinfo backward compat with getpeerinfo pre-v26
10:04 < bitcoin-git> bitcoin/master 4baa162 Ava Chow: Merge bitcoin/bitcoin#29212: Fix -netinfo backward compat with getpeerinfo...
10:04 < bitcoin-git> [bitcoin] achow101 merged pull request #29212: Fix -netinfo backward compat with getpeerinfo pre-v26 (master...2024-01-netinfo-transport) https://github.com/bitcoin/bitcoin/pull/29212
10:09 < maflcko> the windows fun tests used to be disabled on PR runs, but are now enabled. So I guess that's why the failure was missed earlier
10:10 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
10:13 < bitcoin-git> [bitcoin] fanquake opened pull request #29235: doc: refer to "Node relay options" in policy/README (master...refer_to_help) https://github.com/bitcoin/bitcoin/pull/29235
10:13 < bitcoin-git> [bitcoin] fanquake closed pull request #29095: Update doc/policy/README.md (master...patch-1) https://github.com/bitcoin/bitcoin/pull/29095
10:24 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 240 seconds]
10:26 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
10:30 < bitcoin-git> [bitcoin] maflcko opened pull request #29236: log: Nuke error(...) (master...2401-log-error-) https://github.com/bitcoin/bitcoin/pull/29236
10:32 -!- pablomartin4btc [~pablomart@89.40.212.238] has quit [Remote host closed the connection]
10:32 -!- pablomartin4btc [~pablomart@89.40.212.238] has joined #bitcoin-core-dev
10:34 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has joined #bitcoin-core-dev
10:37 -!- DarrylTheFish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 252 seconds]
10:44 -!- not_reserved [~not_reser@185.153.177.185] has quit [Quit: Client closed]
10:44 -!- not_reserved [~not_reser@185.153.177.185] has joined #bitcoin-core-dev
10:47 < bitcoin-git> [bitcoin] alfonsoromanz opened pull request #29237: [depends] Allow PATH with spaces in directory names. (master...allow-spaces-for-paths-in-depends) https://github.com/bitcoin/bitcoin/pull/29237
10:49 < bitcoin-git> [bitcoin] fanquake closed pull request #28733: depends: Allow PATH with spaces in directory names. (master...allow-spaces-in-path) https://github.com/bitcoin/bitcoin/pull/28733
10:52 -!- Guest49 [~Guest18@ool-45789c73.dyn.optonline.net] has joined #bitcoin-core-dev
10:53 -!- Guest49 [~Guest18@ool-45789c73.dyn.optonline.net] has quit [Client Quit]
10:53 -!- rzasfo [~rzasfo@ool-45789c73.dyn.optonline.net] has joined #bitcoin-core-dev
10:59 -!- rzasfo [~rzasfo@ool-45789c73.dyn.optonline.net] has quit [Quit: Client closed]
11:04 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has joined #bitcoin-core-dev
11:07 < sforza> hi new here
11:10 < sforza> i have btc-core, how do i set up transaction fee
11:12 < sforza> what does network traffic mean ?, 16mb received 4 mb sent. ive recieved 16mb worth of btc ?
11:13 < sforza> the number of transactions is 16370. these are the number of transactions that have already happened in my node ?
11:13 < sforza> its used 175mb. ive recieved and sent 175mb worth of btc ?
11:13 < sforza> what does it all mean
11:13 < sipa> sforza: i suggest searching/asking on https://bitcoin.stackexchange.com for questions; this channel is for development
11:13 < sforza> ok
11:13 < sforza> thanks
11:18 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 240 seconds]
11:21 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
11:35 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
11:51 -!- GregTonoski [~GregTonos@2a02:a31a:4049:ea80:94cd:ff56:29e1:e0ae] has joined #bitcoin-core-dev
11:51 < sforza> everyone on stackexchange is just getting robbed and scammed
11:51 < sforza> i dont want to be there
11:51 < sforza> no one knows what theyre doing on stackexchange, apparently.
12:06 < sipa> this is off topic here
12:08 < sforza> ok
12:14 -!- DarrylTheFiish [~DarrylThe@user/DarrylTheFish] has quit [Ping timeout: 264 seconds]
12:27 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
13:03 -!- GregTonoski [~GregTonos@2a02:a31a:4049:ea80:94cd:ff56:29e1:e0ae] has quit [Quit: Client closed]
13:06 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has joined #bitcoin-core-dev
13:16 -!- Guest99 [~Guest34@ip-103-51-113-33.mel.xi.com.au] has joined #bitcoin-core-dev
13:17 -!- Guest99 [~Guest34@ip-103-51-113-33.mel.xi.com.au] has quit [Client Quit]
13:19 < jamesob> man the tone has been pretty prickly around the project lately
13:22 -!- x11u [~0x11u@176.42.33.65] has joined #bitcoin-core-dev
13:25 -!- Guest15 [~Guest15@84.69.33.68] has joined #bitcoin-core-dev
13:26 < x11u> exit
13:26 -!- x11u [~0x11u@176.42.33.65] has quit [Quit: WeeChat 3.8]
13:26 -!- Guest15 [~Guest15@84.69.33.68] has quit [Client Quit]
13:27 -!- x11u [~0x11u@176.42.33.65] has joined #bitcoin-core-dev
13:28 -!- x11u [~0x11u@176.42.33.65] has quit [Client Quit]
13:29 < bitcoin-git> [bitcoin] jamesob opened pull request #29238: test: unbreak: exclude windows from wallet_assumeutxo (master...2024-01-au-wallet-fix) https://github.com/bitcoin/bitcoin/pull/29238
13:29 < bitcoin-git> [bitcoin] sipa opened pull request #29239: Make v2transaction default for addnode RPC when enabled (master...202401_default_addnode_bip324) https://github.com/bitcoin/bitcoin/pull/29239
13:31 -!- x11u [~0x11u@176.42.33.65] has joined #bitcoin-core-dev
13:34 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
13:58 -!- salvatoshi_ [~salvatosh@193.46.242.46] has joined #bitcoin-core-dev
13:58 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
14:01 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has quit [Ping timeout: 256 seconds]
14:02 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 240 seconds]
14:02 -!- pablomartin4btc [~pablomart@89.40.212.238] has quit [Ping timeout: 264 seconds]
14:03 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
14:04 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
14:08 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
14:09 -!- x11u [~0x11u@176.42.33.65] has quit [Quit: WeeChat 3.8]
14:16 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
14:23 -!- x11u [~0x11u@176.42.33.65] has joined #bitcoin-core-dev
14:40 -!- vysn [~vysn@user/vysn] has quit [Remote host closed the connection]
14:41 -!- salvatoshi__ [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has joined #bitcoin-core-dev
14:44 -!- salvatoshi_ [~salvatosh@193.46.242.46] has quit [Ping timeout: 256 seconds]
14:56 -!- kevkevin [~kevkevin@2601:241:8703:7b30:7400:c2ce:4264:4ecd] has quit [Remote host closed the connection]
15:03 -!- x11u [~0x11u@176.42.33.65] has quit [Quit: WeeChat 3.8]
15:13 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.1.2]
15:21 -!- jon_atack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
15:23 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
15:27 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has quit [Ping timeout: 250 seconds]
15:28 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Remote host closed the connection]
15:31 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
15:33 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
15:33 -!- salvatoshi__ [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has quit [Ping timeout: 264 seconds]
15:43 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has joined #bitcoin-core-dev
15:50 -!- zato [~zato@user/zato] has quit [Quit: Om mani padme hum]
15:57 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has quit [Ping timeout: 250 seconds]
16:05 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has joined #bitcoin-core-dev
16:30 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
16:34 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
16:48 -!- conman [~con@180-150-21-3.b49615.mel.static.aussiebb.net] has quit [Quit: Konversation terminated!]
16:52 -!- conman [~con@180-150-21-3.b49615.mel.static.aussiebb.net] has joined #bitcoin-core-dev
16:52 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Remote host closed the connection]
16:54 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
17:07 -!- not_reserved [~not_reser@185.153.177.185] has quit [Quit: Client closed]
17:08 -!- Guest53 [~Guest53@89.56.130.147] has joined #bitcoin-core-dev
17:08 -!- Guest53 [~Guest53@89.56.130.147] has quit [Client Quit]
17:18 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
17:19 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
17:31 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
17:49 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
17:53 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 245 seconds]
17:54 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
17:58 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
18:05 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
18:15 -!- sforza [~sforza@ool-45789c73.dyn.optonline.net] has quit [Quit: Client closed]
18:15 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
18:28 -!- Guest3333 [~Guest3333@84.239.49.199] has joined #bitcoin-core-dev
18:28 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:edf4:b9d8:e1ed:9c11] has joined #bitcoin-core-dev
18:33 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:edf4:b9d8:e1ed:9c11] has quit [Ping timeout: 268 seconds]
18:50 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
19:01 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
19:02 -!- Saloframes [~Saloframe@user/Saloframes] has joined #bitcoin-core-dev
19:06 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
19:07 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
19:11 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
19:17 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
19:20 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
19:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
19:23 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
19:31 -!- Guest3333 [~Guest3333@84.239.49.199] has quit [Quit: Client closed]
19:35 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
19:38 -!- johnny9dev [~johnny9de@136.54.29.162] has quit [Ping timeout: 255 seconds]
19:41 -!- johnny9dev [~johnny9de@136.54.29.162] has joined #bitcoin-core-dev
20:01 -!- kevkevin [~kevkevin@104-182-134-253.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev
20:05 -!- kevkevin [~kevkevin@104-182-134-253.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 252 seconds]
20:18 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
20:19 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Remote host closed the connection]
20:19 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
20:31 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
20:36 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
20:40 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 264 seconds]
20:41 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 276 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:02 -!- cloudburst [~Guest11@84.239.49.168] has joined #bitcoin-core-dev
21:04 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:08 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
21:10 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Remote host closed the connection]
21:10 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
21:28 -!- justache [~justache@user/justache] has quit [Quit: ZNC 1.8.2 - https://znc.in]
21:32 -!- justache [~justache@user/justache] has joined #bitcoin-core-dev
21:33 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
21:35 -!- adil [~Thunderbi@2a00:f29:290:ae2e:e184:f1d0:1934:5ab4] has joined #bitcoin-core-dev
21:37 -!- test__ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
21:41 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Remote host closed the connection]
21:42 -!- puchka [~puchka@185.203.122.163] has joined #bitcoin-core-dev
21:43 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev
21:49 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:49 -!- Guest73 [~Guest73@188.138.141.203] has joined #bitcoin-core-dev
21:52 -!- kurt20 [~kurt@139-177-188-177.ip.linodeusercontent.com] has joined #bitcoin-core-dev
21:53 -!- kurt20 [~kurt@139-177-188-177.ip.linodeusercontent.com] has quit [Client Quit]
21:53 -!- kevin37 [~kevin@139-177-188-177.ip.linodeusercontent.com] has joined #bitcoin-core-dev
21:53 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
21:55 -!- justache [~justache@user/justache] has quit [Quit: ZNC 1.8.2 - https://znc.in]
21:58 -!- justache [~justache@user/justache] has joined #bitcoin-core-dev
22:05 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:10 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
22:13 -!- kevin37 [~kevin@139-177-188-177.ip.linodeusercontent.com] has quit [Quit: Client closed]
22:16 -!- adil [~Thunderbi@2a00:f29:290:ae2e:e184:f1d0:1934:5ab4] has quit [Quit: adil]
22:16 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has quit [Remote host closed the connection]
22:16 -!- adil [~Thunderbi@2a00:f29:290:ae2e:e184:f1d0:1934:5ab4] has joined #bitcoin-core-dev
22:17 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has joined #bitcoin-core-dev
22:20 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has quit [Remote host closed the connection]
22:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
22:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
22:22 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:23 -!- bob_x2 [~bob_x@user/bob-x1/x-8934932] has joined #bitcoin-core-dev
22:26 -!- puchka [~puchka@185.203.122.163] has quit [Ping timeout: 264 seconds]
22:26 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 256 seconds]
22:28 < dviola> cloudburst: why are you pming me those links?
22:29 -!- cloudburst [~Guest11@84.239.49.168] has quit [Quit: Client closed]
22:35 -!- Guest11 [~Guest11@84.239.49.168] has joined #bitcoin-core-dev
22:35 -!- Guest11 [~Guest11@84.239.49.168] has quit [Client Quit]
22:37 -!- adam_ [~adam_@84.239.49.168] has joined #bitcoin-core-dev
22:44 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:49 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
22:52 -!- justache [~justache@user/justache] has quit [Read error: Connection reset by peer]
22:52 -!- puchka [~puchka@185.203.122.162] has joined #bitcoin-core-dev
22:55 -!- puchka [~puchka@185.203.122.162] has quit [Client Quit]
22:56 -!- justache [~justache@user/justache] has joined #bitcoin-core-dev
22:58 -!- puchka [~puchka@185.203.122.31] has joined #bitcoin-core-dev
22:59 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
22:59 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has quit [Client Quit]
23:00 -!- justache [~justache@user/justache] has quit [Remote host closed the connection]
23:03 -!- justache [~justache@user/justache] has joined #bitcoin-core-dev
23:06 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:09 -!- vysn [~vysn@user/vysn] has joined #bitcoin-core-dev
23:11 -!- Guest73 [~Guest73@188.138.141.203] has quit [Quit: Client closed]
23:11 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
23:12 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:22 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 276 seconds]
23:24 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:24 -!- adam_ [~adam_@84.239.49.168] has left #bitcoin-core-dev []
23:25 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Remote host closed the connection]
23:25 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
23:28 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 246 seconds]
23:35 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:edf4:b9d8:e1ed:9c11] has joined #bitcoin-core-dev
23:39 -!- kevkevin [~kevkevin@2600:1700:b30:47c0:edf4:b9d8:e1ed:9c11] has quit [Ping timeout: 245 seconds]
--- Log closed Fri Jan 12 00:00:26 2024