arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-14 03:30:02 +00:00
Code Issues Releases Wiki Activity
13,093 Commits 336 Branches 206 Tags 189 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
6b76ec0413
Go to file
obrusvit 6b76ec0413 feat(core/ui): add T3T1 Status/PromptScreen 
StatusScreen serves to show a result of operation, typically a checkmark
with a circle around dismissed by swipe up gesture.

PromptScreen serves to confirm action, typically by holding a button.

Designs based on Figma.
So far without animation.
2024-05-31 11:59:52 +00:00
.clusterfuzzlite
.github ci: actions: no block-fixup on scheduled pipelines 2024-05-10 09:41:54 +00:00
ci feat(core/ui): rust-based UI flows 2024-05-31 11:59:52 +00:00
common feat(core): Add extendable BackupTypes. 2024-05-28 18:03:26 +02:00
core feat(core/ui): add T3T1 Status/PromptScreen 2024-05-31 11:59:52 +00:00
crypto chore(crypto): initialize automatic variables to zero 2024-05-10 20:06:28 +02:00
docs feat(core): Support extendable backup flag in SLIP-39. 2024-05-28 18:03:26 +02:00
legacy chore(legacy): initialize automatic variables to zero 2024-05-10 20:06:28 +02:00
python feat(core): add icons for T3T1 2024-05-31 11:59:52 +00:00
rust feat(core): Add extendable BackupTypes. 2024-05-28 18:03:26 +02:00
storage style: fix style according to new clang 2024-05-10 20:06:28 +02:00
tests feat(core): T3T1 ShareWords component 2024-05-31 11:59:52 +00:00
tools style(core): upgrade pyright to 1.1.361 2024-05-07 11:57:10 +02:00
vendor feat(core): introduce new drawing library 2024-05-17 09:17:37 +02:00
.clang-format
.editorconfig
.gitattributes chore: tag generated files for github diffs 2024-03-15 13:11:17 +01:00
.gitignore
.gitlab-ci.yml ci: move hardware tests over to github actions 2024-02-20 19:49:41 +01:00
.gitmodules
.pylintrc chore: move pylint config from setup.cfg to .pylintrc 2023-11-30 09:27:57 +01:00
.yamllint.yml
build-docker.sh
CODEOWNERS chore(CODEOWNERS): remove me from some components 2021-10-17 10:45:14 +02:00
COMMITS.md docs: introduce conventional-commits (#1234) 2020-09-15 16:11:39 +02:00
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 2020-04-30 14:49:47 +02:00
COPYING
create_monorepo.py chore: update branch name to main where its used 2023-10-18 10:40:05 +02:00
LICENSE.md
Makefile feat(crypto): Add Brian Gladman's implementation of GCM. 2024-04-03 10:26:46 +02:00
poetry.lock feat(core): Support extendable backup flag in SLIP-39. 2024-05-28 18:03:26 +02:00
poetry.toml
pyproject.toml feat(core): Support extendable backup flag in SLIP-39. 2024-05-28 18:03:26 +02:00
README.md
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg
shell.nix nix: unify ci/shell.nix and shell.nix 2020-07-03 12:32:55 +02:00

README.md

Trezor Firmware

img

Repository Structure

  • ci: Gitlab CI configuration files
  • common/defs: JSON coin definitions and support tables
  • common/protob: Common protobuf definitions for the Trezor protocol
  • common/tools: Tools for managing coin definitions and related data
  • core: Trezor Core, firmware implementation for Trezor T
  • crypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmware
  • docs: Assorted documentation
  • legacy: Trezor One firmware implementation
  • python: Python client library and the trezorctl command
  • storage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmware
  • tests: Firmware unit test suite
  • tools: Miscellaneous build and helper scripts
  • vendor: Submodules for external dependencies

Contribute

See CONTRIBUTING.md.

Using Conventional Commits is strongly recommended and might be enforced in future.

Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.

Security vulnerability disclosure

Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.

Documentation

See the docs folder or visit docs.trezor.io.