Keys and secrets
What the console stores, how, and what it never stores at all.
Every tool here takes private keys, because every tool signs transactions. This page says exactly what happens to them.
What is stored, and how
| What | Where | Encrypted under |
|---|---|---|
| Wallet book keys | The server's wallet store | A server-side secret |
| Position keys | The position record | The same secret |
| Volume-bot sub-wallet keys | An encrypted vault, one file per run | The same secret |
| Account passwords | The account file | Hashed with a per-account salt, not reversible |
Wallet book keys are decrypted in memory to sign, and to show you a key when you ask with your wallet password.
Position keys are kept because a launch that cannot be sold later is not much of a launch. A position stores which wallet holds what together with the key needed to sell it. You can turn this off per run, and then the position is a record you can watch but not sell from.
Volume-bot keys are written to the vault as the bot creates each wallet, before any money moves to it, so a run that dies badly can still be swept. The vault entry is deleted the moment every wallet in it is empty.
What is never stored
Seed phrases. The Seed Sweeper uses one for the run and discards it. Nothing writes a phrase to disk, in any form.
Your wallet password. It is not stored anywhere in any form that could be turned back into it. That is why it cannot be reset, and why losing it means the keys in the book are unreadable.
What leaves the server
Keys do not. They are sent from your browser to the console's own backend over TLS, and from there only as signed transactions, to the RPC endpoint you configured or to a block builder.
Your RPC sees your transactions
The endpoint in Settings sees everything broadcast through it. For a launch where that matters, use an endpoint you control or one with a private mempool. On BNB Smart Chain the non-bundled paths already send through a private relay, but every read still goes to your endpoint.
Isolation between accounts
Positions, wallets, volume bots and exchange orders are scoped to the account that created them. A job is readable only by its owner, which matters because some job logs contain freshly generated private keys. An admin account has no view into another account's wallets either.
Practical advice
- Use fresh wallets for buying. They are cheap to make and they end the run empty.
- Never reuse a key between this console and a wallet holding anything you care about.
- Treat invite codes as credentials. Anyone with an unused one can create an account.
- Assume the funding wallet is public. Anything funded from one address is linkable to it in a single query. The CEX Funder exists for when that is unacceptable.
- Keep the backup passphrase somewhere other than the server. See Backups.