zax_cloud on Nostr: It’s a force close. Could be due to HTLC on expire, could be one side publishing an ...
It’s a force close. Could be due to HTLC on expire, could be one side publishing an old state. It’s often automated by the node software, and not a conscious human actions. It happens. State gets corrupt, node tears down a channel to restore a known state. I have had several, out of my control, costing me lots of sats :-(
This all demonstrates the lack of sustainability of Lightning. The bleeding of sats will continue until the spam goes away. The fact some morons can break Lightning for $60 worth of jpegs shows you this tech isn’t working as expected
Published at
2023-12-19 15:37:04Event JSON
{
"id": "0a58373cc3e7fbcb0c22b2ded79f73df4513c9628e978a1c3446b63032e8ddc9",
"pubkey": "4355759457e9098267b66e666fcd27de5fef663f3543303e13d2eb0a0326b86f",
"created_at": 1703000224,
"kind": 1,
"tags": [
[
"e",
"96687c3074b6589e92ab95a3c50189dd442ce1e2faaf966c9fb751ecb03f9b3b"
],
[
"e",
"e53502220ad0ed2c429f984cb93377e33b4b379514bc08afde70772deee2f194"
],
[
"p",
"d1665cf52f5a9f27cf29703e05cc180c09b52aca9bb598af2c58c63e572bf387"
],
[
"p",
"0d06480b0c6e3be3c9a1a65d7e6bc2091227d55bf4c77eeb6037ba7776c300ec"
]
],
"content": "It’s a force close. Could be due to HTLC on expire, could be one side publishing an old state. It’s often automated by the node software, and not a conscious human actions. It happens. State gets corrupt, node tears down a channel to restore a known state. I have had several, out of my control, costing me lots of sats :-(\n\nThis all demonstrates the lack of sustainability of Lightning. The bleeding of sats will continue until the spam goes away. The fact some morons can break Lightning for $60 worth of jpegs shows you this tech isn’t working as expected",
"sig": "a3db40deb4497118b76f0009be500b319d7055cfa5cccb1b717c8d24982b2248d7b764c1e28125e188cd08e3d25cb59e4f2e8e4f0dce43d2a8044b8175dc2233"
}
