matt on Nostr: Checked looks like the node is working just fine. Can you share more about why your ...
Checked looks like the node is working just fine. Can you share more about why your channel “wasn’t able to be closed cooperatively”? Usually that’s because of a feerate disagreement that causes a force-close (new protocol changes to address this coming to a node near you soon!), not (to my knowledge, from any implementation) “lost data”.
Published at
2025-03-09 01:35:56Event JSON
{
"id": "ab5ebbd7bfc3a6d7c764cf87afdfe0b235d7bc1ba47b86ecf13350c8161e5330",
"pubkey": "3d2e51508699f98f0f2bdbe7a45b673c687fe6420f466dc296d90b908d51d594",
"created_at": 1741484156,
"kind": 1,
"tags": [
[
"e",
"6626512fe6e6351d6a01df55339e7cf5cf95e9ecd7e73bee8836ece90d4c51c3",
"",
"root"
],
[
"e",
"5af9db9c344c9bb8fdcbe534a978f2da4624ff417697b09552d7df81f7cc580c",
"",
"reply"
],
[
"p",
"9a39bf837c868d61ed8cce6a4c7a0eb96f5e5bcc082ad6afdd5496cb614a23fb"
]
],
"content": "Checked looks like the node is working just fine. Can you share more about why your channel “wasn’t able to be closed cooperatively”? Usually that’s because of a feerate disagreement that causes a force-close (new protocol changes to address this coming to a node near you soon!), not (to my knowledge, from any implementation) “lost data”.",
"sig": "45699a1f6a399bfd7aa0db4b097c1e93776241a0df170a4a40245852b6b51cea89497928d46c510906e87d63f34f1dc5d2524f09f4b7c2c94f645e98978f921d"
}
