--- Log opened Sat Oct 23 00:00:12 2021
04:38 -!- tibo [~tibo@240d:1a:afa:1d00:848d:f1b1:cc60:d391] has joined #bitcoin-rust
05:48 -!- tibo [~tibo@240d:1a:afa:1d00:848d:f1b1:cc60:d391] has quit [Remote host closed the connection]
07:49 -!- tibo [~tibo@240d:1a:afa:1d00:848d:f1b1:cc60:d391] has joined #bitcoin-rust
07:53 -!- tibo [~tibo@240d:1a:afa:1d00:848d:f1b1:cc60:d391] has quit [Ping timeout: 264 seconds]
13:55 -!- willcl_ark [~quassel@user/willcl-ark/x-8282106] has joined #bitcoin-rust
14:09 < elsirion> In rust-secp KeyPair does not have a serde impl currently. I imagine this is due to the problem of getting a secp context into the decoding function? Would there be any opposition to implementing it using the global context when enabled?
14:09 < elsirion> Context: https://github.com/fedimint/minimint/pull/19/files#r735020368
14:11 < elsirion> andytoshi: real_or_random: what's the actual risk of using the global, but in most cases randomized on startup, context to decode KeyPairs?
21:21 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
21:34 -!- belcher [~belcher@user/belcher] has joined #bitcoin-rust
--- Log closed Sun Oct 24 00:00:12 2021