Guide library PENGER Academy

Wallet Types Comparison

Choose a custody and signing arrangement for a job: everyday spending, savings or shared approval.

What you’ll learnCompare multisig, PSBT transport and threshold signing by their failure and recovery assumptions.

Before you startUnderstand keys and backups. Wallet Anatomy explains the transaction flow.

Multi-Signature (Multi-Sig) Wallets

Multi-sig wallets require M-of-N signatures to authorize a transaction. The spending conditions are encoded directly into the Bitcoin script, meaning the blockchain itself enforces the policy — no single compromised key can move funds.

Common Configurations

  • 2-of-3 — ideal for personal use. Keys distributed across three locations (e.g., phone, hardware wallet, metal backup in a safe). Any two can sign, so losing one doesn't lock you out.
  • 3-of-5 — suited for organizations. Five key holders (board members, executives), any three must approve. Tolerates two simultaneous compromises or losses.
  • 2-of-2 — collaborative custody or family setups where both parties must agree to spend.

Script Implementations

Bitcoin supports native multi-sig through several script types:

  • P2SH — the multi-sig script is hashed and the hash goes on-chain. The full script and all signatures are provided at spending time.
  • P2WSH — SegWit version, moves witness data to save block space and reduce fees.
  • P2TR (Taproot) — with MuSig2 key aggregation, an M-of-N setup can appear as a single-signature output on-chain when all parties cooperate, improving privacy and reducing fees. The multi-sig fallback is encoded in a Tapscript leaf.

Back up the multisig configuration as well as the seed phrases. The configuration file, often called a wallet descriptor or multisig coordination file, records all cosigners’ xpubs, the M-of-N quorum policy and derivation paths needed for recovery.

Air-Gapped Signing and PSBTs

Air-gapped signing removes a live USB or wireless connection from the transaction workflow. PSBT data still crosses the boundary through QR codes or removable media, and the signer still has to parse it and explain the spend correctly.

PSBT Workflow

  1. The watch-only wallet (online) creates an unsigned PSBT containing transaction inputs, outputs, and metadata
  2. The PSBT is transferred to the air-gapped signer via animated QR codes or SD card
  3. The signer validates the transaction on its trusted display, adds its signature, and outputs a partially or fully signed PSBT
  4. The signed PSBT is transferred back to the watch-only wallet
  5. The wallet finalizes and broadcasts the fully signed transaction to the network

PSBT Structure

A PSBT (Partially Signed Bitcoin Transaction) is a serialization format that carries all information needed for a signer to validate and sign:

  • Global fields — unsigned transaction, xpub metadata
  • Per-input fields — UTXO details, derivation paths, partial signatures, redeem/witness scripts
  • Per-output fields — derivation paths for change outputs (so the signer can verify change goes back to the same wallet)

The transaction travels between signers; their private keys stay with them. In ordinary script multisig, each signer can add its signature to a PSBT at a different time. They do not have to be online together or exchange private keys.

Transport does not explain the transaction

A malicious coordinator can put an attacker-controlled change output in a PSBT delivered by QR code just as it can over USB. The signer must verify ownership of change and display external outputs and fees. Changing transport does not change that requirement.

Source: BIP174: PSBT roles and fields.

MPC Wallets and Threshold Signatures

Threshold signing distributes signing material and computation. Protocols using distributed key generation can avoid reconstructing a full key during normal operation, but some products import or reconstruct keys. Check the actual setup and recovery procedure; the label MPC alone does not establish that property.

How MPC Signing Works

  1. Distributed Key Generation (DKG) — each party generates a key share. The shares are created through an interactive protocol where no single party sees the full key.
  2. Threshold Signing — to sign a transaction, a threshold of parties (e.g., 2 of 3) run an interactive signing protocol. Each contributes a partial signature from their share.
  3. Signature Combination — the partial signatures are combined into a standard ECDSA or Schnorr signature that is indistinguishable from a single-signer signature on-chain.

MPC vs. Multi-Sig

What the blockchain verifies
Script multisig
The spending script expresses the approval policy. The executed policy is revealed when it is spent.
Threshold signing
A compatible protocol produces a signature for the chain’s ordinary verifier. That signature need not reveal how the shares were arranged.

Compatibility still depends on the algorithm, curve and implementation. Signing needs the protocol’s communication and recovery arrangements; transactions and off-chain metadata can still reveal relationships.

Source: NIST: multi-party threshold cryptography.

Use Cases

  • Institutional custody — distribute signing authority across geographic regions and organizational roles
  • Cross-chain security — enforce threshold policies on chains that don't support multi-sig natively
  • Share refresh — some protocols can refresh shares without changing the public key. Confirm support and the compromise assumptions; refreshing shares is different from replacing an exposed signing key.
Three different forms of distribution
Approach What is distributed What recovery needs
Multisig Independent keys, with a spending policy Enough signers plus all policy and public-key metadata
Threshold signing Shares used by an interactive signing protocol The product’s documented recovery quorum and protocol support
Threshold backup Shares reconstructing one secret Enough backup shares and compatible restoration software

Secure Elements and Firmware Verification

The security of a hardware wallet ultimately depends on its hardware architecture and the integrity of its firmware. Two critical components:

Secure Element (SE)

A secure element is designed to resist specified attacks on sensitive data. Capabilities vary by chip, configuration and the surrounding device. Ask for evidence in these areas:

  • Side-channel resistance — which power, electromagnetic and timing attacks were tested, and under what conditions.
  • Fault injection protection — which voltage, clock or laser faults are detected or mitigated.
  • Certified evaluation — the evaluated chip/version, protection profile and exclusions; a chip certificate does not certify the whole wallet.
  • Rollback protection — whether the complete update path enforces rollback policy, including recovery and debug paths.

Firmware Verification

Before trusting a hardware wallet, verify the firmware is authentic and unmodified:

  • Reproducible builds — independent builders recreate a release from specified source, inputs and environment. Source availability alone does not establish this. Reproducible Builds definition.
  • Signed firmware updates — check whose keys authorize updates and how recovery or custom firmware paths work. A signature authenticates a publisher, not the safety of its code.
  • Attestation — check exactly what an attestation measures or identifies. Authentic hardware and an approved measurement are narrower claims than an uncompromised signing experience.

Ask what the evidence actually covers. Evaluate the signing boundary, display and approval path, verified updates, recovery and independent review together. A chip certificate or open repository establishes only part of that picture.

Choose by the failed dependency

Test a lost device, unavailable cosigner, missing service and incompatible recovery app on paper. Prefer the arrangement whose recovery you can explain and rehearse, rather than the one with the most security features.

Questions that remain

Which wallet type is best for a beginner?

For small amounts and learning, start with a reputable self-custodial mobile wallet. Write down and securely store your seed phrase from day one. As your holdings grow, add a hardware wallet for cold storage. The key principle: start with self-custody immediately, even if you begin small. Building good habits early is more valuable than any specific app choice.

Can a hardware wallet be hacked?

Yes. Hardware signers reduce the remote attack surface, but they still parse data from USB, Bluetooth, QR codes, memory cards or companion software, and vulnerabilities can exist in firmware or protocol handling. Physical extraction, supply-chain tampering and a compromised display are separate risks. Buy through a trusted channel, verify firmware and transaction details, keep recovery backups secure, and follow vendor security advisories.

Is it safe to keep crypto on an exchange?

Exchanges are frequent targets for hackers and have a documented history of collapses. Mt. Gox (2014), QuadrigaCX (2019), and FTX (2022) collectively lost billions in customer funds. While exchanges are convenient for active trading, long-term storage exposes you to counterparty risk that you cannot control or mitigate. The crypto community summarizes this as: "Not your keys, not your coins."

How many hardware wallets should I own?

For a single-sig setup, one hardware wallet plus a properly stored seed phrase backup is sufficient. Having a spare device speeds up recovery if the primary device fails. For a multi-sig setup (e.g., 2-of-3), you need at least 2-3 devices, ideally from different manufacturers to avoid correlated firmware vulnerabilities. The devices should be stored in separate physical locations.

What is a watch-only wallet?

A watch-only wallet imports your extended public key (xpub) without any private key material. It can display your balances, generate receiving addresses, and construct unsigned transactions — but it cannot sign or spend. This is useful for monitoring balances on your phone while the signing keys stay securely on a hardware wallet. Watch-only wallets are a key component of air-gapped signing workflows.

[ CHECK YOURSELF ]

Test Your Knowledge

Take a quick quiz to check your understanding of this guide.

Take the Quiz

5 questions per level · ~2 min