Orko Versions Save

0.15.3-SNAPSHOT

Includes updates to a number of dependencies, including security patches, so it is advised to upgrade as soon as possible. Also:

Fixes:

• Browser updates are now batched for better performance. Less high CPU during periods of high market activity
• Fixed a few small visual issues

0.15.2-SNAPSHOT

0.15 is heavily focused on internal work. I've been putting a lot of time into the deployment architecture and updating the code to prepare for the next big feature push. This release introduces a Java 11 requirement.

Features:

• Started work on breaking up the application into smaller docker services to optimise containerised deployment or use of only parts of the application. The first to be split out is the market data application. Note that this isn't ready for production use and is not currently a documented feature.
• Experimental support for using an Apprise microservice to push notifications to anything supported by Apprise (e.g. Slack, Mattermost, etc) rather than only Telegram. This is also not currently documented.

Bug fixes:

• Fixed bug where an IP whitelisting expiry could cause the application to go into an endless loop

Security:

• Added a robots.txt file to the web root

Developer quality-of-life:

• Switched to Java 11.
• Build now supports forks deploying to private docker repositories.
• Significant rework of the backend Java configuration architecture to improve modularity.
• Removed the need to maintain a modified cypress.json file locally when running end-to-end tests locally.
• [WIP] Partially eliminated redux/reselect from UI code and replaced with more sensible modular Contexts. This work will continue into the next release.

Emergency fix for a bug which caused snapshot releases to appear as a new release when opening the app. See 0.14.2.

Don't use this release. 0.14.3 was released only minutes later with an urgent fix.

This update does not affect the database schema, so if there are problems, it can be easily rolled back to 0.13.1. Follow these instructions to upgrade.

Warning:

Please see the warning in the changelog for the previous release regarding current market conditions.

Bug fixes:

• #408 - Prevent socket disconnects/reconnects from sending constant browser notifications. These are now only shown in the app's notifications panel.
• Bitfinex trades were arriving from the websocket with bid/ask flipped in seemingly random cases. This is now fixed.
• Prevent errors in streaming on some exchanges if not authenticated
• The UI was missing from the app build published to Docker Hub. Fixed.
• [xchange-stream] Coinbase Pro order books were causing high server CPU usage and intermittent corruption. Fixed.

Security:

• Lots of dependency updates

Developer quality-of-life:

• Preparation for switch to Java 11. Build now works fine on both Java 8 and 11.
• Fixed numerous intermittent CI/build errors
• Moved to track the standard XChange and xchange-stream releases on Maven. I'm going to experiment with using classpath overrides for expedited fixes for the time being to see how things go. This should speed up release cycles.

This update does not affect the database schema, so if there are problems, it can be easily rolled back to 0.13.1. Follow these instructions to upgrade.

Warning:

Please see the warning in the changelog for the previous release regarding current market conditions.

Features:

• Added Docker support. You can now pull and run directly from Docker Hub.
• You can now always get a bleeding-edge version of the application from GitHub releases. Serious issues such as fixes for changes to exchange APIs are usually fixed far quicker than the release cadence, so this can be extremely helpful.

Bug fixes:

• #374 - [kucoin] Fix error fetching trade history and open orders due to new API limits
• #375 - Added Github to the Content-Security-Policy. This was preventing new release alerts from appearing.
• A number of low-level fixes from bumps to XChange and xchange-stream dependencies

Developer quality-of-life:

• Removed Travis build. All CI is now handled by parallel CircleCI jobs, which is much faster and simpler.

This update does not affect the database schema, so if there are problems, it can be easily rolled back to 0.13.1. Follow these instructions to upgrade.

Warning:

Due to the phenomenal increase in market activity over the last few months, Heroku instances are too slow to handle more than a handful of coins at once. This is being handled under #360. A proper solution will be in place soon. In the meantime, either:

• keep the number of coins you track as low as possible (particularly making sure you only track one BTC/Fiat pair, which have the highest volume)
• or avoid server-side ("soft") orders, since there is a good chance they will trigger too late if the server is lagging
• or avoid Heroku.

Features:

• Added buttons to limit order panel allowing the trade amount to be set to the maximum possible given the current balance. These need improving on mobile but do work so rolling out.

Bug fixes:

• [bittrex] Fixed bug where zero balances would should as loading.
• [bitfinex] Fixed NPE exceptions and blocked updates when there are stop-limit orders on the exchange (XChange)
• [bitfinex] Fixed NPE fetching currency metadata [#362]

Security:

• Fixed security advisory in dropwizard-https-redirect caused by logging on untrusted user-supplied data.

Developer quality-of-life:

• Dependency updates

This update does not affect the database schema, so if there are problems, it can be easily rolled back to 0.12.2. Follow these instructions to upgrade.

Exchange support:

• Bittrex is now fully supported, albeit without streaming updates (like Kucoin), so the UI is not as responsive as Binance, Bitfinex or Coinbase Pro. This could be added but is not a priority for me right now.

Enhancements:

• Reliability features for "soft" or "complex" orders, which includes trailing stops, OCOs, soft stops or scripted complex orders:
  • All in-built soft/complex orders will now warn you if the balance isn't currently available to satisfy the orders. This is fine (you might have set them up specifically to trade on the opposite side of an exchange order, which is the whole reason for using soft orders) but sometimes a warning can help you realise you've done something stupid.
  • All soft/complex orders, including scripts, will now gracefully handle the case where the full balance isn't available to execute an order, and reduce the trade size to fit within the available balance. This tries to handle the complexities of price scale and lot size filters applied by exchanges. This can be a lifesaver, since most exchanges take their fee from the purchased asset, making it hard to predict in advance what your balance will actually be after a sequence of trades. You can now just set a high guess and let Orko manage the trade amount down.
• Now warns the user if any of the Bitfinex, Coinbase Pro or Binance socket connections to the exchanges drop for more than 10m (was previously only Binance).
• Added simulated exchange, which allows integration testing without any socket connectivity to an exchange. This will get improved over time and used heavily in Orko's own tests.
• Improved the login/authentication experience with more descriptive fields, validation and tooltip help
• On-screen alerts for new releases.

Bug fixes:

• Much better and more consistent handling of exchange errors from background processing. Most of the time these errors are now dealt with silently and without spamming the logs (particularly around common transient issues such as socket timeouts or load control at Cloudflare). Only if the error type is unexpected is the user alerted and a stacktrace logged.
• Improved logging around Bitfinex connection errors.
• Fix bugs where Binance and Bifinex trades were displayed as buys when they were actually sells and vice versa under certain conditions.
• Fix UndeclaredThrowableException errors in logs when using Kraken. Kraken remains in early stage support and is not recommended for use.
• Some exchanges don't return all the 24hr stats (e.g. open or close prices). These previously displayed a spinner in the UI the whole time, hoping a value would arrive. They are now hidden entirely unless there's a value to display.
• Fixed broken link to the Wiki from the paper trading confirmation text.

Developer quality-of-life:

• Greatly increased unit test coverage, and the simulated exchange now means this can be expanded even further.
• Lots of dependency updates (nothing marked as security critical)
• Switched from Semantic-UI to Fomantic-UI, eliminating security warnings in gulp build

Patch release to resolve some urgent issues in 0.12.1.

Fixes:

• Fixed: 404 errors when running the package release downloaded from GitHub (this did not affect Heroku users or anyone else building from source).
• Fixed: Password hashing was asymmetric - passwords hashed with the CLI would not be matched by the application.

In addition:

• Improved back-off when we hit rate limitation errors from exchanges that tell us nicely what's going on
• Improved error messaging in some cases.