From 601ecc9fa4beaa08d7376e2c7f07a74361e55a58 Mon Sep 17 00:00:00 2001 From: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com> Date: Tue, 19 May 2026 13:42:28 -0700 Subject: [PATCH] Update standards/application/inbox.md Co-authored-by: Igor Sirotin --- standards/application/inbox.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/inbox.md b/standards/application/inbox.md index ba8c797..8fd4eb7 100644 --- a/standards/application/inbox.md +++ b/standards/application/inbox.md @@ -102,7 +102,7 @@ How these are transferred is out of scope for this protocol. ## Recipient Key Identifier When receiving a payload it is initially unclear which Recipients ephemeral key was used by the sender in the noise handshake. -The Recipient sends their ephemeral key out of band, and there may exist many such keys. The recipient could exhaustively attempt decryption with it's available keys however this is potentially inefficient. Additionally in the case of decryption failure, its ambiguious whether the ephemeral keys was never valid or has expired/consumed. +The Recipient sends their ephemeral key out of band, and there may exist many such keys. The recipient could exhaustively attempt decryption with its available keys however this is potentially inefficient. Additionally in the case of decryption failure, its ambiguious whether the ephemeral keys was never valid or has expired/consumed. To make this efficient, the Sender includes a short identifier for the key.