Get back the XLM locked in your Stellar account.
LumenWipe walks you through closing a Stellar account from start to finish: trustlines, offers, data entries, signers, even Soroban DeFi positions. It converts what's left to XLM and merges it out to your wallet or exchange. One guided flow, signed entirely in your browser.
- Normalize signers1 extra key removed+0.50
- Clear data entries1 ManageData entry+0.50
- Cancel DEX offers2 open offers+1.00
- Exit Blend positionSorobanrepay + withdraw+3.84
- Convert assets to XLM3 tokens routed+3.08
- Remove trustlines4 trustlines+2.00
- Account mergevia mediator to CEX+1.00
5.00 XLM in locked reserves unlocked, then balance swept and merged.
Your lumens are locked, and the exit is a maze.
Every Stellar account holds XLM in reserve: 1 XLM for the account itself, plus 0.5 XLM for every trustline, offer, data entry, and signer. That reserve is only recoverable by closing the account, and closing one cleanly is harder than it sounds.
One mistake and it all reverts
A single leftover subentry makes the final ACCOUNT_MERGE fail. You have to cancel every offer, exit every position, sell every asset, and clear every entry, in the right order, before the merge will go through.
Exchanges can't merge
No major exchange supports ACCOUNT_MERGE. Send your remaining XLM to a CEX deposit address and the 1 XLM minimum balance stays frozen forever.
DeFi has no tool at all
Any account with a Blend loan, an Aquarius LP, or a Soroswap position simply cannot be closed with today's tools.
One guided flow. Eight steps. Everything recovered.
LumenWipe reads the whole account, builds a deterministic ordered plan, and executes it step by step, re-reading live state and simulating before every signature. You confirm each move; nothing happens without you.
Analyze
Enumerate every subentry and DeFi position
Normalize signers
Remove extra keys, reset thresholds
Clear data entries
Remove ManageData in batches
Cancel offers
Close every open DEX order
Exit DeFi & AMM
Withdraw from pools and protocols
Convert to XLM
Best route across SDEX & Soroswap
Remove trustlines
Release each 0.5 XLM reserve
Merge
Direct, or via mediator for a CEX
Built for the messy reality of real accounts.
Full Soroban DeFi coverage
The piece the original demolisher lacks. LumenWipe detects positions through OctoPos, then exits each one with its own protocol adapter, repaying loans, withdrawing liquidity, and unstaking before it removes the trustline.
Exchange-compatible merge
A transparent, single-use mediator account bridges the merge to any CEX deposit address, with the right memo, validated.
Allowance inspector
See every token approval your account has granted to DeFi contracts, and revoke risky ones, even without closing.
Resumable sessions
An explicit state machine in IndexedDB. Close the tab mid-flow and pick up exactly where you left off, reconciled on-chain.
Deterministic, auditable plan
The same account state always produces the same ordered plan: testable, reviewable, and never built on stale data.
Simulated before you sign
Every Soroban call runs through simulateTransaction first. You see the result before being asked for a signature.
The trust boundary is your browser.
LumenWipe builds transactions that drain accounts irreversibly, so the design starts from that fact. Your keys are created and used only in your browser and never reach a server. The backend can't touch your account: its one signing key is the shared exchange mediator, which can only co-sign a forwarding payment you already authorized.
- Private keyNever transmitted. Stays in your wallet, or in memory only and cleared after each signing.
- Every destructive stepReviewed as raw XDR and explicitly confirmed before signing.
- Exchange memoRequired and validated for known exchanges; a missing memo blocks submission.
- Backend compromiseIts only key is the shared mediator, which can't sign for your account and can't divert funds (atomic, validated). Wrong read data is caught by simulation and confirmations.
- Strict CSPNo inline scripts, no unsafe-eval. Dependencies are lockfile-pinned and audited in CI.
Wallets, protocols & data sources it speaks to
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.
Still curious? Read the full documentation.
Reclaim the XLM that's been sitting locked.
Try the entire flow on testnet with no funds at risk, then switch to mainnet for the real close.