arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-20 14:59:06 +00:00
Code Issues Releases Wiki Activity
9,748 Commits 322 Branches 205 Tags 199 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
48024de685
Go to file
matejcik 48024de685 chore: gitignore memperf results
2020-12-11 11:37:56 +01:00
.github/ISSUE_TEMPLATE github: firmware version AND revision (#1057) 2020-06-09 11:43:52 +02:00
ci ci(core): increase PYTEST_TIMEOUT for memory profiling 2020-12-08 18:07:50 +01:00
common fix(common): update protob combine script to reflect new changes 2020-12-10 16:53:00 +01:00
core chore: gitignore memperf results 2020-12-11 11:37:56 +01:00
crypto fix(crypto): Fix undefined behavior in xmr_read_varint(). 2020-12-03 20:05:05 +01:00
docs docs: minor clarification of review process 2020-11-27 13:55:03 +01:00
legacy legacy: update release date for 1.9.4 2020-11-26 16:51:44 +01:00
python style(common): use new syntax for typing in autogenerated protobuf enums 2020-12-01 15:52:29 +01:00
storage core: unify usage of TREZOR_MODEL 2020-06-06 21:06:15 +02:00
tests fix(tests): run test_softlock_instability on emulator only 2020-12-01 12:35:11 +01:00
tools tools/build_protobuf: don't compare __pycache__ 2020-08-21 14:12:49 +02:00
vendor chore(vendor): update micropython to include more precise memory profiling 2020-12-08 18:07:50 +01:00
.clang-format
.editorconfig style: add .editorconfig [skip ci] 2020-11-05 16:45:52 +01:00
.gitignore
.gitlab-ci.yml chore(python): replace pipenv with poetry 2020-10-07 16:21:00 +02:00
.gitmodules feat(common): add upstream Ethereum chains repository 2020-11-20 18:55:35 +01:00
.travis.yml ci(travis): install editorconfig-checker 2020-11-14 16:41:32 +01:00
.yamllint.yml ci: exclude more submodules from the yaml checker 2020-11-20 18:55:35 +01:00
build-docker.sh build: review the build script [skip ci] 2020-11-11 16:53:42 +01:00
CODEOWNERS CODEOWNERS: add more people 2020-05-09 22:24:35 +02:00
COMMITS.md docs: introduce conventional-commits (#1234) 2020-09-15 16:11:39 +02:00
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 2020-04-30 14:49:47 +02:00
create_monorepo.py
Makefile ci: enable editorconfig checks, fix whitespace issues 2020-11-11 14:43:50 +01:00
poetry.lock feat(ci): introduce yamllint 2020-11-10 10:27:47 +01:00
poetry.toml chore(python): replace pipenv with poetry 2020-10-07 16:21:00 +02:00
pyproject.toml feat(ci): introduce yamllint 2020-11-10 10:27:47 +01:00
README.md docs: introduce conventional-commits (#1234) 2020-09-15 16:11:39 +02:00
SECURITY.md
setup.cfg test(python): add flake8-requirements 2020-09-29 11:30:40 +02:00
shell.nix nix: unify ci/shell.nix and shell.nix 2020-07-03 12:32:55 +02:00

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.

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.