--- Day changed Sat Nov 07 2020
02:10 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has quit [Ping timeout: 246 seconds]     
08:17 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has joined ##miniscript     
10:02 < andytoshi> can we make stealh addressess fit into descriptors
10:02 < sipa> no     
10:02 < andytoshi> lol, ok
10:02 < sipa> descriptors are functions that evaluate to a scriptPubKey
10:03 < sipa> it would be a major break in functionality to turn it into something tx dependent
10:04 < andytoshi> hmm maybe i'm misremembering how stealth addresses work
10:04 < andytoshi> can they be based on the spk rather than the wholetx
10:05 < andytoshi> i guess not, the scriptpubkey doesn't change :)
10:05 < sipa> they at least need to depend on something in the input
10:05 < andytoshi> right
10:05 < sipa> hmm, maybe not - maybe the tweak info can go in the spk as well
10:06 < andytoshi> i think, in elements we could do something liek this where you encrypt the tweak into the rangeproof
10:06 < andytoshi> or into the encrypted data field
10:06 < andytoshi> but in bitcoin i'm doubtful
10:07 < sipa> but that'd still mean that descriptors would be predicates over spks rather than a nullary function that evaluates to an spk
10:07 < andytoshi> hmm right
10:07 < sipa> meaning you can't precompute what to watch for
10:07 < andytoshi> yeah. and that's inherent to stealth addresses
10:07 < sipa> and instead need to evaluate every spk/tx separately
10:07 < sipa> righr
10:07 < sipa> right
10:13 < sipa> if the tweak or whatever additional information that goes into the computation is part of the descriptor itself, it's possible of course
10:14 < andytoshi> yeah ... but what does that get you over the existing bip32 support
10:14 < andytoshi> or p2c
10:14 < sipa> and in some use cases that may be interesting... you'd need to do the scanning yourself, but you may be able to reuse descriptor framework for signing, after you have the tweak
10:34 < andytoshi> musing whether there's value in adding a flag to p2c keys with the entire scriptpubkey ... so then you at least couldn't reuse keys in multiple multiparty descriptors
10:35 < andytoshi> i think this would have no security implications (or at least, any security gain would be so fragile/specific would be not worth analyzing)
10:35 < andytoshi> but might help privacy
10:36 < andytoshi> oh "p2c with the scriptpubkey" is kinda circular, you'd have to compute the scriptpubkey, use that as a tweak on the keys, then you get the "real" scriptpubkey 
11:34 -!- sipa_ [~pw@gateway/tor-sasl/sipa1024] has joined ##miniscript     
11:36 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 240 seconds]     
11:52 -!- sipa_ is now known as sipa     
12:49 -!- jonatack [~jon@213.152.161.30] has quit [Ping timeout: 272 seconds]     
13:14 -!- jonatack [~jon@88.124.242.136] has joined ##miniscript     
13:19 -!- jonatack [~jon@88.124.242.136] has quit [Ping timeout: 246 seconds]     
13:19 -!- jonatack [~jon@134.19.179.27] has joined ##miniscript     
15:19 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]     
18:12 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]     
18:17 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined ##miniscript