Blockstream Co-founder Adam Back Says Multi-chain Custody Complexity Weakens Security, More Features Mean Larger Attack Surface
Blockstream co-founder Adam Back stated that Bitcoin-specific hardware wallets are more secure than custodial architectures because system complexity expands the attack surface and weakens security audit capabilities.
He believes that some alternative coins lack mature multi-signature or Schnorr signature support, forcing multi-chain wallets to design custodial architectures based on "minimum common capabilities," potentially sacrificing Bitcoin's native security features.
Back pointed out that Bitcoin can utilize native multi-signatures, Schnorr signatures, and clearer signature and script architectures to help hardware wallets reduce unnecessary logic in key management, transaction authorization, and backup recovery.
This viewpoint reflects Back's technical and product stance and does not constitute an independent audit conclusion on the security of all multi-chain wallets, all alternative chains, or specific custodial services; different chains can achieve various security models through smart contract multi-signatures, MPC, threshold signatures, or protocol layer account abstractions.
In market mechanisms, Bitcoin-specific hardware wallets trade off functionality convergence for a smaller codebase, fewer transaction parsing rules, and a more controllable audit scope; multi-chain wallets trade off asset coverage for more protocols, signature formats, transaction encoding, token standards, and dApp interaction risks. For large long-term BTC holders, single-asset isolation can reduce exposure to mis-signatures and supply chain attacks; for users needing cross-chain transactions, the convenience of multi-chain may still outweigh the security premium of dedicated devices.
Source: Public Information
ABAB AI Insight
Adam Back's argument follows the "minimum trusted computing base" principle of Bitcoin security engineering. Bitcoin has gradually enhanced signature verification, transaction expression, and script rules through conservative upgrades from early P2PKH, P2SH multi-signatures to SegWit, Taproot, and Schnorr signatures. If a hardware wallet only needs to parse one transaction semantics, it can control display, amount verification, change address confirmation, and signature strategy within a relatively limited code and testing scope.
The capital path of multi-chain custody is "covering more assets - accessing more wallets and dApps - obtaining more transaction flow and users." However, with each additional chain, hardware or custodians may introduce new address encoding, transaction formats, Gas logic, token authorizations, contract calls, RPC dependencies, and blind signing risks. Security costs do not increase linearly: a special transaction on one chain or an error in a token authorization interface can become an entry point for attackers to breach user asset boundaries.
This contrasts with the strategies of hardware wallets like Ledger and Trezor that support multi-chain assets, and with Casa and Unchained that focus on Bitcoin multi-signature custody. The former views broad compatibility as a product distribution advantage, while the latter sees dedicated multi-signatures, geographic key isolation, and recovery processes as core services. The two architectures serve different risk preferences: frequent DeFi operators need compatibility, while long-term large BTC holders prioritize minimal permissions and verifiability.
Essentially, this is a choice of security architecture beyond technical alternatives: more features do not necessarily mean higher security; security depends on the matching degree of assets, permissions, and attack surfaces. The mechanism is that hardware wallets protect not the "chain," but the user's understanding and control over signing actions; when devices cannot fully display the real consequences of complex contracts, users will outsource security judgments to front ends, wallet plugins, or third-party interpretation layers. Bitcoin-specific devices transform security from "identifying all risks" to "defaulting to rejecting most risks."
ABAB News · Law of Cognition
The more features, the larger the attack surface
Compatibility creates convenience, isolation creates security
Unintelligible signatures mean handing assets to the front end