Bot Options

Authentication

The bot supports to protect the frontend from unauthorised accesses since the bot can be public via the local tunnel.

You can enable the authentication from the configuration.

To activate authentication, you must configure the following environment parameters in the .env file

Environment Key	Description	Sample Value
BINANCE_AUTHENTICATION_ENABLED	Enable/Disable frontend authentication	true
BINANCE_AUTHENTICATION_PASSWORD	Frontend password	123456

And there are extra configurations in the global setting.

• Lock list
• Lock after

If you enable the lock list, then the bot will show the login screen before showing the list. If disable the option for lock list, then the bot will display the coin list and hide all actions until login with a password.

The lock after option will remember the login for the configuration time.

Auto-trigger buy

The bot can automatically place new buy order after selling all the coins. This auto-trigger buy action will be automatically queued and once queue time is expired, then it will place an order.

There are configurations in the global setting.

• Enabled
• Trigger after: The bot will wait for triggering buy based on this config value.
• Conditions
  • Re-schedule when the current price is over ATH restriction: The bot will reschedule the auto-trigger buy action until the current price is under the ATH restriction price.
  • Re-schedule when the action is disabled: The bot will reschedule the auto-trigger by action if the symbol is disabled.
• TradingView
  • Override interval: Override TradingView interval while attempting auto-trigger buy. If set, then the bot will monitor TradingView as the configured interval when auto-trigger buy is active until the buy order is executed.
  • Allow auto-buy trigger when the recommendation is Strong buy: When TradingView recommendation is not Strong buy, the bot will reschedule the auto-trigger buy action.
  • Allow auto-buy trigger when the recommendation is Buy: When TradingView recommendation is not Buy, the bot will reschedule the auto-trigger buy action.

Note that the TradingView technical analysis will be updated in sequence. And each request takes about 1-3 seconds. It means if you have 5 symbols, to get the next technical analysis, it will take 5-15 seconds. If you have a large set of symbols to monitor, it may take more time to get the next technical analysis.

Order Limit

The bot can limit the buy open orders and maximum open trades.

There are configurations in the global setting.

• Enabled
• Maximum buy open orders: The bot will not place a buy order if the current buy open orders are exceeded this config value.
• Maximum open trades: The bot will not place a buy order if open trades are exceeded this config value.

The open trade means, number of symbols recorded with the last buy price. Let say if you set the maximum open trades as 5 and there are 5 symbols already recorded with the last buy price, then the bot will not place more buy orders.

However, there are exceptions.

• If the buy action is triggered by the auto-trigger buy action
• If the buy action is triggered by the manual trade

So you may see some orders exceeding your configured maximum open trades.

TradingView

Please refer https://github.com/chrisleekr/binance-trading-bot/wiki/TradingView

Logs

The bot is storing the last 30 minutes logs in MongoDB. The logs will help to find out why the bot decided to do certain actions.

You are also able to export by clicking the export button.

There is a configuration in the global settings.

• Delete after: You can set the minutes to delete the log. If the log is older than the configured minutes, the log will be removed from the database.

Note that the bot will check the last message and will not save if the new message was the same as the last message to prevent logging data is exploding in MongoDB.

This setting may impact the storage usage of the bot if you change it. So use with caution.