--- Log opened Thu Jul 21 00:00:27 2022
02:08 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
02:09 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 268 seconds]
04:15 -!- berryyoghurt [sid553661@id-553661.helmsley.irccloud.com] has quit [Quit: Connection closed for inactivity]
06:07 -!- real_or_random [~real_or_r@user/real-or-random/x-4440763] has quit [Quit: ZNC 1.8.2 - https://znc.in]
06:15 -!- real_or_random__ [sid554204@id-554204.tinside.irccloud.com] has quit [Quit: Updating details, brb]
06:15 -!- real_or_random [sid554204@user/real-or-random/x-4440763] has joined #secp256k1
06:27 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1
06:29 -!- mode/#secp256k1 [+o real_or_random] by ChanServ
06:32 -!- real_or_random changed the topic of #secp256k1 to: libsecp256k1 development | https://github.com/bitcoin-core/secp256k1 | Logs: http://gnusha.org/secp256k1 | Developer meeting: Monday 15:00 UTC every odd week
06:33 -!- mode/#secp256k1 [-o real_or_random] by ChanServ
06:40 < halosghost> real_or_random: this may be an odd clarification, but does “odd week” refer to Gregorian week number?
06:44 < halosghost> I assume not becuase this week is week 30; so I guess my more reasonable question is “what does ‘odd week’ mean?”
06:46 < real_or_random> this week is 29 according to  ISO 8601 
06:47 < halosghost> ahh; zero-indexed
06:47 < halosghost> cool; thank you!
06:48 < real_or_random> no, ISO 8601 says a week begins with the Monday. The first week is week 1. Week 1 of year X is the earliest week with at least 4 days in year X  
06:48 < halosghost> ahh
06:48 < halosghost> calendars are terrible
06:49 < real_or_random> We may want to change the policy to even in 2027 because 2026 will have 53 weeks
06:49 < sipa> Is that guaranteed to be consistent? As in: does it guarantee that the successor to an odd week is an even week?
06:49 < sipa> Ah, I see.
06:50 -!- mode/#secp256k1 [+o real_or_random] by ChanServ
06:51 -!- real_or_random changed the topic of #secp256k1 to: libsecp256k1 development | https://github.com/bitcoin-core/secp256k1 | Logs: http://gnusha.org/secp256k1 | Developer meeting: Monday 15:00 UTC in every week with an odd ISO 8601 week number
06:56 <@real_or_random> Maybe we should just meet every week...
06:56 -!- mode/#secp256k1 [-o real_or_random] by ChanServ
06:57 < halosghost> sorry for the bike-shed
06:57 < sipa> Meet every monday whose first UNIX second in UTC, serialized as a big-endian 64-bit integer, fed to SHA256, yields a result whose first byte is odd.
06:59 < halosghost> sipa: first == most-significant?
06:59 < real_or_random> halosghost: what's most-significant in a string?
06:59 < real_or_random> (hashes are strings, not numbers)
06:59 < sipa> Irrelevant. The output of SHA256 is a byte array (or a bit array if you want, but that doesn't affect the result).
07:00 < halosghost> real_or_random: hmm, I suppose I tend to think of them as 256-bit numbers
07:00 < halosghost> (well, I think of 256-bit hashes as 256-bit numbers)
07:00 < sipa> That's your choice, but it isn't well-defined whether that interpretation as numbers is little or big endian.
07:00 < sipa> So the burden is on you to define that.
07:01 < halosghost> mm
07:05 < sipa> so if you choose to interpret the output of SHA256 as big endian (as SHA256 does internally), then the answer is that I mean the most significant byte. If you interpret it as little endian (as Bitcoin does for PoW purposes), then the answer is that I mean the least significant byte.
07:06 < halosghost> sipa: it was your format. I think the burden is on you, I'm afraid ☺
07:08 < sipa> Well, no. I defined it already: the first byte. If you choose to interpret SHA256 as outputting a numbrr, then it depends on how you map the output to numbers.
07:11 < halosghost> so, more accurately for me would be to interpret “first” as the_hash[0], yes?
07:12 < halosghost> (assuming the_hash is indexable by-byte)
07:14 < halosghost> $CALENDAR is definitely not able to set recurring meeting on ISO week-number pattern. I assume cron is
07:14  * halosghost explroed
07:14 < halosghost> s/roed/ores/
07:15 < halosghost> mm, nope, it doesn't
07:28 < hebasto> real_or_random: does https://github.com/bitcoin-core/secp256k1/pull/1113#issuecomment-1191554440 look like a move in the right direction?
08:29 < real_or_random> what's $CALENDAR? 
08:29 < real_or_random> halosghost: you can just set it for this week and say it should repeat every two weeks ^^
08:34 < halosghost> real_or_random: sadly, Google calendar for the moment. long-term, I'm slowly developing a tzdata (and tooling) for calendars so I can use symmetry454 and have much more pleasant repetition scheduling
08:34 < halosghost> real_or_random: hah; I suppose that'd work well enough ☺
08:49 < real_or_random> :D
08:52 < real_or_random> hebasto: Hah, yes, that's nice. That means that your PR won't depend on the config simplications
08:53 < real_or_random> (In the meeting, we said that we want to change config stuff first to avoid that CMake will add yet another config file)
09:03 < hebasto> real_or_random: that is the point :)
09:07 < hebasto> for now, to be a drop-in replacement of Autotools build system, Cmake stuff requires support for (a) valgring, (b) experimental options, and (c) exporting of the `libsecp256k1.pc`
09:13 -!- halosghost [~halosghos@user/halosghost] has quit [Ping timeout: 240 seconds]
09:15 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1
09:23 -!- halosghost [~halosghos@user/halosghost] has quit [Ping timeout: 268 seconds]
09:24 -!- halosghost [~halosghos@user/halosghost] has joined #secp256k1
11:25 -!- halosghost [~halosghos@user/halosghost] has quit [Quit: WeeChat 3.6]
12:56 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
12:57 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 268 seconds]
14:44 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
14:44 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
16:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
16:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
16:13 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 268 seconds]
16:19 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
17:46 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
17:47 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
19:01 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
19:02 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
21:30 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
21:30 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
22:38 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
22:39 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #secp256k1
--- Log closed Fri Jul 22 00:00:27 2022