Ohh, interesting, so we should fetch the info event as a command to get the permissions for the current connection

We publish the 13194 event to announce what capabilities the wallet service supports, but this is done only once for the entire service.

The get_info command however is specific to the app connection, and can have a different list of commands based on the permissions granted to that app.

rolznz

. Let's see what they have to say about this 👀

SN release: autowithdraw fixes. Trouble with attached wallets? Ask here!

k00b

Oh, mhh, the [official spec](https://github.com/nostr-protocol/nips/blob/master/47.md#theory-of-operation) ("official" as mentioned [here](https://docs.nwc.dev/contribute/specification)) says this in [Theory of Operation](https://github.com/nostr-protocol/nips/blob/master/47.md#theory-of-operation):

> **Theory of Operation**
>
> 1. Users who wish to use this NIP to send lightning payments to other nostr users must first acquire a special "connection" URI from their NIP-47 compliant wallet application. The wallet application may provide this URI using a QR screen, or a pasteable string, or some other means.
>
> 2. The user should then copy this URI into their client(s) by pasting, or scanning the QR, etc. The client(s) should save this URI and use it later whenever the user makes a payment. **The client should then request an `info` (13194) event from the relay(s) specified in the URI. The wallet service will have sent that event to those relays earlier, and the relays will hold it as a replaceable event.**

Afaik, [docs.nwc.dev](https://docs.nwc.dev/) is from @Alby. Let's see what they have to say about this 👀