Esteban Ordano [ARCHIVE] on Nostr: 📅 Original date posted:2019-12-20 📝 Original message: On Fri, Dec 20, 2019 at ...
📅 Original date posted:2019-12-20
📝 Original message:
On Fri, Dec 20, 2019 at 12:59 PM ZmnSCPxj via Lightning-dev <
lightning-dev at lists.linuxfoundation.org> wrote:
> Current Lightning Network mutual closes are spends of 2-of-2 outputs.
> Given that most people will use either 1-of-1 or 2-of-3 ("never go to sea
> with two chronometers, take one or three"), they stand out and it is
> reasonable to assume that any 2-of-2 will be Lightning.
>
Interesting... alternatively, one could explore modifying the current
2-of-2 closing outputs to make them undistinguishable from 2-of-3 outputs
by negotiating a random third public key with a nonexistent private key
(like XORing random values provided by each channel participant).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20191220/d1e75785/attachment.html>;
📝 Original message:
On Fri, Dec 20, 2019 at 12:59 PM ZmnSCPxj via Lightning-dev <
lightning-dev at lists.linuxfoundation.org> wrote:
> Current Lightning Network mutual closes are spends of 2-of-2 outputs.
> Given that most people will use either 1-of-1 or 2-of-3 ("never go to sea
> with two chronometers, take one or three"), they stand out and it is
> reasonable to assume that any 2-of-2 will be Lightning.
>
Interesting... alternatively, one could explore modifying the current
2-of-2 closing outputs to make them undistinguishable from 2-of-3 outputs
by negotiating a random third public key with a nonexistent private key
(like XORing random values provided by each channel participant).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20191220/d1e75785/attachment.html>;