170 sats \ 3 replies \ @zapomatic 16 Dec 2023 \ on: Etiquette for closing channels? lightning
I think we are heading into a time where node operators are going to require more external communication from other nodes. Rather than treating all nodes that connect as the same, ones that have prearranged connections and operating standards will get preferential treatment and flow policies. Anyone blindly connecting without a published way to communicate could be at risk of getting closed.
I had an issue where someone who recently connected to me appeared to vanish (the edge was no longer found in mempool.space or anywhere else). They restarted tor, and, I think, added me as a peer via clearnet, and they came back as a connected node and the edge resolved. This resolution came after I emailed them because they had an email published on amboss.space.
In a case like yours, if I were the other node in the situation, I would hope we would have a communication channel open (DM, email, or keysend) so that I could address the performance issue before being closed.
But if they are anon and have no comms method... then I'd say the whole relationship is a liability.
Even though it's far from trivial, I (have to) assume that my peers are interested in the channel and care about its performance. Basic information like liquidity distribution and number of transactions is available even to the most inexperienced node runner, and tools exist that provide more detailled information. With over 100 peers I can't reach out and discuss basics everytime I want to access my sats.
reply
That's fair. How often are you in this situation? Are you normally closing multiple channels per day? or is this like a once a week finding a channel that isn't doing great kind of event?
I don't see anything wrong with you closing the channel (though it sucks for the recipient). It is your right as a node and nodes opening connections to you are signing up for the risk of channel closing cost. I haven't connected to you (yet) for instance because I know my node doesn't have enough balanced liquidity and performance to do the relationship justice. If I had a connection to you right now, in the state of things, I wouldn't be outraged if you were to close the channel since it would be my operational bad that got me into the state of malperformance.
But also, things happen and not everyone is professionally managing their node--maybe that's a reason not to connect to nodes that are more serious (if you can't take the heat, as they say)...
reply
I'd say it happens roughly once a week, although I have a bit of a backlog right now.
reply