You’re signing with the wallet where you generated the bitcoin address that you’re using for OCEAN.
Check this out and let me know if I need to clarify anything. 🫡
nostr:note1uv4hrwayym2tzw3vhl9wm9lqs056ram0ddm20zwyh47k5kcxsucs0gxseq
Discussion
Ah, you used blue wallet, I used CoinOs to generate the address.
I don’t think nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch has a sign/verify function at the moment. Maybe nostr:npub12ekpvme6m2cv37a9mgq4kzemej8tx6ttg40j582rh77ewpvkg65qj8tq0f can let us know if that’s something on the roadmap. 🤙
But yeah, I generated a new wallet in Blue Wallet just for signing. I don’t intend to receive anything there if that makes sense.
Here you go: https://coinos.io/sign
Bullish. Looks like the address displayed is in a different format (starts with a “1”). Is it the same as the bc1 address for receiving or does it not matter since the message will be signed from the same wallet?
bc1 addresses can't sign messages so I have to give you a legacy address to sign with. You'll need to copy the legacy address that we give you on the signing page into Ocean, sorry if that wasn't clear.
No problem. Thanks Adam. I’ll test it out when I get a chance. 🧡🙏
Hey Adam. I configured the miner with the legacy address, created a BOLT12 offer with the “OCEAN Payouts to 1…” memo, submitted that to OCEAN, and got the message to sign.
Unfortunately, the signing was unsuccessful without much detail. I did notice that every time I go back to coinos.io/sign, a new address is displayed. Not sure if that matters.