--- Log opened Thu Jul 24 00:00:51 2025
03:19 -!- jungly [~jungly@user/jungly] has joined #bitcoin-rust
08:30 < andytoshi> we use it heavily at blockstream (but also not the plan API)
08:31 < andytoshi> and there are lots of bdk users who directly use the miniscript API
08:31 < andytoshi> anchorwatch, liana, the TABConf "capture the bitcoin" project
08:31 < andytoshi> there are also several hww vendors who use it, though i don't know any details about them
08:32 < andytoshi> i will start using the plan API whenever i get around to updating my wallet software
08:32 < andytoshi> its main use is when you are trying to use miniscript but it's not easy for you to access signing material directly
08:38 -!- jerryf_ [~jerryf@user/jerryf] has joined #bitcoin-rust
08:40 -!- jerryf [~jerryf@user/jerryf] has quit [Ping timeout: 244 seconds]
08:59 -!- Emc99 [~Emc99@212.129.74.38] has joined #bitcoin-rust
09:16 -!- Emc99 [~Emc99@212.129.74.38] has quit [Quit: Client closed]
09:16 -!- Emc99 [~Emc99@212.129.74.38] has joined #bitcoin-rust
09:21 -!- Emc99 [~Emc99@212.129.74.38] has quit [Quit: Client closed]
09:40 < Ademan> yeah. My use case is tx weight estimation without unlocking private keys
09:41 < Ademan> (this is all somewhat of an artificial barrier because I am pretty comfortable just assuming taproot keyspend only in this project)
09:42 < Ademan> hrm 
09:42 < Ademan> but if there's a *useful* use case I can add support for while I'm doing this, that seems worthwhile
09:44 < Ademan> s/estimation/calculation/
10:32 < yancy> re tx weight estimation, it seems like there's a few ways to go about this.  There's also the predict_weight() api in rust-bitcoin.
14:03 -!- darosior [~darosior@109.205.214.46] has quit [Quit: Ping timeout (120 seconds)]
14:04 -!- darosior [~darosior@109.205.214.46] has joined #bitcoin-rust
14:12 -!- jerryf_ [~jerryf@user/jerryf] has quit [Remote host closed the connection]
14:13 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-rust
15:23 -!- jerryf [~jerryf@user/jerryf] has quit [Remote host closed the connection]
15:23 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-rust
15:37 -!- thelounge4966 [~thelounge@149.106.235.56] has joined #bitcoin-rust
16:02 -!- jerryf [~jerryf@user/jerryf] has quit [Ping timeout: 244 seconds]
16:04 -!- jerryf [~jerryf@user/jerryf] has joined #bitcoin-rust
17:02 -!- thelounge4966 [~thelounge@149.106.235.56] has quit [Quit: The Lounge - https://thelounge.chat]
17:04 -!- thelounge4966 [~thelounge@149.106.235.56] has joined #bitcoin-rust
17:06 -!- thelounge4966 [~thelounge@149.106.235.56] has quit [Client Quit]
17:08 -!- thelounge4966 [~thelounge@149.106.235.56] has joined #bitcoin-rust
17:30 < Ademan> yancy: sorry for the latency lol, if I'm not mistaken predict_weight kinda requires all of the interesting stuff (witness sizes) as input (which afaict I can derive from plan)
--- Log closed Fri Jul 25 00:00:54 2025