-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Importing Bitcoin Uncompressed WIF PrvKey Derives Compressed Legacy Address #107
Comments
@nc50lc our programmer knew it. We will fix it. When it is done, we will inform you. Tks. |
Thank for letting me know that they're working on this. |
Any movement on this getting resolved? |
Hello? Any news about resolving this problem? |
sorry, our dev is very busy. If any news, i will update. |
There seem to be quite a few situations like this, so if you restore the wallet plug-in configuration file through data recovery after resetting Windows, can you enter the wallet interface through the originally installed wallet plug-in, enter the password set at that time, and then enter the wallet interface? Export helper words? Is this a feasible solution? I've done this but still can't open the plugin wallet, I need technical support, |
@sendentone it is an issue different with the main topic, and it is a bit complex, please open a ticket in our discord server https://discord.com/invite/unisat , we could get a timely communication there. |
The issue is straightforward:
A WIF prvKey with uncompressed flag (starts with '5')
should have an uncompressed pubKey pair which where the address should be derived from.
Instead, current release forces it to use the compressed pubKey.
To reproduce:
Related link (Bitcointalk): Unisat gives different public address after importing a private key
The text was updated successfully, but these errors were encountered: