<oembed><type>rich</type><version>1.0</version><title>Rusty Russell [ARCHIVE] wrote</title><author_name>Rusty Russell [ARCHIVE] (npub1zw…hkhpx)</author_name><author_url>https://yabu.me/npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpx</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2020-02-20&#xA;📝 Original message:&#xA;lisa neigut &lt;niftynei at gmail.com&gt; writes:&#xA;&gt;&gt; With PoDLE this would not be possible I think, as you would not be able&#xA;&gt; to open the PoDLE commitment with the other node as the target (if we go&#xA;&gt; with the modified PoDLE which also commits to which node an opening is for,&#xA;&gt; to prevent the pouncing venus flytrap attack).&#xA;&gt;&#xA;&gt; Good question. It should be possible to do multi-channel open even with the&#xA;&gt; PoDLE signature committing to a node_id.&#xA;&gt;&#xA;&gt; - An initiator can use the same utxo (h2) as their proof for multiple&#xA;&gt; peers; the signatures passed to each peer will have to commit to that&#xA;&gt; specific peer&#39;s node_id, however.&#xA;&gt; - The revised PoDLE signature commitment requires every initiator to&#xA;&gt; include at least one of their own inputs in the tx. Attempting to initiate&#xA;&gt; an additional open etc using someone else&#39;s utxo&#39;s won&#39;t work (this is the&#xA;&gt; pouncing venus flytrap attack which we&#39;re preventing). The initiator&#xA;&gt; including at least one input is expected behavior, at least in the open&#xA;&gt; case, since the opener has to cover the fees for the funding output.&#xA;&gt; - Ideally, a node would remove the PoDLE TLV data from any &#39;forwarded&#39;&#xA;&gt; `tx_add_inputs` that isn&#39;t the input they&#39;re proving for, to prevent&#xA;&gt; leaking information about which inputs belong to other parties. I say&#xA;&gt; ideally here because even if you fail to do this, the peer can iterate&#xA;&gt; through all the provided commitment proofs until one of them&#xA;&gt; matches/verifies with the upfront provided PoDLE.&#xA;&#xA;Yes, you need to PoDLE your own contribution I think, which means you&#xA;need one UTXO per contributor in the N-way-open who you want to&#xA;contribute a UTXO.&#xA;&#xA;Consider Alice trying to create a single-tx to open a channel with both&#xA;Bob and Carol, and wants *both* of them to also contribute.&#xA;&#xA;Alice sends her own UTXO1 with proof to Bob, he shares his UTXO back.&#xA;Alice sends her own UTXO2 with proof to Carol, she shares a UTXO back.&#xA;Alice sets the lower bit on the serial_id from Bob and sends to Carol,&#xA;and sets the lower on the serial_id from Carol and sends to Bob.  She&#xA;similarly reflects everything from Carol to Bob and vice-versa, and&#xA;sends both of them the two &#34;channel opening&#34; outputs.&#xA;&#xA;Now all parties have the same tx; unless Bob and Carol chose the same&#xA;serial_ids (spec says random, but Bob and Carol don&#39;t get along).  But&#xA;this is trivially identifiable, and you give up on mutual opening.&#xA;&#xA;Cheers,&#xA;Rusty.</html></oembed>