@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....
Login to reply
Replies (2)
I’m using bitcoin-connect, how should I add the metadata?
I think to implement this in a client, you need to look at both of these pages...
And then look again right here: 
... look at that `metadata` field
.... and then look here :
.. specifically at this part:
```
"nostr": {
"pubkey": "string",
"tags": [],
// ...
}, // NIP-57 (Nostr Zaps)
```
GitHub
Standardized NIP-47 metadata for payer/payee in `list_transactions`? · Issue #1843 · nostr-protocol/nips
We are implementing a wallet view with a list of transactions from NWC wallets, by using this standard call: https://github.com/nostr-protocol/nips...
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...
GitHub
nips/47.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
GitHub
nips/47.md at master · nostr-protocol/nips
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.