dcrdex v0.5.3
DCRDEX v0.5.3
IMPORTANT: Use the v0.5.4 patch release (or newer) instead. There is a critical bug fix related to Bitcoin block parsing.
Please read the v0.5.0 release notes for a full list of changes since v0.4.
For important information and an introduction to DCRDEX, read the initial release (v0.1.0) notes.
NOTE: This release includes an experimental downloadable executable for Windows, the dexc-tray archive, which starts the DEX client with no terminal, and with a system tray icon. For Windows users, this should feel more natural. See #1828 for more info.
Features
- Add translations for de-DE. (d8c6ce3)
- Native BTC wallets now have an option to obtain a current network fee rate from an external source. (1af28ea)
- Decred wallets now have the ability to change certain settings without requiring a full restart of the wallet. This allows the user to change certain minor settings such as the option to use the external fee rate source while trades are active. However, it is still recommended to keep wallet settings unchanged while trades are active. (2ac43de)
Fixes
- Concurrent login requests are handled in sequence now, preventing certain bugs when the user attempts to login again while a previous login request is being handled. (5084446)
- The password fields on the wallet configuration forms are generated with the
autocomplete = 'off'
attribute. This improves privacy by preventing the browser from remembering the values entered. (3d365d7) - The network fees paid for a swap redemption were incorrectly shown on the order details page. The correct fees are now shown. (11ce1ff)
- Various frontend fixes. (b01d81c)
- More thorough handling of epoch status orders when network connectivity is interrupted and restored. This may resolve a variety of uncancellable orders, as well as perpetual locking of funds, which was previously only resolvable by restarting the DEX client. (942e594)
- The default RPC port is removed from the Electrum wallet configuration form since there is no default. (e9ca06d)
Server
- The server now sends a
revoke_order
notification after a preimage miss to assist with epoch order status resolution with clients that had lost connectivity at the time of the preimage request, but regained connectivity before the end of that epoch's match cycle. (26fa5a1)
Code Summary
11 commits, 46 files changed, 3,670 insertions(+), and 323 deletions(-)
5 contributors
- Jonathan Chappelow (@chappjc)
- @karamble
- @martonp
- Victor Oliveira (@vctt94)
- Philemon Ukane (@ukane-philemon)