Only allow printable chars in metadata keys

iotaledger · Dec 21, 2023 · d2af320 · d2af320
1 parent e8765c7
commit d2af320
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/tips/TIP-0038/tip-0038.md b/tips/TIP-0038/tip-0038.md
@@ -840,7 +840,7 @@ Feature</i>: smart contract request parameters are encoded in the metadata field
           <tr>
             <td>Key</td>
             <td>(uint8)ByteArray</td>
-            <td>A string which may only consist of ASCII characters. A leading uint8 denotes its length.</td>
+            <td>A string which may only consist of printable ASCII characters. A leading uint8 denotes its length.</td>
           </tr>
           <tr>
             <td>Value</td>
@@ -855,8 +855,8 @@ Feature</i>: smart contract request parameters are encoded in the metadata field
 
 #### Additional Transaction Syntactic Validation Rules
 
-- Each `Key` in the `Entries` must consist only of bytes that are valid ASCII characters, that is, each byte may not
-  exceed `127`.
+- Each `Key` in the `Entries` must consist only of bytes that are printable ASCII characters, that is, for each
+  character `char` (interpreted as a byte) in the `Key` it must hold: `33 <= char <= 126`.
 - Each `Key` in the `Entries` must be unique.
 - `Entries Count` must be at least `1`.
 - The serialized size of the map, consisting of the serialized size of `Entries Count` plus the serialized size of all