đĄEVM transaction failed
Why can't I sell my EVM tokens? What is Pixiu/honeypot/closed source/conditional restrictions on selling tokens?
On EVM, taking the ERC20 standard as an example, TOKEN only provides an abstract definition standard for each token contract, but in fact the specific implementation of each token contract is implemented by the developer of the token contract. For the contract developer, it is completely possible to implement the token sale control code at will without violating the token standard.
Therefore, on the EVM, smart contract scanning and anti-fraud have always been an infinite proposition, but given that the EVM has not made any actual progress in token security standards, it is impossible to 100% eliminate tokens that are conditionally restricted in code sales in the current EVM DEX trading market. Take the following case as an example:
The contract code of a token can be set with invisible conditions to restrict token sales as follows, so as to fully/partially lock sales and push up token prices to lure more buyers.
The token can only be sold within a certain period of time (time lock)
After this period of time, it can be sold normally, which will often lead to the situation that it is impossible to reproduce the situation at that time, so as to achieve the effect of passing off fakes as real ones.
The token cannot be sold within a certain price range (price lock)
It can also be implemented dynamically, that is, malicious token developers can control the dynamic selling price of tokens through token contracts, and cannot sell if the price is not met. In this way, addresses and transactions that partially meet the price can succeed at this moment, so as to achieve the effect of passing off fakes as real ones.
The token cannot be sold at a certain address/part of the transaction address (blacklist)
In the early days, blacklists were mainly static, but now there are many dynamic blacklists, because it is completely possible to implement dynamic floating through code, that is, malicious developers monitor the transactions of certain addresses and dynamically blacklist/unban the addresses that meet the conditions, and often do so during peak trading, and then unban them after the peak trading. In this way, some addresses controlled by humans can succeed at this moment, so as to achieve the effect of mixing fakes with reals.
The above conditions are only used as examples. In practice, the EVM code used to restrict the conditions for selling tokens can be more conditions, with infinite combinations. That is, there are more conditions besides the above conditions, and each condition can be combined arbitrarily. This is why many contract fraud tokens cannot be sold when the price is good on the K-line chart, even if all the fee configurations are good, especially for closed-source token contracts, where even the code itself cannot be viewed.
However, even for open source token contracts, there are a large number of new token contracts every day, and professional smart contract engineers cannot check them all. Current smart contract security service providers can only use AI to assist in marking, but cannot achieve 100% filtering, which is also a major pain point in the current EVM contract ecosystem.
How to avoid Pixiu/honeypot/non-open source/conditional restrictions on selling tokens on EVM?
Try to avoid "non-open source" tokens. Even open source tokens are difficult to traverse and identify 100% accurately, not to mention non-open source tokens. In addition, token contracts generally do not involve commercial technology patents that need to be kept secret. Non-open source itself is problematic, so try to avoid them.
Before buying EVM tokens, do enough DYOR, because the DEX trading market is a completely unrestricted free trading market with opportunities and risks. Understanding the potential risks of token contracts is the key to improving the winning rate.
Pay attention to the security check parameters of token contracts. DBot provides a contract check function in fast trading and a professional advanced filtering function in copy buying. It can be set according to your needs to help you avoid the Pixiu/honeypot/non-open source/conditional restrictions on selling tokens on EVM to the greatest extent.
However, it should be noted that the data of this security function comes from the smart contract security service provider GoPlus. Currently, all smart contract security service providers on the market cannot 100% guarantee the absolute security of the smart contracts they detect, and can only serve as one of the auxiliary reference information for self-judgment!
DBot EVM chain Fast Buy/Sell contract detection
After entering CA, token security detection will be performed, including whether it is a Pixiu, pool burn amount, whether it can be minted, whether there is freezing permission, top 10 holdings, etc. The data comes from GoPlus, which is realized through smart contract analysis and can only be judged based on the status at the time of the transaction. DYOR
DBot EVM chain copy buy filter settings
Skip Hoeypot: Tokens that defined as honeypots by GoPlus will not be bought when enabled, the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Skip Not Opensource: Not opensouce tokens that defined by GoPlus will not be bought when enabled, the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Only Buy Once: Buy the same token only once when enabled (The on-chain data is highly volatile, and this feature is only used as an auxiliary)
Token Holding: If the following wallet buys tokens that your wallet is holding, whether or not to continue to follow buying (The on-chain data is highly volatile, and this feature is only used as an auxiliary)
Max Buy Tax: Only buy tokens with buy tax below this value(data from GoPlus), the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Max Sell Tax: Only buy tokens with sell tax below this value(data from GoPlus), the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Min Liquidity: Only buy tokens with liquidity above this value, the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Max Token Age: Only buy tokens with ages less than this value (Judged based on token creation time, not trade pair creation time, and the on-chain date is highly volatile, this feature is only used as an auiliary)
Copy Range: Only buy tokens that are bought within this range by the copied wallet, the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Market Cap Range: Only tokens with market cap in this range will be copied buy, the filtering function is realized through smart contract analysis and can only be judged based on the state of the transaction, and will be filtered as much as possible but not 100% guaranteed
Last updated
