Well 2 of those implementations were Mutiny Wallet run so the proposal has died with them it seems. They were the only wallet provider that supported it. Alby used to say they would implement it (and presumably would if it had been merged). Now it feels fully abandoned.

We have just moved on with using the flawed onboarding flow and as such virtually no services interact with NWC at all.

I don’t think it can be merged as is anymore unfortunately. I think Alby is working on some other flow now 🤷‍♂️

Reply to this note

Please Login to reply.

Discussion

The implementations that worked at the time were listed here: https://github.com/nostr-protocol/nips/pull/851#issuecomment-1879569550

Aren't nutzaps a better flow? (I don't even know if it's related).

They force you to use a custodial wallet or run your own mint, I think? NWC allows for both custodial and non-custodial wallets.

Running an NWC server probably requires the same amount of work as running a NWC server if you want to plug it in your own node.

Nutzaps have the advantage of not requiring any setup from the Nostr side.

Alby could come with a built-in mint.

Most Alby Hubs are self-hosted so I don’t think it’s easy to run a mint over http. That’s what NWC fixes

Well maybe now that we know Mutiny is dead it was a good choice after the fact to not push this protocol, right? We could have merged and then Mutiny died and then it would be abandoned anyway, but now we would have another confusing unused spec in the repo. Maybe Mutiny died specifically because they implemented this? Who knows.

I know everything could have been the opposite, maybe Mutiny wouldn't have died if we had merged this, but just consider the possibilities.

Hahah yes but if you read the actual proposal you can’t believe any of these “possibilities”.

The entire purpose is to simple reduce an extra roundtrip from the onboarding process. Instead of having to leave our site, go to your NWC wallet, create and copy a URI, then come back and paste it to us all you have to do is scan a QR code from our website and approve the request on your wallet.

Do you really think this flow improvement killed mutiny? Who knows indeed lol

the biggest problem of nostr is that relay and client devs are not teaming up

ahahah, I wouldn't bet on it (but I wouldn't bet against it either).

We could also argue the PR not getting merged killed mutiny. Both equally fair 😂

PRs are not a congress, they are hard to find and hard to search

Many such cases

the fact that they call them "possibilities" (dis you nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 ) and yet they require some absurd requirement where 2x as many clients have to support what the relay supports, means they are not possibilities but this is a dictatorship and people respond to that instead of it just being a record of people's attempts to converge on a spec on both sides

interop means not just many clients use it it means many clients and relays use it and if you put this obstacle against publication and make it hard to find them, thank you github PRs then you see exactly where this problem originates

it's not a consensus if there is no easy to access congress to access the actual discussion

but you have to use telegram for this group or simplex for that group and nobody even considered making it a moderated wiki, oh yeah, i suggested this but then i got some retarded answer from fiatjaf about it

and here we are, where shit just isn't happening because the spec is borken so nobody can actually implement it and nobody has the balls to implement it without getting approval first on the nips repo which is a total contradiction

wen nips wiki, and fuck off with your excuses, the problem is blatant at this point

it would be better if we moved nips to slack, then at least we could fucking talk about shit

nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz Alby almost has a simpler version of NWA implemented for Alby Go. Flash wallet is also interested. We are getting there!

I will share a PR soon for the proposed updates to the NIP-47 spec (rather than a separate NIP).

nostr:npub1zk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q0gl6ef simplified is good

yeah i'm in the process of implementing the one i have described on the https://realy.lol readme... got a bit of work to do on implementing the database access