Does the long run SIGHASH_ANYPREVOUT functionality damage the privateness of Taproot lightning channels?


One of many benefits I’ve heard about Taproot is that every one transactions will seem an identical to a blockchain observer. This could after all even be true for lightning channel open/shut transactions as properly which might be an awesome privateness profit for lightning customers.

For what I perceive of the proposed ANYPREVOUT improve, it should construct on prime of Taproot however might want to use a distinct size pubkey. Wouldn’t it be potential for an observer to scan the blockchain for this pubkey size with a purpose to decide which transactions are utilizing ANYPREVOUT, and are subsequently more likely to be lightning associated? Or is it potential to in some way cover this inside Taproot in such a method that privateness can nonetheless be maintained?

Supply hyperlink

Leave a reply