Skip to content

Latest commit

 

History

History
42 lines (33 loc) · 2.29 KB

File metadata and controls

42 lines (33 loc) · 2.29 KB

hw-core Roadmap

Last updated: 2026-03-13

Product Goal

Ship a stable, reusable host stack for hardware-wallet communication over THP/BLE that external developers can adopt through well-defined Rust and FFI surfaces.

Current Baseline

  • THP/BLE host stack is operational end-to-end for discovery, pairing, session establishment, encrypted messaging, and persisted pairing state.
  • Android BLE support is updated to btleplug 0.12.0, with only the remaining required Android Java behavior patch carried locally.
  • Shared wallet orchestration (hw-wallet) is used by CLI and FFI.
  • Consumer-facing ETH message-sign validation is shared across wallet, CLI, and FFI entry points.
  • CLI supports scan, pair, address, sign-tx, and message-signing workflows.
  • hw-ffi generates Swift/Kotlin bindings consumed by Apple and Android sample surfaces.
  • Emulator CI retains quiet successful runs while preserving emulator stdout/stderr automatically on failures.

Feature Status

Capability Ethereum Bitcoin Solana
Address retrieval Done Done Done
Transaction signing Done Partial (advanced TxRequest variants pending) Done
Message signing Done (EIP-191 + EIP-712) Done Deferred

Near-Term Priorities

  1. Complete remaining BTC protocol gaps and keep shared ETH/BTC validation regression-covered.
  2. Make Android and Apple consumption paths supportable through packaged artifacts and integration docs.
  3. Narrow validation and CI to the developer-facing flows we explicitly support.

Milestones

Milestone Status Exit Criteria
M1: Protocol-complete baseline In progress BTC signing handles the full supported firmware-requested TX* sequence and consumer-facing validation remains regression-covered across entry points
M2: Consumer-ready SDK surfaces In progress Android and Apple consumers can integrate hw-core from packaged artifacts using documented setup
M3: Release confidence In progress CI, smoke checks, and release docs reflect the actual supported developer experience

Not the Current Focus

  • Expanding beyond the current transport model.
  • Multi-vendor wallet support.
  • Additional chain work beyond gaps that block current developer adoption.
  • Sample-app UX polish that does not improve integration reliability.