A wallet's mobile app disappearing from the app store feels like the end of the whole system — but self-custody Bitcoin doesn't work that way. When Samourai Wallet's backend infrastructure went dark earlier this year after its coordinator servers were seized, funds already sitting 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. That's a distinction worth sitting with: an app disappearing and the money disappearing have nothing to do with each other in a self-custody system — the wallet interface is a window onto the blockchain, not a container holding the coins inside it. What actually broke wasn't fund access — it was the specific privacy-coordinator features, Whirlpool and Ricochet, that depended on Samourai's own servers to function. Those coordination services required a live backend to match participants for CoinJoin rounds; once that backend went offline, the coordination stopped, even though the underlying wallet software and any BTC already held in it were unaffected. CoinJoin-style mixing works by combining several participants' transactions into a single joint transaction, which requires some party — historically Samourai's own servers — to match those participants together in real time. Remove that matchmaking layer and the individual participants can still hold and send their own BTC, including on to a Bitok Arena round, which never depended on the coordinator feature that actually broke. They simply lose the specific privacy technique that depended on being matched with others.
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.
That distinction matters for anyone reconsidering their wallet setup after watching a coordinator-dependent service go dark: the lesson isn't "self-custody failed," it's "a specific server-dependent feature stopped working," a much narrower problem with a much simpler fix — moving to a wallet that doesn't depend on a single company's servers staying online for basic sending and receiving. It's a distinction with real precedent elsewhere in crypto, too — 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, and conflating the two leads to the wrong fix.
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 — doesn't require any company's server to keep running. Only optional add-on features layered on top, like coordinated mixing, typically do. Signing a transaction is math performed locally with a private key the wallet already holds; broadcasting it is simply relaying that signed transaction to any node on the Bitcoin network, of which thousands run independently around the world at any given time. Neither step has ever required a single company's infrastructure specifically — only convenience features layered on top of that core function typically do.
What to check in a wallet before treating it as resilient to a company-level shutdown:
Local key storage — seed phrase and private keys should be generated and stored on-device, never dependent on a remote server to exist.
Broadcast independence — the ability to send a transaction shouldn't require a single proprietary server; open node connections are more resilient.
Optional vs core features — privacy add-ons that need a live coordinator are useful but shouldn't be confused with the wallet's core custody function.
None of these three properties depend on which specific company built the wallet. They depend on how the wallet is architected underneath the interface.
That architecture question is exactly what a lot of Samourai users found themselves asking for the first time — not because self-custody had failed them, but because it was the first moment a coordinator-dependent feature going away made the difference between core function and add-on function suddenly very visible. For most users, that question had simply never come up before, because 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.
Setting Up a Bitok Arena Wallet
None of that migration complexity carries over to what Bitok Arena actually needs from a wallet. Any self-custody wallet capable of a standard on-chain transaction clears the bar — no coordinator, no mixing service, no proprietary server dependency of any kind. Native SegWit (bc1q) is the preferred sending format, since it keeps network fees lower, but it's a recommendation rather than a gate on entry. That's a narrower bar than the one a full-featured privacy wallet is built to clear, and intentionally so — a competition round only ever needs one thing to happen correctly: BTC leaving a self-custody wallet and arriving at a single destination address on time.
What a wallet needs to support Bitok Arena participation, regardless of which app a user migrated from:
Self-custody control — the user holds the seed phrase, not a shutdown-vulnerable third party.
Native SegWit, preferred but not required — a bc1q address keeps transaction fees lower and is broadly supported across modern wallets.
Standard on-chain sending — no coordinator or mixing step is required to send BTC to the master wallet.
Whatever wallet a former Samourai user lands on next, the first and third points are what actually gate participation — Native SegWit just makes the send a little cheaper.
That simplicity is worth stating directly: the feature that went dark with Samourai's coordinator servers was never something Bitok Arena participation depended on in the first place, which makes the migration a matter of picking any well-regarded self-custody wallet with standard on-chain support. Anyone weighing several replacement wallets can apply the same three-point check outlined earlier — local keys, independent broadcast, and a clear line between core and optional features — to any candidate, regardless of which app gets recommended.
The Part No One Could Seize
That's the part worth remembering long after this specific shutdown fades from the news cycle. Servers get seized, companies fold, and coordinators go dark — none of it touches a private key that was never stored anywhere near them.
A coordinator server can be seized. A seed phrase written on paper in a drawer can't be. The migration question was always about which one a setup actually depended on.
Whatever wallet replaces Samourai in daily use, the underlying self-custody principle it was built on — keys controlled by the user, not a company — carries forward unchanged. That's the only property a Bitok Arena entry actually needs from a wallet.
Samourai's coordinator shutdown took down a specific privacy feature, not self-custody itself — the seed phrase still controls the funds regardless of which server went offline. Pick any self-custody wallet capable of a standard on-chain send, favor Native SegWit if it's available for the lower fee, then send BTC to the Bitok Arena master wallet and get back to competing on today's leaderboard without a single coordinator in the chain.