trezor-firmware VS bitbox02-firmware

That kind of confirmation does exist, it’s called using a hardware wallet, such as those made by Trezor and others.

https://trezor.io/

Trezor | Software Engineer (Embedded, Firmware, React) | Prague, CZ | Remote | https://satoshilabs.com/careers

Description copied from the Firmware Developer role, have a look at the careers page for many more details!

We’re Trezor (https://trezor.io/), a leading company in crypto security, that has pioneered the hardware wallet industry. As a Firmware Developer, you’ll help us develop firmware that runs on thousands of Trezor devices all over the world. Basically, our products put people at ease knowing their digital assets are safe. Your job here will consist of providing new features, fixing bugs, and solving difficult technical problems. Along the way, you'll gain valuable insights into the practical application of cryptography.

We picture you as a skilled developer who has a background in Python programming and has completed at least some side projects in Rust. A solid understanding of C will also be necessary.

Together, we will bring new hardware wallets to life, including a flagship Trezor product with Bluetooth connectivity. Sounds exciting, right?

Keyword: Bitcoin

PS: You can apply directly using the Satoshi Labs careers page or email me at [email protected] and I will make sure to forward your application to the relevant people in our HR department.

https://trezor.io/ - Easy to use, no matter how new in Bitcoin you're.

Added (November 2021): https://github.com/trezor/trezor-firmware/pull/1903

Next thing to have is a hard wallet if you haven’t already like a Ledger or a Trezor and let it sit there. That’s the safest thing to do! Also, there’s always been a risk of KYC (Know Your Customer) on CEXes as mentioned several times. This was all meant to be decentralized and keep our identity under wraps and retain that anonymity that crypto was originally designed for… and you get a hold of your keys.

https://trezor.io/ - Easy to use, no matter how new in Bitcoin you're.

where "x.y.z" is the VERSION of trezor (aka TrezorCTL) you are trying to install. See the version history when picking a version. "Oldest" is not necessarily "best". You'll want to pick a version that was released around the same time your Trezor-1 was last updated.

I'm looking at this, you can see a comparison when you scroll down: https://bitbox.swiss/bitbox02/

Bitbox02 - https://bitbox.swiss/bitbox02/

I also implemented BIP-85 just recently.

Here's the repository for the firmware of BitBox02: https://github.com/digitalbitbox/bitbox02-firmware

Complementary to that, you can also download the official release from https://github.com/digitalbitbox/bitbox02-firmware/releases and install it manually using command line tools, after verifying it is legit by reproducing it. Or build the app yourself after checking that the bundled firmware is correct.

At the bottom of this page, they concisely explain what they mean for each entry in the table and why they give that specific score. For this in particular, they consider the setup easier because you can backup to an (offline) SD card instead of writing it down manually.

I decided on this: https://shiftcrypto.ch/bitbox02/

There you go: https://github.com/digitalbitbox/bitbox02-firmware/pull/1069

The firmware code is open source and can be found here. The official releases are built from this code in a reproducible fashion. The community is able to verify that currently the only two ways of exporting the seed are via the 24 words displayed on the BitBox02 screen or onto a microSD card inserted directly into the device. If there are other unintended ways, it might be a bug, and should be sent to us as part of our bug bounty program.