No the seed is right.
The address with the balance belongs to a different seed.
You have a seed... not the seed.
Maybe it's time to talk to your friend.
Topic: Can't access my money because of the derivation path - page 2. (Read 739 times)
There is no doubt in my mind that that is the wallet that belongs to that seed and that it is in fact empty.
So you think the seed is wrong?
Yet almost all transactions of the coinbase wallet are shown in the legacy wallet.
But the last transaction is the one that is shown in the segwit wallet! WTF?! It's like the conbase wallet app contains different wallets with different derivation paths within itself and it exchanges between them from time to time.
There is no doubt in my mind that that is the wallet that belongs to that seed and that it is in fact empty.
The chance of you accidentally stumbling on that/someone else wallet with that seed is extremely slim.
The chance of you accidentally stumbling on that/someone else wallet with that seed is extremely slim.
This is what I see when I create the legacy wallet
this is what I see when I create the segwit wallet
this is what I see when I enter the coinbase wallet app
this is what I see when I create the segwit wallet
this is what I see when I enter the coinbase wallet app
I wrote your code in the console, pressed enter, restarted electrum but I see the same amount of addresses.
I also entered his coinbase wallet app, I can see all the transactions up to 3 days ago. I tried all 10 different wallets that you find by pressing settings/advanced/active wallet but everything is empty. Also, no matter which wallet I tried, they all show the same exact transactions.
Another thing that doesn't app up is that the transaction list shown in the app does not coincide 100 % with the 2 wallets I have found with electrum. The transactions I found on the segwit electrum wallet are not shown in the coinbase wallet app.
The transactions I found on the legacy electrum wallet are shown in the coinbase wallet app, but not all of them and some that are listed in the coinbase wallet up are not present in the electrum wallet.
So there's clearly a mess going on here. Same seed, same wallet and not all txs show up?
I also entered his coinbase wallet app, I can see all the transactions up to 3 days ago. I tried all 10 different wallets that you find by pressing settings/advanced/active wallet but everything is empty. Also, no matter which wallet I tried, they all show the same exact transactions.
Another thing that doesn't app up is that the transaction list shown in the app does not coincide 100 % with the 2 wallets I have found with electrum. The transactions I found on the segwit electrum wallet are not shown in the coinbase wallet app.
The transactions I found on the legacy electrum wallet are shown in the coinbase wallet app, but not all of them and some that are listed in the coinbase wallet up are not present in the electrum wallet.
So there's clearly a mess going on here. Same seed, same wallet and not all txs show up?
I am able to retrieve another wallet (always with the same seed), this time with bc1 addresses, I open it and I see some transactions, so this wallet was used too. Unfortunately though the address I am looking for is not there.
So, you created a "standard" wallet in Electrum, using the seed your friend provided, selected "BIP39" and then selected the "Native SegWit (p2wpkh)" option... and doing this, you see transaction history, but not the address you're looking for? 
I've just been trying with the Coinbase App to create addresses/wallets from different derivation paths, and I just don't see a way to do it... Regardless of the "Active Wallet" setting in "Settings -> Advanced"... it only seems to use the standard m/84'/0'/0' and m/44'/0'/0' addresses for BTC... the "Active wallet" setting only seems to affect ETH as far as I can tell.
Although I don't think Coinbase provides a way to get addresses beyond the gap limit, you could try increasing the number of addresses generated by using the method that was posted earlier:
There's also a chance that the address is at higher index than Electrum's default of 20,
in that case, try to create more addresses by typing this in the console (View->Show Console):
Change "False" to "True" if you want to generate change addresses.
in that case, try to create more addresses by typing this in the console (View->Show Console):
Code:
[wallet.create_new_address(False) for i in range(200)]
Then restart Electrum.Change "False" to "True" if you want to generate change addresses.
He certainly screwed it up by using a legacy wallet and giving out a segwit address.
I don't think so... the Coinbase app lets you swap between Segwit and Legacy in the "same" wallet. You simply tap the "SegWit"/"Legacy" tabs above the QR code shown on the "Receive" screen.Did your friend ever use the Coinbase website? I'm wondering if they had used the "walletlink" feature or something... and the "mystery" address was one that was actually from the Coinbase website and not one generated by the app?
I am using the website https://iancoleman.io/bip39/ on an offline computer, telling it to scan for thousands of addresses but the one I want is not listed there.
I have selected bip84 and it doesn't show up. Then I tried to put "1" in the "account" box but it's not there either.
I have selected bip84 and it doesn't show up. Then I tried to put "1" in the "account" box but it's not there either.
m/84'/0'/0' == bip84 == bc1 == zpub
If you have the keys you do not need any coinbase wallet at all.
You can import them into any application that is able to handle the protocol and your friends funds will be spendable immediately.
If you have the keys you do not need any coinbase wallet at all.
You can import them into any application that is able to handle the protocol and your friends funds will be spendable immediately.
Hey by the way what do you mean with bip84? When he made the wallet and writes the seed in electrum (12 words), you can't click next. So I told him to press the option button and select bip39 so that he could click next (and also because as far as I know the seed phrase is taken from the bip39 list).
Could this bip84/bip39 be the issue???
Probably you are currently looking at the external and change addresses, while you are searching for the address that belongs not to external or change, but to the root, or master key.
This is the hard key from 256 bits HMAC512 and all child addresses will be generated from the other 256bits HMAC512 chain code.
The chance that you found a used address that belonged to someone else is neglectable, so this means that you are looking into the right direction you most likely only need to look up one more level.
You can also use the public key to generate a variety of non standard addresses but since this seems to be a online wallet issue the chances on non standard protocol implementations are very slim.
I have a slight feeling that your friend has a seed from a previous or older wallet.
It can help to ask him how many wallets he made and if he still has the seeds to all of them.
For now i would advise you to use the keypair, or public key to generate an extended address list including roots.
I am able to retrieve another wallet (always with the same seed), this time with bc1 addresses, I open it and I see some transactions, so this wallet was used too.
It's possible then there are further segwit (bc1) accounts which were generated using this seed phrase. Electrum should have detected them, but you can try doing it manually just to be sure. Recover your seed phrase on Electrum, and on the Script Type page, select "native segwit (p2wpkh)" but change the derivation path from m/84'/0'/0' to m/84'/0'/1'. You could also try changing to 2', 3', 4', etc. just to be sure.If that still shows up blank, then the options are either a very nonstandard derivation path, an additional passphrase which has been forgotten about, or the wrong seed phrase entirely.
I now have the seed and I have entered the wallet.
When I enter the wallet though, the addresses to receive are in the form of 15..., 14... whereas the address that contains the money is bc1.
With that seed, I tried to access the wallet with electrum. I click "detect existing account" and it finds me a bip44 legacy wallet (but the address I need is bc1 so not legacy), I open it anyway and I do see the old transactions.
I am able to retrieve another wallet (always with the same seed), this time with bc1 addresses, I open it and I see some transactions, so this wallet was used too. Unfortunately though the address I am looking for is not there.
What else can I do?
He certainly screwed it up by using a legacy wallet and giving out a segwit address.
When I enter the wallet though, the addresses to receive are in the form of 15..., 14... whereas the address that contains the money is bc1.
With that seed, I tried to access the wallet with electrum. I click "detect existing account" and it finds me a bip44 legacy wallet (but the address I need is bc1 so not legacy), I open it anyway and I do see the old transactions.
I am able to retrieve another wallet (always with the same seed), this time with bc1 addresses, I open it and I see some transactions, so this wallet was used too. Unfortunately though the address I am looking for is not there.
What else can I do?
He certainly screwed it up by using a legacy wallet and giving out a segwit address.
Is there a way to verify if the seed he's using is in charge of that address? If that is so, then it must be a derivation path issue, right?
Maybe signing a message?
Maybe signing a message?
Unfortunately, no.
The only way would be to bruteforce it yourself.
This would mean you'd need a short script to try each derivation path until you are successful. You should find someone to code it for your for ~10$.
If you decide to do so, make sure to check the code tho.
Is there a way to verify if the seed he's using is in charge of that address? If that is so, then it must be a derivation path issue, right?
There's no wallet which will automatically do this. It is the same situation as your suggestion above regarding creating an unsigned transaction. If you haven't found the correct derivation path, then the wallet won't be able to either.Scanning or searching for addresses with zpubs is unlikely to be successful either since if the derivation path uses hardened derivation at any point, as all BIP 44/49/84 paths do, you cannot derive these levels using only the zpub.
You could potentially write some code which would scan thousands of derivation paths, but you would need your friend's seed phrase or zprv (master private key).
Edit: Actually, a bit of searching seems that this exact feature is currently in development for Electrum - type in your seed, and it scans for a variety of commonly used derivation paths and script types to see if have been used. Perhaps this could help your friend - https://github.com/spesmilo/electrum/pull/6219
Is there a way to verify if the seed he's using is in charge of that address? If that is so, then it must be a derivation path issue, right?
Maybe signing a message?
Maybe signing a message?
But you know that a different seed phrase will generate a different "@username", if it's new to their server, it will ask you to create a new user.
And Folio claimed in the OP that his friend generated the same wallet username when he restored from the backup seed phrase.
True. I had forgotten about that part of it... it's been a busy couple of weeks with lots of very early starts And Folio claimed in the OP that his friend generated the same wallet username when he restored from the backup seed phrase.
So, I'm wondering if it just a Legacy/SegWit thing then?
I have a suspicion that o_e_l_e_o is correct... It's starting to look a lot like the classic "have (valid) seed for a different wallet" scenario
But you know that a different seed phrase will generate a different "@username", if it's new to their server, it will ask you to create a new user.And Folio claimed in the OP that his friend generated the same wallet username when he restored from the backup seed phrase.
For the BIP39 passphrase, I don't think Coinbase wallet app has an option to enable it;
the PIN however is just an app security feature and I tried to load the same seed phrase with different PIN and both generated the same addresses.
If Folio's friend is telling the truth, this is an issue with Coinbase wallet app itself (I'll take it with a pinch of salt).
I have a suspicion that o_e_l_e_o is correct... It's starting to look a lot like the classic "have (valid) seed for a different wallet" scenario
I've seen a few instances on these forums of users that have been experimenting/testing wallet applications and have setup multiple wallets (accidentally or deliberately). Then they end up with a situation where they think they have the correct seed mnemonic written down, but are in fact using a wallet derived from a completely different seed.
Inevitably, "Murphy's Law" strikes and they lose access to the wallet (computer failure, lost password etc)... then they go to restore... only to discover the seed they have derives a completely different wallet and they're like "W.T.F??!?"
As I mentioned earlier, it's possible that the wallet was doing strange stuff and had both Legacy/SegWit addresses... and so was actually using multiple derivation paths for the one wallet... or it was generating SegWit address off "Legacy" derivation paths or vice versa...
So, the address that you couldn't find... it it SegWit or Legacy?
I've seen a few instances on these forums of users that have been experimenting/testing wallet applications and have setup multiple wallets (accidentally or deliberately). Then they end up with a situation where they think they have the correct seed mnemonic written down, but are in fact using a wallet derived from a completely different seed.
Inevitably, "Murphy's Law" strikes and they lose access to the wallet (computer failure, lost password etc)... then they go to restore... only to discover the seed they have derives a completely different wallet and they're like "W.T.F??!?"
With his public key I can see these addresses and his transactions, but not the one he wants.
https://talkimg.com/images/2023/11/15/zfO4I.png
What I find a bit confusing tho, is that apparently you found some transactions/coins... but not others??!? https://talkimg.com/images/2023/11/15/zfO4I.png
As I mentioned earlier, it's possible that the wallet was doing strange stuff and had both Legacy/SegWit addresses... and so was actually using multiple derivation paths for the one wallet... or it was generating SegWit address off "Legacy" derivation paths or vice versa...
So, the address that you couldn't find... it it SegWit or Legacy?
I'm still not convinced this is a derivation path issue. As HCP showed on the previous page, a seed phrase generated by the Coinbase Wallet App imports no problem in to Electrum and Ian Coleman, and both show the correct addresses at the default derivation path. He also shouldn't have two zpubs - there is only one master private key and one master public key per seed phrase.
This sounds more like either a seed phrase or a passphrase issue to me than a derivation path issue.
This sounds more like either a seed phrase or a passphrase issue to me than a derivation path issue.
Yes it's weird that coinbase didn't show that address once he logged back in.
The 2 different public keys are explained (I think) by the fact that he manually modified the derivation path on electrum.
I'm still not convinced this is a derivation path issue. As HCP showed on the previous page, a seed phrase generated by the Coinbase Wallet App imports no problem in to Electrum and Ian Coleman, and both show the correct addresses at the default derivation path. He also shouldn't have two zpubs - there is only one master private key and one master public key per seed phrase.
This sounds more like either a seed phrase or a passphrase issue to me than a derivation path issue.
This sounds more like either a seed phrase or a passphrase issue to me than a derivation path issue.
Would it work?
No. The wallet still needs to know which derivation path to look for the private key in question. It will only be able to sign the transaction if you have found the correct derivation path and told the wallet what it is. If you can't find the path, then the wallet won't be able to either.Has he had any response from Coinbase yet?
No, nothing.
Isn't it absurd that you can't find the derivation path having the address? No one tells you to write down your derivation path when you open a wallet.
Would it work?
No. The wallet still needs to know which derivation path to look for the private key in question. It will only be able to sign the transaction if you have found the correct derivation path and told the wallet what it is. If you can't find the path, then the wallet won't be able to either.Has he had any response from Coinbase yet?
Jump to: