nostr:nprofile1qqsrq7p2sv3m0jvtzuk952hhyp4ms2puv4d7dhwwzyfnvydq8403zacdqda04 Zapstore could expose an Android intent to apps to pay with the loaded NWC string! It would be even better if an NWC token could fork child tokens specific to apps, all within the same budget but I'm probably dreaming too hard here 😅
Discussion
Unless I'm missing an easier way of obtaining a new string, maybe thru Alby Go? 🤔
cc nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpqzk6u7mxlflguqteghn8q7xtu47hyerruv6379c36l8lxzzr4x90q8tg5jd nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqsv695mmraa29u792x5nrlux8f6urjqsf0l9w9gt634n3z9tgg8e2q8pqu7d
You can enable Alby Go to create new connections - you can read about it and see some demos here: https://blog.getalby.com/new-nwc-one-click-wallet-connections-simplify-app-ux/
It’s possible to launch Alby Go to create the connection and then return to Zap Store with a single tap. Let me know if you’re interested and have any questions!
There is this PR to the spec -> https://github.com/nostr-protocol/nips/pull/1818
which is implemented in NDK, sample use -> https://github.com/relaystr/ndk/blob/master/packages/sample-app/lib/nwc_page.dart
It's already used in Yana and https://zap.stream/app
Don't know what shosho uses since it doesn't seem to be opensource...
Very cool. Will look into it!