--- Log opened Thu May 18 00:00:05 2023
12:25 -!- peko[m] [~pekomatri@2001:470:69fc:105::3:5cd3] has quit [Excess Flood]
14:58 -!- devrandom [~devrandom@2001:470:69fc:105::d4d] has joined #bitcoin-rust
15:08 < devrandom> is there interest in a "push model" block/tx decoder to be contributed to the crate?  we need to parse a block in small-memory devices where the block (and maximum tx) are larger than the RAM size.  perhaps others may find it useful.
15:09 < devrandom> (I seem to have fallen off the channel somehow...  I blame the IRC bridge)
18:07 -!- Ademan [~ademan@47.161.28.214] has joined #bitcoin-rust
21:29 -!- Ademan_ [~Ademan@47.161.28.214] has joined #bitcoin-rust
21:40 < Ademan_> I'm trying to use secp256k1-zkp and rust-bitcoin, but the two depend on very different versions of secp256k1, resulting in me having two "incompatible" versions of XOnlyPublicKey used with the two libraries. is there some way I could force rust-bitcoin to use a newer version? I made an attempt with [patch.crates-io] but that wasn't successful. I'm extremely new to rust so apologies if the answer is 
21:40 < Ademan_> obvious. #rust was less helpful than I'd hoped
21:48 < Ademan_> it does seem to me that rust-bitcoin could pretty safely depend on secp256k1 >=0.24.0 instead of just =0.24.0, but that probably would need someone to actually review it...
21:54 < Ademan_> currently trying to use a local copy of rust-bitcoin with secp256k1 0.27.0 and it's not going as well as I'd hoped, this seems to have had cascading effects on dependencies
22:16 < BlueMatt[m]> It’ll get upgraded sooner or later. In the mean time, can you downgrade to a previous rust-bitcoin?
22:20 < Ademan_> rust-bitcoin is the one lagging, secp256k1-zkp wants secp256k1 0.27.0
22:21 < Ademan_> I'm (probably inadvisedly) trying to hack this into shape, somewhat surprisingly the biggest changes seem to have been in bitcoin_hashes
22:21 < BlueMatt[m]> Can you use a previous zkp?
22:24 < Ademan_> nope, I'm working with sanket's musig implementation (I know that's extremely likely to change, I'm also reviewing it to the best of my abilities)
22:26 < Ademan_> I could probably see how far I can dial back the secp256k1 dependency in zkp but I'm already a bit uncomfortable with the binary compatibility between the c side of libsecp256k1 vs libsecp256k1-zkp
22:40 -!- ademan[m] [~ademan@2001:470:69fc:105::1:16db] has joined #bitcoin-rust
22:40 -!- Ademan [~ademan@47.161.28.214] has quit [Quit: leaving]
23:45 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has quit [Ping timeout: 240 seconds]
23:46 -!- Ademan_ [~Ademan@47.161.28.214] has quit [Ping timeout: 246 seconds]
23:46 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-rust
--- Log closed Fri May 19 00:00:06 2023