Go to file

Ondřej Vejpustek f0fef1d8c1 chore: update gcc		4 months ago
.clusterfuzzlite	…
.github	ci: actions: no block-fixup on scheduled pipelines	4 months ago
ci	chore: update gcc	4 months ago
common	feat(core): add ability to request backups with any number of groups/shares	5 months ago
core	chore(core): introduce THP flag	4 months ago
crypto	test(crypto): add elligator2 tests	4 months ago
docs	chore(core): introduce THP flag	4 months ago
legacy	feat(core): add ability to request backups with any number of groups/shares	5 months ago
python	style(python): upgrade to pyright 1.1.361	5 months ago
rust	feat(core): add ability to request backups with any number of groups/shares	5 months ago
storage	…
tests	chore(core): update cs.json and fixtures	4 months ago
tools	style(core): upgrade pyright to 1.1.361	5 months ago
vendor	…
.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.