From 337a2149e91c2dd576fd8469bc4401db393c7964 Mon Sep 17 00:00:00 2001 From: Vitor Pamplona Date: Tue, 19 Nov 2024 10:55:25 -0500 Subject: [PATCH] fixes representation to sustain order in the hex representation. --- 01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/01.md b/01.md index 708579c..183b042 100644 --- a/01.md +++ b/01.md @@ -42,7 +42,7 @@ To obtain the `event.id`, we `sha256` the serialized event. The serialization is ] ``` -Once the `sha256` is computed, replace the first 4 bytes of the hash byte array by the 4-byte, signed, little-endian representation of the `created_at`. When verifying the event, Clients MUST check if the `id` matches the full hash OR the sorted hash. +Once the `sha256` is computed, replace the first 4 bytes of the hash byte array by the 4-byte, unsigned, big-endian representation of the `created_at`. When verifying the event, Clients MUST check if the `id` matches the full hash OR the sorted hash. To prevent implementation differences from creating a different event ID for the same event, the following rules MUST be followed while serializing: - UTF-8 should be used for encoding.