pull down to refresh

doesn't work for setting up the bolt12 receipts from Ocean.
Be sure you have compatible peers in your backend LN node. Maybe you are trying a bolt12 through a peer that doesn't support it. Not all nodes support it.
That's interesting. Alby posted a guide specifically for receiving payments from Ocean and they did not include Alby Hub as one of the signers that would work.
reply
69 sats \ 6 replies \ @siggy47 20h
If I recall you need to sign on chain. I don't recall the exact details, but I needed to use electrum.
reply
I remember you said you run a CLN node. Did you tried with that one using Zeus ?
reply
0 sats \ 1 reply \ @siggy47 10h
I use Zeus now with it for remote management, spending, etc, but I didn't sign the initial transaction with it.
reply
Good news: soon Zeus will introduce sub-accounts and NWC server...
reply
Right, but I don't know why that can't be done with Alby Hub. I have an on-chain wallet associated with my node.
reply
69 sats \ 1 reply \ @siggy47 20h
I had the same problem. You can't sign with that type of wallet. I can't explain why. I created an electrum on chain wallet, then signed the transaction.
reply
It sounds like it's technically possible but difficult and not a priority.
reply
Note: Ensure you have at least one payment channel with sufficient receiving capacity with Megalith LSP or LNServer. Both support onion message forwarding. You can check your channel partners and receiving capacity on the Node page of your Alby Hub.
reply
That's not a problem
reply