Sniper Bot for Token Launches
Imagine: a new coin launches on Uniswap, liquidity is added, but you find out 10 seconds later — the price has already shot up 3x. A sniper bot solves this. The difference between entering on block N and block N+3 can mean 5x vs 1.2x. We build sniper bot infrastructure for guaranteed early entry: mempool monitoring, listing event detection, and transaction submission with the right gas price within milliseconds. Over the last few years, we've delivered 30+ such projects across different networks. A manual entry mistake can cost $5,000 in one minute — automatic honeypot and tax detection saves that amount. Proper mempool and gas strategy configuration lets you outpace competitors by 2-3 blocks.
Where Money Is Lost Without a Proper Bot
A naive approach — listen to the PairCreated event from the Uniswap factory and send a swap. Problem: by the time the event lands in a block, 2-5 seconds have passed. Competitors read the mempool directly and see the addLiquidity transaction before it's included in a block.
Another common pitfall — tax tokens. A contract with _transfer override withholds 10-30% on purchase but is invisible via the standard ABI. Honeypot tokens block selling — sell reverts. Honeypot detection automatically cancels such trades, saving thousands of dollars per trade.
Why Mempool Monitoring Is Critical
Connecting directly to a node via WebSocket (eth_subscribe("newPendingTransactions")) gives pending transactions before they are included in a block. For EVM networks we use private RPC with mempool access (Chainstack, Alchemy). On Solana — logsSubscribe with a filter by Raydium or Orca program ID. A private node is 5x faster than a public one: 0.3-1 second latency vs 2-5 seconds.
How Simulation Works Before Purchase
Before sending the real transaction — simulation via eth_call or tenderly_simulateTransaction. We check:
- Actual token count after transfer (detect tax)
- Sell possibility (does sell revert)
- Presence of blacklist/whitelist functions
async function simulateBuy(tokenAddress: string, amountIn: bigint): Promise<SimResult> { const balanceBefore = await getTokenBalance(tokenAddress, botAddress); let expectedOutput = await getAmountOut(amountIn, tokenAddress); await provider.send('eth_call', [{ from: botAddress, to: ROUTER_ADDRESS, data: encodeSwapExact(WETH, tokenAddress, amountIn) }, 'pending']); const balanceAfter = await getTokenBalance(tokenAddress, botAddress); const received = balanceAfter - balanceBefore; const taxRate = 1 - Number(received) / Number(expectedOutput); return { received, taxRate, isSafe: taxRate < 0.05 }; } Gas Strategy
For EIP-1559 networks (Ethereum, Polygon): maxPriorityFeePerGas set to 2-3x current baseFee + aggressiveTip. For BSC (legacy gas): monitor current gasPrice of competitors and set 10-20% higher. Anti-grief protection: gas limit per operation, not unlimited.
Node Type Comparison
| Parameter | Public Node | Private Node (Alchemy/QN) |
|---|---|---|
| Mempool latency | 2-5 seconds | 0.3-1 second |
| Access to pending txs | Limited | Full |
| Reliability | Medium | High (SLA) |
| Cost | Low | Higher but pays off |
Second comparison: manual entry vs bot.
| Characteristic | Manual Entry | Sniper Bot |
|---|---|---|
| Reaction time | 3-10 seconds | 0.5-1 second |
| Tax token detection | No | Simulation + auto-cancel |
| Honeypot protection | No | Sell check before purchase |
| Gas optimization | Manual setting | Automatic calculation based on mempool |
What's Included in the Work
- Analysis: network selection, DEX, risk parameters.
- Design: bot architecture, configs, simulator.
- Implementation: core logic in TypeScript + viem, node integration.
- Testing: fork tests on Tenderly, listing simulations.
- Deployment: to your server or cloud (AWS, Hetzner).
- Documentation: README, config description, run examples.
- Support: 1 month of consultations after delivery.
Development is turnkey: you get a ready bot with instructions. Order sniper bot development and get a ready solution in 3-14 days. Contact us for an individual quote.
Tech Stack and Architecture
- TypeScript + viem — core bot logic
- ethers.js — fallback for provider quirks
- WebSocket to private node — mempool subscription
- Redis — cache for already-seen transactions, anti-double-buy
- PostgreSQL — log of all operations, P&L
Configuration via .env: RPC endpoint, private key in HSM or KMS, risk parameters (max buy amount, max tax tolerance, stop-loss). Detailed documentation included.
Example Configuration
# .env RPC_URL=https://eth-mainnet.g.alchemy.com/v2/your_key WS_URL=wss://eth-mainnet.g.alchemy.com/v2/your_key PRIVATE_KEY=your_private_key MAX_BUY_AMOUNT=2 ETH MAX_TAX_TOLERANCE=0.05 STOP_LOSS=0.8 Typical Mistakes in Sniper Bot Development
- Using public RPCs: 2-5 second delay kills the advantage.
- No simulation before purchase: buying a token with 30% tax and no sell possibility.
- Fixed gas price under network congestion: transaction gets stuck.
- Ignoring contract pause: bot buys a token that is frozen.
- No logging and monitoring: impossible to debug loss of funds.
Timeline Estimates
Basic sniper for one DEX and one network — 3-5 days. Multi-chain version with honeypot detector and tax simulator — 1-2 weeks. Cost is calculated individually. If you want to discuss the project or order development, contact us. Get a consultation on sniper bot setup right now.