What's the schedule again?
The schedule is to deliver in October (metallic version) and November (plastic version).
Topic: [ESHOP launched] Trezor: Bitcoin hardware wallet - page 230. (Read 966173 times)
The schedule is to deliver in October (metallic version) and November (plastic version).
What's the schedule again?
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.
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
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.
Just had a thought. What if, in the future, cellphones had a 'Trezor slot' similar to a SD-card slot. You'd slide your micro-sized Trezor-card into the phone and could not only sign bitcoin transactions, but perhaps it'd have keys for auto-encrypting phone communications too. Perhaps the display would be tied into the cellphone display--it would temporarily take it over, let's say, and have buttons on the phone reserved purely for cryptographic signing that the rest of the system doesn't have access to.
Just a thought and imagining of what the future may hold. Wish all luck to the Slush and the Trezor! Can't wait to get one soon
Just a thought and imagining of what the future may hold. Wish all luck to the Slush and the Trezor! Can't wait to get one soon
The video from OHM2013 is up:
http://wipkip.nikhef.nl/events/OHM/video/d2-t5-07-20130801-1700-trezor_bitcoin_hardware_wallet-stick.m4v
http://wipkip.nikhef.nl/events/OHM/video/d2-t5-07-20130801-1700-trezor_bitcoin_hardware_wallet-stick.m4v
See also the BIP32.5 thread on Bitcoin development.
Here's the thread for anyone is like me, interested but not subscribed.
Great find! We'll look into it.
See also the BIP32.5 thread on Bitcoin development. It would be preferable if it also only produced even signatures, so that the signatures produced won't have to be postprocessed to remove the malleability attacks. The device will probably have the choice to combine entropy source from it's hardware and from the computer. The worst case (when you'll have hacked machine): The entropy will be as strong as the hardware RNG (which should be still enough for common use) and there won't be a way how to malicious machine can guess the seed . In standard case: You'll have perfect entropy created by combination of hardware generator and your entropy source provided by the computer.
PLEASE USE DERANDOMIZED DSA. There is absolutely no reason to have MORE wallet leaks. DSA signing information leaks are completely preventable.
If trezor uses randomized DSA its users will have no way of knowing that their device isn't just slowly leaking out an encrypted copy of their master root key a bit or two at a time in their signatures.
Has this whole Android pseudo-random generator bug had any effect on the Trezor?
No.
If there is a similar software glitch that's found in the Trezor after product is shipped, will there be ways to upgrade firmware? (I believe there is, just checking)
Yes, there is a firmware update mechanism.
Has this whole Android pseudo-random generator bug had any effect on the Trezor?
If there is a similar software glitch that's found in the Trezor after product is shipped, will there be ways to upgrade firmware? (I believe there is, just checking)
If there is a similar software glitch that's found in the Trezor after product is shipped, will there be ways to upgrade firmware? (I believe there is, just checking)
Its relative..These are more expensive.
http://www.dellamoda.com/Coach-Signature-Embossed-Slim-Billfold-Wallet-for-Men-CMW100.html?gclid=CMe8xtCg_bgCFU5xQgodJCwAMg
http://www.dellamoda.com/Coach-Signature-Embossed-Slim-Billfold-Wallet-for-Men-CMW100.html?gclid=CMe8xtCg_bgCFU5xQgodJCwAMg
Nice, once it is released, will it be cheaper? $100 is a lot.
Just an update on progress for Trezorj (the Java library for communicating with Trezor devices).
I've got a pre-alpha version of the API fleshed out and communicating with a Trezor Shield on an RPi. It only does this over a socket at the moment but it's enough to start seeing some life in the wee beastie.
You can download the code or read the project wiki for more information.
We're one step closer to Jim winning his bet.
I've got a pre-alpha version of the API fleshed out and communicating with a Trezor Shield on an RPi. It only does this over a socket at the moment but it's enough to start seeing some life in the wee beastie.
You can download the code or read the project wiki for more information.
We're one step closer to Jim winning his bet.
hey stick did you ever see my post about how the next step for you guys ought to be the creation of a hardware devise that protects people from rogue devises that look like trezors on the outside but on the inside are actually designed to compromise the security of computers that they interface with.
And how would this work?
Hm maybe by having only enough memory to pass along a single digital signature and requiring the retailer to manually authorize each transmission with a hardware button. im no expert though. perhaps i should have prefaced my comment by saying "assuming such a thing is possible"
hey stick did you ever see my post about how the next step for you guys ought to be the creation of a hardware devise that protects people from rogue devises that look like trezors on the outside but on the inside are actually designed to compromise the security of computers that they interface with.
And how would this work?
hey stick did you ever see my post about how the next step for you guys ought to be the creation of a hardware devise that protects people from rogue devises that look like trezors on the outside but on the inside are actually designed to compromise the security of computers that they interface with.
The combination of such a devise with the trezor would really truly bring bitcoin down to grandmas level. your paycheck from work would automatically be deposited onto your trezor and inorder to spend your coins you just plug it into the little terminal at the grocery store and press confirm. this would take bitcoin from being prohibitively complicated to significantly less complicated than the traditional banking system in one fell swoop with the introduction of one little hardware devise. (it would be two hardware devises if you hadnt already created the trezor but since you have its one)
The combination of such a devise with the trezor would really truly bring bitcoin down to grandmas level. your paycheck from work would automatically be deposited onto your trezor and inorder to spend your coins you just plug it into the little terminal at the grocery store and press confirm. this would take bitcoin from being prohibitively complicated to significantly less complicated than the traditional banking system in one fell swoop with the introduction of one little hardware devise. (it would be two hardware devises if you hadnt already created the trezor but since you have its one)
Jump to: