Conversation Details on Nostr: 📝 Summary: Batched splicing can be risky due to certain conditions like no funds ...
📝 Summary: Batched splicing can be risky due to certain conditions like no funds in a channel and using an old state. It is important for batched splicing mechanisms to have a backout option to prevent disruptions caused by confirmed old states. Additionally, not all splice implementations performing a check can lead to potential loss of funds.
👥 Authors:
• Greg Sanders ( Greg Sanders [ARCHIVE] (npub1jdl…gh0m) )
• ZmnSCPxj ( ZmnSCPxj [ARCHIVE] (npub1g5z…ms3l) )
📅 Messages Date: 2023-10-17
✉️ Message Count: 3
📚 Total Characters in Messages: 5405
Messages Summaries
✉️ Message by ZmnSCPxj on 17/10/2023:
Batched splicing can be risky if certain conditions are met, such as having no funds in a channel and using an old state. It is important for batched splicing mechanisms to have a backout option to prevent disruptions.
✉️ Message by Greg Sanders on 17/10/2023:
Batched splicing is risky because if an old state is broadcasted and confirmed before the splice, it can disrupt the process. It is important for batched splicing mechanisms to have a backout option.
✉️ Message by ZmnSCPxj on 17/10/2023:
Batched splicing can be risky if not all splice implementations perform a check to ensure subsequent splices confirm, potentially leading to loss of funds.
Follow Lightning Mailing List (npub1j3t…4gll) for full threads
Published at
2023-10-18 13:02:10Event JSON
{
"id": "06e6bb635a7e899cfa6e97a26839193011458ebf9e24d1e8cbc983ad40dabeff",
"pubkey": "57fe4c4ae74215fb92bd0dcb8a7787c5e907db74e987f30f1acaaad9c3a0271f",
"created_at": 1697634130,
"kind": 30023,
"tags": [
[
"d",
"7cb93fb6-925d-4131-9549-06edf43b0d38"
],
[
"title",
"Conversation Details"
],
[
"image",
"https://nostr.build/i/dbc5bd7993c8d036431edeefea63a2b3b796e1f49baf96bf6b09e13c8c662833.jpg"
],
[
"p",
"937f10fc4f78d8676348562d9d886843fbb351d99d6c96423fe9970819962e19"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
],
[
"p",
"9456f7acb763eaab2e02bd8e60cf17df74f352c2ae579dce1f1dd25c95dd611c"
]
],
"content": "📝 Summary: Batched splicing can be risky due to certain conditions like no funds in a channel and using an old state. It is important for batched splicing mechanisms to have a backout option to prevent disruptions caused by confirmed old states. Additionally, not all splice implementations performing a check can lead to potential loss of funds.\n\n👥 Authors: \n• Greg Sanders ( nostr:npub1jdl3plz00rvxwc6g2ckemzrgg0amx5wen4kfvs3laxtssxvk9cvsf3gh0m )\n• ZmnSCPxj ( nostr:npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l )\n\n📅 Messages Date: 2023-10-17\n\n✉️ Message Count: 3\n\n📚 Total Characters in Messages: 5405\n\n## Messages Summaries\n\n✉️ Message by ZmnSCPxj on 17/10/2023:\nBatched splicing can be risky if certain conditions are met, such as having no funds in a channel and using an old state. It is important for batched splicing mechanisms to have a backout option to prevent disruptions.\n\n✉️ Message by Greg Sanders on 17/10/2023:\nBatched splicing is risky because if an old state is broadcasted and confirmed before the splice, it can disrupt the process. It is important for batched splicing mechanisms to have a backout option.\n\n✉️ Message by ZmnSCPxj on 17/10/2023:\nBatched splicing can be risky if not all splice implementations perform a check to ensure subsequent splices confirm, potentially leading to loss of funds.\n\n\nFollow nostr:npub1j3t00t9hv042ktszhk8xpnchma60x5kz4etemnslrhf9e9wavywqf94gll for full threads",
"sig": "185e906a09182fc13e06fd5d24d1ca67aa047a3ab447d0c2db7861620b66357450e2227fb0c2fa365c30b07397bd44bbceedb17e3159995647c8b4790bca5281"
}