connect VS data

It returns some html that has some javascript. The JavaScript being returned is not defined in the extension repo - but the trezor connect repo https://github.com/trezor/connect

In this thread, you can find different troubleshooting tips: https://github.com/trezor/connect/issues/784.

"Manifest not set. Read more at https://github.com/trezor/connect/blob/develop/docs/index.md"

Starting with Trezor Connect 7, we have implemented a new feature — Trezor Connect Manifest — which requires that you as a Trezor Connect integrator, to share your e-mail and application url with us. This provides us with the ability to reach you in case of any required maintenance. This subscription is mandatory. Trezor Connect raises an error that reads "Manifest not set. Read more at https://github.com/trezor/connect/blob/develop/docs/index.md" if manifest is not provided.

The Trezor window that comes up when you confirm a transaction in metamask, quickly disappears and the transaction gets stuck in metamask. It is described in complete detail here, here and here.

Anyone familiar with this issue? https://github.com/trezor/connect/issues/784

Trezor Connect Changelog

We've been receiving reports that some of you are still experiencing this issue with Metamask. If it's your case, it would be helpful if you could describe your setup (OS, browser and its version, Trezor firmware, MM version) in this post. The details will be shared with our testers.

Hi, what browser and what version of Metamask you’re using? This issue was fixed by Metamask devs in the 10.8.0 version. You can find more details at https://github.com/trezor/connect/issues/784

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.