Re: [Lightning-dev] PoDLEs revisited

2021-02-02 Thread Lloyd Fournier
On Fri, Jan 29, 2021 at 10:51 AM Rusty Russell wrote: > Less true after taproot though? > The heuristic from [1] is not affected by Taproot. Taproot will be helpful for keeping private channels private against the method in [2] though. > [1] https://arxiv.org/abs/2007.00764 > > [2] https://arx

Re: [Lightning-dev] PoDLEs revisited

2021-01-28 Thread Rusty Russell
Lloyd Fournier writes: > I think immediate broadcast of signaling TX is a bad idea even if it's done > over lightning since it leaks that the UTXO associated with the signaling > TX is creating a channel (even if the channel was meant to be private). > You could argue that the signaling TX need no

Re: [Lightning-dev] PoDLEs revisited

2021-01-27 Thread Lloyd Fournier
On Wed, Jan 20, 2021 at 12:34 PM Rusty Russell wrote: > > > Yes, sorry. I assumed immediate broadcast + 60 second wait for > conflicts. It's this scheme I was trying to shoehorn into the mempool > (broadcast signalling tx, wait, try to RBF it with a real open). But > there are three problems w

Re: [Lightning-dev] PoDLEs revisited

2021-01-19 Thread Rusty Russell
Lloyd Fournier writes: > I think PoDLE might actually have an advantage in parallel attacks if the > scheme was changed a bit. A weakness of the lightning proposal as compared > to the joinmarket idea is that the `h2` point is not broadcast immediately > -- rather you wait for failure and then bro

Re: [Lightning-dev] PoDLEs revisited

2021-01-14 Thread Lloyd Fournier
On Wed, Jan 13, 2021 at 11:54 AM Rusty Russell wrote: > Lloyd Fournier writes: > > Rusty, Zman, > > > > A concern I have with only doing one signaling transaction out of the > whole > > group of inputs is that it means you don't prove ownership of the other > > inputs. > > But that's by design.

Re: [Lightning-dev] PoDLEs revisited

2021-01-12 Thread Rusty Russell
Lloyd Fournier writes: > Rusty, Zman, > > A concern I have with only doing one signaling transaction out of the whole > group of inputs is that it means you don't prove ownership of the other > inputs. But that's by design. You can contact two peers and middleman between them to produce a single

Re: [Lightning-dev] PoDLEs revisited

2021-01-08 Thread Lloyd Fournier
Rusty, Zman, A concern I have with only doing one signaling transaction out of the whole group of inputs is that it means you don't prove ownership of the other inputs. I am not exactly sure what you could do by adding inputs from the chain you don't own but it does feel a bit risky. Perhaps it wo

Re: [Lightning-dev] PoDLEs revisited

2021-01-07 Thread Rusty Russell
Lloyd Fournier writes: > This achieves all properties except for (4 - distinguishable on-chain) > which is why it was dismissed. It also seems to require 2 txs per channel open? (Interestingly I missed that post previously, thanks for the pointer!) > I think it is possible to extend the idea to

Re: [Lightning-dev] PoDLEs revisited

2021-01-05 Thread ZmnSCPxj via Lightning-dev
Good morning LL, and happy new year as well, > # Signaling Transactions > > Finally I present a simple but unintuitive protocol that achieves roughly the > same properties as the PoDLE protocol but without lightning gossip messages. > > Whenever the initiator adds an input in the interactive tx

[Lightning-dev] PoDLEs revisited

2021-01-03 Thread Lloyd Fournier
Happy New Year Lightning Developers, I've recently been closely looking at the dual funding proposal [1] because it uses a DLEQ proof (PoDLE) which we are also working on specifying as part of DLC ECDSA adaptor signatures [2]. While reading it I had some queries and ideas that I thought were worth