How it works

A deterministic plan for an irreversible action.

Closing an account is several sequential transactions in the right order. LumenWipe shows the whole plan up front, then executes it one confirmed step at a time, re-reading live state and simulating before every signature, so nothing is ever signed on stale data.

The execution loop

Every step runs the same safe loop.

No step trusts a cached value. Each one reconciles against the live ledger, simulates, and waits for your explicit approval before a single byte is signed.

Re-read live state

getLedgerEntries

Simulate

simulateTransaction

Confirm

you approve

Sign in browser

your wallet

Submit XDR

to Stellar RPC

Poll & advance

next step

repeats for every step in the plan

The plan

Eight ordered steps, every reserve accounted for.

  1. 01

    Analyze the account

    Enumerate every subentry (trustlines, offers, data entries, signers) and detect DeFi positions through OctoPos. The result is a single, ordered execution plan.

    opstellar.expert + Stellar RPC
  2. 02

    Normalize signers

    Remove extra signers and reset thresholds so a single key can authorize every remaining step without surprises mid-flow.

    opSetOptions
  3. 03

    Remove data entries

    Clear every ManageData entry in batches, releasing 0.5 XLM of reserve each.

    opManageData (value = null)
  4. 04

    Cancel DEX offers

    Close all open order-book offers, freeing the reserve each one holds.

    opManageSellOffer / ManageBuyOffer · amount = 0
  5. 05

    Exit AMM & DeFi positions

    Withdraw from classic liquidity pools and every supported Soroban protocol, repaying loans and unstaking first where needed, via each protocol's own adapter.

    opLiquidityPoolWithdraw · Blend · Aquarius · Soroswap · Phoenix · FxDAO
  6. 06

    Convert assets to XLM

    Swap every remaining token to XLM along the best available route across Soroban and classic venues.

    opSoroswap API · SDEX path payments
  7. 07

    Remove trustlines

    Once a balance is zero, remove its trustline and release the 0.5 XLM reserve.

    opChangeTrust · limit = 0
  8. 08

    Merge the account

    Execute the final merge, directly to a wallet or through a mediator account for an exchange destination. The base reserve comes back too.

    opAccountMerge
Exchange destinations

The CEX mediator flow.

Exchanges don't support ACCOUNT_MERGE. LumenWipe bridges the gap with a transparent, single-use mediator account, generated in your browser, used once, and cleared from memory.

Source account
the account you're closing
AccountMerge
Mediator account
single-use · generated in browser
Payment + memo
Exchange deposit
validated address & memo

The ~1 XLM that stays as the mediator's base reserve is disclosed upfront. Known exchanges are validated against a registry that enforces the correct memo type.

Resumable by design

Close the tab. Pick up where you left off.

The entire wind-down is an explicit state machine, persisted in IndexedDB, never your keys. On return, the session is reconciled against on-chain state, and any completed step is skipped, so nothing double-executes.

IdleAnalyzingPreflightCompleteStepExecutingStepConfirmedComplete
Architecture

Three layers, one trust boundary.

No bespoke indexer. Every read source sits behind an adapter, so any compatible provider can be swapped in without touching the rest of the system.

Browser
UI · wallet · tx builder · session
keys never leave
Read-only backend
analysis · DeFi adapters · routing · cache
no custody
Stellar network
Stellar RPC · stellar.expert · Soroswap
read-only
FAQ

Questions, answered.

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.

Ready when you are.

Open the app