dcrdex v0.1.5

DCRDEX v0.1.5

This patch release provides several important bug fixes.

Please read the initial release (v0.1.0) notes for important information and instructions.

Client (dexc)

Features and Improvements

The user's account ID is now logged on connect and authentication with a DEX server. (8ce328c)

Fixes

• Fix a possible panic when reconfiguring a wallet that is not connected. (dfe4cd1)
• When resuming trades on startup and login, counterparty contract audits now retry repeatedly, as is the case when an audit request is initially received. This prevents a match from being incorrectly revoked on startup if the wallet/node fails to locate the counterparty contract immediately. (172dbb7)
• The client's database subsystem is always started first and stopped last. (b4ef3ff) This is a prerequisite for the following wallet lock-on-shutdown change.
• On shutdown of client Core, the wallets are now locked even if the PromptShutdown function is not used. This does not affect dexc users, only direct Go consumers of the client/core.Core type. (70044e6)
• Fix a possible interruption of the DEX reconnect loop if the config response timed out. (4df683a)
• Update the crypto/x/blake2 dependency to prevent silent memory corruption from the hash function's assembly code. (c67af3f)
• Handle orders that somehow loose their funding coins. Previously, such orders would forever be logged at startup but never retired, and any matches from such orders that required swap negotiation of other recovery would have been improperly abandoned. (a7b5aa0)

Server (dcrdex)

There are no substantive server changes, just a few logging improvements.

Code Summary

11 commits, 13 files changed, 564 insertions(+), and 254 deletions(-)

v0.1.4...v0.1.5

3 contributors

• Brian Stafford (@buck54321) (review)
• David Hill (@dajohi) (blake2 fix)
• Jonathan Chappelow (@chappjc)