Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add readme to the firmware folder #86

Merged
merged 1 commit into from
Jul 17, 2024
Merged

Conversation

komret
Copy link
Contributor

@komret komret commented Jul 17, 2024

Resolves #61

@komret komret requested a review from mroz22 July 17, 2024 10:16

File `authenticity.json` is the source of truth for public keys used in the device authenticity check. This feature is ony available for devices with a secure element, i.e. not T1B1 and T2T1. File `authenticity-dev.json` holds debug keys to be used in conjunction with [Trezor Emulator](https://github.com/trezor/trezor-user-env). The keys are regularly copied to Trezor Suite by a [Github action](https://github.com/trezor/trezor-suite/actions/workflows/update-connect-config.yml) so that they can be accessed offline.

Folder `translations` holds translation blobs. These are not available for T1B1 and older firmware versions. Trezor Suite downloads translations from [https://data.trezor.io/](https://data.trezor.io/). During the initial firmware installation, Suite downloads and installs a firmware translation corresponding to the Suite language, if available. The file is silently updated during subsequent firmware installations and during any `TrezorConnect.getFeatures` call, i.e. during Suite startup. If a translation download fails, no error is shown and the outdated version is kept, which may result in some strings not being translated.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

true, but more specifically - it is updated during virtually any TrezorConnect call that is using device.

@komret komret force-pushed the chore/add-firmware-readme branch from b6ecd3e to 6492773 Compare July 17, 2024 10:25
@komret komret force-pushed the chore/add-firmware-readme branch from 6492773 to acb2139 Compare July 17, 2024 10:25
@komret komret merged commit 6a8f482 into master Jul 17, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add README to firmware folder
2 participants