Questions, answered.
Closing an account is irreversible. Here's exactly how LumenWipe keeps it safe.
Yes. Every transaction is built and signed in your browser, through your wallet or an in-memory secret key. Your private key never reaches our servers. The backend is read-only and stateless. It aggregates on-chain data and is never in the signing path, so no operator (including us) can move your funds.
No. ACCOUNT_MERGE permanently removes the source account from the Stellar ledger. Because the action is irreversible, LumenWipe shows the complete plan up front, simulates each step, and asks for explicit confirmation (with the raw XDR available to review) before every signature.
Everything recoverable. Stellar requires a 1 XLM minimum balance (two base reserves) plus 0.5 XLM for each subentry: every trustline, open offer, data entry, and extra signer. LumenWipe unwinds all of them to release those reserves, converts leftover tokens to XLM, and sweeps the full balance to your destination.
Yes. Exchanges don't support ACCOUNT_MERGE, so LumenWipe routes the final merge through a shared mediator account in one atomic transaction and pays out to your deposit address with the correct memo, so you recover essentially all of your XLM. Known exchanges are validated against a registry that enforces the required memo type, so deposits don't go missing.
This is where LumenWipe goes furthest. It detects and exits positions across Blend, Aquarius, Soroswap, Phoenix and FxDAO, on top of classic DEX offers and AMM pools, using OctoPos for position detection. The full classic wind-down is live today; complete DeFi coverage is on the way.
Any SEP-43 wallet through stellar-wallets-kit: Freighter, xBull, Albedo, LOBSTR, Hana, WalletConnect and more. Power users can also use an advanced secret-key mode where the key is held in memory only for the duration of the close, never persisted and never sent to a server, and wiped when you finish, abort, navigate away, or click "Forget key".
Nothing is lost. The wind-down is an explicit state machine persisted in IndexedDB (never your keys). When you return, the session is reconciled against on-chain state and any step already completed is skipped, so nothing double-executes.
Both. Run the entire flow on testnet with no real funds at risk to see exactly what will happen, then switch to mainnet for the real close. Closing an account on mainnet is irreversible and entirely at your own risk: review each step, the simulation result, and the destination address before you sign anything.