Ta dar!
Thanks… the steps on the vid really opened up due to my increased familiarity through numerous failed attempts.
Bitcoin is a thing and the folks building stuff have really got us covered. I now see the significance of the seed phrase and I bet that’s just the tip of the cryptographic iceberg.
Channel Management
I’ve created a public channel between my CLN and LND nodes and created liquidity within it for Ocean payouts. I’m set to receive my first payout at some point now the Bolt12 offer has been set up.
I’m a bit worried because the channel constantly shows ‘offline’ at both ends. Not sure what to do if anything?
You could try restarting the services to see if that helps. Simple test of the connection would be to create an invoice for a few sats on the CLN node, and see if you can pay it from the LND node. If that works, then we can test if the broader network can reach you (create a small invoice from your CLM node, say 100 sats, and send it to me and I’ll see if I’m able to pay it).
Classic… have you tried turning her off and on again!
So, I restarted from the LND end (couldn’t see any restart option on CLN), both ends lit up and the Ocean payment came through… like boom!
But…
I couldn’t figure how to get the sats into my CLN Lightning wallet and then the offer timed out!
Could see it RTL but have no clue what action is required for the offer to be paid? Both the attached are snaps from RTL
Technically speaking, it is the individual invoices which expire, not the offer. They expire when they are not paid by some expiration date.
The interesting note is that Ocean reports no connection to your CLN node. The most likely cause for this that I can think of would be if you made the channel between your LND and CLN nodes a private channel instead of a public one (which would result in there not being any gossip data for Ocean to be able to construct a route) There is a way to add hints to normal lightning transactions when you want to use private channels, but I don’t know how to extend that capability to offers. I think you need public channels for offers to work.
If your channels are public already (and not private) then the next thing to look at would be liquidity. In the above example, you would need 50,100 sats of inbound liquidity into your LND node from the larger network, and 50,100 sats of inbound liquidity into your CLN node from the channel with the LND node. I couldn’t see what is the inbound/outbound ratio on your channels from any of the screenshots you posted. Could you let me know what those ratios are for each of your channels? You probably already understand this, but for reference, inbound means the sats are on your side of the channel, and outbound means the sats are on the other side of the channel.
Noted re the difference between the invoice and offer. I was helplessly watching this invoice expire!
The channel is public with a total capacity of 150,000. I can see it’s as you’ve said, insufficient liquidity LND end? If I’m understanding it correctly, LND inbound is a few sats shy of the required 50,100. CLN end looks ok at 98,000 inbound?
Is it a case of send 50,000 out of LND?
Yes, that is definitely a problem. Send some sats out of that VIOLETBEAM chanel to open up more inbound liquidity. You’ll need a place to send to (another Lightning wallet, Boltz.exchange, Aqua or other Liquid wallet, etc). Then wait for Ocean to mine another block and see if the rewards come in this time.
BTW, depending on how much hashrate you are running, if you frequently mine 50K sats at a time, you will likely have to watch the channels on a regular basis and move sats to keep things flowing. When the Kush channel in CLN fills up, just create an invoice in LND and pay it to your self from CLN. And when the VIOLETBEAM channel fills up, send up more out from there like you are doing this time.
I found since my payouts expanded so much and OCEAN’s own lightning routing on their side breaks at times the delay in payouts could be up to 200,000 sats. It’s happened a few times in the last month alone.
I ended up opening a total of 3 channels from LND to CLN totally 350,000. But even with that room I still have to move sats out of CLN on a regular basis. On the LND side I added a large channel (1,000,000) with Megalith LSP . Purring like a kitten. 
Ok, I’ll send some sats out as advised and wait the next Ocean block.
Understood re monitoring the Ocean rewards; the process for creating liquidity in CLN via LND and then out to another wallet as required.
Much thanks
Ta for the heads up. I can see how easily the sats stack so they outstrip the liquidity created.
I hear you. I guess getting my head around managing a single payment channel will contribute to creating and managing a channel or two on the wider network
Well… I can’t find a route out of VioletBeam for neither love nor money! Tried sending 50k Lsats to Blockstream, then Aqua but ‘unable to send lightning payment: no_route’. Then tried 50k straight up sats to Blink but again ‘no_route’. Is it me?
Try increasing the maximum fee rate. 2% usually works, and 4% will definitely work if there is enough liquidity out of the node you have a channel with.
Appreciate your time on this…
Wow and well… I found this on the LND under Advance Setting
Then the current fee setting on RTL
Then the option to update policy on RTL
And finally the actual options on RTL
Is this where I make the changes?
It looks like VIOLETBEAM has only one channel (with you), so there is no path in or out from the broader Lightning network if that is the only channel you have on LND.
Wait, Kush also only has one channel listed (with VIOLETBEAM). Is VIOLETBEAM your CLN node? If so, you will need to open another channel from your LND node with some other node which is well connected with other nodes on the network.
I opened a channel with your LND node, transaction ID: e6cf1d3fab79acdfe14175f8207cd07a85fad456e09c803a2c8002e817bc8f66
Once it gets a couple of confirmations, you’ll have some inbound liquidity. Let me know if Ocean still has a problem sending the payouts.
