--- Log opened Thu Mar 07 00:00:20 2024
00:26 -!- Srishti [~Srishti@103.151.209.156] has joined #secp256k1
01:00 -!- Srishti [~Srishti@103.151.209.156] has quit [Quit: Client closed]
01:01 -!- jon_atack [~jonatack@user/jonatack] has joined #secp256k1
01:04 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 264 seconds]
01:30 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
02:03 -!- jonatack [~jonatack@user/jonatack] has joined #secp256k1
02:05 -!- jon_atack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
02:35 -!- Srishti [~Srishti@103.151.209.156] has joined #secp256k1
02:45 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
03:23 -!- jon_atack [~jonatack@user/jonatack] has joined #secp256k1
03:25 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
03:48 -!- Srishti [~Srishti@103.151.209.156] has quit [Quit: Client closed]
05:34 < siv2r> I am currently exploring project ideas that could be a good fit for the Summer of Bitcoin 2024 program.
05:35 < siv2r> What is the opinion on the Safer Tweaking API (issue #1017)? The tweaking for BIP341 appears straightforward, but the BIP32 tweaking design needs more input.
05:35 < siv2r> If anyone has other ideas that could be a better fit, please let me know. I'd be happy to look into it.
05:48 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
06:56 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
07:01 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
08:37 < real_or_random> I don't think that's a good fit. Or it depends. If we have a concept, then it may be good... Otherwise it has too many undefined ends.
08:38 < real_or_random> I think it's also related to what I said here: https://github.com/bitcoin-core/secp256k1/pull/1471#issuecomment-1967953283
08:39 < real_or_random> if we tidy our current unsafe tweaking functions into a "hazmat" (=don't use this unless you know what you're doing), then we could nice provide BIP341/BIP32 functions on top of it
08:40 < real_or_random> Not saying that we can't provide nicer tweaking functions without tidying the unsafe tweaking functions. But I think the natural approach to do the tidying first.
08:41 < real_or_random> All of this could be a SoB project, but then we need some discussions first to clarify the rough direction in which we want to move
09:52 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
10:01 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
11:01 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
11:01 -!- achow101 [~achow101@user/achow101] has joined #secp256k1
11:33 -!- Srishti [~Srishti@103.151.209.156] has joined #secp256k1
11:41 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
11:49 -!- Srishti [~Srishti@103.151.209.156] has quit [Ping timeout: 250 seconds]
12:03 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
12:30 -!- Srishti [~Srishti@103.151.209.156] has joined #secp256k1
12:47 -!- Srishti [~Srishti@103.151.209.156] has quit [Quit: Client closed]
13:41 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
13:54 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
14:16 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
14:19 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
14:22 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.2.1]
14:33 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
19:55 < siv2r> Got it. Creating hazmat APIs does go against the libsecp's principle of being difficult to use insecurely.
19:56 < siv2r> Given the uncertainty around this idea and the need for further discussions to clarify the direction, I get why it might not be the best fit for this year's Summer of Bitcoin. Side note: the project idea submission deadline is March 15.
19:56 < siv2r> I'll drop the idea for now and maybe we can revisit it next year if there's more consensus or clarity on the topic by then.
22:53 -!- Srishti [~Srishti@103.151.209.156] has joined #secp256k1
23:25 -!- Srishti [~Srishti@103.151.209.156] has quit [Quit: Client closed]
23:26 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
--- Log closed Fri Mar 08 00:00:20 2024