--- Log opened Mon Dec 06 00:00:53 2021
06:34 -!- roconnor [~roconnor@coq/roconnor] has joined #secp256k1
08:34 -!- hg [~halosghos@user/halosghost] has joined #secp256k1
08:55 -!- ajonas_ [sid385278@id-385278.helmsley.irccloud.com] has joined #secp256k1
09:44 < robot-dreams> How did gmaxwell collect benchmarks like the ones here? https://github.com/bitcoin-core/secp256k1/pull/815#issuecomment-834728868 did he just have a bunch of hardware lying around?
09:47 < sipa> he has a lot of hardware
10:51 -!- t-bast [~t-bast@user/t-bast] has joined #secp256k1
10:58 < robot-dreams> General question, it looks there's a lot going on in secp256k1 and secp256k1-zkp (e.g. optimizations, musig, FROST, range proofs). What are you all focusing on / where needs review attention right now?
11:12 < roconnor> musig?
11:59 < nickler> musig is at least my focus right now secp wise. The plan was to merge it if real_or_random gives his thumbs up. He's currently reviewing, but more review is always appreciated of course.
12:00 < nickler> Especially since we need to build things on top like bip32-type tweking, sign to contract, variable length messages, etc.
12:07 -!- t-bast [~t-bast@user/t-bast] has quit [Quit: Leaving]
17:04 -!- hg [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.3]
22:26 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #secp256k1
22:27 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 256 seconds]
22:27 -!- lukedashjr is now known as luke-jr
--- Log closed Tue Dec 07 00:00:54 2021