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…