The "EMASkipPump" strategy is designed to avoid pump and dump market conditions. It utilizes a combination of technical indicators to make buying and selling decisions. Here is a breakdown of how the strategy works:
The strategy uses three Exponential Moving Averages (EMAs) with different time periods: a short-term EMA (5 periods), a medium-term EMA (12 periods), and a long-term EMA (21 periods).
It also calculates Bollinger Bands using the typical price and a window of 20 periods with 2 standard deviations.
The strategy calculates the minimum and maximum values of the closing price over a medium-term EMA period.
During the "populate_buy_trend" phase: It identifies potential buy signals based on the following conditions: The volume is less than 20 times the 30-day rolling average volume. The closing price is below both the short-term EMA and the medium-term EMA. The closing price is equal to the minimum value calculated over the medium-term EMA period. The closing price is less than or equal to the lower Bollinger Band. During the "populate_sell_trend" phase: It identifies potential sell signals based on the following conditions: The closing price is above both the short-term EMA and the medium-term EMA. The closing price is greater than or equal to the maximum value calculated over the medium-term EMA period. The closing price is greater than or equal to the upper Bollinger Band. Additionally, the strategy has defined a minimal return on investment (ROI) and a stop-loss value: The minimal_roi dictionary specifies the minimum desired ROI at different sell points. For example, at the sell point "0", a minimum ROI of 0.2 (20%) is expected. The stoploss attribute defines the optimal stop-loss value for the strategy, which is set to -0.1 (-10%) by default. The ticker_interval attribute specifies the optimal ticker interval for the strategy, which is set to '5m' (5 minutes) by default. Overall, the strategy aims to identify potential buying opportunities when the market shows signs of avoiding pump and dump scenarios and sell when specific criteria are met based on the EMAs, Bollinger Bands, and other indicators.
It also calculates Bollinger Bands using the typical price and a window of 20 periods with 2 standard deviations.
The strategy calculates the minimum and maximum values of the closing price over a medium-term EMA period.
During the "populate_buy_trend" phase: It identifies potential buy signals based on the following conditions: The volume is less than 20 times the 30-day rolling average volume. The closing price is below both the short-term EMA and the medium-term EMA. The closing price is equal to the minimum value calculated over the medium-term EMA period. The closing price is less than or equal to the lower Bollinger Band. During the "populate_sell_trend" phase: It identifies potential sell signals based on the following conditions: The closing price is above both the short-term EMA and the medium-term EMA. The closing price is greater than or equal to the maximum value calculated over the medium-term EMA period. The closing price is greater than or equal to the upper Bollinger Band. Additionally, the strategy has defined a minimal return on investment (ROI) and a stop-loss value: The minimal_roi dictionary specifies the minimum desired ROI at different sell points. For example, at the sell point "0", a minimum ROI of 0.2 (20%) is expected. The stoploss attribute defines the optimal stop-loss value for the strategy, which is set to -0.1 (-10%) by default. The ticker_interval attribute specifies the optimal ticker interval for the strategy, which is set to '5m' (5 minutes) by default. Overall, the strategy aims to identify potential buying opportunities when the market shows signs of avoiding pump and dump scenarios and sell when specific criteria are met based on the EMAs, Bollinger Bands, and other indicators.
Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 467, in _make_request self._validate_conn(conn) File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 1099, in _validate_conn conn.connect() File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connection.py", line 653, in connect sock_and_verified = _ssl_wrap_socket_and_match_hostname( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connection.py", line 806, in _ssl_wrap_socket_and_match_hostname ssl_sock = ssl_wrap_socket( ^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/ssl_.py", line 465, in ssl_wrap_socket ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/ssl_.py", line 509, in _ssl_wrap_socket_impl return ssl_context.wrap_socket(sock, server_hostname=server_hostname) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/ssl.py", line 517, in wrap_socket return self.sslsocket_class._create( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/ssl.py", line 1104, in _create self.do_handshake() File "/usr/local/lib/python3.11/ssl.py", line 1382, in do_handshake self._sslobj.do_handshake() TimeoutError: _ssl.c:989: The handshake operation timed out The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/requests/adapters.py", line 486, in send resp = conn.urlopen( ^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 847, in urlopen retries = retries.increment( ^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/retry.py", line 470, in increment raise reraise(type(error), error, _stacktrace) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/util/util.py", line 39, in reraise raise value File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 793, in urlopen response = self._make_request( ^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 491, in _make_request raise new_e File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 469, in _make_request self._raise_timeout(err=e, url=url, timeout_value=conn.timeout) File "/home/ftuser/.local/lib/python3.11/site-packages/urllib3/connectionpool.py", line 370, in _raise_timeout raise ReadTimeoutError( urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10.0) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 598, in fetch response = self.session.request( ^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/sessions.py", line 589, in request resp = self.send(prep, **send_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/sessions.py", line 703, in send r = adapter.send(request, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/requests/adapters.py", line 532, in send raise ReadTimeout(e, request=request) requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='api.binance.com', port=443): Read timed out. (read timeout=10.0) The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/freqtrade/freqtrade/exchange/exchange.py", line 486, in _load_markets self._markets = self._api.load_markets(params={}) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 1474, in load_markets markets = self.fetch_markets(params) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/binance.py", line 2734, in fetch_markets promisesRaw.append(self.publicGetExchangeInfo(params)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/types.py", line 34, in unbound_method return _self.request(self.path, self.api, self.method, params, config=self.config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/binance.py", line 10089, in request response = self.fetch2(path, api, method, params, headers, body, config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 3523, in fetch2 return self.fetch(request['url'], request['method'], request['headers'], request['body']) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/ftuser/.local/lib/python3.11/site-packages/ccxt/base/exchange.py", line 628, in fetch raise RequestTimeout(details) from e ccxt.base.errors.RequestTimeout: binance GET https://api.binance.com/api/v3/exchangeInfo
stoploss: -0.1 timeframe: 5m hash(sha256): d0f58c73c9ad5981600270c4c1b6ce7740bb8dba418628c6d927e69844b719cf indicators: min upper mid lower volume bb_middleband close bb_upperband bb_lowerband max
No similar strategies found. (based on used indicators)
last change: 2024-07-28 21:26:18