SolSniper guide

What it does

SolSniper runs on your server around the clock. It watches for brand-new Solana tokens, checks each one for safety and liquidity, and sends the ones that pass to your Telegram for approval. After you tap Buy, it manages the exit automatically.

Setup checklist

The bot is already installed at ~/projects/solsniper with everything it needs. You only have to do this:

• Create your Telegram bot and put its token and your chat ID in .env (about 5 minutes)
• Optional but recommended: add a free Solana RPC URL and Jupiter API key
• Run a test check to confirm it works
• Install it as a service so it runs 24/7 and restarts itself
• Paper trade for at least a week or two, then decide about going live

All commands below are run in a terminal on the server. Start every session with:

cd ~/projects/solsniper

Step 1 · Set up the Telegram bot

Telegram is how the bot asks permission to buy and tells you what it's doing. You create your own private bot (free, takes a couple of minutes). It will only ever listen to your chat; messages from anyone else are ignored.

cd ~/projects/solsniper
cp .env.example .env
chmod 600 .env
nano .env

TELEGRAM_BOT_TOKEN=7412345678:AAH3k...xyz

.venv/bin/python -m solsniper tg-chatid

TELEGRAM_CHAT_ID=123456789

status - Mode, balance, PnL, open positions
positions - Open positions with live multiples
pending - Tokens waiting for approval
recent - Last 10 evaluated tokens
pnl - Profit and loss summary
pause - Stop new buys
resume - Resume new buys
sell - Sell a position: /sell ID PCT
check - Safety-check a token: /check MINT
get - Show a setting: /get KEY
set - Change a setting: /set KEY VALUE
unset - Remove an override: /unset KEY
help - All commands

Step 2 · Optional API keys (recommended)

The bot works without these, but both are free and make it faster and more reliable. Add them to the same .env file.

SOLANA_RPC_URL=https://mainnet.helius-rpc.com/?api-key=YOUR-KEY
JUPITER_API_KEY=your-jupiter-key

Changes to .env only take effect after a restart: sudo systemctl restart solsniper.

Step 3 · Test it

Run the safety checks on any Solana token to confirm everything is connected. Copy a token address from dexscreener.com/solana and run:

.venv/bin/python -m solsniper check PASTE_TOKEN_ADDRESS_HERE

You'll get a full report: liquidity, market cap, holders, LP lock, RugCheck score, buy/sell activity, and a verdict (PASS, SOFT FAIL, FAIL or NOT READY) with the reasons.

To see the Telegram side working, start the bot in the foreground for a minute:

.venv/bin/python -m solsniper run

Within a few seconds you should get "🚀 solsniper started — mode PAPER, approval manual" in Telegram. Send /status to it. Press Ctrl+C in the terminal to stop.

Step 4 · Run it 24/7

Install it as a system service. It then starts on boot and restarts itself within 10 seconds if it ever crashes.

sudo cp deploy/solsniper.service /etc/systemd/system/
sudo systemctl daemon-reload
sudo systemctl enable --now solsniper

Everyday service commands

Using it day to day

1 · You get a candidate alert

When a token passes every check, you get a message like this:

Tap the DexScreener link to see the chart before deciding. Then:

• ✅ Buy 0.1 SOL buys your normal size. Buy 0.2 buys double and Buy 0.05 buys half.
• ❌ Skip ignores it. Doing nothing does the same: it expires after 3 minutes.
• Want a custom size? Type /approve 42 0.3 to buy 0.3 SOL of candidate #42.

2 · You get a buy confirmation

Note the position number (#7). Those Sell buttons work at any time. From now on the bot checks the price every 10 seconds and sells by your exit rules.

3 · You get sell notices

💰 = partial sell (position still open). 🏁 = position closed with final profit/loss.

Other messages you may see

Telegram commands

IDs can be typed with or without #: /sell #7 and /sell 7 are the same.

Changing settings

You can change any setting two ways. Neither needs a restart.

Budget & risk

Exits

Example /set commands

/set budget.buy_amount_sol 0.05
/set budget.max_open_positions 3
/set budget.daily_loss_limit_sol 0.2
/set exits.stop_loss_pct -25
/set exits.stop_loss_after_initial_recovered 1.0
/set exits.trailing_stop {activate_at: 2, drawdown_pct: 25}
/set exits.max_hold_minutes 120
/set exits.take_profit [{at: 1.5, sell_pct: 30}, {at: 2, sell: initial}, {at: 5, sell_pct: 100}]
/set filters.min_liquidity_usd 30000
/set filters.max_pair_age_min null
/set sources.dexscreener_boosts true
/set approval_timeout_sec 300

Lists and groups use the format shown above: square brackets for a list, curly braces for a group. null turns a check or rule off.

How selling works

Every 10 seconds the bot asks Jupiter, "if I sold my whole remaining position right now, how much SOL would I get?" It compares that to what those tokens cost you. That ratio is the multiple: 1.0x = break-even, 2.0x = doubled, 0.65x = down 35%. Price impact is included, so the multiple is what you'd really get.

The rules, in priority order

1. Stop loss: multiple at or below 0.65x (−35%), sell 100%.
2. Trailing stop: once the peak has reached 1.8x, if the price drops 30% from that peak, sell 100%.
3. Max hold: after 6 hours, sell 100%.
4. Take-profit ladder: each step fires once, lowest first.

The take-profit ladder

Each step is either:

• {at: 4, sell_pct: 50}: at 4x, sell 50% of what you still hold.
• {at: 2, sell: initial}: at 2x, sell exactly enough to get your original SOL back. The rest is a "free ride".

Worked example with the defaults (0.1 SOL buy)

If instead it dumps straight after you buy, the stop loss sells everything around −35% (≈0.065 SOL back). In a fast crash the actual fill can be worse.

Safety checks

A token must pass every enabled check before you see it. Hard failures reject a token permanently. Soft failures (things that can improve, like volume) are re-checked every 2 minutes, up to 3 times. Type /recent to see why tokens are being rejected.

Getting too few alerts? Loosen the market filters first (e.g. /set filters.min_holders 80, /set filters.min_liquidity_usd 10000). Getting junk? Tighten them. Leave the contract checks (authorities, extensions, LP lock, round-trip) on.

Going live (real money)

cd ~/projects/solsniper
.venv/bin/python -m solsniper keygen

SOLSNIPER_KEYPAIR=/home/mattbox/projects/solsniper/secrets/bot-wallet.json

sudo systemctl restart solsniper

/set mode live confirm

/set approval auto

Withdrawing profits

The bot wallet is a normal Solana wallet. To move SOL out, import secrets/bot-wallet.json into a wallet app (Phantom and Solflare can import a private key), or ask your assistant for a one-off withdraw command. Send /pause first and wait until no sells are in progress.

Shell commands

Everything you can do in Telegram also works from the server terminal, which is handy if Telegram is down. Run them from ~/projects/solsniper:

.venv/bin/python -m solsniper status
.venv/bin/python -m solsniper positions
.venv/bin/python -m solsniper pending
.venv/bin/python -m solsniper approve 42 0.1
.venv/bin/python -m solsniper skip 42
.venv/bin/python -m solsniper sell 7 50
.venv/bin/python -m solsniper pause
.venv/bin/python -m solsniper resume
.venv/bin/python -m solsniper recent
.venv/bin/python -m solsniper pnl
.venv/bin/python -m solsniper check TOKEN_ADDRESS
.venv/bin/python -m solsniper get exits.take_profit
.venv/bin/python -m solsniper set budget.buy_amount_sol 0.05
.venv/bin/python -m solsniper unset budget.buy_amount_sol

approve, skip, sell, pause and resume are passed to the running bot, so the service must be running.

alias sniper='cd ~/projects/solsniper && .venv/bin/python -m solsniper'

Troubleshooting

sudo systemctl stop solsniper
mv data/solsniper.db data/solsniper-old.db
sudo systemctl start solsniper

Files & backups