rich1.0npub1tsl0vdp4gegx6p7m073lphfl7zcrctud0qhutzf63up2h6r2kdcq99cyxzhttps://nostr.ae/npub1tsl0vdp4gegx6p7m073lphfl7zcrctud0qhutzf63up2h6r2kdcq99cyxznjumphttps://nostr.ae📅 Original date posted:2023-05-23 🗒️ Summary of this message: A discussion on the potential risks of using Lightning Network and Atomic Swap Protocol (ASP) for Bitcoin transactions without waiting for on-chain confirmations. 📝 Original message:Do you have any write up that presents a fully detailed architecture, including mechanisms like bitcoin scripts, transactions and L2 protocols, and then derives claims from that base? On Tue, May 23, 2023, 5:59 AM Burak Keceli via bitcoin-dev < bitcoin-dev at lists.linuxfoundation.org> wrote: > > As the access to Lightning is also by the (same?) ASP, it seems to me > that the ASP will simply fail to forward the payment on the broader > Lightning network after it has replaced the in-mempool transaction, > preventing recipients from actually being able to rely on any received > funds existing until the next pool transaction is confirmed. > > Yes, that's correct. Lightning payments are routed through ASPs. ASP may > not cooperate in forwarding HTLC(s) AFTER double-spending their pool > transaction. However, it's a footgun if ASP forwards HTLC(s) BEFORE > double-spending their pool transaction. > > What makes Ark magical is, in the collaborative case, users' ability to > pay lightning invoices with their zero-conf vTXOs, without waiting for > on-chain confirmations. > > This is the opposite of swap-ins, where users SHOULD wait for on-chain > confirmations before revealing their preimage of the HODL invoice; > otherwise, the swap service provider can steal users' sats by > double-spending their zero-conf HTLC. > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev at lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230523/0870c6d9/attachment.html>