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
M1nd3r d5aa315202
fix(core): remove `handshake hash` from `auth_data` in transport noise messages
9 hours ago
.clusterfuzzlite Run fuzzer in CI 1 year ago
.github ci: build T3T1 firmware for production bootloader 2 weeks ago
ci feat(core): implement a new Trezor-Host protocol 5 days ago
common fix(core): fix RSODs on firmware builds, fix indentation in aesgcm documentation 10 hours ago
core fix(core): remove `handshake hash` from `auth_data` in transport noise messages 9 hours ago
crypto chore(crypto): initialize automatic variables to zero 3 months ago
docs feat(core): implement a new Trezor-Host protocol 5 days ago
legacy feat(core): implement a new Trezor-Host protocol 5 days ago
python feat(core): add thp pairing values into debugLinkState object, allow debugLinkGetState in pairing (in one place) 3 days ago
rust fix(core): fix RSODs on firmware builds, fix indentation in aesgcm documentation 10 hours ago
storage feat(storage): Do not lock freshly initialized storage. 2 weeks ago
tests chore(core): update fixtures.json 1 week ago
tools chore: generate-changelog.py adjustments 2 weeks ago
vendor build(core): fix build for GCC13 2 weeks 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 4 months 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 5 months ago
.gitmodules chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 5 months ago
.pylintrc chore: move pylint config from setup.cfg to .pylintrc 8 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 refactor(core): move vendor headers to model specific directories 1 week ago
README.md chore(readme): add link to trezor.io KB disclosure article 2 years ago
SECURITY.md docs: use monospace for fingerprints 5 years ago
build-docker.sh build(core): add T3T1 to build-docker.sh 2 months ago
create_monorepo.py chore: update branch name to main where its used 9 months ago
poetry.lock build(deps): bump setuptools from 67.6.0 to 70.0.0 2 weeks ago
poetry.toml build(poetry): use new (parallel) installer 2 years ago
pyproject.toml build(deps): bump typing-extensions to fix compatibility with Python 3.12 1 month ago
setup.cfg chore: upgrade style checkers 5 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.