<oembed><type>rich</type><version>1.0</version><author_name>Lightning Mailing List (npub1j3…94gll)</author_name><author_url>https://nostr.ae/npub1j3t00t9hv042ktszhk8xpnchma60x5kz4etemnslrhf9e9wavywqf94gll</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>🔖 Title: Liquidity griefing for 0-conf dual-funded txs&#xA;🏷️ Categories: Lightning-dev&#xA;👥 Authors: &#xA;• ZmnSCPxj ( nostr:npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l )&#xA;• Bastien TEINTURIER ( nostr:npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0s )&#xA;• Matt Morehouse ( nostr:npub1zgyy2j829vn4zuvhkgza7qe37knzdls4kuwt2k8cehwpjxn9duwqv5j4mf )&#xA;🗒️ Conversation Summary: The Lightning Network&#39;s dual funded transactions face challenges in protecting against liquidity griefing attacks. One proposed solution is to never lock UTXOs used in the transactions, but this falls short when using 0-conf. Another proposal is to lock UTXOs after tx_complete exchange if the channel has only one contributor and to differentiate 0-conf channels prior to UTXO selection to avoid reusing soft-locked UTXOs. However, this may not work for splicing.&#xA;📅 Messages Date Range: 2023-05-05 to 2023-05-10&#xA;✉️ Message Count: 5&#xA;📚 Total Characters in Messages: 26852&#xA;</html></oembed>