Wallet tools overview

There are two very different kinds of wallet here, and mixing them up is the most common way people lose funds. Plus how local keys are encrypted, when the vault locks itself, and which step of the pipeline each wallet tool handles.

7 min readCost:Free, but it prevents most accidentsUpdated 2026-10

First the short version: we never ask for your seed phrase or private key, and we never hold your funds. Every signature happens in your browser and you confirm every transaction yourself.

What you needWhich tool
A batch of fresh addressesBulk wallet generator
An address with a nice endingVanity wallet
See which of a list of addresses still hold fundsCheck balances
Fund new wallets without it looking like one personPrivate transfer
Move what is left in old wallets to a new addressWallet asset migration
  1. Know the two kinds of walletThe first is the browser or mobile wallet you connect with in the top right. It signs, and you never have to hand its key to us. The second is the wallet you generate or import inside a tool (bot wallets, batch tools, private transfer): those keys live in this browser, so a batch run can sign hundreds of transactions for you.
  2. Always back up before you send anythingSafari's ITP, in-app browsers (WeChat and the like) and a routine clear of browsing data can all wipe local storage without asking. The seed phrase is the only real key: keep it and you can rebuild the same addresses on another computer or after a cache wipe.
  3. Only keep what this run needsTop up tool wallets with what this round costs, then sweep the rest out when it ends. Keep large balances in a cold or hardware wallet instead of leaving them sitting in a pile of hot wallets.
  4. Clean up when you are doneImported keys stay in browser storage by default so you can pick up where you left off. On a shared computer, delete the wallets in the bot wallet page or clear the cache when you finish.
  5. Put a lock on local keys (the vault)The wallet module has a wallet vault: encrypt it with a password or a passkey and only ciphertext is written to disk, so copying localStorage or IndexedDB gets nothing usable. Once unlocked, a refresh in the same tab does not ask again; closing the tab or 15 minutes idle locks it, and the padlock in the top bar locks it right away. Without a vault, keys are stored as plain text — convenient, but anyone on this computer can read them.
  6. Test small, then scale upEvery new flow — a new token, a new pool, a new RPC node — gets run once with the smallest amount. Confirm it arrives and that you can sell, then raise the size.

Never do this · If anyone asks you to do one of these, it is a scam

Sending them your seed phrase or private key, moving assets to a "safe address", downloading an "accelerator" they sent, or re-importing your seed phrase on a site you do not know. No one from this platform will ever DM you for a key.

Careful · Where private transfer stops

It scatters where a batch of wallets gets its funding from, which makes chain analysis more expensive. It is not anonymity: timing, amounts and buying the same token still link wallets together.

Related guides