This issue is due to some gaps in the NIP-47 spec that make it unclear how implementers should communicate sender/receiver information.
We have an open issue on the NIPs repo about this, with useful context and information: https://github.com/nostr-protocol/nips/issues/1843
Currently Damus is using the description field (following NIP-57 conventions) and/or the metadata field (following AlbyHub’s conventions) to communicate sender/receiver information.
danieldaquino / Daniel D’Aquino
npub13v…zl3l8
2025-06-02 17:35:32 UTC
in reply to nevent1q…v23w
Author Public Key
npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8Published at
2025-06-02 17:35:32 UTCEvent JSON
{
"id": "97a6a2d5618b097c16ae3924f9f2a6b9cd0cf9d295032f9f32f0e83fb5b7a298",
"pubkey": "8b2be0a0ad34805d76679272c28a77dbede9adcbfdca48c681ec8b624a1208a6",
"created_at": 1748885732,
"kind": 1,
"tags": [
[
"e",
"3194584a252b6fc458e0b259a3a771cc4ceaed905c9480065f038bd93992723d",
"",
"root"
],
[
"e",
"67267b73815a68bff3772595138528c368f00018b500f549ea8c7600df793661",
"",
"reply"
],
[
"p",
"06b7819d7f1c7f5472118266ed7bca8785dceae09e36ea3a4af665c6d1d8327c"
],
[
"p",
"2779f3d9f42c7dee17f0e6bcdcf89a8f9d592d19e3b1bbd27ef1cffd1a7f98d1"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"r",
"https://github.com/nostr-protocol/nips/issues/1843"
]
],
"content": "This issue is due to some gaps in the NIP-47 spec that make it unclear how implementers should communicate sender/receiver information.\n\nWe have an open issue on the NIPs repo about this, with useful context and information: https://github.com/nostr-protocol/nips/issues/1843\n\nCurrently Damus is using the description field (following NIP-57 conventions) and/or the metadata field (following AlbyHub’s conventions) to communicate sender/receiver information.",
"sig": "5a42a72ab0b6a57a4a186af485d7b4025e708c74ed1f5c695481f3c215bfbad3e6d6859f4b3ab69eddd27de77a3093f199cb4a2165d710e466c93e5cec276be1"
}