--- Log opened Thu Nov 07 00:00:08 2024
--- Day changed Thu Nov 07 2024
00:00 -!- emcy__ [~emcy@185.69.145.98] has quit [Quit: Leaving]
00:01 -!- mcey [~emcy@185.69.145.98] has joined #bitcoin-core-dev
00:04 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 272 seconds]
00:20 -!- stratospher[m] [~stratosph@2620:6e:a000:ce11::1e] has quit [Ping timeout: 248 seconds]
00:20 -!- laanwj [~laanwj@user/laanwj] has quit [Ping timeout: 248 seconds]
00:20 -!- stratospher[m] [~stratosph@2620:6e:a000:ce11::1e] has joined #bitcoin-core-dev
00:21 -!- laanwj [~laanwj@user/laanwj] has joined #bitcoin-core-dev
00:22 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has joined #bitcoin-core-dev
00:29 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
00:36 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 276 seconds]
00:39 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has joined #bitcoin-core-dev
01:06 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
01:12 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 248 seconds]
01:33 -!- Guyver2 [~Guyver@77-174-98-73.fixed.kpn.net] has left #bitcoin-core-dev [Closing Window]
01:43 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
01:46 -!- tripleslash [~triplesla@user/tripleslash] has quit [Remote host closed the connection]
01:48 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 255 seconds]
01:51 -!- tripleslash [~triplesla@user/tripleslash] has joined #bitcoin-core-dev
01:55 < vasild> achow101: the meeting is at 14:00 UTC?
02:10 -!- mcey_ [~emcy@148.252.144.188] has joined #bitcoin-core-dev
02:13 -!- mcey [~emcy@185.69.145.98] has quit [Ping timeout: 260 seconds]
02:20 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
02:27 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 245 seconds]
02:27 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/564238aabf1c...c9e67e214f03
02:27 < bitcoin-git> bitcoin/master fa461d7 MarcoFalke: fuzz: Limit wallet_notifications iterations
02:27 < bitcoin-git> bitcoin/master c9e67e2 merge-script: Merge bitcoin/bitcoin#31238: fuzz: Limit wallet_notifications iterations
02:27 < bitcoin-git> [bitcoin] fanquake merged pull request #31238: fuzz: Limit wallet_notifications iterations (master...2411-wnl) https://github.com/bitcoin/bitcoin/pull/31238
02:45 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Ping timeout: 248 seconds]
02:59 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev
03:00 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
03:05 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 252 seconds]
03:36 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
03:41 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 244 seconds]
03:48 < sipa> vasild: indeed
03:48 < sipa> 2h12m from now
03:49 < vasild> ok
03:53 -!- aleggg [~aleggg@177.204.246.39.dynamic.adsl.gvt.net.br] has joined #bitcoin-core-dev
04:07 -!- pablomartin [~pablomart@92.118.61.187] has joined #bitcoin-core-dev
04:11 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
04:17 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 252 seconds]
04:45 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
04:50 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 260 seconds]
05:08 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has quit [Ping timeout: 245 seconds]
05:15 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
05:20 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has joined #bitcoin-core-dev
05:20 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 260 seconds]
05:22 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
05:24 < 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
05:24 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has quit [Ping timeout: 252 seconds]
05:25 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has joined #bitcoin-core-dev
05:25 -!- wannabe [~wannabe@58.143.219.112] has joined #bitcoin-core-dev
05:27 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has quit [Remote host closed the connection]
05:27 -!- eval-exec [~Thunderbi@58.137.176.32] has joined #bitcoin-core-dev
05:38 -!- josie_ [~josibake@suhail.uberspace.de] has joined #bitcoin-core-dev
05:43 -!- josie_ is now known as josie
05:56 -!- Emc99 [~Emc99@212.129.84.175] has joined #bitcoin-core-dev
05:56 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 276 seconds]
05:59 -!- Emc99 [~Emc99@212.129.84.175] has quit [Client Quit]
05:59 -!- Emc99 [~Emc99@212.129.84.175] has joined #bitcoin-core-dev
05:59 < 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
05:59 < kanzure> #proposedmeetingtopic bitcoin-dev mailing list archive links
05:59 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has joined #bitcoin-core-dev
06:00 < achow101> #startmeeting
06:00 < pinheadmz> hi
06:00 < TheCharlatan> hi
06:00 < josie> hi
06:00 < 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
06:00 < jarolrod> Hi
06:00 < kanzure> hi
06:00 < b10c> hi
06:00 < abubakarsadiq> hi
06:00 < ryanofsky> hi
06:00 < furszy> hi
06:00 < achow101> There is one pre-proposed meeting topic this week. Any last minute ones to add?
06:00 < dergoegge> hi
06:00 < lightlike> Hi
06:00 < sipa> hi
06:00 < maxedw> hi
06:00 < stickies-v> hi
06:01 < willcl-ark> hi
06:01 < achow101> #topic Fuzzing WG Update (dergoegge)
06:02 < theStack> hi
06:02 < cfields> hi
06:02 < dergoegge> no update
06:02 < dergoegge> I thought we're doing these monthly
06:02 < achow101> #topic Kernel WG Update (TheCharlatan)
06:03 < 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.
06:03 < josie> dergoegge: i think some people will have updates each week, others monthly ? 
06:03 < 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.
06:03 < TheCharlatan> The experimental rust-bitcoinkernel crate, which implements a Rust wrapper around the API as implemented in #30595, is now available through crates.io.
06:03 <@gribble> https://github.com/bitcoin/bitcoin/issues/30595 | kernel: Introduce initial C header API by TheCharlatan · Pull Request #30595 · bitcoin/bitcoin · GitHub
06:04 -!- wannabe [~wannabe@58.143.219.112] has quit [Quit: Client closed]
06:04 < TheCharlatan> This makes it a bit easier for other developers that might also want to experiment with it.
06:04 < TheCharlatan> I also started work on an experimental kernel-based node to validate the API.
06:04 < TheCharlatan> This has already surfaced some stuff that I put into the API PR.
06:05 < TheCharlatan> that's it from me
06:05 < achow101> dergoegge: last week, seemed like most people wanted updates every week. so doing it based on who's here to minimize downtime.
06:05 < achow101> #topic Benchmarking WG Update (josibake, l0rinc)
06:05 < josie> since last week, willcl-ark and i have been working on a CI workflow for long running benchmarks. so far, making good progress!
06:05 < 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
06:06 < 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)
06:06 < josie> next steps will be to make this work on mainnet and figure out how to intelligently distribute workloads to our dedicated runners pool
06:06 < 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
06:06 < josie> thats all for benchmarking! 
06:06 < achow101> #topic Silent Payments WG Update (josibake, RubenSomsen)
06:06 < cfields> which PR#?
06:06 < josie> ive been incorporating all of the review comments / feedback from coredev on the bitcoin-core/secp256k1#1519, hoping to finish that this week
06:06 <@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
06:07 < 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)
06:07 <@gribble> https://github.com/bitcoin/bitcoin/issues/28536 | BIP352 tracking issue · Issue #28536 · bitcoin/bitcoin · GitHub
06:07 < josie> thats all for silent payments
06:07 < josie> cfields: was that a question for the benchmarking update?
06:07 < cfields> josie: yes
06:08 < willcl-ark> cfields: #29491
06:08 <@gribble> https://github.com/bitcoin/bitcoin/issues/29491 | [DO NOT MERGE] Schnorr batch verification for blocks by fjahr · Pull Request #29491 · bitcoin/bitcoin · GitHub
06:08 < cfields> ah, nice. thanks.
06:08 < achow101> #topic Cluster Mempool WG Update (sdaftuar, sipa)
06:08 < 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 
06:08 < sipa> be added later, some memory usage optimizations, reorg...
06:08 < sipa> logic), but i hope to have the basics out next week.
06:09 < sipa> After that, the main PR for cluster mempool can be rebased on the txgraph logic + the mempool changeset PR.
06:09 < sipa> That's it for me, suhas doesn't seem to be around.
06:09 -!- eval-exec [~Thunderbi@58.137.176.32] has quit [Ping timeout: 252 seconds]
06:10 -!- adil1 [~Thunderbi@2402:d000:8134:2758:d164:eaa4:79c2:62ff] has joined #bitcoin-core-dev
06:10 < achow101> #topic MuSig2 WG Update (achow101)
06:10 < 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
06:10 <@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
06:11 < achow101> #topic Legacy Wallet Removal WG Update (achow101)
06:11 < achow101> Still waiting on review on #30328, otherwise, no update
06:11 <@gribble> https://github.com/bitcoin/bitcoin/issues/30328 | wallet: Remove IsMine from migration code by achow101 · Pull Request #30328 · bitcoin/bitcoin · GitHub
06:12 < achow101> there's signal groups for both of my WGs, lmk if you would like to join
06:12 < achow101> #topic Multiprocess WG Update (ryanofsky)
06:13 < kanzure> brb 5min
06:14 < cfields> heh perhaps "WG call directly after the IRC meeting" isn't the best approach for _every_ WG.
06:14 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
06:15 < achow101> saw ryanofsky, but i guess no update
06:15 < achow101> #topic package relay WG Update (glozow)
06:15 < josie> cfields: certainly not for people in multiple working groups 
06:15 < glozow> working on #31190 followup
06:15 <@gribble> https://github.com/bitcoin/bitcoin/issues/31190 | TxDownloadManager followups by glozow · Pull Request #31190 · bitcoin/bitcoin · GitHub
06:15 < glozow> That’s it
06:16 < achow101> #topic Ad-hoc high priority for review
06:16 < achow101> Anything to add or remove from https://github.com/orgs/bitcoin/projects/1/views/4
06:16 < glozow> (I thought we signed up for the dates we were gonna give updates? Or did I read that wrong?)
06:16 < 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.
06:16 <@gribble> https://github.com/bitcoin/bitcoin/issues/28722 | Multiprocess tracking issue · Issue #28722 · bitcoin/bitcoin · GitHub
06:16 < 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)
06:17 -!- adil1 [~Thunderbi@2402:d000:8134:2758:d164:eaa4:79c2:62ff] has quit [Quit: adil1]
06:18 < 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?
06:18 < glozow> Ok my bad
06:18 < 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
06:18 < stickies-v> achow101: sounds good. people can still suggest ad-hoc topics too if anything urgent non-wg comes up, of course
06:19 < sipa> we're all still figuring things ouy
06:19 < sipa> out
06:19 < achow101> josie: I don't recall there being discussion about this topic
06:20 < 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
06:21 < achow101> will remove it for now
06:22 < achow101> #topic bitcoin-dev mailing list archive links (kanzure)
06:22 < 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?)
06:22 < kanzure> see recently announced on https://x.com/kanzure/status/1853779672514826334
06:22 < kanzure> see general mailing list migration background here https://gnusha.org/pi/bitcoindev/CABaSBaxDjj6ySBx4v+rmpfrw4pE9b=JZJPzPQj_ZUiBg1HGFyA@mail.gmail.com/
06:22 < kanzure> to be fair, they did give us some notice, hence the actual migration was done earlier this year
06:22 < kanzure> there's a lot of backlinks out there, it's really sad to have this many links broken :(
06:22 < 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
06:22 < achow101> kanzure: I thought they promised to keep the archive?
06:23 < kanzure> well if they did then i did not receive that, i don't have LF contactperson details
06:23 < kanzure> i have made https://gnusha.org/url to help with the link rot, try it out:
06:23 < kanzure> https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-June/014472.html
06:23 < kanzure> https://gnusha.org/url/https://lists.linuxfoundation.org/pipermail/lightning-dev/2015-November/000313.html
06:23 < kanzure> just made lightning-dev work a few minutes ago, pls test and let me know if something is broken
06:23 < 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.
06:23 < 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
06:23 < kanzure> btctranscripts.com pull request here: https://github.com/bitcointranscripts/bitcointranscripts/pull/566
06:23 < 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
06:23 < kanzure> oh just saw a new pull request for that, maybe 31240 https://github.com/bitcoin/bitcoin/pull/31240
06:24 < kanzure> uhh there was one more thing
06:24 < achow101> these links are sprinkled all over the place. this is gonna be a pain
06:24 < 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.
06:24 < bitcoin-git> [bitcoin] kevkevinpal closed pull request #30570: [tests] New fuzz target wallet_rpc (master...fuzzwalletrpc) https://github.com/bitcoin/bitcoin/pull/30570
06:25 < 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
06:25 < achow101> and the announcements occur in a ton of other places too, including bitcoin-dev
06:25 -!- Emc99 [~Emc99@212.129.84.175] has quit [Quit: Client closed]
06:26 < 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
06:26 -!- Emc99 [~Emc99@212.129.84.175] has joined #bitcoin-core-dev
06:27 < achow101> perhaps ask on bitcoindev?
06:29 < achow101> Any other topics to discuss?
06:31 < achow101> #endmeeting
06:31 < josie> let the flood of WG calls begin! 
06:31 -!- Emc99 [~Emc99@212.129.84.175] has quit [Quit: Client closed]
06:31 < theStack> :D
06:31 < 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
06:33 < 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)
06:36 < 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)
06:51 -!- brunoerg [~brunoerg@2804:14c:3bfb:37:a4ad:484a:4330:8e73] has quit [Remote host closed the connection]
06:56 -!- hodlinator [~hodlinato@user/hodlinator] has joined #bitcoin-core-dev
07:07 -!- eval-exec [~Thunderbi@96.45.190.137.16clouds.com] has joined #bitcoin-core-dev
07:11 < stickies-v> cool, thanks. parameterizing sounds like it would be helpful
07:25 -!- preimage [~halosghos@user/halosghost] has joined #bitcoin-core-dev
07:25 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
07:55 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has joined #bitcoin-core-dev
08:01 -!- bugs_ [~bugs@user/bugs/x-5128603] has joined #bitcoin-core-dev
08:26 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 260 seconds]
08:28 -!- achow101 [~achow101@user/achow101] has quit [Ping timeout: 276 seconds]
08:28 -!- achow101 [~achow101@user/achow101] has joined #bitcoin-core-dev
08:38 -!- twistedline [~bitcoin@185.193.125.44] has quit []
08:38 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
08:39 -!- twistedline [~bitcoin@185.193.125.44] has joined #bitcoin-core-dev
08:42 < 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
08:47 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Ping timeout: 256 seconds]
08:52 < 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
08:52 < 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?
08:56 < 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
08:57 < dergoegge> darosior: there's https://github.com/andrewtoth/rust-bitcoincore-rest/
08:57 -!- jb55 [~jb55@user/jb55] has quit [Ping timeout: 252 seconds]
08:57 < dergoegge> perhaps worth asking andrew
09:01 < darosior> Thanks. It does mention a couple usecases:
09:01 < 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.
09:01 < darosior> And:
09:01 < darosior> > It also has API for quickly retrieving large amounts of block headers and BIP157 compact block filter headers.
09:02 < dergoegge> ldk also uses it (or at least has support): https://github.com/lightningdevkit/rust-lightning/blob/c35adff51d576ec91d86f50a409a2df0c14653c3/lightning-block-sync/src/rest.rs#L1
09:04 < dergoegge> I remember discussion in the past about removing the rest server on #17631 (also see #23309)
09:04 <@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
09:04 -!- bob_x1 [~bob_x@user/bob-x1/x-8934932] has joined #bitcoin-core-dev
09:04 <@gribble> https://github.com/bitcoin/bitcoin/issues/17631 | Expose block filters over REST by TheBlueMatt · Pull Request #17631 · bitcoin/bitcoin · GitHub
09:06 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
09:09 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
09:11 -!- jb55 [~jb55@user/jb55] has joined #bitcoin-core-dev
09:12 < bitcoin-git> [bitcoin] fanquake pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/c9e67e214f03...3a5f6027e165
09:12 < bitcoin-git> bitcoin/master e2ba823 Hennadii Stepanov: depends: Specify CMake generator explicitly
09:12 < bitcoin-git> bitcoin/master 3a5f602 merge-script: Merge bitcoin/bitcoin#31171: depends: Specify CMake generator explicitly
09:12 < bitcoin-git> [bitcoin] fanquake merged pull request #31171: depends: Specify CMake generator explicitly (master...241028-generator) https://github.com/bitcoin/bitcoin/pull/31171
09:15 < 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.
09:16 < andrewtoth> Not having to bother with auth for read only use cases is a nice bonus
09:21 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Ping timeout: 256 seconds]
09:30 < bitcoin-git> [bitcoin] fanquake pushed 4 commits to master: https://github.com/bitcoin/bitcoin/compare/3a5f6027e165...018e5fcc462c
09:30 < bitcoin-git> bitcoin/master 917ab81 glozow: [doc] comment fixups from n30110
09:30 < bitcoin-git> bitcoin/master 8351562 glozow: [fuzz] allow negative time jumps in txdownloadman_impl
09:30 < bitcoin-git> bitcoin/master 5dc94d1 glozow: fuzz fix: assert MAX_PEER_TX_ANNOUNCEMENTS is not exceeded
09:30 < bitcoin-git> [bitcoin] fanquake merged pull request #31190: TxDownloadManager followups (master...2024-10-30110-followups) https://github.com/bitcoin/bitcoin/pull/31190
09:35 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
09:48 < darosior> Yeah i see the upsides. I was pondering if Bitcoin Core really had to maintain an HTTP server (through a dependency or otherwise).
10:10 < bitcoin-git> [bitcoin] achow101 opened pull request #31244: descriptors: MuSig2 (master...musig2-desc) https://github.com/bitcoin/bitcoin/pull/31244
10:10 < andrewtoth> See #31065 as well. There is some agitation to make it do more.
10:10 <@gribble> https://github.com/bitcoin/bitcoin/issues/31065 | rest: Support transaction broadcast in REST interface by danielabrozzoni · Pull Request #31065 · bitcoin/bitcoin · GitHub
10:12 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Quit: Client closed]
10:12 < bitcoin-git> [bitcoin] achow101 opened pull request #31245: wallet: Sign transactions containing MuSig2 inputs (master...musig2-signing) https://github.com/bitcoin/bitcoin/pull/31245
10:12 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
10:15 < bitcoin-git> [bitcoin] achow101 closed pull request #31245: wallet: Sign transactions containing MuSig2 inputs (master...musig2-signing) https://github.com/bitcoin/bitcoin/pull/31245
10:22 < bitcoin-git> [bitcoin] achow101 opened pull request #31247: psbt: MuSig2 Fields (master...musig2-psbt) https://github.com/bitcoin/bitcoin/pull/31247
10:32 < 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
10:32 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Quit: Client closed]
10:35 < 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
10:42 < 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
10:43 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
10:50 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
10:56 -!- SpellChecker [~SpellChec@user/SpellChecker] has joined #bitcoin-core-dev
10:58 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Quit: Client closed]
11:06 < 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
11:43 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
11:49 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Ping timeout: 256 seconds]
11:53 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
11:57 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Client Quit]
11:59 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has quit [Quit: PaperSword]
12:01 -!- tyzef [~tyzef@user/tyzef] has joined #bitcoin-core-dev
12:13 -!- tyzef [~tyzef@user/tyzef] has quit [Quit: WeeChat 3.8]
12:27 -!- Talkless [~Talkless@mail.dargis.net] has quit [Read error: Connection reset by peer]
12:39 < bitcoin-git> [bitcoin] polespinasa opened pull request #31252: rpc: print P2WSH redeemScript in getrawtransaction (master...p2wsh_redeem) https://github.com/bitcoin/bitcoin/pull/31252
12:49 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
12:52 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Client Quit]
12:59 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.4.3]
13:07 -!- sliv3r__ [~sliv3r__@190.210.196.115] has joined #bitcoin-core-dev
13:49 -!- sliv3r__ [~sliv3r__@190.210.196.115] has quit [Quit: Client closed]
13:55 -!- bugs_ [~bugs@user/bugs/x-5128603] has quit [Quit: Leaving]
14:35 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has quit [Remote host closed the connection]
14:36 -!- andrewtoth [~andrewtot@gateway/tor-sasl/andrewtoth] has joined #bitcoin-core-dev
15:19 < bitcoin-git> [bitcoin] threewebcode opened pull request #31253: fix: recitfy typos (master...master) https://github.com/bitcoin/bitcoin/pull/31253
15:27 < abubakarsadiq> Is  https://doxygen.bitcoincore.org/ inaccessible, or is the issue on my end?
15:32 < andrewtoth> inaccessible from my end too
15:34 < lightlike> there is an issue for it: https://github.com/bitcoin-core/bitcoincore.org/issues/1068
16:17 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-dev
16:40 -!- zeropoint [~alex@45-28-139-114.lightspeed.sntcca.sbcglobal.net] has quit [Quit: leaving]
16:49 -!- tripleslash [~triplesla@user/tripleslash] has quit [Ping timeout: 260 seconds]
17:01 -!- tripleslash [~triplesla@user/tripleslash] has joined #bitcoin-core-dev
17:20 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has joined #bitcoin-core-dev
17:21 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has quit [Client Quit]
17:23 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has joined #bitcoin-core-dev
17:24 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has quit [Client Quit]
17:33 -!- pablomartin [~pablomart@92.118.61.187] has quit [Ping timeout: 252 seconds]
17:43 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has joined #bitcoin-core-dev
17:43 -!- Guest51 [~Guest51@2a01:cb1c:11dc:5e00:c46:b2ec:7a62:38cd] has quit [Client Quit]
18:07 -!- PaperSword [~Thunderbi@securemail.qrsnap.io] has joined #bitcoin-core-dev
18:38 -!- abubakarsadiq [uid602234@id-602234.hampstead.irccloud.com] has quit [Quit: Connection closed for inactivity]
18:41 -!- Guest42 [~Guest42@2804:ccc:520:f500:7432:55a4:2fe6:bb69] has joined #bitcoin-core-dev
18:51 -!- Guest42 [~Guest42@2804:ccc:520:f500:7432:55a4:2fe6:bb69] has quit [Ping timeout: 256 seconds]
19:04 -!- pablomartin [~pablomart@92.118.61.174] has joined #bitcoin-core-dev
20:00 -!- qxs [~qxs@gateway/tor-sasl/qxs] has quit [Ping timeout: 260 seconds]
20:00 -!- emzy [~quassel@user/emzy] has quit [Ping timeout: 265 seconds]
20:02 -!- qxs [~qxs@gateway/tor-sasl/qxs] has joined #bitcoin-core-dev
20:10 -!- emzy [~quassel@user/emzy] has joined #bitcoin-core-dev
20:21 -!- pablomartin [~pablomart@92.118.61.174] has quit [Ping timeout: 260 seconds]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:08 -!- aleggg [~aleggg@177.204.246.39.dynamic.adsl.gvt.net.br] has quit [Ping timeout: 260 seconds]
22:01 -!- mcey_ [~emcy@148.252.144.188] has quit [Remote host closed the connection]
22:01 -!- mcey_ [~emcy@148.252.144.188] has joined #bitcoin-core-dev
23:01 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Remote host closed the connection]
23:15 -!- pablomartin [~pablomart@92.118.61.179] has joined #bitcoin-core-dev
23:16 -!- pablomartin [~pablomart@92.118.61.179] has quit [Remote host closed the connection]
23:23 -!- cornfeedhobo [~cornfeedh@user/cornfeedhobo] has quit [Ping timeout: 252 seconds]
23:29 -!- cornfeedhobo [~cornfeedh@user/cornfeedhobo] has joined #bitcoin-core-dev
23:32 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
23:36 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 260 seconds]
23:51 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has joined #bitcoin-core-dev
23:57 -!- kevkevin [~kevkevin@209-242-39-30.rev.dls.net] has quit [Ping timeout: 252 seconds]
--- Log closed Fri Nov 08 00:00:43 2024