Swap / DEX·Ethereum · Solana · BSC · Base · MegaETH · Sonic · Unichain
Banana Gun
Multi-chain Telegram trading bot with a companion Pro web terminal. One Telegram session covers Ethereum, Solana, BNB Chain, Base, and MegaETH (with Sonic and Unichain accessible) for manual buys, autosniping, DCA, and copy trading.
- 01Telegram-native trading across EVM + Solana
- 02Ethereum first-block sniping
- 03multi-chain DCA / copy trading
- 04pre-trade simulation against honeypots
- 05stablecoin swaps with zero protocol fee
Banana Gun is a consumer Telegram bot (`@BananaGunSniper_bot` and friends) plus a Pro web terminal — there is no general-purpose public REST/SDK. Integrate by deep-linking into the bot with a referral code (`https://t.me/BananaGunSniper_bot?start=ref_{code}`) or to a token's Banana Pro trading page. Mirror its model in your own product with: a non-custodial multi-chain hot wallet, pre-trade simulation that catches honeypots, autosnipers per chain, and per-chain fee logic (≈0.5% manual on ETH, ≈1% on autosnipes and other chains, 0% on stable swaps). For programmatic equivalents, compose 0x/1inch (EVM aggregation), Jupiter (Solana routing), and Flashbots/MEV-Share for private bundles on Ethereum.
- ⚑Telegram-bound wallets are hot wallets — Banana Gun has historically been exploited (the 2024 incident refunded ~$3M); keep balances small and rotate keys.
- ⚑First-block Ethereum snipes require private bundles + priority bribes; without those, public-mempool snipes lose to MEV searchers regardless of UI speed.
- ⚑Slippage and MEV exposure differ per chain — Solana relies on Jito tips, EVM on private mempools, BNB/Base on chain-specific MEV protections; never reuse the same 'safe slippage' across chains.
- ⚑Per-chain fee schedule is non-trivial (0.5% ETH manual, 1% autosnipe and non-ETH, 0% stable swaps) and stacks with chain gas/MEV tips; surface effective round-trip cost per trade to users.
- ⚑Phishing clones impersonate Banana Gun under near-identical handles and look-alike domains; verify the official handles via `bananagun.io` and warn users in onboarding.
- ⚑Telegram chat history is not E2E-encrypted by default and contains balances, addresses, and signed-tx hashes — treat the bot session itself as sensitive.
- ⚑Geographic restrictions and KYC-style limits can apply on certain features; some jurisdictions are blocked at signup.