[0.12] Add backwards-compatibility issues (chainstate obfuscation) to release notes #7345
Conversation
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
0c7441d to
888889a
Compare
|
Concept ACK. Is there a way to instruct 0.12 to not use obfuscation? |
| reindex, the block files and databases are not backwards-compatible with | ||
| pre-0.12 versions of Bitcoin Core or other software. | ||
|
|
||
| If you want to downgrade after you did a reindex with 0.12.0 or later, |
888889a to
77778fb
Compare
77778fb to
fa8c497
Compare
|
Thanks, makes sense! |
laanwj
added a commit
that referenced
this pull request
Jan 18, 2016
fa8c497 [doc] backwards-compatibility issues due to chainstate obfuscation (MarcoFalke)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
No description provided.