Skip to main content
Operating on Stellar accumulates accounts the same way operating on AWS accumulates instances: deposit accounts per customer, payout channels, distribution accounts from a finished airdrop, test accounts that outlived their experiment. Each one holds at least 1 XLM, usually more, and each one is a small liability until it is cleanly retired.

​
Batch decommissioning

The REST API takes a list of addresses and returns a per-account plan: what each account holds, what the wind-down steps are, what XLM lands at the destination. An operator drives execution from their own backend through the hosted API and signs with their own keys; LumenWipe never holds anything. This is the difference between “we should clean those up someday” and a script that runs in an afternoon. Typical fleets:
  • Channel and payout accounts from a payments or remittance operation that changed architecture.
  • Airdrop or campaign distribution accounts that finished their purpose but still hold trustlines and dust balances.
  • Per-customer deposit accounts at an anchor or custodial service after migration to a different model.
  • Test and staging accounts that were funded on mainnet for a launch rehearsal.
Leftover non-XLM balances are not an obstacle: the plan converts them to XLM before removing the trustlines, and anything that cannot be converted or closed safely is reported as a blocker for that account rather than silently skipped, so a batch run never half-closes anything.

​
What the SDK sends, and to whom

LumenWipe supports only the hosted API at api.lumenwipe.com. @lumenwipe/sdk is a thin fetch client to that API: it builds no plans and no transactions locally, and it has no @stellar/stellar-sdk dependency. Every account address you send for analysis, and the destination of the close, reaches LumenWipe, which reads the network and builds the unsigned transactions on its side. Self-hosting is not supported. Your signing keys are never sent. Transactions come back unsigned, and you verify and sign them in your own backend. If your operations team cannot send account lists to a third party, this API is not the right tool for those accounts. See the SDK overview for what the client does and does not do.