PumpStriker filters: every setting, default and safety rule
PumpStriker filters work in two layers. The Engine applies fixed rules to every token: eleven safety kills and four nested safety tiers that set grades A, B and C. Your Telegram bot then applies your filters: minimum score, market-cap and liquidity bands, lowest grade and auto-buy trading hours. Unreadable bounds, and unknown liquidity against a set bound, fail closed.
By Mezyan D, Bathyr Devs Last reviewed
Layer 1 · Engine rules, fixed
- Scope and age
- Fire line
- Fresh price
- Safety kills
- Safety tiers
- Grade A, B, C
Layer 2 · Your filters, in the bot
- Signals Active
- Min Score
- Market cap
- Liquidity
- Lowest grade
For auto-buy only: the trading-session window and the auto-buy guards.
What are the key facts about PumpStriker's filters?
| Your filters | Signals Active, Min Score, market-cap and liquidity bands, lowest card grade, trading-session windowLive |
|---|---|
| Telegram default | Grade B or better |
| Fail closed | An unreadable bound, or unknown liquidity against a set bound, removes the card and the buy |
| Safety kills | 11 hard rules in the Engine (K1 to K12, no K7); an unknown value never killsLive |
| Safety tiers | 4 nested auto-buy tiers (BS, B0, B1, B2) that set grades A, B and CLive |
| Recorded labels | More than 30 named risk and data-quality labels, recorded only |
| Auto-buy | Off by default, dry run first, default caps, one buy per tokenBeta |
| Exits | The default plan or your own preset per grade; the hard-rug exit is always keptLive |
| Manual trades | Balance check, one buy at a time per wallet and token, duplicate-buy guardLive |
- Live
- In the current build and on by default, or on when you turn it on.
- Beta
- Works, but experimental, opt-in and capped.
- Needs setup
- Built, but off until you configure it.
Which filters can I set in the Telegram bot?
These are the settings you control in your own bot, with their defaults and allowed ranges. Filters that apply to cards also apply to auto-buy.
| Filter or setting | Default | Range or options | Applies to |
|---|---|---|---|
| Signals Active | ON | ON or OFF (OFF = no cards and no auto-buy) | Cards and auto-buy |
| Min Score | None | 0 to 100, or none, compared with the signal's score. A token under 60 minutes old always scores 85, so any Min Score above 85 hides every signal on tokens younger than 60 minutes | Cards and auto-buy |
| Min / Max market cap | None | USD; accepts 150k, 1.5m or $150,000; the minimum must be at most the maximum; an unreadable stored bound fails closed | Cards and auto-buy |
| Min / Max liquidity | None | USD; unknown liquidity fails any set bound | Cards and auto-buy |
| Lowest card grade | B | A, A and B, or all | Cards only (an auto-buy you would not see still sends a one-line notice) |
| Trading-session window | OFF (24/7) | USA 08:00 to 17:00 New York, Europe 08:00 to 17:00 London, Asia 09:00 to 18:00 Tokyo, or a custom start, stop and time zone; a malformed start, stop or time zone (or start = stop) leaves the window open | Auto-buy only; cards and exits are never gated |
| Auto-buy mode Beta | Off | Off, dry run or live (live needs a strategy PASS plus a typed confirmation) | Auto-buy |
Dry-run safety default (BOT_DRY_RUN) Beta | On | Off only when set to 0, false, no or off | Auto-buy sends |
| Buy keyboard | 0.1 / 0.5 / 1 SOL | Up to 8 positive amounts | Card buttons |
| Signal buy amount | 0.01 SOL | Positive SOL | Each auto-buy, and /buy when no amount is typed |
| Global slippage | 3% | 0.1 to 50% | Manual sells, exits, and auto-buy when the Signals value is unset |
| Per-token slippage | Unset | 0.1 to 50% | Sells of that token |
| Max slippage on retry | 15% | 0.1 to 50% | Take-profit retries |
| Priority fee | 100,000 lamports | 0 to 5,000,000 | Standard RPC lane (pump.fun direct trades use Helius' live fee estimate by default) |
| Anti-MEV | OFF | Global and per token | Send path (Helius Sender, 0.0002 SOL tip) |
| Allow Duplicate Buy | OFF | ON or OFF | Manual buys |
| Auto-Sell by Grade | ON (OFF = default EA plan) | Per grade: follow the plan, or a custom preset | Signal positions |
What does fail closed mean?
When the bot cannot read a value a rule needs, it blocks instead of letting the signal or the buy through.
- An unreadable stored market-cap bound removes the card and the buy.
- Unknown liquidity fails any liquidity bound you set.
- If the wallet balance cannot be read, a real auto-buy is skipped.
- If the caps file cannot be read, auto-buy is held for 24 hours; an invalid cap value blocks auto-buy.
- In the Engine, unknown mint authority, freeze authority, sell tax or top-10 share marks the signal safety pending, which closes every auto-buy tier.
Two rules stay open by design: a malformed trading-session window leaves the auto-buy window open, and an unknown launch-run does not block Telegram eligibility.
Which tokens does the Engine remove before any card?
Eleven safety kills run on GMGN's data before a decision. A token that fails any of them is stored as killed and never sent to the bot. There is no K7.
K1Honeypot
GMGN reports the token as a honeypot.
Kills only on a definite true.
K2Cannot sell
The token cannot be sold.
K3Blacklist
The token has a blacklist function.
Kills only on a definite true.
K4Mint authority
Mint authority is not renounced.
Unknown sets safety pending.
K5Freeze authority
Freeze authority is not renounced.
Unknown sets safety pending.
K6Sell tax
A sell tax of 10% or more.
Unknown sets safety pending.
K8Mayhem
Launched in pump.fun Mayhem mode.
K9Dev wallet
The creator wallet holds more than 25%.
K10Top-10 holders
The ten largest holders hold 50% or more, as GMGN reports it.
Unknown sets safety pending.
K11Wash trading
Wash trading is flagged.
K12Tiny market cap
Market cap under $5,000.
K1 and K3 kill only on a definite true. For K4, K5, K6 and K10 an unknown value does not kill: it sets safety pending, which makes the signal grade C and closes every auto-buy tier. Other unknown checks are recorded as data gaps and re-checked for 5 minutes after the signal.
How do the safety tiers set the grade?
A tier is open only when none of its blocks is true and every needed fact is known; an unknown fact keeps it closed. Each block below is an acting label on the decision.
| Block (acting label) | BS | B0 | B1 | B2 | Rule |
|---|---|---|---|---|---|
| safety-pending | Closes BS | Closes B0 | Closes B1 | Closes B2 | Mint authority, freeze authority, sell tax or top-10 share unknown |
| line-unconfirmed | Closes BS | Closes B0 | Closes B1 | Closes B2 | Fire line not met on the frozen input |
| liq-unknown | Closes BS | Closes B0 | Closes B1 | Closes B2 | Effective liquidity unknown |
| thin-liquidity | Closes BS | Closes B0 | Closes B1 | Closes B2 | Liquidity under 2% of market cap |
| pool-lt-1k | Closes BS | Closes B0 | Closes B1 | Closes B2 | Pool under $1,000, or drained |
| below-10k | Not checked by BS | Closes B0 | Closes B1 | Closes B2 | Market cap under $10,000 |
| knife | Not checked by BS | Closes B0 | Closes B1 | Closes B2 | Price at or below 70% of its 10-minute high, or a 5-minute drop of 30% or worse |
| spike5 | Not checked by BS | Not checked by B0 | Closes B1 | Closes B2 | Price up 100% or more in 5 minutes |
| young-pump | Not checked by BS | Not checked by B0 | Closes B1 | Closes B2 | Pool under 60 minutes old, 1-hour change of +50% or more and a burst of 0.35 or more |
| launch-run | Not checked by BS | Not checked by B0 | Closes B1 | Closes B2 | Young token already 3x above its pump curve start |
| band-10-25k | Not checked by BS | Not checked by B0 | Not checked by B1 | Required | Must be true for B2: market cap from $10,000 to under $25,000 |
| Grade | Rule | Meaning for you |
|---|---|---|
| A | B2 eligible | Passed every tier, inside the $10k to $25k band |
| B | B1 eligible, B2 not | Passed the B1 tier |
| C | Everything else, including safety pending | Not shown in Telegram at the default setting |
Which labels are recorded but never act?
Beyond the hard kills and the safety tiers, every decision records more than 30 named risk and data-quality labels, such as insider and bundler share, copycat names and late clusters. They are kept for transparency and auditing and do not change the decision.
Which delivery rules apply to signal cards?
| Rule | Value |
|---|---|
| Replay expiry | A signal older than 10 minutes at arrival is neither shown nor bought |
| LATE banner | Shown when the card is sent more than 30 s after the decision |
| Pacing | At most 8 signal cards per 10 minutes; the rest wait and none are dropped; cancels and alerts are not paced |
| Exit-alert cards | Only within 120 s, and at or above your grade filter |
| Launch-run suppression | No card of any kind for that token for 30 days |
Which guards apply to auto-buy?
BetaAuto-buy is an experimental, opt-in beta. These guards apply on top of your filters; see auto-buy (beta) for the design.
| Guard | Value |
|---|---|
| Mode gate | Off by default; live needs the strategy's PASS, then CONFIRM <ARM> <report_id> within 5 minutes; switches off if the PASS is withdrawn. A new install has no verdict yet: the earliest PASS can come after your own Engine has measured at least 150 go-live decisions over at least 4 days |
| Exit-policy match | The signal's exit-policy version must equal the bot's own, with no fallback |
| Stale entry price | Older than 5 seconds (the default): skipped; a higher value is accepted and logged as a deviation |
| One per token | At most one auto-buy per token, ever; a second signal or an open position is skipped |
| Caps | 3 per rolling hour, 20 per rolling 24 hours, SOL per day of 20 times the buy amount, 5 open signal positions and a 0.03 SOL reserve (code defaults); settings may change them; a value above a default is accepted and logged as a deviation; an invalid value blocks auto-buy |
| Price impact | Routes above 15% (the default) are refused before signing; AUTOBUY_MAX_IMPACT_PCT accepts up to 100% |
| Pauses | 3 failed buys in a row; the last 50 verified closed signal trades below the rolling threshold; 10 or more live buys with no successful sell for over 30 minutes |
| Unknown balance | A real auto-buy is skipped |
| Caps file unreadable | Auto-buy is held for 24 hours |
Which exit rules apply to my positions?
One exit engine watches every position the bot holds. Signal positions follow the default plan or your preset for their grade.
| Leg | Rule |
|---|---|
| Hard-rug exit | A sudden collapse between two closely spaced price checks triggers an immediate full sell |
| Rug stop | At 0.62x of entry while the peak is below 1.5x: sell all |
| Take-profits 1 to 3 | 2x sells 30%, 3x sells 30% and 5x sells 20% of the original position |
| Trailing stop | Armed at a 1.5x peak; exits at 60% of the peak |
| Maximum hold | 6 hours |
| Clean-up | The empty token account is closed after a full exit |
| Setting | Allowed range |
|---|---|
| Stop-loss | 1 to 95%; a "No stop" choice needs a one-time confirmation, valid for 5 minutes |
| Take-profits | Up to 3, with increasing triggers up to 100,000%; at most 100% of the original position sold in total |
| Trailing stop | Arms after 0 to 10,000%; trails 1 to 95% under the peak |
| Maximum hold | 1 to 168 hours, or none |
| Trigger types | Entry Price %, Price % or Market Cap %, all measured from entry |
| Always kept | The hard-rug exit |
| Other | Positions keep the plan they opened with; Apply to open positions; Reset; Clear All (the stop stays) |
Manual positions
Buys from /buy, a pasted address or a token card get a floor 25% below the first evaluated quote. A sudden collapse between two closely spaced price checks triggers an immediate full sell; for your own buys this is 40% between checks up to 60 s apart, sold at maximum slippage. Your own take-profit, stop-loss and trailing-stop orders sell 25, 50, 75 or 100% or a custom share, and stay active for 1 to 96 hours. A Buy tap on a signal card follows that signal's plan instead.
Exit safety and price sources
- Take-profits try 3 times: at the base slippage, at the midpoint, then at your max retry slippage.
- Protective exits use at least 40% slippage, then a 99% leg, 2 attempts, then a cool-down with re-checks from 90 s up to 30 minutes and an alert at most every 10 minutes.
- A landed-check comes before any retry, so nothing is sold twice.
- 5 failed sells in a row turn that token's take-profits off until restart; protective exits stay on.
- An alert fires if nothing could be sent for 2 minutes.
- Exits use the on-chain curve or pool price first, then a Jupiter quote, then the Engine's price only if it is at most 30 s old and only for protective exits; take-profits never fire on an Engine-only price. After 3 passes without a price, an "exits blind" alert goes out.
Which guards apply to manual trades?
| Guard | Value |
|---|---|
| Balance check | Native SOL must cover the amount plus 0.01 SOL, read within 5 s; if it cannot be read, the buy is refused and nothing is sent |
| Buy lock | One buy per wallet and token at a time (stale after 5 minutes); an unresolved earlier buy blocks a new one |
| Address | Must decode to 32 bytes |
| Amounts | SOL above 0; a sell percentage is a whole number from 1 to 100 |
| Buttons | Button data of at most 64 bytes; forged settings fields are refused |
| Orders | Active for 1 to 96 hours |
Frequently asked questions
What is the default lowest grade that reaches Telegram?
Grade B. By default only grade A and B signals are marked for Telegram. You can set the lowest card grade to A only, A and B, or all grades. The setting changes only the cards you see; an auto-buy you would not see still sends a one-line notice.
Why does a Min Score above 85 hide new tokens?
A token under 60 minutes old always scores 85, so any Min Score above 85 hides every signal on tokens younger than 60 minutes. Leave Min Score empty, or set it to 85 or less, to keep seeing them.
What happens when liquidity is unknown?
Unknown liquidity fails any liquidity bound you set, so the card is removed and no auto-buy is sent. On the Engine side, unknown effective liquidity also keeps every auto-buy safety tier closed.
Does the trading-session window stop signal cards?
No. The trading-session window limits only auto-buy. Signal cards arrive around the clock while your machine runs, and exits always run. A malformed start, stop or time zone, or a start equal to the stop, leaves the window open.
Can I change the auto-buy caps?
Yes. The caps are set in your own configuration. The code defaults are 3 buys per rolling hour, 20 per rolling 24 hours, a daily SOL cap of 20 times the buy amount, 5 open signal positions and a 0.03 SOL reserve. A value above a default is accepted and logged as a deviation, and an invalid value blocks auto-buy.
Which safety kills remove a token?
Eleven: honeypot, cannot sell, blacklist, mint authority not renounced, freeze authority not renounced, a sell tax of 10% or more, a Mayhem launch, a dev wallet over 25%, top-10 holders at 50% or more, wash trading and a market cap under $5,000. There is no K7, and an unknown value never kills.
Sources and review
- Product facts: the current PumpStriker Engine and Telegram bot code (settings, defaults, ranges and guards), checked in November 2026.
- Helius documentation: Priority Fee API
- Helius documentation: Sender
- Jupiter developer documentation
Last reviewed by Mezyan D, Bathyr Devs. Facts are as of November 2026 and follow the current build; release notes are on the changelog.
Risks and disclosures
- High risk: Memecoins are extremely high-risk and can move very fast in either direction. Only trade with money you can afford to put at risk.
- No guarantees: PumpStriker does not promise profit, a win rate or any trading result. A signal or grade is information, not a prediction, and no tool can make an outcome certain. Anything promising guaranteed returns is a scam.
- Experimental auto-buy: Auto-buy is an experimental, opt-in feature. It is off by default, starts in dry run, and live buys stay inside caps (by default 3 per hour, 20 per day, 5 open positions, a daily SOL cap, a 0.03 SOL reserve and a 15% price-impact cap). The caps are set in your own configuration; a value above the default is accepted and logged as a deviation. Turning it on is your decision.
- Your costs: You pay Solana network and priority fees, Helius Sender tips when Anti-MEV is on, venue fees, and any paid plan you choose with third-party services.
- Third parties and partners: PumpStriker relies on services run by others (GMGN, Helius, Jupiter, pump.fun, Telegram), and their uptime, fees and terms apply. UnclaimedSol is a partner: rent-recovery claims made through the in-bot button may earn Bathyr Devs a referral share.
- No token: There is no PumpStriker or BATHYR token, presale or airdrop. Anyone selling one is running a scam.
Not financial advice: PumpStriker is software, not financial advice. Nothing on this site is a recommendation to buy or sell any token. Do your own research (DYOR). Read the risk disclaimer and the terms of use.