--- Log opened Fri May 05 00:00:53 2023
00:16 -!- Netsplit *.net <-> *.split quits: tromp, lightningbot
00:20 -!- Netsplit over, joins: lightningbot
06:48 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
10:48 < stratospher[m]> <real_or_random> "it just unifies the bound into a..." <- would this also explain VERIFY_CHECK [here](https://github.com/bitcoin-core/secp256k1/blob/359be0d80b2c40e3f27656491f2108f6c7736f64/src/group_impl.h#L749) in the ellswift PR? (limiting magnitude of t to 31 and finally r to 32).or is there some other reason for why we limit r's magnitude to 32 here?
11:26 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
11:42 -!- g-tenko-r[m] [~g-tenko-r@2001:470:69fc:105::3:5410] has joined #secp256k1
13:29 -!- jonatack1 [~jonatack@user/jonatack] has joined #secp256k1
13:30 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 260 seconds]
14:41 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.8]
15:05 < real_or_random> stratospher[m]: yes! this line probably deserves a comment
15:08 < real_or_random> this assertion is a bit unusual. SECP256K1_B is the "b" constant of the curve, so it won't change in this library. but I think it's not not entirely crazy that someone will reuse parts of the code base for another curve in the future, so it's a good idea to try to document when we're relying on specific properties of "b".
15:10 < real_or_random> (and we use small curves with different b values for testing, see the "exhaustive tests") 
15:42 -!- jonatack1 [~jonatack@user/jonatack] has quit [Ping timeout: 268 seconds]
15:51 -!- jonatack1 [~jonatack@user/jonatack] has joined #secp256k1
--- Log closed Sat May 06 00:00:53 2023