--- Log opened Sun Jan 22 00:00:21 2023
00:07 -!- scg [~scg@2804:1530:104:44a:aca8:85d4:c20d:bb30] has quit [Quit: Ping timeout (120 seconds)]
01:00 -!- stratospher[m] [~stratosph@2001:470:69fc:105::2:728e] has quit [Quit: You have been kicked for being idle]
01:21 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
02:38 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
05:09 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
05:14 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
05:33 -!- scg [~scg@2804:1530:104:44a:aca8:85d4:c20d:bb30] has joined #secp256k1
07:30 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
07:42 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
08:04 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
08:13 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
09:13 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
09:20 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
09:50 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Read error: Connection reset by peer]
13:24 -!- roconnor [~quassel@coq/roconnor] has quit []
13:31 -!- roconnor [~quassel@coq/roconnor] has joined #secp256k1
14:27 -!- DeanWeen is now known as DeanGuss
14:27 -!- DeanGuss [~dean@nonplayercharacter.me] has quit [Changing host]
14:27 -!- DeanGuss [~dean@user/deanguss] has joined #secp256k1
19:32 < harding> Hi.  https://github.com/bitcoin-core/secp256k1/pull/1192 looks like something that might be useful to summarize in next week's Optech newsletter, but I haven't a clue about what's going on.  Do people here (1) think this is something other people (e.g. downstream devs using libsecp256k1) might want to know about and (2) would anyone here like to write a one paragraph (ish) summary we can publish?
19:33 < sipa> I don't think it's interesting to a wider public.
19:34 < sipa> It doesn't affect anything but a special test mode of libsecp256k1 which performs exhaustive testing in an artificial, tiny, elliptic curve group that's very similar to the real one.
19:35 < sipa> And it was quite surprising to us that something weird algebraically was going on, and figuring that out was interesting, but the only practical result is that there is now one more tiny group we can test things with.
19:35 < sipa> It doesn't affect the API or users of the library in any way.
19:41 < harding> sipa: ok, thanks!  It did look like y'all were having an interesting discussion there.  :-)
--- Log closed Mon Jan 23 00:00:23 2023