PumpStriker Best Practices: 25+ Pro Tips

Read this once the bot is installed and scanning. Everything in this chapter exists to protect your capital and your setup before a single coin is bought. The one-line summary: prove the bot and its data pipeline on an empty wallet first, trade the hours where exit liquidity lives, and guard your keys like the hot wallet depends on it, because it does.

---

Rule zero: start with an unfunded dry run

Once the bot is installed and started scanning, we strongly suggest running it with an empty wallet first, or no wallet linked at all. The bot does not need a wallet to detect, scan, and send signals. The wallet is only required at the moment you buy through the bot.

Use the first day or two to watch, not trade:

• Watch the bot's behaviour and the quality of its signals. Do the cards arrive fast? Do the scores make sense against what you see on the chart?
• Verify the APIs are returning all the required data. Every score is built from a pipeline of API responses (market data, holder data, security flags, smart-money context). The engine can only score what it receives.
• Understand what a data gap does to a score. If a source is down, late, or returns partial data, two bad things can happen: the engine can miss a huge winner, a runner that goes on to do 100x or more, because a missing field produced a discriminatory, eliminating score; or it can give a good score to a dumping token because the data was corrupted and could not be counter-verified a second time.
• The goal of the dry run: confirm that all API requests are returning and gathering the full data pipeline needed to score a token with high conviction. Only then does a score mean what it is supposed to mean.

Checking all of this costs you nothing when no funds are linked. That is the whole point.

---

If the trading bot misbehaves, stop it and report it

If anything is wrong with the trading side of the Telegram bot, wrong amounts, stuck buttons, failed sells, anything:

1. Stop the bot.
2. Report the bug to bathyrdev@pumpstriker.fun or the official Telegram, with the log file from the bot folder. We will get you fixed right away.
3. In the meantime, the signals keep coming, and you can execute them with any other trading bot of your choice, at your own risk. The engine and the executor are separate by design; a bug in one never has to block the other.

---

Trade the hours where the liquidity lives

Memecoin markets do not behave the same around the clock. These are the structural facts to plan around (all times UTC):

Window	What happens
US hours (~14:00 to 00:00)	This is where memecoin virality lives. Runners need Crypto Twitter attention, and CT is American: most launches, deepest follow-through, best exit liquidity. It is also maximum bundler and sniper competition, so latency edge matters most here and filter edge matters least.
EU/US overlap (~13:00 to 17:00)	Arguably the best risk-adjusted window: volume is ramping and entries have runway into peak hours instead of dying into a dead zone.
Asian session	Thin on Pump.fun outside Chinese meta waves. A genuinely good token launched at 05:00 often flatlines from pure lack of eyeballs, and the bot cannot fix that. Best move: stop the bot during this stretch.
Dead zone (~02:00 to 07:00 weekdays)	Fewer snipers, but the rug ratio does not drop and exit liquidity does. Low competition on garbage is not an edge.

The RPC-credit reason to schedule. If you are on free-tier RPCs, running non-stop can drain your entire request quota within about a week. Stopping the bot through the thin sessions saves your credits for the hours that actually pay.

Coming in the next bot upgrade: start and end trading hours and days, configurable inside the Telegram bot. You will still be able to receive signals in the off hours, but as above, we recommend running during the high-volume sessions.

---

The 10 core practices

1. Run on a VPS, and pick the region deliberately. Use a VPS as close as possible to your Helius Sender endpoint and RPCs; that proximity directly increases your transaction submission speed. Recommended locations: Newark (US East), Salt Lake City (US West), Amsterdam (Netherlands), Frankfurt (Germany), London (UK), Singapore, Tokyo (Japan).
2. Not your keys, not your coins. You already know it, take it as a reminder: it is the first rule in the crypto Bible. Store your keys in a safe place, and that means more than the wallet private key. Your Telegram bot token and chat ID protect the wallet file encryption; treat them like passwords. Never use them on a compromised laptop or VPS.
3. Wired beats wireless. If you run the bot on a laptop, keep it LAN-connected to the internet. The bot has a recovery mode for sudden connection interruptions, but you do not want the Telegram bot offline while a position is open.
4. Trade from a dedicated hot wallet with limited funds. Never link a wallet holding your long-term stack. Top the hot wallet up as needed and sweep profits out regularly.
5. Always run with Stop Loss and Trailing Stop Loss set. The market is tied to BTC and Solana; when the majors dump, the domino effect drags everything down within minutes. SL and TSL are what stand between a red trade and a wiped wallet.
6. Start with small position sizes and scale up slowly. Size your first week so that a full losing streak costs you tuition, not capital. Memecoin outcomes are streaky by nature; survive the streaks first.
7. Back up wallets.json, your .env, and the bot token together, offline. The wallet file is encrypted with the bot token; one is useless without the other. A backup that is missing either half is not a backup.
8. Keep the machine clean and current. Update the OS and Node.js, enable the firewall, and use SSH keys instead of passwords on the VPS. The bot's security ends where the machine's security fails.
9. Watch your RPC dashboards. Check your Helius usage a few times a week. Hitting a rate cap mid-session degrades scoring data silently, and degraded data means degraded scores (see rule zero).
10. Update the bot from official sources only. Pull updates only from the official repository and links published on this site or the official Telegram. Fake "updated" copies of trading bots are a known theft vector.

---

15 extra tips from the trenches

1. Journal your first 50 signals. Score, entry, outcome, and what you did. A week of notes teaches you more about how to trade the cards than any documentation can.
2. Respect signal freshness. A memecoin entry decays in seconds, not minutes. If you see a card late, the move may already be crowded; chasing a signal that has already pumped is a different, worse trade than the one the engine flagged.
3. Take partial profits into strength. Sell a portion into the pump and let the trailing stop manage the rest. Round-tripping a green position to zero is the most common self-inflicted wound in this market.
4. Do not manually override the safety wall. If the engine vetoed a token, buying it anyway because the chart looks good defeats the entire purpose of running a filter.
5. Keep a SOL buffer for fees. Never deploy 100% of the hot wallet. Failed sells for lack of fee SOL, during a dump, is a preventable disaster.
6. Check network conditions before sizing up. During Solana congestion, landing transactions gets harder and slippage grows. Congested chain, smaller size.
7. Mind the macro calendar. Major macro events (rate decisions, CPI prints, big exchange news) move BTC, and BTC moves everything. Flat or tiny sizing through scheduled volatility is a strategy.
8. One wallet, one bot instance. Never run two bot instances against the same wallet; they will fight over nonces, balances, and positions.
9. Use a dedicated Telegram bot for trading. Do not reuse a bot token from another project, and do not share the trading bot's group with anyone. One token, one job.
10. Redact before you share. When reporting a bug, share the log file, never your .env. Double-check pasted screenshots for tokens, keys, and chat IDs before they leave your machine.
11. Restart after every update and check the dashboard. A clean restart plus a one-minute dashboard glance confirms the engine, the bot, and the data feeds all came back healthy.
12. Never operate the bot over public Wi-Fi. Hotel and cafe networks are hostile territory for anything that touches keys. If you must check positions on the go, do it through Telegram on mobile data; the keys stay home.
13. Rotate credentials after any scare. Suspicious login, lost laptop, weird VPS activity: rotate the Telegram bot token, move funds to a fresh wallet, and reinstall from the official source. Assume compromise, act cheap.
14. Set a daily stop and honor it. Decide before the session what a red day costs, and when it is hit, stop the bot and walk away. The market reopens tomorrow; revenge trading against a dump does not end well.
15. Re-run the dry run after big changes. New VPS, new API keys, new bot version, new region: run unfunded for a few hours again. Five cheap hours of verification beats one expensive surprise.

---

The mindset

The bot is a filter and an executor, not a promise. It exists to put better-vetted tokens in front of you faster than you could find them yourself, and to execute your decisions with protection layers a human cannot match at 3 in the morning. What it cannot do is guarantee outcomes in a market driven by human behaviour. Nobody can, and anyone who says otherwise is selling something worse than nothing.

Run it unfunded until you trust it. Trade the sessions where liquidity lives. Protect the keys. Size to survive. NFA, DYOR, and never risk more than you can afford to lose.