Go to file

Andrew Kozlik dc8ed0f0de feat(core): Force basic attestation in FIDO2 for google.com.		1 year ago
.github	…
ci	chore(docs): Clean up dead links [no changelog]	2 years ago
common	feat(core): Force basic attestation in FIDO2 for google.com.	1 year ago
core	feat(core): Force basic attestation in FIDO2 for google.com.	1 year ago
crypto	chore(core): Use C implementation of Bech32 decode.	2 years ago
docs	chore(docs): Clean up dead links [no changelog]	2 years ago
legacy	feat(common): Add CoinJoin request message.	2 years ago
python	chore(common): Rename "unstable" protobuf tag to "experimental_message".	2 years ago
storage	…
tests	feat(tests): Do not automatically enable experimental features in device tests.	2 years ago
tools	chore(common): update chains and tokens	2 years ago
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.