1.1.5
1.1.4
1.1.3
Revision - Manual Coin holdings + FTX
v1
July 6, 2021
See more- The Balances tab has been upgraded to:
- Accommodate manual balances.
- FTX integrated to include Balances, Positions and Orders (including cancellation thereof)
- Deribit orders added also including cancellations
- Changed default ApiKey file location to local user.
- Formatted Balance BTC values with monospace font
- Binance bug fix for 1000ms 1021 error.
1.1.2
Revision - Aggregation of balances in BTC
v1
June 29, 2021
See more- The Balances tab has been upgraded to:
- Aggregate all balances in BTC on an exchange level as well as on a global "Total BTC" level.
- Default grouping of all exchanges which can be individually expanded to see balance details per exchange.
1.1.1
Revision - Bybit 6sec Fix
v1
June 15, 2021
See more- A workaround for the Bybit 6 second error on POST requests. See (v1.0.1) for more info.
- Also added a new menu item under Help to view "Previous Release Notes"
1.1.0
Minor - Login and Automatic Updates
v1
June 1, 2021
See more- Security - When launching the application one would need to log in either using Google Authenticator or YubiKey. Users are also required to register first before access to the software is granted.
- Auto Updating - To update to the newest version simply go to Help -> Check For Updates on the menu strip and follow the instructions.
- Website - Not specifically an application feature but the website will make distributing the application easier as well as provide a page listing current and previous release notes.
- Item User Settings - User settings are now stored on a local-user level (instead of an application version specific level) so that all previous application settings are easily applied to new versions. This will include the location of the API Keys file, application layout, etc.
- Improvement: Menu Layout - An updated menu layout to clearly indicate what features are still up-coming and to provide an overview of the roadmap
1.0.0
1.0.1
- 6 second post request issues on the Bybit server. We have made a work around for now by specifying a 10sec receive window on all Post web requests.