Go to file

Andrew Kozlik acf7294ca2 test(crypto): Add more unit tests for invalid T9 prefix in SLIP39 word lookup.		4 years ago
.github/ISSUE_TEMPLATE	…
ci	ci(core): increase PYTEST_TIMEOUT for memory profiling	4 years ago
common	fix(common): update protob combine script to reflect new changes	4 years ago
core	chore(core): Improve naming of SLIP39's T9 mask lookup.	4 years ago
crypto	test(crypto): Add more unit tests for invalid T9 prefix in SLIP39 word lookup.	4 years ago
docs	docs: use absolute link for toif_convert	4 years ago
legacy	legacy: update release date for 1.9.4	4 years ago
python	fix(python): do not log "resumed session" if there is no id	4 years ago
storage	core: unify usage of TREZOR_MODEL	4 years ago
tests	fix(tests): run test_softlock_instability on emulator only	4 years ago
tools	tools/build_protobuf: don't compare __pycache__	4 years ago
vendor	chore(vendor): update micropython to include more precise memory profiling	4 years ago
.clang-format	…
.editorconfig	…
.gitignore	…
.gitlab-ci.yml	…
.gitmodules	…
.travis.yml	…
.yamllint.yml	…
CODEOWNERS	…
COMMITS.md	…
CONTRIBUTING.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.

Issue Labels

Priority

Label	Meaning (SLA)
P1 Urgent	The current release + potentially immediate hotfix (30 days)
P2 High	The next release (60 days)
P3 Medium	Within the next 3 releases (90 days)
P4 Low	Anything outside the next 3 releases (120 days)

Severity

Label	Impact
S1 Blocker	Outage, broken feature with no workaround
S2 Critical	Broken feature, workaround too complex & unacceptable
S3 Major	Broken feature, workaround acceptable
S4 Low	Functionality inconvenience or cosmetic issue

CI

The complete test suite is running on a public GitLab CI. If you are an external contributor, we also have a Travis instance where a small subset of tests is running as well - mostly style and easy fast checks, which are quite common to fail for new contributors.

Documentation

See the docs folder or visit docs.trezor.io.