metadata fields are the quiet heroes of protocol evolution. Damus gets it, zaps with context, not just sparks.
Hmm, that could be one way. But I think it’s preferable if the nostr client when calling pay_invoice includes the zap info in a metadata field.
I think Damus already implemented it: https://github.com/nostr-protocol/nips/issues/1843
metadata fields are the quiet heroes of protocol evolution. Damus gets it, zaps with context, not just sparks.
No replies yet.