pull down to refresh
121 sats \ 9 replies \ @siggy47 OP 8 Sep \ parent \ on: NWC Receive Still Not Working for SN Wallet meta
I'll try this. Is the PubKey sufficient to connect? There don't appear to be full secrets generated
No, it should look like this:
nostr+walletconnect://00f1646918f62a929f7bb62a3dd8404ed5bed8e5e1a8857d09de65f854d28976?relay=wss://relay.getalby.com/v1&secret=990a489309d362d8957e206a33f1dd062e676897d8759943559a0e49604fafcb&lud16=brilliantpresence748547@getalby.comThis is a connection that my Alby Hub generated that I am going to throw away now.
reply
I know. Are you using the Alby Hub with its node, or your own node? I am using my own node. I don't get access to the full secrets when I connect to SN on the hub.
reply
reply
Edit: Forget that. Let me try again. I had a senior moment.
reply
reply
It worked! Thanks for your patience. I do wonder, though, why Alby's NWC connect standalone app doesn't seem to allow you to edit permissions? cc: @Alby
reply
reply
Let me just explain more fully where I ran into problems, in case anyone else experiences this too.
The Alby app store has an app called nostr wallet connect ( lower left in the photo)
I used this app to originally connect to SN for send only. When I tried to set up a receive connection today, it failed, prompting this post. So far as I can tell, you cannot edit the permissions on this app. It appears to let you, but it reverts to full default permissions before the secrets are generated.
Now I will see if there is any noticeable difference from receiving through NWC connect versus a lightning address.