Decommissioning Lightning node PaulsCode [migrating to LND]

Bitcoin
1

After some considerable thought, weighing the pros and cons, I have decided to no longer try and maintain my Core Lightning node (formerly known as “PaulsCode”) due to the significant issues with Core Lightning on various fronts, including stability, routing, and re-balancing functionalities, compared to LND. I will instead be moving to a more sustainable architecture that relies primarily on my LND node (currently called “PaulsCode LND”). I apologize in advance to the significant number of folks who have opened channels with my Core Lightning node, but it is just becoming a time sink to maintain. The new architecture will not only make things easier on my end, but those who are depending on channels with me will have a more reliable experience as well.

I have begun the process of spinning down my Core Lightning node, which I expect will take several weeks to complete. If you have a channel with my node, I will check the publicly available details about your node before deciding how to decommission your channel. If my node is the only one you have a channel with, I will attempt to create a new channel from my new node before closing the old one, and re-balance it so that it is at least close to the same inbound/outbound ratio that your current channel has. If I run into any weird errors while trying to open the new channel or re-balance, I will simply close your current channel. If it appears that your node has other channels that you can leverage (or if you already have another channel with my LND node), then I will simply close your channel to my Core Lightning node.

I have renamed the node that is being decommissioned as “PaulsCode [migrating to LND]” and I have set the minimum channel capacity for new channels very high so that no new channels are opened with it. If you prefer to get a head-start and help out with the decommissioning process, then feel free to close your channel with my Core Lightning node and create a new one to my LND node. Sometime in the future I will rename “PaulsCode LND” to “PaulsCode”, so that it is obvious that it is my primary node.

3 Likes
2

I’ll have to follow your progress as Core Lightning is not really playing nice for me. I’m going to make an assumption that the info in RTL, channels, peers, onchain, etc. is either derived from CL or LND. One I get my head around who TRL operates with the channels I’ll have more confidence in what I’m doing.

I have one liquidity channel I committed to though so don’t know how I can maintain the relationship via LND. I committed for 12 months.

BTW - I do have your LND channel active but balancing is impossible (with my current knowledge).

Thanks for the heads up.

1 Like
3

I’ll record a video about setting up the configuration that I’m migrating to. The video will start from scratch, though, so much simpler than migrating from an already established, less optimal configuration. The basic setup is two lightning nodes: Core Lightning with one small single channel opened from LND, where LND is the main player with all the channels out to the broader network. Core Lightning is only used for accumulating mining rewards in this setup (since LND doesn’t yet support Lightning Offers)

3 Likes
4

Guess I’ll be following suit as i a single CLN channel but have struggled to get my head around that side of things

5

Ok… I’ll be looking out for the video. As mentioned I’ve got the single channel open on CLN for the Ocean Bolt12 offer. So what your say is spin up an LND node and create the channel from there to CLN.