Skip to content
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

Issue with the correct path for the Segwit. #969

Open
PUNKWISE opened this issue Jun 23, 2023 · 2 comments
Open

Issue with the correct path for the Segwit. #969

PUNKWISE opened this issue Jun 23, 2023 · 2 comments

Comments

@PUNKWISE
Copy link

Hi,

I'm facing a problem with the Bitcoin Wallet (beta) on my Android device, which I downloaded from the Play Store. However, I'm here seeking help from the community, as I'm trying to assist a friend who's experiencing this issue.

We want to export the private key from the Bitcoin Wallet. We've managed to export the backup file and extract the seed phrase successfully.(openssl) The trouble arises when we attempt to import the seed phrase into Electrum and detect an existing account. Unfortunately, every time we try, we're met with the frustrating message "No account exists!". We have changed the path and all the parameters.

Now, here's where it gets interesting. The Bitcoin addresses within the wallet are segwit addresses, "bc1q". All transactions are visible on these addresses without any problems -(Mobile). In an effort to resolve the issue, we've useed the Coleman BIP39 tool, using the m/84 path (bip84). Surprisingly, the tool generates different addresses that have never been used.

To investigate further, we compared the legacy addresses (starting with "1") within the wallet app to the bip32 addresses on the tool, and they match perfectly. (which means that there is no problem with the seed and it is correct) However, when it comes to the segwit addresses, the correct ones don't show up. We've scoured the web for specific paths to try, but none of our attempts have been successful. Even when importing the wallet backup file onto another device, we encounter the same data as on the initial device.

The only information we can gather from the app is the extended public key, which starts with "z".

I'm reaching out to this community in the hopes of finding a solution to this problem and retrieving the correct used addresses. Any help or guidance would be immensely appreciated.

Thank you all in advance for your support.

Best regards,

@bitcoin-wallet bitcoin-wallet deleted a comment from Helloween45 Jul 20, 2023
@bitcoin-wallet bitcoin-wallet deleted a comment from Helloween45 Jul 20, 2023
@bitcoin-wallet bitcoin-wallet deleted a comment from Helloween45 Jul 20, 2023
@schildbach
Copy link
Collaborator

Why don't you use "Restore wallet" to restore from your backup?

@bitcoin-wallet bitcoin-wallet deleted a comment from Laye27 Jul 27, 2023
@bitcoin-wallet bitcoin-wallet deleted a comment from Laye27 Jul 27, 2023
@bitcoin-wallet bitcoin-wallet deleted a comment from Arielek9 Jul 27, 2023
@sharonleerichardson88
Copy link

Why don't you use "Restore wallet" to restore from your backup?

I don’t have my money

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants