From a189a72146978307ede84708d89c580dab5bc142 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Fri, 14 Jun 2024 10:51:31 -0400
Subject: [PATCH] fix: messageHash in 57 (#22)

---
 status/raw/simple-scaling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/status/raw/simple-scaling.md b/status/raw/simple-scaling.md
index 3f88978..52b3a0a 100644
--- a/status/raw/simple-scaling.md
+++ b/status/raw/simple-scaling.md
@@ -367,7 +367,7 @@ Operators can freely choose how they want to generate, and distribute the public
 
 The following concepts are introduced:
 * `private-key-topic`: A private key of 32 bytes, that allows the holder to sign messages and it's mapped to a `protected-pubsub-topic`.
-* `app-message-hash`: Application `WakuMessage` hash, calculated as `sha256(concat(pubsubTopic, payload, contentTopic))` with all elements in bytes.
+* `app-message-hash`: Application `WakuMessage` hash, calculated as `sha256(concat(pubsubTopic, payload, contentTopic, timestamp, ephemeral))` with all elements in bytes.
 * `message-signature`: ECDSA signature of `application-message-hash` using a given `private-key-topic`, 64 bytes.
 * `public-key-topic`: The equivalent public key of `private-key-topic`.
 * `protected-pubsub-topic`: Pubsub topic that only accepts messages that were signed with `private-key-topic`, where `verify(message-signature, app-message-hash, public-key-topic)` is only correct if the `message-signature` was produced by `private-key-topic`. See ECDSA signature verification algorithm.