pull down to refresh

Hello lightning users,
I've been trying to receive my Ocean payouts using a node on my Start9. I have 3 private channels with large nodes, Receiving / sending liquidity split at about 50/50. All signs point to it should work. In the past, I had a core lightning node that worked but it had public channels.
I want to do this with, ideally, my LDK running through albyhub. I can configure the bolt 12 offer successfully on Ocean, but so far I get an error from the Ocean side saying it can't find a route to my node. I also spun up a core lightning node with a few small channels and had the same problem too.
I've tried contacting Ocean, but so far they don't answer...so crowd sourcing here, seeing how other people's experience has been getting payouts to work with their own node. Are you successful with the type of setup (small, balanced node with private channels only) ?
91 sats \ 7 replies \ @k00b 27 Sep
A few things that come to mind:
  1. there might be an issue with your bolt12 and private channels
  2. there are known incompatibilities between bolt12 for different lightning implementations
  3. OCEAN might be suffering liquidity problems and not you
@alby might know more
reply
Maybe it is Ocean liquidity. They haven't paid out since 9/23,and have hit 6 blocks since then.
reply
135 sats \ 3 replies \ @carter 28 Sep
im getting ln payouts to a coinos account
reply
Interesting. It must be my node, then. Maybe someone else running their own node can chime in? I'll check my logs.
reply
Can you describe your settings in more details for the rest of the class? :-)
reply
121 sats \ 0 replies \ @carter 28 Sep
not sure what else to share while not doxing my address
I did the bolt12 on coinos with the string they gave me, signed it and it was accepted. Now on the stats I see its set to get ln payments. One of the first days this happened
I sent and email but then a few hours later it seemed to retry and i got double the payout so i figured it just failed. Its done it one other time so 2 total rpc timeouts but none since then
they show inactive most of the time unless there was a burst of shares recently
reply
Could be. I have gotten payouts to coinos configured wallets. Maybe i should open a channel to coinos 🤔
reply
Yes it could be any of these...just hard to know without feedback from Ocean. I can understand if its not high on their priorities so...here I am :)
I will say I can receive when sending to my configured offers using other sources like phoenix wallet and coinos. And I can receive my lightning payouts using coinos. But would just really like it to work with my LDK node.
reply
I haven't successfully configured the bolt 12 offer yet.
I'm trying to receive the payments to my Alby Hub and bolt 12 support is a new feature for them. It doesn't seem to be set up exactly the way Ocean expects. Or, I'm just doing something wrong, which is highly probable.
reply
Are you using the built in LDK light node? I wonder if @BeeRye is using that too? I don't think so, based on his replies.
reply
I am attempting go use the ldk light node, but also having errors configuring with a cln too. Im gonna try adding a public channel to each, see if that helps.
reply
Meanwhile, I just opened a bigger public channel on my cln node, since it looks like I might be having liquidity issues. I'm not sure though. It's puzzling, because the logs don't show failed transactions, but obviously on coinos everyone is getting paid out.
reply
ya, its hard to troubleshoot without Ocean providing feedback.
reply
I just got my back payments in one lump transaction.
reply
alright i have a new public channel open with coin OS on my CLN. I'll see if the sats are able to successfully get sent to me via lightning over the next day or so.
I wonder: Is a bolt12 offer static with the channels you had when creating it ? Wonder if I need to configure a new offer now...
reply
I'm sure someone will eventually post a guide for this or an update will make it more obvious how to do it correctly.
reply
@BitcoinMechanic said this during his AMA. It may still apply:
LND is not functional as they still don't support BOLT12. Yes, requires CLN until the ecosystem (cough LND) finally starts using BOLT12. (Phoenix would work but they don't support descriptions yet, but working on a workaround for that).
Descriptions may be the issue.
I never have problems with CLN bolt12 on my start 9 connected directly through the GUI.
Good luck.
reply
Oh, can I ask if your CLN has public channels, private channels, mix of both ?
reply
I had private channels initially, but had liquidity issues. Now I run CLBoss with a few large public channels.
reply
Thanks!
reply
It might be worth experimenting with a minimal public footprint just to confirm if the routing issue disappears. That will tell you whether it is a network discovery problem versus a configuration problem with LDK or Ocean.
reply
Good point, i think that will be my next step, is a public channel on the LDK node
reply
Is this the error you get?
OCEAN lightning payout error:

Latest Error
Latest lightning error: No route found

Raw error: cln err code: `210` - message `Ran out of routes to try after 1 attempt: see `paystatus``

Recommendation: No payment route available. Wait or contact lightning@ocean.xyz after one week

Encountered at: 2025-09-22 17:20:04 UTC
reply
55 sats \ 2 replies \ @bataroot 20h
It's working now. Just got my lightning payout.
reply
nice! and what's your setup ? CLN with private channels, public channels, mix private/public ? If you are willing to disclose.
reply
10 sats \ 0 replies \ @bataroot 8h
Simple coinos custodial setup, when I started that was the only way to accept BOLT12 without running your own node (as I had issues with mine)
I move my funds to another non-custodial once a week...
I'll have to take the necessary time to use my self-hosted AlbyHub at one point, now that they support BOLT12 offers.
reply
Latest lightning error: Unknown payout error, contact lightning@ocean.xyz
Raw error: cln err code: -1 - message JSONRPCError: code=1005, message=Timeout waiting for response, data=map[]
Encountered at: 2025-09-27 14:06:47 UTC
reply
oh this has happened to me... its failed a couple times i sent them an email but got no response (it eventually retired and worked)
reply