--- Day changed Fri Oct 06 2017
00:55 < gmaxwell> I wonder if we should consider going all the way to verify after sign inside libsecp256k1 itself.. https://research.kudelskisecurity.com/2017/10/04/defeating-eddsa-with-faults/
01:03 -!- jtimon [~quassel@199.31.134.37.dynamic.jazztel.es] has joined #secp256k1     
04:02 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #secp256k1     
06:05 < andytoshi> we could add a flag to the context object, which is on by default, which signals this
11:42 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Ping timeout: 240 seconds]     
11:45 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #secp256k1     
13:05 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Read error: Connection reset by peer]     
15:11 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds]     
18:36 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1     
21:43 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #secp256k1