Sending MAID from a Trezor hardware wallet

I’m not sure where he stated the Trezor address starts with a one. Only that the OmniWallet address that was imported starts with a “1”.

His Trezor uses BIP49, so it must be a SegWit address — with a “3”:

Anyhow, I think OmniWallet just does not import the private key as BIP49, so you end up with a legacy address in OmniWallet.

Sorry you are right. My bad reading skills exposed. Crawls back into my corner

I’ve not a Trezor but if you can get BIP39… then look to the 1st part of

from step 6 then

Once you have your recovery phrase you will need access to the Bip39 generator

looks straightforward.

From a quick search perhaps that tool can give the private key

The 24 words are basically your master private key. There are programs, e.g., that can compute the private key for each bitcoin(cash)/litecoin/dash/zcash/ethereum address that your Trezor uses.

can Maidsafe coins be stored as ETH token ? or is that something the team should provide us with , first ?

1 Like

It was a cheap shot at the expense of the OP, to promote the idea MAID should be moved to ERC20.

But no MAID is as it has always been a OMNI token.


Hi guys. To clarify, the Trezor address starts with a 3. I have added it into OW as a Watch Only address and it shows my BTC and MAID balance fine, and is represented correctly starting with a 3 etc. Mav, I did actually already go through the process you suggested above, the “Import Address with Private Key” in the Add Addresses section, but it created a new address instead of adding the key to the correct address. And the new address starts with a 1 :O( It seems stupid that Omni Wallet can easily create the correct address (starting with a 3) as a Watch Only address and see the account balance of MAID and BTC, but not import that same address and allow me to send the MAID as well, even if I provide the Private Key?


Agreed. Omniwallet should have two import options for private keys - one option to import the private key as a ‘normal’ p2pkh address starting with 1 and another option to import the private key as a ‘segwit’ p2wpkh-in-p2sh starting with 3.

The same private key is used for both addresses so omniwallet must decide which address to use and it chooses the ‘normal’ type. Omniwallet doesn’t offer the option for it to be the segwit type. Understandable but very frustrating.

Glad you could find your private key but a shame it can’t be used in omniwallet.


One thing you can try is the same thing this guy did, but they have a problem of using multisig whereas yours is a problem of using segwit:

Basically the answer is to contact omniwallet support.

A second thing to note is the place to patch this problem is here:


this method needs to be modified to import the p2wpkh address instead of the p2pkh address.

I tried to do it ‘live’ in the developer tools of my browser but that’s not really a good way to solve your problem! Better to fork the code and patch; that would solve the problem.

1 Like

I am having the exact same issue with my ledger. Totally my mistake but would love to see if you resolve this issue.

1 Like

I am not certain this works but I am currently having the same issue. I discovered this article and seems to match what you are looking for.

1 Like

I currently have my maidsafecoins stored in a bitcoin address generated from on my Mac and would like to improve my security if/when they appreciate in value. If I’m reading this correctly, I could reset my TREZOR and write down the recovery seed, then send my maidsafecoins to a new bitcoin address. This is good for me at least for the next year or two.

Once I’m ready to spend the maidsafecoins (or burn them for Safecoins) I can use the OMNI sweep all command and Electrum to move the coins from the TREZOR (whose private key has never been exposed until now) to the Safecoin burn address.

Is that correct? Is there a better to accomplish this?

At this time DO NOT STORE on Trezor. Trezor generates segwit addresses and at this time omniwallet cannot import the addresses. It can watch them but it cannot import the private key to give a sewit address.

There is no need to sweep since the import of the private key that gave you allows you to send from that address

Just keep the paper wallet you generated from and import that private key into omniwallet when you want to send your coins somewhere. Remember to have some BTC at the same address.


Thanks for the reply. Just curious… it does appear that Trezor lets me generate bitcoin addresses that start with “1” under the legacy wallet. I assumed those would be alright to use with the steps I mentioned above. Is that incorrect? You are correct, however, that the standard wallet generates addresses that start with “3” which I assume are the Segwit ones.

On the surface it sounds correct. Test it with a very small amount of MAID (like one coin) and see. It’ll cost you 2 transactions (a dollar or two) to test, but save you a lot of heartache if it fails. Obviously use another address after your test since you will have imported the private address into omniwallet.

AND report back to us with the exact steps you took so others can learn.



You mean what I said?

It came across as you prompting Maidsafe to do the transfer to ERC20 (seeing as the OP was about MAID). At the expense of the opening poster’s serious situation. and considering that bad things happen with ERC20 too as with every other coin.

Wasn’t trying to do anything at the expense of anyone

All I did was offer my apologies to him, and use it as a chance to push for a better future so this doesn’t keep happening to people

Maybe you use the word “at the expense of” in a different way than I do. I see people using words differently often, depending on which country I’m in. So having to get used to that.

“at the expense of” means with harmful, jabbing, intent, etc. where I come from at least.


I saw it as using his misfortune to make a point/push that MAID should go to ERC20. Which you now indicate was never your intention.

Anyhow this is getting out of hand now and is becoming a lot worse than either ever meant our comments to be. I am at least digging a hole deeper that we may not come back out of. :wink:

I understand that you would not be malicious etc or put anyone down. Sorry if my comments appear worse than they were meant to be.


It’s a fair and relevant point - the fact Omni haven’t integrated seg-wit properly leaves a huge risk for Omni tokens to be sent to an address where the tokens can no longer be accessed (as seen in this thread… and I nearly did it once).

Though not perfect, I don’t think a similar issue exists with ERC20. This won’t be the last time we see this problem, unless Omni get their act together soon.


Me too, I remember looking into MAID / Trezor compatibility and ran into this same thing, causing me to toss my first Trezor back in the day