CryptoSlate
Bitcoin HWI, the widely used bridge between wallet software and hardware signing devices, is moving into a hard maintenance freeze. Its maintainer announced on Aug. 18 that HWI will no longer accept new devices or features beyond work needed for MuSig2, then likely ship one final release before settling into minimal upkeep. The Rust-based successor named in the notice, BHWI, has published parity tests against HWI 3.2.0 for BitBox02, Coldcard, Ledger and Jade, but no wallet currently ships it as a production replacement. The freeze does not break today's devices; it removes the normal upstream path for the next one.
Why it matters
HWI sits behind the external-signer boundary that Bitcoin Core documented as its supported integration, and Specter Desktop, Wasabi Wallet, BTCPay Server Vault and Sparrow each consume it differently. Specter pins HWI 3.1.0 in its dependency tree, BTCPay Server Vault wraps the command line, Wasabi documents HWI as its hardware-wallet backbone, and Sparrow routes through Lark, a Java port of the same interface rather than a Python swap. The freeze converts a maintenance announcement into a succession problem because BHWI's device matrix is narrower than HWI's and its parity tests, while meaningful, do not cover every host platform, packaging format or downstream wallet flow. When the next device, firmware behavior or host change arrives, there will be no shared upstream to merge fixes into, so each project carries its own integration cost.
Market impact
The user-visible risk is device coverage gaps rather than lost funds. An April Specter report already showed a setup running HWI 2.4.0 that could not detect the BitBox02 Nova added in HWI 3.2.0, and the pinned-version gap foreshadows the kind of mismatch the freeze formalises. New models from Ledger, Trezor, Coldcard, BitBox, KeepKey and Jade will require forks, separate integrations or simply go unsupported on some wallets. For self-custody users, the practical question is whether their wallet team's release plan keeps HWI updated, ships BHWI or accepts a smaller device matrix, while the HWI repository stays open and supported devices keep working in the interim.
Frequently asked questions
-
What is Bitcoin HWI?
It's the Hardware Wallet Interface, a Python library and command-line tool that lets wallet software discover Ledger, Trezor, Coldcard, BitBox, KeepKey and Jade devices, retrieve public keys, display receive addresses and send partially signed Bitcoin transactions for approval.
-
Why is HWI stopping new device support?
Its maintainer said on Aug. 18 the project has been a solo maintenance effort for years and that Python prevents the deterministic builds Bitcoin Core uses for release binaries. The freeze stops new devices and features beyond MuSig2 work.
-
What is BHWI?
BHWI is the Rust-based successor candidate named in the freeze notice. It uses a sans-I/O core with command-line, asynchronous and WebAssembly layers and aims to reproduce HWI's command output. Its parity tests run against HWI 3.2.0 for BitBox02, Coldcard, Ledger and Jade.
-
Is Bitcoin at risk from the HWI freeze?
No. Supported devices keep working today, the HWI repository stays open, no retirement date has been set and the notice does not say user funds are exposed. The risk is coverage gaps on future hardware models with no upstream to merge into.
-
Which Bitcoin wallets depend on HWI?
Specter Desktop pins HWI 3.1.0 as a direct Python dependency. BTCPay Server Vault wraps HWI's command line. Wasabi documents HWI as its hardware-wallet backbone. Sparrow routes through Lark, a Java port of the same interface rather than a Python swap.
TheBlock
CoinDesk
CoinTelegraph
WatcherGuru