From 9a7c10f57f84ce241b419763b6d4dc02daba9822 Mon Sep 17 00:00:00 2001 From: fiatjaf Date: Thu, 17 Sep 2026 13:22:27 -0300 Subject: [PATCH] nip17: the seal timestamp shouldn't have to be randomize. --- 17.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/17.md b/17.md index 23fde73a..00a8bfc7 100644 --- a/17.md +++ b/17.md @@ -35,7 +35,7 @@ Following [NIP-59](59.md), the **unsigned** chat messages must be sealed (`kind: { "id": "", "pubkey": senderPublicKey, - "created_at": randomTimeUpTo2DaysInThePast, + "created_at": actualCorrectTime, "kind": 13, // seal "tags": [], // no tags "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 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