The issue is that ecash forces custody while making the path to non-custody harder.
NWC is a superior API to build around instead of focusing on ecash integrations, since switching to your own node is trivial with NWC if you want to upgrade to a non-custodial setup.
There is no real non-custody upgrade path in the ecash case if devs focus on building ecash integrations instead of NWC.
Let's focus dev energy around #NWC and lightning wallets with zap support! They are severely lacking!
Let's not rebuild the world we are trying to deprecate.
nostr:note14p8qklmp4xmnxkeee4vj8l35haref64pdqzcl0x6r7eh0t2vmfhs200cy9
Just discovered that NWC solves half the problem of opening ports on a router. Awesome.
Please Login to reply.
yeah its amazing for that
Yep. I am expanding my NWC implementation to handle more directives, such as privately transmitting records to other NWC wallets.
I use NIP-4 for receiving the directives and communicating the results, but everything behind the scenes is NIP-59/NIP-44
