--- Log opened Mon Feb 19 00:00:07 2024
04:38 -!- salvatoshi [~salvatosh@213.215.6.86] has joined #bitcoin-rust
05:45 -!- salvatoshi [~salvatosh@213.215.6.86] has quit [Remote host closed the connection]
05:45 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has joined #bitcoin-rust
05:46 -!- arik__ [sid402902@id-402902.lymington.irccloud.com] has quit [Ping timeout: 246 seconds]
05:47 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has quit [Ping timeout: 260 seconds]
05:53 -!- jkczyz [sid419941@id-419941.lymington.irccloud.com] has quit [Ping timeout: 260 seconds]
05:55 -!- FelixWeis__ [sid154231@hampstead.irccloud.com] has joined #bitcoin-rust
06:02 -!- FelixWeis__ [sid154231@hampstead.irccloud.com] has quit [Ping timeout: 256 seconds]
06:04 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has joined #bitcoin-rust
06:15 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has quit [Ping timeout: 256 seconds]
06:28 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has joined #bitcoin-rust
06:29 -!- arik__ [sid402902@lymington.irccloud.com] has joined #bitcoin-rust
06:34 -!- jkczyz [sid419941@id-419941.lymington.irccloud.com] has joined #bitcoin-rust
07:50 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has quit [Ping timeout: 256 seconds]
07:53 -!- FelixWeis__ [sid154231@id-154231.hampstead.irccloud.com] has joined #bitcoin-rust
08:45 -!- darosior1 [~darosior@109.205.214.46] has joined #bitcoin-rust
08:46 -!- darosior [~darosior@109.205.214.46] has quit [Read error: Connection reset by peer]
08:47 -!- darosior1 is now known as darosior
09:13 -!- salvatoshi [~salvatosh@genymobile-2-6-86.fib.nerim.net] has quit [Ping timeout: 264 seconds]
09:53 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has joined #bitcoin-rust
10:21 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has quit [Ping timeout: 256 seconds]
10:57 < Ademan> https://github.com/bitcoin/bitcoin/pull/29189 do I read this correctly that libbitcoinkernel is expected to be "ready" in short order? losing rust-bitcoinconsensus is troublesome otherwise
12:32 < darosior> Ademan: why do you think it's troublesome? Any use you aware of which were not reported in this thread?
12:48 < Ademan> darosior: I am using bdk-reserves in my application, and also need to validate child transactions (in my case, a refund tx) before signing the parent transaction. both of these use bitcoin::Transaction::verify() I suppose I can continue using the old rust-bitcoinconsensus if/until the next soft fork, it wasn't totally clear to me though, if I can expect libbitcoinkernel to be a viable replacement by 
12:48 < Ademan> then
14:54 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has joined #bitcoin-rust
15:46 -!- salvatoshi [~salvatosh@lfbn-idf3-1-1331-187.w92-170.abo.wanadoo.fr] has quit [Ping timeout: 246 seconds]
22:48 -!- Guest7282 [~Guest7282@1.195-178-91.adsl-dyn.isp.belgacom.be] has joined #bitcoin-rust
23:00 -!- Guest7282 [~Guest7282@1.195-178-91.adsl-dyn.isp.belgacom.be] has left #bitcoin-rust [Error from remote client]
--- Log closed Tue Feb 20 00:00:05 2024