keystone-se-firmware VS Keystone-developer-hub

Keystone's firmware of gen2 is already open source, and gen3 I think is being released as 100% open source soon. So you can check everything, and build it yourself. Otherwise you can double-check the checksum of the downloaded binary before you put it into your Keystone.

that's because it's verifiably not true - the chip they're using isn't documented (huge red flag when mentioning using a SE) and their "source code" still contain binaries blob for critical functionalities such as https://github.com/KeystoneHQ/keystone-se-firmware/blob/bitcoin/source/driver/ecdsa_v2.lib

A: The answer is NO. To make sure there's no access of the firmware, we have made our firmware open-sourced for the whole community to examine that we didn’t have any backdoors or misconduct from ourselves. The firmwares are released by Keystone official to ensure that no malicious third party can get into your device. We also use QR code data transmission which is transparent and verifiable to prove that there’s no secrets inside the data.

We use a EAL 5+ bank-grade Secure Element. We cannot reveal the secure element to public because of the IP of the manufacturer. But to be as transparent as possible, we have open-sourced the Secure Element firmware and the datasheet (We are the first hardware wallet company who did so). If you are hoping to further verify the operations of the Secure Element, we can send you a development board under NDA. You can find more infos in this blog.

The signature nonce generation is closed-source in Keystone: https://github.com/KeystoneHQ/keystone-se-firmware/issues/8

open source firmware

open source hardware