nostr:nprofile1qyg8wumn8ghj7vf5xqhxvdm69e5k7qgkwaehxw309ashgmrpwvhxummnw3ezumrpdejqqgrxlkw9cq3thedcswuxazj4p37eeyxj373yga2vfaejum07j87ttqte6cq5 This is the standard that Primal would need to implement so you can see both inbound and outbound zap data with NWC. Primal might be more interested if you reply here and tell them it would be useful ;)
For Nostr clients that support nostr:nprofile1qyfhwumn8ghj7mn0wd68yt3nxd3k7tnyv5q3qamnwvaz7tmwdaehgu3wd3skueqqypm78zzh2lxmf2twk2y6x6n903w9kezlupyr2r4wqm5uzjz9wdrqxnx5zlp please consider including the zap in the recently added optional `metadata` field in `pay_invoice`. This will enable wallets to display the zap in their transaction list rather than just a standard outgoing payment. Already added in nostr:nprofile1qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgqgdwaehxw309ahx7uewd3hkcqpq8m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsmthtls !
See https://github.com/nostr-protocol/nips/pull/2063
nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3qamnwvaz7tmwdaehgu3wd4hk6tcqyprqcf0xst760qet2tglytfay2e3wmvh9asdehpjztkceyh0s5r9cpvx58v nostr:nprofile1qythwumn8ghj7mn0wd68ytnsv9ex2ar09e6x7amwqyvhwumn8ghj7mn0wd68ycmgv43kktndv5hhyetvv9usqgzn9kpsmllqnsf7wh5tz3wgy4cclsftqqplv8tpayrhwgw8llunevk4p6dz nostr:nprofile1qyv8wumn8ghj76twvfhhstnjv4kxz7tn9ekxzmny9uqsuamnwvaz7tmwdaejumr0dshsqgpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg5502tfpf nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyw8wumn8ghj7mn0wd68ytfsxyh8jcttd95x7mnwv5hxxmmdqqszpxr0hql8whvk6xyv5hya7yxwd4snur4hu4mg5rctz2ehekkzrvcsuxfmc nostr:nprofile1qyvhwumn8ghj76rzwghxxmmjv93kcefwwdhkx6tpdshszrnhwden5te0dehhxtnvdakz7qpqjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qy09qsr + tag your favorite Nostr clients / developers!
Discussion
No replies yet.