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
cepetr a14ae705fb
chore(core/embed): move TOIF format definition to rust
4 months ago
.clusterfuzzlite Run fuzzer in CI 10 months ago
.github ci: fix changelog check for github 5 months ago
ci ci: fix changelog check for github 5 months ago
common feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`. 5 months ago
core chore(core/embed): move TOIF format definition to rust 4 months ago
crypto feat(core/prodtest): Check device certificate chain integrity using authority key identifier. 5 months ago
docs docs: fix typos 6 months ago
legacy feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`. 5 months ago
python feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`. 5 months ago
rust feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`. 5 months ago
storage refactor(core): remove residual usage of old flash api 6 months ago
tests feat(common & core & legacy & python/stellar): add support for `ClaimClaimableBalanceOp`. 5 months ago
tools refactor(core): make ethereum summary reusable for more coins 5 months ago
vendor build: fix compilation on darwin 1 year 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: mark generated files as linguist-generated 5 months ago
.gitignore fix(core,crypto): add more test cases from bip-173 3 years ago
.gitlab-ci.yml ci: allow jobs to be cancelled when redundant 10 months ago
.gitmodules feat(common): switch to external Ethereum definitions, add generators 1 year 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(solana): add solana templates 5 months 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 7 months ago
poetry.lock feat: custom Pylint plugin 5 months ago
poetry.toml build(poetry): use new (parallel) installer 2 years ago
pyproject.toml feat: custom Pylint plugin 5 months ago
setup.cfg chore: move pylint config from setup.cfg to .pylintrc 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.