Thank you for that explanation. It makes much more sense to me now. I had also watched BTC Sessions tutorial, and understand now why there’s an issue here. I also saw your Boltz Exchange action- would that help in this case? Or could I put more BTC into my CLN and open a larger channel to a larger partner?
Yes, that is another option if you have the sats to spend. A good node to connect with is ACINQ, which last I checked has a minimum channel capacity of 1 million sats. If you open a channel with them, you would then send most of the 1M sats (minus the minimum balance) back to cold storage via Boltz. Depending on ACINQ’s liquidity, you might have to break it into multiple pieces (such as two 500K chunks or four 250K chunks) if they aren’t able to route the full 1 million in a single bite.
If a million is a bit high for you to put into lightning now, I can also set up a virtual meeting to walk you through setting up a Core Lightning to LND link if you’d rather go that route. It would probably be easier than reading my wall of text above, haha.
1 Like
One other thought- could i send/gift you, for example, 10,000 sats directly? Would that avoid routing fee issue and give me some inbound liquidity? If not, I’m not opposed to the 1M sat option you mentioned above, and yes, I realize i’m going through a lot to just mine a few sats on a Bitaxe with Ocean. But the lightning fees and gifted sats are a small price to pay to learn and teach my kids about the future of money.
1 Like
I can open a channel with you (which will show up as 100% inbound liquidity on your side). No need for the 10K sat payment (I’ll collect routing fees over time if it works). What is the name of your node?
My Node ID is 03e7d6e4507881cb416194cb0cf76b9bebbea52f5083af1e44c998a33cdb8a2146@5e56sfil45v3wyvtnbwgtsygnra3djp2qrgcwmroa5auybs3pbt7h6id.onion:9735
Is that what you need?
1 Like
Channel should be active.
Excellent- I do see it in my CLN connections now. Thank you!
I’m guessing it will also benefit you and us if we open a number of public channels between us thus generally contributing to Lightning payments routing and specifically earning fees alongside Ocean hashing payouts
Yes, in general, the more channels there are on Lightning, the stronger and more reliable and decentralized the network becomes. You do have to weigh that with the fact that a Lightning node is essentially a hot wallet. Being on a dedicated server with a niche OS like Start9 helps of course, but you should always approach it from the perspective that you do not want to have more sats tied up in Lightning than you are able to lose in the worst case scenario of your keys being hacked.
Since Core Lightning has routing issues in general, though, I would recommend actually not putting too much effort into building out your Core Lightning channels (at least for now, until they improve their software). LND is way more reliable, and is where I would recommend focusing as you start to build your expertise in Lightning, presence on the network, and using Bitcoin as a medium of exchange. One way you could have the best of both worlds, though, would be once you have your LND node up and well connected, set up a channel from it back to your Core Lightning node. The more folks who are able to eventually reach that level, the less pressure there will be on my main channels. Like I mentioned, though, I’ve got the fee rate high enough for it to be manageable, so this is certainly not any sort of imperative.
1 Like
Ok. As mentioned I’m running the Umbrel Home off the shelf server so can load LND from their App Store. Just checked to confirm it can run on Knots. I’ll aim to set up 3 x 25,000 sat channel. Also I’ve got a 200k ‘private’ channel open with ACINQ on CLN. Seems like a waste of a route sitting there for use with Ocean Bolt 12 payouts for Bitaxe hash which won’t touch the sides of it. Can’t see how to make the channel public. I’m guessing it will be a case of closing it as and when I’m confident with LND?
Yes, that is what I would do. Get things going well with LND, then close the channel. Once the closure finalizes after a number of confirmations, you’ll be able to move the funds from that channel out of the base layer wallet for other purposes.
Ok. Also I had a look at Electrum and Sparrow. I’ve loaded Sparrow but not set it up as yet. If I’m going with LND, should I just focus on their Lightning wallet?
Hi Paul- I’m looking in CLN, and I see that on May 29, I had a withdrawl from my Bitcoin wallet of 100,369 sats, and on June 13th, a deposit of 99,849 sats, and now the channel with PaulsCode is not there (which I had established with 100,000 sats). Did you close it, or did something on my end cause it to close? No worries if you needed to close it- just trying to understand the mechanics of all this. I still see my connection to PaulsCode LND, and i’m still able to receive the Ocean payouts.
Yes, I am in the process of migrating over to use my LND node only (it is more stable and easier to manage). I posted another thread about it here, for more information: Decommissioning Lightning node PaulsCode [migrating to LND]
Excuse my ignorance. In the client list of the Datum gateway there is a column called RemHost. My brain says Remote Host but not sure. I see other examples from screen/video that the filed is an external IP outside local network. My gateways has these characters in front of the IP:… ::ffff: while others don’t.
The gateway works as expected but what are those characters?
You are correct, RemHost = “Remote Host”
That column is simply showing you the IP (or hostname) of the client that’s connected.
The ::ffff: prefix is the IPv6 “IPv4-mapped” notation. Modern TCP/IP stacks often speak IPv6 internally, even when clients connect over IPv4. To represent an IPv4 address in an IPv6-only API, they put the IPv4 bits in the low 32 bits of an IPv6 address, with the high 96 bits all zero except for a 0:0:0:0:0:ffff marker.
So if you see something like:
::ffff:203.0.113.47
that’s really just the IPv4 address 203.0.113.47 “wrapped” in IPv6.
:: is shorthand for “lots of zeros” in an IPv6 address
ffff: flags that the next 32 bits are actually an embedded IPv4 address
the dotted-quad that follows is the original IPv4
No need to worry - your gateway is still talking IPv4, it’s just reporting it via the IPv6 API. Technically, there is probably a way to force the daemon to listen only on an IPv4 socket, but functionally there’s no difference here.
1 Like
Thank you very much Paul. 
I’m sorry if this is the wrong place to post…I tried looking for your video Mining Bitcoin at Home with Datum and Start9 you posted but I didn’t see it here in the forums?
Any who…since I re-adjusted Core Lightning channels OCEAN seems to have a problem paying out. I wonder if creating a new payout invoice if I broke something? BTW - payout is over 15000 sats at the moment but wont come in.
I see this:
Should I re-setup the OCEAN payout again? Thoughts?
That is an odd one. I assume you have sufficient inbound liquidity on a public channel with a node which itself has sufficient inbound liquidity with the larger network. I suppose another thing you could try is just shutting down Core Lightning and starting it back up in case something silently crashed. Otherwise, may as well try creating another offer and repeating the singnature, etc.
Thanks for moving to correct area. Yes…Ill shut down core and restart and work forward from there.
Thank you
ps - interesting…it worked but wow…channel balance should not have moved so much in CL. Like I told @Fletcher I need to capture screen shots and watch changes…