--- Log opened Wed Oct 23 00:00:44 2019
00:11 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 245 seconds]
01:15 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has joined #secp256k1
01:52 -!- jonatack [~jon@54.76.13.109.rev.sfr.net] has quit [Ping timeout: 240 seconds]
01:52 -!- jonatack [~jon@213.152.161.35] has joined #secp256k1
04:35 -!- roconnor [~roconnor@host-104-157-204-21.dyn.295.ca] has quit [Ping timeout: 246 seconds]
05:22 -!- jonatack [~jon@213.152.161.35] has quit [Ping timeout: 268 seconds]
06:09 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #secp256k1
06:24 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #secp256k1
06:45 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
06:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 245 seconds]
06:58 < elichai2> All the num implementations in secp or little endian. right? (i.e. to check for evenness I test the first byte)
07:38 -!- roconnor [~roconnor@host-104-157-204-21.dyn.295.ca] has joined #secp256k1
07:46 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Quit: jonatack]
07:59 -!- Honthe [~Honthe@s91904421.blix.com] has joined #secp256k1
08:08 < roconnor> Is it an error for secp256k1 to call secp256k1_sha256_initialize_tagged without it being declared in hash.h?
08:08 < roconnor> *for secp256k1.c to call
08:14 < sipa> roconnor: C does not require functions to be declared if the definition is before the call
08:16 < roconnor> Sure, but you could get rid of most of the declariation .h files by that logic, so there seems to be some sort of guideline for which functions get declairations and which ones do not.  I guess my question is what is that guideline?
08:22 < roconnor> perhaps the guideline is that function calls between _impl.h must have declairations but secp256k1.c (and modules included at the end of secp256k1.c) can call any _impl.h function regardless of if it has a declaration.
08:23 < roconnor> because _impl.h are all included at the top of secp256k1.c, but their order is arbitrary.
08:23 < roconnor> so between themsleves they require forward declairations but at and after secp256k1.c everything is more or less fine.
08:35 < sipa> i guess
08:44 < roconnor> heh. Maybe you feel that as long as it compiles you are happy.
08:47 < sipa> i think the internal .h files mostly function as documentation
08:47 < sipa> in some cases they're actually needed, i expect
08:48 < sipa> so if something is missing from the .h file it should be added for clarity, and perhaps to avoid problems later
08:48 < elichai2> Why do people write papers on algorithms without providing a reference implementation? :/
08:49 < sipa> elichai2: because many academics (not all) write code that nobody would want to read :)
08:50 < elichai2> Well i'd rather read assembly at this point lol
08:50 < sipa> and they have incentives to publish papers, not code
08:50 < roconnor> There isn't a good place to put reference implementations.  On occasion I've tried putting reference implementation in tiny font in an appendix.
08:50 < elichai2> roconnor: putting a reference to a gist?
08:51 < elichai2> if anyone is bored and what to help me understand some pseudo code from a paper feel free :) otherwise i'll keep trying lol
08:51 < roconnor> Last time I was an academic, gist didn't exist.  Even today I'm skeptical that it counts as a good place.
08:51 < elichai2> :)
08:53 < roconnor> Occassionally I dream of leveraging Nix to build a reproduciable archive for research software artifacts to be stored.
08:53 < elichai2> use ipfs :P
08:55 < roconnor> clearly we need a blockchain and a new coin. :P
08:57 < roconnor> What does the SECP256K1_BUILD flag mean?
08:57 < elichai2> wow. so I continued to google this and found the exact same paper but under a different name. WAT lol
08:58 < sipa> roconnor: it means we're building libsecp256k1 itself (and not code depending on it?
08:58 < sipa> s/\?/\)/
09:47 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #secp256k1
12:09 -!- belcher [~belcher@unaffiliated/belcher] has joined #secp256k1
12:15 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
12:16 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:17 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
12:17 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:18 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
12:19 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:19 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
12:20 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:20 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Read error: Connection reset by peer]
12:21 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
12:34 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Quit: jonatack]
12:34 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #secp256k1
12:35 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Client Quit]
12:35 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #secp256k1
12:52 < elichai2> making sure again. all the nums implementation are data[0] - > Least significant byte/word/limb. and data[end] -> Most significant byte/word/limb. right?
12:57 -!- roconnor [~roconnor@host-104-157-204-21.dyn.295.ca] has quit [Ping timeout: 265 seconds]
13:02 < sipa> elichai2: you should not make any assumptions about the representation of num
13:02 < elichai2> sipa: I'm writing new functions inside of num :)
13:02 < sipa> ah!
13:05 < elichai2> in particular I need to count the first MSB bit and the first LSB bit. so need to know on what order to check :)
13:20 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #secp256k1
13:58 -!- andytosh1 [~apoelstra@wpsoftware.net] has joined #secp256k1
14:08 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Quit: Lost terminal]
17:04 -!- andytosh1 [~apoelstra@wpsoftware.net] has quit [Read error: Connection reset by peer]
17:31 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined #secp256k1
18:04 < ariard> 8
18:07 < sipa> 7
18:12 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Ping timeout: 240 seconds]
19:25 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
19:26 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
19:31 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 264 seconds]
21:03 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
21:42 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection]
21:43 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #secp256k1
21:48 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Ping timeout: 264 seconds]
22:31 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
22:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
--- Log closed Thu Oct 24 00:00:43 2019