Cowrie Research

satoshilabs-primary-sources-2026-08-07

3 min read

SatoshiLabs primary-source snapshot

Fetched: 2026-08-07 UTC

1) SatoshiLabs site

Source: https://satoshilabs.com/

Selected excerpts from the official site:

Trezor is part of SatoshiLabs, a technology holding company focused on bitcoin and crypto innovation.

Additional signals from the source:

  • The page is framed around a Trezor Safe 7 launch, but the important entity-level signal is explicit: Trezor is being presented as part of a broader SatoshiLabs shell rather than as a disconnected standalone label
  • The same page ties the operator story to open-source firmware, TROPIC01, quantum-ready update architecture, and the broader self-custody trust narrative the company wants users to inherit

2) Trezor security page

Source: https://trezor.io/why-trezor-is-secure

Selected excerpts from the official site:

Open-source design

Benefit from community-testing, giving users protection from threats.

NDA-free design

Our hardware design is completely transparent. We have no secrets.

Additional signals from the source:

  • The page packages Trezor’s official trust story around open-source design, transparent hardware, firmware authenticity checks, custom-backend support, Bitcoin-only firmware, coin control, Tor, and other first-party defaults
  • That is useful for the entity split because these are not only device properties; they are company-curated release, documentation, and support choices

3) Trezor Suite page

Source: https://trezor.io/trezor-suite

Selected excerpts from the official site:

The Trezor Suite app makes it easy and secure to manage, buy, sell, and swap your crypto all in one place.

Trezor Suite is the official app for managing your Trezor hardware wallet.

Additional signals from the source:

  • The official app bundles device management, buying, selling, swapping, staking, mobile support, dapp access, and wallet-app compatibility into one operator-controlled shell
  • This is one of the clearest reasons a company note is useful: users and integrators inherit the company-run app and routing surface, not just a hardware device

4) Trezor firmware documentation

Source: https://docs.trezor.io/trezor-firmware/

Selected excerpts from the official docs:

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

python: Python client library and the trezorctl command

Please report suspected security vulnerabilities in private to security@satoshilabs.com

Additional signals from the source:

  • The repository structure covers firmware, protocol definitions, storage, tests, tooling, and developer libraries rather than only a single device image
  • The security disclosure address is especially useful because it ties the public engineering and vulnerability-handling boundary directly to SatoshiLabs

5) Existing Trezor primary-source snapshot

Source: ../whitepapers/trezor-primary-sources-2026-05-01.md

Additional signals from the captured sources:

  • The Trezor GitHub organization publicly exposes firmware, Suite, Blockbook, and communication-daemon layers
  • The Suite repository shows Trezor Connect, Trezor Suite, and Trezor Suite Mobile in one codebase
  • The Blockbook repository confirms Trezor maintains backend infrastructure that can become part of the practical trust and default-routing boundary

Notes

  • SatoshiLabs is the useful entity cut when the question is about release workflow, hardware provenance, software distribution, security disclosure, support posture, and the named operator above Trezor’s signer/app/backend stack.
  • The product-layer note should stay on projects/trezor.md; the company layer belongs in companies/satoshilabs.md.

Graph View