🔖 Title: Liquidity griefing for 0-conf dual-funded txs
🏷️ Categories: Lightning-dev
👥 Authors:
• ZmnSCPxj ( ZmnSCPxj [ARCHIVE] (npub1g5z…ms3l) )
• Bastien TEINTURIER ( Bastien TEINTURIER [ARCHIVE] (npub17fj…tr0s) )
• Matt Morehouse ( Matt Morehouse [ARCHIVE] (npub1zgy…j4mf) )
🗒️ Conversation Summary: The Lightning Network'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.
📅 Messages Date Range: 2023-05-05 to 2023-05-10
✉️ Message Count: 5
📚 Total Characters in Messages: 26852
Lightning Mailing List /
npub1j3…94gll
2023-06-09 13:13:15
Author Public Key
npub1j3t00t9hv042ktszhk8xpnchma60x5kz4etemnslrhf9e9wavywqf94gllPublished at
2023-06-09 13:13:15Event JSON
{
"id": "f54bc696b16f3f7f65bfa10c63b404793b63a17ad7145030b93a2dec70764217",
"pubkey": "9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c",
"created_at": 1686316395,
"kind": 1,
"tags": [
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
],
[
"p",
"f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb"
],
[
"p",
"12084548ea2b27517197b205df0331f5a626fe15b71cb558f8cddc191a656f1c"
]
],
"content": "🔖 Title: Liquidity griefing for 0-conf dual-funded txs\n🏷️ Categories: Lightning-dev\n👥 Authors: \n• ZmnSCPxj ( nostr:npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l )\n• Bastien TEINTURIER ( nostr:npub17fjkngg0s0mfx4uhhz6n4puhflwvrhn2h5c78vdr5xda4mvqx89swntr0s )\n• Matt Morehouse ( nostr:npub1zgyy2j829vn4zuvhkgza7qe37knzdls4kuwt2k8cehwpjxn9duwqv5j4mf )\n🗒️ Conversation Summary: The Lightning Network'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.\n📅 Messages Date Range: 2023-05-05 to 2023-05-10\n✉️ Message Count: 5\n📚 Total Characters in Messages: 26852\n",
"sig": "ccfe0be0a7e20245bb75ead4f38736857b4f9d93508d5d2e1671aa449c10cb2c6c6803eee867bd30b8f11dba2603cb871374477c20e6b6c40868ef9a7026b7c1"
}