Skip to content

Files

Latest commit

bec3aea · Jul 20, 2022

History

History
38 lines (28 loc) · 2.83 KB
·

index.md

File metadata and controls

38 lines (28 loc) · 2.83 KB
·

Onekey Firmware documentation

Welcome to the Onekey Firmware repository. This repository is so called monorepo, it contains several different yet very related projects that together form the Onekey Firmware ecosystem.

Repository Structure

  • ci: Gitlab CI configuration files
  • common/defs: JSON coin definitions and support tables
  • common/protob: Common protobuf definitions for the Onekey protocol
  • common/tools: Tools for managing coin definitions and related data
  • core: Onekey Core, firmware implementation for Onekey T
  • crypto: Stand-alone cryptography library used by both Onekey Core and the Onekey One firmware
  • docs: Assorted documentation
  • python: Python client library and the onekeyctl command
  • storage: NORCOW storage implementation used by both Onekey Core and the Onekey One firmware
  • tests: Firmware unit test suite
  • tools: Miscellaneous build and helper scripts
  • vendor: Submodules for external dependencies

Contribute

  • Adding a small feature or a fix If your change is somewhat subtle, feel free to file a PR in one of the appropriate repositories directly. See the PR requirements noted at CONTRIBUTING.md.
  • Add new coin/token/network to the official onekey firmware See COINS.md

Security vulnerability disclosure

  • Please read Bug Bunty Rules, we have detailed the exact plan in this article.
  • Please report suspected security vulnerabilities in private to dev@onekey.so
  • Please do NOT create publicly viewable issues for suspected security vulnerabilities.
  • As an open source project, although we are not yet profitable, we try to give some rewards to white hat hackers who disclose vulnerabilities to us in a timely manner.

Note on terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.