Getting started

The fastest way to see what Account Demolisher does is to open the live app and run the demo flow. It creates a throwaway testnet account, populates it with the kinds of state the demolisher can clean up, and walks you through closing it.

Open the live app

Go to demolisher.saliht.xyz and click Demolish an account. The connect step has three options.

Option 1: Create a demo account

Recommended for first-time users and anyone evaluating the project. Click Create demo account & continue. A throwaway ed25519 keypair is generated locally in the browser, funded from friendbot, and walked through a 13-step setup that produces an account with:

• Three trustlines (USDC, AQUA, YXLM)
• Two data entries
• One open sell offer
• A co-signer at weight 1
• Demo issuer credit balances (1000 AQUA, 500 YXLM)
• A self-claimable 5-XLM balance
• 50 XLM supplied as collateral to the Blend testnet pool
• A SEP-41 allowance on the native XLM SAC

The Soroswap steps (swap and add liquidity) skip on testnet because Soroswap testnet has no on-chain pools right now. The skip is surfaced as a per-step diagnostic, not a silent failure.

Once setup finishes, the Continue to demolish button takes you straight into the closure flow. A Use demo address shortcut button next to the destination field in the configure step pastes a stable testnet sink address so you can run the demolition without sourcing another wallet.

Option 2: Connect a real wallet

Click Connect wallet to open Stellar Wallets Kit. Freighter, xBull, Albedo, Rabet, Lobstr, Hana, and WalletConnect are supported. The wallet holds the secret key; the app only sees the public key and asks the wallet to sign each transaction. Approve every signing prompt in your wallet of choice.

Option 3: Secret key fallback

If you don't have a wallet installed, the Advanced section reveals a secret-key paste input. The seed stays in browser memory and is used to construct a fresh Keypair for each signing call. It is never persisted, sent to any server, or copied to the clipboard. This path exists for users who genuinely don't have a wallet; the warning above the form is real.

The five-step closure flow

After connecting, the app moves through five steps for every closure:

1. Connect. Pick a signing path (above).
2. Configure. Enter the destination address, an optional memo (required for some exchanges), and opt in or out of any claimable balances the account holds.
3. Preview. The app reads the account, generates the plan, and simulates every step against the live network. You see the audit summary and a node-by-node plan tree before signing anything.
4. Confirm. Type the last four characters of the destination address. A 5-second timer ticks before the confirm button enables. A separate warning shows if the balance is large enough to be worth a second look.
5. Execute. Each node signs in your wallet, submits to the network, and is marked confirmed when it lands. Failed nodes can be retried; recoverable horizon and soroban failures (stale sequence, footprint change, insufficient fee) are auto-classified and retried with the right fix. Slippage breaches surface for explicit user consent instead of retrying silently.

Network selection

The default network is testnet. To use mainnet, the operator sets NEXT_PUBLIC_STELLAR_NETWORK=mainnet at build time. The active network is shown as a badge in the top-right of every page.

You don't have to do anything to pick a network from the UI side. If you're running your own deployment and want to swap, see Self host.