A wallet's mobile app disappearing from the app store feels like the end of the whole system — but self-custody Bitcoin does not work that way. When Samourai Wallet's backend infrastructure went dark after its coordinator servers were seized, funds already in a user's wallet remained exactly as accessible as before, because self-custody was never about Samourai's servers staying online. It was about the seed phrase, which nobody seized. An app disappearing and money disappearing have nothing to do with each other in a self-custody system. What actually broke was the privacy-coordinator features — Whirlpool and Ricochet — that depended on Samourai's own servers. The underlying wallet software and any BTC held in it were unaffected. Bitok Arena's analysis distinguishes the feature that broke from the self-custody property that did not.
Self-custody means the keys were never on someone else's server to begin with. A coordinator shutting down is a service disappearing — not a vault being seized. The lesson from Samourai is not that self-custody failed. It is that a specific server-dependent feature stopped working. The distinction matters because the fix is completely different: the first problem is unsolvable; the second is a straightforward wallet migration.
That distinction matters for anyone reconsidering their wallet setup after watching a coordinator-dependent service go dark. A custodial exchange freezing withdrawals during a liquidity crunch is a fund-access failure, because the exchange holds the keys. A non-custodial coordinator going offline is a feature-access failure, because the keys were never there to begin with. Conflating the two leads to the wrong fix — and missing the fact that the funds were accessible throughout the Samourai event.
What Actually Needs to Survive a Shutdown
The events around Samourai clarified something worth generalizing: a wallet's core function — holding keys, signing transactions, broadcasting to the network — does not require any company's server to keep running. Signing a transaction is math performed locally with a private key the wallet already holds. Broadcasting it is relaying that signed transaction to any node on the Bitcoin network, of which thousands run independently. Neither step requires a single company's infrastructure — only convenience features layered on top typically do. CoinJoin-style mixing requires a matchmaking server; basic sending and receiving does not.
Bitok Arena reviewed the architectural properties that determine whether a self-custody wallet's core functions survive a company-level shutdown, identifying the checks that distinguish resilient architecture from coordinator-dependent architecture.
Local key storage — seed phrase and private keys must be generated and stored on-device; any wallet requiring a remote server to hold or generate keys fails this check; Samourai passed — the keys were always local.
Broadcast independence — the ability to send a transaction should not require a single proprietary server; wallets that can connect to any public Bitcoin node maintain broadcasting capability even if their default node goes offline.
Optional vs core features — CoinJoin coordination is a privacy add-on layered on top of core sending; Samourai's Whirlpool and Ricochet were optional; basic custody was not.
That architecture question is what many Samourai users found themselves asking for the first time — not because self-custody had failed, but because it was the first moment a coordinator-dependent feature going away made the distinction between core function and add-on function suddenly visible. A wallet's marketing rarely leads with its architecture; it leads with its features, and a coordinator-dependent privacy tool looks, from the interface, indistinguishable from a core sending function until the moment the server behind it goes quiet.
What Standard Transactions Actually Require
Standard on-chain Bitcoin transactions — the kind used for any payment, competition entry, or self-custody transfer — require less from a wallet than a full-featured privacy wallet is built to provide. Any self-custody wallet capable of a standard on-chain send meets the requirement. No coordinator, no mixing service, no proprietary server dependency.
What Standard On-Chain Transactions Need
Bitok Arena reviewed the specific wallet requirements for standard on-chain Bitcoin transactions, identifying the properties that actually gate participation and the one that is merely preferable.
Self-custody control — the user holds the seed phrase, not a server that could be seized or shut down; the fundamental custody property Samourai maintained throughout its shutdown event.
Standard on-chain sending — the ability to send BTC to a destination address without requiring a coordinator or mixing step; any wallet that can perform a standard Bitcoin mainnet transaction meets this requirement.
Native SegWit, preferred — bc1q addresses produce smaller transaction sizes and lower fees; broadly supported in modern wallets; not a hard gate but consistently recommended.
The simplicity is worth stating directly: the feature that went dark with Samourai's coordinator servers was never a requirement for standard on-chain Bitcoin transactions. The migration is a matter of picking any well-regarded self-custody wallet with standard on-chain support. Electrum, Blue Wallet, Sparrow Wallet, and most other established non-custodial Bitcoin wallets meet all three criteria without any coordinator dependency. The same three-point check — local keys, independent broadcast, clear distinction between core and optional features — applies to any candidate wallet regardless of which replacement gets chosen.
The Property No One Could Seize
Servers get seized. Companies fold. Coordinators go dark. None of it touches a private key that was never stored anywhere near them. The Samourai shutdown illustrated exactly this: the coordinator servers were seized, the backend went dark, the privacy-coordination feature stopped working — and the BTC held in every Samourai user's wallet remained under their control throughout, accessible via any wallet software that could read the same seed phrase. That is what self-custody means, and it is the property that survived intact.
Bitok Arena's analysis of the Samourai shutdown finds the self-custody property worked exactly as designed — funds remained accessible because keys were never on the seized servers. The migration question is not about recovering from a self-custody failure. It is about replacing a privacy feature that required a coordinator with any wallet that provides standard on-chain functionality without one.
Whatever wallet replaces Samourai in daily use, the underlying self-custody principle carries forward unchanged. Keys controlled by the user, not a company — that is the only property standard on-chain Bitcoin activity requires from a wallet, and it survived the Samourai shutdown intact because it was never dependent on the servers that were seized.
Bitok Arena's review of the Samourai shutdown finds the coordinator servers' seizure took down CoinJoin privacy coordination, not self-custody — user funds remained accessible throughout because keys were never on the seized servers. Standard on-chain Bitcoin transactions require local key storage, independent broadcast capability, and basic send functionality; none of those properties depended on Samourai's coordinator servers. Any established non-custodial wallet providing those three properties supports standard on-chain activity without requiring the coordination features that broke.