Topic: Help Me Recover My Bitcoins. (Read 867 times)

That was something I considered... but thought it unlikely as Trezor has been using "M" addresses for Litecoin SegWit for about a year if I recall correctly... certainly this blog post regarding the subject is dated June 2017.

Given the seed came from a Trezor T, which was only released earlier this year, I'd say it was "unlikely" that this 3 address was a LTC P2SH address. Nevertheless, I have checked the basic derivation path (m/49'/2'/0') against the "3" address provided converted to an "M" address (as that is what Ian Coleman's tool and Electrum-ltc are producing) just in case... sadly, without success.

.. Well ok then. Electrum does validate BIP 39 seeds properly, and, AFAIK actually follows the BIP 39 spec to the word.

The seed is likely a BIP 39 seed then.

So this is what we know:

• 12 word BIP 39 seed
• BIP 49 derivation path is default (m/49'/0'/0')
• Came from a Trezor T
• OP used Trezor web interface

Did OP use any other accounts besides the default account?

I'll take a look through the Trezor code and docs to see if there is any unexpected behavior like generating with different purposes or coins or whatever.

One last thing. Litecoin's P2SH addresses used to also start with a 3. So for segwit, a Litecoin address looks identical to a Bitcoin address. Is it possible that the key was generated on the Litecoin derivation path somehow?

Well... this falls into the "unlikely" category then I guess... unless both Electrum and Ian Coleman's Mnemonic tool are not validating BIP39 seeds properly...

BIP39 seed validated:



Tried changing "work" to "word" and Electrum detects as invalid:



Without BIP39 selected, it is detected as SegWit:



In other news... the OP has told me that they are using a Trezor T... apparently the "T" defaults to using a 12 word seed (unlike the Trezor One), hence my confusion about 12 vs. 24 word seeds. OP has also mentioned that they had not used Electrum prior to trying to fix this issue. Unfortunately, this puts us back at square one.

It's possible, but it's also rather unlikely.

BIP 39 wallets are not supposed to just accept any seed. Rather they are supposed to warn you if a seed is invalid. However some wallets may not be implemented in this way and may not actually be checking the validity of a seed before using it. I suspect that is actually what is happening here.

Is this really possible?
Both formats use different schemes to calculate the checksum, is it possible for there to be anintersection between both?

Well that's the really curious thing... this 12 word seed shows up as "valid" according to BIP39 wallets??!? So this combination of words is apparently a valid BIP39 seed... AND a valid Electrum SegWit seed...

For my mind, the fact that it is only 12 words is what makes me believe that it is more likely an Electrum seed than a Trezor seed. Not conclusive proof, I know... but still.

Anyway, the address provided by the OP was a "3" address... so it should be a P2SH-P2WPKH address (from a Trezor). However, using m/49'/0'/0' with the provided seed as BIP39 doesn't yield the address... neither does any of the "Account" values from 0-10... including change address chains (External/Internal = 1)

And of course, using the seed as an Electrum SegWit seed generates a wallet with "bc1" addresses.

So, I'm left with the conclusion that the OP has mixed up his seeds somehow...


EDIT: apparently Trezor T's default to 12 word seeds as opposed to 24 word seeds like Trezor One. Also, OP has never used Electrum... Sooooo... the mystery deepens

Electrum uses its own seed format which is different from the BIP 39 format that basically every other wallet uses (included Trezor). Such seeds should not be valid on a Trezor. Furthermore, if Electrum recognizes it properly as a Segwit seed, then the seed is most definitely an Electrum one as their seeds distinguish between segwit and non-segwit. Has OP tried using the seed in Electrum? The derivation paths that should be tried are m/49'/0'/0' (BIP 49) and m/44'/0'/0'/ (BIP 44).

I think it might be possible that the OP doesn't actually have a Trezor seed.

OP gave me a seed that is only 12 words long... and I thought that Trezor seeds were 24 words by default? Additionally, their seed is detected by Electrum as being a valid Electrum "SegWit" seed!!?!

I've tried the most likely derivation paths... and nothing seems to work. Aside from BCH and LTC... were there any other coin types that used "3" addresses? I'm trying to figure out how the OP might have got a "3" address without it being a Bitcoin one.

Any ideas guys?

EDIT: Turns out that the new Trezor T defaults to using 12 word seeds... unlike the Trezor One which uses 24 words.

Have you tried linking your Trezor to Electrum (view-only using the "hardware wallet" option)? Or restore using your seed? Use the correct derivation path for SegWit addresses,
Enable the tab "console" type:If it said "true" the address belongs to that seed.

---

Why is it still receiving small amount of Bitcoins until this week?

You can used this way to check your wallet! But In my opinion you should be careful when storing in bulk! Should back up your wallet and check the backup before using!

sorry to hear that, mate. but also thank you for pulling such thread so i can be more cautious in the future. good luck!

Sorry HCP, i just read it now, i didn't use a passphrase, i'm sure of it, i would remember.

Did you read my post in the other thread?

Did you use a BIP39 passphrase when you originally setup the Trezor? If so, the seed on it's own won't recover your funds. You MUST uses the same passphrase to be able to access your funds.

The instructions for the BIP39 tool:

You'll need a Linux system for this. Ubuntu is easy to use.
In a Linux OS, open a terminal window and type the following (press enter after each line):
 Then let it run.
PS do not insert the brackets in or

An example usage is:

Code:

  ./mnemonicgen correct horse battery staple | ./bip39bruteforce 3HZgtFDmfwohrz2cRfzSECxeszpEzJqiYY

Replace "correct horse battery staple" with your seed.

---

As for the ypub tool, Blockonomics block explorer supports Segwit HD addresses so you can search ypub: http://www.blockonomics.co/

You can also use Shivaenigma's port of pycoin that has support for ypubs.
Run

Code:

ku  -s 0/0-5 -a

Replace ypub with your ypub
Replace 0/0 with the node you're checking
Replace 5 with the number of addresses you want to create

Xynerise, that is exactly what happened to me EXACTLY!!!! what can be the problem and how can i use the extended public key to find the address, the extended public key is YPUB NOT XPUB and i haven't found any program that supports segwit extended public key, please i am not good with python or scripting so no suggestion regarding writing a script for me. I can give the pub to anyone who can help me check for it.

I am absolutely convinced you will be able to recover your coins, because it's fairly common that a device reads zero because of the wrong derivation path. (side note, a pretty nice software enhancement would be to have in the Trezor a function to clue the user in that he has coins in one or more derivation paths OTHER THAN the one he is currently displaying)

This BIP explains the derivation paths concept, may be worth your time to read it.

https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki

Unfortunately, there are numerous perturbations. Trezor uses BIP39, Electrum uses sort of BIP42. Then there's segwit and non-segwit....

Suppose you get another Trezor with the same firmware version, do not update the firmware, and load your word sequence. Your coins pretty much have to come up. You are recreating exactly the same environment. (And if they don't, seems this definitively proves you have a problem with the word sequence not being right. In this case you proceed to permutation of each word one by one, starting with common misspells)

I have a couple of Trezors that I have not used or looked at in a couple months, used them for testing and verification. Could be one/both of them have the version number firmware of interest.

Do you recall the firmware version before, and after, your update that started the problems? Analysis of the problem would preferably start with knowledge of those specific versions.

I actually believe you because something like that has happened before And he still hasn't solved the problem.

However, on the off chance that the problem is from your seed and not a bug in Trezor's derivation path mechanism, then you can try their BIP 39 brute force tool
Clone the repo and run the script to check if the possible mnemonics that differ with a word generate your address.
It's worth a shot even though you're sure your seed is correct.

-Did you buy trezor from the official store? If not, you should consider your hardwallet compromised and the seed originally generated could be someone else's Wallet.
 When you updated the firmware, your trezor was" fixed" and is now working properly.

-Another option is to use de extended public key, this was already suggested before and did not help. The extended public key generates all possible public addresses for that seed. If the address is not there, the seed is wrong.

-its possible that you misspelled some word. Raccoon or raccon for example.
Here is a list of all possible words in English. Check each of your 24 .

https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt

-supposing your trezor is complety broken.  have you tried to recover your seed in another wallet using these 24 words? This could solve.

You guys still don't get it, irregardless of the trezor i should be able to restore my seed in another wallet but it still doesn't work, honestly i don't care if the trezor messed up the update i just want my funds back, maybe i am using a wrong derivation path. Someone give me something i can do other than contact trezor support page, i have the right seed and that should count for something, i have only used the device twice and its just a month old.

I don't think it would be spotted that easily.
While its true that a simple error would be found fast, a (almost identical) word would not always attract attention that fast.
In fact, if both words are part of the wordlist, it depends on the checksum (a part of the last word) wether it can be spotted or not.




Upgrading won't help when OP already can access his trezor and can't access his coins/addresses in ANY wallet with his seed.