(note: this is a temporary file, to be added-to by anybody, and moved to release-notes at release time)
LUX Core version version is now available from:
https://github.com/216k155/lux/releases
This is a new major version release, including various bug fixes and performance improvements, as well as updated translations.
Please report bugs using the issue tracker at github:
https://github.com/216k155/lux/issues
LUX Core v3.0.0 is a mandatory update for all users. This release contains new consensus rules and improvements that are not backwards compatible with older versions. Users will have a grace period of one week to update their clients before enforcement of this update is enabled.
Users updating from a previous version after the 16th of October will require a full resync of their local blockchain from either the P2P network or by way of the bootstrap.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/LUX-Qt (on Mac) or luxd/lux-qt (on Linux).
LUX Core is extensively tested on multiple operating systems using the Linux kernel, macOS 10.8+, and Windows Vista and later.
Microsoft ended support for Windows XP on April 8th, 2014, No attempt is made to prevent installing or running the software on Windows XP, you can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker.
LUX Core should also work on most other Unix-like systems but is not frequently tested on them.
At long last, the zLUX release is here and the zerocoin protocol has been fully implemented! This allows users to send transactions with 100% fungible coins and absolutely zero history or link-ability to their previous owners.
Full and comprehensive details about the process and the use will be posted here during the days between Oct 6 and Oct 13.
Integrating with Tor is now easier than ever! Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket API, to create and destroy 'ephemeral' hidden services programmatically. LUX Core has been updated to make use of this.
This means that if Tor is running (and proper authorization is available), LUX Core automatically creates a hidden service to listen on, without manual configuration. LUX Core will also use Tor automatically to connect to other .onion nodes if the control socket can be successfully opened. This will positively affect the number of available .onion nodes and their usage.
This new feature is enabled by default if LUX Core is listening, and a connection to Tor can be made. It can be configured with the -listenonion, -torcontrol and -torpassword settings. To show verbose debugging information, pass -debug=tor.
Detailed release notes follow. This overview includes changes that affect behavior, not code moves, refactors and string updates. For convenience in locating the code changes and accompanying discussion, both the pull request and git merge commit are mentioned.
- #264
15e84e5zLUX is here! (Fuzzbawls Mrs-X Presstab Spock LUX)
- #242
0ecd77f[P2P] Improve TOR service connectivity (Fuzzbawls)
- #251
79af8d2[Qt] Adjust masternode count in information UI (Mrs-X)
- #258
c950765[Depends] Update Depends with newer versions (Fuzzbawls)
Thanks to everyone who directly contributed to this release:
- Fuzzbawls
- Jon Spock
- Mrs-X
- LUX
- amirabrams
- presstab
As well as everyone that helped translating on Transifex.