Wallets and keys
See and make your wallets, save and remove their keys, swap in a fresh deployer and set up standby deployers for the sniper guard.
On this page
Kosher launches and trades with several wallets for each group. This page explains each one, where its key comes from, how to make, save and remove them, and what you must back up. Read it before you fund anything.
The wallets
| Wallet | What it does | Where it comes from |
|---|---|---|
| π³ Deployer | Creates the token and makes the dev buy, its own first buy | Created by Kosher when you set up the group |
| π Bundle | The wallets that buy in the launch | Created by Kosher, or brought in with a sealed import |
| π Holders | Holder wallets for the token | Created by Kosher, or brought in with a sealed import |
| π§ββοΈ Standby deployer | A spare deployer the sniper guard relaunches from | Added before launch |
| πΈ Funder | The group's paying wallet | Created for the group |
Kosher signs transactions with keys it holds for your group. That is how it can buy, sell and withdraw when you tap a button.
Back up the deployer key
When you set up a group, Kosher creates its deployer wallet and says: "π Back up β¦ somewhere offline before you fund it. It is the only copy of this key."
Never paste a key into a chat, a website or a form, and never send it to anyone, including someone who says they are from Kosher.
The π Wallets screen
Tap π Wallets on the panel, or send /wallets. It lists the group's bundle wallets and what each holds, read when you open it.
Each wallet's SOL and, once the token is live, its share of the supply and the leg it bought in. Addresses are shortened; the full ones come with the keys.
π Bundle wallets β Solana
π° Holding Β· 12
| # | Wallet | SOL | Supply | Bought at |
|---|---|---|---|---|
| 1 | u9Ydβ¦8pNu | 0.31 | 1.70% | L1 Β· 2026-11-19T12:02:00.000Z |
| 2 | Z2u7β¦SHm7 | 0.32 | 1.67% | L1 Β· 2026-11-19T12:02:00.000Z |
| 3 | De8dβ¦yp8T | 0.32 | 1.64% | L1 Β· 2026-11-19T12:02:00.000Z |
| 4 | eTRhβ¦4M4j | 0.33 | 1.61% | L1 Β· 2026-11-19T12:02:00.000Z |
| 5 | f8uTβ¦QaF6 | 0.33 | 1.58% | L1 Β· 2026-11-19T12:02:00.000Z |
| 6 | UCxUβ¦yo21 | 0.34 | 1.55% | L1 Β· 2026-11-19T12:02:00.000Z |
| 7 | 7tFCβ¦Deg8 | 0.35 | 1.52% | L1 Β· 2026-11-19T12:02:00.000Z |
| 8 | 2r9vβ¦jNHT | 0.35 | 1.49% | L1 Β· 2026-11-19T12:02:00.000Z |
| 9 | ACazβ¦Cj26 | 0.36 | 1.46% | L2 Β· 2026-11-19T12:06:00.000Z |
| 10 | 5n8Wβ¦sVgC | 0.36 | 1.43% | L2 Β· 2026-11-19T12:06:00.000Z |
| 11 | YY4Mβ¦ZGkF | 0.37 | 1.40% | L2 Β· 2026-11-19T12:06:00.000Z |
| 12 | N4Raβ¦yjBV | 0.38 | 1.37% | L2 Β· 2026-11-19T12:06:00.000Z |
| Button | What it does |
|---|---|
| π Refresh | Reads the balances again |
| β¬οΈ Download keys | Sends the key file again |
| π Make | Makes more wallets |
| π Remove these wallets | Sets the set aside. Shown only for an empty set, before a launch. |
| βΉ Panel | Back to the panel |
Each wallet's tokens, ETH and what it is worth, the total profit on what was put in, and every full address in π Full addresses.
π Bundle wallets
| # | Wallet | OTTR | Supply | ETH | Worth |
|---|---|---|---|---|---|
| 1 | 0xb937β¦41ee | 9.60M | 0.96% | 0.0021 | $417.10 β² $316.10 |
| 2 | 0xdf4cβ¦55ee | 9.48M | 0.95% | 0.0024 | $411.70 β² $310.70 |
| 3 | 0x0546β¦1168 | 9.36M | 0.94% | 0.0027 | $406.30 β² $305.30 |
| 4 | 0x3963β¦cab7 | 9.24M | 0.92% | 0.003 | $400.90 β² $299.90 |
| 5 | 0x7d4dβ¦25d6 | 9.12M | 0.91% | 0.0033 | $395.50 β² $294.50 |
| 6 | 0x1373β¦7037 | 9.00M | 0.90% | 0.0036 | $390.10 β² $289.10 |
| Together | $2,422 Β· 55.80M OTTR + ETH |
| Profit | β² $1,816 on $606.00 put in Β· 4.00x |
| Supply | 5.58% across the wallets |
| Market cap | $43k |
π Full addresses
| 1 | 0xb937c532c605daa86d02d03387602cd4026f41ee |
| 2 | 0xdf4c87a5e136116e68649a44588c46298dda55ee |
| 3 | 0x0546ae20db5fd3819802f937f4eeed01ee731168 |
| 4 | 0x3963b700b79a7f8ba6d710f511320374e3b5cab7 |
| 5 | 0x7d4d4af2e65f9c4d28154ba9583a2ba9607325d6 |
| 6 | 0x13738d58c22d9c6aaebec1317a64f5c0b4ab7037 |
| Button | What it does |
|---|---|
| π Refresh | Reads the balances, prices and market cap again |
| β¬οΈ Download keys | Sends the key file again |
| πΈ Fund (deployer), π§Ή Sweep | Moves ETH from the deployer to the wallets, or back |
| β Make more | Makes more wallets |
| ποΈ Delete these wallets | Deletes the set and its keys. See Remove wallets. |
| βΉ Panel | Back to the panel |
Create wallets
Tap π Make
On a group with no wallets yet the button is π Create wallets; on Robinhood Chain it is β Make more.Send how many
Type a number. With wallets already in the set, the number is how many more to add, and the new ones come from the same recovery phrase.
Wallets in a set
Choose how to make them
β‘ Instant makes them all at once, ready now. β³ With gaps makes them over a few minutes with a random gap between each, in the background, so you can keep using the bot:
KosherbotSampleβ³ Making 12 wallets in the background About 9 min, a random gap between each. Keep using the bot β the keys arrive here as a new message when the last one is made. Until then, launching and funding use the wallets you already had.14:02π WalletsβΉ PanelEither way a wallet only shows on chain once it is funded.
Save the key file
The addresses arrive in the chat and the keys in a file below them. The file deletes itself after 60 seconds, so save it offline straight away.
- Making is one set at a time. While a set is being made with gaps, a second tap says how far it has got.
- Kosher will not add wallets to a set that a funding is still paying.
- A full set of 50 cannot grow. Set it aside first, then make a new one.
Download keys
β¬οΈ Download keys sends the key file again. Its first line is the recovery phrase, which alone restores every wallet in the file in any wallet app; each wallet's address and private key follow.
Remove wallets
Removing a set makes the group stop using it, so you can make a new one. On Solana nothing is deleted: the keys are kept, along with their funding records. Only the bot's owner or the group's admins can remove wallets, and Kosher checks the wallets again when you tap.
Bundle wallets (Solana). π Remove these wallets appears on the Wallets screen only when every wallet is empty and the token has not launched:
| π Remove the 12 bundle wallets? |
| β Checked now | |
|---|---|
| β β β SOL | none β they hold nothing |
| β β β In use | nothing pays them or trades with them |
| β β β Launch | not yet |
| π What it does | |
| β β β The group | stops using them β π Make starts a new set, any size |
| β β β Their keys | kept, never deleted, with their funding records |
Tap π Remove them, then π Make wallets for a new set of any size.
Holder and maker wallets. Tap π in their section of the panel. Kosher removes them only when each holds less than 0.001 SOL, none holds the coin or the pair, and nothing runs on them or pays them:
| π Remove the 8 holder wallets? |
| β Checked now | |
|---|---|
| β β β SOL | dust only Β· 0.0071 SOL in all |
| β β β Coin | none |
| β β β In use | nothing runs on them or pays them |
| π What it does | |
| β β β The group | stops using them β π Make or π₯ import new holders |
| β β β Their keys | kept, never deleted |
If something is in the way, Kosher says what and what to do, such as stopping the spread or moving the SOL out first.
Bundle wallets (Robinhood Chain). ποΈ Delete these wallets deletes the set and its recovery phrase. Kosher refuses while the wallets hold more than dust; empty them first.
Bring your own wallets: sealed import
You can bring wallets you already have into the group with a sealed import. Your keys are sealed on your phone first, so they never appear in the chat in readable form.
Say what the wallets are for
Send/import(or tap π₯ Bring wallets in) and choose π For the bundle, π₯ As holders or π To unload from.Open the import page
Tap π Import keys. The page opens inside Telegram, or as a link.Seal them
The page reads "Seal your wallets" and "For Otter Club Β· bundle". Paste your keys or phrases, one per line, or tap Add a file. Then tap Seal N wallets.Paste the sealed parts into the group
The page shows "N wallets sealed" with a Copy button (or Part 1 of 3 and so on for many wallets). Paste each part, which startsπ LK1 β¦, into the group. Kosher deletes each part as soon as it reads it.Confirm
Kosher shows "π₯ Import wallets Β· N found", with each wallet's balance and history.
KosherbotSample14:02π₯ 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 π For the bundleπ₯ As holdersπ To unload fromβΉ Wallets
π Fresh deployer
On Solana every launch goes out from a deployer that has never launched: bots skip a deployer they have seen launch. Once a deployer has launched, the panel's π³ Solana Deployer says so, and Kosher will not launch from it again.
When the old deployer holds nothing, because you sold everything and swept it home, Kosher swaps in a fresh one by itself. While it still holds something, tap π Fresh deployer:
KosherbotSample7xKpβ¦xYo3, launched $OTTR.
β οΈ It still holds 0.0021 SOL.
Best: sell everything and sweep it home first. The bot then swaps it for a fresh one by itself.
Retiring moves its key to data/deployers/retired/, kept for good, and makes a fresh deployer at the same place, so the launcher and the scripts use the new one from then on. What it still holds stays with the retired key: the bot no longer sells or sweeps from it, so that would be done by hand with that key file. The fresh one is funded from home like the first, never from this one: that transfer would be the one link between them.
- π± Sell its $TICKER β SOL on the panel sells what the old deployer still holds of its token. Do this first if you can.
- π Retire it, make a fresh one appears when the old deployer is empty, and is safe.
- π Retire it anyway retires it while it still holds something.
The fresh deployer has a new address. Fund it the way you funded the first: enough for the dev buy, the launch tip, its accounts and fees. Never fund it from the old one.
Standby deployers
With Sell + relaunch or Sell + buy back, the π‘ sniper guard relaunches from a standby deployer if snipers trip it. It needs one standby for each relaunch, made and funded before the launch. With none, it says "β No standby deployer yet β a sniped launch is keptβ¦". See Sniper guard.
Before the launch, the panel's π³ Solana Deployer section shows the standbys:
| Button | What it does |
|---|---|
| β Standby deployer N of M | Makes the next standby, while you have fewer than the guard's relaunches |
| π‘ Fund standby N | Pays the standby now |
| β³ With delay | Pays it with a delay |
| π | Puts the standby away, its key kept. Only when it holds less than 0.001 SOL and nothing is paying it. |
The π‘ guard screen has the same with β New standby deployer and π§ββοΈ Fund standby N, and shows each standby's SOL against what it needs.
A standby is funded through Husher from the SOL funder, as the deployer is. Husher is an external service that pays your wallets from exchanges, with delays between payouts; it costs about 1.45% and takes longer.
Wallet sets
/sets lists your wallet sets and what they hold, and /wallets lists the bundle wallets.
- Make a set: sets are not made on
/sets. One is created when you tap π Create wallets or π Make them, or when you import wallets. - Remove a set: on
/sets, tap π Name Β· N wallets, then π Yes, delete it. Kosher refuses while the wallets hold more than dust; empty them first. π Refresh reloads the list. - Rename a set: not possible.
KosherbotSample0x301ec0β¦9b7c
Otter (OTTR) Β· 12 wallets
2026-11-18 21:40 Β· empty
no launch yet
Deleting a set destroys its phrase. The wallets become unreachable and anything they hold is gone.Two-tap confirmations
First tap: the check
Kosher shows what will happen: which wallets, how much and where to.Second tap: confirm
Kosher sends it.
A check is good for about 10 minutes; after that a tap says "That choice has expired". Only group admins can use money buttons.
Typed answers
When Kosher asks you to type something, only the person who opened the prompt can answer it, for 10 minutes. Sending any command cancels the open prompt. Kosher deletes your typed answer after reading it.