ARCHALIS GUIDES · BNB CHAIN
Why can’t I sell my token?
A failed sale can mean a trading restriction, a liquidity problem or an execution error. Start with the evidence before changing your swap settings.
By Archalis · Published 5 November 2026
Before another attempt, check these four things.
- Contract and network. Match the address on BNB Chain. A familiar name or logo does not establish that you hold the intended token.
- Where the failure happened. Was there no quote, a wallet warning, a pending transaction or a confirmed on-chain failure? Keep the exact error and transaction hash, if one exists.
- Fees and approval. Check the wallet’s fee estimate and the router’s allowance. Standard BNB Chain transactions use BNB for gas; supported wallet features may provide alternative fee payment. An approval is separate from the sale. MetaMask’s fee explanation.
- Pool, route and amount. Identify the market used by the quote. A displayed token price does not prove that sufficient liquidity exists for your intended trade.
A QUICK WAY TO NARROW THE PROBLEM
Where does the sale stop?
No quote or wallet warning?
Check the network, route, balance, fees and approval.
Transaction reverted?
Read the exact error and contract evidence. A failure alone does not identify the cause.
Received less than expected?
Separate token charges, price impact, swap fees and quote changes.
What does the failure actually tell you?
The wallet cannot submit
Start with the network, fee estimate, balance and transaction status. A submission problem does not by itself establish a token restriction.
The swap reverts
Read the error in context. A transfer failure can involve an allowance or contract restriction. INSUFFICIENT_OUTPUT_AMOUNT concerns the minimum output; it is not a standalone honeypot verdict. PancakeSwap’s error reference.
There is no usable quote
Check whether the selected route has liquidity. Missing route coverage in one interface and an empty pool are different findings.
The sale returns much less
Separate token transfer charges, pool price impact, swap fees and quote changes. A completed transaction can still have a poor outcome.
More slippage is not a diagnosis.
Slippage tolerance sets how much the execution may deviate from the quote before the swap fails. It does not remove a blacklist, restore drained liquidity or bypass a contract rule. Raising it can permit a worse execution price.
A token tax and price impact are different: one is imposed by token transfer logic; the other reflects how a trade moves the pool price. In an observed buy/sell test, a measured loss can include more than a transfer tax.
There is no universal “safe” slippage percentage for an unknown token. Establish the reason for the failure before accepting a worse quote or paying for repeated attempts.
Three costs, three different questions.
| Concept | What it describes | What to inspect |
|---|---|---|
| Token transfer charge | A deduction imposed by token transfer logic. | Contract rules and the recorded transfer outcome. |
| Price impact | The effect of the trade on the pool price. | Trade size and liquidity in the selected market. |
| Slippage tolerance | The permitted deviation from the quote before execution fails. | The quoted output and minimum output accepted. Tolerance is not itself a fee. |
Read the result, the conditions and the date.
In an Archalis report, start with Sellability: did the recorded buy and sell succeed, for which tested conditions, and with what measured loss? Then inspect Liquidity and Contract control.
A successful test applies to its recorded wallet, route, amount and blockchain state. It does not establish that your later sale will succeed. A failed or incomplete test needs its supporting evidence; missing evidence is not a pass.
See an archived sellability result for SUPERMAMA →
Read how Archalis assesses structural risk →
Two cases that show why context matters.
SUPERMAMA · OCTOBER 2026
Renounced ownership did not protect the pool.
The investigation reconstructed a concealed transfer permission used to remove tokens from the pool. Burning LP tokens and renouncing ownership did not disable that permission.
This is evidence about a specific contract, not a rule that all failed sales share the same cause.
Read the SUPERMAMA reconstruction →AXIS · OCTOBER 2026
A successful sale can be part of the attack.
A privileged balance change was followed by a sale that removed USDT from the pool. Most pool funding was associated with the owner; the outflow was not equivalent to outside buyers’ losses.
The case illustrates contract-control risk. It is not proof that a prior public honeypot test passed.
Read the AXIS evidence and limits →FROM SYMPTOM TO EVIDENCE
Check the contract you actually hold.
Use the BNB Chain checker to open the available report. Read its observation date and missing evidence before requesting a new assessment.
Public reports need no account. Saving a token and enabling monitoring are separate choices. Archalis does not execute trades or recover funds.