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.

1 Answer 1


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.

  • Is there any documentation which covers these changes?
    – Daniel F
    Commented Jan 13, 2018 at 12:54
  • No documentation, the changes haven't been tested yet. Commented Jan 13, 2018 at 13:02
  • What is the bundleNonce? POW nonce? Commented Jan 13, 2018 at 14:26
  • No, PoW nonce is in another place of the transactions. bundleNonce replaces Winternitz checksum. Commented Jan 13, 2018 at 15:52
  • @Come-from-Beyond Is there a reference or document with the final design?
    – mike
    Commented Mar 16, 2019 at 22:57

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.