### WalletWasabi: v1.0.1

WalletWasabi version Wasabi v1.0.1: Small UX Tweaks released.

# Summary

The 1.0.1 Release mostly consists of smaller fixes those came up due to the influx of mainstream users. The most notable improvements are the implementation of OSX cmd+… copy-paste related keys (it was previously working with ctrl) and fixing a bug that prevented users with non-English Linuxes to use Wasabi.

# Newbie Guide

While setting up Wasabi is straightforward, even the Linux wizard with the longest beard can get stuck on the most basic tasks. In that case, take a look at the Installation Instructions guide.

# Pro Guide

If you want to build Wasabi from source code or update the source code check out these instructions.

## FAQ

• Where is Wasabi’s working directory located? Configuration, wallet and similar files can be found in %appdata%\WalletWasabi folder on Windows and in ~/.walletwasabi folder on Linux/OSX.
• Can I use my own Tor instance, instead of Wasabi’s built in one? If you already have Tor, and it is running, then Wasabi will try to use that first, if it is not running, then Wasabi will use its built-in Tor. If you are running a Tor daemon not on the default port, then you can configure it in Wasabi’s Tools/Setting menu. If Wasabi is using your Tor daemon, then bear in mind that some Linux distributions’ package repositories ship with out of date Tor. In that case, either remove or shut down that Tor of yours or make sure it’s not out of date: Check Tor version: tor --version. If it’s not at least 0.3.2.2, then see this writeup on how to update it.
• Why are the binary sizes so big? Wasabi is using client side filtering and these filters must be synced before using the wallet. The size of these filters are currently about 90MB. These filters are included with the binaries to avoid initial wallet syncing.
• Requirements? x64, linux, >win7, >osx.10.12.