Update header_id to reflect changes since EOSIODB3 #48
Conversation
This file contains 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current
header_idencodingEOSIODB3is used in an earlier version ofChainbasethat was incorporated intoLeap5.0. However, since then changes have been made into the main branch of this repo that make Chainbase incompatible with that prior version; that version of Chainbase should not be used in any patched toLeap5.0 but can be used in newer releases of the Antelope implementation. A new version is required to prevent wrong version of Chainbase from being used.It was decided to change the version encoding scheme and start with
CHAINB01.Resolves #47