Quote from: goatpig on September 18, 2014, 03:22:54 PM

Quote from: CHAOSiTEC on September 18, 2014, 10:58:29 AM

so im assuming that after trezor support is included in armory, its going to be easy to implement other hardware wallets, since the ground work has been done, am i correct?

Not necessarily. There are 4 steps to integrating a hardware wallet:

1) Implement the standard. That's a one time cost, but there's no knowing which BIPs future hardware wallets will require.
2) Communication layer. With Trezor that part is overly simple (for us, we use Python on the front end), but again, no guarantee other wallets will go down that path.
3) UI integration. A portion of the Trezor code can be recycled for new wallets, but maybe not as large as we hope.
4) Unit tests. Depending on how many features the hardware wallet supports and its API, this can take its sweet time.

The good side is that we will most likely release support for these devices in the form of plugins, so it won't have to wait for a major release.

Nice, since ive been using armory for.. well ages, lol, and i have just recieved my HW.1 hardwarewallet (btcchip.com) and they use python, so that should make it easy to implement, since its python based pluginish :-p (electrum has support for it in dev version)