pull down to refresh

I attempted to set up NWC receive connection to my SN wallet on mobile. I received this message:
failed to create test invoice: pay_invoice must not be supported

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.

reply

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?

https://files.ekzy.is/public/sn/2024-09-08%2015-56-48.mp4

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.com

This 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.

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

I think I'm going to delete this post but save the dialogue. It looks negative, but the fault was with me, not SN.

reply

No
Please let it be.
I've been following everything and I don't wanna miss the next time I read it or suggests someone.

reply

Okay.

reply

Yes, keep it, it's relevant context. And I don't mind the "still", being wrong happens :)

reply

Thanks for holding the same views! I really appreciate your patience everytime you answer wallet or also SN related questions. Really you're doing it incredibly and eclxceptionally.

reply

Well, it's what I'm getting paid to do, lol

Thanks, much appreciated though

reply

Thank you so much!
All of this is worth reading and it answered a lot of questions.

reply

After such long conversations, in case, you want to get relaxed with some cool 60s and 70s rock music, @SN_MusicPool has got a good post. I'm sharing this with you as I feel you'll really like it.

reply

I'll check it out when I get home. I'm at a birthday party.

reply

works for me, did you customize the nwc string by removing pay authorization?

reply

I attempted to, but the permissions reverted back to include pay authorization. I couldn't figure out how to save the edits.

reply

Are you referring to the hub or standalone app?

reply

This is gotham dude

reply

Is can perform other transaction tho

reply

No. It works for both send and receive. My mistake.

reply