Go to file

matejcik bd06b72923 docs(core): document building with Rust		3 years ago
.github	…
ci	fix(ci): update to latest nixpkgs-unstable	3 years ago
common	…
core	…
crypto	fix(crypto): use ck_assert_uint_eq where we compare unsigned values	3 years ago
docs	docs(core): document building with Rust	3 years ago
legacy	fix(legacy): don't erase firmware and storage in intermediate firmware	3 years ago
python	fix(core/bitcoin): fix CoinJoin authorization with new cache	3 years ago
storage	…
tests	…
tools	…
vendor	…
.clang-format	…
.editorconfig	…
.gitignore	…
.gitlab-ci.yml	…
.gitmodules	…
.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.