Telegram Trading Bot Withdrawal Problems
A step-by-step check for a Telegram crypto trading bot withdrawal that fails: confirm the bot, read the transaction, spot the advance-fee pattern, and know when to revoke access.
Published 2026-11-12
What "withdrawal not working" can mean
Four different problems get described the same way:
- The bot ignores the withdraw command. No reply, no error, nothing.
- The bot replies, the transaction is broadcast, and it fails on-chain.
- The transaction succeeds, but the funds do not land where you expected.
- The bot, or an account claiming to be support, says you must send more money before the withdrawal is released.
Each has a different cause and a different next step. Working out which one you are looking at is the first job, because a thin-liquidity problem and a demand for a new deposit lead in opposite directions.
A number in the chat is not a balance in your wallet
The distinction that matters most: a figure shown inside the bot chat is an entry in the bot's own ledger. A balance in a wallet you control with your own seed phrase sits on-chain and moves only when you sign.
When a bot holds your key, it can move, hold or refuse to move funds in its ledger. Whether that ledger entry turns into coins in a wallet you control depends on the bot releasing them. Keeping the two balances separate tells you where to look when something stalls.
Three failure types side by side
| What you see | Where the problem usually is | First thing to check |
|---|---|---|
| Bot never answers the withdraw command | Telegram session, bot availability, wrong chat | That you are in the official bot chat and the bot is responding to any command |
| Transaction broadcast and failed | Network fee, token rules, liquidity | The transaction in a block explorer for the right chain |
| Transaction confirmed, nothing arrived | Wrong chain, wrong token, wrong destination | The address and token you withdrew to |
Most failed withdrawals are network or token problems: no native coin to pay the fee, a token that restricts transfers, liquidity too thin for the exit. A few are not, and a request for a further deposit before release is the one to recognise early.
The checks that follow run in the order you meet them: confirm the chat is genuine, establish where the balance actually sits, read the transaction, then handle the cases where funds are being held back.
Check you are talking to the real bot first
Before you debug a withdrawal, confirm the chat you are in belongs to the bot you think it does. Impersonator bots copy branding, copy the welcome message and copy the fee table. The only thing they cannot copy is the handle.
Open the bot's own website in a browser and copy the handle from there. Do not use a handle from a pinned message, a forwarded link, a YouTube comment or a direct message. Those are the places impersonators put their links.
Handle to bot, as listed on each bot's own site
| Bot | Official Telegram handle |
|---|---|
| Banana Gun | @BananaGun_bot |
| BONKbot | @bonkbot_bot |
| Trojan | @solana_trojanbot |
| Maestro | @maestro |
| Bloom | @BloomSolana_bot |
| GMGN | @GMGN_sol_bot |
| Sigma | @Sigma_buyBot |
| Unibot | @unibotsniper_bot |
| Pepeboost | @pepeboost_sol_bot |
Compare character by character. Lookalike handles swap a lowercase L for a capital I, add a word like "official" or "support", or append an underscore. A difference of one character is the whole attack.
The fake support pattern
A "support" account that messages you first is not support. Real teams answer in a public channel or through a form on their own site, and they contact you only after you ask. Treat any unprompted DM that offers to "fix" a stuck withdrawal as hostile, especially if it asks you to connect a wallet to a link, install something, or share a seed phrase.
Subscriber counts prove nothing. The official Telegram news channel at https://telegram.me/telegram lists 9,170,375 subscribers, and anyone can buy members or clone a channel's appearance. A big number next to a name is not verification.
If the handle does not match the bot's own website, stop. Send nothing, sign nothing, and leave the chat.
Where your balance actually sits: bot wallet or your wallet
The word "withdraw" hides two very different setups. Which one you are in decides what you can do when the bot stops responding.
Setup one: an imported wallet
You paste or import your private key into the bot, and it trades directly from that wallet. Your funds and tokens stay on-chain at your address the whole time. The bot is only a signer that acts for you.
The practical test: search your address in a block explorer for the chain the bot trades on. Your tokens show up there, with or without the bot's cooperation. Anyone holding the key can move those funds through any wallet app.
The trade-off is real: a bot that holds your private key can lose your funds. That is the price of this setup, and it is why the key you import should belong to a wallet you keep lightly funded, not your main holdings.
Setup two: a bot-managed ledger balance
You send funds to an address the bot gives you, and the bot credits a number to your account in its own chat. That number is a record the bot keeps. Until the bot sends an on-chain transaction, nothing has moved. Nothing sits at an address you control.
A ledger balance is a promise recorded in someone else's system. If the bot is slow, offline or unresponsive, the balance is only as good as the operator behind it.
Telling them apart
| What you see | What it usually means |
|---|---|
| A deposit address, then a balance in the chat | Ledger balance |
| A private key or seed phrase import step | Imported wallet |
| Your tokens visible at your own address in a block explorer | Imported wallet |
| No address of yours holds the tokens | Ledger balance |
Why this matters for a stuck withdrawal
In an imported wallet, you can move funds without the bot: import the same key into a wallet app and send from there. No permission needed.
With a ledger balance, you depend on the bot sending a transaction. Your options are limited to getting the bot working, reaching its official support, or waiting.
So before you send another withdraw command, work out which setup you are in, and check the address your tokens actually sit at.
Read the transaction before you blame the bot
When a bot reports a withdrawal, it usually posts a transaction link or a signature/hash in the chat. Copy it. If there is no link, paste your wallet address into a block explorer for the chain the bot trades on and read the most recent transactions from that address.
The explorer is the only neutral record of what happened. It does not care what the chat says, and it cannot be edited by the bot. Read it before you send another command.
The three failure types side by side
| What you see | What it means | Where the problem is |
|---|---|---|
| No transaction in the explorer, and the bot never answered the withdraw command | Nothing was broadcast | The bot, the command or the chat |
| A transaction that is pending | Broadcast and waiting for inclusion | Network conditions, fee paid |
| A transaction that is failed | Included in a block and reverted | The transfer itself, often token or liquidity side |
| A transaction that succeeded, but the funds are not where you expected | The transfer happened as written | The recipient, token or amount in the transaction |
How to read each result
Pending means the transaction was broadcast and is waiting to be included. It can still land, or it can drop out. Do not resubmit it and assume the first one vanished.
Failed means the transaction reached a block and reverted. The network fee is still spent, because the chain processed the attempt. A failed transaction is evidence the bot tried to send something; it is not evidence that it took the funds. Read the failure note in the explorer for the reason the transfer reverted.
Nothing at all means no transaction was sent. Nothing was broadcast from your address, so the fault sits upstream: the bot did not process the command, or it processed it and stopped.
When the transaction succeeded
Open the recipient address inside the transaction and check three things against what you asked for: the token, the amount and the destination address. A confirmed transfer of the wrong token, or to an address you do not recognise, is a different problem from a transfer that never happened, and it needs a different response.
Always use the explorer for the chain the bot actually trades on. A Solana signature will not appear on an Ethereum explorer, and an empty result there tells you nothing.
Wrong chain, wrong token, wrong network
Many withdrawals that look like bot bugs are chain mismatches. The bot traded on one network, and the withdrawal was checked, sent or funded on another. Three versions cover most cases.
The common mismatches
- A Solana withdrawal looked up in an Ethereum explorer. Nothing appears there, because the transaction, if it exists, lives on Solana.
- A token sent on one chain to an address you use on another. The wallet may support both networks, but the asset arrives only on the chain it was sent on.
- A deposit made on a network the bot does not support. Check the bot's own page first: BONKbot lists Solana only (BONKbot), while Bloom lists Solana, Ethereum, BNB Chain and Base.
The native token problem
Every transfer needs a small network fee paid in the chain's native coin: SOL on Solana, ETH on Ethereum and Base, BNB on BNB Chain. A wallet holding only the token you want to withdraw cannot pay that fee, so the withdrawal never gets broadcast at all. The bot may report a failure with no transaction hash, which looks like the bot is refusing to send.
Keep a small amount of the native coin in whichever wallet pays the fee, the sending one or the receiving one, depending on how the bot structures the transfer.
Identical tokens, different contracts
Two tokens with the same ticker and logo can exist at different contract addresses on different chains. If the wrong one is sent, the bot cannot recover it. The transfer is valid on the chain where it was made, and the receiving side has no obligation to return it. Confirm the contract address and the chain in the bot's own documentation before you send.
Check in this order
- Chain: the one the bot trades on, confirmed on its page or on /chain/solana, /chain/ethereum or /chain/base.
- Token contract: the exact address, on the correct network.
- Fee balance: enough native coin to broadcast.
- Destination address: on the same network as the token.
When the swap leg of the withdrawal is what fails
On most Solana and EVM bots a withdrawal of a token position is really two steps: the bot sells your token for the chain's native coin (SOL, ETH), then sends that coin to your wallet. The send is usually the simple part. When a withdrawal stalls, the swap is often what broke, even though the message you see just says the withdrawal failed.
Reasons a sell or transfer fails on the token side
- Transfer restrictions or taxes. The token contract can limit who may transfer it, charge a tax on sells, or block selling entirely for wallets it flags.
- Trading paused. The contract owner can switch trading off, or pause it for one direction only.
- Thin liquidity. There may be no pool deep enough to absorb your size at any reasonable price.
- Slippage set too low. A route exists, but the price moves beyond your tolerance before the swap lands, so the transaction reverts.
Thin liquidity gets worse when everyone exits at once
A pool that absorbed your exit yesterday can fail today on identical settings, because other holders sold into it first. On a token in freefall, liquidity leaves faster than the price does.
Read the error, do not guess
The error text names the failure. Each one points somewhere different.
| Error text | What it usually means | What to check |
|---|---|---|
| Slippage exceeded / too much slippage | Price moved past your limit during the swap | Whether the pool is deep enough for your size |
| Route not found / no route | No pool the bot can trade through | The token's pairs and liquidity |
| Insufficient liquidity | Pool too shallow for the amount | Your size against the pool |
| Transfer restricted / blacklisted | Contract blocks the transfer | The token's own contract rules |
Some tokens cannot be sold by design, and no bot setting changes that.
Raising slippage blindly is not a fix. On a restricted token a 50% tolerance still fails, and when a swap does go through at that tolerance you can receive far less than expected.
If the token cannot be sold, that is a token problem, not necessarily a bot problem.
Telegram-side problems: blocked bot, deleted chat, logged-out session
If the bot never answers at all, the fault may be in Telegram rather than in the bot or the chain. Four messenger-side causes cover most silent withdrawals.
A blocked bot looks like a silent bot
A blocked bot still accepts your messages: the command appears to send, with a single tick, and nothing comes back. No error, no menu, no confirmation. If you blocked the bot at some point, for example to stop notifications, open its profile, tap Unblock, then send /start and try the withdrawal command again.
Clearing the chat does not delete your balance
Deleting the conversation only removes messages from your device. A balance held in the bot's ledger is unaffected by clearing history, so a wiped chat is not a lost withdrawal. Archived chats are different: they still receive messages, but without a notification, so a confirmation can sit unread for hours. Search the bot's name in Telegram to find it, and check the Archived Chats folder before assuming nothing was sent.
Sessions ended on another device
A session closed elsewhere logs you out, sometimes in the middle of a withdrawal, and commands sent from a logged-out session never reach the bot. In Telegram, open Settings, then Devices, and check the active sessions list. End anything you do not recognise, then log back in and resend the command. Keep the same account: a withdrawal started from one Telegram account cannot be completed from another.
Busy bot during volatile markets
When the market moves, a bot with many users can respond slowly or drop commands from its queue. Wait a few minutes, then check whether the earlier command actually executed before sending it again.
Public groups are not a support channel
Telegram groups can hold up to 200,000 members (telegram.org), so a question posted in a busy group is rarely read by anyone official, and scammers watch those groups for exactly that message. A direct message from an account calling itself support, arriving just after you post, is a common approach pattern. Official support does not need your seed phrase.
If the bot wants a new deposit before it releases your funds
The withdrawal stalls. Then a message arrives, from the bot chat or from an account calling itself support. It says the funds can be released after one more step: a deposit to "verify" the wallet, an unlock fee, a gas top-up sent to an address they provide, or a payment to a verification service.
A legitimate withdrawal never requires a new deposit, an unlock fee, or your seed phrase. If the balance shown in the chat can only leave after more money goes in, that balance is an entry in the bot's ledger, not funds waiting in a wallet you control.
A real network fee versus a payment to someone
| Request | Where the money goes | Normal? |
|---|---|---|
| Gas to send the transaction | Paid to the chain from your own wallet | Yes |
| "Unlock" or "release" fee | Sent to an address given to you in chat | No |
| Deposit to "verify" or "activate" the account | Sent to the bot or a support account | No |
| Seed phrase or private key "for verification" | Handed to a person | Never |
A genuine fee is paid to the network, by you, from a wallet you hold the keys to. It is not transferred to an individual or to an address someone types into the chat.
Why a seed phrase request ends the conversation
Whoever holds the phrase holds the funds. There is no support process, no verification step and no recovery procedure that needs it. Once it is shared, the wallet is no longer yours, and any balance still visible in the bot chat can be emptied at any moment. Do not send it, and treat the chat as compromised from that point.
The pattern to watch
Each payment tends to produce a new requirement: the unlock fee is followed by a gas fee, then a tax, then a verification deposit. The balance in the chat may even grow while nothing becomes withdrawable. The growing number is part of the pitch, not evidence of funds.
What to do now
Stop sending funds. Take screenshots of every message, request and payment, and keep the transaction hashes. Then work through the escalation steps below in order: confirm the official handle from the bot's own website, re-read its documentation on withdrawals, and use only its official support channel. Check the bot you are using against its own page on BotFees so you know which chat is the real one before you send another command.
What to do, in order, when a withdrawal fails
Each step removes one possible cause. Work through them in sequence before you send another withdrawal command.
- Confirm the official handle. Open the bot's own website and copy the handle from there, then compare it with the chat you are typing in, character by character. Lookalike accounts copy the name, the logo and the wording of the messages.
- Re-read the bot's own docs on withdrawals. They may document a minimum amount, a cooldown between requests, a chain requirement, or a fee taken out of the amount you receive. If the docs list supported chains, check that the address you entered belongs to one of them.
- Find the transaction in a block explorer for the chain the bot trades on. Record which of three things is true: it failed, it is still pending, or it does not exist. That single fact tells you whether the problem sits on-chain or in the bot's own ledger.
- Check the native coin balance at the sending address. A wallet holding only the token you want to withdraw still cannot pay the network fee, so the transfer never gets broadcast.
- Use the bot's official support channel only, reached from the bot's own website or from the bot itself, never from a direct message or a group reply that found you first. Send the transaction hash, the amount, the chain and the time of the request.
- Revoke wallet access if you no longer trust the bot, then move any remaining funds from a wallet you control. Revoking stops future access; it does not recover funds already sent. A balance that exists only inside the bot chat has no on-chain record to revoke, and can only be disputed through the bot's own channel.
Match the bot you are using against its own page on BotFees before you send another withdrawal command, so you know you are in the right chat: Banana Gun is listed with @BananaGun_bot and BONKbot with @bonkbot_bot on their pages, and the full list sits at /bots.
Before you deposit again
A failed withdrawal is easier to sort out when the bot publishes what it does. A bot with a documented fee, documented chains and a documented withdrawal process gives you something to check against. Treat that as a selection criterion, not a detail.
What to check before you deposit
- Official handle. Open the bot's own website and copy the handle from there. Compare it character by character with the chat you are using. For example, BONKbot's page lists @bonkbot_bot and Trojan's lists @solana_trojanbot.
- Custody model. Decide whether the bot imports your private key or keeps an internal ledger balance that you withdraw from. That answer decides where your funds sit and what a "balance" in the chat means.
- Supported chains. Banana Gun (/bot/banana-gun) lists Ethereum, Solana, BNB Chain and Base. BONKbot (/bot/bonkbot) and Trojan (/bot/trojan) list Solana only. Maestro (/bot/maestro) lists many chains. Sending the wrong asset to a bot that does not support that chain is a common way to lose funds.
- Fee on your chain. Fees differ by chain inside the same bot. Banana Gun's site states a 0.5% Ethereum trade fee and a 1% Solana trade fee; Sigma's docs state 1% on Ethereum and 0% on Solana. Check the chain you actually trade on.
- Documented withdrawals and support. If the docs never describe how withdrawals work or how to reach support, you have nothing to follow when a withdrawal stalls.
Compare before you deposit
Put two bots side by side on their documented features and chains, then pick the one whose process you can verify. Trading memecoins can lose all of the money put in. None of this is financial, legal or tax advice.
Frequently asked questions
Why does my Telegram trading bot say the withdrawal failed but no transaction appears?
A failed withdrawal usually never reaches the blockchain, so there is no transaction to find. Before assuming funds are gone, look for a transaction signature in the bot's own withdrawal history. If there is none, nothing was broadcast and the balance should still sit in the wallet the bot controls. Common causes are a price move while the order was pending, a token that could not be sold into the withdrawal currency, a minimum withdrawal amount, or not enough of the chain's native coin to pay the network fee. Check the bot's own documentation and its official Telegram handle from its website.
The bot shows a balance but nothing arrives in my wallet. Where is the money?
A balance inside a bot is a record on the bot's side, not coins sitting in your wallet. Funds generally stay in a wallet the bot controls until a transfer confirms on-chain. Compare two things in a block explorer: your own address, and the deposit address the bot gave you. If your address shows nothing and the bot's address still holds the amount, the transfer did not happen. Withdrawals can also convert tokens into the chain's native coin first, which takes a moment and needs fee headroom. Keep the bot's transaction history open while you check.
Can a Telegram bot block a withdrawal on purpose?
If a bot holds your private key, it controls the wallet, so an operator can technically restrict or delay transfers. That is the trade-off of a custodial bot: you trust the service to release your funds. Published terms may also set minimum withdrawal amounts, cooldowns or limits during heavy load, which can look like a block. Read the bot's own documentation for those rules. Test with a small amount first, keep only trading funds in any custodial bot, and treat unexplained repeated refusals as a reason to stop depositing.
Do I need to keep native coin in my wallet to withdraw?
Yes, usually. Moving tokens on Solana needs SOL, and on Ethereum, BNB Chain, Base or other EVM chains it needs that chain's native coin for gas. Some bots deduct the network fee from the withdrawn amount; others expect the fee to come from your balance. If the balance is entirely in a token and the bot cannot sell it, the withdrawal can stall. Keep a small amount of native coin available, and check the bot's documentation for how it handles withdrawal fees. Nothing here is financial advice.
A support account says I must deposit first to unlock my withdrawal. Is that normal?
No. A demand for a new deposit before an existing balance can be withdrawn is a standard impersonation pattern. Official support does not message you first, does not ask for a seed phrase or private key, and does not require a payment to release your own funds. Open the bot's own website and use only the Telegram handle listed there, then contact support through that handle. Do not send anything to the account that contacted you. Screenshot the conversation, report and block it, and warn others in the bot's official channel.
Should I revoke the bot's access while a withdrawal is stuck?
It depends on how the bot holds funds. If you connected an external wallet, revoking token approvals stops further spending from that wallet, but it will not push a pending withdrawal through, and it may complicate a transfer already in progress. If the bot holds a wallet and key it created for you, wallet-level revoking does nothing to that balance. In both cases, wait for any pending transaction to resolve, confirm the outcome in a block explorer, and never share a seed phrase with anyone, including support.