You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ken 22abc7086e Initial commit 4 years ago
..
ci Initial commit 4 years ago
common Initial commit 4 years ago
core Initial commit 4 years ago
crypto Initial commit 4 years ago
docs Initial commit 4 years ago
legacy Initial commit 4 years ago
python Initial commit 4 years ago
storage Initial commit 4 years ago
tests Initial commit 4 years ago
tools Initial commit 4 years ago
CODEOWNERS Initial commit 4 years ago
CONTRIBUTING.md Initial commit 4 years ago
Makefile Initial commit 4 years ago
Pipfile Initial commit 4 years ago
Pipfile.lock Initial commit 4 years ago
README.md Initial commit 4 years ago
SECURITY.md Initial commit 4 years ago
build-docker.sh Initial commit 4 years ago
create_monorepo.py Initial commit 4 years ago
poetry.lock Initial commit 4 years ago
pyproject.toml Initial commit 4 years ago
setup.cfg Initial commit 4 years ago
shell.nix Initial commit 4 years ago

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.