Adds notifications via telegram bot.

Configuration is handled with the usual config file.

~~Configuration is done via environment variables.~~

~~I have another PR to allow config via env vars #17 which i hope can be merged. Then i would unify configuration for telegram as well.~~

This makes the buy and sell blocks event driven, so that we attempt to buy immediately after hearing the announcement, and then sell once we're done buying.

I also made the config values global, since I figured that it makes sense for them to be global and I figured it would be the easiest way to get those values to the buy block.

~~I decided to leave the sell block in the main thread. It has to keep a sleeper anyway, since it does api requests to learn the current sale price.~~

This is based on ~~#62~~ master

~~The only way I've tested the Threading.Event.Wait() func is through the ctrl-c functionality. I'm confident it will work, based on the buy_ready event triggered log message coming when I expect after hitting ctrl-c, but it has not been tested with a real announcement.~~ It still hasn't been tested with a real announcement, but it works with a fake announcement.

I get this error when running script from main.py

I am on Windows 10 running Python through Visual Studio Code. I configured auth.yml file and config.yml file, all correctly. I also installed all requirements. I am not a programmer, so excuse me if this is a newbie error. :D

Since the size of the log file can be MASSIVE very quickly, it would be better to split them into several files and place them into a seperate folder.

With this change, log files are now split into daily files which means that there will be a log file for every day beginning on midnight. Also, the logs will now be placed into a seperate folder called "logs" with a date appendix.

This PR allows to read config data from environment variables.

This is in preparation for another PR to run inside docker and allow configuration via docker-compose.

Also, this is my first PR ever, so let me know if there are any issues.

This PR addresses issues regarding rate limiting by using a socks5 rotating proxy derived from a list of proxies fetched from proxyscan.io. May fix #137 and #115 Main issue is proxy quality, some of them are slow or not working.

TODO:

• [x] Proxy checker
• [x] Add option for configuring through config.yml

The bot is using incorrect price values (possibly) from the response of Gate.io spot orders API payload.
Not sure what we can do about this. It's simply wrong info. The price returned doesn't even match what they show on their website for your trade order history.

Real Example: I had the bot purchase a new listing coin on gate.io called ZLK.
The purchase went through and I had an order closed (and filled 100%). The order id is 97094620091. It's real. it's in the books.
But... The bot recorded the response to the spot order with a price of 7.
The gateio website shows a filled price of 6.10. The bot determined it bought a volume of 49.9999998 (config set to 50) at an amount of 7.14285714 at a price of 7. The gateio website shows a volume of 43.571428554 at an amount of 7.14285714 at a price of 6.10. Interesting, huh? If I GET the order by id (GET /spot/orders/{order_id}), it shows an price of 7. Even a request by order id returns the wrong price amount. How can this be, Gateio? How can your website have a different price than your orders endpoint?

The outcome of the bot says I lost -12%. But it was using an incorrect price. I actually lost less than 1% (it was $0.90 USDT). 2021-11-25 11:00:21,708 INFO: Sold ZLK with -0.9 profit | -12.857% PNL

• Gate.io website trade history:

• Session data from the buy

• API GET to orders/[id]

I'm not sure there is anything we can do about this. It's a gate.io issue really.

I can also add to ignore exclusions = ['Futures', 'Margin', 'adds', 'Adds'] But right now it should look after matches in brackets with regex '\(([^)]+)' i.e. Binance will add () it will extract

# python3 main.py
Traceback (most recent call last):
  File "main.py", line 1, in <module>
    from gateio_new_coins_announcements_bot.main import main
ModuleNotFoundError: No module named 'gateio_new_coins_announcements_bot'

Hello.

@CyberPunkMetalHead

I sold it manually because I saw that the stop loss was not working at all

My config.yml:

---
  TRADE_OPTIONS:
    # In your pairing coin
    QUANTITY: 5
    # BTCUSDT will be bought for example
    PAIRING: USDT
    TEST: False
    # In %
    SL: -3
    TP: 60
    ENABLE_TSL: True
    TSL: -4
    TTP: 20
  LOGGING:
    # Logging levels used in this program are ERROR, INFO, and DEBUG
    LOG_LEVEL: INFO
    LOG_FILE: bot.log

2021-11-04 10:04:14,384 INFO: last_price='242.061'
2021-11-04 10:04:14,384 INFO: stored_price + (stored_price*sl /100)=242.5
2021-11-04 10:04:14,384 INFO: starting sell place_order with :BNX | USDT | 295.31442 | side=sell 242.061
2021-11-04 10:04:14,680 ERROR: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Date': 'Thu, 04 Nov 2021 07:04:14 GMT', 'Content-Type': 'application/json', 'Content-Length': '61', 'Connection': 'keep-alive', 'Server': 'openresty', 'X-Request-Id': '[48530729-1567413425]'})
HTTP response body: {"label":"BALANCE_NOT_ENOUGH","message":"Not enough balance"}

2021-11-04 10:04:14,681 ERROR: (400)
Reason: Bad Request
HTTP response headers: HTTPHeaderDict({'Date': 'Thu, 04 Nov 2021 07:04:14 GMT', 'Content-Type': 'application/json', 'Content-Length': '61', 'Connection': 'keep-alive', 'Server': 'openresty', 'X-Request-Id': '[48530729-1567413425]'})
HTTP response body: {"label":"BALANCE_NOT_ENOUGH","message":"Not enough balance"}

I'm getting a TypeError from the 'Order' object wich is returned by Gate.io Api.

Traceback (most recent call last): File "E:/Entwicklung/binanceListingTradingbot/main.py", line 63, in main stored_price = float(order[coin]['price']) TypeError: 'Order' object is not subscriptable

Hi,

Describe the bug Should the telegram notifications be working currently with the latest master? I followed the instructions, running the bot in Docker, but not getting any telegram related logs or notifications.

To Reproduce Steps to reproduce the behavior:

~> cat config.yml
...
  TELEGRAM:
    # set to True to enable telegram notifications
    ENABLED: True
    # Disable / Enable specific notifications
    NOTIFICATIONS:
      STARTUP: True 
...
~>
cat auth.yml
  telegram_token: "yxz"
  telegram_chat_id: "123"
...

Expected behavior Telegram notifications showing up / Log Entries in INFO or DEBUG mode

regards, strowi

Hi. I´m having problems with kucoin's announcements. My gate.io wallet have 0.41 ETH and I set 0.39 ETH in bot´s config file.

2022-06-27 07:04:01,834 INFO: New announcement detected: CSPR 2022-06-27 07:04:03,249 INFO: LATEST TRADE: CSPR_ETH | id=3753869116 | create_time=27-06-22 10:02:50.232000 | side=sell | amount=4071.9 | price=2.5e-05 2022-06-27 07:04:03,249 INFO: starting buy place_order with : announcement_coin='CSPR' | globals.pairing='ETH' | volume=0.39 | amount=15600.0 x price='2.5e-05' | side = buy | status='test_partial_fill_order' 2022-06-27 07:04:03,599 ERROR: (400) Reason: Bad Request HTTP response headers: HTTPHeaderDict({'Date': 'Mon, 27 Jun 2022 10:04:04 GMT', 'Content-Type': 'application/json', 'Content-Length': '92', 'Connection': 'keep-alive', 'Server': 'openresty', 'X-Request-Id': '[f1bf83ab-2436108246]'}) HTTP response body: {"label":"INVALID_PARAM_VALUE","message":"Invalid request parameter price value: 2.5e-05"}

2022-06-27 07:04:03,599 ERROR: (400) Reason: Bad Request HTTP response headers: HTTPHeaderDict({'Date': 'Mon, 27 Jun 2022 10:04:04 GMT', 'Content-Type': 'application/json', 'Content-Length': '92', 'Connection': 'keep-alive', 'Server': 'openresty', 'X-Request-Id': '[f1bf83ab-2436108246]'}) HTTP response body: {"label":"INVALID_PARAM_VALUE","message":"Invalid request parameter price value: 2.5e-05"}

2022-06-27 07:04:05,294 INFO: Kucoin announcements enabled, look for new Kucoin coins... 2022-06-27 07:04:05,889 INFO: Checking for coin announcements every 3 seconds (in a separate thread) 2022-06-27 07:04:06,614 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating 2022-06-27 07:04:09,339 INFO: Kucoin announcements enabled, look for new Kucoin coins...

The latest coin announcement bump is very weak and might be non existent soon:

2022-05-09 08:57:42,349 INFO: LATEST TRADE: LDO_USDT | id=3441486742 | create_time=09-05-22 06:57:34.157000 | side=buy | amount=11.769 | price=3.208
2022-05-09 08:57:42,351 INFO: {'_fee_currency': 'LDO', '_price': '3.208', '_amount': '4.675810473815461', '_time': 1652079462.351539, '_tp': 2, '_sl': -3, '_ttp': 2, '_tsl': -4, '_id': 'test-order', '_text': 'test-order', '_create_time': 1652079462.35155, '_update_time': 1652079462.351552, '_currency_pair': 'LDO_USDT', '_status': 'cancelled', '_type': 'limit', '_account': 'spot', '_side': 'buy', '_iceberg': '0', '_left': '3.0860349127182043', '_fee': '0.0031795511221945133'}
2022-05-09 08:57:45,589 INFO: LATEST TRADE: LDO_USDT | id=3441487113 | create_time=09-05-22 06:57:38.848000 | side=sell | amount=6.238 | price=3.1864
2022-05-09 08:57:45,590 INFO: {'_fee_currency': 'LDO', '_price': '3.1864', '_amount': '3.1069545568666834', '_time': 1652079465.590204, '_tp': 2, '_sl': -3, '_ttp': 2, '_tsl': -4, '_id': 'test-order', '_text': 'test-order', '_create_time': 1652079465.590211, '_update_time': 1652079465.590213, '_currency_pair': 'LDO_USDT', '_status': 'closed', '_type': 'limit', '_account': 'spot', '_side': 'buy', '_iceberg': '0', '_left': '0', '_fee': '0.006213909113733367'}
2022-05-09 08:57:45,832 INFO: LATEST TRADE: LDO_USDT | id=3441487113 | create_time=09-05-22 06:57:38.848000 | side=sell | amount=6.238 | price=3.1864
2022-05-09 08:57:49,074 INFO: LATEST TRADE: LDO_USDT | id=3441488131 | create_time=09-05-22 06:57:47.323000 | side=sell | amount=427.699 | price=3.2469
2022-05-09 08:57:52,771 INFO: LATEST TRADE: LDO_USDT | id=3441488131 | create_time=09-05-22 06:57:47.323000 | side=sell | amount=427.699 | price=3.2469
2022-05-09 08:57:56,235 INFO: LATEST TRADE: LDO_USDT | id=3441489053 | create_time=09-05-22 06:57:55.327000 | side=sell | amount=20.72 | price=3.35
2022-05-09 08:57:59,474 INFO: LATEST TRADE: LDO_USDT | id=3441489346 | create_time=09-05-22 06:57:58.513000 | side=sell | amount=17.591 | price=3.375
2022-05-09 08:58:03,398 INFO: LATEST TRADE: LDO_USDT | id=3441489346 | create_time=09-05-22 06:57:58.513000 | side=sell | amount=17.591 | price=3.375
2022-05-09 08:58:06,634 INFO: LATEST TRADE: LDO_USDT | id=3441489346 | create_time=09-05-22 06:57:58.513000 | side=sell | amount=17.591 | price=3.375
2022-05-09 08:58:09,875 INFO: LATEST TRADE: LDO_USDT | id=3441489462 | create_time=09-05-22 06:57:59.631000 | side=sell | amount=20.72 | price=3.375
2022-05-09 08:58:13,106 INFO: LATEST TRADE: LDO_USDT | id=3441490057 | create_time=09-05-22 06:58:06.230000 | side=sell | amount=20.72 | price=3.3949
2022-05-09 08:58:16,338 INFO: LATEST TRADE: LDO_USDT | id=3441490057 | create_time=09-05-22 06:58:06.230000 | side=sell | amount=20.72 | price=3.3949
2022-05-09 08:58:19,571 INFO: LATEST TRADE: LDO_USDT | id=3441490922 | create_time=09-05-22 06:58:18.217000 | side=buy | amount=0.929 | price=3.4921
2022-05-09 08:58:22,806 INFO: LATEST TRADE: LDO_USDT | id=3441490922 | create_time=09-05-22 06:58:18.217000 | side=buy | amount=0.929 | price=3.4921
2022-05-09 08:58:26,040 INFO: LATEST TRADE: LDO_USDT | id=3441490922 | create_time=09-05-22 06:58:18.217000 | side=buy | amount=0.929 | price=3.4921
2022-05-09 08:58:29,277 INFO: LATEST TRADE: LDO_USDT | id=3441491886 | create_time=09-05-22 06:58:28.114000 | side=buy | amount=3.4 | price=3.4921
2022-05-09 08:58:32,758 INFO: LATEST TRADE: LDO_USDT | id=3441492034 | create_time=09-05-22 06:58:31.731000 | side=buy | amount=28.30844951 | price=3.51
2022-05-09 08:58:35,995 INFO: LATEST TRADE: LDO_USDT | id=3441492174 | create_time=09-05-22 06:58:35.306000 | side=sell | amount=3.185 | price=3.4885
2022-05-09 08:58:39,227 INFO: LATEST TRADE: LDO_USDT | id=3441492333 | create_time=09-05-22 06:58:38.871000 | side=sell | amount=39 | price=3.53
2022-05-09 08:58:42,458 INFO: LATEST TRADE: LDO_USDT | id=3441492344 | create_time=09-05-22 06:58:39.171000 | side=buy | amount=235.259 | price=3.54
2022-05-09 08:58:45,690 INFO: LATEST TRADE: LDO_USDT | id=3441492344 | create_time=09-05-22 06:58:39.171000 | side=buy | amount=235.259 | price=3.54
2022-05-09 08:58:48,921 INFO: LATEST TRADE: LDO_USDT | id=3441492344 | create_time=09-05-22 06:58:39.171000 | side=buy | amount=235.259 | price=3.54
2022-05-09 08:58:52,167 INFO: LATEST TRADE: LDO_USDT | id=3441492784 | create_time=09-05-22 06:58:48.166000 | side=sell | amount=78.70318 | price=3.55
2022-05-09 08:58:55,400 INFO: LATEST TRADE: LDO_USDT | id=3441493396 | create_time=09-05-22 06:58:54.983000 | side=sell | amount=599.98463 | price=3.5526
2022-05-09 08:58:58,632 INFO: LATEST TRADE: LDO_USDT | id=3441493396 | create_time=09-05-22 06:58:54.983000 | side=sell | amount=599.98463 | price=3.5526
2022-05-09 08:59:02,094 INFO: LATEST TRADE: LDO_USDT | id=3441493396 | create_time=09-05-22 06:58:54.983000 | side=sell | amount=599.98463 | price=3.5526
2022-05-09 08:59:05,329 INFO: LATEST TRADE: LDO_USDT | id=3441493396 | create_time=09-05-22 06:58:54.983000 | side=sell | amount=599.98463 | price=3.5526
2022-05-09 08:59:08,562 INFO: LATEST TRADE: LDO_USDT | id=3441494547 | create_time=09-05-22 06:59:06.127000 | side=buy | amount=0.896 | price=3.58
2022-05-09 08:59:12,024 INFO: LATEST TRADE: LDO_USDT | id=3441494949 | create_time=09-05-22 06:59:10.784000 | side=sell | amount=2.449755 | price=3.5948
2022-05-09 08:59:15,258 INFO: LATEST TRADE: LDO_USDT | id=3441495272 | create_time=09-05-22 06:59:14.500000 | side=sell | amount=41.91 | price=3.5947
2022-05-09 08:59:18,492 INFO: LATEST TRADE: LDO_USDT | id=3441495506 | create_time=09-05-22 06:59:17.791000 | side=buy | amount=6950.69 | price=3.6
2022-05-09 08:59:21,727 INFO: LATEST TRADE: LDO_USDT | id=3441495639 | create_time=09-05-22 06:59:19.523000 | side=buy | amount=2094.591 | price=3.6
2022-05-09 08:59:25,925 INFO: LATEST TRADE: LDO_USDT | id=3441495639 | create_time=09-05-22 06:59:19.523000 | side=buy | amount=2094.591 | price=3.6
2022-05-09 08:59:29,159 INFO: LATEST TRADE: LDO_USDT | id=3441496023 | create_time=09-05-22 06:59:23.585000 | side=sell | amount=0.099 | price=3.5999
2022-05-09 08:59:32,390 INFO: LATEST TRADE: LDO_USDT | id=3441496454 | create_time=09-05-22 06:59:29.385000 | side=buy | amount=91.73294584 | price=3.61
2022-05-09 08:59:35,624 INFO: LATEST TRADE: LDO_USDT | id=3441496511 | create_time=09-05-22 06:59:30.580000 | side=sell | amount=2.711 | price=3.5764
2022-05-09 08:59:38,860 INFO: LATEST TRADE: LDO_USDT | id=3441496982 | create_time=09-05-22 06:59:34.483000 | side=sell | amount=1574.301 | price=3.5768
2022-05-09 08:59:42,095 INFO: LATEST TRADE: LDO_USDT | id=3441497667 | create_time=09-05-22 06:59:41.551000 | side=sell | amount=44.707 | price=3.6
2022-05-09 08:59:47,419 INFO: LATEST TRADE: LDO_USDT | id=3441497756 | create_time=09-05-22 06:59:42.220000 | side=sell | amount=5.61699 | price=3.6
2022-05-09 08:59:50,652 INFO: LATEST TRADE: LDO_USDT | id=3441498671 | create_time=09-05-22 06:59:49.309000 | side=buy | amount=54.52193584 | price=3.615
2022-05-09 08:59:53,888 INFO: LATEST TRADE: LDO_USDT | id=3441498907 | create_time=09-05-22 06:59:52.086000 | side=buy | amount=27.388 | price=3.615
2022-05-09 08:59:57,595 INFO: LATEST TRADE: LDO_USDT | id=3441498907 | create_time=09-05-22 06:59:52.086000 | side=buy | amount=27.388 | price=3.615
2022-05-09 09:00:00,837 INFO: LATEST TRADE: LDO_USDT | id=3441499551 | create_time=09-05-22 06:59:59.517000 | side=sell | amount=611.99 | price=3.555
2022-05-09 09:00:04,067 INFO: LATEST TRADE: LDO_USDT | id=3441499551 | create_time=09-05-22 06:59:59.517000 | side=sell | amount=611.99 | price=3.555
2022-05-09 09:00:07,299 INFO: LATEST TRADE: LDO_USDT | id=3441499760 | create_time=09-05-22 07:00:02.681000 | side=sell | amount=52.576 | price=3.555
2022-05-09 09:00:10,531 INFO: LATEST TRADE: LDO_USDT | id=3441499878 | create_time=09-05-22 07:00:04.221000 | side=buy | amount=1172.852119 | price=3.57
2022-05-09 09:00:13,763 INFO: LATEST TRADE: LDO_USDT | id=3441500296 | create_time=09-05-22 07:00:10.438000 | side=buy | amount=1793.77413709 | price=3.3332
 {'symbol': 'LDO', 'price': '3.3332', 'volume': '4.69673011796394', 'time': 1652079613.765893, 'profit': '0.14680000000000026', 'relative_profit_%': '4.607080090384141%', 'id': 'test-order', 'text': 'test-order', 'create_time': 1652079613.765936, 'update_time': 1652079613.765942, 'currency_pair': 'LDO_USDT', 'status': 'closed', 'type': 'limit', 'account': 'spot', 'side': 'sell', 'iceberg': '0'}

I tested the announcement API for a few weeks and I noticed that the API data is always delayed than the real releaseDate of the announcement.

So I tried to use proxies to pretend the request from different countries, like the USA, Canada, Singapore, Japan, and I found the latency is different for each country.

The fastest I can reach is about 15s now, and I don't know how to improve it.

And I recently found every notification of announcement is delayed than before, like telegram, binance windows client and etc

So, I guess the binance did something with the API, it was done deliberately by the binance programmers so that a narrow circle of people could react to the news faster than everyone else.

Any idea of this and how to improve it?

https://github.com/CyberPunkMetalHead/gateio-crypto-trading-bot-binance-announcements-new-coins/blob/180763fa167ede0a7534d485a3c4c7b3030b43ec/src/gateio_new_coins_announcements_bot/trade_client.py#L22-L23

I had USDC as my preferred pairing in the last WOO anouncement. Gate.io, however, only makes USDT_WOO and ETH_WOO pairings available. This assert line caused the following error:

{"log":"Traceback (most recent call last):\n","stream":"stderr","time":"2022-02-08T02:20:56.351154707Z"}
{"log":"  File \"/usr/local/lib/python3.9/threading.py\", line 973, in _bootstrap_inner\n","stream":"stderr","time":"2022-02-08T02:20:56.351189051Z"}
{"log":"    self.run()\n","stream":"stderr","time":"2022-02-08T02:20:56.352852517Z"}
{"log":"  File \"/usr/local/lib/python3.9/threading.py\", line 910, in run\n","stream":"stderr","time":"2022-02-08T02:20:56.352999854Z"}
{"log":"    self._target(*self._args, **self._kwargs)\n","stream":"stderr","time":"2022-02-08T02:20:56.353485095Z"}
{"log":"  File \"/src/gateio_new_coins_announcements_bot/main.py\", line 79, in buy\n","stream":"stderr","time":"2022-02-08T02:20:56.353712756Z"}
{"log":"    obj = get_last_price(announcement_coin, globals.pairing, False)\n","stream":"stderr","time":"2022-02-08T02:20:56.353996537Z"}
{"log":"  File \"/src/gateio_new_coins_announcements_bot/trade_client.py\", line 23, in get_last_price\n","stream":"stderr","time":"2022-02-08T02:20:56.354121108Z"}
{"log":"    assert len(trades) == 1\n","stream":"stderr","time":"2022-02-08T02:20:56.354310747Z"}
{"log":"AssertionError\n","stream":"stderr","time":"2022-02-08T02:20:56.354449017Z"}

I would suggest having an if check and a good log message instead of an assert here, so that people don't have to look into code like I did. :)

A new option CUSTOM_PROXIES in the configs to provide a list of custom proxies (e.g. premium proxies you bought).

We should then also add an option USE_PROXYSCAN_PROXIES to enable/disable proxies from the proxyscan.io api, if someone only wants to use his own premium proxies. If no custom proxies are provided and the USE_PROXYSCAN_PROXIES option is disabled it should default to using no proxy.