--- Log opened Fri May 19 00:00:06 2023
00:04 < ademan[m]> it just occurred to me the lower impact change is probably just to utilize serialize and deserialize for the small number of times any data needs to cross between zkp and vanilla secp... i might pursue that if i burn out on this port-to-bitcoin_hashes-0.12.0 approach
02:05 -!- darosior [~darosior@194.36.189.246] has quit [Remote host closed the connection]
02:07 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-rust
02:14 -!- explore [uid233125@id-233125.hampstead.irccloud.com] has left #bitcoin-rust []
02:25 -!- darosior [~darosior@194.36.189.246] has quit [Ping timeout: 256 seconds]
02:59 -!- greypw254600216 [~greypw254@grey.pw] has quit [Quit: I'll be back!]
02:59 -!- greypw254600216 [~greypw254@grey.pw] has joined #bitcoin-rust
04:12 -!- darosior [~darosior@194.36.189.246] has joined #bitcoin-rust
09:45 -!- b42 [~mmilata@b42.cz] has quit [Quit: WeeChat 3.7.1]
09:46 -!- b42 [~mmilata@b42.cz] has joined #bitcoin-rust
18:48 -!- Ademan_ [~Ademan@47.161.28.214] has joined #bitcoin-rust
22:12 < Ademan_> actually managed to fight through all of the issues, though there were several places I'm not confident my fix was the right thing... All that to realize that bdk depends on a particular version of rust-bitcoin, leaving me the choice to either use a local copy of bdk with a tweaked Cargo.toml (might at least try it) or punt and go with the XOnlyPublicKey::{from_slice,serialize} approach heh
23:22 -!- Ademan_ [~Ademan@47.161.28.214] has quit [Ping timeout: 268 seconds]
--- Log closed Sat May 20 00:00:08 2023