--- Log opened Tue Jan 17 00:00:18 2023
02:18 < josie> RubenSomsen: from what I understand, taproot privacy comes from not having to reveal the script path unless it is needed and then *only* revealing the branch taken and not revealing all the other possible scripts
02:38 < RubenSomsen> Yeah that makes me realize you actually need a different K (and thus ECC mult) for every script path, since otherwise the entire tree can be generated
02:42 < RubenSomsen> I.e. the same problem: if I have a tree with four publicly known keys A, B, C, D and I tweak them all with K and then reveal one branch, let's say A, then the entire tree can be generated to figure out that B, C and D are also part of the tree with the same K
02:46 < RubenSomsen> I think when using a different K for every path the only remaining distinction is that you are revealing which scripts you're using ahead of time, instead of at the time when you use the paths.
02:47 < RubenSomsen> This also makes it easier to link a revealed script path to a specific person/entity, as normally you wouldn't necessarily know who the output with the revealed script belongs to (although I imagine it's hard not to leak this info, especially for exchanges).
--- Log closed Wed Jan 18 00:00:19 2023