OneKey Zcash Hardware Support with Unified Wallet Architecture (Transparent + Shielded)

OneKey × Zcash — Progress Update

Project: OneKey hardware wallet Zcash support (Unified Wallet Architecture, Transparent + Shielded)

Target device: OneKey Pro2

Grant: Zcash Community Grants #228 / Zcash Community Forum proposal

Stage: All support items are complete except the hardware wallet’s on-device signing for the new Ironwood shielded pool; expected launch before 2026-10-15.

1. Background

This update covers the Core Zcash Hardware Support (Transparent + Shielded, with PCZT & Clear Signing) committed under the Zcash Community Grant.

The core principles of the solution remain unchanged:

  • Unified wallet architecture: a single mnemonic manages all chains and assets; Zcash keys are derived and isolated within the unified firmware, with no separate app and no firmware splitting.

  • Keys never leave the device: only the UFVK and addresses are exported; all signing happens inside the hardware.

  • Transparent + the new shielded pool (Ironwood, NU6.3), Sapling excluded: Ironwood activated with NU6.3 on 2026-07-28, reusing the existing Orchard receiver and the Halo 2 proof system (the legacy Orchard pool is now exit-only). It covers all four transaction types (transparent / shielding / deshielding / fully shielded).

  • Fully open source: all Zcash-related code will be released to OneKey’s public repositories under the same open-source license as the existing firmware.

Headline: As of this update, every support item is complete except the hardware wallet’s on-device signing support for the new Ironwood shielded pool. This is now the single remaining item and is in the development stage; because of the new shielded-pool support, the launch date has been adjusted to before 2026-10-15.

2. Status Overview

  • SE-level cryptographic primitives (RedPallas, Orchard primitives; reused by Ironwood)
  • ZIP-32 key derivation
  • Unified Address generation (Transparent + Orchard receiver, reused by Ironwood)
  • UFVK export (Transparent + Shielded)
  • Seed fingerprint export
  • Correctness verification of the above
  • Transparent transaction signing (PCZT)
  • PCZT parsing & Clear Signing (on-screen display + physical confirmation
  • Documentation (derivation paths, PCZT integration protocol, signing model)

In development: New shielded pool (Ironwood) on-device signing (shielded spends / Ironwood actions)

3. Question—Do we need to be compatible with Orchard?