--- Log opened Fri Aug 19 00:00:54 2022
08:58 < darosior> sanket1729: i remember discussing input size estimation for Taproot outputs with you. Have you reached a conclusion?
10:23 < darosior> Using the largest of the branch satisfactions is probably the most reasonable, but it can be a pretty large overestimation..
10:24 <@sipa> could it be possible to mark in the descriptor itself which keys are available yes/no/maybe?
10:29 < darosior> If we go this way we might want to mark which leaves are available, because we may not be able to complete some other challenges, even if we have the key
10:32 <@sipa> How so?
10:32 <@sipa> Oh this would apply to keys, hash preimages, and locktimes.
10:45 < darosior> This makes me think of the probabilities in the policy language. We could have something similar (and optional) in descriptors. A probability of 0 would be the "unavailable" case you mentioned. Not sure if it's worth the complexity though.
10:54 <@sipa> I don't think probabilities is what you care about.
10:54 <@sipa> Just possible/impossible/certain.
10:54 <@sipa> As they guide the maximum size of a witness.
10:55 <@sipa> No matter how likely a key is to be available (99.999%...), if you don't know that it will be, you need to take solutions into account that don't rely on it.
10:55 < darosior> Yes, right.
19:27 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has quit [Quit: ZNC 1.8.2 - https://znc.in]
19:27 -!- sanket1729 [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has quit [Quit: ZNC 1.8.2 - https://znc.in]
19:29 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has joined ##miniscript
19:29 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has quit [Remote host closed the connection]
19:30 -!- sanket_cell [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has joined ##miniscript
19:31 -!- sanket1729 [~sanket172@ec2-100-24-255-95.compute-1.amazonaws.com] has joined ##miniscript
19:36 < sanket1729> sipa: AFAIR, I think we discussed having labels for keys. Something like tr(cold@02042143....,{multi_a(hot_key1@431344....,hot_key2@01324134.....)}). While using the descriptor we can additionally supply which keys we expecting to sign with. Spend with {hot_key1, hot_key2}
--- Log closed Sat Aug 20 00:00:55 2022