Thread - Nostr Hypermedia

For Nostr clients that support @Nostr Wallet Connect 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 @Damus ! See

GitHub

feat: add metadata to NIP-47 make_invoice and payment commands by rolznz · Pull Request #2063 · nostr-protocol/nips

Closes #1843 This PR allows storing metadata to give more context for sent/received payments, for example to display zaps, payment or recipient dat...

@Vitor Pamplona @primal @hzrd149 @YakiHonne @hodlbod + tag your favorite Nostr clients / developers!

Replies (9)

idsera idsera@blitzwalletapp.com 6 months ago

cc @Cody @Jumble

The Daniel 🖖 daniel@ghostr.org 6 months ago

Don’t forget @Fabian & @Cody.

Rizful.com admin@rizful.com 6 months ago

@Cody 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....

2 replies ↓

Rizful.com admin@rizful.com 6 months ago

@miljan 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....

Rizful.com admin@rizful.com 6 months ago

@Achilles 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 ;)