Closed AdamB2023 closed 1 year ago
Another one: https://dexscreener.com/ethereum/0x95e28f6884e4b67284cc96328924ebcd33ee16ce
Looking pretty similar to previous, it's now 98% fee. Is it caused by some customization for the contract? Can it be prevented?
-- SWAP DETECTED -----------------------------------------------
02-07 21:03:30.330 Tx [...]
069c -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-07 21:03:30.330 069c - TX GAS CONTROL ------- Tx GAS = 63.687922802 and current GAS price = 40.895308078 --> let's continue
02-07 21:03:30.330 069c - MIN_MAX_MARKETCAP ---- liquidity = 4857.83$ --> let's buy
02-07 21:03:30.330 069c - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.1) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-07 21:03:30.330 069c - GAS CALCULATION ------ Tx GAS = 63.687922802 --> your Tx GAS = x
02-07 21:03:30.330 069c - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 0% | SellTax: 0% - Check made in: 0.00181s
069c -- COPY SWAP ---------------------------------------------------
02-07 21:03:30.330 069c - BUY Tx - SHIBEREUM AI - [...]
069c -- CONTROLS AFTER Tx -------------------------------------------
02-07 21:03:35.335 069c - BUY PRICE ----------- You used x Wrapped Ether to buy x SHIBEREUM AI --> Buy price = x Wrapped Ether/SHIBEREUM AI
02-07 21:03:35.335 069c - SAME BLOCK ? --------- Swap block: x / Your Tx block: x --> CONGRATS!! Your Tx was in the same block :)
02-07 21:03:35.335 069c - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (25 position before)
02-07 21:03:35.335 069c - BALANCE CHECK -------- Your ETH balance is: x
02-07 21:03:35.335 069c - TOKEN APPROVAL ------- Token SHIBEREUM AI needs approval --> let's approve
02-07 21:03:48.348 069c - SHIBEREUM AI approval Tx: [...]
069c -- ANTI RUG ----------------------------------------------------
02-07 21:03:48.348 069c - SHOULD WE CONTINUE? -- BUY Tx made in a row = 2 | AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP parameter = 10 --> let's continue
02-07 21:03:48.348 069c ANTIRUG -------------- Anti rug-pull method starts for token SHIBEREUM AI
02-07 21:03:48.348 - ANTI RUG FINAL LIST -- Anti rug-pull method starts for token
02-07 21:03:48.348 - LIQUIDITY REMOVAL ---- We will sell if more than 30% of liquidity is removed
02-07 21:03:48.348 - OTHER RUG METHODS ---- We will also check for Sell Allowance / Blacklisting / Trading Status / Cooldown changes
02-07 21:03:48.348 069c GET CONTRACT --------- SHIBEREUM AI contract is open source --> we will be able to offer you good protection
-- SWAP DETECTED -----------------------------------------------
02-07 21:03:52.352 Tx [...]
daf9 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-07 21:03:52.352 daf9 - TX GAS CONTROL ------- Tx GAS = 63.488109411 and current GAS price = 41.092343966 --> let's continue
02-07 21:03:52.352 daf9 - BUY...SAME_TOKEN ----- Token SHIBEREUM AI was already bought --> buy cancelled
SHIBEREUM AI Price (069c): 0.000000002247 | Sell Tax 0% | Price after Tax 0.000000002247486744 | 1st target price 0.000000007567 | Stoploss 0.000000002 | Current profit: -40.6%
02-07 21:16:03.163 069c - SHIBEREUM AI STOPLOSS REACHED : current price = 0.000000000022475 --> let's sell all your remaining tokens! (26430665512374683015052633 tokens)
02-07 21:16:03.163 069c - HONEYPOT / TAX CHECK - SHIBEREUM AI - Trading is open: true | BuyTax: 0% | SellTax: 99% - Check made in: 0.00296s
02-07 21:16:03.163 069c --> SELL TAX > 50% --> TOO HIGH --> buy cancelled.
I need more details, please find me the Tx that set the sell tax to 98%
After little investigation, I only found the "Cool Starts" Tx for the first token , but no mention of the "fee" word, or of a percentage above 90%, in the Tx parameters..
--
For 1st coin Cool Starts
https://etherscan.io/tx/0x61fda4c3564dd73940cbb7c333ad954d3d74fe8dbb597123aa7483befed0c659
https://tokensniffer.com/token/eth/0x47976102c15a21d63541bf3b0dea2fcd76436592
function CoolStarts(uint256 _sum) public {
for(_sum; _sum !=MaxSwapPerc; _sum++) {
TimeStampInitial = _sum;
TimestampOne = _sum;
}
}
https://etherscan.io/address/0x47976102c15a21d63541bf3b0dea2fcd76436592#code
He passed 1, and loop started till 100, as uint256 public MaxSwapPerc =100;
This set both TimeStampInitial
and TimestampOne
to max.
For 2nd coin Bitbinary
https://etherscan.io/tx/0x0b1a81afc8d50a7d6730a61270bdf2a30040950e76d4b4b1f7ceef8c66e9a360
https://tokensniffer.com/token/eth/0xacc862047fe2b7339def33c813158cfe006303c1
function Bitbinary(uint256 _twe) public {
_twe = 1;
for(_twe; _twe !=TsVal; _twe++) {
VisibleValue = _twe;
}
}
Both are passing uint256
= 1
Both of them have priority 440+
This makes front running it unprofitable, most likely?
Contracts comparison: https://etherscan.io/contractdiffchecker?a2=0xACc862047Fe2B7339DeF33c813158CFe006303c1&a1=0x47976102c15a21d63541bf3b0dea2fcd76436592
Not sure how far we can go to prevent it, or what methods we can use. Maybe we could somehow detect such contracts and use a custom skip?
mmh, honestly here, I don't see which rule I could implement to detect this...
because dev can take same function and just change variable names in it...
so for me, sadly, those kind of functions cannot be detected automatically. I close this issue unless you have a cleverer idea than me :)
Is it possible to see fee in mempool before it triggers to be processed on-chain, so that we can exit the trade eariler?
TAX_CHECK : true, MAX_SELL_TAX: "75%"
WH entered trade with SellTax: 1%, and didn't make any action when tax changed to 99%.
The contract is open source.
Coin: https://dexscreener.com/ethereum/0xb3640ef11cf9534dd9092d715a5eae045014e7e0