ChanServ changed the topic of #bitcoin-core-dev to: Bitcoin Core development discussion and commit log | Feel free to watch, but please take commentary and usage questions to #bitcoin | Channel logs: http://www.erisian.com.au/bitcoin-core-dev/, http://gnusha.org/bitcoin-core-dev/ | Weekly Meeting Thursday @ 14:00 UTC | Meeting topics http://gnusha.org/bitcoin-core-dev/proposedmeetingtopics.txt
abubakarsadiq has quit [Quit: Connection closed for inactivity]
__DuBPiRaTe__ has quit [Quit: Leaving]
PaperSword has joined #bitcoin-core-dev
pablomartin has joined #bitcoin-core-dev
LainExperiments has joined #bitcoin-core-dev
LainExperiments has quit [Quit: Client closed]
psue has joined #bitcoin-core-dev
zeropoint has quit [Quit: leaving]
LainExperiments has joined #bitcoin-core-dev
psue has quit [Quit: Client closed]
flag has quit [Ping timeout: 265 seconds]
flag has joined #bitcoin-core-dev
Guest88 has joined #bitcoin-core-dev
Guest88 has quit [Client Quit]
kevkevin has quit [Remote host closed the connection]
dongcarl has quit [Quit: Ping timeout (120 seconds)]
dongcarl has joined #bitcoin-core-dev
LainExperiments has quit [Ping timeout: 256 seconds]
vysn has quit [Remote host closed the connection]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 276 seconds]
pablomartin has quit [Ping timeout: 248 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 260 seconds]
SpellChecker has quit [*.net *.split]
ghost43 has quit [*.net *.split]
vasild has quit [*.net *.split]
qxs has quit [*.net *.split]
kevkevin has joined #bitcoin-core-dev
qxs has joined #bitcoin-core-dev
vasild has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 246 seconds]
hirish has quit [Ping timeout: 255 seconds]
takinbo has quit [Ping timeout: 244 seconds]
takinbo has joined #bitcoin-core-dev
hirish has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
cmirror has quit [Remote host closed the connection]
cmirror has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 260 seconds]
eval-exec has quit [Ping timeout: 276 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
qxs has quit [Remote host closed the connection]
qxs has joined #bitcoin-core-dev
emcy__ has quit [Remote host closed the connection]
emcy__ has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 260 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 276 seconds]
mudsip has joined #bitcoin-core-dev
mudsip has quit [Client Quit]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 272 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 248 seconds]
cm_ has joined #bitcoin-core-dev
cm has quit [Ping timeout: 260 seconds]
cm_ is now known as cm
kevkevin has joined #bitcoin-core-dev
emcy__ has quit [Quit: Leaving]
mcey has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 272 seconds]
stratospher[m] has quit [Ping timeout: 248 seconds]
laanwj has quit [Ping timeout: 248 seconds]
stratospher[m] has joined #bitcoin-core-dev
laanwj has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 276 seconds]
eval-exec has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 248 seconds]
Guyver2 has left #bitcoin-core-dev [Closing Window]
kevkevin has joined #bitcoin-core-dev
tripleslash has quit [Remote host closed the connection]
kevkevin has quit [Ping timeout: 255 seconds]
tripleslash has joined #bitcoin-core-dev
<vasild> achow101: the meeting is at 14:00 UTC?
mcey_ has joined #bitcoin-core-dev
mcey has quit [Ping timeout: 260 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 245 seconds]
<bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/564238aabf1c...c9e67e214f03
<bitcoin-git> bitcoin/master fa461d7 MarcoFalke: fuzz: Limit wallet_notifications iterations
<bitcoin-git> bitcoin/master c9e67e2 merge-script: Merge bitcoin/bitcoin#31238: fuzz: Limit wallet_notifications iterations
<bitcoin-git> [bitcoin] fanquake merged pull request #31238: fuzz: Limit wallet_notifications iterations (master...2411-wnl) https://github.com/bitcoin/bitcoin/pull/31238
PaperSword has quit [Ping timeout: 248 seconds]
PaperSword has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 244 seconds]
<sipa> vasild: indeed
<sipa> 2h12m from now
<vasild> ok
aleggg has joined #bitcoin-core-dev
pablomartin has joined #bitcoin-core-dev
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 252 seconds]
kevkevin has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 260 seconds]
eval-exec has quit [Ping timeout: 245 seconds]
kevkevin has joined #bitcoin-core-dev
eval-exec has joined #bitcoin-core-dev
qxs has quit [Ping timeout: 260 seconds]
qxs has joined #bitcoin-core-dev
<bitcoin-git> [bitcoin] vasild opened pull request #31239: test: clarify log messages when handling SOCKS5 proxy connections (master...socks5proxy_log) https://github.com/bitcoin/bitcoin/pull/31239
eval-exec has quit [Ping timeout: 252 seconds]
eval-exec has joined #bitcoin-core-dev
wannabe has joined #bitcoin-core-dev
eval-exec has quit [Remote host closed the connection]
eval-exec has joined #bitcoin-core-dev
josie_ has joined #bitcoin-core-dev
josie_ is now known as josie
Emc99 has joined #bitcoin-core-dev
kevkevin has quit [Ping timeout: 276 seconds]
Emc99 has quit [Client Quit]
Emc99 has joined #bitcoin-core-dev
<bitcoin-git> [bitcoin] edilmedeiros opened pull request #31240: RFC: doc: Fix dead links to mailing list archives (master...fix-mailing-list-links) https://github.com/bitcoin/bitcoin/pull/31240
<kanzure> #proposedmeetingtopic bitcoin-dev mailing list archive links
abubakarsadiq has joined #bitcoin-core-dev
<achow101> #startmeeting
<pinheadmz> hi
<TheCharlatan> hi
<josie> hi
<achow101> #bitcoin-core-dev Meeting: abubakarsadiq achow101 _aj_ ajonas b10c brunoerg cfields darosior dergoegge fanquake fjahr furszy gleb glozow hebasto instagibbs jarolrod jonatack josibake kanzure laanwj LarryRuane lightlike luke-jr maflcko maxedw Murch pinheadmz provoostenator ryanofsky sdaftuar S3RK stickies-v sipa sr_gi tdb3 theStack TheCharlatan vasild willcl-ark
<jarolrod> Hi
<kanzure> hi
<b10c> hi
<abubakarsadiq> hi
<ryanofsky> hi
<furszy> hi
<achow101> There is one pre-proposed meeting topic this week. Any last minute ones to add?
<dergoegge> hi
<lightlike> Hi
<sipa> hi
<maxedw> hi
<stickies-v> hi
<willcl-ark> hi
<achow101> #topic Fuzzing WG Update (dergoegge)
<theStack> hi
<cfields> hi
<dergoegge> no update
<dergoegge> I thought we're doing these monthly
<achow101> #topic Kernel WG Update (TheCharlatan)
<TheCharlatan> The focus is currently on "de-risking" the necessary "glue" code between the external header and the internal code. This means de-duplicating redundant logic between the various interfaces.
<josie> dergoegge: i think some people will have updates each week, others monthly ?
<TheCharlatan> In the working group we recently discussed approaches for handling the logging in a better way. An alternative that was not explored yet could be directly exposing a kernel logging macro.
<TheCharlatan> The experimental rust-bitcoinkernel crate, which implements a Rust wrapper around the API as implemented in #30595, is now available through crates.io.
<gribble> https://github.com/bitcoin/bitcoin/issues/30595 | kernel: Introduce initial C header API by TheCharlatan · Pull Request #30595 · bitcoin/bitcoin · GitHub
wannabe has quit [Quit: Client closed]
<TheCharlatan> This makes it a bit easier for other developers that might also want to experiment with it.
<TheCharlatan> I also started work on an experimental kernel-based node to validate the API.
<TheCharlatan> This has already surfaced some stuff that I put into the API PR.
<TheCharlatan> that's it from me
<achow101> dergoegge: last week, seemed like most people wanted updates every week. so doing it based on who's here to minimize downtime.
<achow101> #topic Benchmarking WG Update (josibake, l0rinc)
<josie> since last week, willcl-ark and i have been working on a CI workflow for long running benchmarks. so far, making good progress!
<josie> we have a workflow where someone can take their branch and open it as a PR against https://github.com/bitcoin-dev-tools/benchcoin and this will automatically kick off a benchmark and publish the final results as artifacts on the PR
<josie> right now, the only benchmark we have working is an assumeutxo benchmark on signet (i.e., loading a snapshot and doing IBD from snapshot to chaintip with background validation paused)
<josie> next steps will be to make this work on mainnet and figure out how to intelligently distribute workloads to our dedicated runners pool
<josie> Novo__ has been working on rebasing fjahr 's batch validation PR, as thats one of the first ones we'd like to start benchmarking using the assumeutxo bench method
<josie> thats all for benchmarking!
<achow101> #topic Silent Payments WG Update (josibake, RubenSomsen)
<cfields> which PR#?
<josie> ive been incorporating all of the review comments / feedback from coredev on the bitcoin-core/secp256k1#1519, hoping to finish that this week
<gribble> https://github.com/bitcoin/bitcoin/issues/1519 | GUI: change language selection format to "language - country (locale name)" by Diapolo · Pull Request #1519 · bitcoin/bitcoin · GitHub
<josie> next will be rebasing the bitcoin core PRs on top of that. for a list of the PRs / status, im keeping the tracking issue up to date (bitcoin/bitcoin#28536)
<gribble> https://github.com/bitcoin/bitcoin/issues/28536 | BIP352 tracking issue · Issue #28536 · bitcoin/bitcoin · GitHub
<josie> thats all for silent payments
<josie> cfields: was that a question for the benchmarking update?
<cfields> josie: yes
<willcl-ark> cfields: #29491
<gribble> https://github.com/bitcoin/bitcoin/issues/29491 | [DO NOT MERGE] Schnorr batch verification for blocks by fjahr · Pull Request #29491 · bitcoin/bitcoin · GitHub
<cfields> ah, nice. thanks.
<achow101> #topic Cluster Mempool WG Update (sdaftuar, sipa)
<sipa> Update on txgraph (part of cluster mempool). My plan is to have a first PR for the "txgraph" module open next week (this is the layer that reasons about dependencies/clusters/linearizations for the entire mempool, as opposed to the cluster_linearize.h file that is already merged, which is for reasoning about a single individual cluster). Txgraph will probably be a few PRs (mining/eviction logic may
<sipa> be added later, some memory usage optimizations, reorg...
<sipa> logic), but i hope to have the basics out next week.
<sipa> After that, the main PR for cluster mempool can be rebased on the txgraph logic + the mempool changeset PR.
<sipa> That's it for me, suhas doesn't seem to be around.
eval-exec has quit [Ping timeout: 252 seconds]
adil1 has joined #bitcoin-core-dev
<achow101> #topic MuSig2 WG Update (achow101)
<achow101> The libsecp subtree has been updated to 0.6.0 which includes the musig module. #29675 is no longer draft. the WG will be meeting after the IRC meeting to discuss breaking it up so it isn't 30 commits
<gribble> https://github.com/bitcoin/bitcoin/issues/29675 | wallet: Be able to receive and spend inputs involving MuSig2 aggregate keys by achow101 · Pull Request #29675 · bitcoin/bitcoin · GitHub
<achow101> #topic Legacy Wallet Removal WG Update (achow101)
<achow101> Still waiting on review on #30328, otherwise, no update
<gribble> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
<achow101> there's signal groups for both of my WGs, lmk if you would like to join
<achow101> #topic Multiprocess WG Update (ryanofsky)
<kanzure> brb 5min
<cfields> heh perhaps "WG call directly after the IRC meeting" isn't the best approach for _every_ WG.
kevkevin has joined #bitcoin-core-dev
<achow101> saw ryanofsky, but i guess no update
<achow101> #topic package relay WG Update (glozow)
<josie> cfields: certainly not for people in multiple working groups
<glozow> working on #31190 followup
<gribble> https://github.com/bitcoin/bitcoin/issues/31190 | TxDownloadManager followups by glozow · Pull Request #31190 · bitcoin/bitcoin · GitHub
<glozow> That’s it
<achow101> #topic Ad-hoc high priority for review
<achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
<glozow> (I thought we signed up for the dates we were gonna give updates? Or did I read that wrong?)
<ryanofsky> Sorry was afk. Multiprocess update was: Not much new, priority is to get multiprocess code enabled in next release so mining IPC interface is easily accessible. Tracking issue is #28722 with PRs to review, and there is now a Signal group linked there. That's it.
<gribble> https://github.com/bitcoin/bitcoin/issues/28722 | Multiprocess tracking issue · Issue #28722 · bitcoin/bitcoin · GitHub
<achow101> glozow: last week, seemed like most people wanted weekly updates from all WGs; will be doing it based on who's here (people saying hi)
adil1 has quit [Quit: adil1]
<achow101> Perhaps we should kill this high priority for review topic. it doesn't seem like anyone is using, and if you have something high priority for review, maybe make a working group?
<glozow> Ok my bad
<josie> achow101: iirc, everyone seemed to favor that last meeting? or if you have a high prio, just drop it here? i could be misremembering tho
<stickies-v> achow101: sounds good. people can still suggest ad-hoc topics too if anything urgent non-wg comes up, of course
<sipa> we're all still figuring things ouy
<sipa> out
<achow101> josie: I don't recall there being discussion about this topic
<achow101> right now there is only one pr in the board, and things that have been added to it previously don't seem to have actually gotten any more review than if they hadn't been on it
<achow101> will remove it for now
<achow101> #topic bitcoin-dev mailing list archive links (kanzure)
<kanzure> lists.linuxfoundation.org is no more and is no longer hosting the mailing list static archives at this time (not just for bitcoin-dev but ~everything including some LKML stuff?)
<kanzure> see recently announced on https://x.com/kanzure/status/1853779672514826334
<kanzure> to be fair, they did give us some notice, hence the actual migration was done earlier this year
<kanzure> there's a lot of backlinks out there, it's really sad to have this many links broken :(
<kanzure> someone is working on asking them to re-host the static archives to preserve backlinks and fight against bit rot on the web, dunno if they will
<achow101> kanzure: I thought they promised to keep the archive?
<kanzure> well if they did then i did not receive that, i don't have LF contactperson details
<kanzure> i have made https://gnusha.org/url to help with the link rot, try it out:
<kanzure> just made lightning-dev work a few minutes ago, pls test and let me know if something is broken
<kanzure> attachments do not presently work for lightning-dev, someone can make a public-inbox archive from lightning-dev.mbox if they have a complete archive.
<kanzure> the mapping (used by my /url service) from {id}.html -> {Message-ID} was made with these scripts, pls review if you are bored: https://gist.github.com/kanzure/4e7bcc58344ceaa1a668e65a434adb2b
<kanzure> btctranscripts.com pull request here: https://github.com/bitcointranscripts/bitcointranscripts/pull/566
<kanzure> bitcoin.git can also be updated, please see https://github.com/bitcoin/bitcoin/pull/29782#issuecomment-2460974096 which is asking about what to do about the comments in the codebase that need to be updated
<kanzure> oh just saw a new pull request for that, maybe 31240 https://github.com/bitcoin/bitcoin/pull/31240
<kanzure> uhh there was one more thing
<achow101> these links are sprinkled all over the place. this is gonna be a pain
<kanzure> oh right, it occurs to me that bitcoin-core-dev is not supported on gnusha.org/url at the moment, does anyone have strong opinions about this. announcement emails always went out to bitcoin-dev AFAIK so they are captured there at least.
<bitcoin-git> [bitcoin] kevkevinpal closed pull request #30570: [tests] New fuzz target wallet_rpc (master...fuzzwalletrpc) https://github.com/bitcoin/bitcoin/pull/30570
<achow101> considering the demise of that list, i'm not sure that migrating it will even be useful as everyone who was previously on it won't be notified of the new list location
<achow101> and the announcements occur in a ton of other places too, including bitcoin-dev
Emc99 has quit [Quit: Client closed]
<kanzure> maybe post a question publicly and ask if anyone was using just the bitcoin-core-dev announcement list specifically, or thinks it should continue to exist, i would hate to break something important
Emc99 has joined #bitcoin-core-dev
<achow101> perhaps ask on bitcoindev?
<achow101> Any other topics to discuss?
<achow101> #endmeeting
<josie> let the flood of WG calls begin!
Emc99 has quit [Quit: Client closed]
<theStack> :D
<stickies-v> josie: in https://github.com/bitcoin-dev-tools/benchcoin, it seems `results.json` only contains a run for PR head. Since `master` is ~going to be different for each PR, doing a run on `master` too might be helpful to isolate effects from other recent commits? Then again, doubles the compute for what will presumably be heavy workloads, so might not be worth the trade off. Just wondering what your thoughts are, i guess
<josie> stickies-v: that should be fixed soon (tm). regarding master changing, the idea is we will only sync benchcoin up with bitcoin-core master manually, once weve got agreement in the WG to choose a new base to benchmark against. long term, wed like to make it fully parameterized where you can pick a specific commit to bench your PR against (master at a certain point in time, another PR, etc)
<josie> stickies-v: we had discussed not running master vs PR branch on each run to save compute, but ultimately felt it was better to just accept the compute so that we have more guarantees its an apples to apples comparison (like changing bitcoin.conf options)
brunoerg has quit [Remote host closed the connection]
hodlinator has joined #bitcoin-core-dev
eval-exec has joined #bitcoin-core-dev
<stickies-v> cool, thanks. parameterizing sounds like it would be helpful
preimage has joined #bitcoin-core-dev
sliv3r__ has joined #bitcoin-core-dev
zeropoint has joined #bitcoin-core-dev
bugs_ has joined #bitcoin-core-dev
jb55 has quit [Ping timeout: 260 seconds]
achow101 has quit [Ping timeout: 276 seconds]
achow101 has joined #bitcoin-core-dev
twistedline has quit []
jb55 has joined #bitcoin-core-dev
twistedline has joined #bitcoin-core-dev
<bitcoin-git> [bitcoin] furszy opened pull request #31241: wallet: remove BDB dependency from wallet migration benchmark (master...2024_bench_migration_remove_bdb_dependency) https://github.com/bitcoin/bitcoin/pull/31241
sliv3r__ has quit [Ping timeout: 256 seconds]
<bitcoin-git> [bitcoin] achow101 opened pull request #31242: wallet, desc spkm: Return SigningProvider only if we have the privkey (master...wallet-signingprov-no-h) https://github.com/bitcoin/bitcoin/pull/31242
<darosior> Is there known users of the REST interface? Do we know why they can't use the RPC interface instead? It's not like the REST interface gives any more guarantees?
<bitcoin-git> [bitcoin] achow101 opened pull request #31243: descriptor: Move filling of keys from `DescriptorImpl::MakeScripts` to `PubkeyProvider::GetPubKey` (master...descriptor-direct-fill) https://github.com/bitcoin/bitcoin/pull/31243
jb55 has quit [Ping timeout: 252 seconds]
<dergoegge> perhaps worth asking andrew
<darosior> Thanks. It does mention a couple usecases:
<darosior> > The REST interface is useful for quickly iterating over the blockchain, because it can request blocks and transactions in binary form without having to serialize/deserialize into JSON.
<darosior> And:
<darosior> > It also has API for quickly retrieving large amounts of block headers and BIP157 compact block filter headers.
<dergoegge> I remember discussion in the past about removing the rest server on #17631 (also see #23309)
<gribble> https://github.com/bitcoin/bitcoin/issues/23309 | [WIP] Add a basic python REST API Server Wrapper by JeremyRubin · Pull Request #23309 · bitcoin/bitcoin · GitHub
bob_x1 has joined #bitcoin-core-dev
<gribble> https://github.com/bitcoin/bitcoin/issues/17631 | Expose block filters over REST by TheBlueMatt · Pull Request #17631 · bitcoin/bitcoin · GitHub
sliv3r__ has joined #bitcoin-core-dev
andrewtoth has joined #bitcoin-core-dev
jb55 has joined #bitcoin-core-dev
<bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/c9e67e214f03...3a5f6027e165
<bitcoin-git> bitcoin/master e2ba823 Hennadii Stepanov: depends: Specify CMake generator explicitly
<bitcoin-git> bitcoin/master 3a5f602 merge-script: Merge bitcoin/bitcoin#31171: depends: Specify CMake generator explicitly
<bitcoin-git> [bitcoin] fanquake merged pull request #31171: depends: Specify CMake generator explicitly (master...241028-generator) https://github.com/bitcoin/bitcoin/pull/31171
<andrewtoth> darosior: romanz (author of electrs) has had recent improvements to the REST server merged. I don't see electrs using it but perhaps that is a direction they are taking.
<andrewtoth> Not having to bother with auth for read only use cases is a nice bonus
sliv3r__ has quit [Ping timeout: 256 seconds]
<bitcoin-git> [bitcoin] fanquake pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/3a5f6027e165...018e5fcc462c
<bitcoin-git> bitcoin/master 917ab81 glozow: [doc] comment fixups from n30110
<bitcoin-git> bitcoin/master 8351562 glozow: [fuzz] allow negative time jumps in txdownloadman_impl
<bitcoin-git> bitcoin/master 5dc94d1 glozow: fuzz fix: assert MAX_PEER_TX_ANNOUNCEMENTS is not exceeded
<bitcoin-git> [bitcoin] fanquake merged pull request #31190: TxDownloadManager followups (master...2024-10-30110-followups) https://github.com/bitcoin/bitcoin/pull/31190
sliv3r__ has joined #bitcoin-core-dev
<darosior> Yeah i see the upsides. I was pondering if Bitcoin Core really had to maintain an HTTP server (through a dependency or otherwise).
<bitcoin-git> [bitcoin] achow101 opened pull request #31244: descriptors: MuSig2 (master...musig2-desc) https://github.com/bitcoin/bitcoin/pull/31244
<andrewtoth> See #31065 as well. There is some agitation to make it do more.
<gribble> https://github.com/bitcoin/bitcoin/issues/31065 | rest: Support transaction broadcast in REST interface by danielabrozzoni · Pull Request #31065 · bitcoin/bitcoin · GitHub
sliv3r__ has quit [Quit: Client closed]
<bitcoin-git> [bitcoin] achow101 opened pull request #31245: wallet: Sign transactions containing MuSig2 inputs (master...musig2-signing) https://github.com/bitcoin/bitcoin/pull/31245
sliv3r__ has joined #bitcoin-core-dev
<bitcoin-git> [bitcoin] achow101 closed pull request #31245: wallet: Sign transactions containing MuSig2 inputs (master...musig2-signing) https://github.com/bitcoin/bitcoin/pull/31245
<bitcoin-git> [bitcoin] achow101 opened pull request #31247: psbt: MuSig2 Fields (master...musig2-psbt) https://github.com/bitcoin/bitcoin/pull/31247
<bitcoin-git> [bitcoin] achow101 opened pull request #31248: test: Rework wallet_migration.py to use previous releases (master...migratewallet-prev-rels) https://github.com/bitcoin/bitcoin/pull/31248
sliv3r__ has quit [Quit: Client closed]
<bitcoin-git> [bitcoin] achow101 opened pull request #31249: test: Add combinerawtransaction test to rpc_createmultisig (master...combinerawtx-test) https://github.com/bitcoin/bitcoin/pull/31249
<bitcoin-git> [bitcoin] achow101 opened pull request #31250: wallet: Disable creating and loading legacy wallets (master...disable-legacy-wallets) https://github.com/bitcoin/bitcoin/pull/31250
Talkless has joined #bitcoin-core-dev
sliv3r__ has joined #bitcoin-core-dev
SpellChecker has joined #bitcoin-core-dev
sliv3r__ has quit [Quit: Client closed]
<bitcoin-git> [bitcoin] furszy opened pull request #31251: test: report a more detailed failure during utf8 response decoding (master...2024_test_report_invalid_response) https://github.com/bitcoin/bitcoin/pull/31251