Go to file

matejcik cc9e74772b chore(common): rename MATIC to POL, following a network upgrade		2 weeks ago
.clusterfuzzlite	…
.github	…
ci	ci: migrate trezor-common sync to github actions	3 weeks ago
common	chore(common): rename MATIC to POL, following a network upgrade	2 weeks ago
core	chore(common): rename MATIC to POL, following a network upgrade	2 weeks ago
crypto	refacor(crypto): refactor hdnode_public_ckd	4 weeks ago
docs	fix(docs): generate pipeline docs	3 weeks ago
legacy	…
python	…
rust	…
storage	feat(storage): Do not lock freshly initialized storage.	2 months ago
tests	chore(core): support T3B1 for translation blobs	2 weeks ago
tools	style(core): add check for utils.INTERNAL_MODEL in (tuple)	3 weeks ago
vendor	chore(vendor): update vendor/fido2-tests	3 weeks ago
.clang-format	…
.editorconfig	…
.gitattributes	…
.gitignore	…
.gitlab-ci.yml	…
.gitmodules	…
.pylintrc	…
.yamllint.yml	…
CODEOWNERS	…
COMMITS.md	…
CONTRIBUTING.md	…
COPYING	…
LICENSE.md	…
Makefile	…
README.md	…
SECURITY.md	…
build-docker.sh	…
create_monorepo.py	…
poetry.lock	…
poetry.toml	…
pyproject.toml	…
setup.cfg	…
shell.nix	…

README.md

Trezor Firmware

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.