--- Log opened Fri Aug 07 00:00:42 2020
00:08 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
00:33 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
01:23 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
01:24 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
01:56 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has joined #rust-bitcoin
02:10 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:49 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has joined #rust-bitcoin
03:03 -!- Mathew7Kuhn [~Mathew7Ku@static.57.1.216.95.clients.your-server.de] has joined #rust-bitcoin
03:28 -!- Kiminuo [~mix@141.98.103.100] has joined #rust-bitcoin
03:36 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
03:39 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has joined #rust-bitcoin
04:16 < dr-orlovsky> Am I right that right now there is no complete implementation of BIP-174 PSBT signing in rust? Rust-wallet does not support PSBTs, other existing projects providing PSBT signing functionality do that not according to the spec (no checks mentioned in the spec are performed, no clear roles separation)
04:20 -!- Mathew7Kuhn [~Mathew7Ku@static.57.1.216.95.clients.your-server.de] has quit [Ping timeout: 260 seconds]
04:35 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has quit [Read error: Connection reset by peer]
04:35 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has joined #rust-bitcoin
04:49 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:52 < darosior> dr-orlovsky: Riccardo Masetta has one iirc
04:52 < darosior> Masutti*
04:53 < darosior> Arf Casatta *
04:53 < darosior> https://github.com/RCasatta/firma
04:56 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has joined #rust-bitcoin
05:14 -!- reallll [~belcher@unaffiliated/belcher] has joined #rust-bitcoin
05:17 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds]
05:18 -!- reallll is now known as belcher
05:25 -!- dr_orlovsky [~dr-orlovs@31.14.40.19] has joined #rust-bitcoin
05:28 -!- dr_orlovsky [~dr-orlovs@31.14.40.19] has quit [Client Quit]
05:28 -!- dr_orlovsky [~dr-orlovs@31.14.40.19] has joined #rust-bitcoin
05:32 -!- Kiminuo [~mix@141.98.103.100] has quit [Ping timeout: 246 seconds]
05:53 -!- Kiminuo [~mix@141.98.103.100] has joined #rust-bitcoin
06:04 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 240 seconds]
06:05 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin
06:27 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
06:44 -!- dr-orlovsky [~dr-orlovs@2001:171b:c9ab:8170:15f8:b38e:6c70:6ad0] has quit [Quit: Textual IRC Client: www.textualapp.com]
06:45 -!- dr_orlovsky [~dr-orlovs@31.14.40.19] has quit [Quit: ZNC 1.8.0 - https://znc.in]
06:45 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #rust-bitcoin
06:47 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has quit [Client Quit]
06:47 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #rust-bitcoin
07:33 -!- otoburb [~otoburb@unaffiliated/otoburb] has quit [Quit: Lost terminal]
07:41 < dr-orlovsky> darosior: yep, I know this implementation (https://github.com/RCasatta/firma), unfortunately it's not complete impl of the BIP
07:41 < darosior> What's missing ?
07:45 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has quit [Read error: Connection reset by peer]
07:45 -!- dongcarl [~dongcarl@unaffiliated/dongcarl] has joined #rust-bitcoin
08:40 < dr-orlovsky> darosior: checks from this part of the spec, for instance: https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki#signer
10:18 < dr-orlovsky> I've made this proposal on filling the API gap with PSBTs: https://github.com/rust-bitcoin/rust-bitcoin/issues/455
--- Log closed Fri Aug 07 10:58:26 2020
--- Log opened Fri Aug 07 10:58:26 2020
11:07 < andytoshi> dr-orlovsky: nice, thanks for looking into this
11:07 < andytoshi> i think it's reasonable that a PSBT signer role should be implemented in rust-bitcoin
11:07 < andytoshi> the finalizer role belongs in rust-miniscript
11:08 < andytoshi> combiner should also be in rust-bitcoin probably
11:08 < andytoshi> and extractor
11:08 < andytoshi> Creator and Updator are pretty boring, i think they're sufficiently "implemented" by exposing the PSBT maps, they don't need to be explicitly implemented as roles
12:18 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
12:34 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
13:07 < BlueMatt> andytoshi: hmm, wouldnt it be nice to automatically use the global context if its set?
13:07 < BlueMatt> ie if global-context is set in libsecp at build-time, then all manually-created contexts become dummy values
13:08 < BlueMatt> or is that not practical due to randomization of the global context being race-y?
13:08 < BlueMatt> sgeisler probably has an opinion
13:32 < andytoshi> (a) it prevents rerandomization, (b) it makes it ambiguous which functions require a secp context and which don't
13:32 < andytoshi> i find that basically any global variable use increases cognitive load
13:33 < andytoshi> i mean, i could certainly get used to it, but i've never wanted a global secp context
13:33 < BlueMatt> right, the randomization part is annoying :(
13:33 < BlueMatt> but, it certainly would be nice to not have to work hard to pass contexts around everywhere which is the current state :(
13:33 < BlueMatt> either you pass them around a ton or you allocate a million of them :(
16:34 < sgeisler> andytoshi, bluematt: at least verification could always be done with the global context imo. Randomization seems silly for that as it can't possibly leak private data.
16:35 < sgeisler> Regarding other things like deriving keys and signing I don't know. How important is randomization after you do it once in the beginning?
16:37 < sgeisler> I feel like API bloat due to secp contexts is pretty bad. So I'm very inclined to use the global context wherever possible. After all the randomization only seems to be another measure against timing attacks and not the only one.
16:40 < sgeisler> I have to disagree that a *constant* global would increase cognitive load. Having to think about where to create contexts and how to pass them around seems a much bigger annoyance to me.
16:43 < sgeisler> my long term goal is to have a context-free version of every function requiring a context now, so that only people who actually care about it (embedded systems or need to re-randomize) have to pay the API complexity price while everyone else can use the simpler, probably still secure enough version.
17:25 -!- Blackwolfsa4 [~Blackwolf@195.159.29.126] has quit [Quit: Ping timeout (120 seconds)]
17:26 -!- Blackwolfsa4 [~Blackwolf@195.159.29.126] has joined #rust-bitcoin
18:22 < andytoshi> i need some time to come around to that goal
18:23 < andytoshi> i'm unconvinced that it's more complicated to have functions labeled with what crypto operations they do
18:23 < andytoshi> (although i am always thrown that you can do ECDH with a dummy context, so this already isn't a very accurate labeling..)
18:44 < gwillen> the labeling is not the problem, smart money just sets all the bits on the context anyway
18:44 < gwillen> the problem is just keeping track of the context objects :-P
18:51 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
18:52 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin
--- Log closed Sat Aug 08 00:00:42 2020