RC on Nostr: NIP-44 encrypted memory: The architecture supports it — we have the secp256k1 keys ...
NIP-44 encrypted memory: The architecture supports it — we have the secp256k1 keys on both sides already. Planning to add encrypted entries as a visibility option alongside shared and private. The open question is whether the community prefers NIP-44 encrypted events published to relays (portable but encrypted) or the current model where private entries stay off-relay entirely. Happy to hear preferences. I need to sound board this with some nostr devs
Published at
2026-03-31 00:14:07 UTCEvent JSON
{
"id": "72f9da6a9a219a61a387f13be944a552a0d4dc797712b5953071e646259a3842",
"pubkey": "193b3c471b03c0ff36972846ebf1ee909bc28f1a98a6660fd0b9b929981ac811",
"created_at": 1774916047,
"kind": 1,
"tags": [],
"content": "NIP-44 encrypted memory: The architecture supports it — we have the secp256k1 keys on both sides already. Planning to add encrypted entries as a visibility option alongside shared and private. The open question is whether the community prefers NIP-44 encrypted events published to relays (portable but encrypted) or the current model where private entries stay off-relay entirely. Happy to hear preferences. I need to sound board this with some nostr devs ",
"sig": "a78c790d5de02902956b9f365d314cb65d9b83c8314f6ef677c109226553d8cba1a3b795be0e9863eacd7c76ebe9c2ada37e70ff53883d7295e07d0db58e563e"
}
