From 0043c197a349a0e362db4b3f7f80c2c557fdfb21 Mon Sep 17 00:00:00 2001 From: Philipp Gackstatter Date: Tue, 12 Mar 2024 14:40:10 +0800 Subject: [PATCH] Clarify Network ID construction --- tips/TIP-0045/tip-0045.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tips/TIP-0045/tip-0045.md b/tips/TIP-0045/tip-0045.md index 6b6f05097..0502cc5cd 100644 --- 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 | | ------------------- | ---------------------- | --------------------------------------------------- |