Update the identifier tag d for user's app data event #120

New Issue

s · 2024-07-17T10:00:18Z

s commented

2024-07-17 10:00:18 +00:00

Currently we are using sha256 hash of 938 + user's pubkey for user's the identifier tag d of user's app data event. Rather we should sign the event with 938 + user's pubkey and create_at = 0 or start of UNIX timestamp if 0 is not allowed and use the signature of that event as an identifier.

Currently we are using sha256 hash of `938 + user's pubkey` for user's the identifier tag `d` of user's app data event. Rather we should sign the event with `938 + user's pubkey` and create_at = 0 or start of UNIX timestamp if 0 is not allowed and use the signature of that event as an identifier.

s changed title from ~~Update filter for getting user's appData~~ to Update the identifier `d` for user's app data event

2024-07-22 08:19:02 +00:00

s changed title from ~~Update the identifier `d` for user's app data event~~ to Update the identifier tag `d` for user's app data event

2024-07-22 08:19:16 +00:00

~~s referenced this issue 2024-08-22 08:19:49 +00:00~~

feat: use nip04 for encryption and decryption of userData to store on blossom server #162

s commented

2024-08-22 11:14:50 +00:00

This approach wouldn't work as we would get different signatures every time we sign an event.

Sign in to join this conversation.