pull down to refresh
20 sats \ 27 replies \ @Undisciplined 10 Dec \ on: Bitcoin Beginner Saloon #1 bitcoin_beginners
When I started mining, I used a bitcoin address associated with my Alby Hub node.
I didn't realize how long it would take to reach Ocean's minimum on-chain payout threshold and I assumed I'd be able to set up the lightning payments.
Alby has implemented bolt12 payments and you can sign messages with your node, but the signature doesn't work for setting up the bolt12 receipts from Ocean.
I'm certainly not desperate to receive those sats, I'm fine with waiting for the on-chain payout, but I am curious about why it's not working and if there's an easy fix.
Edit: Nice hat, btw. How'd you get that?
- Your Alby hub is self-hosed?
- Your Alby Hub have LDK or phoenixd backend ? In this case you can generate a bolt12 offer from a cli command in phoenixd if the one from Alby doesn't work.
reply
Yes, self-hosted. The backend is LDK.
reply
OK, so you can generate the bolt12 offer but you cannot sign the message with Ocean?
I think is a separate thing, read here.
reply
You need to check if your node has the ability to sign a msg with an specific address (the one you use in ocean), I don't know if albyhub support that:
lncli wallet addresses signmessage --address <YOUR_OCEAN_BITCOIN_ADDRESS> --msg <PASTE_UNSIGNED_MESSAGE_HERE>```
reply
Look into this: https://github.com/getAlby/hub/issues/162
reply
Thanks, if I'm reading that correctly, it's not currently supported and not a priority.
reply
Indeed, so... I research a little and LDK doesn't have that feature :( ... you could try to use the seed with other software in order to obtain the address (derivation paths) and have the feature to sign messages, long shoot and I have no idea how to do it, but that's the path I would follow if I am in the same situation that you.
reply
Yeah I think that Alby in that guide forgot to mention that you can import the LDK seed into another wallet app and use it from there to sign the configuration message.
That's what I'm wondering but I didn't know how to check.
reply
Yes, I've gone through those steps. Alby Hub isn't one of the signing options, though.
reply
I think you can use any other external wallet to sign to Ocean, not really necessary to sign with the same Alby backend. Is practically signing a configuration message, not the payouts (that goes to your bolt12 offer).
reply
This is the way to go if you start from scratch, in case you already have some sat pointing to an address from you couldn't sign, you can wait until reach the min amount to withdraw, or focus in see how could you sign with an specific address from your backend node.
Next time, sign with an address you can control (sparrow is a good default) and as darth said, the bolt12 invoices is from one part of the process and is independent of the address.
reply
This was basically my plan going forward.
reply
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.
reply
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
reply
I remember you said you run a CLN node. Did you tried with that one using Zeus ?
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
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