Spark wallet review · checked 2026-09-11
Blitz Wallet and Spark
Blitz Wallet is included in this review of wallets and wallet surfaces that use, expose, or publicly describe Spark. The question tested here was whether the reviewed product provides a complete in-app unilateral-exit workflow when Spark operators are unavailable.
Review result
No complete in-app exit flow found
Stable Android v0.7.15 contains the recovery-bundle exporter previously described as pre-release. It refreshes available state and can export cached leaves and ancestors when the live fetch fails. Its export excludes every leaf below 16,348 sats and records the omitted total. The recovery link opens external Blink tooling; no complete in-app broadcast-and-resume executor was found.
Surface reviewed: public mobile source
Release or source boundary: Stable Android v0.7.15 (September 7) release source and current default branch were reviewed. The inspected exporter, leaf store and Spark adapter are identical. No binary runtime exit was performed.
What the review found
incremental local leaf and ancestor caching with retryable pending state best-effort online refresh before export, with cached-state fallback when the leaf fetch fails spark.unilateral-exit-bundle.v1 export through the device share sheet separate totals for leaves excluded below the application’s 16,348-sat threshold external Blink recovery tooling and Spark documentation links
What this does not establish
This is a dated, bounded review of the named source, release or public documentation. It does not establish that every version behaves identically, that a private implementation has no recovery path, or that protocol-level unilateral exit is impossible. A partial SDK capability, seed backup or cooperative withdrawal is not counted as a complete operatorless mobile recovery flow.
Evidence and limits
- Export is a useful implemented prerequisite. It does not by itself execute an exit or prove the cached graph is complete and current.
- The 16,348-sat threshold is hard-coded application policy, not a universal protocol or Bitcoin consensus minimum. Actual economics depend on path and fee rate.
- A nonempty ancestor cache is not a per-leaf completeness proof. The exporter can fall back to old cached state when live queries fail; missing state cannot be reconstructed by a seed alone.
- The release source was inspected; the published Android binary was not executed in an operator-outage test.
Original source · Original source · Original source · Original source · Original source · Original source · Original source