--- Log opened Mon Dec 09 00:00:31 2019
01:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 250 seconds]
01:58 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #secp256k1
02:03 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Ping timeout: 240 seconds]
02:03 -!- jonatack [~jon@213.152.161.35] has joined #secp256k1
03:15 -!- reallll [~belcher@unaffiliated/belcher] has joined #secp256k1
03:16 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
05:50 -!- reallll is now known as belcher
06:20 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Remote host closed the connection]
06:24 -!- jonatack [~jon@213.152.161.35] has quit [Read error: Connection reset by peer]
06:47 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
07:04 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Remote host closed the connection]
07:09 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
07:54 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #secp256k1
08:34 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
08:38 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 268 seconds]
08:57 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
09:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
09:14 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
09:18 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 240 seconds]
10:03 < elichai2> if I know I have a number `s` such that `0<s<N` should I still call `secp256k1_ec_seckey_verify`? (i.e. if my CSPRNG can generate between a range)
10:09 < sipa> no
10:09 < sipa> all that function does is test whether the number is in range
10:09 < sipa> if you effectively implement that functionality elsewhere, all is good
10:13 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
10:53 < elichai2> thx. i'm also thinking about how bad is it to share the same privkey for ecdsa and schnorr
10:53 < elichai2> A. it should be fine if and only if you use a different nonce generation function
10:54 < elichai2> B. is the API is even built for that? (i.e. because of privkey negation etc.) cc nickler
10:55 < sipa> elichai2: there is a secp256k1_pubkey and a secp256k1_xonly_pubkey
10:55 < sipa> but the private key type is the same (32 byte array)
10:55 < elichai2> I don't remember if it's modified by the schnorr functions or not (negated)
10:56 < sipa> what do you mean?
10:57 < elichai2> is the privkey ever negated to make the according pubkey quad residue?
10:57 < sipa> at signing time, if needed
10:58 < elichai2> but not the user's side (i.e the user still pass a const privkey)
10:58 < sipa> no, that would break everything
10:59 < sipa> you can't go and change a private key the user generated already
11:00 < elichai2> makes sense. just wanted to make sure I remember correctly :)
13:04 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
13:04 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
13:05 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
13:06 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
14:26 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]
15:55 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
16:43 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 245 seconds]
16:44 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
16:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
--- Log closed Tue Dec 10 00:00:33 2019