Bring wallets in
Every way to add wallets you already hold to a group, including the file on the bot's computer.
On this page
๐ฅ Bring wallets in adds wallets you already hold to a group. Open it from the group's Wallets screen, or send /import. First choose what the wallets are for:
| ๐ฅ Bring wallets in ยท $OTTR |
| ๐ Now | |
|---|---|
| โ โ โ ๐ Bundle | 12 wallets |
| โ โ โ ๐ฅ Holders | 6 wallets |
| โ โ โ ๐ The unload sells from | ๐ auto |
| ๐ What are they for? | |
| โ โ โ ๐ The bundle | they buy at the launch |
| โ โ โ ๐ฅ Holders | the spread sells the bundle's coin to them |
| โ โ โ ๐ The unload | it sells from them โ your own wallets holding the token, say |
| Role | Used for |
|---|---|
| ๐ The bundle | Buying in the launch |
| ๐ฅ Holders | The spread and pour (Solana) |
| ๐ The unload | Selling from wallets that already hold an adopted token (Solana) |
An Ethereum or Robinhood group goes straight to its bundle: holders and the unload are Solana's.
The ways in
| Way | What it is |
|---|---|
| ๐ Import keys | The sealed import: you type the keys on your own phone or computer, and they travel sealed. One wallet or hundreds. See Wallets and keys. |
| ๐ Make them | The bot makes them (๐ Create wallets, or ๐ Make holder wallets). |
| ๐ฅ The bot's file | A text file on the computer running the bot. Only the owner can use it. |
The bot's file
Keys never travel through Telegram on this route. The bot makes one template file per group in the data/import/ folder of the project, named like the group's deployer file, for example NPC_-_RELAUNCH--1004342150758.txt (a group with no deployer file yet gets group-<chat id>.txt). A group reads only files whose name ends with its own chat id, so a renamed group still finds its file and no group reads another's.
Open the template
On the bot's computer, open the group's file. It holds comment lines and three example lines that read
PASTE-A-PRIVATE-KEY-OR-RECOVERY-PHRASE-HERE. Lines left as they are are skipped.Paste your wallets and save
One wallet a line: a private key, a recovery phrase, or either followed by its address. Other
.txt,.csv,.jsonor.keysfiles in the folder, named for the group, are read too.Check
Tap Check. Kosher shows each address with its balance and history; ๐ฃ means it has none. A key or phrase is never shown: only addresses, file names and line numbers. A line it cannot read keeps the file as it is.
Add or make a new set
Tap โ Add to join the group's bundle, or ๐ Own set to keep them apart. Only what the check showed is imported, and only within 10 minutes of the check.
After an import, the files that held wallets are deleted, because the keys now live in the group's wallet set. The template comes back empty.
What it reads
| Group's chain | Keys and phrases accepted |
|---|---|
| Solana | Base58 or JSON-array keys; phrases from Phantom, older Solflare, or solana-keygen (the account with history wins) |
| Robinhood, Ethereum | 0x keys; MetaMask phrases (the usual path) and Ledger Live phrases |
On Robinhood and Ethereum, history is read as the wallet's nonce and balance on the group's launch chain.
Rules
- Imported wallets have their own keys. Every script signs with them like the bot's own wallets.
- Import is refused while ๐ wallet activity or the bot's funding is running.
- ๐ Unload: the wallets become the group's holder set and the unload sells from it.
- Back up the file, not a screenshot: after the import, the keys live in the group's wallet set, so back that up (
npm run backupsaves every wallet file in one zip).