You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Go to file
obrusvit 3628630584
feat(core/ui): improve T3T1 recovery
12 hours ago
.clusterfuzzlite Run fuzzer in CI 10 months ago
.github feat(core): copy T2T1 bootloader UI for T3T1 2 weeks ago
ci feat(core/ui): rust-based UI flows 1 week ago
common fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 weeks ago
core feat(core/ui): improve T3T1 recovery 12 hours ago
crypto chore(crypto): Zero-initialize stack variables in AES code. 3 weeks ago
docs docs: minor fix of build emu 1 week ago
legacy fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 weeks ago
python feat(core): add icons for T3T1 1 week ago
rust refactor(core): improve tjpg interface 1 week ago
storage feat(core): use U5 HW keys to additionally encrypt storage items 3 weeks ago
tests feat(core): T3T1 ShareWords component 1 week ago
tools feat(crypto): Add Brian Gladman's implementation of GCM. 3 weeks ago
vendor chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 months ago
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" 4 years ago
.editorconfig style: add .editorconfig [skip ci] 4 years ago
.gitattributes chore: tag generated files for github diffs 1 month ago
.gitignore fix(core,crypto): add more test cases from bip-173 3 years ago
.gitlab-ci.yml ci: move hardware tests over to github actions 2 months ago
.gitmodules chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 months ago
.pylintrc chore: move pylint config from setup.cfg to .pylintrc 5 months ago
.yamllint.yml style: ignore yaml files in venv 3 years ago
CODEOWNERS chore(CODEOWNERS): remove me from some components 3 years ago
COMMITS.md docs: introduce conventional-commits (#1234) 4 years ago
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 4 years ago
COPYING docs: clear up licensing information 3 years ago
LICENSE.md docs: clear up licensing information 3 years ago
Makefile feat(crypto): Add Brian Gladman's implementation of GCM. 3 weeks ago
README.md chore(readme): add link to trezor.io KB disclosure article 1 year ago
SECURITY.md docs: use monospace for fingerprints 5 years ago
build-docker.sh build: differentiate between models for prodtest build 11 months ago
create_monorepo.py chore: update branch name to main where its used 6 months ago
poetry.lock build(deps): bump idna from 3.3 to 3.7 2 weeks ago
poetry.toml build(poetry): use new (parallel) installer 1 year ago
pyproject.toml feat: Remove pyblake2 1 month ago
setup.cfg chore: upgrade style checkers 2 months ago
shell.nix nix: unify ci/shell.nix and shell.nix 4 years ago

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.