Oh sorry. I see what you mean. The client just displays the 3x3 boxes for you to click on.
Yes. It's quite straightforward concept, but hard to explain without any visualization.  |
|
|
|
It is unfortunate that you are sending the pin matrix to the client. Because then, a hacked client can figure out your pin. If you don't send the pin matrix to the client, then there would be no way for a compromised client to figure out your pin. I think that would be a better solution. Please consider it.
Of course we are not sending the matrix to the client. If we did, it would defeat the whole purpose of it. I meant "indices" instead of "numbers" in this sentence: (and clicks will be translated to numbers by software) |
|
|
|
I suggest you do a server-side check on a new pin to make sure there's no 0 in it so that one doesn't accidentally make this mistake.
You are entering PIN during the initialization phase of the device. If there is no 0 in the matrix, you can't enter it. Right now, you'd have to find the spots that have 1,2,3, and 4 and then figure out the index of those spots. In this case it's 9872.
If client has the proper implementation of pin matrix you won't be entering numerical indices (like 9872), but you'll click on blank squares (and clicks will be translated to indices by software). This will be much more intuitive and so there will be no need for reverse mapping you mentioned. P.S. Is there a better place (forum/irc/etc) for suggestions like these?
Probably https://bitcointalk.org/index.php?topic=296078.0 |
|
|
|
you'll need to make sure your users use a cryptographically strong password - at least 128 bits of entropy
If you've read the whole thread you would have learned that the plan is to use BIP32 - maybe a modified one, so the "metadata" tree would not collide with the main address tree. |
|
|
|
Remember that in future wallets will hold not only keys and labels, but also things like signed payment requests (receipts), micropayment channel state, info for dispute mediation and so on. Lots of stuff.
That's something we'd like to tackle on some of the upcoming BIPs. Basically it is just defining which path(s) in BIP32 tree will be used for various purposes (PGP, SSH, etc.). We can also change "Bitcoin seed" to "Meta seed" (or sth similar) in the HMAC call during initialization of the root to make sure we won't be mixing address tree with meta tree. |
|
|
|
Ok so I take it the only connection I have to make is the USB port on the shield?
Right. |
|
|
|
The little (micro?) USB on the RasPi is power and I think you can use either of the 2 stacked USB for the 'trezor' cable back to your PC.
For power you can use either of microUSB connectors. If you want to communicate with TREZOR, use the one on the shield (it will also provide power for the RasPi). |
|
|
|
How does that work? Is there a second firmware (bootloader)?
Yes. |
|
|
|
Is this the case? EDIT Clarification: can the authenticity of the firmware be verified?
Yes. If you flash unofficial firmware on the device it will print a warning during the boot-up (which you have to confirm). |
|
|
|
|
Trust issues are not problem. Handling complaints is. Lots of people want to become resellers, because they see easy money, but when we ask about how they plan to provide support and handle complaints they are suddenly speechless. :-)
|
|
|
|
I'm not familiar with Open Street Map. Can anyone edit the info, like on Wikipedia, or does the business owner have to keep the listing updated?
OpenStreetMap is built on the very same principles as Wikipedia, see http://en.wikipedia.org/wiki/OpenStreetMap |
|
|
|
|
Another option would be:
"trezor-" + hex(hash(serial number of the device || master public key from device)) + ".wallet" (where || means concatenation)
I think we have to decide if we want to treat two different devices loaded with the same seed as the same wallet (first option) or not (second one).
|
|
|
|
|
Thanks to all of you for your support and that you add new venues to OpenStreetMap.
Now we have 327 venues listed on CoinMap which makes CoinMap the biggest map/listing of places accepting Bitcoin! Big round of applause for everybody involved!
I think now it's the time to come up with CoinMap logo. If you have any ideas, please, post them here! (ideally as a SVG vector or PNG bitmap with transparency with size at least 1024x1024 px).
By posting an image here you agree that it can be used exclusively by CoinMap for promoting its activities. Thank you!
|
|
|
|
I chose not to implement that optimization in strong-arm, since it really wasn't much of a bottleneck, and I personally prefer transparent code over optimized code. Easier to audit and avoid bugs.
This optimization makes code 5x faster on x86. Even more on ARM devices. That's a significant improvement. Unfortunately, it makes also code 3x-4x bigger, that's why there are macros to turn it on/off. |
|
|
|
How much will this cost?
Use Google. |
|
|
|
What's the schedule again?
The schedule is to deliver in October (metallic version) and November (plastic version). |
|
|
|
Any update on the ETA of our pre-orders? Everything still on track ? Not that i need the device now , but a little information on the progress would be nice Yes, everything is still on track and we stick to the schedule. |
|
|
|
I think it would be nice if future Trezors could have a standard audio jack so that it could be used with any smartphone, new or old.
We played with that idea, but there is a big problem with Android phones - the market is just too fragmented and it's very hard to get communication through audiojack working with all these different models. Also TREZOR would still need a battery which we decided to skip in the first model. |
|
|
|
|
Show Posts
