Todo:

• Create the Breaker Block indicator [Maybe other indicators will be useful]
• Create every indicator output as classes
• Create a possibility to return non-visual (numeric) data
• Add tests for this
• Create a possibility to enable/disable indicators
• Connect the bot to database (probably local), to store the user_ids and their preferences
• Possibility to calculate indicators only on demand
• Add tests for this
• Create a logic to find predictable movements, based on the created indicators
• Tune this logic properly
• Add tests for this
• Don't count very small FVGs
• Impove handling the cases where some indicators are not shown (Covered FVGs in text representation)
• Tune order block detection - Important
• Keep previous 1000 candles in history and send signal based on the extended analysis (probably multi-frame) - done in another way (merging requests responses)
• Create a logic regarding pinging users about signals
• Add tests for this
• Check if a requested cryptocurrency pair exists on a Bybit (suggest the correct name using Levenstein distance) - not important
• Refactor obsolete function for 1k candles, put the logic into the basic function
• Create a signal finding pipeline
• Tune the signal finding logic
• Create an adequate UI for managing signals
• Prevent from creating a multiple signal queries for the same currency
• Possibility to choose whether we need a chart along with the signal using query setting
• Clarify the exception message for this use-case: '/create_signal ARBUSDT 1 2'
• Possibility to apply only chosen indicators to signals
• Limit frequency of signals and amount of signals to not violate the API limits
• If possible, make the bot to continue sending signals after it is restarted
• Create a neural network and make it learn on own data
• Integrate a neural network to the predictions system
• Prettify the bot and make it easy to use