WASABI 2.8.5 FIXES A CASE WHERE A MALICIOUS COORDINATOR “COULD CAUSE A LOSS OF FUNDS” — THE RELEASE NOTES SAY “MALICIOUS SERVERS” — AND PAYJOIN IS GONE SIX WEEKS AFTER IT GOT TAPROOT

Wasabi Wallet shipped version 2.8.5 at 8:34 PM ET on October 26. The release notes say it "adds stricter transaction verification to protect against malicious servers." The pull request behind that line says more. PR #15173, merged October 19, "fixes a case where a malicious coordinator could cause a loss of funds."

Here's the case. In a Wasabi coinjoin, a coordinator assembles one big transaction and each wallet signs its own inputs. If the coordinator left out one of your registered inputs along with your outputs, the PR says, "the remaining signatures can still complete the transaction." The fix has your wallet hold back one signature when its safety checks fail. A maintainer wrote "this is confirmed bug" on October 18, and then, "We will need a v2.8.5."

That's the part you can check. Wasabi's own docs still describe its WabiSabi protocol as running coinjoins "in a trustless (meaning nobody can steal)" manner. The repo had no published security advisory at 9:23 AM ET on October 27, and the release notes don't describe the flaw. The protection lives in your client, so it only counts once you've updated.

Payjoin is gone, too. Version 2.8.3 added Taproot support for payjoin on September 14. Six weeks later, 2.8.5 drops sending payjoins "to reduce code complexity and attack surface." The commit deletes 1,458 lines. The docs page explaining payjoin was still up at 9:23 AM ET. At the time of this writing, bitcoin was $80,169.