OK, this is now sorted. For those curious, my LN anchor TX got RBF-ed into an anchor consolidation TX (part of the protocol apparently), but that TX was not in my mempool (300MB) and so LND wouldn't let me spend my output in the parent TX.
So, I increased my mempool memory, waited for it to sync (which took a while) and then boom, it appeared. LND restart and the 'stuck' TX is now spendable.
LN is a beast.
Thx to ziggie (npub1l5u…aap5) for the insight and helping get my sats unfucked!
Nathan Day
npub1cn…jwt8a
2024-04-18 16:56:05
in reply to nevent1q…w3c0
Author Public Key
npub1cn670f663n3ks02jnnlsvd5y88zjnefy8343ykaxs7y3nzzketrsrjwt8aPublished at
2024-04-18 16:56:05Event JSON
{
"id": "8ef14207e4471c39f1c8d47d5a9fa9a6fbb3467a4e26d636077cf28fb5b0de46",
"pubkey": "c4f5e7a75a8ce3683d529cff06368439c529e5243c6b125ba68789198856cac7",
"created_at": 1713452165,
"kind": 1,
"tags": [
[
"p",
"fd38f135ef675eac5e93d5b2a738c41777c250188031caf1dcf07b1687a1fe49",
"",
"mention"
],
[
"e",
"94f68f229a33dbc5fc245208500704f4d430b4560c4417c25fc47b0b6f4e62b5",
"wss://nostr.einundzwanzig.space",
"root"
],
[
"p",
"c4f5e7a75a8ce3683d529cff06368439c529e5243c6b125ba68789198856cac7"
]
],
"content": "OK, this is now sorted. For those curious, my LN anchor TX got RBF-ed into an anchor consolidation TX (part of the protocol apparently), but that TX was not in my mempool (300MB) and so LND wouldn't let me spend my output in the parent TX.\n\nSo, I increased my mempool memory, waited for it to sync (which took a while) and then boom, it appeared. LND restart and the 'stuck' TX is now spendable.\n\nLN is a beast.\n\nThx to nostr:npub1l5u0zd00va02ch5n6ke2wwxyzamuy5qcsqcu4uwu7pa3dpapleysf7aap5 for the insight and helping get my sats unfucked!",
"sig": "3612dab8cec7b16d578578c8b9213ae2e72d57ac49df86d8ca55f3e500e58985b7049c1adadf74dc3f74d6242d0d64c941f51fa310928c378c64a203040e08fd"
}