Could You Recover Your Bitcoin Without Your Provider?

Jake Woodhouse

25. Juni 2026June 25, 2026 · 4 Min. Lesezeit4 min read

I asked Bitcoin Twitter a simple question this week.

If you own meaningful Bitcoin, which worries you more: a 50% drop in price, or losing access to it?

Almost everyone said losing access.

One person put it simply: a 50% drop means you've lost half. Losing access means you've lost everything. Another described being completely shaking while restoring a wallet. Another said losing 2 BTC hurt more than sitting through multiple 50% drawdowns.

This tells us something important about how serious Bitcoiners actually think.

Volatility is uncomfortable. But it's temporary. Losing access can be permanent.

So I want to ask you a direct question: could you recover your Bitcoin without your provider?

Not your family. You. If the multisig platform you're using, the wallet software you rely on, or the company holding one of your keys disappeared tomorrow, could you independently reconstruct your wallet using nothing but what you have documented right now?

I recently asked myself this question about one of my own setups. My honest answer was: I'm not completely sure.

That was uncomfortable. I've been storing Bitcoin in self-custody for over a decade. I think about custody every day. And I still found a gap. I had created a second vault inside a multisig platform and hadn't properly updated my plan to document the derivation path required to rebuild it independently if that provider disappeared.

That's what I'm calling a "provider dependency".

A provider dependency exists when your recovery process depends on a specific company, software, or service remaining available. The scenarios worth thinking through are more common than people realise.

Providers go bust. Ownership changes. Terms change. Software changes. Regulations change. In Australia right now, Unchained no longer opens accounts for Australian residents. That's not a criticism of Unchained. It's a reminder that the environment around your setup is always moving.

This week a friend messaged me about a Sparrow wallet software update. Their instinct was to pause before clicking yes. That instinct was correct. Most people blindly trust the update prompt. The right process involves verifying signatures against the developer's known key before installing anything. If you don't know how to do that, you have a software dependency. You're trusting the interface rather than verifying the source.

Same class of problem as provider dependency. Different surface area.

From 1 July 2026, Australian exchanges are required to collect and share sender and recipient details on every crypto transfer under the AUSTRAC Travel Rule. Exchanges are already asking: is this going to a personal wallet or another exchange? If you're still moving Bitcoin to self-custody, you're doing it in an increasingly regulated environment. Your plan needs to survive regulatory change, not just technical failure.

A friend recently told me their Ledger died inside a 2-of-3 multisig. Overnight, that became a 2-of-2. To move funds to a new setup they needed both remaining keys to work perfectly. That's device dependency. Same class of problem again.

The questions every Bitcoiner should be able to answer honestly:

Could I recover my Bitcoin without my provider? Could my partner or family recover my Bitcoin without my provider? Do I have every piece of recovery information documented independently of provider systems? Have I actually tested recovery end to end? Do I have the wallet descriptor, xpubs, and derivation paths stored somewhere my provider doesn't control? Would these instructions still make sense to someone with basic technical skills in ten years, using whatever tools exist then?

That last question is the one most people haven't asked. Bitcoin custody is a time capsule problem. The documentation needs to work years from now, not just today.

I think of my role as a Bitcoin Custody Architect, rather than a provider. A provider gives you a solution. That's their job. An architect sits one layer above and asks different questions: is this the right solution for this person's situation? What are the tradeoffs? What are the dependencies? What happens if the provider disappears?

You don't choose between the two. You may need both. One provides the tools. The other helps design the system that survives when the tools change.

My last podcast episode asked: could your family recover your Bitcoin without you?

This week's episode I ask: could you recover your Bitcoin without your provider?

Different questions. Both matter.

If your family cannot recover your Bitcoin without you, you have a Bitcoin dependency. If you cannot recover your Bitcoin without your provider, you have a provider dependency. Both are worth taking seriously.

jakewoodhouse.io/bca

Written by

Comments

No comments yet. Start the conversation.