Skip to Content
DocumentationFirmwareRelease Status & ClearSign

Release status and ClearSign

Reviewed 2026-09-24. This page is generated from the versioned feature register. Working software, candidate test evidence and a publicly signed release are different states.

Release program

7.14.1 — Published firmware baseline

Status: Published snapshot. The latest-release endpoint checked on 2026-09-24 returned v7.14.1.

Use the live release record at install time; later candidates are not implied to be published.

Evidence: source 1 

7.14.2 — Signing hardening

Status: Final QA — owner-confirmed. 7.14.2 is part of the immediate release program, with working software in KeepKey Desktop and final QA underway.

Publication requires the final signed artifact, changelog and matching acceptance evidence; no date promised.

Evidence: source 1 

7.14.3 — Bitcoin-only product

Status: Final QA — owner-confirmed. 7.14.3 supplies the Bitcoin-only path in the immediate program.

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

Evidence: source 1 

7.15 — Additive provider context

Status: Final QA — owner-confirmed. The 7.15 provider contract 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 

7.16 — KeepKey-approved ClearSign

Status: Destination — candidate contract. 7.16 is the destination for KeepKey-approved interpretation: certified authority, context binding and coverage requirements.

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 AtlasSupported Chains