Unilateral-exit readiness
Exit-state backup must track wallet mutations; a one-time seed backup cannot encode later state
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
What the evidence shows
Technical and product details
- Documented behavior
Blink's mobile-integration plan says applications must not rely on seed-only unilateral recovery and should refresh an encrypted recovery bundle whenever an event can change the wallet's leaves or ancestors. 1
Supporting material shown on this page
Blink mobile integration planPinned source code · github.com · checked 2026-07-14 Relevant lines from the pinned source · open raw file 1# App Integration Plan - Examples
The plan names startup after synchronization, deposit claims, incoming and outgoing Spark transfers, swaps or withdrawals, completed receive flows, and leaf optimization as refresh triggers. 1
Supporting material shown on this page
Blink mobile integration planPinned source code · github.com · checked 2026-07-14 Relevant lines from the pinned source · open raw file 1# App Integration Plan - Operational consequence
A consumer implementation needs durable refresh, completeness validation, and restart-safe recovery state in addition to mnemonic backup. 1
Supporting material shown on this page
Blink mobile integration planPinned source code · github.com · checked 2026-07-14 Relevant lines from the pinned source · open raw file 1# App Integration Plan
Scope control
What this does not establish
- The plan identifies events that can change exit state; it does not claim every synchronization or every listed event necessarily mutates a particular wallet. Atomic update behavior is an implementation requirement inferred from keeping wallet state and its backup consistent, not a measured result in the plan. 1
Sources and excerpts
Primary sources
The relevant details and available source-code excerpts appear alongside the claims above. This list preserves the complete original-source trail for independent verification.
Blink mobile integration plan
Pinned source code · github.com · Pinned or archival · checked 2026-07-14
How sources, absence findings, and limitations were evaluated