Wallet Load
Loading wallet step-by-step
To load a wallet and start the synchonization process, you need to open your wallet by typing in the passphrase. The first time synchronization of your wallet might take some time depending on the size of its history.
Wallet list
On the left side of Wasabi Wallet is the Wallet list, where you see an alphabetically sorted list of all the previously generated wallets.
Click the wallet you want to view, type in the passphrase and press Open.
Synchronization
Filter download
As soon as you start Wasabi, it connects to the backend server with a new Tor identity and requests the BIP 158 block filters. At the first start, this can take a while because all filters need to be downloaded, but for the subsequent starts, this is faster as only the most recent filters are requested.
Filter scanning
When you load a wallet, it checks if the generated addresses within the gap limit hit against a block filter. Most filters do not hit, and then the wallet is certain that this block does not contain a transaction of yours so it will not download it. If a transaction of yours is in a block, then the corresponding filter will always be hit, and the wallet will know this is a relevant block for you. There can be a small chance for a false positive where the filter matches, but the block actually does not contain a transaction.
Block download
When a block filter hits, either a true match or a false positive, then this block is important for you, so the wallet will download it. If you have a Bitcoin full node connected, then it will fetch the verified block locally. If not, then Wasabi will connect to a random Bitcoin P2P node with a new Tor identity, request only this block for download, and then disconnect. In this step, your Wasabi behaves like any other full node, and cannot be differentiated.
TurboSync
Since Wasabi version 2.0.4 a new feature is added called TurboSync. TurboSync leads to a significant reduction of wallet loading time, especially for a big wallet.
During a coinjoin, a new address (key) has to be generated for each output. As a result, wallets that use the coinjoin service a lot have a quickly growing set of generated addresses. This is a problem for wallet synchronization: each address has to be tested against each filter, with a small probability of matching as false-positive for every address. As a result, wallets with many derived addresses will have to download many false-positive blocks, making the synchronization more time consuming.
It leverages a simple heuristic: addresses used as coinjoin outputs or as change (internal keys) should only be used once. In other terms, once an internal address has been used to receive a coin and then this coin was used as input in a new transaction (the coin has been spent), the address should never be used again, and there is no need to test it against the remaining filters.
Wallets coinjoining a lot will benefit the most from this feature, as the vast majority of their addresses will be skipped, reducing the number of blocks to download because of false-positive matches.
Once the wallet is opened, the skipped addresses will be tested in the background, in the case that some funds have been received on those addresses. Users in that edge case would see their balance update automatically after some time. Once done the message Wallet is fully synchronized. is written to the logs file to indicate that the verification process has finished.
You can disable it!
TurboSync feature shouldn't cause any problem, but you might want to disable it to debug potential issues with the synchronization of your wallet. In that case, go to your wallet file (search for Wallet Folder using Wasabi's searchbar then open the file corresponding to your wallet) and set UseTurboSync to false.