pull down to refresh

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
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.
reply
I might look into that. Like I said, I'm not in a rush to recover these sats and will probably wait to see if Alby adds this functionality in the near future.
Thanks for all the help, though.
reply
you waiting for Ocean payouts...
reply
Could be, but it seems like the lightning payments haven't been coming through either
reply
That's what I'm wondering but I didn't know how to check.
reply