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.
 
 
 
 
 
 
Go to file
matejcik 9a718b92b9
WIP - C side verification of write validity
5 months ago
.clusterfuzzlite
.github ci: fix changelog check for github 7 months ago
ci WIP - firmware translations 6 months ago
common feat(common): provide some useful paths for the mako templates 5 months ago
core WIP - C side verification of write validity 5 months ago
crypto fix(crypto): add missing header for size_t 5 months ago
docs WIP - firmware translations 6 months ago
legacy WIP - firmware translations 6 months ago
python WIP: Python part 5 months ago
rust WIP - firmware translations 6 months ago
storage WIP - firmware translations 6 months ago
tests WIP - firmware translations 6 months ago
tools WIP - firmware translations 6 months ago
vendor
.clang-format
.editorconfig
.gitattributes
.gitignore
.gitlab-ci.yml
.gitmodules
.pylintrc
.yamllint.yml
CODEOWNERS
COMMITS.md
CONTRIBUTING.md
COPYING
LICENSE.md
Makefile WIP - firmware translations 6 months ago
README.md
SECURITY.md
build-docker.sh
create_monorepo.py
poetry.lock
poetry.toml
pyproject.toml
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.

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.