👨‍🔧How does TradeEye work?

TradeEye Discord Bot for finding the best settings for crypto signal groups Telegram and Discord.

TradeEye Access

To Access TradeEye Beta testing version, you need to join the PumpBot server and activate your subscription (you need at least the PumpBot Starter Role).

After you have done that, you can message bot: TradeEye v1.0.1 (Beta) in private dm with the command .setup (dot (.) is a prefix and it is required for the bot recognize commands).

How it works

1 . Message the bot by typing .setup command in message field and hit 'Enter'.

.setup

TradeEye Discord Bot

1. TradeEye will reply with a message that looks like this below. TradeEye will also send you a the settings file for the signals backtesting group.

TradeEye: License check for the access

1. Download the .json file and send it back to TradeEye. Just send the file in the chat Discord Bot chat. Uploaded settings will be used for the analysis with TradeEye (to get more information about TradeEye configuration file see the next page).

TradeEye: settings file upload

1. That is it! Now you can start the TradeEye using .start command and you will receive the overall channel performance and detailed log about each trade analysed by TradeEye.

.start

TradeEye: results from the analysis

1. Likewise if you want to try other or different configurations just upload the settings file again, changes will take effect on next usage of .start command.

Note: TradeEye for backtesting crypto signal groups

TradeEye is in testing phase. If you notice any inaccuracy please contact the developers via PumpBot Discord ticket system or Jacked Mort#1220.

Time needed for analysing a channel will vary, ranging between 1 to 30 minutes (depending on settings and demand on TradeEye). If you don't get results after about 30 minutes, try again. If it still doesn't work and you didnt receive any result in given timeframe (1 to 30 minutes) please contact us. Reason for this could be many: might be because of incorrect settings configuration, demand overload, internal bug or something else.