I figured it out, can we just delete this? đ
Force Closing a Lightning Channel Troubles
4 replies 175 views
Seems like your force close transaction worked just fine. It's confirmed and you got your funds back. The pending transaction is likely unrelated to the lightning network issue. But hey, correct me if Iâm mistaken here.
That pending TX had a fee of 1sat/vbyte, which is way too low given the mempool situation. Most nodes probably ignored it and it'll vanish after a couple weeks unless you rebroadcast it.
No need to delete your thread just because you found a fix. This forum is all about sharing and learning, right? Your answer can really help someone else facing the same issue down the line. Makes sense to keep it up.
gwei_blockNewbie
Posts: 185 · Reputation: 37
#4Nov 27, 2021, 05:15 AM
Honestly, it's kinda selfish to ask for deletion now that you got your answer. You found a solution and just wanna keep it to yourself? Not cool.
Remember, this forum is here to share knowledge. Youâre not the only one who mightâve hit that problem. Why not share how you solved it? Others might benefit from your experience.
Appreciate the link!
So, piecing it all together, OPâs fix was ditching that local transaction from his history. That freed up a big input he used like 16 days ago.
The other input from the force-close transaction was consolidated recently. Thought it was related since that dropped transaction used it as input.
Related topics
- Proposal for Simplifying Lightning Channel Closures 6
- Setting Up a Lightning Node with Umbrel: Channel Tips 3
- Unlocking Einstein-Tiling: A Fresh Take on Lightning Network Efficiency 4
- Issues with Lightning Node Connectivity 5
- Lightning vs Bitcoin: Separate Entities 21
- Can HTLCs Prove Solvency in Lightning Network? 4