pull down to refresh
117 sats \ 16 replies \ @ek 8 Sep \ on: NWC Receive Still Not Working for SN Wallet meta
P2P zaps and autowithdrawals are coordinated on the server. This means the NWC connection for receiving is sent to us unlike the one for paying which only exists on your device.
The error message means that you're trying to give us a NWC connection that would let us spend your funds instead of only create invoices.
If you're using Alby Hub, it is giving you the option to not give us full access. That should work but I am going to verify now.
It looks like I need to edit and remove send payments from the permissions. I'll see if that works.
reply
Yes, if you use
Read Only it should work, I just tested on my end:However, all we need is to create invoices so that is also enough:
reply
Now I see my problem. The Alby NWC connect app supposedly allows you to edit permissions, but it reverts to default when moving to the secrets menu. When I examine the permissions, they are still unlimited. In other words, I can't find a way to save my edits on the app.
reply
Does this not work for you? Why do you need to edit an existing connection?
reply
I'll try this. Is the PubKey sufficient to connect? There don't appear to be full secrets generated
reply
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
I was using the Alby hub standalone NWC connect app I have on my node. Now I'll try the actual Alby Hub SN connection.
reply
I'll try read only now.
reply