Why is there a tag and obsoleteTag in a transaction? In the code, I could find one usage (iota.lib.js) of the obsoleteTag being incremented if the normalized hash is considered insecure. This implies that one can't be sure that the obsoleteTag, or a small part of it, changes during bundle creation.
Add a comment
|
1 Answer
obsoleteTag will be removed soon. The preliminary final design of the bundle essence fragment is:
extraDataDigest [243 trits]
address [243 trits]
value [81 trits]
issuanceTimestamp [27 trits]
timelockLowerBound [27 trits]
timelockUpperBound [27 trits]
bundleNonce [81 trits]
Now that part contains obsoleteTag.
answered Jan 13, 2018 at 12:52
-
-
-
-
No, PoW nonce is in another place of the transactions. bundleNonce replaces Winternitz checksum. Jan 13, 2018 at 15:52
-
@Come-from-Beyond Is there a reference or document with the final design?– mikeMar 16, 2019 at 22:57