cryptognome/lickhunterpro

Cryptocurrency Trading Bot that looks for large pools of liquidity getting liquidated on margin trading, when it finds these it counter trades them!

Liquidation Hunter counter trades liquidations along with VWAP offsets on all trading pairs on Binance. You can run multiple trading pairs on the same exchange with more than one bot ant the base currency is USDT.

NEW VERISON v4 for Bybit Here:

https://github.com/CryptoGnome/Bybit-Lick-Hunter-v4

Current Supported Exchanges

Binance Futures

Bybit

Bybit- USDT VERSION HERE

Made with <3 with @ccxt

https://github.com/ccxt/ccxt

---

Read the wiki here to get started:

WiKi

Disclamers:

This program has been made in connection with Bybit’s Affiliate Program. Utilizing the following referral link may result in a commission to us.

ANY results are based on simulated or hypothetical performance results that have certain inherent limitations. Unlike the results shown in an actual performance record, these results do not represent actual trading. Also, because these trades have not actually been executed, these results may have under-or over-compensated for the impact, if any, of certain market factors, such as lack of liquidity. Simulated or hypothetical trading programs in general are also subject to the fact that they are designed with the benefit of hindsight. No representation is being made that any account will or is likely to achieve profits or losses similar to these being shown.

TRADING LEVERAGE IS HIGH RISK PLEASE DYOR

lickhunterpro's Issues

Source code?

Is there any source code to this bot or do I have to trust you blindly, that this isn't a complete mess?

Stop loss not working

Not sure if it's fixed but in alpha 0.52 stop loss didn't work.

https://cdn.discordapp.com/attachments/704578798200422411/750293243429912626/unknown.png

"ret_code":20006,"ret_msg":"symbol is not in the range of selected"

Keep getting this error everytimes the bot try to make a trade.

Fetch Ticker Called
Current VWAP Value: 348.99064766488215
Take Longs Below: 342.01
Take Shorts Above: 355.97
Ticker Last: 356.1
Fetching Account Balance
Current Balance: 1.4247785 ETH
Auto Calculate Size Used, Order size = 3.0442
Max Position Size = 3044.1817431
Check Positions Called
Checking Direction
No Open Positions Found
No Position for ETHUSDT
Current PNL % 0
SHORT ORDER CALLED
Setting Leverage ETH/USD 6
bybit {"ret_code":20006,"ret_msg":"symbol is not in the range of selected","ext_code":"","result":null,"ext_info":null,"time_now":"1601856470.186249","rate_limit_status":74,"rate_limit_reset_ms":1601856470208,"rate_limit":75}
Starting Loop...
Launching Liquidation Websocket...
Release unicorn-binance-websocket-api_1.21.0 is available, please consider updating! (Changelog: https://github.com/oliver-zehentleitner/unicorn-binance-websocket-api/blob/master/CHANGELOG.md)

bybit {"ret_code":20006,"ret_msg":"symbol is not in the range of selected","ext_code":"","result":null,"ext_info":null,"time_now":"1601615152.485359","rate_limit_status":71,"rate_limit_reset_ms":1601615152492,"rate_limit":75}

Currently running settings and the wallet have 2.8 ETH as balance.

`chooseExchange = 'bybit'

pairs = ['ETHUSDT']

percentBal = 0.4
maxPosition = 100

dcaOne = 3
factorOne = 2
dcatwo = 5
factorTwo = 8

long_vwap_offset = 2.5
short_vwap_offset = 2.5

leverage = 5

lick_value = 500

take_profit = 0.38
stop_loss = 20`

Feature enhancement to negate editing bat files and copying settings.py

Edit the change directory command in all bats to reference current working directory this is for v1.6
cd .\Binance\binanceProfit for profits bats
cd .\Binance\binanceWebsocket for websocket bats
then it doesn't really matter where its extracted too and cuts out having to edit 4 files. 😄

for creating symlinks for settings.py
Create a bat file that runs from the current working directory where all the other bats are located :
mklink /H .\Binance\binanceWebsocket\settings.py .\settings.py
mklink /H .\Binance\binanceProfit\settings.py .\settings.py

Adjustable log level and multiple log files

I would like to see two enhancements. At the moment the logging is not quite good at all. It would be much better if you could adjust the logging level and if there would be one log file per day. The adjustment could be thru the settings file and/or a start argument.
It makes it much more organized.

Buy orders mixed between PB and DCA amounts (double spending)

Noticed that the bot will open more PB amount buys when a liq comes as well as a DCAONE amount buy mixed together.
https://cdn.discordapp.com/attachments/685258964266647564/798936921496879154/Screenshot_20210113_152955.jpg

My balance is 4707$, pb is 0.07 and dcaOne is 0.5, with factorOne 2. dcaTwo is 1.75 and factorTwo is 4.

No TP/SL added to orders on Binance

The orders posted by the bot do not have TP and SL on Binance.

For the settings I used:
leverage = 5
take_profit = 0.25
stop_loss = 20
percentBal = 0.5
maxPosition = 40

Version 1.75: No webhook for long liquidation

At the current moment, when there is long liquidation event. The bot no longer show webhook for long liquidation. It work fine on short liquidation. Checking websocket error log nothing found related to websocket error.

The same issue also have been reported in channel by "Crypto Monkey"

Can not establish a connection with MongoDB

Hi, i am ItsMacro from Discord group

when starting websocket, i get this error. Log file attached, the only thing i could see is that i can not seem to find pip install through 'pip --version'
Though i installed pip in every single way with even path variable, so it is installed fine
The only thing that lasts maybe is my firewall

See attached file
Thanks CG

binanceWebsocket-error.log

pymongo.errors.ServerSelectionTimeoutError

2020-09-02T09:56:49: Traceback (most recent call last):
2020-09-02T09:56:49: File "binanceWebsocket.py", line 291, in
2020-09-02T09:56:49: File "site-packages\pymongo\collection.py", line 1273, in find_one
2020-09-02T09:56:49: File "site-packages\pymongo\cursor.py", line 1156, in next
2020-09-02T09:56:49: File "site-packages\pymongo\cursor.py", line 1050, in _refresh
2020-09-02T09:56:49: File "site-packages\pymongo\mongo_client.py", line 1810, in _ensure_session
2020-09-02T09:56:49: File "site-packages\pymongo\mongo_client.py", line 1763, in __start_session
2020-09-02T09:56:49: File "site-packages\pymongo\mongo_client.py", line 1796, in _get_server_session
2020-09-02T09:56:49: File "site-packages\pymongo\topology.py", line 487, in get_server_session
2020-09-02T09:56:49: File "site-packages\pymongo\topology.py", line 208, in _select_servers_loop
2020-09-02T09:56:49: pymongo.errors.ServerSelectionTimeoutError: SSL handshake failed: cluster0-shard-00-02-rsyek.gcp.mongodb.net:27017: _ssl.c:1091: The handshake operation timed out,SSL handshake failed: cluster0-shard-00-00-rsyek.gcp.mongodb.net:27017: _ssl.c:1091: The handshake operation timed out,SSL handshake failed: cluster0-shard-00-01-rsyek.gcp.mongodb.net:27017: _ssl.c:1091: The handshake operation timed out
2020-09-02T09:56:49: cript binanceWebsocket

feature: more standardized/relative way to define licks (e.g. only licks 10% higher than 12h SMA of licks)

lick value can vary drastically over coins and also over time for the same coin.
but having too low lick is very dangerous, because every lick triggers one buy
implement a more relative way defining lick size e.g. take all licks that are 10% over the 12h moving average of licks

Wrong DCA order size picked

Sometimes the bot pick wrong order size when placing orders.
My DCA settings are:

This all happen on -40% PNL and all orders need to be dcaTwo( x6 size ( 65-66XLM ))
On biger price placing "normal" order after that the price move close to my entry and start placing DCA orders

Here again on biger price normal order after that dcaTwo order

I have a lot more axamples if needed.

Also i know i use LHPC GUI, but this are the active settings from the json file

One more Adition. I notice it happens more when the trade is more than -40-50% PNL.
This is a good example of that. DCA working and suddenly stop working and start placing normal orders.

Multiple Errors, bot sometimes dosnt open any trades but Bot Monitor shows nothing wrong.

So from the Websocketlog I get these:

CRITICAL - 2020-11-12 02:32:51,194 - BinanceWebSocketApiSocket.start_socket(50ea59ee-eed1-4f7d-9d47-1ea95410e43f, ['!forceOrder'], ['{}']) - Exception ConnectionClosed - error_msg: code = 1006 (connection closed abnormally [internal]), no reason
CRITICAL - 2020-11-12 02:32:51,194 - BinanceWebSocketApiManager.stream_is_crashing(50ea59ee-eed1-4f7d-9d47-1ea95410e43f)

And also this one "ERROR - 2020-11-12 06:02:01,646 - binance {"code":-4003,"msg":"Quantity less than zero."}"

and from my Profit log its this:

ERROR - 2020-11-12 06:01:02,639 - binance {"code":-2022,"msg":"ReduceOnly Order is rejected."}

Hope you can help me out :)
binanceProfitError.log
binanceWebsocketError.log

Settings.json not found

Unzipped 1.74 and input keys and values in settings.json. Upon start up I get this error:

This is the the directory structure:

ERROR text for reference:
binanceProfit > File "binanceProfit.py", line 12, in
binanceProfit > FileNotFoundError: [Errno 2] No such file or directory: '../settings.json'
binanceProfit > [888] Failed to execute script binanceProfit

Binance

LH wrongly read lick value for each coin.

LickHunter Version: 1.79

Running just LH bot without any control panel

This is what shown on Websocket Log. As you can see the lick value keep changing.

LINK Lick Value $USD not above Min Value $  4107
Liquidation found for: 10.31 Contracts worth: $ 198.11696000000003 on LINK
LINK Lick Value $USD not above Min Value $  4528
Liquidation found for: 10.31 Contracts worth: $
 198.11696000000003 on LINK
LINK Lick Value $USD not above Min Value $  1496
Liquidation found for: 10.31 Contracts worth: $ 198.11696000000003 on LINK
LINK Lick Value $USD not above Min Value $  859
Liquidation found for: 37.9 Contracts worth: $ 500.1663 on DOT

DOT Lick Value $USD not above Min Value $  4282
Liquidation found for: 37.9 Contracts worth: $ 500.1663 on DOT
DOT Lick Value $USD not above Min Value $  2913
Liquidation found for: 37.9 Contracts worth: $ 500.1663 on DOT

DOT Lick Value $USD not above Min Value $  4313
Liquidation found for: 37.9 Contracts worth: $ 500.1663 on DOT

This is what inside coins.json

{
    "symbol":  "DOT",
    "longoffset":  "3",
    "shortoffset":  "3",
    "lickvalue":  "4282"
},{
    "symbol":  "LINK",
    "longoffset":  "3",
    "shortoffset":  "3",
    "lickvalue":  "4107"
}

Feature Requests - Automated VWAP offset - Multiple Pairs - HODL when inactive

1. Automated VWAP offset changes based on Volatility to enable better, more precise entry points. One might use ADX to automate this.

2. Multiple Pairs being simultaneously watched/traded at the same time. This can increase the amount of liquidations available to be capitalized on. Each asset would have it's own vwap settings and the bot would only catch a single asset's liquidation at a time thus preventing the bot's capital from being spread too thin across multiple assets.

3. The ability to have assets in a HODL trade when vwap is not above or below the offsets instead of USDT. This will enable the bot both capitalize on liquidations whilst simultaneously catching the movements of another long term asset. For instance, I might hold ADA when the bot is in the vwap range and move to USDT when it is above or below the vwap range.

check_licks = False is not working

make false if you want to ignore licks
check_licks = False

Setting above is not working, it's keeps placing orders on licks.

No errors are showing in logs

I'm using 1.6 beta

Bybit lickvalue and VWAP offset not applying

I have a problem with Bybit, I've set lickvalue high (50.000) and the bot buy half of my maxPosition in seconds, neither I´m sure if it´s applying the VWAP offset. I think that it could be because I´ve some errors in my log files and the bot is not reading my settings correctly. I attach my logs so you can see it.
First, I notice that one of my log files generated when I execute the aplication for first time is called binanceprofit, I don´t sure if it is correct but I'm attaching it anyway.

feature: auto-refresh settings when changed (making feeder scripts possible)

bot should automatically reload settings when changed/every minute.
=> you do not need to restart bot when you play with settings
=> it opens up the bot for other people writing scripts modifying the settings based on external factors, e.g. BTC moves big, increase VWAP or auto-remove pumped coins etc. (feeder approach)

Error

Version 1.74 - Bybit dca settings have no effect

I have been testing bybit on version 1.74, the order size (pb), VWAP, TP, etc all work ok for both ETH and BTC (running concurrently on the same bot).

I have noticed that order size does not change regardless of when price exceeds the set dcaone and dcatwo threshold (so it looks like the dca function is not working on bybit), orders reman at 1 x percbal and not multiplied by the relevant factor as expected. This occurred with the below dca settings:

dcaOne = 1
Factorone = 2
dcaTwo = 5
factorTwo = 3

I haven't tried this on binance to confirm whether its a common bug to the bot or just specific to the bybit exchange.

Thanks.

v1.6 running but won't place trades

I downloaded LickHunter Pro v1.6 and installed as per the setup guide. Been running for three days without any trades placed. I've tried running with very low vwap and lick values and high volume pairs just to get some action but to no avail. I have a balance of 334 USDT in my Binance USDT Futures account. Can't figure out why it won't place orders. Only errors are the few lines visible in the binanceProfitError.log file.

binanceProfitError.log

settings.txt

1.72 Issue, binaceProfit not picking up latest pairs from coins.json

It looks like binanceWebsocket is picking up the latest pairs in coins.json, but binanceProfit only uses the pairs it started the process with.

kill switch

Would it possible in a future release to add a kill switch so that the bot would stop automatically under certain conditions in order to avoid account liquidation. Not sure if this request makes sense or not. I realize that the best insurance against getting liquidated is to run with prudent settings. But let's say we think our settings are conservative enough but a really large market swing occurs. Would it be advantageous to be able to set the bot to shutdown or maybe just not open any more positions once the available margin drops below a certain level? After available margin increases past the minimum level then it could resume opening new positions.

Stop loss is broken on Bybit

Looks like stop-loss is broken on Bybit. If necessary I've screened the trade log and position on chart, but probably the following excerpt from the bybitProfit-out.log would be enough:

Check Positions Called
Checking Direction
Entry Price: 1287.58749559
Fetch Take Profit Called
Direction IS Short
Fetch Ticker Called
Ticker Last: 1295.35
Checking For Open Take Profit
Orders Found, Checking More
Take Profit is up to Date Passing.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Stop Loss Triggered - Market Closing Position.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
binance does not have market symbol ETH/USD

Given what the last line says, it seems like it tried to close it but failed (non-migrated code from binance version?)

Websocket memory leak

When the websocket is running the memory usage increases over time:

Here are the logs for both websockets:
binanceWebsocketError.log
binanceWebsocketDaanError.log

400 restarts-runtime 27h

Added error logs of Profit and websocket. Using V1.51

"BinanceWebSocketApiManager->stream_is_crashing(8f1b2b51-68ad-4ad8-b547-0632a7877b43)"

binanceWebsocketError.log
binanceProfitError.log

Binance does not have market symbol BTC/USDT

Out of suddent the bot suddenly not working. Try fresh installation also not work

invalid literal for int() with base 10: '4582.1'

LHP002-profit > 2020-09-24T02:54:10: Check Positions Called
LHP002-profit > 2020-09-24T02:54:10: ALGO/USDT
LHP002-profit > 2020-09-24T02:54:10: Fetch Ticker Called
LHP002-profit > 2020-09-24T02:54:10: Fetch Take Profit Called
LHP002-profit > 2020-09-24T02:54:10: Direction IS LONG
LHP002-profit > 2020-09-24T02:54:10: Cancel TP Orders Called
LHP002-profit > 2020-09-24T02:54:10: Orders Found, Checking More
LHP002-profit > 2020-09-24T02:54:10: invalid literal for int() with base 10: '4582.1'
LHP002-profit > 2020-09-24T02:54:10: Check Positions Called
LHP002-profit > 2020-09-24T02:54:10: ALGO/USDT
LHP002-profit > 2020-09-24T02:54:10: Fetch Ticker Called
LHP002-profit > 2020-09-24T02:54:10: Fetch Take Profit Called
LHP002-profit > 2020-09-24T02:54:10: Direction IS LONG
LHP002-profit > 2020-09-24T02:54:10: Cancel TP Orders Called
LHP002-profit > 2020-09-24T02:54:10: Orders Found, Checking More
LHP002-profit > 2020-09-24T02:54:10: invalid literal for int() with base 10: '4582.1'
LHP002-profit > 2020-09-24T02:54:10: Check Positions Called
LHP002-profit > 2020-09-24T02:54:10: ALGO/USDT
LHP002-profit > 2020-09-24T02:54:10: Fetch Ticker Called
LHP002-profit > 2020-09-24T02:54:10: Fetch Take Profit Called
LHP002-profit > 2020-09-24T02:54:10: Direction IS LONG
LHP002-profit > 2020-09-24T02:54:10: Cancel TP Orders Called
LHP002-profit > 2020-09-24T02:54:10: Orders Found, Checking More
LHP002-profit > 2020-09-24T02:54:10: invalid literal for int() with base 10: '4582.1'

what is the error?

"code":-4061,"msg":"Order's position side does not match user's setting."

Hello,
what can it be?
binance {"code":-4061,"msg":"Order's position side does not match user's setting."}
binanceWebsocket > Starting Loop...
binanceWebsocket > Launching Liquidation Websocket...

percentBal = 0.2
maxPosition = 30
maxOpen = 10

leverage = 10

lick_value = 500

check_licks = False

Regards.

Compile Linux binaries

When I look at the technology which is used, the bot could easily be ported to Linux. That would be more comfortable for a VPS. (Enhancement)

problems with bybit websockets.

bybitWebsocketError.log
bybitWebsocketError.log
After starting the start profit and start websockets, the program runs normally and if i remove the SL, the bot puts again.
the problem is after i whiles start to give some errors in .txt file. and sometimes on bot monitor.

as u can see sometimes it works. but takes a lot of time to show on bot monitor.

i uploaded again the file. because the errors appear again.

1.6 beta error

im getting this error everyday

CRITICAL - 2020-09-11 17:57:30,838 - BinanceWebSocketApiSocket->start_socket(33377b60-8c39-42b4-b08c-d6334646f477, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 17:57:30,839 - BinanceWebSocketApiManager->stream_is_crashing(33377b60-8c39-42b4-b08c-d6334646f477)
CRITICAL - 2020-09-11 18:04:30,888 - BinanceWebSocketApiSocket->start_socket(ec779bad-40c2-476c-916a-f85c9a863e38, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:04:30,893 - BinanceWebSocketApiManager->stream_is_crashing(ec779bad-40c2-476c-916a-f85c9a863e38)
ERROR - 2020-09-11 18:06:51,814 - Invalid URL 'WEBHOOK HERE': No schema supplied. Perhaps you meant http://WEBHOOK HERE?
CRITICAL - 2020-09-11 18:06:54,059 - BinanceWebSocketApiSocket->start_socket(36f3ed95-8702-452b-bc32-b72b061f83fa, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:06:54,065 - BinanceWebSocketApiManager->stream_is_crashing(36f3ed95-8702-452b-bc32-b72b061f83fa)
CRITICAL - 2020-09-11 18:11:29,585 - BinanceWebSocketApiSocket->start_socket(ec779bad-40c2-476c-916a-f85c9a863e38, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:11:29,590 - BinanceWebSocketApiManager->stream_is_crashing(ec779bad-40c2-476c-916a-f85c9a863e38)
CRITICAL - 2020-09-11 18:17:14,977 - BinanceWebSocketApiSocket->start_socket(e512c800-0526-45d7-b1f9-16e4db76489d, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:17:14,983 - BinanceWebSocketApiManager->stream_is_crashing(e512c800-0526-45d7-b1f9-16e4db76489d)
CRITICAL - 2020-09-11 18:18:14,934 - BinanceWebSocketApiSocket->start_socket(317de02a-441a-4587-b65f-e8a389c8786d, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:18:14,940 - BinanceWebSocketApiManager->stream_is_crashing(317de02a-441a-4587-b65f-e8a389c8786d)
CRITICAL - 2020-09-11 18:20:23,369 - BinanceWebSocketApiSocket->start_socket(36f3ed95-8702-452b-bc32-b72b061f83fa, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:20:23,370 - BinanceWebSocketApiManager->stream_is_crashing(36f3ed95-8702-452b-bc32-b72b061f83fa)
CRITICAL - 2020-09-11 18:23:54,413 - BinanceWebSocketApiSocket->start_socket(1baf12bd-1f74-4bfe-8139-da25af9bed24, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:23:54,413 - BinanceWebSocketApiManager->stream_is_crashing(1baf12bd-1f74-4bfe-8139-da25af9bed24)
CRITICAL - 2020-09-11 18:39:28,081 - BinanceWebSocketApiSocket->start_socket(56e11819-f997-437b-ba4f-23ed0abd22d7, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:39:28,082 - BinanceWebSocketApiManager->stream_is_crashing(56e11819-f997-437b-ba4f-23ed0abd22d7)
CRITICAL - 2020-09-11 18:49:45,641 - BinanceWebSocketApiSocket->start_socket(9b105dd8-2cf4-4be5-8786-8a34bde6b75c, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:49:45,642 - BinanceWebSocketApiManager->stream_is_crashing(9b105dd8-2cf4-4be5-8786-8a34bde6b75c)
CRITICAL - 2020-09-11 18:49:45,648 - BinanceWebSocketApiSocket->start_socket(11d5183a-b712-4bc5-a985-1927dcca8443, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:49:45,648 - BinanceWebSocketApiManager->stream_is_crashing(11d5183a-b712-4bc5-a985-1927dcca8443)
CRITICAL - 2020-09-11 18:57:36,890 - BinanceWebSocketApiSocket->start_socket(1baf12bd-1f74-4bfe-8139-da25af9bed24, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 18:57:36,890 - BinanceWebSocketApiManager->stream_is_crashing(1baf12bd-1f74-4bfe-8139-da25af9bed24)
CRITICAL - 2020-09-11 19:04:29,452 - BinanceWebSocketApiSocket->start_socket(1baf12bd-1f74-4bfe-8139-da25af9bed24, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 19:04:29,452 - BinanceWebSocketApiManager->stream_is_crashing(1baf12bd-1f74-4bfe-8139-da25af9bed24)
CRITICAL - 2020-09-11 19:11:28,893 - BinanceWebSocketApiSocket->start_socket(9b105dd8-2cf4-4be5-8786-8a34bde6b75c, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 19:11:28,894 - BinanceWebSocketApiManager->stream_is_crashing(9b105dd8-2cf4-4be5-8786-8a34bde6b75c)
CRITICAL - 2020-09-11 19:18:36,855 - BinanceWebSocketApiSocket->start_socket(9b105dd8-2cf4-4be5-8786-8a34bde6b75c, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 19:18:36,855 - BinanceWebSocketApiManager->stream_is_crashing(9b105dd8-2cf4-4be5-8786-8a34bde6b75c)
CRITICAL - 2020-09-11 19:23:45,643 - BinanceWebSocketApiSocket->start_socket(9b105dd8-2cf4-4be5-8786-8a34bde6b75c, ['!forceOrder'], ['{}']) Exception AttributeError Info: module 'asyncio.base_futures' has no attribute 'InvalidStateError'
CRITICAL - 2020-09-11 19:23:45,644 - BinanceWebSocketApiManager->stream_is_crashing(9b105dd8-2cf4-4be5-8786-8a34bde6b75c)

Bot triggers an order to the opposite direction despite having an open position

I noticed where the bot triggers an order in an opposite direction despite having an open position. This usually occurs when im keeping an open long position for days during a massive dump, the vwap then gets resseted the following day, now if the coin pumps passes the vwap offset, instead of waiting to hit the TP of the long position first, the bot will immediately try to open a short position resulting in settling some of my position with a loss.

1.77 bybitProfix.exe has errors and doesnt set TP orders

websocket works fine. Positions are open but bybitProfit has errors, doesnt set TP and therefore doesnt take profit.

https://i.imgur.com/PPVTWSC.png

I had to manually close the positions. I know of one other member who has the same issues.
Rebooting the machine didnt help.

"Error binance {"code":-2015,"msg":"Invalid API-key, IP, or permission " Where I can see full log?

Where I can see full logs from this tool? I mean log like in the video? With price etc

version 1.8 Trojan:Win32/CryptInject!ml

Trojan:Win32/CryptInject!ml

1.8 is recognized as a virus. Please check again that there are no problems with the file.

binanceWebsocket

binance does not have market symbol

since a couple of hours ago the error log is full of these:

ERROR - 2020-11-10 02:38:48,703 - binance does not have market symbol BTC/USDT
ERROR - 2020-11-10 02:40:09,467 - binance does not have market symbol ETH/USDT
ERROR - 2020-11-10 02:40:11,828 - binance does not have market symbol SXP/USDT
ERROR - 2020-11-10 02:41:38,483 - binance does not have market symbol XTZ/USDT
ERROR - 2020-11-10 02:45:44,516 - binance does not have market symbol SNX/USDT
ERROR - 2020-11-10 02:46:57,515 - binance does not have market symbol ALGO/USDT
ERROR - 2020-11-10 02:47:25,157 - binance does not have market symbol VET/USDT
ERROR - 2020-11-10 02:47:27,468 - binance does not have market symbol BNB/USDT
ERROR - 2020-11-10 02:47:29,156 - binance does not have market symbol XTZ/USDT
ERROR - 2020-11-10 02:47:31,131 - binance does not have market symbol ALGO/USDT
ERROR - 2020-11-10 02:47:34,358 - binance does not have market symbol LINK/USDT
ERROR - 2020-11-10 02:47:39,436 - binance does not have market symbol ETH/USDT
ERROR - 2020-11-10 02:47:45,343 - binance does not have market symbol LINK/USDT
ERROR - 2020-11-10 02:47:55,530 - binance does not have market symbol ETH/USDT
ERROR - 2020-11-10 02:48:01,312 - binance does not have market symbol VET/USDT

Bot not working if coins.json missing from the root folder

Step to produce this. Delete coins.json from the root folder. After that the bot will return coins.json not found even it's in their folder.

v1.6 Bybit Bot "Failed to execute script"

I have installed the bot half a dozen times now thinking maybe I did something wrong, or out of order, etc. I have done it to the spec of the wiki and the video Gnome made. For some reason, after I run the Bot Monitor and start the profit and WebSocket it shows me this error in the bot (see screenshot below). I would post the error log but that isn't working either. It doesn't report anything, it creates the error file but when I open it in notepad it is blank. Also, the file that it creates for Bybit is named BinanceProfitError and BybitWebsocketError instead of it saying BybitProfitError, so it makes me think something is messed up and the bot somewhere along the lines thinks it's connecting to Binance not Bybit. I edited all the executable files and replaced them with the proper directory and file name as seen in the other below screenshots. I copied the settings file over into each folder as well.

I was told numerous times to provide a log file but as you can see below in the screenshots, the error log is improperly named when it is created and there is nothing in it when you open it...

Max Pairs Open at once

Add in the ability to have a maximum number of open positions. Ie I would run with 10 pairs but would only have 2 open at the same time.

bybit {"ret_code":20006,"ret_msg":"symbol is not in the range of selected","ext_code":"","result":null,"ext_info":null,"time_now":"1603982435.117794","rate_limit_status":74,"rate_limit_reset_ms":1603982435180,"rate_limit":75}

I get this error code over and over seems like right when it's going to place an order
bybit {"ret_code":20006,"ret_msg":"symbol is not in the range of selected","ext_code":"","result":null,"ext_info":null,"time_now":"1603982435.117794","rate_limit_status":74,"rate_limit_reset_ms":1603982435180,"rate_limit":75}
there's also some kind of websocket error asking to update websocket api to 1.26.0

Bot crashing

error on v1.51

im getting this error every day

Precentbal per pair

is it possible to have precentbal per pair ? as in a new feature for the bot since i tend to lower my pb for more liquid pairs.
if thats doable would love to see that as a new feature.

Best regards ,

Salty

Version 1.75: Bot do not reload settings.json

Try to change the settings.json while the bot running (Changing leverage, percentBal, Take Profit) and the change do not take effect until the bot is restarted.

Is the behaviour correct?

1.76 don't open orders on ETH ByBit

as you see on screen, when licks occurred bot don't sent orders to open position even if USD value of lick is 4877$ with my LH settings 500$ . VWAP was ok on this level.

The exe files are identified as a trojan by several AV engines

See: https://www.virustotal.com/gui/file/dfb1907815d7158d153b843ad60bd59a12f2e4a52128858abcaa0bb987b482bc/behavior