Telegram Bot for Token Sniping Development

Developing Telegram Bot for Token Sniping

New token added to liquidity pool on Uniswap v2—addLiquidityETH transaction lands in mempool. You have 1-2 blocks, max 3, to buy before price flies. Manual monitoring excluded: human can't keep up. Need bot that listens mempool, decodes pending txs, sends buy-tx with proper gasPrice within 50-200 milliseconds of discovery.

This isn't "buy cheaper"—this is buy before others realize token exists.

Where Everything Breaks in Typical Implementations

Latency—Main Problem

Most open-source snipers written with ethers.js via standard WebSocket to public node (Infura, Alchemy). Delay between network event and Infura notification—300-800 ms. By then co-located MEV-bots executed 2-3 transactions.

Real sniper architecture requires:

• Own node (go-ethereum or Erigon) with direct WebSocket to localhost—latency drops to 20-50 ms
• Subscribe to newPendingTransactions instead of logs—catch tx before block inclusion
• Decode pending tx input data via Uniswap Router ABI: find addLiquidityETH and addLiquidity with right signatures

Without own node or private mempool connection (Flashbots, bloXroute), competing with professional MEV-bots nearly impossible.

Honeypot Tokens and Rug Pulls

Of 100 new tokens daily on BSC or Ethereum, ~60-70 outright scam. Contract may:

• Forbid transfer for any address except owner (classic honeypot: buy possible, sell—no)
• Set 99% tax on sale via custom _transfer logic
• Add blacklist after sniping

Without simulating buy and sell before execution, bot regularly loses money on honeypot contracts. We use eth_call simulation of two sequential txs: swap ETH→Token immediately Token→ETH. If sell simulation reverts or returns <50% of input—skip token.

Additional check: static bytecode analysis of token contract for functions with signatures typical for blacklist/whitelist patterns, check via HoneyPot.is API.

Front-Running from Pool Itself

With small initial liquidity and high initial gasPrice, MEV-bot may wedge before our tx via sandwich. Especially on Ethereum mainnet. Solution—Flashbots bundle: send tx directly to validator, bypassing public mempool, execute in exact bundle order.

Flashbots unavailable on BSC, but bloXroute BDN offers transaction priority delivery.

How We Build Bot

Architecture

Node (Erigon/geth) → WebSocket mempool listener
       ↓
  Tx decoder (ABI parse → filter by router address)
       ↓
  Token analyzer (simulate buy/sell, bytecode analysis)
       ↓
  Risk engine (max buy amount, slippage config)
       ↓
  Executor (Flashbots bundle / direct tx)
       ↓
  Telegram notification + position tracker

Main logic written in Node.js with viem for low-level node interaction. Viem faster than ethers.js on latency due to finer JSON-RPC batching control. Critical parts—monitoring and decoding—run in separate Worker Thread to not block event loop.

Bot config via Telegram: slippage, max buy amount, whitelist/blacklist router contracts, minimum initial liquidity threshold in ETH/BNB. All changes on the fly without restart.

Supported Chains and DEXs

On Solana, architecture fundamentally different: use gRPC-stream Yellowstone from Triton, subscribing to account updates of Raydium AMM program. Gives 10-30 ms latency to new pool initialization.

Gas Management

On Ethereum mainnet, tactics depend on mode: if using public mempool—set gasPrice to 150-200% of current baseFee + priorityFee. If Flashbots bundle—optimize bribe (validator tip) so bundle includes next block, without overpay.

Automatic adaptation to current network load via eth_gasPrice + analysis of last 5 blocks via eth_feeHistory.

Development and Setup Process

Analytics (1-2 days). Determine target chains, DEXs, strategy (pure liquidity-add sniping, listing-event sniping, presale sniping). Different strategies—different mempool entry points.

Development (5-10 days). Monitoring, decoder, token analyzer, executor. Parallel—Telegram Bot API integration for control and notifications.

Testnet Testing (2-3 days). Deploy custom Uniswap v2 to Sepolia, simulate liquidity add, test full path. Test honeypot scenarios with contracts where sale blocked.

Node Deployment and Setup. Help with hosting selection (proximity to validators critical), Erigon/geth configuration, firewall, monitoring via Prometheus + Grafana.

What Affects Timelines

Basic bot for single chain and single DEX—1-1.5 weeks. Multi-chain with Flashbots integration, Solana via Yellowstone, extended anti-honeypot analysis—2-3 weeks. Timelines also depend on client infrastructure: own node availability, UI management requirements.

Cost calculated after discussing stack and target chains.