stellarterm VS data

> All of the above exchange links that I've visited required account registration and login, which means that they are not decentralized

Next you'll tell me that Ether is centralized because Coinbase requires registration and login.

You've been looking at clients, i.e. independently developed user interfaces to the Stellar DEX. You can interact directly with the DEX here:

https://laboratory.stellar.org/

Or you can roll your own. Stellarterm is open source, could be a good starting point:

https://github.com/stellarterm/stellarterm

If you prefer algorithmic trading, there is Kelp:

https://github.com/stellar/kelp

> Claiming to be decentralized and then requiring signup is dishonest.

I find it hard to believe that you honestly don't understand the difference between an independently developed client and the decentralized exchange which it connects to. Regarding automated market making, see Kelp above.

> There are no non-custodial stablecoins

This subthread started with your recommendation of USDC, a custodial stablecoin.

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.