How to Search for New Coins on Binance Efficiently

3. Regex pattern r'[A-Z]{3,5}\s+Launches\s+on\s+Binance' filters raw text, isolating candidate ticker strings before and after the word “Launches”.

4. Candidate tickers undergo cross-validation against CoinGecko’s list of verified tokens to eliminate false positives from typographical errors or placeholder names.

5. Validated tickers are pushed to a Redis queue with TTL set to 300 seconds, ensuring downstream services consume only fresh signals.

Community Signal Aggregation Layer

1. X (Twitter) feeds are scraped using official Academic API v2, filtering for accounts verified by Binance’s official handle @binance and posts containing hashtags #BinanceListing or #NewCoin.

2. Discord webhook payloads from official project servers are ingested via dedicated gateway endpoints, extracting message content where embed title matches regex r'✅\s+Live\s+on\s+Binance'.

3. Reddit posts from r/binance are scanned using PRAW, prioritizing submissions with >50 upvotes and domain “binance.com” in the URL, then extracting ticker symbols from post body markdown links.

4. All community-derived tickers are weighted by source credibility score: official account = 10, verified project team = 7, top-1000 crypto influencer = 4, unverified user = 1.

5. Aggregate scores above threshold 12 trigger immediate notification via Telegram bot, including direct link to original source and timestamp delta from first detection.

Pre-Launch Token Verification Pipeline

1. Smart contract address is retrieved from official announcement or verified GitHub repository README, then submitted to Etherscan’s contract verification API.

2. Bytecode hash is computed and matched against Binance’s internal whitelist of audited contracts, rejecting any mismatch.

3. Liquidity pool data is pulled from PancakeSwap V2 router on BSC using multicall, calculating total value locked and verifying minimum $2M USD equivalent across two stablecoin pairs.

4. Holder distribution is analyzed via Nansen API, flagging tokens where top 10 addresses hold >45% of supply or show abnormal transfer clustering within last 72 hours.

5. Transaction history is scanned for suspicious patterns: repeated zero-value transfers, self-transfers exceeding 100 per hour, or rapid mint-burn cycles detected via ERC-20 event logs.

Execution Trigger Configuration

1. Three-tier confirmation logic applies: Level 1 requires API detection only, Level 2 adds announcement scrape match, Level 3 mandates community signal + contract verification.

2. Order parameters are preloaded from JSON config file stored in encrypted S3 bucket, including maximum slippage (0.8%), position size (0.3% of portfolio), and take-profit ratio (2.4x).

3. Stop-loss is dynamically calculated using 5-minute VWAP deviation, recalculated every 30 seconds during order placement phase.

4. All orders execute via Binance’s margin-enabled spot API with request signature validated through HMAC-SHA256 using stored API keys.

5. Post-execution validation checks order status via /api/v3/order endpoint within 200ms, retrying failed confirmations up to three times with exponential backoff.

Frequently Asked Questions

Q: Does the bot support Binance.US endpoints?A: No. It exclusively targets Binance.com API domains and ignores all geoblocked or jurisdiction-specific endpoints.

Q: Can I manually override auto-detected symbols?A: Yes. A dedicated CLI command binance-bot --override BTC --priority high injects custom symbols into the detection queue with elevated weight.

Q: How often does the Redis queue flush expired entries?A: Every 300 seconds, enforced by Redis EXPIRE command issued at insertion time—no background cron job involved.

Q: Is contract bytecode verification performed on-chain or off-chain?A: Off-chain. The bot computes SHA-256 hash of deployed bytecode retrieved from Etherscan and compares it against precomputed hashes stored in AWS Secrets Manager.