Nostr Web Client

I'm waiting for nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzamhxue69uhkzarvv9ejumn0wd68ytnvv9hxgtcpzfmhxue69uhhqatjwpkx2urpvuhx2ucunm6wg to debug the code so I can connect my nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcprdmhxue69uhkummnw3ez6vfwde3x7tnpdenkzmnf9e3k75xqss4 account to an NWC compatible wallet like nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzdmhxue69uhhqatjwpkx2urpvuhx2ue0fjzwm2

bumi 1y ago

I've debugged this and there seems to be an issue with the nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv NWC URL.

Minibits adds multiple relays (e.g. relay=wss://relay.minibits.cash&relay=wss://relay.primal.net&relay=wss://relay.damus.io&relay=wss://nostr.mom ) This is not as the spec describes it and I think also different client implementation interpret this differently.

Our implementation here uses the last relay and this one seems to not respond to a NWC request.

nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv I recommend to only use one relay now.

(We as Alby also operate a NWC optimized relay that we offer.)

Reply to this note

Please Login to reply.

Discussion

retired npub 1y ago

Okay, let me try with nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzdmhxue69uhhqatjwpkx2urpvuhx2ue0fjzwm2 NWC

bumi 1y ago

nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch does not support all NWC functions, yet. So far only sending and loading the balance I think.

retired npub 1y ago

It didn't connect to nostr:nprofile1qqst4qyeqenw7zm0fwjsty68h6cnys5jre2xd8ngqpjv5a2j26s78fspzdmhxue69uhhqatjwpkx2urpvuhx2ue0fjzwm2 either

bumi 1y ago

nostr:npub1h2qfjpnxau9k7ja9qkf50043xfpfy8j5v60xsqryef64y44puwnq28w8ch do you plan to implement the other NWC functions, too?

Mysterious Hamster 1y ago

Sure we can. Can you suggest some apps/clients that make use of some of the other methods so we can test? Currently we have pay_invoice get_info and get_balance

Mysterious Hamster 1y ago

Oh I guess you're referring to the Alby NWC app? Does it need us to support all the methods in the NIP or is there some subset it's looking for?

bumi 1y ago

whatever you are comfortable with using.

here the goal was to use the coinos wallet with the alby account.

you can also check the alby extension that would work the, too

Mucky the Moose 1y ago

cannot add any technical details here, but wanted to say that I have hooked coinos wallet to my Alby browser extension for zapping. Its working but has some minor issues with how it integrates with the Alby extension. (so I guess, if you can make it 'fully compatible' that would be great. 🙏)

Mysterious Hamster 1y ago

workin' on it!

Minibits 1y ago

Spec says that relay param may be more than one. You're right that multiple relay params in query string looks weird but that was what I've seen in some other implementation.

If it is indeed wrong encoding, I'd be happy to fix it but would prefer not to rely on a single relay.

bumi 1y ago

True. hmm, that spec needs to be updated there. because if more than one is provided then it should be an array imo relay[]=xxx&relay[]=yyy

otherwise different parsers interpret it differently.

At the same time multiple relays add some complexity for apps and wallets. so far all NWCs used one relay afaik.

I personally doubt that relays for NWC are the weak link in the chain and need redundancy that the event is published to multiple ones.

Also considering privacy and that those are no "normal" events.

Do you know why nostr.mom seems to not work for NWC events?

Minibits 1y ago

Agree, relay[] is supported encoding in query strings, but I'm afraid it might not be what nwc clients expect.

Will consider to point it to my strfry instance relay.minibits.cash

bumi 1y ago

I am rather sure that no nwc client supports multiple relays at this point.

and the implementation like in the spec would have issues because of underlaying query parsers.

Minibits 1y ago

Ok will change it in the next release.