Topic: [ESHOP launched] Trezor: Bitcoin hardware wallet - page 252. (Read 966173 times)
missing gold color
First eloxed (colored) prototypes of casings. Color isn't stable enough so it isn't perfect yet, but we're making a progress!
Shield contains OLED display, two buttons and USB HID chip. All parts are freely available in shops or you'll be able to buy assembled shield from us.
That's it? Would've thought it'd be a bit more complicated. Awesome!
Shield contains OLED display, two buttons and USB HID chip. All parts are freely available in shops or you'll be able to buy assembled shield from us.
There won't be any "development boards" for testing, but soon there'll be Raspberry shield with python software for DYI hackers, which will be wire-compatible with Trezor device.
What will one need to assemble a shield?
Yubikey works in the most naive way - it act like USB keyboard and when you press the sensor, it simply prints out the signature to stdin. In the oposite Trezor works with custom protocol encapsulated to generic HID messages.
They're doing both, but using feature reports to communicate
when can I order one device for testing?
There won't be any "development boards" for testing, but soon there'll be Raspberry shield with python software for DIY hackers, which will be wire-compatible with Trezor device.
Don't things like the Yubikey use HID too?
Yubikey works in the most naive way - it act like USB keyboard and when you press the sensor, it simply prints out the signature to stdin. In the oposite Trezor works with custom protocol encapsulated to generic HID messages.
Don't things like the Yubikey use HID too?
yes they do
Another option ("cleaner", theorically speaking) is WinUSB on Windows, then accessing it using libusb on Linux & Mac.
Both are hacks, but the generic HID hack is more popular IMHO.
Another great thing about HID is that it'll almost always work on Windows, even if a policy is used to disable typical USB devices (mass storage ...)
Don't things like the Yubikey use HID too? Both are hacks, but the generic HID hack is more popular IMHO.
Another great thing about HID is that it'll almost always work on Windows, even if a policy is used to disable typical USB devices (mass storage ...)
when can I order one device for testing?
Another option ("cleaner", theorically speaking) is WinUSB on Windows, then accessing it using libusb on Linux & Mac.
Both are hacks, but the generic HID hack is more popular IMHO.
Another great thing about HID is that it'll almost always work on Windows, even if a policy is used to disable typical USB devices (mass storage ...)
Both are hacks, but the generic HID hack is more popular IMHO.
Another great thing about HID is that it'll almost always work on Windows, even if a policy is used to disable typical USB devices (mass storage ...)
Which one, which has also straightforward support across all platforms? HID is a bit limiting, still it has the best user experience available.
Edit: HID has a generic class, which mean that the device is not identified as any known device (keyboard, mouse), but application still can use (driver-less) HID protocol to talk with the token. Don't worry that your mouse pointer will move during transaction signing ;-).
Edit: HID has a generic class, which mean that the device is not identified as any known device (keyboard, mouse), but application still can use (driver-less) HID protocol to talk with the token. Don't worry that your mouse pointer will move during transaction signing ;-).
Using HID means you're basically emulating a keyboard or mouse, right? Are you sure that's a good idea? Isn't there a more direct protocol that can be used?
+ work on the low level 'byte transport layer'. Probably using javahidapi.
at least you shouldn't have too many issues with this, as long as you're using interrupt transfers (I've seen some oddities using control transfers on OS X). Integration on Windows XP, 7, Vista 32/64, OS X and Linux 32/64 (with the proper udev rules to let anyone write to the USB device) has been pretty much transparent for me.
Good to hear. I noticed you were using javahidapi so was going to get in touch to see what your experience was.
How do you pronounce Trezor (I have to copy/paste the z since the key broke 
)? Is it pronounced like treasure or razor?
)? Is it pronounced like treasure or razor?It's more like as "treasure". International Phonetic Alphabet writes it as /trězoːr/ (source http://en.wiktionary.org/wiki/trezor)
ahaaa, nice. Didn't get that before.
We finally decided to choose name for our hardware wallet. After considering all options from bitcointalk contest and after talking with some marketing specialists, we chose name Trezor.
Good choice 
How do you pronounce Trezor (I have to copy/paste the z since the key broke )? Is it pronounced like treasure or razor?
)? Is it pronounced like treasure or razor?It's more like as "treasure". International Phonetic Alphabet writes it as /trězoːr/ (source http://en.wiktionary.org/wiki/trezor)
There is a fair bit to do to get everything to work, in rough order:
+ finish off the existing MultiBit work and get it out the door to 'clear the decks'.
+ work on the low level 'byte transport layer'. Probably using javahidapi.
+ produce BIP32/ HD wallet code, for eventual inclusion in bitcoinj. I am liaising with Chris Rico on this.
+ The Trezor wallet will be (in MultiBit) watch only so there will be some work there.
+ Probably write a new 'Create Wallet' wizard to improve the user experience.
+ There will also be some UI work (extra tabs etc) I expect too.
+ finish off the existing MultiBit work and get it out the door to 'clear the decks'.
+ work on the low level 'byte transport layer'. Probably using javahidapi.
+ produce BIP32/ HD wallet code, for eventual inclusion in bitcoinj. I am liaising with Chris Rico on this.
+ The Trezor wallet will be (in MultiBit) watch only so there will be some work there.
+ Probably write a new 'Create Wallet' wizard to improve the user experience.
+ There will also be some UI work (extra tabs etc) I expect too.
Although I know very well that today was an "epic facepalm" day for myself (have guaranteed that no-one will ever think that I am Satoshi) I think that CIYAM Open could be very helpful for managing this (will be starting to "set up shop" on Monday and please understand that *zero* bitcoins are stored at ciyam.org and that the Project owners control all their own bitcoins in whatever way they wish to so the "brain fart" that I had today could never affect another project that is hosted there).
The first 10 projects hosted will be "fee free for life" so hope you guys will at least take a look at it (btw - I think the name is great - 1 BTC very well spent!).
+ work on the low level 'byte transport layer'. Probably using javahidapi.
at least you shouldn't have too many issues with this, as long as you're using interrupt transfers (I've seen some oddities using control transfers on OS X). Integration on Windows XP, 7, Vista 32/64, OS X and Linux 32/64 (with the proper udev rules to let anyone write to the USB device) has been pretty much transparent for me.
Jump to: