- C 43.6%
- Python 33.2%
- Rust 18.4%
- HTML 3.2%
- Mako 0.3%
- Other 1.1%
The contacts "anchor + N satellites" model publishes kind-31926 events in which
this identity vouches for a secondary Nostr address (a "satellite"). Signed via
the generic nostr sign_event path, the device previously showed only "Event kind
31926" + raw tags, so a malicious host could get the identity to publicly vouch
for an address the user never saw on the trusted screen.
Recognise kind-31926 and render a dedicated confirm that names the satellite key
(the `d` tag) and its class (`scope`/`app`), so the on-device confirm actually
backs the third-party-verifiable claim. Sibling of
|
||
|---|---|---|
| .clusterfuzzlite | ||
| .conductor | ||
| .github | ||
| ci | ||
| common | ||
| core | ||
| crypto | ||
| docs | ||
| legacy | ||
| nordic | ||
| python | ||
| rust | ||
| scripts/suite-dark | ||
| storage | ||
| tests | ||
| tools | ||
| vendor | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .pylintrc | ||
| .yamllint.yml | ||
| build-docker.sh | ||
| CODEOWNERS | ||
| COMMITS.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| create_monorepo.py | ||
| LICENSE.md | ||
| Makefile | ||
| pyproject.toml | ||
| pyrightconfig.json | ||
| README.md | ||
| SECURITY.md | ||
| setup.cfg | ||
| shell.nix | ||
| tf-tools.toml | ||
| uv.lock | ||
Firmware Dark
Unofficial, Bitcoin-only Trezor firmware for the Suite Dark distribution.
Firmware Dark is a fork of trezor/trezor-firmware:
the full upstream source plus a small set of commits. Builds for Trezor Model T
(T2T1), Safe 3 (T2B1), Safe 5 (T3T1) and Safe 7 (T3W1) are published to the
rolling continuous release
as FirmwareDark-<MODEL>.bin.
Install it straight from Suite Dark: Settings → Device → Advanced → "Install Suite Dark firmware".
⚠️ This is unofficial, unsigned firmware. Installing it wipes the device (back up your recovery seed first) and the device will permanently show an "unofficial firmware" warning. Inherent to firmware not signed by SatoshiLabs — not affiliated with or endorsed by SatoshiLabs.
The upstream Trezor Firmware README follows.
Trezor Firmware
Repository Structure
ci: Ancillary files, data, and scripts for the CI pipelinecommon/defs: JSON coin definitions and support tablescommon/protob: Common protobuf definitions for the Trezor protocolcommon/tools: Tools for managing coin definitions and related datacore: Trezor Core, a firmware implementation for Trezor T, Trezor Safe 3, Trezor Safe 5, and Trezor Safe 7crypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmwaredocs: Assorted documentationlegacy: Trezor One firmware implementationpython: Python client library and thetrezorctlcommandstorage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmwaretests: Firmware unit test suitetools: Miscellaneous build and helper scriptsvendor: Submodules for external dependencies
Contribute
See CONTRIBUTING.md.
Using Conventional Commits is strongly recommended and might be enforced in the 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, as it contains useful assorted knowledge.
Security Vulnerability Disclosure
Please do NOT create publicly viewable issues for suspected security vulnerabilities. See the Security tab for reporting instructions.
Documentation
See the docs folder or visit docs.trezor.io.