--- Log opened Thu Dec 07 00:00:51 2023
00:10 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
00:14 -!- abubakarsadiq_ [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
00:14 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
00:15 -!- vasild [~vd@user/vasild] has quit [Ping timeout: 240 seconds]
00:15 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
00:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
00:15 -!- vasild [~vd@user/vasild] has joined #bitcoin-core-dev
00:30 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
00:35 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Ping timeout: 252 seconds]
00:37 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
00:45 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
00:50 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
00:54 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Remote host closed the connection]
00:55 -!- Guest3 [~Guest3@83.240.139.146] has joined #bitcoin-core-dev
01:01 -!- Guest3 [~Guest3@83.240.139.146] has quit [Quit: Client closed]
01:25 < bitcoin-git> [bitcoin] TheCharlatan opened pull request #29019: mempool: Don't sort in entryAll (master...entryAllNoOrder) https://github.com/bitcoin/bitcoin/pull/29019
01:29 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:33 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 255 seconds]
01:34 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
01:44 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:49 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
01:53 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
01:54 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
01:59 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 276 seconds]
02:01 < bitcoin-git> [bitcoin] fanquake pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/2e8ec6b338a8...dce1dfbc4705
02:01 < bitcoin-git> bitcoin/master 423949a fanquake: depends: add -platform_version to macOS build flags
02:01 < bitcoin-git> bitcoin/master 51c97ff fanquake: build: patch boost process for macOS 14 SDK
02:01 < bitcoin-git> bitcoin/master 8ea45e6 fanquake: build: use macOS 14 SDK (Xcode 15.0)
02:01 < bitcoin-git> [bitcoin] fanquake closed pull request #28349: build: Require C++20 compiler (master...2308-c++20-) https://github.com/bitcoin/bitcoin/pull/28349
02:01 < bitcoin-git> [bitcoin] fanquake merged pull request #28622: build: use macOS 14 SDK (Xcode 15.0) (master...macos_sdk_15) https://github.com/bitcoin/bitcoin/pull/28622
02:03 < bitcoin-git> [bitcoin] maflcko reopened pull request #28349: build: Require C++20 compiler (master...2308-c++20-) https://github.com/bitcoin/bitcoin/pull/28349
03:06 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
03:08 < bitcoin-git> [bitcoin] maflcko opened pull request #29021: refactor: rpc: Pass CBlockIndex by reference instead of pointer  (master...2312-less-segfault-) https://github.com/bitcoin/bitcoin/pull/29021
03:11 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 245 seconds]
03:24 < bitcoin-git> [bitcoin] kashifs opened pull request #29022: Make bitcoin-tx replaceable value optional, #fixes 28638 (master...bitcoin-tx-replaceable-value) https://github.com/bitcoin/bitcoin/pull/29022
03:35 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has quit [Quit: Connection closed for inactivity]
03:37 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
03:41 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 256 seconds]
03:47 -!- Guest56 [~Guest42@188.57.116.74] has joined #bitcoin-core-dev
03:51 -!- Guest56 [~Guest42@188.57.116.74] has quit [Client Quit]
03:54 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:00 < bitcoin-git> [bitcoin] fanquake opened pull request #29023: doc: add historical release notes for 26.0 (master...add_26_0_rel_notes) https://github.com/bitcoin/bitcoin/pull/29023
04:07 -!- zato [~zato@user/zato] has joined #bitcoin-core-dev
04:26 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
04:29 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:33 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
04:42 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
04:47 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 256 seconds]
05:08 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
05:22 < instagibbs> I think glozow is out today, and I'll likely be late for the meeting so I'll just give a quick update now:
05:22 < instagibbs> "V3": #28948 is open and is ready for conceptual/approach feedback. Reminder that this is a stepping stone to enabling pin-resistant transactions
05:22 < instagibbs> Package RBF: I opened #28984 to support 2-transaction package rbf without dependency on "v3". #25038 had them coupled together but there's no inherent reason why. By not coupling these features we can also give slight security boost to already-deployed smart contracts, even though they won't be pin-resistant without opting into "v3". I'd appreciate
05:22 < instagibbs> quick feedback on which version of the PR we want to go forward with, and all kinds of review.
05:22 < instagibbs> A little look ahead: #29001 is the final piece of mempool policy to allow pin-resistant transactions
05:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/28948 | v3 transaction policy for anti-pinning by glozow · Pull Request #28948 · bitcoin/bitcoin · GitHub
05:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/28984 | Cluster size 2 package rbf by instagibbs · Pull Request #28984 · bitcoin/bitcoin · GitHub
05:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/25038 | policy: nVersion=3 and Package RBF by glozow · Pull Request #25038 · bitcoin/bitcoin · GitHub
05:22 <@gribble> https://github.com/bitcoin/bitcoin/issues/29001 | Ephemeral Anchors by instagibbs · Pull Request #29001 · bitcoin/bitcoin · GitHub
05:42 -!- flooded is now known as _flood
05:49 < bitcoin-git> [guix.sigs] Kvaciral closed pull request #987: 26.0 kvaciral all (main...26.0-attestations-all-kvaciral) https://github.com/bitcoin-core/guix.sigs/pull/987
05:49 < bitcoin-git> [guix.sigs] Kvaciral reopened pull request #987: 26.0 kvaciral all (main...26.0-attestations-all-kvaciral) https://github.com/bitcoin-core/guix.sigs/pull/987
05:50 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Remote host closed the connection]
05:56 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-dev
05:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:00 < achow101> #startmeeting
06:00 < murch[m]> Hi
06:00 < stickies-v> 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 < sipa> hi
06:00 < RubenSomsen> hi
06:00 < pinheadmz> hi
06:00 < hebasto> hi
06:00 < vasild> hi
06:00 < gleb> hi
06:01 < achow101> There's one pre-proposed meeting topic this week. Any last minute ones to add to the list?
06:01 < fjahr> hi
06:01 < fanquake> #topic dergoegge merge access in qa-assets
06:01 < fanquake> #topic shortly release cycle for 27.0
06:02 < achow101> #topic package relay updates (glozow)
06:02 < dergoegge> hi
06:02 < fjahr> instagibbs commented on it before the meeting
06:03 < achow101> instagibbs left an update before the meeting, read that
06:03 < Sjors[m]> Hi
06:03 < achow101> #topic silent payments updates (josie)
06:03 < RubenSomsen> josie is back now but I think he may have gotten the meeting time wrong
06:03 < RubenSomsen> No big changes from last week. Still actively taking review on BIP352 and responding to feedback. For the BIP we are still discussing how to handle the outpoints: https://github.com/bitcoin/bips/pull/1458#discussion_r1395934177
06:04 < kanzure> hi
06:04 < josie> hi
06:04 < maxedw> hi
06:04 < josie> haha i did have the meeting time wrong
06:04 < josie> but i am back! 
06:05 -!- pablomartin [~pablomart@193.160.246.225] has joined #bitcoin-core-dev
06:05 < josie> regarding the outpoints, i think we have something that works (hashing one outpoint, and some hardening), but would be nice to have a few eyes on it before i go and start updating the PRs
06:06 < josie> ill also be reviewing #25273 this week 
06:06 <@gribble> https://github.com/bitcoin/bitcoin/issues/25273 | wallet: Pass through transaction locktime and preset input sequences and scripts to CreateTransaction by achow101 · Pull Request #25273 · bitcoin/bitcoin · GitHub
06:06 < achow101> please do
06:06 < josie> (looks like it has a silent merge conflict tho)
06:07 -!- guest-127 [~guest-127@212.129.82.152] has joined #bitcoin-core-dev
06:07 < achow101> hmm, thought I fixed that. will take a look today
06:07 < achow101> #topic multiprocess updates (ryanofsky)
06:07 < josie> cool, thx!
06:08 < ryanofsky> Main next multiprocess PR for review is #28921. There is also serialization PR #28929 which simplifies things for multiprocess code, but is not essential. There is also now a design doc being added in #28978.
06:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/28921 | multiprocess: Add basic type conversion hooks by ryanofsky · Pull Request #28921 · bitcoin/bitcoin · GitHub
06:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/28929 | serialization: Support for multiple parameters by ryanofsky · Pull Request #28929 · bitcoin/bitcoin · GitHub
06:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/28978 | doc: Add multiprocess design doc by ryanofsky · Pull Request #28978 · bitcoin/bitcoin · GitHub
06:08 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
06:08 < abubakarsadiq> hi
06:09 < ryanofsky> That's all I have if you want to go to next topic
06:09 < achow101> #topic Ad-hoc high priority for review
06:10 < achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
06:10 -!- abubakarsadiq_ [uid602234@id-602234.hampstead.irccloud.com] has left #bitcoin-core-dev []
06:12 < achow101> #topic cpp-subprocess integration (hebasto)
06:12 < hebasto> hi all
06:12 < hebasto> a year and a half ago the Replacing Boost Process issue was opened -- #24907
06:12 <@gribble> https://github.com/bitcoin/bitcoin/issues/24907 | RFC: Replacing Boost Process · Issue #24907 · bitcoin/bitcoin · GitHub
06:12 < hebasto> moreover, the recently discovered issue with Boost ASIO forces us to disable the external signer support for Windows, both cross and native builds -- #28967
06:12 <@gribble> https://github.com/bitcoin/bitcoin/issues/28967 | build: disable external-signer for Windows by fanquake · Pull Request #28967 · bitcoin/bitcoin · GitHub
06:12 < hebasto> https://github.com/arun11299/cpp-subprocess was suggested as a potential alternative, which basically is a single header-only C++11 implementation of the Python's `subprocess.Popen` interface
06:12 < hebasto> then theStack developed a branch that replaces Boost.Process with cpp-subprocess; however, some Windows-related issues remained
06:12 < hebasto> I fixed all Windows-related issues and submitted a full solution in #28981. Some of my patches have been accepted upstream already; others are in progress.
06:12 <@gribble> https://github.com/bitcoin/bitcoin/issues/28981 | Replace Boost.Process with cpp-subprocess by hebasto · Pull Request #28981 · bitcoin/bitcoin · GitHub
06:12 < hebasto> the question is: if we agree to use cpp-subprocess, what is the best way to integrate this header into our code base?
06:13 < hebasto> during discussion in the pr, a few options were suggested: 1 - subtree (sipa); 2 - add to the repo directly and prune out the unused code (fanquake); 3 - our fork subtree (hebasto); 4 - external dependency (luke-jr)
06:13 < achow101> is it actively maintained?
06:13 < hebasto> it is
06:14 < fanquake> depends on your definition of maintained
06:14 < sipa> it looks maintained, but not really developed anymore
06:14 < fanquake> the author doesn't actually review things, just insta merges etc
06:15 < sipa> how much of the file do we need?
06:15 < sipa> as in, for option two, how much would we keep?
06:15 < hebasto> maybe ~60..70%
06:16 < fanquake> I just want to avoid another boost process scenario, where upstream wasn't maintained well, and no one from our side actually reviewed any of it, or checked to see how it worked/what it was doing under the hood
06:16 < fanquake> Obviously having a static header in our repo is an improvement, similar to nanobench/tinyformat
06:17 < hebasto> in that case, we can adjust code for C++17/20
06:17 < fanquake> If it's unlikely we'll be pulling many/any updates, that seems better than adding the burnden of a subtree, and we can still prune unused code
06:17 < achow101> I'd be slightly concerned with copyright if we just included it in the repo directly, especially if people come along later and decide to refactor/split it
06:17 < sipa> does it *need* any changes right now?
06:18 < fanquake> Isn't it MIT licenesed?
06:18 < josie> yeah its MIT 
06:18 < fanquake> What is the copyright concern
06:18 < hebasto> it needs Windows-specific fixes
06:18 < achow101> fanquake: the copyright header still needs to follow around any bits of code that we take from the project
06:18 < sipa> hebasto: but it looks like you've had some success already getting fixes upstreamed
06:18 < fanquake> Sure, we wouldn't delete that
06:19 < hebasto> sipa: correct, a couple more needed
06:19 < fanquake> Has anyone actually tested it on non-windows yet?
06:20 < fanquake> Note that upstream also has no macOS CI, but I guess the assumption is no real platform specific code?
06:20 < Sjors[m]> Not yet, will do soon(tm) on both Linux and macOS.
06:20 < hebasto> I tested with ledger on windows only for now
06:20 < fanquake> Ok, lets actually check it works on linux on mac first then
06:21 < sipa> agreed
06:21 < hebasto> okay
06:21 < Sjors[m]> Make sure to test QT, not just the RPC.
06:22 < hebasto> sure :)
06:22 < Sjors[m]> The latter is pretty well tested in the CI
06:22 < achow101> a potential alternative is to just completely rearchitect HWI so that it's a persistent daemon with a RPC interface
06:22 < achow101> but that sounds like a lot of work
06:23 < Sjors[m]> I'd also rather not have it run non stop, and/or manually start it as a seperate thing
06:23 < fanquake> HWI is still also usable without anything subprocess in Core right? Because users could just make the same calls that Core is doing, but themselves?
06:23 < dergoegge> or just have a native c++ (or maybe rust 🦀) lib to interface with the hw wallets?
06:23 < achow101> fanquake: yes
06:24 < josie> dergoegge: i think that exists? https://github.com/bitcoindevkit/rust-hwi
06:24 < dergoegge> but that's just a rust wrapper around hwi.py?
06:24 < Sjors[m]> I think that's just a wrapper?
06:24 < achow101> dergoegge: we don't/didn't want any of the hww stuff compiled in
06:25 < achow101> that would include the usb stack and a bunch of vendor specific things
06:25 < josie> ah gross. i think last time i talked with someone about it, i was under the impression they were going to move it away from being a wrapper 
06:25 < josie> but looks like that hasn't happened 
06:25 < dergoegge> we can also just delete external signer
06:25 < dergoegge> 🏃‍♂️
06:26 < fanquake> Might have to get someone to add a GUI to that Rust thing
06:26 < fanquake> Anyways, be good for some people to at least test the subprocess thing works / is a drop in, before we worry further about how to integrate it
06:27 < achow101> indeed
06:27 < achow101> #topic dergoegge merge access in qa-assets (fanquake)
06:27 < fanquake> quick one for any thoughts
06:27 < fanquake> niklas and marco are are doing 90% of the contributing into qa-assets
06:27 < fanquake> given no one else reviews or merges there, doesn't make sense for me to always be a bottleneck
06:27 < achow101> ack
06:27 < fanquake> so I think it makes sense for niklas to be able to push in new inputs
06:28 < instagibbs> ack
06:28 < josie> ACK
06:28 < fjahr> ack
06:28 < fanquake> good stuff
06:28 < hebasto> ack
06:28 < sipa> ack
06:28 < achow101> maflcko too?
06:28 -!- hernanmarino [~hernanmar@181.98.56.2] has quit [Ping timeout: 255 seconds]
06:29 < darosior> ack
06:29 -!- hernanmarino [~hernanmar@181.98.56.2] has joined #bitcoin-core-dev
06:29 < fanquake> I don't think he wants to merge things. You can ask
06:29 < fanquake> That's all for that topic thought, we can sort out the admin side shortly
06:29 < fanquake> *though
06:29 < achow101> #topic shortly release cycle for 27.0 (fanquake)
06:29 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
06:30 < fanquake> *shorten whoops
06:30 < fanquake> Given that the past few releases have slipped a little, and 26.0 nearly happened during Christmas/New Years
06:30 < fanquake> I think it makes sense to have a shorter 27.0 cycle, and release in March/April. 28.0 in September/October
06:30 < fanquake> So that we move back away from holiday type times, and then keep that cadence going forward
06:30 < fanquake> Releasing around holiday times is bad because people are away etc
06:30 < fanquake> i.e If we have to do a 26.(0).1 soonish, it's not going to be an ideal time
06:30 < achow101> we should just do every 4 months to account for the slip
06:30 < fanquake> how does that account for slip
06:31 < achow101> +4 months from time of previous release
06:31 < sipa> releases are primarily extra work for maintainers; if you're ok with doing more frequent releases, there is little reason not to i think
06:31 < fanquake> So 3 major releases a year?
06:32 < sipa> fanquake: i think what achow101 is suggesting that the effective time between releases becomes (4 months + whatever time the previous one slipped)
06:32 < fanquake> Right, but I'm trying to remove variability
06:32 < fanquake> Othewise you just end up with the same problem again
06:32 < sipa> fanquake: agree
06:32 < stickies-v> strongly in favour of picking the 2 month in the year that we think work best, and being okay with certain releases being a bit more/less spaced apart
06:33 < fanquake> Pinning to ~April and ~Oct for example, means you shouldn't have this issue
06:33 < sipa> i like that idea
06:33 < josie> fanquake, stickies-v: +1
06:33 < stickies-v> it's better for users to have a more predictable release cycle, and it doesn't make things unnecessarily difficult for us. no downsides imo?
06:33 < achow101> is that target release in april, or branch in april?
06:33 < fjahr> yeah, well the two months in the year where the two following months are not too bad ;)
06:33 < _aj_> target the freeze dates, not the release dates?
06:33 < fanquake> I think we are also somewhat on track for an April release anyways, as we've already started merging stuff for 27.0 etc
06:33 < stickies-v> _aj_: +1
06:34 < sipa> so freeze dates in february/august?
06:34 < josie> freeze in feb seems pretty early, why not freeze in march? 
06:35 < sipa> when was the freeze for 26.0?
06:35 < fanquake> https://github.com/bitcoin/bitcoin/issues/27758
06:36 < _aj_> sipa: early october?
06:36 < fanquake> october 8th
06:36 < achow101> it slipped a week though
06:36 < stickies-v> I'd be conservative and assume 2 months between freeze and release. If we want to avoid releasing in December, I think that means freeze in march and september?
06:36 < _aj_> branch off was last october
06:36 < fanquake> So yea, freeze the regular amount of time before april and october
06:36 < sipa> right, so there were basically 2 months between feature freeze and final release
06:37 < sipa> 25.0 was slightly shorter but still almost 8 weeks
06:37 < _aj_> (late october, not last october)
06:37 < achow101> I think we've previously targeted 6 weeks betweek feature freeze and release
06:37 < achow101> but that seems to never pan out, so 8 weeks is fine with me
06:38 < sipa> 24.0 had a 7 week interval between feature freeze and final release
06:38 < fanquake> and the breakdown is normally 1 month of freeze + ~1 month of rc(s)?
06:38 < achow101> normall 2 weeks of freeze
06:39 < fanquake> So freeze mid feb, start rc march, release april
06:39 < fanquake> freeze mid aug, start rc sept, release october?
06:39 < achow101> ack
06:39 < sipa> sgtm
06:39 < josie> ACK
06:39 < stickies-v> ack
06:39 < dergoegge> 👍
06:39 < fanquake> So 2 1/2 months were of merging for 27.0 from now
06:40 < fanquake> Get those features in
06:40 < josie> haha 2 1/2 months, with holidays in between.. I think its going to be a very small release 
06:40 < achow101> Any other topics to discuss?
06:41 < fanquake> Maybe we can fix more bugs than we introduce this time then
06:41 < _aj_> woah
06:41 < josie> fanquake: a christmas miracle! 
06:41 < stickies-v> we could do a transition period where we do 27 one month later than (the new) usual before completely switching to the new schedule?
06:41 < fanquake> Can we not
06:41 < sipa> or we can decide that when the time comes
06:41 < maflcko> hi
06:41 -!- Guest20 [~Guest20@130.105.87.64] has joined #bitcoin-core-dev
06:42 < achow101> stickies-v: what we actually normally do is previous schedule +6 months, which is around april anyways
06:42 < josie> stickies-v: I think what's proposed is fine, more just point out we have a pretty big priority list for 27.0 that likely wont happen 
06:42 < achow101> (the original schedule, not what actually happened)
06:42 < stickies-v> okay
06:42 < josie> but i dont think that should reflect badly on the priority projects experiment
06:42 < sipa> priority list is a set of things we are committed to making progress on - we don't need to finish them
06:43 < josie> sipa: agree! 
06:43 -!- Guest20 [~Guest20@130.105.87.64] has quit [Client Quit]
06:43 < achow101> #endmeeting
06:44 -!- guest-127 [~guest-127@212.129.82.152] has quit [Quit: Client closed]
06:45 < murch[m]> ACK on features freezes being ~Feb 15th and ~Aug 16th going forward, sounds great
06:56 -!- cacrowley [~cacrowley@2607:fb90:7591:5194:cc98:7083:8439:acce] has joined #bitcoin-core-dev
06:58 < bitcoin-git> [bitcoin] maflcko opened pull request #29025: doc: Add link to needs-release-notes label (master...2312-doc-link-rel-notes-) https://github.com/bitcoin/bitcoin/pull/29025
06:59 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
07:06 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Ping timeout: 260 seconds]
07:24 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
07:25 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
07:26 -!- AaronvanW [~AaronvanW@user/AaronvanW] has quit [Quit: Leaving...]
07:30 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
07:39 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
07:43 -!- _flood [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 260 seconds]
07:44 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
07:48 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Ping timeout: 246 seconds]
07:50 < bitcoin-git> [bitcoincore.org] fanquake opened pull request #999: 26.0: add missing release note fragments. (master...add_missing_26_rel_notes) https://github.com/bitcoin-core/bitcoincore.org/pull/999
07:55 < bitcoin-git> [guix.sigs] fanquake pushed 2 commits to main: https://github.com/bitcoin-core/guix.sigs/compare/8ba87ddceca8...ba2cb338f113
07:55 < bitcoin-git> guix.sigs/main 8d5ce05 Dimitri: 26.0 kvaciral all
07:55 < bitcoin-git> guix.sigs/main ba2cb33 fanquake: Merge pull request #987 from Kvaciral/26.0-attestations-all-kvaciral
07:55 < bitcoin-git> [guix.sigs] fanquake merged pull request #987: 26.0 kvaciral all (main...26.0-attestations-all-kvaciral) https://github.com/bitcoin-core/guix.sigs/pull/987
08:02 < bitcoin-git> [bitcoin] fanquake pushed 3 commits to master: https://github.com/bitcoin/bitcoin/compare/dce1dfbc4705...fcdb39d3ee17
08:02 < bitcoin-git> bitcoin/master facf629 MarcoFalke: refactor: Remove unused and fragile string interface from arith_uint256
08:02 < bitcoin-git> bitcoin/master fa63f16 MarcoFalke: test: Add uint256 string parse tests
08:02 < bitcoin-git> bitcoin/master fcdb39d fanquake: Merge bitcoin/bitcoin#28924: refactor: Remove unused and fragile string in...
08:02 < bitcoin-git> [bitcoin] fanquake merged pull request #28924: refactor: Remove unused and fragile string interface from arith_uint256 (master...2311-arith-less-brittle-) https://github.com/bitcoin/bitcoin/pull/28924
08:09 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Remote host closed the connection]
08:14 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
08:21 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
08:21 < cfields> ACK dergoegge for qa-assets
08:23 -!- dviola [~diego@user/dviola] has quit [Ping timeout: 256 seconds]
08:27 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
08:29 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
08:30 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Remote host closed the connection]
08:37 -!- unspent_ [~unspent_@user/unspent/x-2117480] has joined #bitcoin-core-dev
08:37 -!- unspent_ [~unspent_@user/unspent/x-2117480] has quit [Remote host closed the connection]
08:38 -!- Guest95 [~Guest95@2401:4900:1c7a:d2cc:24d0:9acd:1cef:a55f] has joined #bitcoin-core-dev
08:43 < murch[m]> ACK dergoegge for qa-assets
08:49 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
08:53 < josie> ls
08:53 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Ping timeout: 256 seconds]
08:54 < sipa> autogen.sh  build_msvc  configure.ac  CONTRIBUTING.md  depends  INSTALL.md                 Makefile.am  SECURITY.md  src
08:54 < sipa> build-aux   ci          contrib       COPYING          doc      libbitcoinconsensus.pc.in  README.md    share        test
08:54 < sipa> $
08:55 -!- brunoerg [~brunoerg@gwsc.sc.usp.br] has joined #bitcoin-core-dev
08:58 -!- guest-127 [~guest-127@212.129.82.152] has joined #bitcoin-core-dev
08:59 -!- brunoerg [~brunoerg@gwsc.sc.usp.br] has quit [Ping timeout: 245 seconds]
09:04 < josie> sipa: 😄
09:09 -!- guest-127 [~guest-127@212.129.82.152] has quit [Quit: Client closed]
09:20 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
09:25 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
09:48 -!- ___nick___ [~quassel@host81-129-235-34.range81-129.btcentralplus.com] has joined #bitcoin-core-dev
09:49 -!- ___nick___ [~quassel@host81-129-235-34.range81-129.btcentralplus.com] has quit [Client Quit]
09:52 -!- ___nick___ [~quassel@host81-129-235-34.range81-129.btcentralplus.com] has joined #bitcoin-core-dev
09:53 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
09:55 -!- not_reserved [~not_reser@45.88.222.253] has joined #bitcoin-core-dev
10:04 -!- szkl [uid110435@id-110435.uxbridge.irccloud.com] has joined #bitcoin-core-dev
10:11 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
10:14 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 240 seconds]
10:20 -!- Guest95 [~Guest95@2401:4900:1c7a:d2cc:24d0:9acd:1cef:a55f] has quit [Quit: Client closed]
10:22 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
10:37 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
10:43 -!- zato [~zato@user/zato] has quit [Quit: Om mani padme hum]
10:46 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Ping timeout: 252 seconds]
10:48 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
10:57 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
11:01 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
11:26 -!- cguida [~cguida@2806:2f0:55e1:f7b9:4dad:8950:6d36:8e13] has joined #bitcoin-core-dev
11:52 < bitcoin-git> [bitcoin] achow101 pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/fcdb39d3ee17...1d9da8da309d
11:52 < bitcoin-git> bitcoin/master 8df4aaa fanquake: doc: add minimum required Linux Kernel to release-notes
11:52 < bitcoin-git> bitcoin/master 7d4e47d fanquake: doc: add historical release notes for 26.0
11:52 < bitcoin-git> bitcoin/master ca59375 fanquake: doc: Missing additions to 26.0 release notes
11:52 < bitcoin-git> [bitcoin] achow101 merged pull request #29023: doc: add historical release notes for 26.0 (master...add_26_0_rel_notes) https://github.com/bitcoin/bitcoin/pull/29023
11:54 -!- cacrowley [~cacrowley@2607:fb90:7591:5194:cc98:7083:8439:acce] has quit [Quit: Client closed]
11:55 < bitcoin-git> [bitcoincore.org] achow101 pushed 2 commits to master: https://github.com/bitcoin-core/bitcoincore.org/compare/52beb0f7d874...9efc6a0ac6ce
11:55 < bitcoin-git> bitcoincore.org/master 71c08ba fanquake: 26.0: add missing release note fragments.
11:55 < bitcoin-git> bitcoincore.org/master 9efc6a0 Andrew Chow: Merge bitcoin-core/bitcoincore.org#999: 26.0: add missing release note fra...
11:55 < bitcoin-git> [bitcoincore.org] achow101 merged pull request #999: 26.0: add missing release note fragments (master...add_missing_26_rel_notes) https://github.com/bitcoin-core/bitcoincore.org/pull/999
12:10 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:13 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
12:21 -!- not_reserved [~not_reser@45.88.222.253] has quit [Quit: Client closed]
12:27 -!- micha_ [uid14316@user/micha/x-4648593] has joined #bitcoin-core-dev
12:37 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Remote host closed the connection]
12:38 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
12:39 < instagibbs> maflcko circling back to this after a while, if I want fuzz coverage report against a single target is there a good way? Do I need to generate a corpus, put it in qa-assets directory, then run "make cov_fuzz"
12:43 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Ping timeout: 246 seconds]
12:50 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
12:58 -!- Guest92 [~Guest92@152.115.211.118] has joined #bitcoin-core-dev
12:58 -!- Guest92 [~Guest92@152.115.211.118] has quit [Client Quit]
13:04 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
13:04 -!- ___nick___ [~quassel@host81-129-235-34.range81-129.btcentralplus.com] has quit [Ping timeout: 256 seconds]
13:09 < dergoegge> DIR_FUZZ_SEED_CORPUS="./qa-assets/fuzz_seed_corpus <target name>" make cov_fuzz
13:30 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Remote host closed the connection]
13:31 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has joined #bitcoin-core-dev
13:36 -!- brunoerg [~brunoerg@2001:12d0:2080:2800:172:26:fffd:f00a] has quit [Ping timeout: 268 seconds]
13:41 -!- sipsorcery [~sipsorcer@213.233.155.172] has joined #bitcoin-core-dev
14:09 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
14:12 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
14:38 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.1.1]
15:10 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
15:14 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
15:17 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 260 seconds]
15:23 -!- pablomartin [~pablomart@193.160.246.225] has quit [Ping timeout: 245 seconds]
15:25 -!- micha_ [uid14316@user/micha/x-4648593] has quit [Quit: Connection closed for inactivity]
15:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
15:33 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
15:40 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
16:22 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
16:50 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
16:50 -!- cguida_ [~cguida@fixed-187-189-154-198.totalplay.net] has joined #bitcoin-core-dev
16:52 -!- cguida [~cguida@2806:2f0:55e1:f7b9:4dad:8950:6d36:8e13] has quit [Ping timeout: 245 seconds]
16:57 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Remote host closed the connection]
17:03 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
17:31 -!- realies [~realies@user/realies] has quit [Remote host closed the connection]
17:31 -!- realies [~realies@user/realies] has joined #bitcoin-core-dev
17:42 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
17:45 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
17:48 -!- realies [~realies@user/realies] has quit [Remote host closed the connection]
17:48 -!- realies [~realies@user/realies] has joined #bitcoin-core-dev
17:48 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
17:49 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 255 seconds]
18:17 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
18:22 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
18:52 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
18:56 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
19:26 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
19:31 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 260 seconds]
19:42 -!- Guest84 [~Guest84@117.20.112.73] has joined #bitcoin-core-dev
19:44 -!- Guest84 [~Guest84@117.20.112.73] has quit [Client Quit]
19:52 -!- midnight [~midnight@user/midnight] has quit [Ping timeout: 260 seconds]
19:52 -!- midnight [~midnight@user/midnight] has joined #bitcoin-core-dev
19:59 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
20:04 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
20:04 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Remote host closed the connection]
20:11 -!- oneeyedalien [~oneeyedal@user/oneeyedalien] has joined #bitcoin-core-dev
20:21 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-dev
20:23 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
20:24 -!- realies [~realies@user/realies] has quit [Remote host closed the connection]
20:25 -!- realies [~realies@user/realies] has joined #bitcoin-core-dev
20:28 -!- Guest84 [~Guest84@117.20.112.73] has joined #bitcoin-core-dev
20:28 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 264 seconds]
20:32 -!- cguida_ [~cguida@fixed-187-189-154-198.totalplay.net] has quit [Ping timeout: 255 seconds]
20:42 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Ping timeout: 256 seconds]
20:46 -!- oneeyedalien [~oneeyedal@user/oneeyedalien] has quit [Quit: Leaving]
20:58 -!- Guest84 [~Guest84@117.20.112.73] has quit [Quit: Client closed]
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:06 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:16 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 268 seconds]
21:30 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
21:40 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 240 seconds]
22:49 -!- flooded [flooded@gateway/vpn/protonvpn/flood/x-43489060] has joined #bitcoin-core-dev
22:51 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
22:52 -!- test_ [flooded@gateway/vpn/protonvpn/flood/x-43489060] has quit [Ping timeout: 252 seconds]
22:56 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 255 seconds]
22:57 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:02 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 245 seconds]
23:03 -!- AaronvanW [~AaronvanW@user/AaronvanW] has joined #bitcoin-core-dev
23:13 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:18 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 252 seconds]
23:41 -!- brunoerg [~brunoerg@187.183.43.117] has joined #bitcoin-core-dev
23:46 -!- zato [~zato@user/zato] has joined #bitcoin-core-dev
23:46 -!- brunoerg [~brunoerg@187.183.43.117] has quit [Ping timeout: 276 seconds]
--- Log closed Fri Dec 08 00:00:53 2023