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 f7c340f333
feat(core/bitcoin): show lock_time as human readable datetime
3 years ago
.github
ci
common style(all): fix pylint complaints 3 years ago
core feat(core/bitcoin): show lock_time as human readable datetime 3 years ago
crypto
docs
legacy feat(legacy/ethereum): support access lists in EIP-1559 transactions 3 years ago
python
storage style(all): use f-strings for formatting 3 years ago
tests feat(core/bitcoin): show lock_time as human readable datetime 3 years ago
tools
vendor
.clang-format
.editorconfig
.gitignore
.gitlab-ci.yml
.gitmodules
.yamllint.yml
CODEOWNERS
COMMITS.md
CONTRIBUTING.md
COPYING
LICENSE.md
Makefile feat(all): enable pylint globally 3 years ago
README.md
SECURITY.md
build-docker.sh
create_monorepo.py
poetry.lock feat(all): enable pylint globally 3 years ago
poetry.toml
pyproject.toml feat(all): enable pylint globally 3 years ago
setup.cfg feat(all): enable pylint globally 3 years ago
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.