Skip to Content
DocumentationFirmwareRelease Status & ClearSign

Release status and ClearSign

Reviewed 2026-10-23. This page is generated from the versioned feature register; every release status on it is read live from GitHub releases  (drafts are never shown). Working software, candidate test evidence and a publicly signed release are different states.

Current releases

  • KeepKey firmware: v7.14.2 (2026-10-16) · newer Pre-release: v7.16.0 (2026-10-28) · Bitcoin-only build: v7.14.3 (2026-10-16)
  • KeepKey Desktop: v1.6.7 (2026-10-28) · newer Pre-release: v1.6.10 (2026-11-05)

Release program

7.14.2 — Signing hardening

GitHub status: Latest release: v7.14.2 (2026-10-16). 7.14.2 is the signing-hardening firmware release. What changed and who it affects: Firmware 7.14.2.

Treat a version as published only when GitHub shows it as a full release with its signed artifact and changelog.

Evidence: source 1  · source 2  · source 3 

7.14.3 — Bitcoin-only product

GitHub status: Bitcoin-only build · Released: v7.14.3 (2026-10-16). 7.14.3 is the Bitcoin-only firmware build; its release carries only the Bitcoin-only image.

Verify actual artifact flags, variant identity, excluded operations and migration behavior.

Evidence: source 1  · source 2  · source 3 

7.15 — Additive provider context

GitHub status: Not published on GitHub (releases). The 7.15 provider contract ships as part of 7.16 (owner, 2026-10-26), not as a separate release. It adds interpretation while retaining baseline review; runtime identities are session-scoped.

Do not infer completed acceptance from alpha source or a report with the relevant section withheld.

Evidence: source 1  · source 2 

7.16 — KeepKey-approved ClearSign

GitHub status: Pre-release: v7.16.0 (2026-10-28). 7.16 delivers KeepKey-approved interpretation: certified authority, context binding and coverage requirements. It is in final QA (owner, 2026-10-26).

Production roots, final validity/revocation model and exact-candidate evidence must support public availability claims.

Evidence: source 1 

Verify before approving

KeepKey approval authenticates the authority behind supported descriptions. It is not a guarantee that a contract is safe, an investment is sound, or a transaction will succeed. Runtime provider context remains distinct from certified authority. Coverage, fallback and refusal behavior depend on the exact firmware, Vault/SDK and metadata versions.

Inspect the evidence

What we are working toward

  • Understand crypto: Explain keys, addresses, networks, fees and approvals without assumed expertise.
  • Set up with confidence: Help a new owner install, create or recover a wallet, verify a backup and make a first receive.
  • Use a KeepKey day to day: Make receive, send, swap, portfolio and dApp decisions understandable and verifiable.
  • Resolve problems safely: Provide a direct path for connection issues, interrupted updates, missing assets and recovery questions.
  • Earn informed trust: Explain security controls, limitations, provenance and product availability with evidence.
  • Enable integrations: Give developers coherent setup, authentication, protocol and API references.
  • Make knowledge easy to find: Connect beginner explanations, task guides, technical references and articles; keep search and AI indexes current.
  • Keep the public story current: Use one reviewed feature register and accountable updates across docs, articles and company surfaces.

These are goals, not claims of completed certification or an independently established security ranking.

Last updated on
CI Test AtlasFirmware 7.14.2