[LEGACY] Digital Bitbox Hardware Wallet Support

[wbobeirne]

Re-implement Digital Bitbox decrypting and send support from v3

[wbobeirne]

I've hit a wall on this one, I'm getting the very opaque client error code 4, DEVICE_INELIGIBLE (See here) It seems v3 is also facing this problem, and my implementation is identical, so I'm not sure how this was ever working. @douglasbakkum if you are available to talk this out, you can find me on the MEW slack or shoot me an email on my profile.

[douglasbakkum]

@wbobeirne Will send an email.

Note that the Digital Bitbox will only communicate with a website that has https://www.myetherwallet.com as a base URL (or https://digitalbitbox.com) (https://www.myetherwallet.com/test or like that will work) - this prevents phishing attacks. Maybe you are testing using a different server?

[Zwilla]

Does this mean, that everyone who want to run an absolute cold storage can’t use a digital bitbox?
If yes = stupid!

Because if you can not trust a bitbox itself it is worthless!!! Take a look at ledger wallet, this is an absolut 0-Trust wallet!

[wbobeirne]

In our email correspondence, I requested that localhost also be whitelisted for running MEW offline.

[wbobeirne]

The Digital Bitbox team just shot me this reference implementation of it running in Electron by directly interfacing with HID: https://github.com/digitalbitbox/ElectronDemo. This means that Digital Bitbox support will probably be limited to Electron until they update the firmware to whitelist mycrypto.com, but this will allow it to work offline.

[tapir]

Digital bitbox supports mycrypto since firmware 3.0.0. It's been quite a while since it's released. This is a feature originally existed in MEW. Why isn't it enabled yet?

[SharonManrique]

Added to Asana