This repository was archived by the owner on Aug 23, 2020. It is now read-only.
fix MAX_TIMESTAMP_VALUE to actually represent "max positive 27-trits value"#777
Merged
GalRogozinski merged 1 commit intoiotaledger-archive:devfrom May 30, 2018
Merged
Conversation
GalRogozinski
approved these changes
May 30, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
fix MAX_TIMESTAMP_VALUE to actually represent "max positive 27-trits value"
Fixes #531
Type of change
How Has This Been Tested?
Manually checking the value of this field in the Debugger,
testing conversion of
3812798742493to trytes:MMMMMMMMM(thanks to https://laurencetennant.com/iota-tools/)