Looking at the spec and our implementation.

Starting from here --

https://github.com/nostr-protocol/nips/blob/master/47.md#nostr-wallet-connect-uri

"The wallet service generates this connection URI with protocol nostr+walletconnect:// and base path its 32-byte hex-encoded pubkey, which SHOULD be unique per client connection."

So our understanding is that for each NWC connection (a user or wallet can have multiple of these), we generate a new, arbitrary nostr npub/sec pair for the NWC connection.

This pubkey doesn't match any other pubkey -- either of the user or as the service "as a whole".

Therefore, the pubkey you get from the "get_info" response is not really useful information and can be ignored.

It would be great if nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef or nostr:npub19hg5pj5qmd3teumh6ld7drfz49d65sw3n3d5jud8sgz27avkq5dqm7yv9p nostr:npub1wl3cs46hek62jm4j3x3k5etut3dkghlqfq6satsxa8q5s3tngcps22kjnr can look at my explanation above, and tell me if I am wrong.

Reply to this note

Please Login to reply.

Discussion

I think the pubkey on the get_info response should be the lightning node pubkey?

Im having trouble connecting with rust nostr-sdk

Where do you see that in the spec?

Its not, but this is what get info returns with LND APIs, include height network information, its pertaining to the info of the lightning node

Right. I'm going to open an issue here: https://github.com/nostr-protocol/nips/issues

I think you're probably right but want to confirm. Opened an issue: https://github.com/nostr-protocol/nips/issues/2070

OK, you are right, good catch. We've fixed our implementation and if you try a `get_info` on a Rizful NWC you should now see the Megalithic.me Lightning node. (Or the user's lightning node for "rizful node" users)