[NOW AVAILABLE] BTChip / Ledger HW1 : Bitcoin Hardware Wallet in a USB smartcard

[Muhammed Zakir]

Hi can I use the same wallet I use for my other ledger products on this easily?

If you backup the seed, you can restore it in any of your HW.1.

[1714749743]

1714749743

[1714749743]

1714749743

[1714749743]

1714749743

[Wotan777]

I tried to install btchip-python under Win 7, 64 bit.

- installed python-2.7.9.amd64.msi
- added to PATH C:\Python27\;C:\Python27\Scripts\
- installed Microsoft Visual C++ VCForPython27.msi
- pip install cython
- pip install hidapi
- downloaded https://github.com/walac/pyusb/archive/pyusb-master.zip
- cd pyusb-master
- python setup.py install
- downloaded https://github.com/LedgerHQ/btchip-python/archive/btchip-python-master.zip
- cd btchip-python-master
- python setup.py install
- cd samples
- python getFirmwareVersion.py
[hang up]

I tried to run pyusb again:
cd pyusb-master\tests
python testall.py
PyUSB ValueError: No backend available

I Googled to this error, and found: http://stackoverflow.com/questions/5152133/pyusb-backend-not-accessible
It said that "You need to install libusb-1.0, libusb-0.1, or openusb as a backend to pyusb."

I downloaded libusb-win32-bin-1.2.6.0
cd libusb-win32-bin-1.2.6.0\bin
inf-wizard.exe

created a driver kit for
Vendor ID        Product ID      Description
0x2581            0x2B7C          Plug-up

Then installed the created driver.

Now pyusb tests run without errors.
Also, btchip-python is operational, gets back the firmware version, but not always:

btchip-python-master\samples>python getFirmwareVersion.py
=> e0c4000000
<= 010001040e014e9000
1.4.14

btchip-python-master\samples>python getFirmwareVersion.py
=> e0c4000000
Traceback (most recent call last):
  File "getFirmwareVersion.py", line 25, in <module>
.
.
    timeout
  File "C:\Python27\lib\site-packages\usb\backend\libusb0.py", line 381, in _che
ck
    raise USBError(errmsg, ret)
usb.core.USBError: [Errno None] libusb0-dll:err [_usb_reap_async] reaping reques
t failed, win error: "A device connected to the system doesn't operate properly"

The next test runs only ONCE conrrectly, then gives an error, then gangs up.
After pwercycle, the same...

\btchip-python-master\tests>python testConnectivity.py
btchip firmware version:
=> e0c4000000
<= 010001040e014e9000
{'compressedKeys': True, 'version': '1.4.14', 'specialVersion': 0}
some random number from the dongle:
=> e0c0000014
<= f673c10e1ce482848366cbc75fe42cd61f41ea3f9000
['0xf6', '0x73', '0xc1', '0xe', '0x1c', '0xe4', '0x82', '0x84', '0x83', '0x66',
'0xcb', '0xc7', '0x5f', '0xe4', '0x2c', '0xd6', '0x1f', '0x41', '0xea', '0x3f']

\btchip-python-master\tests>python testConnectivity.py
btchip firmware version:
=> e0c4000000
Traceback (most recent call last):
  File "testConnectivity.py", line 29, in <module>
    print(app.getFirmwareVersion())
  File "C:\Python27\lib\site-packages\btchip_python-0.1.14-py2.7.egg\btchip\btch
ip.py", line 363, in getFirmwareVersion
    response = self.dongle.exchange(bytearray(apdu))
  File "C:\Python27\lib\site-packages\btchip_python-0.1.14-py2.7.egg\btchip\btch
ipComm.py", line 79, in exchange
    self.device.write(0x02, tmp[offset:offset + 64], 0)
  File "C:\Python27\lib\site-packages\usb\core.py", line 898, in write
    self.__get_timeout(timeout)
  File "C:\Python27\lib\site-packages\usb\backend\libusb0.py", line 499, in intr
_write
    timeout)
  File "C:\Python27\lib\site-packages\usb\backend\libusb0.py", line 552, in __wr
ite
    timeout
  File "C:\Python27\lib\site-packages\usb\backend\libusb0.py", line 381, in _che
ck
    raise USBError(errmsg, ret)
usb.core.USBError: [Errno None] libusb0-dll:err [_usb_reap_async] reaping reques
t failed, win error: Egy rendszerhez csatlakoztatott eszk÷z nem műk÷dik.

btchip-python-master\tests>python testConnectivity.py
btchip firmware version:
=> e0c4000000
[HANG UP]



Please help! How to go on?

[btchip]

Please help! How to go on?

The Python API is broken on Windows, and I didn't have the opportunity to have a look yet.

[Muhammed Zakir]

Please help! How to go on?

The Python API is broken on Windows, and I didn't have the opportunity to have a look yet.

It is working good for me. Was it broken after you made an commit(if any)?

[Wotan777]

@Muhammed Zakir:

It is working good for me. Was it broken after you made an commit(if any)?

In my case under Win7 64 bit btchip-python is unstable, can't be used together with Electrum.

Did you use libusb-win32-bin-1.2.6.0?
Did you compile cython with Microsoft Visual C++ VCForPython27?
Or you used a MinGW environment?

[Muhammed Zakir]

@Muhammed Zakir:

It is working good for me. Was it broken after you made an commit(if any)?

In my case under Win7 64 bit btchip-python is unstable, can't be used together with Electrum.

Did you use libusb-win32-bin-1.2.6.0?
Did you compile cython with Microsoft Visual C++ VCForPython27?
Or you used a MinGW environment?

Yes, I use libusb but don't remember the version and I installed Cython using Python setup.py command and it used Visual C++.

[dasource]

Couple of questions...

1. How much more secure in the mobile app for second factor compared to the security card? (I can see the potential concern with the security card; is the Ledger team confident that the mobile app provides sufficient protection?)
2. I understand the second auth is not available if the nano/hw1 is used for multi-sig .. any plans to support that or is this a design decision?
3. What Key Derivation Paths are used by Ledger Wallet direct and Coinkite? should for example one need to manually pull those keys if said service is down etc.

Keep up the great work

Thanks

[jeannemadrigal2]

I just got a nano, it should come in the mail tomorrow and I am pretty excited about it.

I have a suggestion, I would like to see the support of altcoins, several different types of wallets, etc on the same device.  I know maybe this is a hard thing to do but I am throwing it out there as and idea perhaps for a future product.

[btchip]

Couple of questions...

1. How much more secure in the mobile app for second factor compared to the security card? (I can see the potential concern with the security card; is the Ledger team confident that the mobile app provides sufficient protection?)

the mobile app lets you verify the full transaction (including amount) so it's definitely better than the security card. Regarding its security a malware would have to compromise both the host and the phone simultaneously to trick you into signing something you didn't want to.

2. I understand the second auth is not available if the nano/hw1 is used for multi-sig .. any plans to support that or is this a design decision?

it's a design decision for this product as it'd make things awkward if for example you use your phone and the Ledger Nano for multi signature. On our next products supporting a screen (Trustlet, Blue) we'll be able to consistently verify the transaction.

3. What Key Derivation Paths are used by Ledger Wallet direct and Coinkite? should for example one need to manually pull those keys if said service is down etc.

Ledger Wallet uses standard BIP 44 on account 0 for the time being, Coinkite let you pick your own derivation path on the imported xpub then derives incrementally each key. I think you should be able to retrieve the current index on their signing page.

Keep up the great work

thanks, we'll do exactly that

I just got a nano, it should come in the mail tomorrow and I am pretty excited about it.

I have a suggestion, I would like to see the support of altcoins, several different types of wallets, etc on the same device.  I know maybe this is a hard thing to do but I am throwing it out there as and idea perhaps for a future product.

we plan to make it easier for people to support altcoins in the next firmware for third party wallets, if we get enough code space for that. Some people already worked on it with the current firmware, but it's not deployed yet.

[dasource]

3. What Key Derivation Paths are used by Ledger Wallet direct and Coinkite? should for example one need to manually pull those keys if said service is down etc.

Ledger Wallet uses standard BIP 44 on account 0 for the time being, Coinkite let you pick your own derivation path on the imported xpub then derives incrementally each key. I think you should be able to retrieve the current index on their signing page.

Thanks, in reference to the above; Not specific to Ledger but a general note. I noticed CoinKite starts its default at 1 ... going forward with more implementation and users being able to select which Subkey (at CK) on BIP44 path one could end up with clashes where addresses are being reused (say across multiple wallets using different implementations etc). Any thoughts on that?

[btchip]

Thanks, in reference to the above; Not specific to Ledger but a general note. I noticed CoinKite starts its default at 1 ... going forward with more implementation and users being able to select which Subkey (at CK) on BIP44 path one could end up with clashes where addresses are being reused (say across multiple wallets using different implementations etc). Any thoughts on that?

Sorry, missed your post. Yes, some implementations can reuse key paths. I don't think it's a major problem as that would happen in multisignature use cases with different signers.

Now for the good news, I should have finally fixed Windows support properly and added some updated build instructions on https://github.com/LedgerHQ/btchip-python - also Electrum 2.3.2 binaries should work fine (when they're out)

Electrum 2.3.2 also supports Ledger Security Card validation, allowing you to use it after a regular Ledger Wallet initialization.

[AussieHash]

Are you at liberty to share whether we can expect a HW-2 or Nano-2 with upgraded specs, and perhaps integrated U2F support ?

[btchip]

Integrated U2F is probably not going to happen for the Nano, as that would mean starting a new production run and have people buy the new one. So not very interesting. We're not working on a new Nano, we want to keep this one up to date with as many new features as we can.

We expect to have a Blue design available by the end of the year, beginning of the next, including U2F (and UAF if the specification is stable enough)

In the meantime the public TEE application beta should start in a few weeks (for Samsung Galaxy S6, Note 4 N910C/N910H owners), and probably another surprise during summer.

[nogreedy]

Hello,
That's great you use OpenBazaar to sale Ledger products.
Congrats.
http://bazaarbay.org/contracts/bfd50bcd4e743f243b435a15aa634b1fd45e19c9
https://twitter.com/openbazaar/status/609152199621521408
https://twitter.com/LedgerHQ/status/610355906421870592

[Mitchell]

I tried to update my old HW1 so that I could use the Ledger Wallet application and the firmware update got stuck after the bootloader part where you are ask to remove the device and reconnect it. I can't get passed the reconnet part as my device isn't seen/recognized anymore. The GreenAddress application on my Android phone doesn't recognize it either. Any ideas, hints, tips?

[btchip]

I tried to update my old HW1 so that I could use the Ledger Wallet application and the firmware update got stuck after the bootloader part where you are ask to remove the device and reconnect it. I can't get passed the reconnet part as my device isn't seen/recognized anymore. The GreenAddress application on my Android phone doesn't recognize it either. Any ideas, hints, tips?

The device is in bootloader mode and you'll have to be able to finish flashing it on a computer before being able to use it again on Android.

If you're running Linux, you might want to check that your udev rules have been updated to support the 1807 and 1808 product IDs - http://support.ledgerwallet.com/knowledge_base/topics/ledger-wallet-is-not-recognized-on-linux

If you're running Windows (especially Windows 7), the wrong driver might be installed - http://support.ledgerwallet.com/knowledge_base/topics/ledger-wallet-is-not-recognized-on-windows-7

[Mitchell]

I've installed all the 64 bit drivers and everything worked before doing the update (I wouldn't be able to update without the drivers). I've refreshed the update page multiple times, rebooted my pc, removed and readded the HW1. All to no avail.

[btchip]

I've installed all the 64 bit drivers and everything worked before doing the update (I wouldn't be able to update without the drivers). I've refreshed the update page multiple times, rebooted my pc, removed and readded the HW1. All to no avail.

the device changes completely when in bootloader mode, so it might be necessary to force the driver manually when this happens, or to use Zadig to force it again (the installer didn't really work for bootloader mode either)

[gsupp]

Has anyone used their HW.1 with Electrum 2.4 on Ubuntu? Is there a guide available anywhere?

[tricass]

i have a duo hw1 and have set both up to use the same seed and can pair multiple devices to the wallet. however, it appears transaction authorisations are only push out successfully to the last paired device. is there a way to get this to work for more than one paired device?