🔖 Title: Proposed changes to the splicing specification
🏷️ Categories: Lightning-dev
👥 Authors:
• ZmnSCPxj ( npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l (npub1g5z…ms3l) )
• Dustin Dettmer ( npub1x54n25utwk7dzwzvk2v0aknptez5gxdwcyrxx2wgc0lnhgvwu72qmkqsqu (npub1x54…qsqu) )
• Antoine Riard ( npub1vjzmc45k8dgujppapp2ue20h3l9apnsntgv4c0ukncvv549q64gsz4x8dd (npub1vjz…x8dd) )
🗒️ Conversation Summary: Developers discuss challenges with implementing 0-conf splicing in Bitcoin's Lightning Network, including double-spending risk. Swap-in-potentiam addresses provide implicit protection against this risk. Proposals have been made to protect against double-spend risk during splice-in and channel factory construction. A proposal for simplifying and improving the splicing protocol has also been shared.
📅 Messages Date Range: 2023-04-03 to 2023-04-04
✉️ Message Count: 4
📚 Total Characters in Messages: 18184
