Nostr notes by WasabiWallet

On March 1st, 2027, the Wasabi indexer server, which provides ...

2026-09-23T13:39:23Z

On March 1st, 2027, the Wasabi indexer server, which provides compact filters to older versions, will be shut down.

Here's the fully corrected text: > "Compatibility ...

2026-09-14T15:32:33Z

Here's the fully corrected text:

> "Compatibility passphrase was used! Please consider generating a new wallet to ensure recoverability!"

If Wasabi has been displaying that message to you for the last 5 years, well… it's time to take action.

---

**tl;dr**

Because of a clipboard bug on macOS (OSX) in the Avalonia UI framework, users who created wallets by pasting complex passwords (with non-ASCII characters) got their password silently corrupted. When they later tried to log in by typing the correct password, it didn't match.

When a user enters their passphrase, if it is incorrect, Wasabi derives the corrupted passphrase and tries that one instead — in case of success, it alerts the user with the warning message above. We assume that after 5 years without any news about this issue, no one is affected. We will still give months before removing it.

---

**Long version:**

Some users were locked out of their wallets after updating Wasabi because the password they entered when logging in didn't match the password stored in the wallet file.

**The Root Cause**

There was a clipboard bug on macOS (OSX) in the Avalonia UI framework. When a user pasted a password from the clipboard:

1. Avalonia retrieved the clipboard content as raw bytes plus a "size" value.
2. The size was incorrectly taken from the string length (number of characters) instead of the byte length.
3. This matters because UTF-8 encoding uses variable bytes per character — special characters (like ä, ö, ñ, ¾) use 2–4 bytes each, while ASCII characters use 1 byte.

**Example:** A password like "Café" has 4 characters but takes 5 bytes in UTF-8 (C-a-f-é, where é = 2 bytes). The buggy code would only read 4 bytes, giving "Caf" plus a partial/corrupted character.

**What Happened**

Users who created wallets by pasting complex passwords (with non-ASCII characters) got their password silently truncated and corrupted. The wallet was created with the buggy password, but when they later tried to log in by typing the correct password, it didn't match.

**The Fix**

The compatibility feature tries multiple password variations when logging in:

1. The exact password entered.
2. The "buggy clipboard" version (truncated to string length in bytes).
3. A variant where the last character might be the replacement character \ufffd.

If the original password fails but a buggy variant works, the user is warned:
"Compatibility passphrase was used! Please consider generating a new wallet to ensure recoverability!"

This allows affected users to access their funds while warning them that their wallet was created with a corrupted password (which would be unrecoverable using standard BIP39 tools).

No. Do you want to be able to use czech or euro?

2026-09-05T03:50:16Z

In reply to nevent1q…4a4q
_________________________

No. Do you want to be able to use czech or euro?

Tor 0.4.8 and earlier versions will stop working after September ...

2026-08-17T00:40:49Z

Tor 0.4.8 and earlier versions will stop working after September 1st, 2026.

This means that Wasabi versions older than v2.8.0 will stop working as well.

Latest Wasabi version v2.8.1 is not affected. Please upgrade.

We are proud to announce that Wasabi Wallet v2.8.1 is out. It ...

2026-07-22T20:45:19Z

We are proud to announce that Wasabi Wallet v2.8.1 is out. It sets a major milestone which took more than a year to achieve: to make Wasabi unstoppable.

V2.8.1 fixes a bug that prevented running it in Start9.

2026-07-07T22:18:08Z

In reply to nevent1q…t7r0
_________________________

V2.8.1 fixes a bug that prevented running it in Start9.

🚨 New release 2.8.0 is here ⚙️ P2P synchronization for ...

2026-06-27T20:28:55Z

🚨 New release 2.8.0 is here

⚙️ P2P synchronization for compact filters
🚀 Pay in coinjoin
♻️ Payment batching
📎 Support for arm64 Linux, Tails, and Whonix
📜 Scheme scripting language
↘️ Sub-1 sat/vByte transaction fees
🔑 Signet test network
💀 Forward compatibility for Tor

---

## Feature Highlights

⚙️ P2P synchronization for compact filters

No central server needed anymore — Wasabi now runs fully independently.

🚀 Pay in CoinJoin

Make payments straight from CoinJoin, so privacy is preserved in everyday use. (experimental)

♻️ Payment batching

Batch outputs into one transaction for lower costs and smarter blockspace use.

📎 Support for arm64 Linux, Tails, and Whonix

Renewed support for the privacy-preserving operating systems we should never have abandoned.

📜 Scheme scripting language

Wasabi is now programmable what makes it easier to integrate with AI agents and tooling. (experimental) It doesn't have access to your money.

↘️ Sub-1 sat/vByte transaction fees

Pay less; hodl more. Available for Wallet and Coordinators which can also use this to make coinjoins cheaper.

🔑 Signet test network

Why not?

💀 Forward compatibility for Tor

The trigger for this release. After Sept 1st Tor clients from 0.4.8 (included in previous versions of Wasabi) will stop working.

📖 Read more here: https://github.com/WalletWasabi/WalletWasabi/releases/tag/v2.8.0

There hasn't been a single day we weren't working on ...

2026-06-11T14:24:43Z

There hasn't been a single day we weren't working on improving Wasabi. Stay tuned.