Recovery requirements and wallet support
The documented operatorless-exit procedure, its state and fee prerequisites, and what eleven reviewed consumer-wallet surfaces exposed.
How to read this topic: 5 principal evidence groups organize 25 supporting records by the question they answer.
Critical boundary: The review identifies implementation, usability, and economic constraints. It does not claim that protocol-level exit is impossible or that a prepared user with current recovery state and external fee funds cannot exit.
Evidence group 01
An all-Operator-outage exit requires current leaf and ancestor state acquired while Operators are reachable; wallet mutations can make a one-time backup stale.
Scope boundary: The state need not use Blink's format. With complete current state, matching keys, and fee funds, the documented procedure can continue without later Operator cooperation.
The exit
Blink's published case study states that a seed cannot rediscover current leaves after Operators are offline. Its documented procedure requires complete, current, validated leaf and ancestor state, represented by a recovery bundle saved while Operators are reachable; with that state, the seed still supplies signing authority. [2 sources]
The exit
Breez 0.23 now durably stores the exit tree and supports state export, correcting the earlier default-persistence gap. Reviewed wallets pinned to 0.22 or earlier do not inherit that capability until they upgrade, collect and protect the state, and integrate a recovery workflow. [4 sources]
The exit
Spark exit state can change when leaves are created, transferred, split, renewed, claimed, or spent. Blink's proposed mobile design therefore refreshes its recovery state after balance-changing events; a mnemonic backup made once cannot encode later tree mutations. [1 source]
The exit
Blink's first documented mainnet recovery bundle omitted a legacy root required for offline construction. The tool initially failed without Operator access and was changed to fetch missing roots explicitly and reject open chains before producing a corrected bundle. [2 sources]
The exit
Breez 0.19.0's exit walker omitted the SplitLocked state used by renewed leaves and could leave out a required parent. Breez 0.23 includes SplitLocked and a regression test, so this is a historical affected-version finding rather than a current-SDK defect. [3 sources]
Evidence group 02
The reviewed reference path constructs and advances ordered packages, persists progress, waits through timelocks, and performs later sweeps rather than broadcasting one transaction.
Scope boundary: Separate tooling can automate these stages. Their complexity establishes operational burden, not cryptographic impossibility.
The exit
Spark's current CLI begins with live leaf discovery and requests external fee UTXO data. In normal mainnet mode it emits transactions and unsigned CPFP PSBTs with manual ordering instructions, but lacks a complete durable broadcast, resume, timelock-monitoring, and sweep workflow. [1 source]
The exit
Spark's FAQ says a user can exit at any time by broadcasting a pre-signed transaction. Its dedicated beta manual separately requires Bitcoin Core v29, external L1 UTXOs, economic leaf selection, exact package ordering, mainnet signing and timelock handling, and warns that the wallet is unusable until completion. [4 sources]
The exit
Blink's published 100,000-sat wallet contained 22 leaves and 253 root-to-leaf package steps. When all packages were first submitted together, 252 were rejected because the transaction graph could not enter the mempool in that form. [1 source]
The exit
Blink's documented workflow advances packages confirmation by confirmation, pauses for CSV refund timelocks, and later requires separate sweeps. Under the documented standard-mempool relay path, automation can resume and parallelize independent leaf chains, but it cannot remove within-chain confirmation ordering or the CSV timelock. [3 sources]
The exit
The documented independent exit requires external on-chain fee funding before the Spark value becomes spendable on chain. A third party could sponsor the UTXO, but doing so replaces the user's funding requirement with a service dependency. [4 sources]
Evidence group 03
Leaf values, ancestry depth, and external fee inputs determine package count and net recovery; a displayed Spark balance alone does not express exit cost.
Scope boundary: Large, shallow leaves can remain economical. The measured figures describe one documented wallet and should not be generalized to every balance.
The exit
Blink’s exit mechanics separate the amount eventually swept from the Spark wallet, leaf value excluded by economic triage, and independent on-chain bitcoin spent on CPFP and funding transactions. A destination amount is therefore not the same measure as net economic recovery. [3 sources]
The exit
In Blink's 100,000-sat case, 18 of 22 leaves holding 9,888 sats cost more to recover than their value at 1 sat/vB. Only four leaves holding 90,112 sats were selected for the documented attempt. [1 source]
The exit
Normal Spark use can split and re-split wallet state into multiple leaves, each with an independently sequenced exit chain. The workload of an emergency exit therefore depends on the wallet’s tree history as well as its displayed balance. [3 sources]
The exit
Blink's published method evaluates each leaf against the CPFP cost of its full exit chain plus final sweep. As fee rates rise, costs rise while leaf value does not, so additional leaves can fall below the economic threshold. This is an economic limit, not a cryptographic one. [3 sources]
The exit
Breez documents that its default leaf optimization leans toward routine payment convenience over unilateral-exit value. More small leaves can mean more fee-bearing exit paths and more value abandoned as uneconomical dust, though wallets can configure the tradeoff. [1 source]
Evidence group 04
The wallets advertise non-custodial control or seed recovery, but the dated review found no complete in-app operatorless workflow across eleven named surfaces. In an all-Operator failure, the ordinary mobile user remains operationally dependent on third-party services.
Scope boundary: Open-source results are snapshot-specific; binary searches cannot rule out obfuscated paths; closed-source results are limited to public claims and observed interfaces.
The exit
The reviewed snapshots and public interfaces for Blink, Primal, Cake, Blitz, Radar, Flash, Agicash, Layerz, Club Orange, Wallet of Satoshi, and Bringin exposed no complete in-app sequence for preserving current exit state, supplying CPFP funds, ordered broadcasting, durable resume, timelock handling, and final sweeping. Closed-source findings are limited to public claims and observed interfaces. [14 sources]
The exit
Breez 0.23 exposes mobile-facing prepare, construct, export, and import operations, correcting the earlier API gap. Its own guide says the SDK never broadcasts, leaving the wallet to provide fee funding, package relay, durable multi-day monitoring, retries, timelocks, and sweeping. [3 sources]
The exit
Cake Wallet describes unilateral exit as publishing a pre-signed transaction. In the reviewed Cake snapshot, the pinned Breez version had not shipped its public mobile exit API and no complete recovery-bundle or unilateral-exit product flow was found. [5 sources]
The exit
Club Orange's published 4.3.3 Android artifact bundled Breez Spark's lower-level unilateral-exit primitives, but its 46 exported BreezSdk method names contained no unilateral-exit or recovery operation and the targeted DEX search found no corresponding user-flow strings. [3 sources]
The exit
Blitz's separate recovery site describes recovery without third parties, but its implementation restores a Spark wallet through live services and calls cooperative withdrawal. It does not construct or broadcast unilateral-exit packages. [3 sources]
The exit
Across Primal, Radar, Wallet of Satoshi, and Bringin, public control or recovery claims were not matched in the reviewed surfaces by a demonstrated complete user-operated exit. Closed-source findings are limited to published claims, instructions, and observed interfaces rather than unseen implementation code. [18 sources]
The exit
Blink's current UI calls the account non-custodial, says only the user can access funds, and presents the seed as recovery. The same source says unilateral-exit conflicts belong to flows the app never starts, leaving outage availability operationally dependent on external services. [3 sources]
The exit
Reviewed wallets advertise full control or non-custodial recovery, but a mnemonic supplies keys—not the current exit graph, fee UTXO, package relay, multi-day recovery state machine, or sweep. Their demonstrated mobile self-custody stops short of independent outage recovery. [5 sources]
The exit
Blitz materially improves recovery by caching and exporting complete leaf and ancestor state for offline use. It still sends execution to separate developer tooling rather than funding, broadcasting, monitoring, refunding, and sweeping inside the wallet. [3 sources]
Evidence group 05
One published account described seed-only recovery and an amount as received before the reviewed record showed the final sweep and full economic accounting.
Scope boundary: Real mainnet packages were advanced without later Operator cooperation. The discrepancy concerns prerequisites and completion language, not whether the exit began.
The exit
Blink's Weekly Brief said the exit used only the seed with no Operators online and that 89,668 sats reached the destination. Its linked case study requires previously saved recovery state and records the selected exits as still awaiting refund maturity and final sweeping. [4 sources]