Skip to the page

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:

KosherbotSample
๐Ÿ“ฅ Bring wallets in ยท $OTTR
๐Ÿ“Œ Now 
โ €โ €โ €๐Ÿ‘› Bundle12 wallets
โ €โ €โ €๐Ÿ‘ฅ Holders6 wallets
โ €โ €โ €๐Ÿ“‰ The unload sells from๐Ÿ”„ auto
๐Ÿ‘† What are they for? 
โ €โ €โ €๐Ÿ‘› The bundlethey buy at the launch
โ €โ €โ €๐Ÿ‘ฅ Holdersthe spread sells the bundle's coin to them
โ €โ €โ €๐Ÿ“‰ The unloadit sells from them โ€” your own wallets holding the token, say
๐Ÿ‘› For the bundle
๐Ÿ‘ฅ As holders
๐Ÿ“‰ To unload from
โ€น Wallets
14:02
RoleUsed for
๐Ÿ‘› The bundleBuying in the launch
๐Ÿ‘ฅ HoldersThe spread and pour (Solana)
๐Ÿ“‰ The unloadSelling 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

WayWhat it is
๐Ÿ” Import keysThe 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 themThe bot makes them (๐Ÿ”‘ Create wallets, or ๐Ÿ”‘ Make holder wallets).
๐Ÿ–ฅ The bot's fileA 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.

  1. 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.

  2. Paste your wallets and save

    One wallet a line: a private key, a recovery phrase, or either followed by its address. Other .txt, .csv, .json or .keys files in the folder, named for the group, are read too.

  3. 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.

  4. 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 chainKeys and phrases accepted
SolanaBase58 or JSON-array keys; phrases from Phantom, older Solflare, or solana-keygen (the account with history wins)
Robinhood, Ethereum0x 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 backup saves every wallet file in one zip).

Next steps