What a Wallet Set Is
A wallet set is a named container for wallets that SEND generates for you. Every wallet belongs to exactly one set, and the set is the unit the rest of the platform works with: a project points at a wallet set, deposits and withdrawals are driven from a set, and balances are aggregated per set.
SEND mints every keypair server-side. Each private key is encrypted at rest with AES-256-GCM under a key derived for your account alone, with a fresh nonce per wallet, and no read endpoint ever returns key material. Find your sets under "Wallet Sets" in the sidebar.
- A name (required) and an optional description
- A chain -- Solana in practice; the Ethereum option in the wizard is disabled and marked "Coming soon"
- Its wallets, each with an address and an editable label
- Aggregate figures computed on demand: total SOL, total USD value, and the wallet count
Creating a Set
Use the "New Wallet Set" button on the Wallet Sets page. The wizard has four steps -- Basics, Wallets, Settings, Confirm -- and the fields that actually shape the set are on the first two: Name, Description and Blockchain, then how many wallets to generate (default 5) and an optional Label Prefix.
Confirming runs two requests in sequence. The set record is created first, then the wallets are generated in a batch against it. While the batch runs, the progress bar advances one step per keypair as the server streams generation updates over the WebSocket connection, ending with a completion frame.
The Settings step collects anti-detection and delay values that are not sent with either request and are not stored on the set. Giving wallets real on-chain history is a separate feature -- "Age Wallets" on the set detail page, which generates actual swap activity.
Labels and Numbering
Generated wallets are labelled "<prefix> <number>". If you leave Label Prefix blank, the prefix defaults to the set's own name, so a set called Alpha produces "Alpha 1", "Alpha 2", and so on. An explicit prefix is used verbatim instead.
Numbering continues after the wallets already in the set rather than restarting, and numbers are never reused after a wallet is deleted. The Add Wallets dialog previews the effective prefix before you commit.
- Labels are assigned once, at generation time
- Rename an individual wallet at any time from the Wallets tab of the set
- A rename changes the label only -- the address and its keypair are untouched
Limits and Validation
Names, wallet counts and chains are validated server-side, so the same rules apply whether you use the wizard or call the API directly.
- Name: required, 32 characters or fewer after trimming
- Names are unique per account and compared exactly -- "Treasury" and "treasury" are two different sets, and a duplicate is rejected with "wallet set '<name>' already exists"
- Description: optional, up to 500 characters
- Wallets per request: between 1 and 200, rejected outside that range with "count must be between 1 and 200"
- No ceiling on wallets per set -- repeat Add Wallets to go past 200
- Label prefix: optional, capped at 50 characters by the form
- A set that belongs to another account is indistinguishable from one that does not exist: both return 404
Finding a Set
The Wallet Sets page loads 20 sets at a time and pulls the next page as you scroll, ending with an "All wallet sets loaded" marker. It offers a grid and a list view, multi-select for deleting several sets at once, and two counters at the top: Sets and Wallets.
Those two counters are computed over your whole collection (narrowed by the search term), not just the pages currently loaded, so they stay correct while you scroll.
- Search matches the set NAME only, as a case-insensitive substring -- descriptions are not searched
- The chain dropdown filters the results already loaded in the browser; it is not a server-side filter and the Sets/Wallets counters ignore it
- Each card shows the set name, a chain pill, USD value with the native balance beneath it, and the wallet count
Inside a Set
Opening a set shows Total SOL, USD Value and the wallet count across the header, four quick actions, and three tabs. The quick actions are Deposit (SOL via exchange), Withdraw, Add Wallets, and Age Wallets. The tabs are Wallets, Exchanges and Aging. The kebab menu at the top right holds exactly two items: copy the wallet set ID, and delete the set.
The Wallets tab has its own search, a grid/list toggle, and multi-select bulk delete. Per wallet you can deposit, withdraw, refresh, rename, or delete.
Balances are never a stored column -- they are summed from cached on-chain readings, with the SOL leg valued live against the current SOL price. A wallet whose balance is not in the cache contributes zero rather than failing the whole total.
Deleting a Set
Deleting a wallet set archives it. The set stops appearing in the list, in search, and in the Sets and Wallets counters, and it can no longer accept new wallets -- attempting to add some returns "cannot add wallets to an inactive wallet set".
What deletion does not do is touch the wallets. Their records stay active, they keep their keys, and they keep any funds they hold. If you want a set emptied, delete its wallets first from the Wallets tab -- individually or with multi-select -- and then delete the set. Note that a bulk wallet delete is all-or-nothing: if any selected wallet is not an active member of the set, the whole request is rejected.