--- Log opened Mon Aug 28 00:00:42 2023
01:12 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
01:58 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
02:10 -!- jonatack2 [~jonatack@user/jonatack] has joined #secp256k1
02:12 -!- jonatack1 [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
03:11 < nickler_> I'll be missing the meeting today unfortunately
04:17 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
04:32 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
07:00 -!- preimage [~halosghos@user/halosghost] has joined #secp256k1
07:01 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
07:03 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
08:00 < real_or_random> meeting
08:00 < real_or_random> sipa hebasto 
08:00 < hebasto> hi
08:01 < sipa> hi
08:02 < real_or_random> topics? :)
08:02 < real_or_random>  one topic is that we planned a release
08:03 < real_or_random> https://github.com/bitcoin-core/secp256k1/milestone/4 ... "One month before 26.0 feature freeze bitcoin/bitcoin#27758"
08:03 < real_or_random> this is sep 1
08:03 < sipa> cool
08:03 < real_or_random> there's one issue here which I hoped to have fixed... okay, I guess, next time...
08:04 < sipa> i have not been very active in secp256k1 (lots of bip324 work though!), but feel free to ping me for reviews
08:05 < real_or_random> https://github.com/bitcoin-core/secp256k1/compare/v0.3.2...master a lot of commits, even if one ignores the ci stuff
08:05 < real_or_random> we merged ellswift
08:05 < real_or_random> hm, I guess I can have a look this week and see if we need more changelog entries for a release.
08:06 < real_or_random> maybe next monday is a nice date then. nickler_ is out this week
08:07 < sipa> even quite a few PRs since the last merge into Bitcoin Core: https://github.com/bitcoin-core/secp256k1/compare/c545fdc374...master
08:07 < real_or_random> yeah, lots of invisible improvements ^^
08:07 < real_or_random> it makes sense to update the subtree then after the release 
08:08 < real_or_random> what do you think? would next monday work for you? 
08:09 < sipa> yeah, i'm around i think
08:09 < sipa> it's a US holiday actually, but i don't have any plans
08:09 < hebasto> there are API changes in the next release, right?
08:10 < sipa> yes, but only backward-compatible ones, I believe?
08:11 < real_or_random> I hope yes. are you asking because you want to run the API-diff tool?
08:11 < hebasto> are we interested in tools like https://github.com/bitcoin-core/secp256k1/pull/1380?
08:12 < hebasto> ^^ yes
08:12 < real_or_random> I'm slightly in favor, I think
08:13 < real_or_random> but it will be good if sipa could have a look and Concept (N)ACK
08:13 < hebasto> right
08:13 < sipa> even if we don't actually merge the changes there, it's useful to know what the outcome would be for the new prospective release
08:14 < hebasto> I'll do checks anyway
08:14 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
08:14 < real_or_random> yep indeed
08:15 < real_or_random> anything else to discuss about the release? 
08:16 < sipa> feature-wise, I think ellswift is the only change?
08:16 < sipa> since 0.3.2?
08:16 < real_or_random> should be, yes
08:17 < real_or_random> it could even be the only visible change
08:17 < real_or_random> (for an observer without a stop watch)
08:17 < sipa> apart from the only changelog entry (the static build on windows thing), but i doubt that affects many people (if any)
08:17 < sipa> s/only/other/
08:18 < real_or_random> ah okay, nice that we have an entry there already.
08:18 < real_or_random> did you notice any issues with the API in the Core PRs? 
08:18 < real_or_random> if we want to change the PR, now would be the time.
08:18 < sipa> change what PR?
08:19 < real_or_random> "change the API"
08:19 < real_or_random> sorry
08:20 < sipa> i believe https://github.com/bitcoin/bitcoin/pull/27479/commits/eff72a0dff8fa83af873ad9b15dbac50b8d4eca3 was the one commit that actually interacts with the ellswift API
08:20 < hebasto> does it make sense to label new API an "experimental" one? (for a couple release cycles)
08:21 < sipa> i don't mind doing so, but only if we actually have a concrete plan/condition for making it non-experimental later
08:21 < sipa> and i'm not sure it's necessary here
08:22 < hebasto> okay
08:22 < real_or_random> hm yeah, I think our latest consensus here was not to make experimental 
08:22 < real_or_random> in particular because we have releases now
08:22 < real_or_random> so we could signal API changes
08:22 < real_or_random> (if we really want them)
08:23 < sipa> we also spent a lot of time debating the API already (and made some changes in response to that)
08:23 < real_or_random> and the core commit looks commit (except lol @ the discussion about "initiating" -- I can remember we discussed this a lot)
08:23 < real_or_random> *looks good
08:23 < real_or_random> -.-
08:24 < real_or_random> yeah let's keep it a "full" feature
08:25 < sipa> agreed
08:25 < real_or_random> more discussion points for the release?
08:26 < real_or_random> if not, do we have anything to discuss for the CI migration? I think there's not much to say here. We moved everything to GHA before the sep 1st deadline. We're still doing some improvements (re-add macOS valgrind and add native ARM tasks, probably using Cirrus free credits), those can be tracked in the tracking issue 
08:26 < sipa> ok, good to hear you're on top of it
08:28 < real_or_random> GHA will introduce MacOS on ARM, we may reconsider then. But that's future stuff... It's good that we have Cirrus there as a general option (either with limited free credits, or with the Core runner)
08:28 < real_or_random> If some other stuff (besides ARM) turns out to be strange/difficult on GHA in the future, we have Cirrus as a 2nd option
08:29 < real_or_random> hebasto: more to say about this?  
08:30 < hebasto> I have to admit that Cirrus was easier to write scripts and matrices...
08:31 < hebasto> but GHA indeed allows to reintroduce Valgrind on macOS
08:32 < real_or_random> I agree. Their syntax is more sophisticaed for "typical" testing tasks, whereas GHA is less focused
08:33 < hebasto> performance of both CI providers is roughly at the same level
08:33 < real_or_random> but I also think what we arrived at looks good. And it's ultimately also a matter of taste and the fact that we had to learn how stuff is done in GHA
08:34 < hebasto> right
08:35 < real_or_random> other topics?
08:37 < real_or_random> ok, then end of meeting :)
08:38 < sipa> kthxbye
08:38 < real_or_random> :D
08:44 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
09:16 -!- achow101 [~achow101@user/achow101] has quit [Remote host closed the connection]
09:32 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
10:23 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
10:27 -!- achow101 [~achow101@user/achow101] has joined #secp256k1
11:25 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
11:46 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has joined #secp256k1
13:37 -!- 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:08 -!- tromp [~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl] has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
15:03 -!- HumanGeek [~HumanG33k@82.66.65.160] has quit [Ping timeout: 246 seconds]
15:36 -!- HumanGeek [~HumanG33k@82.66.65.160] has joined #secp256k1
15:44 < roconnor> secp256k1_modinv64_divsteps_62_var is correct (if it terminates).
16:13 -!- preimage [~halosghos@user/halosghost] has quit [Quit: WeeChat 4.0.3]
23:26 -!- jonatack2 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
23:26 -!- jonatack2 [~jonatack@user/jonatack] has joined #secp256k1
23:31 -!- jonatack2 [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
23:31 -!- jonatack3 [~jonatack@user/jonatack] has joined #secp256k1
--- Log closed Tue Aug 29 00:00:42 2023