trezor-firmware VS data

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've purchased a Trezor model T from what I believe is the official Trezor website (https://trezor.io/). Is it rational for me to have a slight fear that it isn't a legit trezor and maybe the chip is compromised, possibly being able to send off my seed to an unknown party?

you can compare the fingerprints here: https://github.com/trezor/data/blob/master/firmware/1/releases.json

The update of the bootloader has failed. You can download the bootloader from here https://github.com/trezor/data/tree/master/bootloader and try installing it from the SD card manually. 3. "invalid firmware header" or "invalid firmware hash"

Download your firmware, "1" is for Model 1, "2" is for Model T. https://github.com/trezor/webwallet-data/tree/master/firmware

Been researching hardware (cold) crypto wallets like ledger and trezor and it seems like all of their software relies on systemd. Has anyone had success using a hardware crypto wallet with Void?

Download firmware v2.4.3 from firmware/2/trezor-2.4.3.bin

Now, on to fingerprints. All the firmware update logic is driven by a file called releases.json (trezor-one version). This file was last updated in commit #d4aaa1b signed with GPG key 4AEE18F83AFDEB23 belonging to @vdovhanych. In this file is a 256bit checksum called fingerprint. Now through the git GPG signature we can verify the authenticity of this file, and through the fingerprint we can verify the authenticity of the firmware.

I've been able to send XLM now. To do so, I downgraded the device to firmware 2.4.2. You can do so by downloading trezor-2.4.2.bin from here and then install it as 'custom firmware' through the Trezor Suite (make sure you have your seed backup in case it bricks your device). I then installed the desktop version of the Exodus wallet. After pairing the Exodus wallet with the Trezor device, I was able to send XLM with Exodus. However, other assets on the Stellar network cannot be sent this way. If you want to try it, do so at your own risk. It might be easier to wait and hope for an official hotfix.

An older article in the wiki pertaining to deterministic builds seems to suggest that the following commands can reproduce the fingerprints shown in the Trezor-1 releases.json and the Trezor-T releases.json

Manual download here https://github.com/trezor/webwallet-data/tree/master/firmware

When attempting to install the latest version of the RPM from https://github.com/trezor/webwallet-data/tree/master/bridge/2.0.27 I get the following error indicating a problem with the key. It appears the RPM is signed but there is a problem finding the public key.