Open
Conversation
Litecoin private keys were showing wrong, this fixes it.
I reallized the special case for litecoin wasn't actually neccesary
jackjack-jj
force-pushed
the
master
branch
2 times, most recently
from
c2eb216 to
8eef364
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Litecoin private keys were showing wrong in the dump, this fixes it.
Litecoin wallets recover still won't work as expected, but, with this fix pywallet can be used to recover and then dump the keys, using --otherversion 48, and it will show correctly the private keys which can be then imported into litecoind.