--- Log opened Fri Jan 28 00:00:42 2022 04:30 < nickler> no update in a while afaik, so the latest status is that this hasn't progressed past the discussion here https://github.com/sipa/bips/issues/207 07:20 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1 09:58 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has quit [Changing host] 09:58 -!- jesseposner [~jesse@user/jesseposner] has joined #secp256k1 09:59 -!- jesseposner [~jesse@user/jesseposner] has quit [Quit: Textual IRC Client: www.textualapp.com] 09:59 -!- jesseposner [~jesse@user/jesseposner] has joined #secp256k1 10:25 < halosghost> andytoshi: question for you on the bulletproofs work. Should/Must a prover or verifier use new generators for each new proof made/verified? I assume not (and that for performance, it's much better to keep them around for as long as possible)? 10:25 < sipa> I don't think there is any reason not to reuse them. 10:26 < andytoshi> yep, you can reuse them 10:26 < andytoshi> and you definitely want to, if you want to batch-verify proofs 10:27 < halosghost> makes sense, thank you! 10:39 < halosghost> is the same true of the scratch-space for verification? 10:40 < sipa> Scratch space is just space, there is nothing to reuse. 10:40 < sipa> "here is some memory if you need it" 10:48 < halosghost> sipa: I suppose what I'm asking is, if allocating scratch-space up-front, and resuing the same pointer across multiple proof verifications (as opposed to allocating/deallocating new scratch space for each one) has any potential for vulnerability or draw-back? 10:48 < sipa> Oh, definitely reuse it. 10:48 < halosghost> (it again makes sense to me for the answer to be “no,” but I wanted to ask to be sure) 10:49 < halosghost> cool, that's what I thought :) 10:54 -!- uasf_ [~uasf@2604:a880:2:d0::1bda:1001] has joined #secp256k1 10:55 -!- uasf [~uasf@157.230.135.166] has quit [Read error: Connection reset by peer] 10:55 -!- andytoshi [~apoelstra@user/andytoshi] has quit [Ping timeout: 256 seconds] 10:55 -!- andytosh1 [~apoelstra@user/andytoshi] has joined #secp256k1 10:55 -!- michaelfolkson [~michaelfo@138.68.143.20] has quit [Ping timeout: 256 seconds] 10:55 -!- michaelfolkson [~michaelfo@138.68.143.20] has joined #secp256k1 11:19 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 2.5-rc1] 12:19 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1 12:23 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #secp256k1 12:24 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds] 12:24 -!- lukedashjr is now known as luke-jr 12:41 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #secp256k1 12:42 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 240 seconds] 12:43 -!- lukedashjr is now known as luke-jr --- Log closed Sat Jan 29 00:00:44 2022