Bitcoin HWI, the software bridge that lets wallet apps talk to hardware wallet devices, will stop accepting new devices and features once its remaining work is done. A Rust successor called BHWI has passed device-parity tests but has not yet shipped in a production wallet, leaving the handoff unfinished.
Bitcoin HWI, a widely used interface connecting wallet software to hardware signing devices, is moving toward retirement, while the Rust project its maintainer named as a promising successor has not yet shown a production handoff.
Maintainer freezes new device support
The maintainer of Bitcoin Core's Hardware Wallet Interface said on Aug. 18 that the project had effectively been in maintenance mode for years and had largely been a solo effort. HWI will no longer accept new devices or features beyond the work still needed for MuSig2. Once that work is finished, the maintainer expects to make a release that will likely be the project's last, then keep HWI in minimal maintenance until a suitable drop-in replacement is ready.
HWI is the bridge wallet software uses to discover a hardware device, retrieve public keys, display a receive address, and send a partially signed transaction to devices such as Ledger, Trezor, Coldcard, BitBox, or Jade for signing. Neither transition is complete: HWI is not archived, no retirement date has been set, and the notice does not say supported hardware wallets will stop working or that users' bitcoin is at risk.
Why the boundary matters for Bitcoin Core
HWI's original goal was bringing hardware-wallet support to Bitcoin Core through an external-signer boundary rather than placing HWI inside Core itself. The maintainer said Python prevents deterministic builds, the reproducible build process Bitcoin Core uses for release binaries, which is why HWI was never shipped with Core. That same separation makes HWI replaceable in principle, since another program can implement Core's external-signer contract.
The pressure now falls on teams that package HWI, invoke its command line, or rely on it to absorb changes in devices, operating systems, and vendor protocols. Specter Desktop pins a specific HWI release in its dependency file, and BTCPay Server Vault wraps HWI's command-line requests. Wasabi Wallet's compatibility documentation ties its hardware-wallet support to HWI, while Sparrow Wallet already runs a separate Java implementation called Lark rather than Python HWI.
BHWI shows testing progress, not a production handoff
BHWI, a Rust project with a sans-I/O core, aims to preserve HWI-style command output. Its parity documentation describes differential tests that run the unmodified HWI 3.2.0 device suite against BHWI for four device families: BitBox02, Coldcard, Ledger, and Jade.
Those tests reduce the risk that a replacement command returns different results for the covered devices, but they do not demonstrate production behavior across HWI's broader matrix, every host platform, or complete downstream wallet flows. BHWI's README and parity document do not name a wallet already shipping it as a production replacement.
HWI's repository may stay open until a successor is suitable, but its contribution freeze is already in effect. The succession risk begins when the next compatibility change arrives and the shared bridge no longer accepts it.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
