2.4.6 – Release

ProfitTrailer

5 years ago

Change log

FIXES
- Implement the new websocket subscription style for Binance and Binance Futures
- Upgrade Binance V1 api calls to V3
- Binance futures buttons should display open/close
- Fix when we revisit /setup/exchange page it should not reset our previous data
- Fix for when we revisit config selection setup screen
- Fix BinanceDEX default exchange url
- Fix for BinanceDEX not able to buy/sell correctly
- Fix trying to better handle BitMEX 403 error
- Small fixes

https://download.profittrailer.com/ProfitTrailer-2.4.6.zip

IMPORTANT 2.4.0 RELEASE NOTES

Breaking changes
- Removed trailing_stop_loss_strategy_formula define your formula inside trailing_stop_loss_trigger
- Change STOCHRSICROSS formula to K% – D%
  - More accurate representation
  - Previous calculation was exaggerating the actual movement of a cross
Broken Add-ons (They need to release an update)
- PT Defender
Deleted (After being deprecated in 2.3.0)
- Removed start_balance (PAIRS config)
  - Use Hotconfig to set the balance for a test bot
  - Use Settings cog start balance to set a balance used for Profit calculation purposes only
Deprecated (Still works but remove as soon as possible)
- Deleted application.properties. Use the settings cog to change your application settings
- Deprecate reserve_amount (Use new button in GUI)
- Deprecate default_initial_cost_percentage in favor of default_initial_cost = 2%
  - Just give your value a % at the end to make it behave as a percentage.
- Deprecate keep_balance_percentage in favor of keep_balance = 25%
- Deprecate default_dca_ignore_sell_only_mode
  - Use DEFAULT_DCA_sell_only_mode_enabled to enable to enable/disable SOM manually
- Deprecate dca_buy_trigger, use PROFITPERCENTAGE strategy instead
- Deprecate som_dca_buy_trigger (No alternative)
- Deprecate LOSS strategy use CHANGEPERCENTAGE strategy instead
- Deprecate ANDERSON strategy use PROFITPERCENTAGE strategy instead
New Exchanges
- Binance JERSEY (binace.je)
- Binance US (binance.us)
- Binance DEX (binance.org)
- HUOBIUS (Huobi.com – for US users)
  - NOTE: Huobi Global is HBG.com
Major GUI changes (See wiki link for more)
- Removed Basic config (Our settings cannot be interpreted into a basic config and thus it lacks)
- Add PT Asssistant to the GUI
- Add Profit Calculation Method to settings screen. Choose between MARKUP or TCV
- Add new advanced stats data
- Add button to buy log and sell log to manually add a record
- Merge PTNotifications into ProfitTrailer (PRO and ADVANCED users only)
  - Enable by clicking the Adv Notifications button
- Remove the sidebar and move it’s buttons to different places around the GUI
- Move Hot Config and create a page for it
- Access public configs from other configs page
- Manual buy and sell now gives you the option between IOC or MARKET. Not all exchanges support market orders though.
Major Changes Bot
- Reversal Trading
- Auto Switch config based on market conditions
- Scale Out profit taking. Sell in multiple stages
- Support Binance Margin trading
  - Note: The bot does not borrow/repay your debt for you and is currently unaware of how much you borrowed
- Trailing profit is no longer linked to profit/GAIN% but to the price when trailing started
  - if the user restarts within 5 minutes trailing can continue where it left off
  - you can trail without having a GAIN specified and thus trailing profit now works for users using formulas too
- SOM (Sell Only Mode) Overhaul
  - Global SOM can be turned on/off with a button in the footer
  - Global SOM will persist after a restart
  - No more complicated SOMO
- price rise / drop and consecutive triggers now work as filters.
  - You will see them blocking a buy on the GUI below the PAIR and no longer as part of SOM in footer
- If you change the setting it immediately invalidates and all coins will check again for validity (No more restarting bot etc)
There are many more changes
- See the full list https://wiki.profittrailer.com/doku.php?id=changes#version_24
PT API Changes
- Created a new V2 API that can do a lot more
- Old V1 api is now deprecated and will be removed in 2.5