--- Log opened Thu Jul 23 00:00:27 2020 01:22 < elichai2> sorcus: what do you mean by "bit-by-bit"? (I can't read whatever language that is) 01:27 < sipa> elichai2: it's just doing an ec multiplication 01:27 < sipa> poont times scalar 01:27 < sipa> sorcus: you can, but i doubt that's what you actually want 01:27 < elichai2> oh, so of course libsecp can do it. and how is that "bit-by-bit" 01:28 < sipa> libsecp256k1 aims to provide a higher level safe protocol interface 01:29 < sipa> ec multiplication is primitive that all secp256kq cryptography is based on, so obviously it is implemented internally 01:29 < sipa> it occurs in signing, verification, key generation, diffie-hellman, ... 01:30 < sipa> but in general you just want to doone of those, instead of the primitive 02:14 -!- jonatack [~jon@82.102.27.195] has joined #secp256k1 02:51 < sorcus> Oh, hi. 02:51 < sorcus> https://gist.github.com/MrSorcus/6f290098e831bea1db7803400d619737 - i mean something like this. 02:52 < sorcus> https://gist.github.com/MrSorcus/8bc6e19096f6c752b9690f24b2c57e0a - this is result. Looks like it works. Hm... 02:58 < elichai2> sorcus: bear in mind that you're using an internal API. so A. This is probably unsafe. B. there's 0 guarantee on the stability and correctness of those functions. 02:59 < elichai2> (as for the serializing you can use this context: https://github.com/bitcoin-core/secp256k1/blob/master/include/secp256k1.h#L191 and you don't need to allocate) 03:00 < sorcus> elichai2: Yeah, i know. Thanks for the warning. :-) 03:02 < sorcus> elichai2: "and you don't need to allocate" - sounds great. Thank you :-) 03:34 -!- jonatack [~jon@82.102.27.195] has quit [Ping timeout: 240 seconds] 03:35 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has joined #secp256k1 03:53 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #secp256k1 03:56 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 240 seconds] 04:06 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection] 04:06 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #secp256k1 05:13 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has quit [Ping timeout: 240 seconds] 06:26 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #secp256k1 07:30 -!- sorcus [~sorcus@2a01:7e01:e002:8ffc:caf2:ef3d:542:bc0e] has quit [Ping timeout: 260 seconds] 12:39 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 12:40 -!- afk11` [~afk11@gateway/tor-sasl/afk11] has joined #secp256k1 12:47 -!- sorcus [~sorcus@2a01:7e01:e002:8ffc:caf2:ef3d:542:bc0e] has joined #secp256k1 16:00 -!- afk11` is now known as afk11 18:12 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Ping timeout: 272 seconds] 18:20 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #secp256k1 23:32 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 260 seconds] --- Log closed Fri Jul 24 00:00:28 2020