I just completed another compatibility test on the Trezor that others may be interested in.
Previously I had tested the Trezor/Wallet32 compatibility on a 12 word list.
I wanted to use a 24 word list on my Trezor but before I did I wanted to make certain that if I lost my Trezor I could recover using Wallet32.
I set up my Trezor with 24 words, entered the same 24 words into Wallet32 and yes! got the same sequence of Bitcoin addresses on both wallets.
Final step, now that I am convinced I have a recovery path if I lose the Trezor: wipe it one more time and create my final 24 word list using the Trezor and then I can start using it to store my gargantuan BTC holdings.
Topic: [ESHOP launched] Trezor: Bitcoin hardware wallet - page 186. (Read 966173 times)
I have a simple idea. I will do this when I receive my trezor.
I will write down the backup words on 3 pieces of paper, to have a distributed solution reducing risk of theft:
If the backup "sentence" is 24 words, you could do it this way:
backup 1: words 1-16
backup 2: words 9-24
backup 3: words 1-8 and 17-24
Put these backups in 3 different locations and you will have created a "2 out of 3" system for your Trezor
I will write down the backup words on 3 pieces of paper, to have a distributed solution reducing risk of theft:
If the backup "sentence" is 24 words, you could do it this way:
backup 1: words 1-16
backup 2: words 9-24
backup 3: words 1-8 and 17-24
Put these backups in 3 different locations and you will have created a "2 out of 3" system for your Trezor
from now on, I'm going to put my Trezor in every drink I have.
Please don't mention that during RMA process ;-). Seriously, I'm happy that TREZOR survives accident like this, but I would not do that on daily basis :-D.
ok, not every drink, maybe just last drink after it actually dies, if that ever happens.
The price is to high 1btc = 600$+
hmm maybe a new price will Trezor is many people buy
hmm maybe a new price will Trezor is many people buy
Maybe help to make up for this by doing something that lets everyone know that the a preorder trezor is a preorder trezor. That way they will be collectable some day.
The price is to high 1btc = 600$+
hmm maybe a new price will Trezor is many people buy
hmm maybe a new price will Trezor is many people buy
from now on, I'm going to put my Trezor in every drink I have.
Please don't mention that during RMA process ;-). Seriously, I'm happy that TREZOR survives accident like this, but I would not do that on daily basis :-D.
from now on, I'm going to put my Trezor in every drink I have.
I want that one!
Today we've received first batch of Classics for testing. As you can see, Trezor quite likes swimming in Club Mate ;-)
My thought was that you guys might want to collaborate to standardise the way everyone uses the Trezor
We'll address this in the upcoming SLIP document. SLIP stands for SatoshiLabs Improvement Proposal and it will be a repo for specifications which are not suitable for inclusion into BIP repository for various reasons.
My current idea is to follow BIP-0043 and set the deterministic hierarchy path to m/N'/a'/b'/c'/d' where N will be the spec number and a,b,c,d are values derived from hash(domain_name) so each domain will get different key automatically. (BitId and BitAuth don't deal with automatic assigning of keys from deterministic pool at all and assume that user will do that manually, which is very clumsy and non-intuitive resulting in reuse of login keys similar to password reuse we see today).
Trezor is already able to do this: https://twitter.com/GreenAddress/status/479939415088062464
Ah, this is good to see.
My thought was that you guys might want to collaborate to standardise the way everyone uses the Trezor, so that the different systems are as interoperable as possible (which extended private key from the chain is selected as the ID, or whether to specify different xprivs for distinct purposes, whether the individual public keys or the extended public key is used as the SIN, etc). I see your point though, the Trezor is openly documented, and so people are free to implement however they choose to.
Any plans to work with BitID or BitAuth
Actually it is BitID's or BitAuth's turn to integrate with hardware wallets.
Quote
so a Trezor could be used to store identities and authorise web access etc?
Trezor is already able to do this: https://twitter.com/GreenAddress/status/479939415088062464
Any plans to work with BitID or BitAuth, so a Trezor could be used to store identities and authorise web access etc?
So what is the estimated price range of plastic and a metal?
thousands asked already, but nobody knows yet. we will have to wait one more month to see...
I tried out wallet32 and loved it.
Then, you issued an update to the code, and now wallet32 will no longer install on my phone due to an application signature issue.
I even researched this for you and I believe the problem is that you recently switched to the latest JDK7 which has a known application signing issue.
I think all you need to do is go back to the earlier JDK6 and reissue the application to the Google store, then I should be able to download it and use it once again.
The ap signing issue along with some possible solutions is discussed here:
http://stackoverflow.com/questions/2519374/published-android-apk-gives-error-package-file-was-not-signed-correctly
Then, you issued an update to the code, and now wallet32 will no longer install on my phone due to an application signature issue.
I even researched this for you and I believe the problem is that you recently switched to the latest JDK7 which has a known application signing issue.
I think all you need to do is go back to the earlier JDK6 and reissue the application to the Google store, then I should be able to download it and use it once again.
The ap signing issue along with some possible solutions is discussed here:
http://stackoverflow.com/questions/2519374/published-android-apk-gives-error-package-file-was-not-signed-correctly
NOTE: this issue has been fixed.
I was able to download the latest version of Wallet32 to my Android phone and so far it appears to work (again)!
So we are back to having a totally workable solution to the "lost Trezor" problem: just enter your words into Wallet32.
Disclaimer: this will reduce the security of the Trezor. But if the Trezor is lost that is exactly what you want to do - move your coins.
So what is the estimated price range of plastic and a metal?
Now stuck at "ImportError: cannot import name enum_type_wrapper"... maybe my protobuf is too old.
Protobuf has to be version >= 2.5.0. Also please move devel discussion to the mentioned list. Forum is horrible for more complex discussions because of the missing threads.
FYI there's experimental Trezor support in Electrum now: https://groups.google.com/forum/#!topic/trezor-dev/PsGKYo6wjcw
Give it a try and feel free to report issues in trezor-dev mailing list! It is still very raw, but I was able to perform basic operations like receiving and sending coins.
Give it a try and feel free to report issues in trezor-dev mailing list! It is still very raw, but I was able to perform basic operations like receiving and sending coins.
I tried this, but got a bit stuck...
I installed https://github.com/trezor/python-trezor ("python2.7 electrum" was complaining about missing cmdtr module, which I figured out comes from python-trezor). Installing python-trezor didn't help. I ended up copying "cmdtr.py" file from python-trezor to my electrum folder.
Now stuck at "ImportError: cannot import name enum_type_wrapper"... maybe my protobuf is too old.
Can you get this message to the wallet32 dev team?
I have no other contact to Ken than this same mailbox. I recommend you to send that email again or create issue on https://github.com/ksedgwic/Wallet32 . Sometimes it is easy to get lost in all those emails...
Can you get this message to the wallet32 dev team?
I have no other contact to Ken than this same mailbox. I recommend you to send that email again or create issue on https://github.com/ksedgwic/Wallet32 . Sometimes it is easy to get lost in all those emails...
Jump to: