A married couple holds Bitcoin acquired over years, Ethereum from staking, and NFTs representing both sentimental and financial value. Neither partner wants complete control over the assets or the ability to move funds unilaterally without the other’s knowledge. Yet they also need protection against the scenario where one partner’s device is compromised, stolen, or accessed inappropriately during a separation or conflict. The challenge is not finding a single solution but rather designing a custody arrangement that respects both shared ownership and individual security boundaries.
Ledger hardware wallets, managed through the Ledger Wallet application, offer technical tools for this task: multiple accounts, separate devices, passphrase options, and transaction approval workflows. However, the tools themselves do not determine the custody model. A couple must decide whether accounts are individually held, jointly controlled, or divided by asset type. They must establish clear procedures for recovery, inheritance, and what happens if access is lost or disputed. The operational design matters as much as the cryptography.
Why traditional shared accounts create custody conflicts
A single cryptocurrency wallet with one recovery phrase offers simplicity: one source of truth, one backup location, one set of private keys. When two people know that phrase, however, both have unilateral control. Either partner can move all assets without the other’s knowledge or consent. This creates asymmetric risk. The partner who cares less about the assets or acts faster in a conflict can spend without restriction, leaving the other to discover the transaction post-facto on an immutable ledger. Even in amicable relationships, this arrangement can generate unnecessary disputes over authorization.
Centralized exchanges solve this by implementing account-level access controls, transaction limits, and approval workflows. But that solution concentrates custody with a third party, reintroducing counterparty risk that self-custody through hardware wallets is designed to eliminate. The hardware device keeps private keys offline and isolated from internet-connected computers. A couple cannot achieve true shared control through a centralized intermediary without accepting that the exchange, not the couple, ultimately holds the assets.
Some couples attempt to use a single Ledger device with one PIN known to both partners. This reduces the number of recovery phrases to manage, but it also means that either partner can access the device and sign transactions without the other being present or informed. If one partner changes the PIN, the other loses access entirely. If the device is stolen, both partners lose their funds simultaneously. The device’s security feature—the PIN protecting the hardware—becomes a point of failure for both rather than a personal control boundary.
The multi-device self-custody model
The most practical approach for couples is to use separate Ledger devices for each partner, combined with a shared-account architecture where appropriate. This means each person owns a device, knows their own recovery phrase, controls their own PIN, and maintains individual access to their hardware signer. The private keys never exist in the same location or under unified control. Through Ledger Wallet’s account system, each partner can add accounts to their device, monitor shared portfolios, and prepare transactions.
The critical distinction is between account ownership and transaction signing. When a couple uses separate Ledger devices, they can structure accounts in several ways. The first model is division by asset: Partner A’s device holds all Bitcoin accounts, Partner B’s device holds Ethereum accounts. Each person has solo custody of their assigned assets. This works for couples who already have natural divisions—one partner may have stronger technical knowledge or clearer preferences about certain assets. The downside is that it does not truly share ownership; it merely divides it.
A second model uses account labels and portfolio monitoring without changing signing authority. Both partners download Ledger Wallet and add each other’s accounts using public addresses. This allows both to see the full portfolio, monitor balances, and discuss allocation, but only the partner whose device holds the private keys can actually sign and broadcast transactions. This model prioritizes transparency over joint authorization. It works well for couples who trust each other operationally but want to prevent impulsive or unauthorized moves. The transaction still requires the device owner to physically approve on the hardware, creating a deliberate pause.
A third model combines separate primary accounts with a small shared-custody account held on both devices. For example, a couple might keep most assets in individually controlled accounts but maintain a smaller “household expense” account that each partner can access. This requires multi-signature arrangements, which most standard Ledger setups do not provide natively. Instead, it requires using Ledger devices in conjunction with multi-sig platforms like Casa or Unchained, which adds complexity but creates genuine joint control for that subset of funds.
Passphrase options and account hierarchy
Ledger devices support optional passphrases, which are additional secrets distinct from the recovery phrase and PIN. A passphrase acts as a 25th word (in BIP39 terminology) that must be entered each time the device signs a transaction. This feature allows a single recovery phrase to generate multiple non-overlapping sets of accounts. For couples, a passphrase can be used to create a hidden account set that only one partner knows, or a joint account set protected by a passphrase both partners memorized together.
The appeal is clear: if Partner A’s Ledger device has two separate account hierarchies—one protected by their personal passphrase and one by a shared passphrase—they can segregate funds without requiring two devices. However, this introduces a new risk. If the recovery phrase is discovered, an adversary can still access all accounts, including the ones protected by passphrases, provided they know those passphrases. The passphrase is not stored on the device; it is typed by the user. If the passphrase is weak or predictable, or if a device is compromised by malware that captures inputs, the protection fails. Additionally, if a partner forgets their personal passphrase, they lose access to those accounts even if they recover the device.
For couples specifically, passphrases work best as a supplementary layer rather than the primary security boundary. A shared passphrase can create an additional barrier to casual access by either partner, but it should not be the only thing standing between one partner’s device and the other’s funds. The passphrase itself must be stored securely—written down in a separate location from the recovery phrase, or memorized—and communicated to the other partner only if both partners agree. If a couple uses passphrases, they should document the account structure clearly so that the surviving partner or executor understands how to recover the funds after loss or death.
Recovery, inheritance, and access after loss
The moment when custody arrangements face their strictest test is after one partner’s death, incapacity, or departure. If assets are truly held in self-custody using hardware wallet devices, the recovery process depends entirely on the recovery phrase and passphrase if used. Many couples keep their recovery phrases in separate physical locations—a safe deposit box, a home safe, or a lawyer’s escrow. If both partners die simultaneously, the other’s recovery phrase may be inaccessible, locking the funds permanently.
A more resilient approach involves a shared document that lists account structures, device identifiers, passphrases (if any), and the location of each recovery phrase. This document should be stored in a place the surviving partner or executor can access—a safe, a lawyer’s file, or a trusted family member. It should not be stored in cloud services or email because those create third-party access points. The document is not the secret itself; it is metadata about how secrets are organized. Someone with access to the document still needs the physical recovery phrases to restore accounts.
For couples with young children or complex estates, some use a tiered recovery strategy. The primary recovery phrase is split using a scheme like Shamir’s Secret Sharing (supported by some hardware wallet vendors), where the phrase is divided into multiple shares and a threshold number of shares is required to reconstruct it. For example, a 3-of-5 split means any three of five shares can recover the key. Two shares might be held by the partner, one by a trusted family member, one in a lawyer’s safe, and one in a separate personal safe. This arrangement prevents any single person from unilaterally accessing the funds, but ensures that legitimate heirs can recover them with coordinated effort.
Before implementing this, couples should test the recovery process with a small amount. Actually recovering a wallet from a phrase and a separate device validates that the procedure works and that both partners understand the steps. Many recovery failures occur because partners who memorized instructions or stored them only in their head never verified the written procedure against reality. Testing also surfaces confusion about whether a device must be initialized in a specific way, whether account discovery is automatic, and whether balances appear immediately or after synchronization.
Transaction workflows and approval processes
In couples using separate devices, a transaction initiated by one partner must still be signed by their own device. They cannot delegate the signing action to their partner without sharing their device, PIN, or recovery phrase. This creates a natural security boundary: even if a partner verbally requests a transaction, the other cannot execute it without physical access to the device. For many couples, this is the intended design. It prevents impulsive decisions and ensures that large transfers cannot happen without the owner’s deliberate hardware-level approval.
However, some couples want more explicit joint approval workflows. This requires moving beyond standard Ledger Wallet features into multi-signature arrangements. One common approach is to use a multi-sig platform that connects multiple Ledger devices, such that a transaction requires signatures from both devices. Services like Unchained or Casa allow couples to set up 2-of-2 or 2-of-3 multi-sig wallets where each partner controls one key. A transaction prepared by Partner A must be signed by both devices—first by Partner A’s Ledger, then by Partner B’s Ledger—before it broadcasts to the blockchain.
The trade-off is operational friction. A 2-of-2 multi-sig protects against unilateral spending but requires both partners to be present (or at least available to review and sign) for every transaction. For a household with frequent transfers, this can become burdensome. For large transfers or sensitive movements, it ensures genuine joint consent. The choice depends on how often the couple needs to move assets and whether the operational burden is acceptable. Couples should also understand that multi-sig on-chain is irreversible: once a 2-of-2 multi-sig address is used, neither partner can unilaterally redirect the funds without the other’s cooperation.
Preventing unauthorized access and managing device compromise
Each partner’s Ledger device is protected by a PIN, typically 4–8 digits. This PIN does not replace the recovery phrase; it prevents someone with physical access to the device from using it immediately. An attacker with the recovery phrase can restore the device on any other hardware and bypass the PIN entirely. However, for household-level security—preventing a partner from casually accessing the other’s device or funds—the PIN is the immediate control. A strong PIN is one that the other partner genuinely cannot guess but that the owner can reliably enter under stress.
Couples should agree on a procedure if a device is lost or suspected to be compromised. If Partner A believes their Ledger has been lost, they should immediately move funds to a new address on their partner’s device or a newly initialized device. The old recovery phrase should be considered compromised. This prevents an attacker from finding the lost device and accessing the funds. The faster the couple can act—ideally within hours—the lower the risk of loss. This highlights why maintaining a functioning second device or understanding recovery procedures before they are needed is important.
Malware on a computer running Ledger Wallet can intercept addresses, pre-populate transactions, or attempt to inject false data into the display. However, the private key signing operation remains on the hardware device, isolated from the compromised computer. The malware cannot steal the private key. It can only manipulate what appears on screen. This is why verifying the receiving address on the hardware device’s display—not the computer screen—is critical before confirming a transaction. If the hardware shows an unexpected address, the transaction is compromised; if the hardware shows the correct address, the transaction is genuine regardless of what malware is running on the computer.
Practical setup steps for a couple
A couple should begin by acquiring two Ledger devices (Nano S Plus, Nano X, or Flex are common options). Each partner initializes their device independently, creates their own PIN, and writes down their own recovery phrase in a physical location only they control initially. The recovery phrases should be stored separately from each other and from the devices. Partner A’s phrase goes in one location; Partner B’s goes in another.
Next, both partners download Ledger Wallet (available via ledger wallet download) on a computer or mobile device. They connect their own Ledger device and add cryptocurrency accounts. Each partner can add their device’s accounts to their own Ledger Wallet instance, creating visibility of their own holdings. If they want joint visibility, Partner A can add Partner B’s public addresses (without needing the private keys) to their Ledger Wallet display, and vice versa.
For shared custody of specific assets, the couple should decide whether to use a multi-sig arrangement or a split-account model. If using split accounts, they document which partner owns which accounts and for what purpose. If using multi-sig, they research and configure a multi-sig provider compatible with their Ledger devices and test the workflow with a small transaction.
Finally, they should create a custody document that describes the arrangement, lists the account structure, and specifies where recovery phrases are stored. This document should be reviewed and updated annually or when circumstances change. They should also perform a recovery test at least once—initializing a new device with the recovery phrase and confirming that funds are accessible—so both partners understand the procedure before they need it in an emergency.
Common pitfalls and how to avoid them
One frequent mistake is storing both recovery phrases in the same location. If that location is compromised—a safe is breached, a lawyer’s file is accessed—an attacker can restore both devices and access all funds. Recovery phrases should be geographically separated or held by different trusted parties. If one phrase is kept in Partner A’s home safe and the other in a lawyer’s office, compromise of either single location exposes only half the assets.
Another pitfall is failing to test recovery procedures before they are needed. A couple who has never actually restored a Ledger device from a recovery phrase may discover during an emergency that they no longer remember the exact initialization steps, or that they stored the phrase in a location that is now inaccessible. Testing with a small dedicated device and a small amount of funds validates the process and builds confidence.
Couples also sometimes assume that Ledger Wallet’s portfolio display is equivalent to ownership or control. Adding a partner’s public addresses to your Ledger Wallet instance allows you to monitor their balance, but it does not give you signing authority. This is intentional, but it can create confusion if not explicitly understood. Similarly, forgetting a passphrase is permanent and irreversible; if Partner A uses a passphrase they later cannot recall, those accounts are inaccessible even with the recovery phrase unless they can recover the passphrase from memory or documentation.
Finally, couples should resist the temptation to simplify by sharing passwords, PINs, or recovery phrases unnecessarily. The goal is to achieve shared visibility and joint financial planning without creating single points of failure. The technical tools—separate devices, account hierarchies, passphrases—are designed to support that balance. Using them correctly means accepting some operational friction: transactions take longer, recovery requires coordination, and neither partner has absolute unilateral power. That friction is the point. It aligns the technical security model with the relationship’s actual governance.
Frequently asked questions
Can both partners use the same Ledger device with different PINs?
No. A Ledger device has one PIN. If both partners know it, either can access the device and sign transactions without the other’s presence. To maintain individual control, each partner should use a separate device with their own PIN and recovery phrase. The separate devices can display the same shared portfolio through Ledger Wallet, but only the partner whose device holds the private keys can authorize transactions.
What happens if one partner loses access to their recovery phrase?
If the recovery phrase is genuinely lost and not stored anywhere, the funds controlled by that partner’s device are permanently inaccessible. This is why couples should store recovery phrases securely in multiple physical locations and test recovery procedures in advance. Documenting which phrase corresponds to which device and account structure also helps prevent confusion during recovery.
How do couples set up true joint approval for transactions?
Standard Ledger Wallet does not support multi-signature natively. True joint approval requires using a multi-signature platform such as Casa or Unchained that connects multiple Ledger devices and requires signatures from both partners before a transaction broadcasts. This adds operational complexity but ensures neither partner can move funds unilaterally. Multi-sig is most practical for larger or less frequent transactions.
