FourMeme Trading Toolkit (BNB Chain)

A modular, CLI-driven trading toolkit tailored for the Four.meme ecosystem on BNB Chain. It includes specialized modules for sniping new launches, mirroring wallets, batching routes, and simulating/measuring volume — all powered directly on-chain with no third‑party market data services.

Modules at a glance

• Sniper: Rapid buys on fresh listings with tunable slippage and deadlines.
• Copy‑Trader: Mirror specific wallets with percentage sizing, per‑trade caps, and de‑duplication.
• Bundler: Execute predefined swap routes (e.g., WBNB → TOKEN) with timing controls; designed to extend toward multicalls.
• Volume Bot: Programmatic buy/sell loops at a set cadence for liquidity/organic activity testing.
• Notifications: Optional Telegram alerts for major lifecycle events.
• Risk Controls: Allow/deny lists, max spend ceilings, and basic MEV‑aware settings.

How it works

Sniper flow

• Load targets from config → query router for expected out → apply configured slippage → perform WBNB → TOKEN swap → emit tx hash/receipt → optionally notify via Telegram.

Copy‑Trader flow

• Subscribe to pending mempool transactions → filter by leader wallets → detect router swap intents → mirror with your position sizing and caps → optionally notify.

Bundler flow

• Read a sequence of routes from config → execute each respecting slippage/deadline settings → suitable base for multicall-style extensions.

Volume Bot flow

• Loop on an interval → small buys → approve when needed → partial or full sells → repeat with built‑in rate limiting.

Getting started

Prerequisites

• Node.js 18.17 or newer
• A BNB Chain RPC endpoint
• A funded wallet private key

Install dependencies

npm install

Environment setup

Copy env.example to .env and populate the required values. PancakeV2/WBNB mainnet defaults are provided. To enable Telegram notifications (optional), add:

TELEGRAM_BOT_TOKEN=123:ABC
TELEGRAM_CHAT_ID=123456789

Sample configurations

You can start from the provided examples and tailor them to your needs:

• config.sniper.example.json
• config.copy.example.json
• config.bundle.example.json
• config.volume.example.json

Build and run

npm run build
# Sniper (dry-run recommended first)
node dist/index.js sniper -c config.sniper.example.json --dry-run

# Copy-trader
node dist/index.js copy -c config.copy.example.json

# Bundler
node dist/index.js bundle -c config.bundle.example.json

# Volume bot
node dist/index.js volume -c config.volume.example.json

Tip: All commands accept standard Node/CLI flags and module‑specific options (see inline --help).

Configuration and safety tips

• Start in dry‑run mode; scale notional size gradually.
• Maintain deny lists and confirm token/router addresses before enabling live trades.
• For fast markets, sniper slippage of 3–8% (300–800 bips) is common; test first.
• For copy‑trading, set both per‑trade caps and a daily max exposure.

Support

• Telegram: Dexoryn

Security best practices

• Never commit secrets or private keys.
• Use a dedicated hot wallet for experimentation.
• Double‑check token and router contract addresses.
• Prefer dry‑run first, then small sizes in production.