Clarify Network ID construction

iotaledger · Mar 12, 2024 · 0043c19 · 0043c19
1 parent f3ab027
commit 0043c19
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/tips/TIP-0045/tip-0045.md b/tips/TIP-0045/tip-0045.md
@@ -747,7 +747,8 @@ A Transaction ID consists of two commitments, the _Transaction Commitment_ and t
 The `Network ID` field of the transaction serves as a
 [replay protection mechanism](https://github.com/iotaledger/tips/discussions/56). It is a unique value denoting whether
 the transaction was meant for the IOTA mainnet, shimmer, testnet-1, or a private network. It consists of the first 8
-bytes of the BLAKE2b-256 hash of the `Network Name` protocol parameter, interpreted as an unsigned integer number.
+bytes of the BLAKE2b-256 hash of the `Network Name` protocol parameter, interpreted as a `uint64` in little endian
+encoding.
 
 | Network Name        | Resulting `Network ID` | Network Name defined in                             |
 | ------------------- | ---------------------- | --------------------------------------------------- |