tsarbuig/limit-sniper-v3

The FASTEST crypto Sniper bot in the market, written in Rust

limit-sniper-v3's Issues

[enhance]mempool with tax detection and honeypot detection

i hope we can mempool snipe with sameblock tax and honeypot detection

and i know tax detection already implement thx alot

[Enhance]multiwallet without custom contract

is it possible using multiwallet without custom contract due to there is some contract (not many) code has "tx.origin" etc.. will make custom contract don't work
(i know this option will destory all the sniper logic from now need to import all the private key etc.., so i put it last, i guess this option will reject i think so ， even i am not good at programing i know it will destory everything like brain 😂)

[Enhance]when you snipe an AddLiquidity Tx, bot auto-detect if liquidity is added in BUSD/USDT... and adapt automatically but enable trading not yet ****

enable trading sniping can't adjust adapt automatic ****

swap ETH <> WETH with the bot

[AddDex]Core chain , Icecreamswap

https://icecreamswap.com/

add fixed gwei to (more_gas_for_first_spam_tx)

please to add fixed gwei to (more_gas_for_first_spam_tx) to prevent eth gas spike or dev sending tx with high gas to rekt sniper

Sell stream improvements

hey bro possible to:

1. show on the sell stream total net tokens worth in BNB/ETH
2. after we sell 25/50/75% sell stream ends, it should restart as long as there is any tokens left
3. add multiwallet sell
4. add sell if tax lower then specified by user. ex. sell if tax lower then 20%
5. autosell after xx seconds

Give the ability to change whitelisted wallets with the bot

Implement Zksync

[Bug]Antirug issue

After buy the token, the bug happen so i couldn't test more for this function
-- COST CALCULATION --------------------------------------------
2023-02-14T01:58:48.262319Z INFO Let's analyze your first tx ok: 0x62ff…069e
2023-02-14T01:58:48.280710Z INFO Bought 601767.0 Maiko using 0.000000000000000000 BNB price=0

-- TOKEN APPROVAL ----------------------------------------------
2023-02-14T01:58:48.280742Z INFO Let's approve token Maiko

-- ANTIRUG and AUTOSELL START ----------------------------------
2023-02-14T01:58:55.450936Z INFO Contract approved successfully - Tx: 0x0480ac07e7a826860388a299370ffb152287913151242baeaae12c6fc0b9cefa
2023-02-14T01:58:56.551229Z INFO AutoSell mode starting for Maiko
The application panicked (crashed).
Message: called Result::unwrap() on an Err value: OddLength
Location: src/modes/antirug.rs:128

This is a bug. Please report it to TsarBuig.

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Aborted (core dumped)

=============Updated=================
even i want to go antirug mode directly there is still issue

Using Stable Coin (like USDT) to using CA spam buy

it's will avoid overdraft problem

and don't effort BNB or ETH 's price fluctuations

Suggestion for improve

"in my opinion"，i will marked which i feel more important and priority with star*
but just reference。

1.mempool with tax detection and honeypot detection(Tax done)
2. ‌c‌‌‌o‌‌‌n‌‌‌t‌‌‌r‌‌‌a‌‌‌c‌‌‌t‌‌‌ ‌‌‌b‌‌‌u‌‌‌y‌‌‌ ‌‌‌a‌‌‌p‌‌‌p‌‌‌r‌‌‌o‌‌‌v‌‌‌e‌‌‌ ‌‌‌problem(solved)
3. ‌ ‌s‌‌‌p‌‌‌a‌‌‌m‌‌‌ ‌‌‌b‌‌‌u‌‌‌y‌‌‌ ‌‌‌s‌‌‌t‌‌‌u‌‌‌c‌‌‌k‌‌‌ problem(solved)
4.simulate buy & sell & tax &honeypot detection (without mempool)
5.implement blacklist front run ****
6.Tax detection switch (optional,detect buy or both of buy and sell)
7.after turn to sell mode still can click one button to sell(in case the token dump too much , or never hit our target) ***
8.when you snipe an AddLiquidity Tx, bot auto-detect if liquidity is added in BUSD/USDT... and adapt automatically but enable trading not yet ****

9. is it possible using multiwallet without custom contract due to there is some contract (not many) code has "tx.origin" etc.. will make custom contract don't work
   (i know this option will destory all the sniper logic from now need to import all the private key etc.., so i put it last, i guess this option will reject i think so ， even i am not good at programing i know it will destory everything 😂)

[Enhance]implement blacklist front run ****

important

this can make u after sniped, and dev blacklist or high tax our address and we can frontrun

[Enhance]Tax detection switch (optional)

for example

if the token buy tax was 10% but sell tax was high like 60%

then, if sniper can have a switch

we can detect buy+sell tax in same block

but, it's optional not too important

[enhance]simulate buy & sell & tax &honeypot detection (without mempool)

for those token which u don't know how many dead block or already launch and u want to buy

[Enhance]Detect Enable trading =true

Hi Tsar due to u coding succes with auto methoid block delay

i think this should be implement for u

example :

function tradingStatus(bool _status) public onlyOwner {
tradingOpen = _status;

can we monitoring this methoid and set position = 1 (due to there is only 1 parameter at this function)

and trigger only if value =1

cuz , some chinese dev will send false or 0 to this function to trigger bot

then send 1 or true to really enable trading

================================
most of this type token, didn't have dead block

but if u can implement with delay block function will be great

solve nonce problem when using Antirug

only_snipe 's filter improvement

for now, if we fill in "dev_wallet" it's will only snipe the token creator's tx

however , many methoid id was trigger by "owner" and owner can be transfer to another address

so i wish we can automactally detect owner's address in "Read Contract"

[Enhance]after turn to sell mode still can click one button to sell ***

(in case the token dump too much , or never hit our target)

if there is no button, we need to go pancake to sell by ourself... too slow

Multi Node selecting transction

Hi Tsarbuig

i've heard there is sniper can send transction to multi node and selecting fastest one
and make fastest one to send transction at result

that kind sniper was very expensive so i'd hope u can do some research of this , i think that will be good feature