arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-17 13:12:05 +00:00
Code Issues Releases Wiki Activity
9,215 Commits 342 Branches 206 Tags 195 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
f09dcc412e
Go to file
matejcik f09dcc412e tests/zcash: enable "version_group_id_missing" test
2020-06-30 15:19:31 +02:00
.github/ISSUE_TEMPLATE github: firmware version AND revision (#1057) 2020-06-09 11:43:52 +02:00
ci ci: add debug firmwares to releases 2020-06-19 19:34:31 +00:00
common legacy, core: rename Features.pin_cached to unlocked and unify 2020-06-19 21:26:36 +02:00
core core/ui: Fix repaint bug in QR code rendering #1067. 2020-06-25 12:25:41 +02:00
crypto crypto: make bn_format faster 2020-06-26 12:29:21 +02:00
docs
legacy legacy, core: rename Features.pin_cached to unlocked and unify 2020-06-19 21:26:36 +02:00
python python: fix padding in first chunk (fixes #1082) 2020-06-25 11:23:26 +02:00
storage
tests tests/zcash: enable "version_group_id_missing" test 2020-06-30 15:19:31 +02:00
tools
vendor
.clang-format
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
build-docker.sh
CODEOWNERS
CONTRIBUTING.md
create_monorepo.py
Makefile
Pipfile
Pipfile.lock
README.md
SECURITY.md
setup.cfg
shell.nix

README.md

Trezor Firmware

img

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.

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.