Nostr Web Client

Just incase you messed up where I did. The signature verification has to be from the BTC address you identify your worker as. So in sparrow, lets say, you'd have to highlight that specific address, right click then paste the message, sign it, the copy and paste the signed message back on the Ocean config page. (I was trying to sign with the On-chain address from my lightning node). I hope this helps.

btconboard #LNHANCE or #CTV 1y ago

Okay got it. So say I have a CLN lightning node on an Umbrel or Start9. That I get and think I did correctly. Totally separated from the lightning node you need an on chain address to sign that message. I guess that concept is where I’m struggling. Why do you need a separate wallet from the CLN node?

Thanks SO much!!!

Reply to this note

Please Login to reply.

Discussion

OCEAN 1y ago

Ocean has no idea I'd the on chain address is from your Lightning node's wallet or any other.

All that matters is the signature is correct.

JackTheMimic 1y ago

It doesn't "Need" to be separate. The thing that matters is your worker: 'bc1....123' needs to be the address that signs the message OCEAN generates from your Lightning Bolt12 offer. The worker can be your on chain address for your Lightning node BUT you'd have to enter your seed phrase into electrum, or sparrow or some othe wallet software that can sign a message. Core Lightning doesn't have that functionality. After signing the message in that software you can paste it into Ocean's config page.

btconboard #LNHANCE or #CTV 1y ago

Thanks!!! 🙏🏻