--- Day changed Wed Sep 12 2018 04:05 -!- sipa_ [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 04:06 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #secp256k1 10:47 < gmaxwell> andytoshi: uh so I see rust-secp256k1 appears to enable options that we default off because of IPR concerns, e.g. https://github.com/rust-bitcoin/rust-secp256k1/blob/master/build.rs#L60 and recovery. 12:18 < andytoshi> well, recovery is needed for bitcoin sign/verifymessage interop 12:19 < andytoshi> but yeah, i should take down the endo .. it was originally there because rust-secp was a low-profile project and i wanted to feel out if anyone was going to be agressive 12:19 < andytoshi> (because i assume they'd send me a C&D rather than trying to harass an individual project maintainer with no revenue) 12:21 < andytoshi> recovery is also used intimately by the entire ethereum project which is flush with dumb money and afaik nobody has caused them trouble for it 13:01 < gmaxwell> it's likely that the relevant patent holder just hasn't realized it yet. 13:02 < gmaxwell> I mean, if not for an accident of history that patent would probably be worthless. 13:02 < gmaxwell> The holder (both the original and now the company that acquired one) has a long history of agressive enforcement. 13:03 < gmaxwell> er. acquired it* 13:05 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 13:06 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1 13:11 < andytoshi> :/. ok. i'll remove it. 13:12 < andytoshi> both endo and recovery? 13:12 < gmaxwell> endo you should just turn off. ... For recovery can you make it optional like we do in libsecp256k1 without a big mess? 13:12 < andytoshi> yep definitely 13:13 < gmaxwell> I'd generally like to be in a state where we're not encouraging people to unwittingly use recovery when they don't have to. 13:13 < andytoshi> sounds good. rust makes it very easy to feature-gate stuff like this 13:13 < andytoshi> "feature-gate" meaning that the user has to type `--features="recovery"` to turn it on 13:14 < gmaxwell> (I don't expect anyone who needs recovery for signmessage or eth compatibility is going to just stop using it until licensing bills and lawsuits show up... but it would be good if uniform treatment didn't guide people to start using it who wouldn't have otherwise) 13:14 < andytoshi> agreed 13:19 < andytoshi> opened https://github.com/rust-bitcoin/rust-secp256k1/issues/70 .. will try to get to this this week ... feature-gating will require a major version bump so i'll need to sync with BlueMatt to see what else we want to throw in there 13:40 < BlueMatt> gmaxwell: ugh, that sucks, cause lightning uses it for imo-kinda-dumb reasons 13:41 < gmaxwell> BlueMatt: well, build with it then. If libraries hadn't been treating it first class, perhaps lightning never would have used it. 13:42 < BlueMatt> yea, fair