From 85f2b2f833889b5742011219303cec08aa479fce Mon Sep 17 00:00:00 2001 From: 0xchatTeam <130329555+0xchatTeam@users.noreply.github.com> Date: Sun, 14 May 2023 13:02:31 +0800 Subject: [PATCH] add sig field in the encrypted_text --- 101.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/101.md b/101.md index 94ccc91..3768cca 100644 --- a/101.md +++ b/101.md @@ -27,7 +27,16 @@ The protocol can be implemented following the steps below. Note that the content 1. User A (the initiator) generates an alias key pair derived from their own private key and User B's (the recipient) public key. -2. User A sends a 10100 kind event to User B, signed with their alias private key. The 'p' parameter is User B's real pubkey. The `encrypted_text` can be in json format: `{"p":"A's real pubkey", "content":"your content"}`. +2. User A sends a 10100 kind event to User B, signed with their alias private key. The 'p' parameter is User B's real pubkey. The `encrypted_text` can be in json format: + + +```json +{ + "p":"A's real pubkey", + "content":"your content", + "sig":"<64-bytes hex of the signature of the event id, signed by A's real private key>" +} +``` For example: