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!
Login to reply
Replies (9)
cc nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl nostr:npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9
Donβt forget nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe & nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl.
nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl also -- This should hopefully be straightforward to implement for Nostr client developers, and would greatly improve the UX for users who use NWC in your apps....
nostr:nprofile1qyvhwumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wshszymhwden5te0wp6hyurvv4cxzeewv4ej7qpq6c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9qe52zdt We have lots of users requesting this behavior ... any chance to add it to the Primal developement queue? It should be straightforward and backwards compatible....
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 ;)
Iβm using bitcoin-connect, how should I add the metadata?
Take a look here: https://github.com/nostr-protocol/nips/issues/1843
I think to implement this in a client, you need to look at both of these pages...
https://github.com/nostr-protocol/nips/issues/1843
https://github.com/nostr-protocol/nips/pull/2063
And then look again right here: https://github.com/nostr-protocol/nips/blob/master/47.md#pay_invoice
... look at that `metadata` field
.... and then look here :
https://github.com/nostr-protocol/nips/blob/master/47.md#metadata
.. specifically at this part:
```
"nostr": {
"pubkey": "string",
"tags": [],
// ...
}, // NIP-57 (Nostr Zaps)
```
nostr:npub14ya7n7czu3kyq3m2sn6kjawmtq6ll6kerrlm90gz9yzfjmflmsxq8dsn39 also, YakiHonne developer