📅 Original date posted:2023-05-07
🗒️ Summary of this message: Dual-funded 0-conf can be made safe if the initiator uses swap-in-potentiam addresses, allowing for immediate transfer to a 0-conf Lightning channel.
📝 Original message:
Good morning t-bast, and list,
Dual-funded 0-conf can be made safe in the following case:
* If the initiator uses swap-in-potentiam addresses (with initiator as Alice, acceptor as Bob).
If the initiator stalls, then the acceptor can retaliate by refusing to sign the swap-in-potentiam UTXOs forever after that, thus also locking their funds until the swap-in-potentiam times out, thus preventing this liquidity griefing from being cost-free.
The expected use-case is that a user expects onchain operations to be slow and take multiple confirmations to receive.
Once there is deep confirmation that a swap-in-potentiam address has been funded, then it can be transferred immediately to a 0-conf Lightning channel.
The initiator still needs to trust that the acceptor does not double-spend out from under the initiator, but see LSPS3 Promise To Unconditionally Fund 0-conf.
Also, it looks like you are allowing for the initiator to trust the acceptor in that case, as I believe you are taking the point of view of the acceptor of the dual-funding flow.
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5…3ms3l
2023-06-19 17:42:18
in reply to nevent1q…evz3
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-19 17:42:18Event JSON
{
"id": "cd7ec5d2feb5f52d88b191f9f453215a70cabe48263edd9c493d099d233d017a",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1687196538,
"kind": 1,
"tags": [
[
"e",
"acdedd1cfdb5604088e466488dc51cd5e92cb63586d3ce388a785b5474fec1d1",
"",
"root"
],
[
"e",
"d76b80cfcc678610d22f30058acb125084699d7bed77d0dc91a761dd7802c23f",
"",
"reply"
],
[
"p",
"f26569a10f83f6935797b8b53a87974fdcc1de6abd31e3b1a3a19bdaed8031cb"
]
],
"content": "📅 Original date posted:2023-05-07\n🗒️ Summary of this message: Dual-funded 0-conf can be made safe if the initiator uses swap-in-potentiam addresses, allowing for immediate transfer to a 0-conf Lightning channel.\n📝 Original message:\nGood morning t-bast, and list,\n\nDual-funded 0-conf can be made safe in the following case:\n\n* If the initiator uses swap-in-potentiam addresses (with initiator as Alice, acceptor as Bob).\n\nIf the initiator stalls, then the acceptor can retaliate by refusing to sign the swap-in-potentiam UTXOs forever after that, thus also locking their funds until the swap-in-potentiam times out, thus preventing this liquidity griefing from being cost-free.\n\nThe expected use-case is that a user expects onchain operations to be slow and take multiple confirmations to receive.\nOnce there is deep confirmation that a swap-in-potentiam address has been funded, then it can be transferred immediately to a 0-conf Lightning channel.\n\nThe initiator still needs to trust that the acceptor does not double-spend out from under the initiator, but see LSPS3 Promise To Unconditionally Fund 0-conf.\nAlso, it looks like you are allowing for the initiator to trust the acceptor in that case, as I believe you are taking the point of view of the acceptor of the dual-funding flow.\n\nRegards,\nZmnSCPxj",
"sig": "a6f1b996a9297dbb921169e52ce134ab4d4e8c02bd24f19dc933b51ab4c488d646d32a1dfa132b2731c4b6eae8267f84dee0470fe374aa6f3a6f9afaaaa14a10"
}