tsarbuig / wallethunter Goto Github PK
View Code? Open in Web Editor NEWThe first Copytrading crypto bot in the World - for Uniswap & Pancakeswap
wallethunter's People
Contributors
Stargazers
Watchers
wallethunter's Issues
[Bug] Coin isn't tracked after restart
8756 -- COPY SWAP ---------------------------------------------------
02-14 04:15:23.1523 8756 - BUY Tx - COINNAME- 0x - Case 1 - Swap sent in: 0.01906s
8756 -- CONTROLS AFTER Tx -------------------------------------------
02-14 04:15:36.1536 8756 - BUY PRICE ----------- You used 0.100000000000 Wrapped Ether to buy X COINNAME--> Buy price = X Wrapped Ether/COINNAME
COINNAME Price (8756): X | Sell Tax 43% < Max Tax (60%) | Price after Tax X | 1st target price x | Stoploss X | Current profit: X
WH restart -> coin not listed on ANTI RUG START, and no log on price update longer than 10 min
next WH restart -> everything ok
detailed logs on Telegram - @adamb
[Improvement] Empty password protection
When reading WH users messages, I noticed that some of them are not using a password to protect their private key.
We know that everyone should take own responsibility for security, however the code itself could help in such case.
This will especially benefit not only the users security, but also in case of breach will prevent making a bad image about WalletHunter.
Please implement a hardcoded password which would encrypt the config for people who aren't using any password.
[Error] Anti Rug console output error
v0.49.4h
It appears that antirug triggered, but there was an error.
02-08 16:04:02.42 cccb - ANTI RUG ------------- Liquidity is being removed for COIN_NAME. Tx: [...]
02-08 16:04:02.42 cccb - LIQUIDITY REMOVAL ---- More than 30% of liquidity was removed --> let's sell quickly!!
02-08 16:04:02.42 ----- ERROR : more details below -----
02-08 16:04:02.42 ----- Unhandled Rejection at -----
Promise {
<rejected> ReferenceError: tx_log_id is not defined
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-08 16:04:02.42 ----- Reason -----
02-08 16:04:02.42 undefined
02-08 16:04:02.42 cccb - HONEYPOT / TAX CHECK - COIN_NAME - Trading is open: true | BuyTax: 5% | SellTax: 40% - Check made in: 0.00203s
02-08 16:04:02.42 cccb - TX EARNINGS ---------- Selling X COIN_NAME will pay you X$ > SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's continue
02-08 16:04:02.42 cccb - SELL Tx sent : [...]
02-08 16:04:12.412 cccb - SELL Tx SUCCESS :)
If SELL TX FAILS, WH needs to Retry Selling Repeatedly
When WH attempts to sell a coin and the SELL TX fails, it simply stops trying to sell it. This can be a costly mistake.
Therefore, I think we need WH to repeatedly attempt to sell after a sell failure.
This feature is already available in LimitSwap and can be set with MAX_FAILED_TX_IN_A_ROW.
[Bug?] BuyTax: NaN% | SellTax: NaN%
Is it a bug, or there are cases it can't be detected and is visible as NaN% ?
If so, it would be better to set it to ex.: unknown, so it doesn't look like a bug.
[Method] Balancer
This TX isn't handled and require implementation
https://etherscan.io/tx/0x61a6dd3c0d7f1234b2818689a84f949976f5f1a32a01cbeadbc76d5543a0001c
“buy_and_sell” Mode - Need to Add Ability to Retry SELL TX if it Fails
If the tracked wallet’s BUY TX fails, then the tracked wallet will have no coins to sell.
Hence, there is no "sell signal" in this mode.
If the tracked wallet's BUY TX fails, BUT our BUY TX succeeds, then it should convert to "autosell mode" for that TX. Otherwise we will end up with coins that do not get sold and possibly crash in the meantime.
===============================================
To address this issue, I propose the following solution:
-
After a successful purchase in my wallet, have Wallet Hunter check the tracked wallet's transaction to see if it was also successful.
-
If the tracked wallet's transaction is not successful, have Wallet Hunter enter into the "autosell" mode and sell the coins according to the user's defined take profit targets and stop loss.
If this requires a lot of work, then, at the very least, I think the user should constantly be alerted that this coin has no sell signal & that a manual sell is required.
===============================================
I realize that the new "buy_and_sell_and_autosell" mode you created mitigates some of the issue above, but it does not change the fact that the "buy_and_sell" mode will not work in this scenario described above.
[Improvement] swapExactETHForTokensSupportingFeeOnTransferTokens
Could the WH use swapExactETHForTokensSupportingFeeOnTransferTokens instead of swapExactETHForTokens?
It would avoid the Error = UniswapV2: K --> not a slippage error... let's stop here.
[Bug] --autosell didn't sold all tokens
-- WH WHITELIST CHECK ------------------------------------------
Current WalletHunter tokens balance = 100
You hold enough tokens --> let's go!!
02-10 19:45:46.4546 -- FORCE SELL MODE ---------------------------------------------
Please enter the address of token you want to sell:
Do you want to use ETH as liquidity pair ? [y/n]: y
02-10 19:45:51.4551 Your _ balance is _ tokens
How many %% of you tokens do you want to sell? (enter '50' for 50% / push Enter or 'y' to sell all): y
BE CAREFUL : this token has MaxTxAmount = 1000000000 tokens. Do you want to sell this amount? [y/n]: y
02-10 19:45:54.4554 You want to sell less than MaxTxAmount --> let's sell 100% of your token SHIBA BOWL with Wrapped Ether pair
02-10 19:45:54.4554 - TOKEN APPROVAL ------- Token SHIBA BOWL is already approved
02-10 19:45:54.4554 Waiting Transaction Receipt...
02-10 19:45:59.4559 Tx:
02-10 19:45:59.4559 Your _ balance is _ tokens
For detailed logs, please DM on Telegram - @adamb
[Error] tokenName is not defined
v0.49.4h
Experienced this error in no-trade time, during a price checks.
02-12 20:24:22.2422 ----- ERROR : more details below ----- │
02-12 20:24:22.2422 ----- Unhandled Rejection at ----- │
Promise { │
<rejected> ReferenceError: tokenName is not defined │
at /snapshot/WalletHunterJs/WalletHunter.js │
at runMicrotasks (<anonymous>) │
at processTicksAndRejections (node:internal/process/task_queues:96:5) │
} │
02-12 20:24:22.2422 ----- Reason ----- │
02-12 20:24:22.2422 undefined │
│
│
02-12 20:24:22.2422 ----- ERROR : more details below ----- │
02-12 20:24:22.2422 ----- Unhandled Rejection at ----- │
Promise { │
<rejected> ReferenceError: tokenName is not defined │
at /snapshot/WalletHunterJs/WalletHunter.js │
at runMicrotasks (<anonymous>) │ at processTicksAndRejections (node:internal/process/task_queues:96:5) │
} │
02-12 20:24:22.2422 ----- Reason ----- │
02-12 20:24:22.2422 undefined │
│
SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS not working due to incorrect TX interpretation
I reported this issue a whole ago, but I'm not sure if it was resolved. Documenting here in case it was overlooked.
Wallet Hunter TX log is showing a profit, when it clearly sold at a loss.
Also, the TX log is reporting a gain when it’s looking at someone else’s TX and not mine.
Also, this is causing SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS to work incorrectly. It’s reporting a gain of $220.07 when it’s in fact negative.
[Improvement] Honeypot not recognized / tax not shown
https://dexscreener.com/ethereum/0x6b5d63c54927395a46c8a1309e688d7658804be9
https://honeypot.is/ethereum?address=0x9871CC5452dF2989A713fD318Ee12355f52F77Dd
https://tokensniffer.com/token/eth/hvcq6bb1s1n2pzgnuhfvh98q4605cdz2f06va8a6lmfun011ez1nzqllq422
4e40 - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 1% | SellTax: 1% - Check made in: 0.00141s
4e40 -- COPY SWAP ---------------------------------------------------
4e40 - BUY Tx - ValentineInu - TX_ID - Case 1 - Swap sent in: 0.00935s
4e40 ANTIRUG -------------- Anti rug-pull method starts for token ValentineInu
- ANTI RUG START ------- Anti rug-pull method starts for token
- LIQUIDITY REMOVAL ---- We will sell if more than 30% of liquidity is removed
- OTHER RUG METHODS ---- We will also check for Sell Allowance / Blacklisting / Trading Status / Cooldown changes
4e40 GET CONTRACT --------- ValentineInu contract is not open source --> we won't be able to protect you as much as we can
4e40 -- AUTO SELL ---------------------------------------------------
4e40 - AUTO SELL VALUES ----- ValentineInu | Buy price (including fees) [...] | Stoploss (0%) 0.000000000000000 | Current Sell Tax 1%
ValentineInu Price (4e40): 0.000020002711 | Sell Tax NaN% < Max Tax (60%) | Price after Tax NaN | 1st target price 0.000028875030 | Stoploss 0.000000000 | Current profit: -15.4%
Any way to improve, to avoid buying such coins, or exiting positon in case of selling lock?
[Bug] BUY_SEVERAL_TIME_SAME_TOKEN : false - failed
02-05 19:12:28 WH bought COIN_NAME
-- SWAP DETECTED ----------------------------------------------- [1715/7880]
02-05 19:12:28.1228 Tx ? from #7: ? - id: 489e
02-05 19:12:28.1228 NEW - This is a Uniswap Universal Tx with Command: 0b0800 --> let's try to clone it
489e -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-05 19:12:28.1228 489e - TX GAS CONTROL ------- Tx GAS = 58.698129361 and current GAS price = 26.550632993 --> let's continue
02-05 19:12:28.1228 489e - MIN_MAX_MARKETCAP ---- liquidity = 42419.44$ --> let's buy
02-05 19:12:28.1228 489e - AMOUNT CONTROL ------- your buyAmount (0.475) > MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's use MAXIMUM_BUY_AMOUNT_IN_BASE (buy_specific)
02-05 19:12:28.1228 489e - GAS CALCULATION ------ Tx GAS = 58.698129361 --> your Tx GAS = 110% * 58.698129361 = 64.567942297
02-05 19:12:28.1228 489e - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 5% | SellTax: 7% - Check made in: 0.00396s
489e -- COPY SWAP ---------------------------------------------------
02-05 19:12:28.1228 489e - BUY Tx - COIN_NAME - ? - Case 1 - Swap sent in: 0.01783s
489e -- CONTROLS AFTER Tx -------------------------------------------
02-05 19:12:36.1236 489e - BUY PRICE ----------- You used 0.100000000000 Wrapped Ether to buy 3284.417426940000 COIN_NAME --> Buy price = 0.000030446800 Wrapped Ether/COIN_NAME
02-05 19:12:36.1236 489e - SAME BLOCK ? --------- Swap block: 16564295 / Your Tx block: 16564295 --> CONGRATS!! Your Tx was in the same block :)
02-05 19:12:36.1236 489e - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (2 position before)
02-05 19:12:36.1236 489e - BALANCE CHECK -------- Your ETH balance is: 0.532832764841433509
02-05 19:12:36.1236 489e - TOKEN APPROVAL ------- Token COIN_NAME needs approval --> let's approve
02-05 19:12:48.1248 489e - COIN_NAME approval Tx: ?
02-05 19:13:46 it detected swap for same coin, and skipped it as intended.
-- SWAP DETECTED -----------------------------------------------
02-05 19:13:46.1346 Tx ___ from #7: ___ - id: 3cc1
02-05 19:13:46.1346 NEW - This is a Uniswap Universal Tx with Command: 0b0800 --> let's try to clone it
3cc1 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-05 19:13:46.1346 3cc1 - TX GAS CONTROL ------- Tx GAS = 60 and current GAS price = 26.138649428 --> let's continue
02-05 19:13:46.1346 3cc1 - BUY...SAME_TOKEN ----- Token COIN_NAME was already bought --> buy cancelled
Then i made an update to recent version, and it did not prevented purchase next day.
-- SWAP DETECTED -----------------------------------------------
02-06 03:59:34.5934 Tx ___ from #7: ___ - id: 13ef
02-06 03:59:34.5934 NEW - This is a Uniswap Universal Tx with Command: 0b0800 --> let's try to clone it
13ef -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-06 03:59:34.5934 13ef - TX GAS CONTROL ------- Tx GAS = 30.199644428 and current GAS price = 17.17356482 --> let's continue
02-06 03:59:34.5934 13ef - MIN_MAX_MARKETCAP ---- liquidity = 30384.63$ --> let's buy
02-06 03:59:34.5934 13ef - AMOUNT CONTROL ------- your buyAmount (0.1425) > MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's use MAXIMUM_BUY_AMOUNT_IN_BASE (buy_specific)
02-06 03:59:34.5934 13ef - GAS CALCULATION ------ Tx GAS = 30.199644428 --> your Tx GAS = 110% * 30.199644428 = 33.219608871
02-06 03:59:34.5934 13ef - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 5% | SellTax: 7% - Check made in: 0.00190s
13ef -- COPY SWAP ---------------------------------------------------
02-06 03:59:34.5934 13ef - BUY Tx - COIN_NAME - ___ - Case 1 - Swap sent in: 0.01661s
13ef -- CONTROLS AFTER Tx -------------------------------------------
02-06 03:59:47.5947 13ef - BUY PRICE ----------- You used 0.100000000000 Wrapped Ether to buy 5045.467234040000 COIN_NAME --> Buy price = 0.000019819770 Wrapped Ether/COIN_NAME
02-06 03:59:47.5947 13ef - SAME BLOCK ___ --------- Swap block: 16566917 / Your Tx block: 16566917 --> CONGRATS!! Your Tx was in the same block :)
02-06 03:59:47.5947 13ef - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (1 position before)
02-06 03:59:47.5947 13ef - BALANCE CHECK -------- Your ETH balance is: 0.367970195324476052
02-06 03:59:47.5947 13ef - TOKEN APPROVAL ------- Token COIN_NAME is already approved
02-06 03:59:47.5947 13ef - ANTI RUG ------------- Anti rug-pull method was already started for token COIN_NAME
02-06 03:59:47.5947 13ef - SHOULD WE CONTINUE___ -- BUY Tx made in a row = 1 | AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP parameter = 5 --> let's continue
13ef -- AUTO SELL ---------------------------------------------------
02-06 03:59:49.5949 13ef - AUTO SELL VALUES ----- COIN_NAME | Buy price (including fees) 0.000019819769976 | Stoploss (50%) 0.000009909884988 | You are holding 672988466098 tokens
02-06 03:59:49.5949 13ef - AUTO SELL VALUES ----- COIN_NAME | 1st target price 0.000039639539952 --> will sell 50% of your initial bag (336494233049 tokens)
02-06 03:59:49.5949 13ef - AUTO SELL VALUES ----- COIN_NAME | 2nd target price 0.001981778799898 --> will sell 50% of your initial bag (336494233049 tokens)
COIN_NAME Price (13ef): 0.000019532452 | Sell Tax 5% | Price after Tax 0.000018555829281462 | 1st target price 0.000039639540 | Stoploss 0.000009910 | Current profit: -6.4%
[Typo] buy instead of sell
In antirug method, when bot tried to sell but tax stopped it, it says "buy cancelled" instead of "sell cancelled".
02-12 20:26:50.2650 1e7c --> SELL TAX > 50% --> TOO HIGH --> buy cancelled.
[Improvement] Follow origin tracked address when selling
While tracking multiple wallets, if you copy buy TX of address A, but B will sell, your bot will copy that as well.
In my case, it makes multiple %'tage sells, which decrease income due to ERC20 fees.
Could you make a switch FOLLOW_ORIGIN_FOR_SELL with true / false?
With it if we copy coin X from wallet A, and wallet B sell it nothing will happen, as it will only follow wallet A sells.
[Method] `swapExactETHForTokensSupportingFeeOnTransferTokens`
This TX wasn't copied due to method isn't handled?
https://etherscan.io/tx/0x957d9eae404088ad5fce929e0973bd038948d0e26afa961ab8517353d5e38f10
[Bug] Tax is NaN%
v0.49.7
https://dexscreener.com/ethereum/0x82fcda725005d82760a75a5be173c4da922d2b33
https://etherscan.io/token/0xfd128e3513a704b6e747ffb723eea79bdae1e3a0
https://etherscan.io/address/0xfd128e3513a704b6e747ffb723eea79bdae1e3a0
Time is in UTC like Etherscan.
02-17 18:43:03.433 6427 GET CONTRACT --------- PrimeFi contract is open source --> we will be able to offer you good protection
PrimeFi Price (6427): 0.000000039678 | Sell Tax 4% < Max Tax (60%) | Price after Tax 0.000000038090640974
PrimeFi Price (6427): 0.000000037325 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000036204772022
PrimeFi Price (6427): 0.000000040234 | Sell Tax 4% < Max Tax (60%) | Price after Tax 0.000000038624719703
PrimeFi Price (6427): 0.000000038276 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000037127465772
PrimeFi Price (6427): 0.000000038584 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000037426373481
PrimeFi Price (6427): 0.000000043421 | Sell Tax 4% < Max Tax (60%) | Price after Tax 0.000000041684356416
PrimeFi Price (6427): 0.000000042651 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000041371749584
PrimeFi Price (6427): 0.000000044017 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000042696744487
PrimeFi Price (6427): 0.000000042744 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000041461976610
PrimeFi Price (6427): 0.000000042062 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000040800272651
PrimeFi Price (6427): 0.000000042261 | Sell Tax 3% < Max Tax (60%) | Price after Tax 0.000000040992981358
PrimeFi Price (6427): 0.000000038201 | Sell Tax NaN% < Max Tax (60%) | Price after Tax NaN
PrimeFi Price (6427): 0.000000038509 | Sell Tax NaN% < Max Tax (60%) | Price after Tax NaN
PrimeFi Price (6427): 0.000000040184 | Sell Tax NaN% < Max Tax (60%) | Price after Tax NaN
-- SWAP DETECTED -----------------------------------------------
02-17 18:48:23.4823
[Bug] buy_and_sell_and_autosell - issues with nonce
Nonce 17 - buy, Nonce 18 - token approval.
Then something happened with nonce, and bot didn't made 2 TXs in a row.
Only the bot is interacting with my address, no Metamask or manual TX at this time.
02-06 05:33:14.3314 7dff - BUY Tx - COIN_NAME1 - TX_ID - Case 3 - Swap sent in: 0.01677s
7dff -- CONTROLS AFTER Tx -------------------------------------------
02-06 05:33:24.3324 7dff - BUY PRICE ----------- You used 0.052980034338 Wrapped Ether to buy 342000.000000000000 COIN_NAME1 --> Buy price = 0.000000154912 Wrapped Ether/COIN_NAME1
02-06 05:33:24.3324 7dff - SAME BLOCK ? --------- Swap block: 16567382 / Your Tx block: 16567382 --> CONGRATS!! Your Tx was in the same block :)
02-06 05:33:24.3324 7dff - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (48 position before)
02-06 05:33:24.3324 7dff - BALANCE CHECK -------- Your ETH balance is: 0.311795071198346661
02-06 05:33:24.3324 7dff - TOKEN APPROVAL ------- Token COIN_NAME1 needs approval --> let's approve
02-06 05:33:35.3335 7dff - COIN_NAME1 approval Tx: TX_ID
7dff -- ANTI RUG ----------------------------------------------------
02-06 05:33:35.3335 7dff - SHOULD WE CONTINUE? -- BUY Tx made in a row = 2 | AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP parameter = 5 --> let's continue
- ANTI RUG ------------- COIN_NAME2 balance = 84123558262.25
02-06 05:33:35.3335 7dff ANTIRUG MANUAL LAUNCH- Anti rug-pull method starts for token COIN_NAME1
02-06 05:33:35.3335 - ANTI RUG FINAL LIST -- Anti rug-pull method starts for token
02-06 05:33:35.3335 - LIQUIDITY REMOVAL ---- We will sell if more than 30% of liquidity is removed
02-06 05:33:35.3335 - OTHER RUG METHODS ---- We will also check for Sell Allowance / Blacklisting / Trading Status / Cooldown changes
02-06 05:33:36.3336 7dff GET CONTRACT --------- COIN_NAME1 contract is not open source --> we won't be able to protect you as much as we can
7dff -- AUTO SELL ---------------------------------------------------
02-06 05:33:37.3337 7dff - AUTO SELL VALUES ----- COIN_NAME1 | Buy price (including fees) 0.000000154912381 | Stoploss (50%) 0.000000077456191 | You are holding 342000000000000 tokens
02-06 05:33:37.3337 7dff - AUTO SELL VALUES ----- COIN_NAME1 | 1st target price 0.000000309824762 --> will sell 50% of your initial bag (171000000000000 tokens)
02-06 05:33:37.3337 7dff - AUTO SELL VALUES ----- COIN_NAME1 | 2nd target price 0.000015489688987 --> will sell 50% of your initial bag (171000000000000 tokens)
[...]
COIN_NAME1 Price (7dff): 0.000000262897 | Sell Tax 20% | Price after Tax 0.000000210317396730 | 1st target price 0.000000309825 | Stoploss 0.000000077 | Current profit: 35.8%
COIN_NAME1 Price (7dff): 0.000000388108 | Sell Tax 20% | Price after Tax 0.000000310486193746 | 1st target price 0.000000309825 | Stoploss 0.000000077 | Current profit: 100.4%
02-06 05:52:27.5227 7dff - COIN_NAME1 1st SELL TARGET REACHED : current price = 0.000000310486194 --> let's sell 50% of your initial bag! (171000000000000 tokens)
02-06 05:52:27.5227 7dff - HONEYPOT / TAX CHECK - COIN_NAME1 - Trading is open: true | BuyTax: 10% | SellTax: 20% - Check made in: 0.00319s
02-06 05:52:27.5227 7dff - TX EARNINGS ---------- Selling 171000000000000 COIN_NAME1 will pay you 107.75$ > SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's continue
02-06 05:52:27.5227 7dff - SELL Tx sent : TX_ID - Waiting Transaction Receipt...
COIN_NAME2 Price (13ef): 0.000037216998 | Sell Tax 5% | Price after Tax 0.000035356148237547 | 1st target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 78.4%
COIN_NAME2 Price (13ef): 0.000041751410 | Sell Tax 5% | Price after Tax 0.000039663839932355 | 1st target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 100.1%
02-06 05:55:39.5539 13ef - COIN_NAME2 1st SELL TARGET REACHED : current price = 0.000039663839932 --> let's sell 50% of your initial bag! (336494233049 tokens)
02-06 05:55:39.5539 13ef - HONEYPOT / TAX CHECK - COIN_NAME2 - Trading is open: true | BuyTax: 5% | SellTax: 5% - Check made in: 0.00273s
02-06 05:55:39.5539 13ef - TX EARNINGS ---------- Selling 336494233049 COIN_NAME2 will pay you 228.24$ > SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's continue
02-06 05:55:39.5539 ---------- PENDING TX ------------
02-06 05:55:39.5539 Pending nonce = 21
02-06 05:55:39.5539 Current nonce = 19
02-06 05:55:39.5539 ----------------------------------
02-06 05:55:39.5539 13ef - WARNING - You have a pending Tx in your wallet: please wait for it to be mined or cancel it with Metamask.
COIN_NAME2 Price (13ef): 0.000041751410 | Sell Tax 5% | Price after Tax 0.000039663839932355 | 2nd target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 100.1%
COIN_NAME2 Price (13ef): 0.000041751410 | Sell Tax 5% | Price after Tax 0.000039663839932355 | 2nd target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 100.1%
COIN_NAME2 Price (13ef): 0.000042476954 | Sell Tax 5% | Price after Tax 0.000040353106572955 | 2nd target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 103.6%
-- SWAP DETECTED -----------------------------------------------
02-06 05:56:26.5626 Tx TX_ID from #16: ADDRESS_ID - id: 7fd3
02-06 05:56:26.5626 NEW - This is a Uniswap Universal Tx with Command: 0a080c --> let's try to clone it
-------------- DEBUG ----------------
amountIn = 360000000000000
amountOutMin= 161877396742076900
path lenght = 2
path = ADDRESS_ID,ADDRESS_ID
-------------- /DEBUG ----------------
7fd3 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-06 05:56:26.5626 7fd3 - TX GAS CONTROL ------- Tx GAS = 19.539377881 and current GAS price = 15.692384048 --> let's continue
02-06 05:56:26.5626 7fd3 - BALANCE CHECK -------- Your wallet hold 342000000000000 tokens before sell (to be divided by 10^token decimals)
02-06 05:56:26.5626 7fd3 - SELL_AMOUNT ---------- This wallet hold 360000000000000 tokens before sell --> he sold 360000000000000 tokens = 100.00% of holdings
02-06 05:56:26.5626 7fd3 - SELL_AMOUNT ---------- Your wallet hold 342000000000000 tokens before sell --> let's sell 100.00% * 342000000000000 = 342000000000000 tokens
02-06 05:56:26.5626 7fd3 - GAS CALCULATION ------ Tx GAS = 19.539377881 --> your Tx GAS = 120% * 19.539377881 = 23.447253457
02-06 05:56:26.5626 ---------- PENDING TX ------------
02-06 05:56:26.5626 Pending nonce = 21
02-06 05:56:26.5626 Current nonce = 19
02-06 05:56:26.5626 ----------------------------------
02-06 05:56:26.5626 7fd3 - TX EARNINGS ---------- Selling 342000000000000 tokens will pay you 291.12$ > SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's continue
02-06 05:56:26.5626 7fd3 - WARNING - You have a pending Tx in your wallet: please wait for it to be mined or cancel it with Metamask.
COIN_NAME2 Price (13ef): 0.000044714592 | Sell Tax 5% | Price after Tax 0.000042478862669420 | 2nd target price 0.000039639540 | Stoploss 0.000009910 | Current profit: 114.3%```
[Bug] Error for AutoSell - gasPrice is not defined
02-07 00:20:14.2014 5b70 - HALF WETH 1st SELL TARGET REACHED : current price = 0.000022961216396 --> let's sell 50% of your initial bag! (2490800852956 tokens)
02-07 00:20:14.2014 5b70 - HONEYPOT / TAX CHECK - HALF WETH - Trading is open: true | BuyTax: 0% | SellTax: 0% - Check made in: 0.00319s
02-07 00:20:14.2014 5b70 - TX EARNINGS ---------- Selling 2490800852956 HALF WETH will pay you 91.37$ > SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's continue
Error during AutoSell
ReferenceError: gasPrice is not defined
at AutoSell (/snapshot/WalletHunterJs/WalletHunter.js)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async AutoSellMode (/snapshot/WalletHunterJs/WalletHunter.js)
[Improvement] save ATH for `AUTOSELL_TRAILING_STOP_LOSS` upon restart
v0.50.0
Please make ATH for price being saved upon restart, otherwise WH is starting from 0.
[Method] Uniswap Universal case (0a000c) is not yet handled
-- SWAP DETECTED -----------------------------------------------
02-02 16:29:20.2920 Tx 0x807f6a7ac33765c46fd1cef2e6877eb618e1237668b7607af00d85a4c6194ee5 from #1: 0x1b73E83b498b68cC3B6b5AeE265322e29DFCb524 - id: 4ee5
02-02 16:29:20.2920 NEW - This is a Uniswap Universal Tx with Command: 0a000c --> let's try to clone it
02-02 16:29:20.2920 4ee5 - This Uniswap Universal case (0a000c) is not yet handled --> please report it to Tsarbuig
------------------- Tx DATA ANALYSIS -------------------
0x3593564c000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000063dbddb700000000000000000000000000000000000000000000000000000000000000030a000c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000001e0000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000001600000000000000000000000006bc08509b36a98e829dffad49fde5e412645d0a3000000000000000000000000ffffffffffffffffffffffffffffffffffffffff00000000000000000000000000000000000000000000000000000000640363a40000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ef1c6e67703c7bd7107eed8303fbe6ec2554bf6b0000000000000000000000000000000000000000000000000000000063dbddac00000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000041071c83b75fd53364291573b870ebc4e07cef6ce82acfbd6ba2166daf140a1c5a743cd9e8571414c425bbe0bef2d993b53c0b6d66f91d64f873cc633c9c3fbcff1c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000033d8db8ed01fd0c0b929000000000000000000000000000000000000000000000000023e76f1b022b51600000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000002b6bc08509b36a98e829dffad49fde5e412645d0a3002710c02aaa39b223fe8d0a0e5c4f27ead9083c756cc200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000023e76f1b022b516
02-02 16:29:20.2920 You will find below the Tx data decrypted:
02-02 16:29:20.2920 Please check inside every line, and search for useful information (token address / amount)
02-02 16:29:20.2920 --> if you find those infos, it can be sniped on same Block: contact @TsarBuig
02-02 16:29:20.2920 [0] 0000000000000000000000000000000000000000000000000000000000000060 --> 96
02-02 16:29:20.2920 [1] 00000000000000000000000000000000000000000000000000000000000000a0 --> 160
02-02 16:29:20.2920 [2] 0000000000000000000000000000000000000000000000000000000063dbddb7 --> 1675353527
02-02 16:29:20.2920 [3] 0000000000000000000000000000000000000000000000000000000000000003 --> 3
02-02 16:29:20.2920 [4] 0a000c0000000000000000000000000000000000000000000000000000000000 --> 4.523211306788825e+75
02-02 16:29:20.2920 [5] 0000000000000000000000000000000000000000000000000000000000000003 --> 3
02-02 16:29:20.2920 [6] 0000000000000000000000000000000000000000000000000000000000000060 --> 96
02-02 16:29:20.2920 [7] 00000000000000000000000000000000000000000000000000000000000001e0 --> 480
02-02 16:29:20.2920 [8] 0000000000000000000000000000000000000000000000000000000000000300 --> 768
02-02 16:29:20.2920 [9] 0000000000000000000000000000000000000000000000000000000000000160 --> 352
02-02 16:29:20.2920 [10] 0000000000000000000000006bc08509b36a98e829dffad49fde5e412645d0a3 --> 0x6bc08509b36a98e829dffad49fde5e412645d0a3
02-02 16:29:20.2920 [11] 000000000000000000000000ffffffffffffffffffffffffffffffffffffffff --> 0xffffffffffffffffffffffffffffffffffffffff
02-02 16:29:20.2920 [12] 00000000000000000000000000000000000000000000000000000000640363a4 --> 1677943716
02-02 16:29:20.2920 [13] 0000000000000000000000000000000000000000000000000000000000000000 --> 0
02-02 16:29:20.2920 [14] 000000000000000000000000ef1c6e67703c7bd7107eed8303fbe6ec2554bf6b --> 0xef1c6e67703c7bd7107eed8303fbe6ec2554bf6b
02-02 16:29:20.2920 [15] 0000000000000000000000000000000000000000000000000000000063dbddac --> 1675353516
02-02 16:29:20.2920 [16] 00000000000000000000000000000000000000000000000000000000000000e0 --> 224
02-02 16:29:20.2920 [17] 0000000000000000000000000000000000000000000000000000000000000041 --> 65
02-02 16:29:20.2920 [18] 071c83b75fd53364291573b870ebc4e07cef6ce82acfbd6ba2166daf140a1c5a --> 0x70ebc4e07cef6ce82acfbd6ba2166daf140a1c5a
02-02 16:29:20.2920 [19] 743cd9e8571414c425bbe0bef2d993b53c0b6d66f91d64f873cc633c9c3fbcff --> 0xf2d993b53c0b6d66f91d64f873cc633c9c3fbcff
02-02 16:29:20.2920 [20] 1c00000000000000000000000000000000000000000000000000000000000000 --> 1.2664759760331459e+76
02-02 16:29:20.2920 [21] 0000000000000000000000000000000000000000000000000000000000000100 --> 256
02-02 16:29:20.2920 [22] 0000000000000000000000000000000000000000000000000000000000000002 --> 2
02-02 16:29:20.2920 [23] 0000000000000000000000000000000000000000000033d8db8ed01fd0c0b929 --> 2.4484100815764922e+23
02-02 16:29:20.2920 [24] 000000000000000000000000000000000000000000000000023e76f1b022b516 --> 161697417046177060
02-02 16:29:20.2920 [25] 00000000000000000000000000000000000000000000000000000000000000a0 --> 160
02-02 16:29:20.2920 [26] 0000000000000000000000000000000000000000000000000000000000000001 --> 1
02-02 16:29:20.2920 [27] 000000000000000000000000000000000000000000000000000000000000002b --> 43
02-02 16:29:20.2920 [28] 6bc08509b36a98e829dffad49fde5e412645d0a3002710c02aaa39b223fe8d0a --> 0x9fde5e412645d0a3002710c02aaa39b223fe8d0a
02-02 16:29:20.2920 [29] 0e5c4f27ead9083c756cc2000000000000000000000000000000000000000000 --> 6.495476124257015e+75
02-02 16:29:20.2920 [30] 0000000000000000000000000000000000000000000000000000000000000040 --> 64
02-02 16:29:20.2920 [31] 0000000000000000000000000000000000000000000000000000000000000001 --> 1
02-02 16:29:20.2920 [32] 000000000000000000000000000000000000000000000000023e76f1b022b516 --> 161697417046177060
----------------------- ORIGINAL TX -----------------------
{
hash: '0x807f6a7ac33765c46fd1cef2e6877eb618e1237668b7607af00d85a4c6194ee5',
type: 2,
accessList: [],
blockHash: null,
blockNumber: null,
transactionIndex: null,
confirmations: 0,
from: '0x1b73E83b498b68cC3B6b5AeE265322e29DFCb524',
gasPrice: BigNumber { _hex: '0x0dfbc9ba59', _isBigNumber: true },
maxPriorityFeePerGas: BigNumber { _hex: '0x59682f00', _isBigNumber: true },
maxFeePerGas: BigNumber { _hex: '0x0dfbc9ba59', _isBigNumber: true },
gasLimit: BigNumber { _hex: '0x0376a8', _isBigNumber: true },
to: '0xEf1c6E67703c7BD7107eed8303Fbe6EC2554BF6B',
value: BigNumber { _hex: '0x00', _isBigNumber: true },
nonce: 20,
data: '0x3593564c000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000063dbddb700000000000000000000000000000000000000000000000000000000000000030a000c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000001e0000000000000000000000000000000000000000000000000000000000000030000000000000000000000000000000000000000000000000000000000000001600000000000000000000000006bc08509b36a98e829dffad49fde5e412645d0a3000000000000000000000000ffffffffffffffffffffffffffffffffffffffff00000000000000000000000000000000000000000000000000000000640363a40000000000000000000000000000000000000000000000000000000000000000000000000000000000000000ef1c6e67703c7bd7107eed8303fbe6ec2554bf6b0000000000000000000000000000000000000000000000000000000063dbddac00000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000041071c83b75fd53364291573b870ebc4e07cef6ce82acfbd6ba2166daf140a1c5a743cd9e8571414c425bbe0bef2d993b53c0b6d66f91d64f873cc633c9c3fbcff1c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000033d8db8ed01fd0c0b929000000000000000000000000000000000000000000000000023e76f1b022b51600000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000002b6bc08509b36a98e829dffad49fde5e412645d0a3002710c02aaa39b223fe8d0a0e5c4f27ead9083c756cc200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000023e76f1b022b516',
r: '0x1c4d9967c3d371b59fbb81fcf55da55664ed8ecf59f7ec5c502def612d3853b5',
s: '0x28c248b4619957902a7245dccda2eed50d4c05ad7bf20cbf6656de58cb5c5ee6',
v: 1,
creates: null,
chainId: 1,
wait: [Function (anonymous)]
}
---------------------- /ORIGINAL TX -----------------------
Tx = 0x807f6a7ac33765c46fd1cef2e6877eb618e1237668b7607af00d85a4c6194ee5
create swaps with MaxTxAmount - 1
instead of MaxTxAmount
[Improvement] MAXIMUM_BUY_AMOUNT_IN_BASE_PER_COIN
We've MAXIMUM_BUY_AMOUNT_IN_BASE, but it only applies to a single transaction.
With BUY_SEVERAL_TIME_SAME_TOKEN : true we are risking being drained.
Having an MAXIMUM_BUY_AMOUNT_IN_BASE_PER_COIN would allow us to mitigate it.
[Bug] TX prevented by SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS block another one
Your wallet is currently handling another Tx
My wallet wasn't handling another TX.
My address didn't make any TX due to SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS
-- SWAP DETECTED -----------------------------------------------
02-18 00:00:40.040 Tx 0x from #39: x - id: aff1
aff1 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 00:00:40.040 aff1 - TX GAS CONTROL ------- Tx GAS = 51.56 and current GAS price = 31.414743413 --> let's continue
02-18 00:00:40.040 aff1 - BALANCE CHECK -------- Your wallet hold 7238545500724 tokens before sell (to be divided by 10^token decimals)
02-18 00:00:40.040 aff1 - SELL_AMOUNT ---------- This wallet hold 41650000000000 tokens before sell --> he sold 2082500000000 tokens = 5.00% of holdings
02-18 00:00:40.040 aff1 - SELL_AMOUNT ---------- Your wallet hold 7238545500724 tokens before sell --> let's sell 5.00% * 7238545500724 = 361927275036 tokens
02-18 00:00:40.040 aff1 - GAS CALCULATION ------ Tx GAS = 51.56 --> your Tx GAS = 150% * 51.56 = 77.34
02-18 00:00:40.040 aff1 - TX EARNINGS ---------- Selling 361927275036 tokens will pay you 7.21$ < SELL_TX_MINIMUM_EARNINGS_IN_DOLLARS --> let's stop
-- SWAP DETECTED -----------------------------------------------
02-18 00:01:22.122 Tx 0x from #39: 0x - id: c302
02-18 00:01:22.122 c302 - SHOULD WE CONTINUE? -- your wallet is currently handling another Tx (x) for the same token --> let's skip this Tx to avoid spam
[Feature] Separate open position handling tool
As already anticipated Tsar, in my opinion If you want to focus your tools for advance users, you should separate the buy/copy tools from selling/trading tools.
For buying sniper and wallet hunters are perfect.
The problem is that I have many instances running for WH and sometimes also for Snippers. When some buy tx happens it is quite big mess to find information between all those files without wasting time.
As active user I would really appreciate if you could create a separate tool for selling and/or trading purposes
This tool would monitor token holdings of several wallets (refresh like every 5-10 sec)
We could skip holding values <$10
Option to skip some contracts manually.
In this way, we can monitor all open positions in ONE PLACE.
Furthermore, if some basic information of the token could be shown would be nice. MC, BUY/SELL FEE, TOTAL SUPPLY, AVG, AVG BUY PRICE, DELTA % FROM AVG ENTRY PRICE, HOLDINGS WORTH $$ (all this information monitored and refreshed every 5 seconds minimizing queris to our nodes)
Now the opperations to do.
Stablish up to two limit sells (like currently WH does)
Trailing stop (under development)
Option for autosell if it detects change fee method ID with >30% to <10% sell fee.
Protection mechanism
All best antirug in place
Minimum $ value to sell
Max sell fee
In the future if you are thinking to put these services behind a nice UI, I think it will be easier having them separated. 1 tab for snipping, 1 tab for wh, 1 tab for open position handling with respective config parameters.
I know these are BIG words and huge development. At least would be good to have some open discussion in the community and hopefully it helps to stablish the best roadmap for your project.
Bot should be able to transfer the tokens to other address as well as sell them
As soon as the bot copies a tx, it will transfer this token to some other specified address if transfer tax is 0%? What some dev does is they block the early buyers address, so just to be safe. And when the tracked wallet sells bot will sell from this other specified wallet.
[Feature] TAX change protection
Similar to LP removal, TAX change protection could be added.
This can be accomplished with the following variables:
TAX_CHECK_DURING_TRADE-trueorfalse; will enable or disable featureMAX_SELL_TAX_DURING_IN_TRADE-x%; if sell tax will reach x% after entering trade, WH will attempt to sellMAX_SELL_TAX_INCREASE_DURING_IN_TRADE-x%; if sell tax change more than x% after entering trade, WH will attempt to sell
[Bug] WH isn't reconnecting on node failure
I had 3 bots running, two got down due to same node, and not reconnected.
[Feature] Sell retry on failure
Sometimes, when price changes too much, we end up with Fail with error 'UniswapV2Router: INSUFFICIENT_OUTPUT_AMOUNT€'.
This force us to either sell manually, or wait on the price pullback, which is pretty uncommon in some cases.
It would be helpful to have an SELL_RETRY_ON_FAILURE option, which would immediately retry sell on failure.
Either a single sell, or the amount of possible attempts could be specified as a parameter.
[Feature] Custom labels for addresses
While tracking many addresses, it would be helpful to add labels to them.
Config file:
TRACKED_WALLET : [
"0xBaF6dC2E647aeb6F510f9e318856A1BCd66C5e19;NAME1",
"0x5a8216a9c47ee2E8Df1c874252fDEe467215C25b;NAME2",
"0x127D736495CCABe6433C62BdDdDF04bf36d411E2;NAME3"
Console:
[Bug] Honeypot Error
02-04 13:40:28.4028 Tx 0x169000c0c574610dd2032354faeec56bad114f108dd4e47f71676a70c9520066 from #14: 0x5Ad16BAA3AB19aDBEd1e21Ae3B4daE72c8C2D0f6 - id: 0066
0066 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-04 13:40:28.4028 0066 - TX GAS CONTROL ------- Tx GAS = 33.709538932 and current GAS price = 17.429580499 --> let's continue
02-04 13:40:28.4028 0066 - MIN_MAX_MARKETCAP ---- liquidity = 14904.81$ --> let's buy
02-04 13:40:28.4028 0066 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.095) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-04 13:40:28.4028 0066 - GAS CALCULATION ------ Tx GAS = 33.709538932 --> your Tx GAS = 110% * 33.709538932 = 37.080492825
02-04 13:40:28.4028 0066 - HONEYPOT ERROR ------ An error occured. More details below.
ReferenceError: tokenName is not defined
at Object.honeypot_check (/snapshot/WalletHunterJs/utils/utils.js)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async honeycheck_before_tx (/snapshot/WalletHunterJs/WalletHunter.js)
at async /snapshot/WalletHunterJs/WalletHunter.js
02-04 13:40:28.4028 0066 --> HONEYPOT DETECTED --> buy cancelled.
New Feature Request - Prevent Sale if SELL TAX Too High
SCENARIO:
——————
-
If the user follows sniper wallets, we often run into the issue where the SALES TAX is huge (>90% sometimes).
-
Usually after some time (30 minutes - 45 minutes), the tax is altered and it drops down to a reasonable level (like 5%). This is because the contract owner has not yet renounced the contract and is able to make changes to the tax settings.
-
After the coin trading well, usually they keep the tax at normal range and then finally reounce the contract.
-
(I believe this is done to prevent bots from pumping and dumping the coin).
Now if the user is utilizing the “autosell mode” and, for example, set his TAKE PROFIT at 200%, it’s very possible that he might buy very low and only to sell on the first spike at 90% tax.
I realize that there is a feature to check for taxes and avoid purchasing a coin if the tax is too high. That’s awesome, but:
-
in the scenario above, this would prevent us from buying a coin with excessive initial tax that will drop its sell tax to reasonable levels in 30 minutes or so.
-
I missed out on a lot of well-performing coins because the sell tax was too high at the time of launch.
NEW FEATURE SUGGESTION:
————————————————
To avoid this situation, I would like to propose a new feature where a sale is prevented if the SELL TAX is above a certain percentage.
This new feature would prevent an unfortunate situation where he snipes for cheap and sells at 90% tax.
It would also enable the user to “weather” the few minutes of excessive sales tax and allow him to sell at a profit later.
Of course an excessive BUY TAX is also not favorable and therefore, I believe that the user should still be able to screen for the excessive buy tax.
For example:
TAX_CHECK : true
MAX_BUY_TAX : “10%”, // used if TAX_CHECK = true --> bot won't buy if buy tax > MAX_BUY_TAX
MAX_SELL_TAX: "80%", // used if TAX_CHECK = true --> bot won't buy if sell tax > MAX_SELL_TAX
STOP_SELL_TX_IF_SELL_TAX_EXCESSIVE: “10” // bot won’t sell if sell tax > X%
[Bug] Github version incorrect
It seems like info from Github isn't recent.
02-07 00:43:47.4347 You are running version : v0.49.4c
02-07 00:43:47.4347 Latest release on Github : v0.49.4b
[Bug] BUY_SEVERAL_TIME_SAME_TOKEN : false not working for block, and multiple addresses tracked
While BUY_SEVERAL_TIME_SAME_TOKEN : false, and two addresses buy same coin in same block, WH is buying twice.
02-13 21:39:55.3955 Tx _ID_ from #27: _ID_ - id: 2644
2644 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-13 21:39:55.3955 2644 - TX GAS CONTROL ------- Tx GAS = 53.334507529 and current GAS price = 22.423918703 --> let's continue
02-13 21:39:55.3955 2644 - MIN_MAX_MARKETCAP ---- liquidity = 10496.60$ --> let's buy
02-13 21:39:55.3955 2644 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.1) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-13 21:39:55.3955 2644 - GAS CALCULATION ------ Tx GAS = ...
02-13 21:39:55.3955 2644 - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 5% | SellTax: 10% - Check made in: 0.00251s
-- SWAP DETECTED -----------------------------------------------
02-13 21:39:55.3955 Tx _ID_ from #28: _ID_ - id: 8c84
8c84 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-13 21:39:55.3955 8c84 - TX GAS CONTROL ------- Tx GAS = 53.334507529 and current GAS price = 22.423918703 --> let's continue
02-13 21:39:55.3955 8c84 - MIN_MAX_MARKETCAP ---- liquidity = 10496.60$ --> let's buy
02-13 21:39:55.3955 8c84 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.1) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-13 21:39:55.3955 8c84 - GAS CALCULATION ------ Tx GAS = ...
02-13 21:39:55.3955 8c84 - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 5% | SellTax: 10% - Check made in: 0.00222s
2644 -- COPY SWAP ---------------------------------------------------
02-13 21:39:55.3955 2644 - BUY Tx - Novus Ordo Seclorum - _ID_ - Case 1 - Swap sent in: 0.02456s
2644 -- CONTROLS AFTER Tx -------------------------------------------
8c84 -- COPY SWAP ---------------------------------------------------
02-13 21:39:55.3955 8c84 - BUY Tx - Novus Ordo Seclorum - _ID_ - Case 1 - Swap sent in: 0.01972s```
[REQUEST] cooldown blocks for WH
Functions which act as wait time since buy block until finally activates autosell functions.
COOLDOWN BLOCKS = 3
It should wait 3 entire blocks (since buy block) to activate autosells.
By default, set it to 0.
New Feature - Was it really a honeypot?
It would be really helpful if the bot could keep track of the coins that were initially labeled as honeypots BUT where the tracked wallet was still able to sell them later on. This would indicate that the coin wasn't a honeypot after all.
This feature would be useful for tweaking strategies. For example, if the tracked wallet is profitable at buying and selling coins that were initially detected to be "honeypots," then the user could decide to disable the honeypot protection mechanism. Disabling the honeypot protection in this case would be desirable because they are overall making profits.
Specifically, I’m thinking WH could display a message indicating that coin originally labeled as a "honeypot" has been successfully sold.
It would be even nicer if the TX log could display a message that the tracked wallet sold a honeypot coin and for how much profit.
(I know the TX wallet is pretty much only for coins that the user bought, but for analysis purposes, I think this would be a great feature).
[Bug] Colors in console for price not reflecting the state
I assume red is supposed to be for loss, and green for profit, but it changes depend on increase or decrease.
[New method] Tranaction
Could you add copying for such transactions?
https://etherscan.io/tx/0x000df739fc90b05d35f0d1411f0cce3c68b1d8e91078e52449d986f2f689dc19
-- SWAP DETECTED -----------------------------------------------
02-15 16:21:06.216 Tx 0x000df739fc90b05d35f0d1411f0cce3c68b1d8e91078e52449d986f2f689dc19 from #1: 0x9834D13b34D91a68Ec912b58C0F84C1745cd42Cf - id: dc19
02-15 16:21:06.216 dc19 - This kind of Tx is not clonable by WalletHunter yet. Please check below:
------------------- Tx DATA ANALYSIS -------------------
0xd5a3928b00000000000000000000000000000000000000000000bba2e235056ae98f380b00000000000000000000000000000000000000000000000000000000000001000000000000000000000000009834d13b34d91a68ec912b58c0f84c1745cd42cf000000000000000000000000
0000000000000000000000000000000063ecfbe58c5c0a0888aaccb68c0923b4e2653a44e54f0994d77b1b05292cc98c0d54a7c100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000160000000000000000000000000315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2000000000000000000000000315e
16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a0000000000000000000000000000000000000000000000000000000000000000
02-15 16:21:06.216 You will find below the Tx data decrypted:
02-15 16:21:06.216 Please check inside every line, and search for useful information (token address / amount)
02-15 16:21:06.216 --> if you find those infos, it can be sniped on same Block: contact @TsarBuig
02-15 16:21:06.216 [0] 00000000000000000000000000000000000000000000bba2e235056ae98f380b --> 8.860872047769477e+23
02-15 16:21:06.216 [1] 0000000000000000000000000000000000000000000000000000000000000100 --> 256
02-15 16:21:06.216 [2] 0000000000000000000000009834d13b34d91a68ec912b58c0f84c1745cd42cf --> 0x9834d13b34d91a68ec912b58c0f84c1745cd42cf
02-15 16:21:06.216 [3] 0000000000000000000000000000000000000000000000000000000063ecfbe5 --> 1676475365
02-15 16:21:06.216 [4] 8c5c0a0888aaccb68c0923b4e2653a44e54f0994d77b1b05292cc98c0d54a7c1 --> 0xe2653a44e54f0994d77b1b05292cc98c0d54a7c1
02-15 16:21:06.216 [5] 0000000000000000000000000000000000000000000000000000000000000000 --> 0
02-15 16:21:06.216 [6] 0000000000000000000000000000000000000000000000000000000000000160 --> 352
02-15 16:21:06.216 [7] 000000000000000000000000315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a --> 0x315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a
02-15 16:21:06.216 [8] 0000000000000000000000000000000000000000000000000000000000000002 --> 2
02-15 16:21:06.216 [9] 000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 --> 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
02-15 16:21:06.216 [10] 000000000000000000000000315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a --> 0x315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a
02-15 16:21:06.216 [11] 0000000000000000000000000000000000000000000000000000000000000000 --> 0
----------------------- ORIGINAL TX -----------------------
{
hash: '0x000df739fc90b05d35f0d1411f0cce3c68b1d8e91078e52449d986f2f689dc19',
type: 2,
accessList: [],
blockHash: null,
blockNumber: null,
transactionIndex: null,
confirmations: 0,
from: '0x9834D13b34D91a68Ec912b58C0F84C1745cd42Cf',
gasPrice: BigNumber { _hex: '0x0df0e73f7c', _isBigNumber: true },
maxPriorityFeePerGas: BigNumber { _hex: '0x1051874f', _isBigNumber: true },
maxFeePerGas: BigNumber { _hex: '0x0df0e73f7c', _isBigNumber: true },
gasLimit: BigNumber { _hex: '0x04fc77', _isBigNumber: true },
to: '0x590a7cC27d9607C03085f725ac6B85Ac9EF85967',
value: BigNumber { _hex: '0x02c68af0bb140000', _isBigNumber: true },
nonce: 495,
data: '0xd5a3928b00000000000000000000000000000000000000000000bba2e235056ae98f380b00000000000000000000000000000000000000000000000000000000000001000000000000000000000000009834d13b34d91a68ec912b58c0f84c1745cd42cf000000000000000
0000000000000000000000000000000000000000063ecfbe58c5c0a0888aaccb68c0923b4e2653a44e54f0994d77b1b05292cc98c0d54a7c100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000160000000000000000000000000315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc20000000000000000000
00000315e16cbb544d0dc2ab9bc164e61fbe7aeaf8f3a0000000000000000000000000000000000000000000000000000000000000000',
r: '0x152671ca767c8c54076ad6aef111b513f73ecb79c4dfb1425acac9ebce88fdc2',
s: '0x4d3e4d58eec29db7838ea8be6e14fb2a572a68e108d4b6029b28b6dadb271b65',
v: 1,
creates: null,
chainId: 1,
wait: [Function (anonymous)]
}
---------------------- /ORIGINAL TX -----------------------
Tx = 0x000df739fc90b05d35f0d1411f0cce3c68b1d8e91078e52449d986f2f689dc19
[Bug] MINIMAL_MARKETCAP error
01-31 00:08:14.814 Tx 0xc3268108a89aeafb9241912cca93d217b688186214c42e949c1464affd62a2a7 from #8: 0xcf289AD73A0ca09916aD10f2b9B6fC56e60F3EfE - id: a2a7
a2a7 -- PRE-CHECKS BEFORE Tx ----------------------------------------
01-31 00:08:14.814 a2a7 - TX GAS CONTROL ------- Tx GAS = 19.663946214 and current GAS price = 18.061984913 --> let's continue
01-31 00:08:14.814 a2a7 - MINIMAL_MARKETCAP ---- Error --> please report it to Tsarbuig
01-31 00:08:14.814 undefined
Error: missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"from":"0x53DC3A7021A5e0a5286ee66163C7CcbFB373Ca8C","to":"0x7a250d5630B4cF
539739dF2C5dAcb4c659F2488D","data":"0xd06ca61f0000000000000000000000000000000000000000000000000000000005f5e1000000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000000200000000000
0000000000000718a28c2e5bf6943424740d278111b20472ad52c000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2","accessList":null}, error={"code":-32000,"response":"{\"jsonrpc\":\"2.0\",\"id\":588043,\"error\":{\"code\":-32000,\"message\":\"e
xecution reverted\"}}\n"}, code=CALL_EXCEPTION, version=providers/5.7.2)
at Logger.makeError (/snapshot/WalletHunterJs/node_modules/@ethersproject/logger/lib/index.js:238:21)
at Logger.throwError (/snapshot/WalletHunterJs/node_modules/@ethersproject/logger/lib/index.js:247:20)
at checkError (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:108:16)
at WebSocketProvider.<anonymous> (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:751:47)
at step (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:48:23)
at Object.throw (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:29:53)
at rejected (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/json-rpc-provider.js:21:65)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
reason: 'missing revert data in call exception; Transaction reverted without a reason string',
code: 'CALL_EXCEPTION',
data: '0x',
transaction: {
from: '0x53DC3A7021A5e0a5286ee66163C7CcbFB373Ca8C',
to: '0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D',
data: '0xd06ca61f0000000000000000000000000000000000000000000000000000000005f5e10000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000002000000000000000000000000718a28c2e5bf
6943424740d278111b20472ad52c000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2',
accessList: null
},
error: Error: execution reverted
at WebSocket.<anonymous> (/snapshot/WalletHunterJs/node_modules/@ethersproject/providers/lib/websocket-provider.js:133:33)
at WebSocket.onMessage (/snapshot/WalletHunterJs/node_modules/ws/lib/event-target.js:132:16)
at WebSocket.emit (node:events:527:28)
at Receiver.receiverOnMessage (/snapshot/WalletHunterJs/node_modules/ws/lib/websocket.js:834:20)
at Receiver.emit (node:events:527:28)
at Receiver.dataMessage (/snapshot/WalletHunterJs/node_modules/ws/lib/receiver.js:437:14)
at Receiver.getData (/snapshot/WalletHunterJs/node_modules/ws/lib/receiver.js:367:17)
at Receiver.startLoop (/snapshot/WalletHunterJs/node_modules/ws/lib/receiver.js:143:22)
at Receiver._write (/snapshot/WalletHunterJs/node_modules/ws/lib/receiver.js:78:10)
at writeOrBuffer (node:internal/streams/writable:389:12) {
code: -32000,
response: '{"jsonrpc":"2.0","id":588043,"error":{"code":-32000,"message":"execution reverted"}}\n'
},
level: 'info',
timestamp: '01-31 00:08:14.814',
[Symbol(level)]: 'info',
[Symbol(message)]: '01-31 00:08:14.814 missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ] (data="0x", transaction={"from":"0x53DC3A7021A5e0a5286ee66163C7Cc
bFB373Ca8C","to":"0x7a250d5630B4cF539739dF2C5dAcb4c659F2488D","data":"0xd06ca61f0000000000000000000000000000000000000000000000000000000005f5e100000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000
00000000000000000000002000000000000000000000000718a28c2e5bf6943424740d278111b20472ad52c000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2","accessList":null}, error={"code":-32000,"response":"{\\"jsonrpc\\":\\"2.0\\",\\"id\\":588043,\\
"error\\":{\\"code\\":-32000,\\"message\\":\\"execution reverted\\"}}\\n"}, code=CALL_EXCEPTION, version=providers/5.7.2)'
}
01-31 00:08:14.814 a2a7 - AMOUNT CONTROL ------- WARNING : this must be a Sniping Tx, cannot calculate precisely BNB value --> let's use tx.value
01-31 00:08:14.814 a2a7 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.075) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
01-31 00:08:14.814 a2a7 - GAS CALCULATION ------ Tx GAS = 19.663946214 --> your Tx GAS = 110% * 19.663946214 = 21.630340835
[Feature] Info in console if there's not enough ETH
It appears that there's no info in console about not enough WETH.
Swaps below haven't had ID and wasn't processed.
-- SWAP DETECTED -----------------------------------------------
02-13 12:43:51.4351 Tx TX_ID - id: 0a4d
-- SWAP DETECTED -----------------------------------------------
02-13 12:44:14.4414 Tx TX_ID - id: 813e
02-13 12:44:14.4414 813e - This Tx is an approval Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-13 12:48:35.4835 Tx TX_ID - id: be42
I had it for another swap:
BALANCE CHECK -------- Your wallet hold 0 of token Wrapped Ether --> not enough to make BUY order --> let's stop here
[Feature] Follow Flashbots mined TX
Since we can't follow Flashbot mempool, we could follow mined one by reliable and fast API, or node data if possible.
There are wallets using hidden mempool, but doing nice profits.
People following them by hand, so the advantage would be huge.
[Error] TypeError: Cannot read properties of undefined (reading 'tx_log_id')
Valentine C Price (eb5b): 0.000000020087 | Sell Tax 53% > MAX TAX | Price after Tax 0.000000009440873246 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 75.9%
02-12 13:02:11.211 ----- ERROR : more details below -----
02-12 13:02:11.211 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:02:11.211 ----- Reason -----
02-12 13:02:11.211 undefined
02-12 13:02:11.211 ----- ERROR : more details below -----
02-12 13:02:11.211 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:02:11.211 ----- Reason -----
02-12 13:02:11.211 undefined
Valentine C Price (eb5b): 0.000000021568 | Sell Tax 54% > MAX TAX | Price after Tax 0.000000009921235234 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 84.8%
Valentine C Price (eb5b): 0.000000021174 | Sell Tax 53% > MAX TAX | Price after Tax 0.000000009951883080 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 85.4%
Valentine C Price (eb5b): 0.000000021549 | Sell Tax 54% > MAX TAX | Price after Tax 0.000000009912487025 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 84.7%
Valentine C Price (eb5b): 0.000000024504 | Sell Tax 54% > MAX TAX | Price after Tax 0.000000011271697419 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 110.0%
Valentine C Price (eb5b): 0.000000024907 | Sell Tax 54% > MAX TAX | Price after Tax 0.000000011457022568 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: 113.4%
02-12 13:03:29.329 ----- ERROR : more details below -----
02-12 13:03:29.329 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:03:29.329 ----- Reason -----
02-12 13:03:29.329 undefined
02-12 13:03:29.329 ----- ERROR : more details below -----
02-12 13:03:29.329 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:03:29.329 ----- Reason -----
02-12 13:03:29.329 undefined
Valentine C Price (eb5b): 0.000000023028 | Sell Tax 99% > MAX TAX | Price after Tax 0.000000000230277828 | 1st target price 0.000000010736 | Stoploss 0.000000000 | Current profit: -95.7%
02-12 13:04:11.411 ----- ERROR : more details below -----
02-12 13:04:11.411 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:04:11.411 ----- Reason -----
02-12 13:04:11.411 undefined
02-12 13:04:11.411 ----- ERROR : more details below -----
02-12 13:04:11.411 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:04:11.411 ----- Reason -----
02-12 13:04:11.411 undefined
02-12 13:04:35.435 ----- ERROR : more details below -----
02-12 13:04:35.435 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:04:35.435 ----- Reason -----
02-12 13:04:35.435 undefined
02-12 13:04:35.435 ----- ERROR : more details below -----
02-12 13:04:35.435 ----- Unhandled Rejection at -----
Promise {
TypeError: Cannot read properties of undefined (reading 'tx_log_id')
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-12 13:04:35.435 ----- Reason -----
02-12 13:04:35.435 undefined
02-12 13:04:50.450 eb5b - Valentine Corgi Inu 1st SELL TARGET REACHED : current price = 0.000000012895558 --> let's sell 50% of your initial bag! (4218938202538557710918748 tokens)
[Method] This kind of Tx is not clonable by WalletHunter yet
-- SWAP DETECTED ----------------------------------------------- [92/2339]
02-02 20:56:14.5614 Tx 0xea8663b414c38cb8d4af9a5c3b2b2206bec4fc8de9966c14f97f7b05888ab3e3 from #1: 0xA432Dd077bc2cDfEA74d2922d3AC8DCD97337a7A - id: b3e3 [91/2339]
02-02 20:56:14.5614 b3e3 - This kind of Tx is not clonable by WalletHunter yet. Please check below: [90/2339]
[89/2339]
[88/2339]
------------------- Tx DATA ANALYSIS ------------------- [87/2339]
0xa0731f6300000000000000000000000000000000000000000000000000071cf26d93b2ef00000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000a432dd077bc2cdfea74d2922d3ac8dcd97337a7a0000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f248[86/2339]
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000063dc17b600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000[85/2339]
c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2000000000000000000000000ac35035649f9fb372ff13c3ec0e2afadc35936bd [84/2339]
[83/2339]
02-02 20:56:14.5614 You will find below the Tx data decrypted: [82/2339]
02-02 20:56:14.5614 Please check inside every line, and search for useful information (token address / amount) [81/2339]
02-02 20:56:14.5614 --> if you find those infos, it can be sniped on same Block: contact @TsarBuig [80/2339]
[79/2339]
02-02 20:56:14.5614 [0] 00000000000000000000000000000000000000000000000000071cf26d93b2ef --> 2002152383034095 [78/2339]
02-02 20:56:14.5614 [1] 00000000000000000000000000000000000000000000000000000000000000e0 --> 224 [77/2339]
02-02 20:56:14.5614 [2] 000000000000000000000000a432dd077bc2cdfea74d2922d3ac8dcd97337a7a --> 0xa432dd077bc2cdfea74d2922d3ac8dcd97337a7a [76/2339]
02-02 20:56:14.5614 [3] 0000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f2488d --> 0x7a250d5630b4cf539739df2c5dacb4c659f2488d [75/2339]
02-02 20:56:14.5614 [4] 0000000000000000000000000000000000000000000000000000000000000000 --> 0 [74/2339]
02-02 20:56:14.5614 [5] 0000000000000000000000000000000000000000000000000000000063dc17b6 --> 1675368374 [73/2339]
02-02 20:56:14.5614 [6] 0000000000000000000000000000000000000000000000000000000000000000 --> 0 [72/2339]
02-02 20:56:14.5614 [7] 0000000000000000000000000000000000000000000000000000000000000002 --> 2 [71/2339]
02-02 20:56:14.5614 [8] 000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 --> 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 [70/2339]
02-02 20:56:14.5614 [9] 000000000000000000000000ac35035649f9fb372ff13c3ec0e2afadc35936bd --> 0xac35035649f9fb372ff13c3ec0e2afadc35936bd [69/2339]
[68/2339]
----------------------- ORIGINAL TX ----------------------- [67/2339]
{ [66/2339]
hash: '0xea8663b414c38cb8d4af9a5c3b2b2206bec4fc8de9966c14f97f7b05888ab3e3', [65/2339]
type: 2, [64/2339]
accessList: [], [63/2339]
blockHash: null, [62/2339]
blockNumber: null, [61/2339]
transactionIndex: null, [60/2339]
confirmations: 0, [59/2339]
from: '0xA432Dd077bc2cDfEA74d2922d3AC8DCD97337a7A', [58/2339]
gasPrice: BigNumber { _hex: '0x098bca5a00', _isBigNumber: true }, [57/2339]
maxPriorityFeePerGas: BigNumber { _hex: '0xb2d05e00', _isBigNumber: true }, [56/2339]
maxFeePerGas: BigNumber { _hex: '0x098bca5a00', _isBigNumber: true }, [55/2339]
gasLimit: BigNumber { _hex: '0x0b71b0', _isBigNumber: true }, [54/2339]
to: '0x27dE7D1dEbaBBE7f63383F9A81793b3f19438321', [53/2339]
value: BigNumber { _hex: '0x7c585087238004', _isBigNumber: true }, [52/2339]
nonce: 280, [51/2339]
data: '0xa0731f6300000000000000000000000000000000000000000000000000071cf26d93b2ef00000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000a432dd077bc2cdfea74d2922d3ac8dcd97337a7a0000000000000000000000007a250d5630b4cf539739df2c5dacb[50/2339]
8d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000063dc17b600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000[49/2339]
000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2000000000000000000000000ac35035649f9fb372ff13c3ec0e2afadc35936bd', [48/2339]
r: '0xd91f92f2d2435ba7773f669aaaf467236d170ccac1728675da922b7ec1c5cb83', [47/2339]
s: '0x411ec28296d2828622e3f30de1a101dc198a1a3b820b8436500369d2e752eee1', [46/2339]
v: 0, [45/2339]
creates: null, [44/2339]
chainId: 1, [43/2339]
wait: [Function (anonymous)] [42/2339]
} [41/2339]
---------------------- /ORIGINAL TX ----------------------- [40/2339]
[39/2339]
Tx = 0xea8663b414c38cb8d4af9a5c3b2b2206bec4fc8de9966c14f97f7b05888ab3e3 [38/2339]
[37/2339]
[36/2339]
-- SWAP DETECTED ----------------------------------------------- [35/2339]
02-02 20:56:25.5625 Tx 0xbbdc96f2eeec8d9a431f32af51888e69dab3cbe8c31d9b2d2c71e0a50a916158 from #1: 0xA432Dd077bc2cDfEA74d2922d3AC8DCD97337a7A - id: 6158 [34/2339]
02-02 20:56:25.5625 6158 - This Tx is an approval Tx --> ignore [33/2339]
[32/2339]
-- SWAP DETECTED ----------------------------------------------- [31/2339]
02-02 20:57:01.571 Tx 0x0692cf30ff513d27ea728b26a02b3fd492eaa63c1e2aadb99210072104cda4fa from #1: 0xA432Dd077bc2cDfEA74d2922d3AC8DCD97337a7A - id: a4fa [30/2339]
02-02 20:57:01.571 a4fa - This kind of Tx is not clonable by WalletHunter yet. Please check below: [29/2339]
[28/2339]
[27/2339]
------------------- Tx DATA ANALYSIS ------------------- [26/2339]
blockNumber: null,
transactionIndex: null,
confirmations: 0,
from: '0xA432Dd077bc2cDfEA74d2922d3AC8DCD97337a7A',
gasPrice: BigNumber { _hex: '0x091494c600', _isBigNumber: true },
maxPriorityFeePerGas: BigNumber { _hex: '0xb2d05e00', _isBigNumber: true },
maxFeePerGas: BigNumber { _hex: '0x091494c600', _isBigNumber: true },
gasLimit: BigNumber { _hex: '0x0b71b0', _isBigNumber: true },
to: '0x27dE7D1dEbaBBE7f63383F9A81793b3f19438321',
value: BigNumber { _hex: '0x8e1bc9bf040000', _isBigNumber: true },
nonce: 282,
data: '0xa0731f630000000000000000000000000000000000000000000000000007ac67ea3079b800000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000a432dd077bc2cdfea74d2922d3ac8dcd97337a7a0000000000000000000000007a250d5630b4cf539739df2c5dacb4c659f2488d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000063dc17e500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2000000000000000000000000ac35035649f9fb372ff13c3ec0e2afadc35936bd',
r: '0xaba70717e1dd517b09512f67a5e86c96c5dffaefa423b5808198e3fd40c7ecd9',
s: '0x285ba5534637ffab9127fc567d9d5c1d82247ea17a8dec51b91a9b679706cc55',
v: 1,
creates: null,
chainId: 1,
wait: [Function (anonymous)]
}
---------------------- /ORIGINAL TX -----------------------
Tx = 0x0692cf30ff513d27ea728b26a02b3fd492eaa63c1e2aadb99210072104cda4fa
Missing TXs in logs
I have observed that certain coins purchased by tracked wallet are not appearing in the my logs (or even output in the terminal).
Normally, WH would either copy the purchase or print a reason why we cannot purchase it.
In this case, there is no record of these coins in the logs or screen output.
It is as if these purchases were not registered or "seen" by WH.
======================================================
The coins that were purchased but did not show up in the logs were:
$ETHGI
https://etherscan.io/address/0x0cdcccdfdded233e29113959833a2793be0be9fa
$SCOUT
https://etherscan.io/address/0xd0e48f71fbc5c2358e0d30d991985bf7392d9824
[Bug] AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP not working properly
v0.49.7b
AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP set to 3, but bot stopped buying after one TX.
Connected to uniswap
02-18 04:48:38.4838 You are running version : v0.49.7
02-18 04:48:38.4838 Latest release on Github : v0.49.7
-- WH WHITELIST CHECK ------------------------------------------
Current WalletHunter tokens balance = 100
You hold enough tokens --> let's go!!
-- LET'S HUNT --------------------------------------------------
02-18 04:48:39.4839 Let's hunt wallet(s) [...]
02-18 04:48:39.4839 - BUY_AMOUNT = same_as_tx --> you will buy same amount as hunted wallets: if he buys 1000 tokens you'll buy 1000 tokens
02-18 04:48:39.4839 - SELL_AMOUNT= same_strategy --> you will copy hunted wallet's sell strategy: if he sells 10% of his bag, you will sell 10% of your bag too
02-18 04:48:39.4839 - Tx_GAS BUY = 150% --> you will use 150% of GAS used by hunted wallet: if he uses GAS = 100 you will use GAS = 150
02-18 04:48:39.4839 - Tx_GAS SELL= 150% --> you will use 150% of GAS used by hunted wallet: if he uses GAS = 100 you will use GAS = 150
-- SWAP DETECTED -----------------------------------------------
02-18 05:17:12.1712 TX ID #62 ADDRESS: a7b5
02-18 05:17:12.1712 a7b5 - This Tx is an approval Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-18 05:17:44.1744 TX ID #62 ADDRESS: 2d17
2d17 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 05:17:44.1744 2d17 - TX GAS CONTROL ------- Tx GAS = 30.934014397 and current GAS price = 20.622676265 --> let's continue
02-18 05:17:44.1744 2d17 - BALANCE CHECK -------- Your wallet hold 0 of token ZkTsunami --> not enough to make SELL order --> let's stop here
-- SWAP DETECTED -----------------------------------------------
02-18 05:18:26.1826 TX ID #62 ADDRESS: 2f28
02-18 05:18:26.1826 2f28 - This Tx is an approval Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-18 05:19:05.195 TX ID #62 ADDRESS: 17d4
17d4 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 05:19:05.195 17d4 - TX GAS CONTROL ------- Tx GAS = 33.289022985 and current GAS price = 22.769981492 --> let's continue
02-18 05:19:05.195 17d4 - BALANCE CHECK -------- Your wallet hold 0 of token The BET --> not enough to make SELL order --> let's stop here
-- SWAP DETECTED -----------------------------------------------
02-18 05:35:46.3546 TX ID #60 ADDRESS: 98e3
02-18 05:35:46.3546 98e3 - This Tx is a Transfer Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-18 08:41:32.4132 TX ID #39 ADDRESS: 6e41
02-18 08:41:32.4132 6e41 - This Tx is a Transfer Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-18 08:49:55.4955 TX ID #55 ADDRESS: 12f8
02-18 08:49:55.4955 12f8 - This kind of Tx is not clonable by WalletHunter yet. Please check below:
------------------- Tx DATA ANALYSIS -------------------
TX ID
02-18 08:49:55.4955 You will find below the Tx data decrypted:
02-18 08:49:55.4955 Please check inside every line, and search for useful information (token address / amount)
02-18 08:49:55.4955 --> if you find those infos, it can be sniped on same Block: contact @TsarBuig
02-18 08:49:55.4955 [0] 00000000000000000000000000000000000000000000000004db732547630000 --> 350000000000000000
----------------------- ORIGINAL TX -----------------------
{
hash: '-',
type: 2,
accessList: [],
blockHash: null,
blockNumber: null,
transactionIndex: null,
confirmations: 0,
from: '-',
gasPrice: BigNumber { _hex: '0x0800ef351a', _isBigNumber: true },
maxPriorityFeePerGas: BigNumber { _hex: '0x3b9aca00', _isBigNumber: true },
maxFeePerGas: BigNumber { _hex: '0x0800ef351a', _isBigNumber: true },
gasLimit: BigNumber { _hex: '0x8caf', _isBigNumber: true },
to: '-',
value: BigNumber { _hex: '0x00', _isBigNumber: true },
nonce: 125,
data: '-',
r: '-',
s: '-',
v: 1,
creates: null,
chainId: 1,
wait: [Function (anonymous)]
}
---------------------- /ORIGINAL TX -----------------------
Tx = -
-- SWAP DETECTED -----------------------------------------------
02-18 08:54:57.5457 TX ID #7 ADDRESS: ef53
ef53 -- PRE-CHECKS BEFORE Tx ----------------------------------------
-- SWAP DETECTED -----------------------------------------------
02-18 08:54:57.5457 TX ID #7 ADDRESS: 23a7
23a7 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 08:54:57.5457 ef53 - TX GAS CONTROL ------- Tx GAS = 120 and current GAS price = 25.348921229 --> let's continue
02-18 08:54:57.5457 23a7 - TX GAS CONTROL ------- Tx GAS = 34.912426224 and current GAS price = 25.348921229 --> let's continue
02-18 08:54:57.5457 ef53 - MINIMAL_MARKETCAP ---- Cannot be calculated because we're in same block as AddLiquidity Tx... price is not defined yet
02-18 08:54:57.5457 23a7 - MINIMAL_MARKETCAP ---- Cannot be calculated because we're in same block as AddLiquidity Tx... price is not defined yet
02-18 08:54:57.5457 ef53 - AMOUNT CONTROL ------- WARNING : this must be a Sniping Tx, cannot calculate precisely BNB value --> let's use tx.value
02-18 08:54:57.5457 ef53 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.085) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-18 08:54:57.5457 ef53 - GAS CALCULATION ------ Tx GAS = 120 --> your Tx GAS = 150% * 120 = 180
02-18 08:54:57.5457 23a7 - AMOUNT CONTROL ------- WARNING : this must be a Sniping Tx, cannot calculate precisely BNB value --> let's use tx.value
02-18 08:54:57.5457 23a7 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.085) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-18 08:54:57.5457 23a7 - GAS CALCULATION ------ Tx GAS = 34.912426224 --> your Tx GAS = 150% * 34.912426224 = 52.368639336
02-18 08:54:57.5457 ef53 - HONEYPOT / TAX CHECK - Honeypot: true | BuyTax: NaN% | SellTax: NaN% - Check made in: 0.00167s
02-18 08:54:57.5457 ef53 --> HONEYPOT DETECTED --> buy cancelled.
02-18 08:54:57.5457 23a7 - HONEYPOT / TAX CHECK - Honeypot: true | BuyTax: NaN% | SellTax: NaN% - Check made in: 0.00120s
02-18 08:54:57.5457 23a7 --> HONEYPOT DETECTED --> buy cancelled.
-- SWAP DETECTED -----------------------------------------------
02-18 08:55:53.5553 TX ID #19 ADDRESS: cb93
02-18 08:55:53.5553 cb93 - This Tx is an approval Tx --> ignore
-- SWAP DETECTED -----------------------------------------------
02-18 08:56:28.5628 TX ID #19 ADDRESS: c7ca
02-18 08:56:28.5628 c7ca - NEW - This is a Uniswap Universal Tx with Command: 0a080c --> let's try to clone it
-------------- DEBUG ----------------
amountIn = 144836901208726150000000
amountOutMin= 27657374398348092
path lenght = 2
path = -,-
-------------- /DEBUG ----------------
c7ca -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 08:56:28.5628 c7ca - TX GAS CONTROL ------- Tx GAS = 44.187662045 and current GAS price = 25.68559679 --> let's continue
02-18 08:56:28.5628 c7ca - BALANCE CHECK -------- Your wallet hold 0 of token Novus Ordo Seclorum --> not enough to make SELL order --> let's stop here
-- SWAP DETECTED -----------------------------------------------
02-18 09:01:06.16 TX ID #46 ADDRESS: 756b
02-18 09:01:06.16 756b - NEW - This is a Uniswap Universal Tx with Command: 0b0800 --> let's try to clone it
756b -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-18 09:01:06.16 756b - TX GAS CONTROL ------- Tx GAS = 46.68 and current GAS price = 30.051091211 --> let's continue
02-18 09:01:06.16 756b - MIN_MAX_MARKETCAP ---- liquidity = 14028.43$ --> let's buy
02-18 09:01:06.16 756b - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.1) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-18 09:01:06.16 756b - GAS CALCULATION ------ Tx GAS = 46.68 --> your Tx GAS = 150% * 46.68 = 70.02
02-18 09:01:06.16 756b - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 0% | SellTax: 0% - Check made in: 0.00183s
756b -- COPY SWAP ---------------------------------------------------
02-18 09:01:06.16 756b - BUY Tx - amogus - TX ID - Case 1 - Swap sent in: 0.02135s
756b -- CONTROLS AFTER Tx -------------------------------------------
02-18 09:01:12.112 756b - BUY PRICE ----------- You used 0.100000000000 Wrapped Ether to buy 10217138.938317941502 amogus --> Buy price = 0.000000009787 Wrapped Ether/amogus
02-18 09:01:12.112 756b - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (18 position before)
02-18 09:01:12.112 756b - BALANCE CHECK -------- Your ETH balance is: 1.861154086897004134
02-18 09:01:12.112 756b - TOKEN APPROVAL ------- Token amogus needs approval --> let's approve
02-18 09:01:36.136 756b - amogus approval Tx: TX ID
756b -- ANTI RUG ----------------------------------------------------
02-18 09:01:36.136 756b ANTIRUG -------------- Anti rug-pull method starts for token amogus
02-18 09:01:37.137 756b GET CONTRACT --------- amogus contract is open source --> we will be able to offer you good protection
756b -- AUTO SELL ---------------------------------------------------
02-18 09:01:38.138 756b - AUTO SELL VALUES ----- amogus | Buy price (including fees) 0.000000009787476 | Stoploss (0%) 0.000000000000000 | Current Sell Tax 0%
02-18 09:01:38.138 756b - AUTO SELL VALUES ----- amogus | 1st target price 0.000000019574952 --> will sell 50% of your initial bag (5108569469158970511529411 tokens)
02-18 09:01:38.138 756b - AUTO SELL VALUES ----- amogus | 2nd target price 0.000000978649704 --> will sell 50% of your initial bag (5108569469158970511529411 tokens)
amogus Price (756b): 0.000000008845 | Sell Tax 0% < Max Tax (60%) | Price after Tax 0.000000008845203938 | 1st target price 0.000000019575 | Stoploss 0.000000000 | Current profit: -9.6%
-- SWAP DETECTED -----------------------------------------------
02-18 09:01:43.143 TX ID #46 ADDRESS: 5d6c
02-18 09:01:43.143 5d6c - NEW - This is a Uniswap Universal Tx with Command: 0b0800 --> let's try to clone it
02-18 09:01:43.143 5d6c - SHOULD WE CONTINUE? -- BUY Tx made in a row = 3 | AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP parameter = 3 --> cancel BUY
[Bug] Cannot read properties of undefined (reading '0')
02-05 15:38:17.3817 Tx 0x21e13d1aa8e7e5ecf49e960118080f6dff4ee20af45239d37cd455e0c6d8c4d5 from #13: 0x084c5e9073D680f3014d01b73D6659D2912F3285 - id: c4d5
02-05 15:38:17.3817 NEW - This is a Uniswap Universal Tx with Command: 0a080c --> let's try to clone it
02-05 15:38:17.3817 ----- ERROR : more details below -----
02-05 15:38:17.3817 ----- Unhandled Rejection at -----
Promise {
<rejected> TypeError: Cannot read properties of undefined (reading '0')
at DecodeTx (/snapshot/WalletHunterJs/WalletHunter.js)
at /snapshot/WalletHunterJs/WalletHunter.js
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
}
02-05 15:38:17.3817 ----- Reason -----
02-05 15:38:17.3817 undefined
“buy_and_sell_and_autosell” mode - clarification on Tx_GAS_FOR_SELL
Let's assume: Tx_GAS_FOR_SELL: '130%'
Normally, in “buy_and_sell” mode this would take the tracked wallet’s gas * 130%
But in “buy_and_sell_and_autosell” mode, if the sell happens through an “autosell”, what gas does it use to calculate that?
I think “BOOST” would work better for an autosell because it takes market gas * PERCENTAGE.
But the problem is we don’t know if the sale will be triggered by (A) the tracked wallet or (B) an autosell.
How do we solve this problem?
[Feature] Autosell based on mempool
A switch MAX_PRICE_DROP, which based on mempool, if trigger, would sell a coin, before TX is mined.
This may prevent us from sudden price drop by front running it.
[Bug] MAX_SELL_TAX didn't trigger after trade started
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
-- SWAP DETECTED -----------------------------------------------
02-07 20:02:32.232 Tx [...]
3ec3 -- PRE-CHECKS BEFORE Tx ----------------------------------------
02-07 20:02:32.232 3ec3 - TX GAS CONTROL ------- Tx GAS = 63.858947421 and current GAS price = 41.466767433 --> let's continue
02-07 20:02:32.232 3ec3 - MIN_MAX_MARKETCAP ---- liquidity = 5347.72$ --> let's buy
02-07 20:02:32.232 3ec3 - AMOUNT CONTROL ------- MINIMUM_BUY_AMOUNT_IN_BASE (0.012) <= your buyAmount (0.05) <= MAXIMUM_BUY_AMOUNT_IN_BASE (0.1) --> let's buy
02-07 20:02:32.232 3ec3 - GAS CALCULATION ------ Tx GAS =
02-07 20:02:32.232 3ec3 - HONEYPOT / TAX CHECK - Honeypot: false | BuyTax: 0% | SellTax: 1% - Check made in: 0.00195s
3ec3 -- COPY SWAP ---------------------------------------------------
02-07 20:02:32.232 3ec3 - BUY Tx - LOCKER AI - [...]
3ec3 -- CONTROLS AFTER Tx -------------------------------------------
02-07 20:02:36.236 3ec3 - BUY PRICE ----------- You used X Wrapped Ether to buy X LOCKER AI --> Buy price = 0.000000003384 Wrapped Ether/LOCKER AI
02-07 20:02:36.236 3ec3 - SAME BLOCK ? --------- Swap block: X/ Your Tx block: X--> CONGRATS!! Your Tx was in the same block :)
02-07 20:02:36.236 3ec3 - POSITION IN BLOCK ---- FRONTRUN : you managed to frontrun the original Tx :) (8 position before)
02-07 20:02:36.236 3ec3 - BALANCE CHECK -------- Your ETH balance is: X
02-07 20:02:36.236 3ec3 - TOKEN APPROVAL ------- Token LOCKER AI needs approval --> let's approve
02-07 20:02:50.250 3ec3 - LOCKER AI approval Tx: [...]
3ec3 -- ANTI RUG ----------------------------------------------------
02-07 20:02:50.250 3ec3 - SHOULD WE CONTINUE? -- BUY Tx made in a row = 1 | AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP parameter = 10 --> let's continue
- ANTI RUG ------------- MelodyMoney balance = X
02-07 20:02:50.250 3ec3 ANTIRUG -------------- Anti rug-pull method starts for token LOCKER AI
- ANTI RUG ------------- Grow AI balance = X
02-07 20:02:50.250 - ANTI RUG FINAL LIST -- Anti rug-pull method starts for token
02-07 20:02:50.250 - LIQUIDITY REMOVAL ---- We will sell if more than 30% of liquidity is removed
02-07 20:02:50.250 - OTHER RUG METHODS ---- We will also check for Sell Allowance / Blacklisting / Trading Status / Cooldown changes
02-07 20:02:50.250 3ec3 GET CONTRACT --------- LOCKER AI contract is open source --> we will be able to offer you good protection
[Bug] AMOUNT_OF_BUY_TX_BEFORE_THE_BOT_STOP not working properly
Bot stopped buying before it made the defined amount.
Maybe it counts something different that successfully completed TX, like attempts or detected one?
Please double-check the process.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.