trezor-hardware VS keepkey-firmware

However if you want, you can open it up and then 3d-print a new case.

If you want to repair, here is the description of the hardware: https://github.com/trezor/trezor-hardware/blob/master/electronics/trezor_model_t/index.md

Trezor is completely open hardware and open software. That means you don't have to trust, you can verify. You can even build everything yourself if you wish to prevent potential supply chain attacks.

Trezor is fully open source. Software, Firmware, PCB Schematics even the plastic case design! The whole shabang. Yes, this means you can build your own trezor if you wanted to. That's the kind of hardcore security dedication that we should support.

Open hardware https://github.com/trezor/trezor-hardware

You can also build the entire Trezor hardware wallet yourself. The files for the 3d printable case is on Trezor's github, along with the schematics for the circuit boards and all of the little electrical parts needed to make it. https://github.com/trezor/trezor-hardware https://github.com/trezor/trezor-firmware

open source firmware, hardware

KeepKey's the cheapest out of the three and it's the one I use. It looks like there's development again on it at least looking at the github activity here: https://github.com/keepkey/keepkey-firmware

Thanks again for your replies! I've created an issue in the keepkey-firmware github but I don't expect that that's going to happen any time soon. There are a lot of open PR's and there does not seem to be a lot of presence from keepkey staff. I hope I'm wrong, but in the mean time I'll be looking out for other wallets that actually do support BSC.

Actually KeepKey does support BSV at the firmware level. See https://github.com/keepkey/keepkey-firmware/blob/master/include/keepkey/firmware/coins.def#L23

Where's the release log that details the changes for firmware 7.1.0? It's not tagged in github repo and it's also missing from the release section as well: https://github.com/keepkey/keepkey-firmware/releases

If you do get one here are couple things you'll probably have to do before it's functional: - On Mac/Linux you'll probably have to add appropriate udev rules so apps can communicate with KeepKey without sudo. See this - On Windows you may need to install usb driver https://zadig.akeo.ie if it's not picking KeepKey up. Just check device manager after plugging in KeepKey to tell. - You'll have to update the bootloader and firmware. I recently got a second KeepKey and it came loaded with bootloader 1.0.3 and firmware 4.0.0, both of which are quite old. After updating to 1.1.0 and 6.7.0 respectively, haven't had any issues using it. - For Windows on any chrome-based browser you may need to enable chrome://flags/#new-usb-backend. I found the behavior to be less quirky with it on. For example, on shapeshift platform some functions like address display on device and device reset wipe doesn't work unless this is on. The usb user prompt will also show unknown for me instead of keepkey when pairing unless this flag is on.

Note that firmware support is still required for this to work. If Shapeshift official support is important to you I suggest pestering them to merge this PR into their upstream repo.