Editing Comparison of Hardware Wallets (section)

= Other Criteria =
{| class="wikitable"
|-

! Criteria
! Details
|-

! Security audited
| The security audit of a hardware wallet depends on the scope and the organization conducting it. It is not a simple yes or no question. Please refer to the {{audit_mininav}} for more information.
|-

! Certification
| Similar to above.

* The secure element might be certified. See [https://bitcointalk.org/index.php?topic=5304483 Secure Element in Hardware Wallets].
* The hardware wallet itself may or may not be certified.

These are an indicator but should not be taken alone as a seal of quality, because, see next column.
|-

! Vulnerabilities 
| [https://thecharlatan.ch/List-Of-Hardware-Wallet-Hacks/ List of Hardware Wallet Hacks]
|-

! Warning if running custom firmware.
| Users running the official firmware should get a warning if an attacker flashed a custom firmware from their device's bootloader.
|-

! Installation of custom firmware deletes storage.
| This is a security feature to avoid a malicious custom firmware stealing the private keys.
|-

! Detach storage
| Can storage be detached, duplicated and re-attached? If de-soldering of the storage chip is possible, this may or may not be a security issue because a custom firmware by an attacker might decrypt, steal the private keys.
|-

! Bitcoin only
| Attack surface reduction, complexity reduction to ease security audits by only supporting 1 cryptocurrency, most likely [[Bitcoin]].
|-

! Multiple cryptocurrency support
| If the user wants to use other cryptocurrencies such as [[Ethereum]].
|-

! Secure Element
|
|-

! Private Key never leaves Secure Element
| Yes / No
|-

! Private Key never leaves Device
| Yes / No
|-

! Country of Incorporation
| Of the hardware wallet vendor.
|-

! Country of Production
| Of the hardware wallet vendor.
|-

! Supply chain attacks
| 
|-

! Track record
| History of past security issues and their handling.
|-

! Quality of Entropy
| Low entropy can result in private keys getting compromised through bruteforce attacks. See also [[Dev/Entropy|entropy]].
|-

! User supplied additional entropy.
| For better entropy.
|-

! Multisig support.
|
|-

! Multisig compatibility with other hardware and software wallets.
| For diversification of multisig, not relying on one single vendor, one single point of failure only.
|-

! USB / SD / Micro-SD Card Backup Support
| For diversification of multisig, not relying on one single vendor, one single point of failure only.
|-

! Native desktop app 
| Or only a (wrapped) web interface.
|-
 
! Mobile app 
|
|-

! Wallet compatibility
|
|-

! [[Hardware_Wallet_Security#Insecure_Display_versus_Secure_Display|Secure Display]]
|
|-

! Big Display
| For ease of readability of long cryptocurrency addresses.
|-

! Display can show QR Codes
| To receive funds.
|-

! Camera can scan QR Codes
| To send funds.
|-

! Can show account number (address) on Secure Display.
|
|-

! Can show balance on Secure Display.
|
|-

! Can show transaction history on Secure Display.
|
|-

|}