Hopefully its simple. The answers I’ve seen in some threads look hopelessly complicated. Have mercy, I’m an old guy. The last transaction I received was July 4th from a Bolt 12 offer, I’m guessing thats the day I lost the channel. I see the history of sats received, but the UI currently indicates that there is no channel open. I had a single million sat channel open with Megalith.
@DarthCoin instructions look like they’re specific to LND. Anybody able to help with Core? Heres the node ID: 03a4099179058d64158eddf7a5639984ca9ec9fc41981f204b934de7f86da791b0@dqtavr3rpnzycmfgc3s77qx5fad5avx2wudzhrdjtmmmtohpv5agkaqd.onion:9735
You channel was cooperatively closed and everything is accounted fine. https://node204.tk7.mempool.space/lightning/channel/975013926218432512
Megalith has been doing some cleaning. Your channel was among 19 others closed by him at the same moment. Many “managed” routing nodes do that if they consider your channel underperforming and have meaningful share of liquidity on their side.. If you want to keep channel with infrequent or low value traffic long term, maybe try different peers. For example bfx0+1 and nicehash are known to not close inactive channels for years and yet are very well connected and with reachable crew, but the catch with such peers with unmanaged liquidity is that if you need any kind of manual help from them, it may be a challenge to get that intervention which you need..
Btw it’s not my business to judge, but do you use this LN node for more then just collecting micro rewards from Ocean, right? For receiving few sats via bolt12, custodial coinos.io would work fine too and on average might even be less risky (compared to beginners running CLN instance)..
Thank you for the explanation and the suggestion! Is there a place I can look to confirm for myself that info? How do I look up the current state of a channel?
Your +210646 “deposit” is matching one of the outputs obvious from my earlier mempool.space link, but internally you can query all the details you need via command line.. #fyi I don’t actually run umbrel anymore so not sure if this is the current correct docker exec prefix..
