laantungir/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2026-10-05 10:48:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

nip17: the seal timestamp shouldn't have to be randomize.

Browse Source
This commit is contained in:
fiatjaf
2026-09-17 13:22:27 -03:00
parent a2494f4f81
commit 9a7c10f57f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
17.md
+2 -2
View File
@@ -35,7 +35,7 @@ Following [NIP-59](59.md), the **unsigned** chat messages must be sealed (`kind:
{ {
"id": "<usual hash>", "id": "<usual hash>",
"pubkey": senderPublicKey, "pubkey": senderPublicKey,
"created_at": randomTimeUpTo2DaysInThePast, "created_at": actualCorrectTime,
"kind": 13, // seal "kind": 13, // seal
"tags": [], // no tags "tags": [], // no tags
"content": nip44.encrypt( "content": nip44.encrypt(
@@ -56,7 +56,7 @@ Following [NIP-59](59.md), the **unsigned** chat messages must be sealed (`kind:
Clients MUST verify if pubkey of the `kind:13` is the same pubkey as that of the `unsignedMessageRumor`, otherwise any sender can impersonate any other by simply changing the pubkey on the rumor. Clients MUST verify if pubkey of the `kind:13` is the same pubkey as that of the `unsignedMessageRumor`, otherwise any sender can impersonate any other by simply changing the pubkey on the rumor.
Clients SHOULD randomize `created_at` in up to two days in the past in both the seal and the gift wrap to make sure grouping by `created_at` doesn't reveal any metadata. Clients SHOULD randomize `created_at` in up to two days in the past in the gift wrap to make sure that grouping by `created_at` doesn't reveal any metadata.
## Publishing ## Publishing