Repository navigation
This release focuses on performance improvements and bug fixes for mixing wallets. All users are recommended to update.
Bug fixes
-
A harmless error logged during the publishing of confirmed mix transactions was fixed by removing an incorrect spend proof check on unmined mempool transactions (
61ca8901). -
Change addresses (and the internal address branch index) are only derived and incremented when necessary (
93fa7d44). -
A missing bounds check of the output index for the
mixoutputJSON-RPC method was added (e7865552). -
A performance issue determining which peers were active in a mixing epoch was improved using a more efficient algorithm (decred/dcrd#3790).
-
Multiple distinct mixing key exchange messages are no longer permitted by the same sender for the same session (decred/dcrd#3820).
-
The permitted total number of mixing key exchange messages that may be publised by a single peer was reduced (decred/dcrd#3822).
-
The lower limit of 64 maximum peers per mixing session was relaxed for key exchange messages, allowing up to the larger 512 limit of pair request messages to be referenced before an alternate session is formed. Following messages in a mix session must still not reference more than 64 total peers (decred/dcrd#3824).
-
A shorter 10s mixclient stage timeout is being tested on testnet. Mainnet mixing wallets continue to use a 30s message timeout for each mixing stage (decred/dcrd#3826).
Changelog
599b5850: [release-v2.1] Bump version to 2.1.7+release.local.4acbfa1c: [release-v2.1] Update minimum Go version described in READMEb9f31d72: [release-v2.1] Update CI to test with Go 1.26 and 1.27c9691d79: [release-v2.1] Update modules93fa7d44: [release-v2.1] txauthor: Only get change address when needed.e7865552: [release-v2.1] mixing: add missing bounds check61ca8901: [release-v2.1] wallet: Do not check ValueIn of announced mempool transactions
Code Contributors (alphabetical order)
- David Hill (@dajohi)
- Jamie Holdstock (@jholdstock)
- Josh Rickmar (@jrick)