-
Notifications
You must be signed in to change notification settings - Fork 71
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
Wrong wallet address #1115
Comments
Hi @jeffmail, I am very sorry you are having this issue. Do I understand correctly you are using the Hiro Wallet in the browser (Web extension)? When you are shown different public address the only likely scenario is that you are using a different seed phrase. The same seed phrase will always produce the same public address(es). |
I think the issue is I am getting a second (non principle wallet address shown in the hiro wallet. The seed phase had a primary wallet SPCGY4K9AN72MBEX51DYX72R7RMV9NQ3X59MNSZQ and a secondary wallet (create additional account) when I log in now I only see the non-principle if I search the stx explorer for SP1JY8YPH63GV1FDM2YBKY3F2BM75QQBCW0603PTS, it gives me an error telling its not a principle wallet address, but in my hiro it shows as account 1 and the previous account 1 does not show. The seed phase was stored written in my safe and I was able to log into it many times over the last year, this is a brand new issue. I have been using crypto since 2013 and I am certain this isnt a seed phase mistake. |
I used to have 2 other accounts in there, the primary and another non primary. they both had .btc domains, not sure if that's relative |
@jeffmail thank you for the additional details. Please rest assured that we take this issue very serious. When you wrote your first comment I started testing with other seed phrases to make sure they give the expected result. Additionally I have discussed your case with our devs. Because this is a huge issue we also have automated tests that are run to test that the same public keys are generated when a seed phrase is used again. We have not been able to reproduce the issue you are experiencing. Please also consider checking for other seed phrases you may have used while we investigate further. For the outside or for the explorer, which has no knowledge of private keys, a primary account is the same as a secondary account. The reason the explorer will not show a principle (address) without transactions is because it does not have any data on it (the explorer database gets filled as blockchain transactions are processed). Do I understand correctly that you had two accounts on the previous login with this seed and each had a .btc name and the second account had this public address? SP1JY8YPH63GV1FDM2YBKY3F2BM75QQBCW0603PTS |
Yes this is helpful. This can help us troubleshoot. Would you mind sharing the names? If you prefer to keep then private please email me at wallet at hiro.so |
email sent |
It turned out that a different key had been input than expected. Closing this as solved. |
Tonight I had the same thing happen. Has anyone ever seen or fixed this?
For the last year my stx wallet was:
SPCGY4K9AN72MBEX51DYX72R7RMV9NQ3X59MNSZQ
I have some NFTs, domain name, and 1000 STX.
Today after several months I signed back into my hiro wallet with my secret key which I have always used and store in a physical safe. It let me restore wallet by entering secret but it gave me this address:
SP1JY8YPH63GV1FDM2YBKY3F2BM75QQBCW0603PTS
I dont see my other address or tokens/etc. When I look for additional accounts it did not show any. I clicked new account and it creates new addresses, but I dont have my old one.
When I look on stx blockchain, I can find my old address and tokens/etc, but if I try and search for this new wallet address it just says no wallet found. Can anyone help?
I just tried with the xverse mobile app and still have the same issue, previously I tried with the hiro web wallet (chrome).
I am having the same issues described in this post
#830
[4.3.0] Bug: Wrong wallet address #830
The text was updated successfully, but these errors were encountered: