diff --git a/404.html b/404.html index 070d3d5535..f490a38e9e 100644 --- a/404.html +++ b/404.html @@ -24,10 +24,10 @@ | Wasabi Docs - +

404

Looks like we've got some broken links.
Take me home
- + diff --git a/FAQ/FAQ-Contribution.html b/FAQ/FAQ-Contribution.html index 725e0a4b5b..d203329225 100644 --- a/FAQ/FAQ-Contribution.html +++ b/FAQ/FAQ-Contribution.html @@ -24,10 +24,10 @@ Contribution FAQ | Wasabi Docs - +
Wasabi Docs

Contributions to Wasabi

How to donate to Wasabi Wallet?

Adam Ficsor had a donation address for a few years while he was working alone on Wasabi. It's not the case anymore. Though it's most likely not an issue to accept Bitcoin donations, zkSNACKs team discontinued accepting donations because they don't want to get into accidental legal gray areas. Wasabi has a coordination fee that is capped at 0.3% for every CoinJoin and it became zkSNACKs' main income. To help Wasabi development, just CoinJoin your bitcoins via Wasabi! If you want to read more about fees here is a nice explanation: What are the fees for the CoinJoin.

The Wasabikas

Who is contributing to Wasabi already?

There are many Wasabikas working with great effort and care to manifest this powerful tool of self-defense. Over 50 peersopen in new window have already contributed to the repository. Four of the main contributors are Ádám Ficsoropen in new window [co-founder and former CTO of zkSNACKs Ltdopen in new window, co-author of the zero link Bitcoin fungibility frameworkopen in new window], Lucas Ontiveroopen in new window [lead engineer of zkSNACKs Ltdopen in new window], Dávid Molnáropen in new window [CTO of zkSNACKs Ltdopen in new window], and Dan Walmsleyopen in new window [co-maintainer of Avalonia UI Frameworkopen in new window].

Watch the videoopen in new window

Watch the videoopen in new window

Watch the videoopen in new window

Who reviews and merges the pull requests?

As the Wasabi code is libre and open-source, anyone has access to review the latest contributions and browse the open pull requestsopen in new window. The review of any Wasabika is not just deeply appreciated, but desperately needed! Wasabi is cutting-edge, high security software, and there can never be enough eyes seeking and squashing bugs. Especially review by experienced C# developers are vitally important, yet even typo and grammar fixes are necessary.

There are four developers who have the ability to merge code into master branch. Per default, they require at least one approving reviewopen in new window by one of the other maintainers before a pull request can be merged. However, since all four are administrators, they can still force the merge without the approval of others, but this will be noticed by many contributors.

What is on the future roadmap of Wasabi development?

Wasabi is far from complete, there are many Wasabikas contributing every day to make this tool of self-defense even more powerful. Because Wasabi is libre and open-source software, anyone can support the project without asking for permission. Thus it is relatively tricky to give a precise roadmap with what will be implemented in the near and distant future.

You can become a Wasabika

How should I start contributing to Wasabi?

Thank you for considering to support this beautiful libre and open-source project! It is the responsibility of everyone using the software to contribute to its growth. Your help is deeply appreciated, and very much needed! First please read the contribution checklist to get introduced to the project and to start out in the right direction. Join our Slackopen in new window and check out our GitHub repositoryopen in new window, so that you can stay up-to-date with the latest contributions.

Is there a bounty program?

Yes! The beauty of Wasabi is that it's not just a very awesome wallet by default, but it has the additional opt-in CoinJoin service. This is provided by zkSNACKs Ltd.open in new window, and in exchange for this service, the user pays a coordination fee. In return, zkSNACKs is supporting several developers to dedicate their full time to contribute to this open-source project. There are also contribution games where a bounty is paid out to any contributor worthy the prize.

How can I report a bug?

Code is speech, and can never be perfect. Thus it is expected that there are many known and unknown bugs, quirks and issues in Wasabi. Such a complex software requires constant and rigorous review by the developers and the users, this is everyone's responsibility working with Wasabi.

When you stumble upon an issue that needs fixing, please first check the open issuesopen in new window and pull requestsopen in new window if there is already someone working on it. If yes, then you can comment your situation and bug report under the open issue. If no, then please consider to open a new issueopen in new window and give a detailed report on the problem. It is especially helpful when you provide a step-by-step guide on how to reproduce what you have found. There is constantly a lot of work done to the code base, thus it's good to know which version of Wasabi, and what operating system you are using. In some cases it might be useful to see your logs, though please consider your privacy and encrypt this data properly in direct communication with the developers.

DANGER

If you find a bug that puts users' privacy or security at serious risk, please take great care with responsible disclosure! Send an email to adam.ficsor73@gmail.com, preferably using PGP encryption 21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075Eopen in new window.

How can I request a feature?

Wasabi is a quite beautiful piece of software already. Yet there are also 1001 things that could be just a little better, or even quite substantially superior. The beauty and bane of libre and open-source software is that it is never complete, there is always more work to be done.

Regardless if you are a new user of Wasabi, or a veteran black belt Wasabika, any suggestions on how to improve are very welcome. Please first check the existing issuesopen in new window and pull requestsopen in new window if someone has the same feature request as you. If yes, then you can comment your desired improvement under the open issue. If no, then please consider to open a new issueopen in new window and give a detailed request. It makes sense to first explain the problem you have in the incumbent version of Wasabi, this is the place to express your frustrations and annoyances. Then describe the solution that you have envisioned, with all the nuances and details of how this would fix your problem. To flesh our your argument, please consider alternatives and different approaches to this feature request.

How can I get help and support?

You are already on the right track by first checking this documentationopen in new window for the knowledge you are seeking. It's likely that you are not the first person who has an issue or a question, and hopefully someone has curated the answer in here already. You can use the search function in the top navbar to look for a specific topic, and the sidebar menu as a table of content. You can also use our GitHub Discussionsopen in new window to find solutions to different issues and to ask questions if necessary. If your trouble is specific to the code, then it might also be suitable to check the existing GitHub issuesopen in new window and open a new one.

What does the Wasabi project need help with?

Wasabi is libre and open-source software, thus it relies on the support of several contributors on all fronts. Of course, this includes coding new features, bug fixes and stability improvements. Yet just equally important is the review of the commits of all other Wasabikas. It's not just the contributions to the code, but also to the documentation and the effort to educate peers using Wasabi. This includes education in meatspace tribe gatherings, but also in cyberspace peer support. So basically, we need help with building and shilling Wasabi!

- + diff --git a/FAQ/FAQ-GeneralBitcoinPrivacy.html b/FAQ/FAQ-GeneralBitcoinPrivacy.html index 233a145fab..a1f5ba97b0 100644 --- a/FAQ/FAQ-GeneralBitcoinPrivacy.html +++ b/FAQ/FAQ-GeneralBitcoinPrivacy.html @@ -24,7 +24,7 @@ Bitcoin Privacy FAQ | Wasabi Docs - +
Wasabi Docs

General Bitcoin Privacy

Why Privacy matters

I have nothing to hide, do I still need financial privacy?

What did you say to your spouse in bed last night? How much money did you earn last month? What websites have you visited yesterday?

TIP

It's not that I have nothing to hide, it's that I have nothing to share.

There are many tasks in everyday life that are simply none of your business. Knowledge you choose not to share with others, things you only tell one individual, actions that you do while nobody is watching. How much money you earn, and where you spend it, is only your business, and of no concern to most other individuals.

How is financial privacy an essential element to fungibility in Bitcoin?

Fungibility is the possibility for an individual receiving bitcoin to safely ignore any connection between this bitcoin and any particular individual or use case it interacted with in the past. If you can meaningfully distinguish one coin from another, then their fungibility is weak. If Bitcoin fungibility is too weak in practice, then it cannot be decentralized: if someone important announces a list of stolen coins they won't accept coins derived from, you must carefully check coins you receive against that list and return the ones that fail. Everyone gets stuck checking blacklists issued by various authorities because in that world we'd all not like to get stuck with bad coins. This adds friction and transactional costs and makes Bitcoin less valuable as money.

How is financial privacy essential for entrepreneurs?

If you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.

How is financial privacy essential for personal safety?

If thieves can see your income, holdings, and spending, they can use this information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your large purchases off your doorstep, or impersonate businesses you transact with towards you. They can tell exactly how much to try to scam you for. If thieves don't know how much bitcoin you have, then they don't know if you are worth the effort to attack.

How is financial privacy essential for human dignity?

No one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.

Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.

The Privacy of Bitcoin

How is Bitcoin good in terms of privacy?

Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.

Instead, in Bitcoin pseudonyms protect your identity. In the Bitcoin ecosystem, everyone can see the history of every account balance, but they cannot see who controls an account. All addresses and transactions are recorded in Bitcoin’s publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.

How is Bitcoin bad in terms of privacy?

Bitcoin is by default a transparent system, in which every piece of information is available to the public. As such, every Bitcoin user requires some level of protection. Anyone with substantial wealth in Bitcoin would not want to advertise their funds to every person they transact with, for obvious reasons. But every time you spend just a tiny portion of your bitcoin, you might reveal your wealth to the other party. Doing that on the internet is like flashing large stacks of cash in a dark back alley, so obviously it’s not advisable! A criminal might see how much you have and decide to come after it. Distributing your wealth between several wallets and using a different address for each transaction is a common practice that prevents others from knowing how much bitcoin you have.

Each Bitcoin transaction contains at least one input (where the Bitcoin are from) and at least one output (where the Bitcoin are being sent). This means that once a single address is known, there is a trail to follow the Bitcoin.

Another characteristic of Bitcoin transactions is that the value of the input always needs to match the value of the previous transaction output. If you previously received 1 bitcoin, and you want to spend 0.4 bitcoin, the transaction needs to spend the whole 1 bitcoin. 0.4 bitcoin will go as payment, then 0.6 bitcoin will return to you as change. Your Bitcoin wallet will handle this process automatically, but it is important to understand the principle in order to use it anonymously.

The owner of the original bitcoin doesn't know whom you paid the money or what you did with it, but they can see the amounts and addresses involved. They can see two outputs of the transaction: one worth 0.4 bitcoin and one worth 0.6 bitcoin. They might not know for certain which is the purchase and which is the change, but they can apply heuristics to estimate it.

Similarly, if you receive 0.5 bitcoin but want to spend 1 bitcoin, you need to own additional coins with a combined value of at least 0.5 bitcoin in them. When spending two coins within one transaction, it is often assumed that both of these coins belong to the same entity, this is the common input ownership heuristic.

Why is it important to run a full node?

TIP

Not your node ~ not your rules

When you download and install bitcoindopen in new window, you define the precise rules of your monetary system. Then you call out to other nodes and only connect to the peers who have agreed to play by the same rules. All those who break your own rules, you simply disconnect and ignore. Your full node defines, verifies and enforces the sound money you use to store your value.

How does a full node protect my privacy?

When you run your own full node, then on your local computer you can verify exactly if the bitcoin you receive are actually valid. When you do not verify this for yourself, then you need to ask another trusted third party how much money you have. Regardless how you ask this other server, there is now more metadata available to potentially link your coins to your identity. There are bad ways to communicate, like querying a block explorer over clearnet, and good ways to communicate, like using BIP 158open in new window block filters over Tor. But regardless, running your own full node means that you don't need to communicate with anyone about your specific coins and this is strictly better.

How can I set up a full node?

Wasabi comes pre-installed with bitcoind from Bitcoin Knotsopen in new window and it can be started on the same desktop or laptop computer with just one click. This is likely the most convenient solution for Wasabikas.

There are also other node implementations different from Bitcoin Knots, such as Bitcoin Coreopen in new window or Libbitcoinopen in new window, that could be used as well.

Instead, if you prefer to use some dedicated hardware solutions, these are some of the most reliable projects:

Why is it important to use a new address for every payment?

Addresses being used more than once is very damaging to privacy because that links together more blockchain transactions with proof that they were created by the same entity. The most private and secure way to use bitcoin is to send a brand new address to each person who pays you. After an address has received a coin, it should never be used again. Also, a brand new bitcoin address should be demanded from the recipient when sending bitcoin. Wasabi has a user interface which discourages address reuse by removing from the GUI addresses which have received a coin.

It has been argued that the phrase "bitcoin address" was a bad name for this object because it implies it can be reused like an email address. A better name would be something like "bitcoin invoice".

Bitcoin isn't anonymous but pseudonymous, and the pseudonyms are bitcoin addresses. Avoiding address reuse is like throwing away a pseudonym after it has been used.

What is a coinjoin Sudoku?

Coinjoin Sudoku is a type of intra-transaction analysis attack on coinjoin transactions that aims to link inputs and outputs together based on their combinatorial sums. You can read more about coinjoin Sudoku hereopen in new window.

The Privacy of Tor

How does Tor protect my network-level privacy?

When you make a Bitcoin transaction, you are essentially creating a message on your phone or computer and sending it to the Bitcoin network. Someone operating a large number of nodes on the Bitcoin network might be able to match some of your transactions to your IP address, then deanonymize your stack of bitcoin.

It is relatively easy to avoid this on a computer by relaying all transactions through the Tor network. Wasabi routes all traffic via Tor’s SOCKS5 proxy, by default.

To maintain your anonymity, use the Tor Browser or the Tails operating system, if possible. Route everything through Tor by default.

It is also good practice to route your chats through the Tor network. You can also configure many cloud storage providers in this way.

Why does Tor process keep running after closing Wasabi Wallet?

There are two main reasons: user experience and privacy.

If a user closes Wasabi and then starts it again, he's already connected to Tor and he does not need to build a new Tor circuit. This means that Wasabi's startup will be much faster, because the Tor circuit is already established.

Regarding the privacy, this is done to avoid time correlation attacks when using Wasabi Wallet. In fact, if a user creates a new Tor circuit every time he opens Wasabi Wallet, he would send a series of information to the Bitcoin network, which could allow a correlation and deanonymization of the user himself.

My country/ISP is blocking/censoring Tor, how can I use Wasabi with Tor bridges?

WARNING

Feature not yet ported to Wasabi 2.0

Tor bridges, also called Tor bridge relays, are alternative entry points to the Tor network that are not all listed publicly. If you suspect your access to the Tor network is being blocked, you may want to use bridges. You can read more on The Tor Project's dedicated page about bridgesopen in new window.

TIP

If you are using Tor Browser Bundle it is extremely easy to configure it to use bridges. Configuring Tor bridges running in a daemon mode is more difficult and takes more time.

Steps with Tor Browser:

  1. Download and install the Tor Browseropen in new window
  2. Change the Settings of the Tor Browser to use one of the bridges or pluggable transports
  3. Leave Tor Browser running after connecting with a bridge
  4. Change the Settings of Wasabi Wallet and edit TorSocks5 Endpoint from 127.0.0.1:9050 to 127.0.0.1:9150
  5. Restart Wasabi

After this, Wasabi will connect to Tor using the Tor Browser's connection via a random bridge.

WARNING

To make use of Tor bridges on Wasabi, you must always keep Tor Browser open.

Steps with Tor Daemon on Linux:

TIP

These are commands for Debian. Feel free to edit these commands according to your distribution.

  1. Get Tor Bridgesopen in new window
  2. Install Tor daemon with sudo apt-get install tor
  3. Install OBFS4 support (needed to connect to bridges), by editing your /etc/apt/sources.list and adding this line:
# Tor Bridges
@@ -38,6 +38,6 @@
 
 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
  1. Restart Tor with sudo service tor restart and check logs with sudo tail -f /var/log/tor/log to verify that everything is working properly
- + diff --git a/FAQ/FAQ-Installation.html b/FAQ/FAQ-Installation.html index da1d1081a4..f3769f06b7 100644 --- a/FAQ/FAQ-Installation.html +++ b/FAQ/FAQ-Installation.html @@ -24,10 +24,10 @@ Installation FAQ | Wasabi Docs - + -
Wasabi Docs

Installation of Wasabi

Installing the Package

Where can I download Wasabi?

You can find the recent version of the compiled packages for Linux, Windows and Mac available on the official wasabiwallet.ioopen in new window. It's always best to download software directly from the official source acknowledged by the developers. In order to preserve your network level privacy from the very first step on, please consider visiting the Tor onion service wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onionopen in new window. The old versions of the software can be found in the releasesopen in new window of the GitHub repository, hereopen in new window you also find the libre & open source code for when you want to build it yourself. Please take special care to verify the PGP signatures of zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window over the software packages and code commits.

Why is it important to verify PGP signatures?

DANGER

Don't trust ~ verify.

These are not just empty words. Self sovereignty is at the core of Bitcoin in general, and Wasabi specifically. You have powerful tools at your disposal, yet they only work when used as they are designed. Wasabi is tailor made so that you do not have to trust anyone, but you have the power to verify everything.

With PGP signatures you can verify that the software package you download is actually the one by the developers. Every release of Wasabi is signed by zkSNACKsopen in new window, the company behind Wasabi. You can verify that the PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window is actually the one of zkSNACKsopen in new window by exploring the web of trustopen in new window. When you have a software package that was signed by this PGP public key, then you can be sure that this is an official release approved by zkSNACKs. This protects you against malicious man in the middle attacks where bad guys give you a fake version of Wasabi with malicious code.

Watch the videoopen in new window

How can I verify PGP signatures?

On the WasabiWallet.ioopen in new window website you can download the packages of the latest release. To verify the signature you also need to download the separate signature .asc file. In the terminal, change the directory to the one with the downloaded files, and verify the signature with gpg --verify + the corresponding signature file name, depending on which operating system you are.

Everything is valid if it returns Good signature from zkSNACKs and that it was signed with the Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E.

For an in-depth guide for Debian and Ubuntu, other Linux, Windows, and macOS see the main documentation.

Watch the videoopen in new window

How do I install Wasabi on Debian and Ubuntu?

Download the most recent .deb package and the .deb.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Debian

Verify the signature of the package with gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb and ensure that the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window.

Now install Wasabi with sudo apt install ./Wasabi-2.0.5.deb, and run it with wassabee. Check out the main documentation for a step-by-step guide.

Watch the videoopen in new window

How do I install Wasabi on other Linux?

Download the most recent .tar.gz package and the .tar.gz.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Linux

Verify the signature of the package with gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz and ensure that the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi with sudo tar -pxzf Wasabi-2.0.5.tar.gz, and run it with ./wassabee. Check out the main documentation for a step-by-step guide.

How do I install Wasabi on Windows?

Download the most recent .msi package and the .msi.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Windows

The Wasabi package is signed and automatically verified on Windows upon installation.

Wasabi Wallet Windows signature verification

Optionally, you can still verify the PGP signature of the package by right-clicking on the signature file > More GpgEX options > Verify and ensure the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi by double-clicking the .msi file. Check out the main documentation for a step-by-step guide.

How do I install Wasabi on macOS?

Download the most recent .dmg package and the .dmg.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for macOS

The Wasabi package is signed and automatically verified on macOS upon installation.

Optionally, you can still verify the PGP signature of the package with sudo gpg2 --verify Wasabi-2.0.5.dmg.asc and ensure that the software has been signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi by double-clicking the .dmg file. Check out the main documentation for a step-by-step guide.

Watch the videoopen in new window

Why are there two different packages for macOS (intel and Apple Silicon)?

Intel and Apple Silicon are two different processors types that Apple uses for their computers. These processors work a bit differently from each other. With the architecture that Wasabi uses, these two different processors need their own specific code binary in order to make it work.

What happens when I install the wrong package for macOS?

Wasabi will crash on startup or run significantly slower than it should. This will not harm your computer.

Do I need to install Tor separately?

No, because Wasabi has Tor built into the software. All Wasabi network traffic goes via Tor by default - no need to set up Tor yourself.

You can turn off Tor in the Settings. Be careful, as this will compromise your privacy. When you coinjoin over clearnet, the coordinator would know the links between your inputs and outputs based on your IP address. When you broadcast a transaction over clearnet, the connected full node will know the link between your transaction and your IP address.

Can I use Wasabi on Tails?

No, it is not possible to install Wasabi on Tails, because Wasabi uses the Tor control port, which is not exposed in this operating system.

Can I use Wasabi on Whonix?

No, it is not possible to install Wasabi on Whonix, because Wasabi uses the Tor control port, which is not exposed in this operating system.

What are the differences between the Debian/Ubuntu version and the "Other Linux" version?

Debian/Ubuntu version contains .deb package. Other Linux version contains .tar.gz package.

The advantages of the .deb format is solely packaging related. It installs Wasabi in your computer, so you're able to access it from start menu, remove it through apt, and so on.

The "Other Linux" option is just a generic install method not targeted to Debian/Ubuntu specifically but that works on it anyway because it is still linux.

There's no difference in the code, the same binaries are being delivered in different formats.

Update Wasabi

Why should I update Wasabi?

Wasabi is cutting edge software and is being worked on by the developers on a daily basis. Once in a while (+- every month) all the changes/improvements are being released in a new Wasabi version. The changes can contain (critical) bug fixes, small improvements, new features etc. It's always a good idea to run (one of) the latest Wasabi versions.

How do I check the current version of Wasabi?

In the GUI, go to the SearchBar at the top of the screen and click on About Wasabi. Here the current version of your Wasabi is displayed. Wasabi is cutting edge software, so it is well-advised to stay up-to-date.

How do I know about a new version of Wasabi?

When a new major version [v2.X.X] has been released, you'll see an orange update icon in the bottom right, upon hovering over it you can see Version 2.X.X is now available.

Wasabi Update Available

Clicking on Update uses the default browser to go to the website, where you can download this new version. There are occasional silent releases like [v2.X.X.X] which fix small issues, and these are not announced in the GUI, so you will not see the orange update icon. The websiteopen in new window always contains the most recent version. All releases (major and minor) are announced on the social media like Twitteropen in new window and Redditopen in new window.

How do I securely upgrade Wasabi?

To upgrade Wasabi, you need to download the new version. Downloading and installing the newer Wasabi package will overwrite the previous one, while preserving your files like your wallets etc. So to upgrade Wasabi, simply download and install the new version like at first install.

You can download the software build for the different operating systems on the main websiteopen in new window or better over Toropen in new window. For extra security, it is reccommended to also download the signatures of the build and verify them with zkSNACKs' PGP public keyopen in new window. For step-by-step instructions, follow this guide or see this video: Watch the videoopen in new window

What does Auto download new version in the settings mean?

If enabled, the software will automatically download the new version's installer upon a new release. If disabled, the software will only signal, but not automatically download, that there is a new version available.

Auto download new version is currently only available for Windows and macOS

For Linux, this setting does not work. A new version will have to be installed manually.

How does the Auto download new version work?

The software will automatically download the new version's installer upon a new release. After it is downloaded, the user can press "Update on Close" to run the installer when closing Wasabi. The installer is downloaded from GitHubopen in new window.

Advanced Installation

How do I compile Wasabi from source?

If you cannot wait until the next release, and you want to experience the most cutting-edge version of Wasabi, then you can build the source code.

The only two required tools are Gitopen in new window and .NET 7.0 SDKopen in new window for "Build apps". You can download every line of the Wasabi code by git clone https://github.com/zkSNACKs/WalletWasabi.git, this will create a new directory called WalletWasabi. In order to build and run the Wallet software, change directory to cd WalletWasabi/WalletWasabi.Fluent.Desktop. Wasabi is written in C# with the .NET framework, and it is very easy to run it. Simply execute dotnet run from the WalletWasabi.Fluent.Desktop folder. You can update the master branch with git pull.

How can I verify the deterministic build?

The guide for the deterministic builds can be found in the WalletWasabi repositoryopen in new window.

My antivirus marks Wasabi Wallet as a virus. Am I downloading the right software?

After you have downloaded Wasabi from the official websiteopen in new window or from the official GitHub repositoryopen in new window, make sure you have verified the PGP signatures.

If you have downloaded and verified digital signatures and your antivirus continues to report Wasabi as positive, you don't have to worry about anything; it is a false positive.

If you are still not sure, before starting Wasabi, you can check that it is safe by uploading and scan it via VirusTotalopen in new window.

TIP

Remember to report Wasabi as a safe software/false positive to your antivirus. In doing so you will help users who use the same antivirus.

Why is the executable called wassabee?

The most obvious thing would be to call the executable Wasabi Wallet.exe on Windows and Wasabi Wallet on Linux and Mac.

However launching Wasabi Wallet from certain terminals/command lines is problematic, so we should remove the spacing: WasabiWallet, and the case sensitivity differences between the operating systems can also cause issues, so that must go too: wasabiwallet.

But it's too long, it needs a faster way to launch: wasabi.

However this is too generic, it'll certainly cause conflicts, we need to make it unique: wassabee.

Also, this sounds awesome and is a fun inside jokeopen in new window.

- +
Wasabi Docs

Installation of Wasabi

Installing the Package

Where can I download Wasabi?

You can find the recent version of the compiled packages for Linux, Windows and Mac available on the official wasabiwallet.ioopen in new window. It's always best to download software directly from the official source acknowledged by the developers. In order to preserve your network level privacy from the very first step on, please consider visiting the Tor onion service wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onionopen in new window. The old versions of the software can be found in the releasesopen in new window of the GitHub repository, hereopen in new window you also find the libre & open source code for when you want to build it yourself. Please take special care to verify the PGP signatures of zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window over the software packages and code commits.

Why is it important to verify PGP signatures?

DANGER

Don't trust ~ verify.

These are not just empty words. Self sovereignty is at the core of Bitcoin in general, and Wasabi specifically. You have powerful tools at your disposal, yet they only work when used as they are designed. Wasabi is tailor made so that you do not have to trust anyone, but you have the power to verify everything.

With PGP signatures you can verify that the software package you download is actually the one by the developers. Every release of Wasabi is signed by zkSNACKsopen in new window, the company behind Wasabi. You can verify that the PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window is actually the one of zkSNACKsopen in new window by exploring the web of trustopen in new window. When you have a software package that was signed by this PGP public key, then you can be sure that this is an official release approved by zkSNACKs. This protects you against malicious man in the middle attacks where bad guys give you a fake version of Wasabi with malicious code.

Watch the videoopen in new window

How can I verify PGP signatures?

On the WasabiWallet.ioopen in new window website you can download the packages of the latest release. To verify the signature you also need to download the separate signature .asc file. In the terminal, change the directory to the one with the downloaded files, and verify the signature with gpg --verify + the corresponding signature file name, depending on which operating system you are.

Everything is valid if it returns Good signature from zkSNACKs and that it was signed with the Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E.

For an in-depth guide for Debian and Ubuntu, other Linux, Windows, and macOS see the main documentation.

Watch the videoopen in new window

How do I install Wasabi on Debian and Ubuntu?

Download the most recent .deb package and the .deb.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Debian

Verify the signature of the package with gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb and ensure that the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window.

Now install Wasabi with sudo apt install ./Wasabi-2.0.5.deb, and run it with wassabee. Check out the main documentation for a step-by-step guide.

Watch the videoopen in new window

How do I install Wasabi on other Linux?

Download the most recent .tar.gz package and the .tar.gz.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Linux

Verify the signature of the package with gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz and ensure that the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi with sudo tar -pxzf Wasabi-2.0.5.tar.gz, and run it with ./wassabee. Check out the main documentation for a step-by-step guide.

How do I install Wasabi on Windows?

Download the most recent .msi package and the .msi.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for Windows

The Wasabi package is signed and automatically verified on Windows upon installation.

Wasabi Wallet Windows signature verification

Optionally, you can still verify the PGP signature of the package by right-clicking on the signature file > More GpgEX options > Verify and ensure the software was signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi by double-clicking the .msi file. Check out the main documentation for a step-by-step guide.

How do I install Wasabi on macOS?

Download the most recent .dmg package and the .dmg.asc signature file from the wasabiwallet.ioopen in new window or the Tor onion serviceopen in new window.

Download Wasabi Wallet for macOS

The Wasabi package is signed and automatically verified on macOS upon installation.

Optionally, you can still verify the PGP signature of the package with sudo gpg2 --verify Wasabi-2.0.5.dmg.asc and ensure that the software has been signed by zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window. Now install Wasabi by double-clicking the .dmg file. Check out the main documentation for a step-by-step guide.

Watch the videoopen in new window

Why are there two different packages for macOS (intel and Apple Silicon)?

Intel and Apple Silicon are two different processors types that Apple uses for their computers. These processors work a bit differently from each other. With the architecture that Wasabi uses, these two different processors need their own specific code binary in order to make it work.

What happens when I install the wrong package for macOS?

Wasabi will crash on startup or run significantly slower than it should. This will not harm your computer.

Do I need to install Tor separately?

No, because Wasabi has Tor built into the software. All Wasabi network traffic goes via Tor by default - no need to set up Tor yourself.

You can turn off Tor in the Settings. Be careful, as this will compromise your privacy. When you coinjoin over clearnet, the coordinator would know the links between your inputs and outputs based on your IP address. When you broadcast a transaction over clearnet, the connected full node will know the link between your transaction and your IP address.

Can I use Wasabi on Tails?

No, it is not possible to install Wasabi on Tails, because Wasabi uses the Tor control port, which is not exposed in this operating system.

Can I use Wasabi on Whonix?

No, it is not possible to install Wasabi on Whonix, because Wasabi uses the Tor control port, which is not exposed in this operating system.

What are the differences between the Debian/Ubuntu version and the "Other Linux" version?

Debian/Ubuntu version contains .deb package. Other Linux version contains .tar.gz package.

The advantages of the .deb format is solely packaging related. It installs Wasabi in your computer, so you're able to access it from start menu, remove it through apt, and so on.

The "Other Linux" option is just a generic install method not targeted to Debian/Ubuntu specifically but that works on it anyway because it is still linux.

There's no difference in the code, the same binaries are being delivered in different formats.

Update Wasabi

Why should I update Wasabi?

Wasabi is cutting edge software and is being worked on by the developers on a daily basis. Once in a while (+- every month) all the changes/improvements are being released in a new Wasabi version. The changes can contain (critical) bug fixes, small improvements, new features etc. It's always a good idea to run (one of) the latest Wasabi versions.

How do I check the current version of Wasabi?

In the GUI, go to the SearchBar at the top of the screen and click on About Wasabi. Here the current version of your Wasabi is displayed. Wasabi is cutting edge software, so it is well-advised to stay up-to-date.

How do I know about a new version of Wasabi?

When a new major version [v2.X.X] has been released, you'll see an orange update icon in the bottom right, upon hovering over it you can see Version 2.X.X is now available.

Wasabi Update Available

Clicking on Update uses the default browser to go to the website, where you can download this new version. There are occasional silent releases like [v2.X.X.X] which fix small issues, and these are not announced in the GUI, so you will not see the orange update icon. The websiteopen in new window always contains the most recent version. All releases (major and minor) are announced on the social media like Twitteropen in new window and Redditopen in new window.

How do I securely upgrade Wasabi?

To upgrade Wasabi, you need to download the new version. Downloading and installing the newer Wasabi package will overwrite the previous one, while preserving your files like your wallets etc. So to upgrade Wasabi, simply download and install the new version like at first install.

You can download the software build for the different operating systems on the main websiteopen in new window or better over Toropen in new window. For extra security, it is reccommended to also download the signatures of the build and verify them with zkSNACKs' PGP public keyopen in new window. For step-by-step instructions, follow this guide or see this video: Watch the videoopen in new window

What does Auto download new version in the settings mean?

If enabled, the software will automatically download the new version's installer upon a new release. If disabled, the software will only signal, but not automatically download, that there is a new version available.

Auto download new version is currently only available for Windows and macOS

For Linux, this setting does not work. A new version will have to be installed manually.

How does the Auto download new version work?

The software will automatically download the new version's installer upon a new release. After it is downloaded, the user can press "Update on Close" to run the installer when closing Wasabi. The installer is downloaded from GitHubopen in new window.

Advanced Installation

How do I compile Wasabi from source?

If you cannot wait until the next release, and you want to experience the most cutting-edge version of Wasabi, then you can build the source code.

The only two required tools are Gitopen in new window and .NET 8.0 SDKopen in new window for "Build apps". You can download every line of the Wasabi code by git clone https://github.com/zkSNACKs/WalletWasabi.git, this will create a new directory called WalletWasabi. In order to build and run the Wallet software, change directory to cd WalletWasabi/WalletWasabi.Fluent.Desktop. Wasabi is written in C# with the .NET framework, and it is very easy to run it. Simply execute dotnet run from the WalletWasabi.Fluent.Desktop folder. You can update the master branch with git pull.

How can I verify the deterministic build?

The guide for the deterministic builds can be found in the WalletWasabi repositoryopen in new window.

My antivirus marks Wasabi Wallet as a virus. Am I downloading the right software?

After you have downloaded Wasabi from the official websiteopen in new window or from the official GitHub repositoryopen in new window, make sure you have verified the PGP signatures.

If you have downloaded and verified digital signatures and your antivirus continues to report Wasabi as positive, you don't have to worry about anything; it is a false positive.

If you are still not sure, before starting Wasabi, you can check that it is safe by uploading and scan it via VirusTotalopen in new window.

TIP

Remember to report Wasabi as a safe software/false positive to your antivirus. In doing so you will help users who use the same antivirus.

Why is the executable called wassabee?

The most obvious thing would be to call the executable Wasabi Wallet.exe on Windows and Wasabi Wallet on Linux and Mac.

However launching Wasabi Wallet from certain terminals/command lines is problematic, so we should remove the spacing: WasabiWallet, and the case sensitivity differences between the operating systems can also cause issues, so that must go too: wasabiwallet.

But it's too long, it needs a faster way to launch: wasabi.

However this is too generic, it'll certainly cause conflicts, we need to make it unique: wassabee.

Also, this sounds awesome and is a fun inside jokeopen in new window.

+ diff --git a/FAQ/FAQ-Introduction.html b/FAQ/FAQ-Introduction.html index df1872b035..ba4840acbd 100644 --- a/FAQ/FAQ-Introduction.html +++ b/FAQ/FAQ-Introduction.html @@ -24,10 +24,10 @@ Introduction FAQ | Wasabi Docs - +
Wasabi Docs

Introduction to Wasabi

The Basics

Who can use Wasabi?

Every single line of code in Wasabi, the walletopen in new window, the backend serveropen in new window, the daemonopen in new window, the testsopen in new window, the packageropen in new window, the libraryopen in new window, the apiopen in new window, the documentationopen in new window - has always been and will always be libre and open-source under the MIT licenseopen in new window. This means that anyone, yes, ANYONE can use Wasabi without permission, for any use case, free of charge.

Wasabi is used by individuals to make everyday payments, to manage their hardware wallet long term hodlings, and to CoinJoin their sats for added privacy. Entrepreneurs may use Wasabi to defend their customers from spies and to ensure a private business relationship. While kids may use Wasabi to stack the sats gifted by grandma, and learn the importance of hodling.

TIP

Wasabi is a tool for everyone.

What is a coinjoin?

Coinjoin is a mechanism by which multiple participants combine their coins (or UTXOs, to be more precise) into one large transaction with multiple inputs and multiple outputs. An observer cannot determine which output belongs to which input, and neither can the participants themselves. This makes it difficult for outside parties to trace where a particular coin originated from and where it was sent to (as opposed to regular bitcoin transactions, where there is usually one sender and one receiver).

This can be done with non-custodial software like Wasabi that eliminates the risk of funds disappearing or being stolen. Each of the signatures are created on the participants’ computers after thorough verification, so nobody can alter the transaction or redirect the funds. The funds will always be in a Bitcoin address that you control.

In very simple terms, coinjoin means: “when you want to make a transaction, find someone else who also wants to make a transaction and make a joint transaction together”.

See also the Bitcoin Wiki on coinjoinsopen in new window

Do I need to trust Wasabi with my coins?

Since Wasabi's coinjoin implementation is trustless by design, there is no need for participants to trust each other or a third party. Both the sending address (the coinjoin input) and the receiving address (the coinjoin output) are controlled by your own private keys. The Wasabi server merely coordinates the process of combining each participant's input into one single transaction, but the Wasabi Wallet can neither steal your coins, nor figure out which outputs belong to which inputs (look up “WabiSabi coinjoin” if you want to know more).

What is the privacy I get after mixing with Wasabi?

This depends on how you handle your outputs after the coinjoin. There are some ways how you can unintentionally undo the mixing by being careless. For example, if you send a mixed coin to an already used address, then anyone can see that both coins are controlled by the same entity. More importantly, anyone who knows that the address belongs to you knows that you own that mixed coin. Address reuse compromises your privacy. Another deanonymizing scenario occurs when you combine mixed outputs with unmixed ones when sending: a third party will be able to make the connection between them as belonging to the same sender. This is why you need to be careful with non-private/change coins.

The practice of being careful with your post-mix outputs is commonly facilitated through coin control. Find out more about coin control in here. However, Wasabi Wallet is build in a way to help the user to avoid privacy leaks when using the wallet.

Why is Wasabi Bitcoin-only?

There are countless reasons why it is the only logical choice to be bitcoin-only. With Bitcoin we have a once in a lifetime opportunity to manifest libre sound money. If we succeed, then an utmost beautiful agora of sovereign individuals may emerge. If we fail, then this will conjure up the most horrific Orwellian nightmare. There is no room for wasted time and energy, this great work requires our full attention. Any line of code written to support a random shitcoin takes away scarce developer time to work on real problems.

What is considered a sufficient anonymity score?

It is difficult to determine a sufficient anonymity score since enough research hasn’t been conducted to provide a definitive answer. The right anonymity score depends on your own personal threat model. However, to be on the safe side, with Wasabi Wallet 2.0 an anonymity score of 5 and above could be considered sufficient.

Is there a way to check Wasabi's uptime status?

Yes, you can check the status of Wasabi-related services and websites (like APIs, Backend, etc.) via UptimeRobot Wasabi Status Pageopen in new window.

What software supplies the block filters that Wasabi uses?

The zkSNACKs coordinator supplies identical filters to every client. This means that you rely on the Wasabi backendopen in new window to provide valid filters. But because you download the blocks from a random Bitcoin peer-to-peer node - or your own node - the coordinator cannot spy on which blocks you are interested in. Furthermore, the random node will only know which block is needed but it won't have any clue which transaction(s) belongs to the wallet.

Is the Backend's (Coordinator) code open-source?

Yes, you can verify the code on GitHubopen in new window.

Is there an Android/iOs version?

No, Wasabi and CoinJoin features require considerable computational power, not currently replicable on a smartphone.

Where can I find Wasabi Wallet on social media?

You can find us on Twitteropen in new window, Redditopen in new window, YouTubeopen in new window, Facebookopen in new window, Instagramopen in new window and Discordopen in new window. For chat groups you can find us on Slackopen in new window, Telegramopen in new window and Keybaseopen in new window.

Also, remember to follow our blogopen in new window to get the latest insights and information about Wasabi Wallet and Bitcoin privacy.

For advanced Wasabikas

Can the coordinator attack me?

The developers have gone to great lengths to ensure that the coordinator cannot steal funds nor link inputs to outputs. The nature of Wasabi is that you should not need to trust the developers or the Wasabi coordinating server, as you can verify that the code does not leak information to anyone. Due to the nature of coinjoin transactions users don't need to trust other users or the coordinator against theft, leaving denial of service and attacks on privacy as the main concerns

The only known possible 'malicious' actions that the server could perform are two sides of the same coin;

  • Blacklisted UTXO's: Though this would not affect the users who are able to successfully mix with other 'honest/real' peers.
  • Targeted Sybil Attack: The follow-up concern is the inverse of the above. It is possible that the server could only include one 'honest/real' coin in the mix and supply the other coins themselves. This gives a false sense of security, but does not worsen the existing privacy of the coin. It would also be noticeable to all users excluding the user being targeted as their coins would not be mixed. It has been argued that this 'attack' would be very costly in terms of fees because the number of coins being mixed is verifiable. Though it is true that remixes pay zero coordination fee to zkSNACKs, they do pay mining fees. See hereopen in new window for more info.

What is the history of Wasabi?

Ádám Ficsor worked with several others on a privacy-focused Bitcoin wallet called Hidden Wallet all the way back in December 2015open in new window. Wasabi 1.0 was unveiled in 2018 at the Building on Bitcoin conference by Ádám. At the time, Wasabi was essentially HiddenWallet rebranded and rewritten from scratch with some new features. Key dates:

  • The 1.0 Beta release was on August 1, 2018 (on the first anniversary of UASF)
  • The 1.0 release was on October 31, 2018 (on the tenth anniversary of the Bitcoin Whitepaper)
  • The 2.0 Testnet release was on March 1, 2022
  • The 2.0 release was on June 15, 2022

Watch the videoopen in new window

Watch the videoopen in new window

Why is Wasabi libre and open-source software?

Wasabi follows Bitcoin's philosophy by making the software open-sourceopen in new window and by publishing it under MIT licenseopen in new window. Bitcoin users prefer open-source software to proprietary software for a number of reasons, including:

Control

Many people prefer open-source software because they have more control over the software they run.

They can examine the code to make sure it's not doing anything they don't want it to do, and they can change parts of it they don't like. Users who aren't programmers also benefit from open-source software, since they can use this software for any purpose.

Training

Other people like open-source software because it helps them become better programmers.

Open-source code is publicly accessible. Students can easily study it as they learn to make better software. Students can also share their work with others, inviting comments and critique, as they develop their skills. When people discover mistakes in programs' source code, they can share those mistakes with others to help them avoid making those same mistakes themselves.

Security

Some people prefer open-source software because they consider it more secure and stable than proprietary software.

Anyone can view and modify open-source software. Other users may spot and correct errors or omissions that a program's original authors might have missed. And because so many programmers can work on a piece of open-source software without asking for permission from original authors, they can fix, update, and upgrade open-source software more quickly than they can proprietary software.

Stability

Many users prefer open-source software to proprietary software for important, long-term projects.

Programmers publicly distribute the source code for open-source software. Users relying on that software for critical tasks can be sure their tools won't disappear or fall into disrepair if their original creators stop working on them. Additionally, open-source software tends to both incorporate and operate according to open standards.

What is the general idea of WabiSabi coinjoin?

While fungibility is an essential property of good money, Bitcoin has its limitations in this area. Numerous fungibility improvements have been proposed; however, none of them have addressed the privacy issues in full. WabiSabi is designed so that no participant, outside observer or even the coordinator can spy on the user. The scope of WabiSabi is not limited to a single transaction, it extends to transaction chains and it addresses various network layer deanonymizations. However, its scope is limited to Bitcoin's first layer. Even if an off-chain anonymity solution gets widely adopted, ultimately the entrance and exit transactions will always be settled on-chain. Therefore, there will always be need for on-chain privacy.

Ideal fungibility requires every Bitcoin transaction to be indistinguishable from each other, but it is an unrealistic goal. WabiSabi's objective is to break all links between coins. Thus, WabiSabi enables the usage of Bitcoin in a fully anonymous way.

WabiSabi defines a pre-mix and a post-mix wallet and a mixing technique. Pre-mix wallet functionality can be added to any Bitcoin wallet without much overhead. Post-mix wallets on the other hand have strong privacy requirements, regarding coin selection, private transaction and balance retrieval, transaction input and output indexing and broadcasting. The requirements and recommendations for pre and post-mix wallets together define the Wallet Privacy Framework. Coins from pre-mix wallets to post-mix wallets are moved by mixing. Most on-chain mixing techniques, like CoinShuffle, CoinShuffle++, TumbleBit's Classic Tumbler mode, or ZeroLink can be used. However WabiSabi defines its own mixing technique: WabiSabi coinjoin.

For more info please see WabiSabiopen in new window.

What are the supported operating systems?

Wasabi runs in most operating systems with 64-bit architecture. For the complete list of all the officially supported operating systems, click hereopen in new window.

What are the minimal requirements to run Wasabi?

As long as your operating system is supportedopen in new window, Wasabi should be able to run on your hardware. The more transactions a wallet has made, the more resources Wasabi will consume, particularly RAM. The software can also consume a significant amount of CPU for specific tasks, such as coinjoins or wallet loading. Approximately 3 GB of disk space are also needed, mainly to store the block filters. If you are running the wallet on a system with scarce resources, consider using the daemonopen in new window instead of the GUI application.

- + diff --git a/FAQ/FAQ-UseWasabi.html b/FAQ/FAQ-UseWasabi.html index 95b1cdd23f..f107c57f01 100644 --- a/FAQ/FAQ-UseWasabi.html +++ b/FAQ/FAQ-UseWasabi.html @@ -24,7 +24,7 @@ Use of Wasabi FAQ | Wasabi Docs - +
Wasabi Docs

Use of Wasabi

General

How do I start using Wasabi?

  1. Download & Install Wasabi (like with any other software) from the official websiteopen in new window.
  2. Create a new wallet or use an already existing one, by importing or recovering your own wallet.
  3. Receive some bitcoin.
  4. Wait, and let the wallet do some coinjoins. Your wallet's privacy progress % will increase.
  5. Enjoy your private bitcoin funds! Spend some, send to your hardware wallet (for cold storage) or leave them in Wasabi for a while.

How do I generate a new wallet?

You can generate as many new wallets as you'd like, for no extra cost and without asking for permission.

Click the Add Wallet button in the bottom left corner of the main view or in the searchbar.

Add new wallet in Wasabi

Click Create a new wallet.

Create a new wallet in Wasabi

As with everything in Wasabi, you are required to label this new wallet. Make sure that you are precise so that you know what this wallet is for and click Continue.

Name a new wallet in Wasabi

Now you will see the 12 recovery words. This is the mnemonic seed that you should back up, together with the password you create in the next phase, in order to recover your wallet. When you've backed everything up, click Continue.

Wasabi Wallet recovery words

In this page you should confirm the words, as a check that you've written down your mnemonic seed in the correct order. Once you're done, click Continue.

Confirm recovery words

Add a password. It is used to encrypt the private key (extracted from the extended private key) on the computer and needed to open the wallet and to recovered it in the future. Make sure that you properly back up and write down this password.

Confirm the password and click Continue.

Add a password in Wasabi

Careful!!

Without knowledge of the password, you CANNOT spend your bitcoin!!

Make sure, and triple-check that you have done a proper backup of BOTH the password AND the mnemonic. If you only have the recovery words, but not the password, then you will NOT be able to open your wallet or to recover it.

In order to protect your backup, consider storing the password and recovery words in different locations.

Now you get to choose your wallets coinjoin strategy. Select one and click Continue.

Wasabi Wallet coinjoin strategies

Can I rename my Wallet?

Yes, but not in the GUI, you'd need to manually rename the wallet file. Type Wallet Folder in the search bar at the top of the main view to access the Wallets folder and rename the .json wallet file. Or you can navigate to the Wallets folder (inside the Wasabi data folder) and rename the .json wallet file. Then go to WalletBackups folder (inside the Wasabi data folder) and rename the .json wallet file.

TIP

You need to mark the “show hidden files” setting to see the Wasabi data folder.

WARNING

To avoid problems, make sure you close Wasabi Wallet before proceeding to rename any of your wallets.

What is the password used for?

The password you set is used:

Wasabi stores only the BIP38 encrypted blob, so you'll need to type in the password to open the wallet and to spend from Wasabi.

DANGER

The password will unlock your bitcoin to anyone who has access to the recovery words backup or the computer! If your backup gets compromised, this password is the only thing protecting your precious sats.

What password should I use?

DANGER

It is VERY important to use a random and long password.

Since it is very difficult for humans to generate true randomness, it is good to use a tool to help find a strong password. This can be the Diceware english wordlistopen in new window for true off-line password generation. A secure password manager software might also be used, but be careful here.

Where can I find the Wasabi data folder?

You can easily reach it from inside Wasabi by typing Data Folder in the search bar at the top of the main view.

Or you can manually navigate to it (depending on which OS you have):

  • Windows: /Users/{your username}/AppData/Roaming/WalletWasabi/Client
  • Linux: /home/{your username}/.walletwasabi/client
  • macOS: /Users/{your username}/.walletwasabi/client

TIP

You need to mark the “show hidden files” setting to see it.

Can I spend my bitcoin without the password?

DANGER

NO!!! Without knowledge of your password, even when you have the wallet file and recovery words, you CANNOT spend your bitcoin!

When creating a new wallet, after labeling it properly, the next step is to select a long and random password. Every time you want to spend your coins from Wasabi, you MUST provide this password. So even if you have these words securely engraved in metal, without the password, you cannot restore the backup of your wallet.

TIP

Always back up your mnemonic recovery words, and your password in two separate secure locations.

Why BIP 38?

BIP 38open in new window is a good standard, a well-tested and very secure way to encrypt a private key. It is also implemented in the NBitcoin libraryopen in new window, which is used by Wasabi. Additionally, there is no standard way (BIP) to encrypt HD wallets. Take into account that it is not only encryption what BIP 38 provides but also a brute-force protection.

What are the terms and conditions?

The most important parts of the legal documents are summarized in the following points:

  • The service is open-source under the MIT license.
  • The service is provided on a non-custodial basis. Safekeeping of keys are the sole responsibility of the user.
  • The user is solely responsible to act according to their local laws and regulations.
  • We do not store any personally identifiable information. Moreover, our trustless software architecture prevents us from gathering this information in the first place.
  • A transaction fee is only charged by the service provider for CoinJoin transactions.
  • We only provide written support, and NEVER ask for recovery words, passwords or similar security critical information.

Read the whole document of terms and conditions, privacy policy, and legal statement hereopen in new window

Can I import a watch-only extended public key?

Yes, but not yet in the GUI, you will need to manually create a new wallet file.

Open a text editor and paste the following wallet structure:

{
@@ -70,6 +70,6 @@
                       0.3 BTC (Change Coin Charlie)

There is no way to know which of the anon set output coins are owned by which of the input owners.

All an observer knows is that a specific anon set output coin is owned by one of the owners of one of the input coins, that is 3 people - hence an anonymity set of 3.

Your Wasabi software has limited information on what the actually achieved anonymity set is, so the anonymity set that the software presents you is just an estimation, not an accurate value. With Wasabi we are trying to do lower estimations, rather than higher ones.

What is the anonymity score?

The anonymity score is a way to estimate the level of entropy of a UTXO in an unequal-but-highly-composable output value coinjoin.

It is different than anonymity set. For example, if the outputs are [1, 1, 1, 1, 0.5, 0.5, 0.5, 0.5, 0.4, 0.4, 0.2, 0.2, 0.2, 0.2, 0.2, 0.1, 0.1, 0.1, 0.1, 0.1] then, even when each of those 1s have anonscore 4, there are still lots of combinations of outputs that sum up to 1, so the anonset should be much higher but the anonscore is extremely conservative and takes into account many other things.

What is the difference between anonymity set and anonymity score?

The anonscore evolved into existence from the anonset, but with some differences. What differs is the kind of coinjoins they are applied to, where anonset was for Wasabi 1 and anonscore is for current Wasabi 2. In Wasabi 1 coinjoins there are unequal inputs, some equal outputs, and change coins. In Wasabi 2 coinjoins there are many equal inputs, many equal outputs, and (sometimes) some unique value outputs, that are not necessarily change coins. In fact most of the times they are well mixed coins.

Basically the anonymity score is an extremely conservative anonymity set calculation.

What are the equal denominations created in a coinjoin round?

The standard denominations are: 5000, 6561, 8192, 10000, 13122, 16384, 19683, 20000, 32768, 39366, 50000, 59049, 65536, 100000, 118098, 131072, 177147, 200000, 262144, 354294, 500000, 524288, 531441, 1000000, 1048576, 1062882, 1594323, 2000000, 2097152, 3188646, 4194304, 4782969, 5000000, 8388608, 9565938, 10000000, 14348907, 16777216, 20000000, 28697814, 33554432, 43046721, 50000000, 67108864, 86093442, 100000000, 129140163, 134217728, 200000000, 258280326, 268435456, 387420489, 500000000, 536870912, 774840978, 1000000000, 1073741824, 1162261467, 2000000000, 2147483648, 2324522934, 3486784401, 4294967296, 5000000000, 6973568802, 8589934592, 10000000000, 10460353203, 17179869184, 20000000000, 20920706406, 31381059609, 34359738368, 50000000000, 62762119218, 68719476736, 94143178827, 100000000000, 137438953472 sats.

So, there are 79 denominations from 0.00005000 BTC up to 1374.38953472 BTC.

What is happening in the input registration phase?

During this phase the client selects which coin(s) will be registered for coinjoin. Wasabi then generates the related input proofs. After that, a unique Tor identity will be generated for each input, which will be used to send the input ownership proof to the coordinator.

The coordinator now verifies that this input is allowed to register (i.e. there is still room for more inputs, the coin is confirmed, the input proof is valid etc.). If all checks are valid, the coordinator creates and sends back the credentials.

Since the goal is to have at least 150 inputs in one round, the input registration phase can fail if too few participants registered in the available time frame.

What is happening in the connection confirmation phase?

Because the input registration phase takes some time, the coordinator needs to ensure that everyone is still online and ready to continue. So in the connection confirmation phase every Alice sends a signal to the coordinator that she is still online, and when all Alices do so, or after a timeout and the number of online Alices is still larger than the minimum number of inputs, this phase ends.

What is happening in the output registration phase?

In this phase, every client needs to change the value of their credentials to the desired output values. For example, the client presents to the coordinator two old credentials and two newly created ones. The two pairs sum up to the exact same value, which the coordinator can verify, without knowing the amount value of the credentials. This process may repeat multiple times.

The client now creates a new Tor identity called Bob, which is not tied to Alice. Bob now sends the coordinator an unblinded credential (signed by the coordinator) and a bitcoin address.

What is happening in the signing phase?

After all inputs and outputs are registered, the coordinator has all the information to build the coinjoin transaction. This raw (unsigned) transaction is sent to all Alices, each of them verifies that the transaction is valid and then signs it. The signatures are sent back to the coordinator who accumulates all of them. The singing phase is concluded when the coordinator receives all the valid signatures for all registered inputs.

What is happening during the blame round?

If the signing phase fails from becoming successful due to some Alices disrupting the round, then a blame round will be created with the successful Alices. In the blame round a new coinjoin will be constructed by repeating the coinjoin phases. All Alices have to sign this new transaction and send their signature to the coordinator.

What is happening in the broadcasting phase?

In the broadcasting phase the coordinator sends the signed final CoinJoin transaction to several random Bitcoin peer to peer nodes, and it is gossiped throughout the network to the miners.

Is there any additional anonymity using multiple wallets for CoinJoins?

You'd gain 1 less anonymity set than if you'd only mix with one wallet (and Wasabi doesn't display that). On the other hand, the systemic anonymity is slightly improved if a few people are mixing with multiple wallets, because that removes the certainty on this Blockchain analysis assumption.

How is the anonymity set target determined for CoinJoins?

2*2 = 4 and 3*3 = 9. 2->3: 50% increase, 4->9:125% increase. So remixing with larger anonsets is exponentially more effective than smaller anonsets. Regarding why do we want 100 number, is among some other reasons, because that was our calculation to be that would make rounds happen in every 2-5 minutes, considering the liquidity of some custodial mixers. Regarding DoS attack, right now our DoS configuration is set to be pretty permissive and this seems to be sufficient for the time being. If a DoS attack would happen, Wasabi team would just harden it in the config file and would kick the bad actors out. Now if even that would fail, then we can start thinking about lowering the required peers and also other methods.

I'd like to experience coinjoin but I'm not comfortable using real Bitcoin. What can I do?

You can try to make a coinjoin via Wasabi on the Bitcoin TestNet (an alternative Bitcoin network, to be used for testing). Go to Settings > Bitcoin and change the network to TestNet. Then restart your Wasabi and create a new wallet, this is needed because Wasabi differentiates between "Main wallets" and "TestNet wallets". This wallet will synchronize for the TestNet, and generate TestNet addresses. You can get tBTC from faucets like: coinfaucet.eu/en/btc-testnetopen in new window or bitcoinfaucet.uo1.netopen in new window

Does Wasabi have to stay on during coinjoin?

Yes, Wasabi needs to stay on during coinjoins, you cannot be offline and still participate in coinjoins.

A coinjoin transaction is different from a normal transaction (where you are the only person signing), as it requires multiple participants to sign the same transaction.

Here is how Wasabi handles different scenarios:

During input registration phaseAfter input registration phase
You close WasabiYour registered coins are automatically dequeuedWasabi will make you wait until the round finishes
Wasabi goes offlineYour registered coins are automatically timed out by the coordinator after 1 minuteThe coin(s) that disrupted the round will be banned for 6h from participating in another coinjoin. (This is to prevent DoS attacksopen in new window)

What if there's a power outage during CoinJoin? Do I lose my coins?

No you don't. CoinJoins are atomic, they either happen or they don't. If your wallet crashes or your computer goes offline during CoinJoin you simply don't participate in this CoinJoin, look at table here for more info.

How much anonymity set do I need?

The amount of privacy needed depends on your individual threat model, who is trying to deanonymize you? It is commonly said that an anonymity set of 50 is sufficient to evade low-level blockchain forensics analysis, but it might not protect you against large adversaries. At least one round to re-mix your coins can increase your privacy drastically. With Wasabi this can be achieved in a matter of hours.

How does my wallet communicate with the Wasabi coordinator server?

Wasabi communicates in many ways to the coordinator server, and it is always over the Tor network.

First of all, Wasabi uses BIP 158 block filtersopen in new window to ensure network level privacy. You can follow these FAQs to have a full explanation on the theme:

Then, there are five different phases in a CoinJoin. You can follow these links to have a full explanation on that:

  1. Input registration phase
  2. Connection confirmation phase
  3. Output registration phase
  4. Signing phase
  5. Broadcasting phase

The backend server also sends you information about the current mempool for fee estimation as well as the US Dollar exchange rate.

What is the address of the coordinator?

The coordinator possibly gets paid in every coinjoin. Wasabi is using a fresh unused coordinator address for every coinjoin round.

What is the maximum number of coins that can be registered in a coinjoin?

Wasabi Wallet's default client is configured to register 1 up to 10 inputs per coinjoin round. However, as the coordinator cannot enforce this, a custom client could use a different configuration.

How many coins/outputs do I get from a coinjoin?

Wasabi Wallet's default client is configured to register 1 up to 10 outputs per coinjoin round. However, as the coordinator cannot enforce this, a custom client could use a different configuration.

Can I manually select which coins to register for coinjoin?

No, that is currently not possible. The automatic coinjoin robot registers the coins, based on multiple factors.

TIP

You can enable the red coin isolation setting, in case you want to prevent possible input heuristics (from outside observers) of anonscore 1 coins into the same coinjoin round.

How long does it take to make my wallet 100% private?

Depending on many factors, like the Anonymity score target, the coinjoin strategy, and the amount of bitcoin, it can take from a couple hours to multiple days.

What coinjoin strategy should I select?

There is no answer for all, or a "best" strategy, it depends on the user's privacy needs. The coinjoin strategy should be selected according to the user's preference: Do you want to Minimize costs, Maximize speed, or Maximize privacy? Or the user can create their own Custom strategy.

Wasabi Coinjoin Strategy

The default coinjoin strategy is `Maximize Speed`

This strategy is sufficient for most users

What is the coinjoin strategy?

A coinjoin strategy has specific pre-configured coinjoin settings.

There are multiple coinjoin settings which the user is able to configure according to their own prefence. Each coinjoin strategy has different specific settings for optimal performance. After a coinjoin strategy is selected, its settings are applied. It is supposed to make it easy for the user to select their preference, without having to know about the specific settings and how to configure them themselves.

Read more here.

What are the differences/settings per coinjoin strategy?

Minimize CostsMaximize SpeedMaximize Privacy
Anonymity score target55random between 27 and 75
Coinjoin time preferenceweekshourshours
Red coin isolationnot enablednot enabledenabled

What does the Auto-start coinjoin threshold mean in the coinjoin settings?

It is the amount at which your funds will automatically participate in coinjoin in the background. If the non-private wallet balance is less than this amount coinjoin will not automatically start. A use case is that it might not be economical to coinjoin with this non-private amount (fee amount compared to coinjoin amount).

For example, if the non-private balance is 0.005 BTC and the Auto-start coinjoin threshold is 0.01 BTC, the user will have to manually press Play to start coinjoining. The default Auto-start coinjoin threshold is 0.01 BTC.

Auto-start coinjoin threshold

What does the Red coin isolation mean in the coinjoin settings?

When the Red coin isolation is enabled, only a single coin with anonymity score 1 will be allowed into the coinjoin registration. To prevent possible coinjoin input heuristics from outside observers. The Red coin isolation is enabled by default when the Maximize Privacy coinjoin strategy is selected.

Red Coin Isolation

Do coinjoin transactions signal RBF?

No. Coinjoin transactions do not signal RBF.

Why do my coins occasionally get banned from participating in CoinJoin?

A CoinJoin consists of multiple users registering inputs (coins) and blinded outputs. Once the appropriate number of participants have registered, the actual transaction (the CoinJoin) is constructed by the coordinator, and given to all participants in the span of about 60 seconds. At this point, all registered participants must sign off on the CoinJoin, and if a single one of the participants fails to sign their input, the entire CoinJoin must be restarted.

So this introduces a problem, or an attack vector - a malicious user could purposefully register coins, only to wait for the signing phase and not sign. This would halt the entire CoinJoin process for all other participants and Wasabi would no longer work. This is also known as denial of service attackopen in new window.

So a simple solution looks like this - the coordinator could collect signatures from all inputs, and if one or more input refuses to sign, the coordinator could record that input and temporarily (or even permanently) ban that coin from participation. This is a nice solution, as it mitigates a single coin from ruining all CoinJoins, but it too comes with trade-offs.

For example, most of the time, users fail to sign a CoinJoin for non-malicious reasons. Perhaps their Tor connection went down in precisely that moment, or perhaps their WiFi had a temporary flicker at the wrong time. Further, some users don't even realize that the signing phase is happening, and sometimes shut down their computer at exactly the wrong moment. All of these things hinder a successful CoinJoin for all other participants, but by pure accident.

If you are one of the victims of this temporary banning then simply wait for the ban to expire and try again. The best thing you can do to avoid the issue is to have a strong internet connection and keep your computer online throughout the whole process.

Note:

Banning does not mean freezing. You can send banned coins to anyone you want. This is a temporary ban on your coins in participation of the CoinJoin.

Backup and Recovery

How do I back up my mnemonic words?

TIP

Write down your recovery words!

Wasabi uses BIP 39: mnemonic code for generating deterministic keysopen in new window to enable easy backups of all private keys in the wallet. The mnemonic is displayed as 12 recovery words that are only shown once during the wallet generation.

Wasabi Wallet recovery words

DANGER

In order to restore a wallet, you need BOTH the recovery words AND the password!

It is a good idea to keep the two in separate analog backups, such as a laminated paper written with pencil. In order to defend against nature destroying fragile paper, you can consider stamping the words into metal. Use two different backups and locations for the mnemonic and password, because whoever has both [including a physical attacker] has full access to your sats. Find a secure physical location to store the backups, maybe a home safe, or an expert security deposit box.

Please see Backup Best Practices for more information about backups.

How do I back up my wallet file?

Although you can back up your private keys with the mnemonic words and password, this is only a last resort recovery. If you want to also secure your address labels, the anonscore and additional metadata, then you can do a digital backup. Simply copy the WalletBackups folder with the wallet.json files from your Wasabi data folder onto suitable hardware, for example an encrypted USB stick. Note that this file has the encrypted private key (extracted from the extended private key), meaning that you only need the password to spend the bitcoin. This also contains the extended public key, the public keys, and the address labels, meaning that it completely links all the coins, both pre and post mix, with clear proof.

WARNING

Make sure to back up your password separately because it is necessary to spend your bitcoin.

TIP

The wallet file backup is sensitive, in terms of privacy, but not critical in terms of loss of funds (if a password was used when generating the wallet). So it is good advice to encrypt this wallet file.

What do I need to recover my wallet?

To recover your wallet you need either your Recovery Words + Password, or the Wallet File + Password, as shown in the table below.

Recovery WordsWallet FilePassword
Recovery Words❌❌✔️
Wallet File❌❌✔️
Password✔️✔️❌

TIP

If no password was entered at the wallet creation, then the Recovery Words or Wallet File alone are enough to recover the wallet.

Can I recover my wallet without the password?

No. The password you set is used as a 13th word (passphrase) as described in BIP39, you should back it up when you generate a wallet. It is necessary to spend your bitcoin or to recover your wallet, as shown in this table.

What should I do if I forget my password?

Try to use the Password Finder Tool to find your password. Having a close guess of what the password is increases the possibility that you get your password.

I lost the recovery words but I still have the .json file and the password. Is my wallet still recoverable?

Yes, but in this case it is advisable to create a new wallet and back up the new recovery words and the password, then move your bitcoin there.

The .json file contains the encrypted secret that requires the password to derive your private keys. That gives you access to your bitcoin.

Can I verify the Recovery Words of an existing wallet?

Yes. Go to Wallet Settings > Verify Recovery Words. Type in your recovery words in the correct order, click on Verify and it will show you if they are correct or not.

Wasabi Wallet Verify Recovery Words

Hardware Wallet

Watch the videoopen in new window

Watch the videoopen in new window

Watch the videoopen in new window

What hardware wallets does Wasabi support?

Wasabi uses the Bitcoin Core Hardware Wallet Interface (HWI)open in new window which allows it to support a variety of hardware wallets. For the complete list of all the officially supported hardware wallets, click hereopen in new window.

Why does Wasabi use the Hardware Wallet Interface?

Wasabi uses the Bitcoin Core Hardware Wallet Interface [HWI]open in new window, a python library tool for proper integration of off-line signing devices. It provides a standard way for any software wallet to communicate with any hardware wallet without needing any device specific drivers. HWI was developed and carefully reviewed over several years, with outstanding contributions by Andrew Chowopen in new window. Wasabi implements C# code that executes the HWI tool. Wasabi uses this powerful tool because there are no other dependencies necessary to support all the existing and future hardware wallets.

Does Wasabi support the hidden wallets of hardware wallets?

Partially. Only device side passphrase is supported. PC side passphrase is not. This means that the hidden wallet feature can be used with Trezor T, Ledger Nano S, Nano S Plus, Nano X and ColdCard. After the 12 or 24 words, enter the passphrase as the 13th or 25th word on the hardware wallet. It’s part of BIP 39open in new window.

How can I generate a Wasabi skeleton wallet file in ColdCard?

On the ColdCard you go to Advanced > MicroSD Card > Export Wallet > Wasabi Wallet and it will save a skeleton json-file to the MicroSD card in the hardware wallet.

Read more here.

How can I import the Wasabi skeleton wallet file?

Take the MicroSD card from the ColdCard and plug it in the computer with the Wasabi Wallet software. In Wasabi Wallet go to Add Wallet and select Import a wallet. Now select the Wasabi skeleton json-file from the MicroSD card, if this fails you can manually enter the file location in Wasabi Wallet window and load the file.

Read more here.

How can I generate a receiving address of my hardware wallet?

In Wasabi Wallet you load your previously imported wallet (from Wasabi skeleton, or USB detection) and go to the Receive dialog, here you enter a label for the observers of the incoming transaction and click Continue. In the receive dialog, previously generated addresses (which haven't received any funds yet) can be viewed and copied at Addresses Awaiting Payment.

Read more here.

How can I sign a transaction with a USB connected hardware wallet?

To send a transaction you will need to connect your hardware wallet and unlock the device (using PIN or password).

  • Go to Send, enter the address to send to and the amount of bitcoin to spend.
  • Enter the label of whom you are sending to.
  • At the Preview Transaction screen, check if all the information is correct.
  • After you have checked that everything is correct, click Send Now to sign it with the connected hardware wallet and broadcast the transaction to the network.

Read more here.

How can I build and export a transaction to ColdCard?

  • Enable PSBT workflow in the Wallet Settings.
  • Go to Send and enter the destination address and amount.
  • Click Continue.
  • Enter the label of whom you are sending to.
  • At the Preview Transaction screen, check that everything is correct.
  • Click on Save PSBT file and save the file to the MicroSD card.
  • You can then insert the MicroSD card (containing the PSBT) in the Coldcard for manual verification and signing.

Read more here.

How can I sign a transaction on the ColdCard?

On the ColdCard (Mk2, firmware 2.1.1 and up) you enter the PIN code to unlock the hardware wallet and press Ready To Sign with the MicroSD card containing the previously generated transaction or PSBT-file. Verify the address and amount and the ColdCard will then create a signed.psbt and final.txn file on the MicroSD card. The finalized transaction (xxx-final.txn) can now be broadcast by Wasabi Wallet with the Broadcaster tool, or even a radio or satellite dish if someone is listening!

Read more here.

How can I import and broadcast a final transaction from ColdCard?

In the top search bar, go to Broadcaster and then select Import Transaction, now you can select the previously finalized (and signed) transaction file from the MicroSD card. If this fails you can manually type the path to this file in Wasabi Wallet to load the transaction. Now click Broadcast Transaction to send it off over Tor to a random Bitcoin node so it can flood over to the miners for confirmation in a block.

Read more here.

TIP

A Broadcast button will be displayed next to the Send button, when PSBT workflow is enabled, for an easier workflow.

Can I coinjoin bitcoins on my hardware wallet?

No, that is currently not possible. A coinjoin is a multi round interactive process, and requires fast signing by the participants, thus the keys need to be on a hot computer. Thus currently you have to send the bitcoins from your hardware wallet to a hot Wasabi Wallet, do the coinjoin and then send them back to a new address on the Hardware wallet for cold-storage.

Read more here.

TIP

Trezor now supports coinjoin with the Trezor Suite, using same rounds as Wasabi Wallet users. Read more hereopen in new window.

Does Ledger Live send my public keys and addresses to a third party server?

Only if you add your accounts in the app, but not if you update your device firmware or install apps. When using the Ledger Live software wallet to manage your coins, you send all of your used, and 20 unused addresses to Ledger's nodes. Sourceopen in new window

Your extended public key, however, is not shared with Ledger's node, but rather stored encrypted on your local machine.

Read more hereopen in new window.

Ledger could potentially analyze information from API calls to their nodes to link addresses to individual users, though Ledger says no logs are kept during normal operation.

To avoid any privacy leak, you can use a Ledger hardware wallet in combination with Wasabi as a software interface, and because Wasabi does not leak your addresses, your transaction history is not shared with anyone.

After I coinjoined my coins and reached 100% privacy, I sent them to my hardware wallet and now the coins have anonscore 1. Why?

Everything is working as expected.

The anonymity score (number) is tied to your wallet that you used to coinjoin, if you send a coinjoined coin to another Wasabi Wallet of yours (hardware wallet or normal wallet) it will have an anonscore of 1 because this wallet doesn't know all of the coinjoin history.

You should put a meaningful label when you generate a receive address in your hardware wallet, e.g. "private UTXO" (something that reminds you that you got this UTXO from your Wasabi Wallet and that it was coinjoined).

Can I use Trezor One with Wasabi?

No. Unfortunately, Trezor One is not supported by Wasabi Wallet. For the complete list of all the officially supported hardware wallets, click hereopen in new window.

Can I use BitBox with Wasabi?

No. Unfortunately, BitBox is not supported by Wasabi Wallet. For the complete list of all the officially supported hardware wallets, click hereopen in new window.

How can I type in the passphrase of my Trezor T?

After connecting the Trezor T to your computer and upon trying to load your wallet, you get a message on the Trezor T to choose where to type your passphrase, on the device or the host (computer), choose the first option (device) then enter the passprase using the touchscreen of your Trezor T. Wasabi wallet will now load this passphrase protected wallet.

I have coinjoined with a Trezor device on Trezor Suite, but in Wasabi I cannot see my coins?

Trezor uses only Taproot for coinjoin, with a non-standard derivation path. So Wasabi does not know about the existence of the Trezor Suite coinjoin coins.

How can I use Hardware Wallets on Linux (udev rules)?

On Linux, you need to create a set of udev rules for the hardware wallet to be reachable.

Udev rules instructions can be found hereopen in new window.

History

How can I check the transactions history?

The wallet's main page displays the history of all transactions made with this specific wallet. It includes receiving, sending, and coinjoin transactions.

Wasabi Wallet History

How can I see coinjoins in the history list?

Coinjoin transactions are indicated with a shield icon:

History Coinjoin

When the wallet has made multiple coinjoins, the coinjoins will be clustered. Coinjoin clusters are indicated with a double shield icon. To see the individual coinjoins, the cluster can be expanded by clicking the arrow on the left:

History Coinjoin Expanded

A coinjoin is a payment within the same wallet, thus it only shows the coordination fee (if any) and mining fee leaving the wallet.

Can I sort the history items?

Yes, the history items can be sorted by clicking on the column title:

Sort Date Column

Can I search for a transaction ID in the history?

Yes. This can be done by pasting the transaction ID into the search bar or by manually typing part of the transaction ID. After clicking the result, the transaction will be highlighted in the history.

SearchBar Search TX

TIP

It will only show results of the wallets which are currently open.

Can I export a list of transactions?

There is currently no convenient way to export a list with transaction details inside the GUI. However, you can see the wallet.json files inside the WalletBackups folder (you can find it in your Wasabi data folder) which contains all the public keys, labels and anonset.

You can use the Wasabi RPC server gethistory call to get a list of all transactions, including date, block height, amount, label and tx id.

Settings

How do I connect my own full node to Wasabi?

There are three different ways of using your Bitcoin full node with Wasabi:

  • If you have a full node already running on the same computer as Wasabi, it will automatically be detected and used by default.
  • If you have a full node on a remote computer, then you can connect to it by specifying the local network IP address or Tor onion service in the Wasabi Settings tab.

Wasabi Wallet Remote P2P Bitcoin Endpoint full node

  • If you are not yet running a full node, Wasabi has the bitcoind binaries included, and with one click in the Settings, you can start Bitcoin Knots together with Wasabi.

Wasabi Wallet local Bitcoin Knots full node integration

Watch the videoopen in new window

How can I turn off Tor?

You can turn off Network anonymization (Tor) in the Settings. Note that this is a privacy concern, especially when you coinjoin and when you broadcast a transaction. In the first case, the coordinator would know the links between your inputs and outputs based on your IP address. In the second case, if you happen to broadcast a transaction of yours to a full node that is spying on you, it will know the link between your transaction and your IP address.

DANGER

It is recommended to always use Tor! The setting to turn it off is only intended for debugging and trouble shooting.

How can I change the anonymity score target?

The anonscore target is a wallet specific setting which is determined by the Coinjoin Strategy, but can also be manually changed in the Coinjoin Settings dialog.

On the main view click the three dots on the top right corner after loading the wallet. Choose Coinjoin Settings, click Change (Coinjoin strategy), click Customize. Move the Anonymity score target slider to the desired value and click Done.

Coinjoin Settings Anonymity score target

Alternatively, you can change the anonymity score target by editing the wallet file. Go to the SearchBar and click Wallet Folder and open the wallet json file and edit the AnonScoreTarget value.

"AnonScoreTarget": 5,

What is the dust threshold?

Dust can mean a lot of thingsopen in new window, depending on how you look at it. It can be a non-economical input, that is a UTXO that has less value than the fees it would cost to spend this coin. A dust attack is actually about forced address reuseopen in new window, the malicious actor sends very small amounts into old addresses and consolidation of these dust UTXOs can link several coins in a wallet cluster.

Specifically in the context of Wasabi, with the dust threshold settings you can limit the value of spam coins shown in the GUI. Coins that you receive from other wallets (so no self-spend) which are less than the dust threshold in value and are received on an already used address are not shown. For example: When it is set to 0.0000 5000 BTC, and you receive a coin worth 0.0000 4000 BTC from a different wallet to an already used address, then this transaction and the coin in the coin list will not be shown.

Wasabi Wallet Dust threshold settings

Where can I find the logs?

In the SearchBar you can see there are several logs available.

  • The Logs shows the general log information about Wasabi Wallet.
  • The Tor Logs shows the Tor specific logs.

Wasabi Wallet SearchBar Help&Support and Open

Alternatively, you can find the logs inside your Wasabi data folder.

How to activate/deactivate discreet mode?

You can activate/deactivate Discreet Mode by clicking the Discreet Mode icon in the bottom left corner of the main view.

Read more here.

Discreet Mode Icon

How can I change to the white theme?

You can change from the default dark to the white theme by disabling Dark Mode in the Settings. Alternatively, you can switch to Dark Mode in the .walletwasabi/client/UIConfig.json data folder. Open the UIConfig.json file and change the line from "DarkModeEnabled": true to "DarkModeEnabled": false. Save the file and restart Wasabi. Please note that Wasabi is designed for the dark theme, and some color schemes might not look beautiful in the white mode.

Wasabi Wallet white theme

Coin Control Best Practices

What are coins?

Bitcoin uses a system of inputs and outputs to keep track of who owns how many sats. Every transaction specifies one or more inputs, the chunk of bitcoin being spent, and one or more outputs, the destination of who receives the bitcoin. A coin is also called an unspent transaction output (UTXO), meaning that this output has not been used as the input of a new transaction - it is yet to be spent. In order to spend a UTXO, the valid signature and script has to be provided in the transaction. This ensures that only with knowledge of the correct private key can this coin be sent to a new address. This chain of links between inputs being spent and outputs being generated is verified by every full node, and stored on the blockchain.

How can I enable (manual) coin control?

The default send workflow uses the automatic coin selection algorithm, which is optimized in a way that "traditional" coin control is obsolete. However, the user can review which coins are selected, or select different coins using the (manual) coin control. This can be done by pressing and holding the keystroke alt (or option on mac device) at the Preview Transaction screen, which will bring up the Review coins button to click on.

Send Review Coins

This is a developer feature

Do NOT use the manual coin control if you do not know what you are doing. Misusing it can have seriously bad privacy consequences.

How do I select coins for spending?

In the normal send workflow, Wasabi automatically selects which coins to send.

To send a specific coin, the user can use the Wallet Coins dialog (a.k.a coinlist). The coinlist can be brought up by pressing the keyboard combination CTRL + C + D simultaneously on the main view or via the search bar.

This is for advanced usage only

Users should stick to the default send workflow. Misusing the coinlist for sending can result in critical privacy risks.

Wallet Coins Send Selected Coins

This is not full coin control

You can only send coins in full. There is no possiblity to enter a bitcoin amount or receive change.

Can I consolidate anonset coins?

It is advisable to limit the recombining of mixed coins because it can only decrease the privacy of these coins. This reveals that all the consolidated UTXOs are controlled by one entity, which was not known before the consolidation. That said, if you combine only a couple of mixed coins, you might not reveal your pre-coinjoin transaction history, especially when you did several re-mixes. So consolidating some private coins is OK to do.

Take great care!

Never consolidate non-private coins with private (mixed) coins, as this negates the privacy benefits of the coinjoin.

Watch the videoopen in new window

How can I send my anonset coins to my hardware wallet?

Most hardware wallets communicate with servers to provide you with your balance. This reveals your public key to the server, which damages your privacy - the hardware wallet company can now link together all your addresses. As a result it is not recommended that you send your mixed coins to an address associated with your hardware wallet unless you are confident that you have set up your hardware wallet in a way that it does not communicate with a 3rd party server (see below).

You can, however, manage your hardware wallet with the Wasabi interface. Alternatively, you can use your hardware wallet with Electrum, and in order to not leak any information to third-party servers run your own Electrum Personal Serveropen in new window, ElectrumXopen in new window or Electrsopen in new window.

What can I do with small change?

There are no hard and fast rules for what to do with the change. Generally try to avoid having change by using the change avoidance suggestions when sending. Generally change should be coinjoined, Wasabi automatically coinjoins the change if possible (if the change is more than the coinjoin minimum).

You should treat change as a kind of toxic waste (handled with great care). You can spend the change to the same entity as the initial transaction, without loosing much privacy. Only spend the change to another entity, if these two won't make you trouble knowing you interact with both of them. If needed, you can consolidate several change coins, but we advise you to do it in a coinjoin. In JoinMarket you can specify the exact amount of coinjoin, so it can be exactly the amount of the change. Or open a new Lightning Network node (not your main Lightning node), create a channel to a random peer on the network and route the funds back to you.

TIP

For more information, see this dedicated chapter.

- + diff --git a/FAQ/index.html b/FAQ/index.html index 2cb3b632da..4680bec669 100644 --- a/FAQ/index.html +++ b/FAQ/index.html @@ -24,10 +24,10 @@ Frequently Asked Questions | Wasabi Docs - +
Wasabi Docs

Frequently Asked Questions

This is an archive with many questions that Wasabikas have asked most frequently, including:

  • Answers about the basics of privacy and Bitcoin in general.
  • The important details of how to install Wasabi properly, and the best practices for using it.
  • Further guidance for those who are interested in contributing to Wasabi.

Chapters

- + diff --git a/assets/404.html.699a943a.js b/assets/404.html.23597e55.js similarity index 63% rename from assets/404.html.699a943a.js rename to assets/404.html.23597e55.js index 8a6ca0486b..3cfe962e38 100644 --- a/assets/404.html.699a943a.js +++ b/assets/404.html.23597e55.js @@ -1 +1 @@ -import{_ as e,o as c,c as t}from"./app.a5b7c2b2.js";const _={};function o(r,n){return c(),t("div")}const a=e(_,[["render",o],["__file","404.html.vue"]]);export{a as default}; +import{_ as e,o as c,c as t}from"./app.65e5b6fd.js";const _={};function o(r,n){return c(),t("div")}const a=e(_,[["render",o],["__file","404.html.vue"]]);export{a as default}; diff --git a/assets/AddressReuse.html.12293165.js b/assets/AddressReuse.html.93127d40.js similarity index 98% rename from assets/AddressReuse.html.12293165.js rename to assets/AddressReuse.html.93127d40.js index b006ded717..c44fc438a5 100644 --- a/assets/AddressReuse.html.12293165.js +++ b/assets/AddressReuse.html.93127d40.js @@ -1 +1 @@ -import{_ as d,r as o,o as l,c,a as e,d as t,w as a,b as s,e as u}from"./app.a5b7c2b2.js";const h={},_=e("h1",{id:"address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address-reuse","aria-hidden":"true"},"#"),s(" Address Reuse")],-1),f=e("p",null,"The first rule of Bitcoin privacy:",-1),m=e("blockquote",null,[e("p",null,"Never reuse addresses!")],-1),p=e("p",null,"The second rule of Bitcoin privacy:",-1),b=e("blockquote",null,[e("p",null,"NEVER reuse addresses!!")],-1),y={class:"table-of-contents"},v=e("hr",null,null,-1),g=e("h2",{id:"problem",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#problem","aria-hidden":"true"},"#"),s(" Problem")],-1),w=e("h3",{id:"easy-wallet-clustering",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#easy-wallet-clustering","aria-hidden":"true"},"#"),s(" Easy wallet clustering")],-1),k=e("p",null,"If an address is used more than once, it means that the same private key can spend all its coins. It is very easy to find all the UTXOs of an address, and thus to find out how many bitcoin the private key holds.",-1),x=e("p",null,"Further, in a transaction where one output has a reused address, then it is very likely that this output is the payment destination, and not the change. Most wallets automatically generate new change addresses for every transaction, but payment addresses are selected manually by the user.",-1),A={href:"https://en.bitcoin.it/wiki/Address_reuse",target:"_blank",rel:"noopener noreferrer"},P={href:"https://en.bitcoin.it/Privacy#Address_reuse",target:"_blank",rel:"noopener noreferrer"},R=e("p",null,"There are different types of address reuse:",-1),I=e("h3",{id:"publicly-advertised-addresses-donations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#publicly-advertised-addresses-donations","aria-hidden":"true"},"#"),s(" Publicly advertised addresses (donations)")],-1),T=e("p",null,"Here, a person publishes a single address to a public forum, like in the bio of a social media network or on a website, and anyone can send bitcoin to this address.",-1),W=e("h3",{id:"dusting",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#dusting","aria-hidden":"true"},"#"),s(" Dusting")],-1),B={href:"https://en.bitcoin.it/Privacy#Forced_address_reuse",target:"_blank",rel:"noopener noreferrer"},E=u('

Intentionally malicious

Since Wasabi is libre and open-source, anyone can modify a fork of Wasabi to make sure the same two addresses are recycled in every CoinJoin registration. This is someone intentionally deanonymizing himself, and he might have quite dubious motives.

Wasabi's Solution

Remove used address from GUI

Wasabi encourages the user to not reuse addresses. You always get a new Bitcoin address whenever you generate one. Previously generated addresses, which haven't received bitcoin yet, are displayed at Addresses Awaiting Payment. An address is automatically removed from the Addresses Awaiting Payment list once that address receives funds.

',5);function N(V,F){const n=o("router-link"),i=o("ExternalLinkIcon"),r=o("RouterLink");return l(),c("div",null,[_,f,m,p,b,e("nav",y,[e("ul",null,[e("li",null,[t(n,{to:"#problem"},{default:a(()=>[s("Problem")]),_:1}),e("ul",null,[e("li",null,[t(n,{to:"#easy-wallet-clustering"},{default:a(()=>[s("Easy wallet clustering")]),_:1})]),e("li",null,[t(n,{to:"#publicly-advertised-addresses-donations"},{default:a(()=>[s("Publicly advertised addresses (donations)")]),_:1})]),e("li",null,[t(n,{to:"#dusting"},{default:a(()=>[s("Dusting")]),_:1})]),e("li",null,[t(n,{to:"#intentionally-malicious"},{default:a(()=>[s("Intentionally malicious")]),_:1})])])]),e("li",null,[t(n,{to:"#wasabi-s-solution"},{default:a(()=>[s("Wasabi's Solution")]),_:1}),e("ul",null,[e("li",null,[t(n,{to:"#remove-used-address-from-gui"},{default:a(()=>[s("Remove used address from GUI")]),_:1})])])])])]),v,g,w,k,x,e("p",null,[s("Read more about the privacy concerns of address reuse in the "),e("a",A,[s("separate entry"),t(i)]),s(" and the "),e("a",P,[s("privacy chapter"),t(i)]),s(" of the Bitcoin wiki.")]),R,I,T,W,e("p",null,[s("With a "),e("a",B,[s("forced address reuse attack"),t(i)]),s(", an attacker sends a small amount of bitcoin to an already existing address. The attacker hopes that this dust coin is consolidated with another coin, thus linking the two in a cluster.")]),E,e("p",null,[s("To protect against forced address reuse attack (Dusting), Wasabi has a modifiable "),t(r,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-dust-threshold"},{default:a(()=>[s("dust limit")]),_:1}),s(", where the wallet does not show coins below a certain threshold value.")])])}const S=d(h,[["render",N],["__file","AddressReuse.html.vue"]]);export{S as default}; +import{_ as d,r as o,o as l,c,a as e,d as t,w as a,b as s,e as u}from"./app.65e5b6fd.js";const h={},_=e("h1",{id:"address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address-reuse","aria-hidden":"true"},"#"),s(" Address Reuse")],-1),f=e("p",null,"The first rule of Bitcoin privacy:",-1),m=e("blockquote",null,[e("p",null,"Never reuse addresses!")],-1),p=e("p",null,"The second rule of Bitcoin privacy:",-1),b=e("blockquote",null,[e("p",null,"NEVER reuse addresses!!")],-1),y={class:"table-of-contents"},v=e("hr",null,null,-1),g=e("h2",{id:"problem",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#problem","aria-hidden":"true"},"#"),s(" Problem")],-1),w=e("h3",{id:"easy-wallet-clustering",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#easy-wallet-clustering","aria-hidden":"true"},"#"),s(" Easy wallet clustering")],-1),k=e("p",null,"If an address is used more than once, it means that the same private key can spend all its coins. It is very easy to find all the UTXOs of an address, and thus to find out how many bitcoin the private key holds.",-1),x=e("p",null,"Further, in a transaction where one output has a reused address, then it is very likely that this output is the payment destination, and not the change. Most wallets automatically generate new change addresses for every transaction, but payment addresses are selected manually by the user.",-1),A={href:"https://en.bitcoin.it/wiki/Address_reuse",target:"_blank",rel:"noopener noreferrer"},P={href:"https://en.bitcoin.it/Privacy#Address_reuse",target:"_blank",rel:"noopener noreferrer"},R=e("p",null,"There are different types of address reuse:",-1),I=e("h3",{id:"publicly-advertised-addresses-donations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#publicly-advertised-addresses-donations","aria-hidden":"true"},"#"),s(" Publicly advertised addresses (donations)")],-1),T=e("p",null,"Here, a person publishes a single address to a public forum, like in the bio of a social media network or on a website, and anyone can send bitcoin to this address.",-1),W=e("h3",{id:"dusting",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#dusting","aria-hidden":"true"},"#"),s(" Dusting")],-1),B={href:"https://en.bitcoin.it/Privacy#Forced_address_reuse",target:"_blank",rel:"noopener noreferrer"},E=u('

Intentionally malicious

Since Wasabi is libre and open-source, anyone can modify a fork of Wasabi to make sure the same two addresses are recycled in every CoinJoin registration. This is someone intentionally deanonymizing himself, and he might have quite dubious motives.

Wasabi's Solution

Remove used address from GUI

Wasabi encourages the user to not reuse addresses. You always get a new Bitcoin address whenever you generate one. Previously generated addresses, which haven't received bitcoin yet, are displayed at Addresses Awaiting Payment. An address is automatically removed from the Addresses Awaiting Payment list once that address receives funds.

',5);function N(V,F){const n=o("router-link"),i=o("ExternalLinkIcon"),r=o("RouterLink");return l(),c("div",null,[_,f,m,p,b,e("nav",y,[e("ul",null,[e("li",null,[t(n,{to:"#problem"},{default:a(()=>[s("Problem")]),_:1}),e("ul",null,[e("li",null,[t(n,{to:"#easy-wallet-clustering"},{default:a(()=>[s("Easy wallet clustering")]),_:1})]),e("li",null,[t(n,{to:"#publicly-advertised-addresses-donations"},{default:a(()=>[s("Publicly advertised addresses (donations)")]),_:1})]),e("li",null,[t(n,{to:"#dusting"},{default:a(()=>[s("Dusting")]),_:1})]),e("li",null,[t(n,{to:"#intentionally-malicious"},{default:a(()=>[s("Intentionally malicious")]),_:1})])])]),e("li",null,[t(n,{to:"#wasabi-s-solution"},{default:a(()=>[s("Wasabi's Solution")]),_:1}),e("ul",null,[e("li",null,[t(n,{to:"#remove-used-address-from-gui"},{default:a(()=>[s("Remove used address from GUI")]),_:1})])])])])]),v,g,w,k,x,e("p",null,[s("Read more about the privacy concerns of address reuse in the "),e("a",A,[s("separate entry"),t(i)]),s(" and the "),e("a",P,[s("privacy chapter"),t(i)]),s(" of the Bitcoin wiki.")]),R,I,T,W,e("p",null,[s("With a "),e("a",B,[s("forced address reuse attack"),t(i)]),s(", an attacker sends a small amount of bitcoin to an already existing address. The attacker hopes that this dust coin is consolidated with another coin, thus linking the two in a cluster.")]),E,e("p",null,[s("To protect against forced address reuse attack (Dusting), Wasabi has a modifiable "),t(r,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-dust-threshold"},{default:a(()=>[s("dust limit")]),_:1}),s(", where the wallet does not show coins below a certain threshold value.")])])}const S=d(h,[["render",N],["__file","AddressReuse.html.vue"]]);export{S as default}; diff --git a/assets/BIPs.html.c05a0bab.js b/assets/BIPs.html.4bd756fe.js similarity index 98% rename from assets/BIPs.html.c05a0bab.js rename to assets/BIPs.html.4bd756fe.js index 70cc171582..5407cbaa0c 100644 --- a/assets/BIPs.html.c05a0bab.js +++ b/assets/BIPs.html.4bd756fe.js @@ -1 +1 @@ -import{_ as a,r as n,o as l,c as b,a as e,d as i,w as s,b as t}from"./app.a5b7c2b2.js";const p={},c=e("h1",{id:"supported-bips",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#supported-bips","aria-hidden":"true"},"#"),t(" Supported BIPs")],-1),h={class:"table-of-contents"},d=e("p",null,"Wasabi Wallet strives toward establishing solid industry best practices and standards. Here is a list of all the supported and integrated Bitcoin Improvement Proposals:",-1),u=e("h2",{id:"what-is-supported",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-supported","aria-hidden":"true"},"#"),t(" What is supported")],-1),_={href:"https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki",target:"_blank",rel:"noopener noreferrer"},m={href:"https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki",target:"_blank",rel:"noopener noreferrer"},P={href:"https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki",target:"_blank",rel:"noopener noreferrer"},B={href:"https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki",target:"_blank",rel:"noopener noreferrer"},I={href:"https://github.com/bitcoin/bips/blob/master/bip-0086.mediawiki",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki",target:"_blank",rel:"noopener noreferrer"},x={href:"https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki",target:"_blank",rel:"noopener noreferrer"},S={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},T={href:"https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki",target:"_blank",rel:"noopener noreferrer"},D={href:"https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki",target:"_blank",rel:"noopener noreferrer"},K={href:"https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki",target:"_blank",rel:"noopener noreferrer"},V=e("h2",{id:"what-is-not-supported",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-not-supported","aria-hidden":"true"},"#"),t(" What is not supported")],-1),C={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},H={href:"https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki",target:"_blank",rel:"noopener noreferrer"};function L(E,N){const o=n("router-link"),r=n("ExternalLinkIcon");return l(),b("div",null,[c,e("nav",h,[e("ul",null,[e("li",null,[i(o,{to:"#what-is-supported"},{default:s(()=>[t("What is supported")]),_:1})]),e("li",null,[i(o,{to:"#what-is-not-supported"},{default:s(()=>[t("What is not supported")]),_:1})])])]),d,u,e("ul",null,[e("li",null,[e("a",_,[t("BIP 21: URI Scheme"),i(r)])]),e("li",null,[e("a",m,[t("BIP 32: Hierarchical Deterministic Wallets"),i(r)])]),e("li",null,[e("a",f,[t("BIP 38: Password-Protected Private Key"),i(r)])]),e("li",null,[e("a",g,[t("BIP 39: Mnemonic Code for Generating Deterministic Keys"),i(r)])]),e("li",null,[e("a",k,[t("BIP 44: Multi-Account Hierarchy for Deterministic Wallets"),i(r)])]),e("li",null,[e("a",P,[t("BIP 72: bitcoin: uri extensions for Payment Protocol"),i(r)])]),e("li",null,[e("a",w,[t("BIP 78: A Simple Payjoin Proposal"),i(r)])]),e("li",null,[e("a",B,[t("BIP 84: Derivation scheme for P2WPKH based accounts"),i(r)])]),e("li",null,[e("a",I,[t("BIP 86: Key Derivation for Single Key P2TR Outputs"),i(r)])]),e("li",null,[e("a",v,[t("BIP 125: Opt-In full Replace-by-Fee Signaling"),i(r)])]),e("li",null,[e("a",x,[t("BIP 141: Segregated Witness (Consensus Layer)"),i(r)])]),e("li",null,[e("a",W,[t("BIP 143: Transaction Signature Verification for Version 0 Witness Program"),i(r)])]),e("li",null,[e("a",y,[t("BIP 144: Segregated Witness (Peer Services)"),i(r)])]),e("li",null,[e("a",S,[t("BIP 158: Block filters"),i(r)])]),e("li",null,[e("a",T,[t("BIP 173: Base32 address format for native v0-16 witness outputs"),i(r)])]),e("li",null,[e("a",D,[t("BIP 174: Partially Signed Bitcoin Transaction Format"),i(r)])]),e("li",null,[e("a",K,[t("BIP 341: Taproot: SegWit version 1 spending rules"),i(r)])])]),V,e("ul",null,[e("li",null,[e("a",C,[t("BIP 37: Bloom filters"),i(r)])]),e("li",null,[e("a",H,[t("BIP 69: Lexicographical Indexing of Transaction Inputs and Outputs"),i(r)])])])])}const R=a(p,[["render",L],["__file","BIPs.html.vue"]]);export{R as default}; +import{_ as a,r as n,o as l,c as b,a as e,d as i,w as s,b as t}from"./app.65e5b6fd.js";const p={},c=e("h1",{id:"supported-bips",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#supported-bips","aria-hidden":"true"},"#"),t(" Supported BIPs")],-1),h={class:"table-of-contents"},d=e("p",null,"Wasabi Wallet strives toward establishing solid industry best practices and standards. Here is a list of all the supported and integrated Bitcoin Improvement Proposals:",-1),u=e("h2",{id:"what-is-supported",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-supported","aria-hidden":"true"},"#"),t(" What is supported")],-1),_={href:"https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki",target:"_blank",rel:"noopener noreferrer"},m={href:"https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki",target:"_blank",rel:"noopener noreferrer"},P={href:"https://github.com/bitcoin/bips/blob/master/bip-0072.mediawiki",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/bitcoin/bips/blob/master/bip-0078.mediawiki",target:"_blank",rel:"noopener noreferrer"},B={href:"https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki",target:"_blank",rel:"noopener noreferrer"},I={href:"https://github.com/bitcoin/bips/blob/master/bip-0086.mediawiki",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki",target:"_blank",rel:"noopener noreferrer"},x={href:"https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/bitcoin/bips/blob/master/bip-0144.mediawiki",target:"_blank",rel:"noopener noreferrer"},S={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},T={href:"https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki",target:"_blank",rel:"noopener noreferrer"},D={href:"https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki",target:"_blank",rel:"noopener noreferrer"},K={href:"https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki",target:"_blank",rel:"noopener noreferrer"},V=e("h2",{id:"what-is-not-supported",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-not-supported","aria-hidden":"true"},"#"),t(" What is not supported")],-1),C={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},H={href:"https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki",target:"_blank",rel:"noopener noreferrer"};function L(E,N){const o=n("router-link"),r=n("ExternalLinkIcon");return l(),b("div",null,[c,e("nav",h,[e("ul",null,[e("li",null,[i(o,{to:"#what-is-supported"},{default:s(()=>[t("What is supported")]),_:1})]),e("li",null,[i(o,{to:"#what-is-not-supported"},{default:s(()=>[t("What is not supported")]),_:1})])])]),d,u,e("ul",null,[e("li",null,[e("a",_,[t("BIP 21: URI Scheme"),i(r)])]),e("li",null,[e("a",m,[t("BIP 32: Hierarchical Deterministic Wallets"),i(r)])]),e("li",null,[e("a",f,[t("BIP 38: Password-Protected Private Key"),i(r)])]),e("li",null,[e("a",g,[t("BIP 39: Mnemonic Code for Generating Deterministic Keys"),i(r)])]),e("li",null,[e("a",k,[t("BIP 44: Multi-Account Hierarchy for Deterministic Wallets"),i(r)])]),e("li",null,[e("a",P,[t("BIP 72: bitcoin: uri extensions for Payment Protocol"),i(r)])]),e("li",null,[e("a",w,[t("BIP 78: A Simple Payjoin Proposal"),i(r)])]),e("li",null,[e("a",B,[t("BIP 84: Derivation scheme for P2WPKH based accounts"),i(r)])]),e("li",null,[e("a",I,[t("BIP 86: Key Derivation for Single Key P2TR Outputs"),i(r)])]),e("li",null,[e("a",v,[t("BIP 125: Opt-In full Replace-by-Fee Signaling"),i(r)])]),e("li",null,[e("a",x,[t("BIP 141: Segregated Witness (Consensus Layer)"),i(r)])]),e("li",null,[e("a",W,[t("BIP 143: Transaction Signature Verification for Version 0 Witness Program"),i(r)])]),e("li",null,[e("a",y,[t("BIP 144: Segregated Witness (Peer Services)"),i(r)])]),e("li",null,[e("a",S,[t("BIP 158: Block filters"),i(r)])]),e("li",null,[e("a",T,[t("BIP 173: Base32 address format for native v0-16 witness outputs"),i(r)])]),e("li",null,[e("a",D,[t("BIP 174: Partially Signed Bitcoin Transaction Format"),i(r)])]),e("li",null,[e("a",K,[t("BIP 341: Taproot: SegWit version 1 spending rules"),i(r)])])]),V,e("ul",null,[e("li",null,[e("a",C,[t("BIP 37: Bloom filters"),i(r)])]),e("li",null,[e("a",H,[t("BIP 69: Lexicographical Indexing of Transaction Inputs and Outputs"),i(r)])])])])}const R=a(p,[["render",L],["__file","BIPs.html.vue"]]);export{R as default}; diff --git a/assets/BackupBestPractices.html.fdb12de8.js b/assets/BackupBestPractices.html.675e45c1.js similarity index 99% rename from assets/BackupBestPractices.html.fdb12de8.js rename to assets/BackupBestPractices.html.675e45c1.js index 70ec91751d..d668dc96c0 100644 --- a/assets/BackupBestPractices.html.fdb12de8.js +++ b/assets/BackupBestPractices.html.675e45c1.js @@ -1 +1 @@ -import{_ as r,r as n,o as l,c as s,a as e,d as i,w as o,b as a,e as d}from"./app.a5b7c2b2.js";const c={},h=e("h1",{id:"backup-best-practices",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#backup-best-practices","aria-hidden":"true"},"#"),a(" Backup Best Practices")],-1),u={class:"table-of-contents"},p=d('

Common mediums for backups

Written on a piece of paper

Printed on a piece of paper

On laminated paper

Engraved / etched / ablated / stamped on a piece of metal

Stored digitally on a computer

Stored digitally on CD, floppy disk, laserdisc, or mini-disc

Stored digitally on a flash drive

A pre-funded physical bitcoin coin (where the manufacturer generates and installs the secret key)

',17);function m(f,y){const t=n("router-link");return l(),s("div",null,[h,e("nav",u,[e("ul",null,[e("li",null,[i(t,{to:"#common-mediums-for-backups"},{default:o(()=>[a("Common mediums for backups")]),_:1}),e("ul",null,[e("li",null,[i(t,{to:"#written-on-a-piece-of-paper"},{default:o(()=>[a("Written on a piece of paper")]),_:1})]),e("li",null,[i(t,{to:"#printed-on-a-piece-of-paper"},{default:o(()=>[a("Printed on a piece of paper")]),_:1})]),e("li",null,[i(t,{to:"#on-laminated-paper"},{default:o(()=>[a("On laminated paper")]),_:1})]),e("li",null,[i(t,{to:"#engraved-etched-ablated-stamped-on-a-piece-of-metal"},{default:o(()=>[a("Engraved / etched / ablated / stamped on a piece of metal")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-a-computer"},{default:o(()=>[a("Stored digitally on a computer")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-cd-floppy-disk-laserdisc-or-mini-disc"},{default:o(()=>[a("Stored digitally on CD, floppy disk, laserdisc, or mini-disc")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-a-flash-drive"},{default:o(()=>[a("Stored digitally on a flash drive")]),_:1})]),e("li",null,[i(t,{to:"#a-pre-funded-physical-bitcoin-coin-where-the-manufacturer-generates-and-installs-the-secret-key"},{default:o(()=>[a("A pre-funded physical bitcoin coin (where the manufacturer generates and installs the secret key)")]),_:1})])])])])]),p])}const b=r(c,[["render",m],["__file","BackupBestPractices.html.vue"]]);export{b as default}; +import{_ as r,r as n,o as l,c as s,a as e,d as i,w as o,b as a,e as d}from"./app.65e5b6fd.js";const c={},h=e("h1",{id:"backup-best-practices",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#backup-best-practices","aria-hidden":"true"},"#"),a(" Backup Best Practices")],-1),u={class:"table-of-contents"},p=d('

Common mediums for backups

Written on a piece of paper

Printed on a piece of paper

On laminated paper

Engraved / etched / ablated / stamped on a piece of metal

Stored digitally on a computer

Stored digitally on CD, floppy disk, laserdisc, or mini-disc

Stored digitally on a flash drive

A pre-funded physical bitcoin coin (where the manufacturer generates and installs the secret key)

',17);function m(f,y){const t=n("router-link");return l(),s("div",null,[h,e("nav",u,[e("ul",null,[e("li",null,[i(t,{to:"#common-mediums-for-backups"},{default:o(()=>[a("Common mediums for backups")]),_:1}),e("ul",null,[e("li",null,[i(t,{to:"#written-on-a-piece-of-paper"},{default:o(()=>[a("Written on a piece of paper")]),_:1})]),e("li",null,[i(t,{to:"#printed-on-a-piece-of-paper"},{default:o(()=>[a("Printed on a piece of paper")]),_:1})]),e("li",null,[i(t,{to:"#on-laminated-paper"},{default:o(()=>[a("On laminated paper")]),_:1})]),e("li",null,[i(t,{to:"#engraved-etched-ablated-stamped-on-a-piece-of-metal"},{default:o(()=>[a("Engraved / etched / ablated / stamped on a piece of metal")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-a-computer"},{default:o(()=>[a("Stored digitally on a computer")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-cd-floppy-disk-laserdisc-or-mini-disc"},{default:o(()=>[a("Stored digitally on CD, floppy disk, laserdisc, or mini-disc")]),_:1})]),e("li",null,[i(t,{to:"#stored-digitally-on-a-flash-drive"},{default:o(()=>[a("Stored digitally on a flash drive")]),_:1})]),e("li",null,[i(t,{to:"#a-pre-funded-physical-bitcoin-coin-where-the-manufacturer-generates-and-installs-the-secret-key"},{default:o(()=>[a("A pre-funded physical bitcoin coin (where the manufacturer generates and installs the secret key)")]),_:1})])])])])]),p])}const b=r(c,[["render",m],["__file","BackupBestPractices.html.vue"]]);export{b as default}; diff --git a/assets/BitcoinFullNode.html.d412c934.js b/assets/BitcoinFullNode.html.c430105c.js similarity index 99% rename from assets/BitcoinFullNode.html.d412c934.js rename to assets/BitcoinFullNode.html.c430105c.js index 05dcc0e269..5ec46c608b 100644 --- a/assets/BitcoinFullNode.html.d412c934.js +++ b/assets/BitcoinFullNode.html.c430105c.js @@ -1 +1 @@ -import{a as l,_ as d}from"./SettingsBitcoinCore.fab2a9f8.js";import{_ as c,r as s,o as u,c as h,a as e,d as n,w as t,b as o,e as f}from"./app.a5b7c2b2.js";const b={},y=e("h1",{id:"bitcoin-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-full-node","aria-hidden":"true"},"#"),o(" Bitcoin Full Node")],-1),p={class:"table-of-contents"},g=e("h2",{id:"the-importance-of-running-a-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-importance-of-running-a-full-node","aria-hidden":"true"},"#"),o(" The importance of running a full node")],-1),m=e("p",null,"When running a Bitcoin full node, you define the precise monetary rules that you voluntarily agree on. Nobody else forces this choice upon you. Thus any sovereign individual who wants to claim financial independence must run a full node. Once your own rules are firmly established, your software discovers other nodes in the Bitcoin peer-to-peer network which do not break your rules. These peers send you transactions and blocks which are valid according to their set of rules, and you verify for yourself if they are also correct for you. If one of the proposed transactions breaks your own rules, then you mark it as invalid, disconnect from and ban the node who sent you the malicious transaction.",-1),w=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Claim your monetary sovereignty"),e("p",null,"With your full node you define, verify, and enforce the rules of your sound money Bitcoin.")],-1),_=e("p",null,"Only by running a full node, do you verify by yourself that the money you receive is actually valid bitcoin. You do not trust an external third party, and thus you also do not leak any sensitive financial information.",-1),v={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},k={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},W={href:"https://libbitcoin.info/",target:"_blank",rel:"noopener noreferrer"},B=e("h2",{id:"how-does-wasabi-use-your-bitcoin-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-does-wasabi-use-your-bitcoin-full-node","aria-hidden":"true"},"#"),o(" How does Wasabi use your Bitcoin full node")],-1),x={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},T=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"Work in progress"),e("p",null,[o("The zkSNACKs server has to be trusted to serve correct filters. This current work in progress integration "),e("strong",null,"does not"),o(" verify consensus within Wasabi.")])],-1),P=e("code",null,"smartfee",-1),I=e("p",null,"The future goal is that the local full node (Knots) is used to generate the BIP 158 block filters from the verified blocks. Only then is there full verification, and no trust in the zkSNACKs server.",-1),N=e("h2",{id:"bitcoind-within-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoind-within-wasabi","aria-hidden":"true"},"#"),o(" bitcoind within Wasabi")],-1),C={href:"https://bitcoinknots.org",target:"_blank",rel:"noopener noreferrer"},K=f('

Wasabi Wallet Bitcoin Knots full node integration

Using an already existing local Bitcoin full node

If you have a Bitcoin full node already pre-installed on the same computer you use to run Wasabi Wallet, then Wasabi will use your node by default. You do not need to change anything in the settings, it should work plug and play. This is especially useful to save on bandwidth, as you have already downloaded and verified a block with your full node, so you don't need to download it again with Wasabi.

Using an already existing remote Bitcoin full node

If you have a Bitcoin full node already on a remote computer, then Wasabi Wallet can use this too. In the Bitcoin settings, specify the local IP address and port or the Tor onion service of your full node.

Wasabi Wallet remote Bitcoin P2P full node endpoint

Verify that Wasabi is connected to your full node

There are two ways to confirm that your Wasabi client is connected to your own full node.

First, in the Wasabi logs. Once you receive a transaction Wasabi downloads the block containing that transaction from your node, and in the logs you should see: Block {hash} acquired from node '{node}'.

Second, by checking the connected peers inside your full node. Wasabi will show up as one of the connected peers while it is downloading a block. You can check this in the Bitcoin Core / Knots GUI by clicking on Window -> Peers. During the period when Wasabi is fetching a block, it will show up in the User Agent column. Alternatively, you can use the Bitcoin RPC call bitcoin-cli getpeerinfo and see the Wasabi client listed.

',10);function U(A,L){const i=s("router-link"),a=s("ExternalLinkIcon"),r=s("RouterLink");return u(),h("div",null,[y,e("nav",p,[e("ul",null,[e("li",null,[n(i,{to:"#the-importance-of-running-a-full-node"},{default:t(()=>[o("The importance of running a full node")]),_:1})]),e("li",null,[n(i,{to:"#how-does-wasabi-use-your-bitcoin-full-node"},{default:t(()=>[o("How does Wasabi use your Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#bitcoind-within-wasabi"},{default:t(()=>[o("bitcoind within Wasabi")]),_:1})]),e("li",null,[n(i,{to:"#using-an-already-existing-local-bitcoin-full-node"},{default:t(()=>[o("Using an already existing local Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#using-an-already-existing-remote-bitcoin-full-node"},{default:t(()=>[o("Using an already existing remote Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#verify-that-wasabi-is-connected-to-your-full-node"},{default:t(()=>[o("Verify that Wasabi is connected to your full node")]),_:1})])])]),g,m,w,_,e("p",null,[o("There are several software implementations that function as a full node, for example, "),e("a",v,[o("Bitcoin Core"),n(a)]),o(", "),e("a",k,[o("Bitcoin Knots"),n(a)]),o(", or "),e("a",W,[o("LibBitcoin"),n(a)]),o(".")]),B,e("p",null,[o("Wasabi currently has a work in progress partial Bitcoin Knots integration. As of now, the zkSNACKs coordinating server broadcasts "),e("a",x,[o("BIP 158 block filters"),n(a)]),o(" to all Wasabi clients, who locally check if the filter hits for their public keys. Then you know that this block has a transaction of yours included, or maybe it is a false positive.")]),T,e("p",null,[o("If a full node is connected to Wasabi, then the relevant block is fetched from this trusted node, and not from a random P2P node. Wasabi also queries if your local mempool has unconfirmed transactions that are of interest to you. Further, your full node is used to estimate the current mining fee level based on the bitcoind "),P,o(" algorithm. Your full node is not used to broadcast your transactions, as this is done through a random peer-to-peer node with a new tor identity, which is better for your "),n(r,{to:"/why-wasabi/NetworkLevelPrivacy.html"},{default:t(()=>[o("network-level privacy")]),_:1}),o(".")]),I,N,e("p",null,[o("Wasabi Wallet ships with "),e("a",C,[o("Bitcoin Knots"),n(a)]),o(". This means that every Wasabi client has the necessary software to run a Bitcoin full node and define, verify, and enforce monetary consensus with bitcoind, but this verification is not yet used within Wasabi itself, it is a work in progress. By default, bitcoind is not started together with Wasabi. This must be activated explicitly in the settings because this is a bandwidth, CPU and storage-intensive program. It is optional to keep bitcoind running even after Wasabi Wallet is shut down, so as to verify blocks as soon as they are received.")]),K])}const S=c(b,[["render",U],["__file","BitcoinFullNode.html.vue"]]);export{S as default}; +import{a as l,_ as d}from"./SettingsBitcoinCore.fab2a9f8.js";import{_ as c,r as s,o as u,c as h,a as e,d as n,w as t,b as o,e as f}from"./app.65e5b6fd.js";const b={},y=e("h1",{id:"bitcoin-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-full-node","aria-hidden":"true"},"#"),o(" Bitcoin Full Node")],-1),p={class:"table-of-contents"},g=e("h2",{id:"the-importance-of-running-a-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-importance-of-running-a-full-node","aria-hidden":"true"},"#"),o(" The importance of running a full node")],-1),m=e("p",null,"When running a Bitcoin full node, you define the precise monetary rules that you voluntarily agree on. Nobody else forces this choice upon you. Thus any sovereign individual who wants to claim financial independence must run a full node. Once your own rules are firmly established, your software discovers other nodes in the Bitcoin peer-to-peer network which do not break your rules. These peers send you transactions and blocks which are valid according to their set of rules, and you verify for yourself if they are also correct for you. If one of the proposed transactions breaks your own rules, then you mark it as invalid, disconnect from and ban the node who sent you the malicious transaction.",-1),w=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Claim your monetary sovereignty"),e("p",null,"With your full node you define, verify, and enforce the rules of your sound money Bitcoin.")],-1),_=e("p",null,"Only by running a full node, do you verify by yourself that the money you receive is actually valid bitcoin. You do not trust an external third party, and thus you also do not leak any sensitive financial information.",-1),v={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},k={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},W={href:"https://libbitcoin.info/",target:"_blank",rel:"noopener noreferrer"},B=e("h2",{id:"how-does-wasabi-use-your-bitcoin-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-does-wasabi-use-your-bitcoin-full-node","aria-hidden":"true"},"#"),o(" How does Wasabi use your Bitcoin full node")],-1),x={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},T=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"Work in progress"),e("p",null,[o("The zkSNACKs server has to be trusted to serve correct filters. This current work in progress integration "),e("strong",null,"does not"),o(" verify consensus within Wasabi.")])],-1),P=e("code",null,"smartfee",-1),I=e("p",null,"The future goal is that the local full node (Knots) is used to generate the BIP 158 block filters from the verified blocks. Only then is there full verification, and no trust in the zkSNACKs server.",-1),N=e("h2",{id:"bitcoind-within-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoind-within-wasabi","aria-hidden":"true"},"#"),o(" bitcoind within Wasabi")],-1),C={href:"https://bitcoinknots.org",target:"_blank",rel:"noopener noreferrer"},K=f('

Wasabi Wallet Bitcoin Knots full node integration

Using an already existing local Bitcoin full node

If you have a Bitcoin full node already pre-installed on the same computer you use to run Wasabi Wallet, then Wasabi will use your node by default. You do not need to change anything in the settings, it should work plug and play. This is especially useful to save on bandwidth, as you have already downloaded and verified a block with your full node, so you don't need to download it again with Wasabi.

Using an already existing remote Bitcoin full node

If you have a Bitcoin full node already on a remote computer, then Wasabi Wallet can use this too. In the Bitcoin settings, specify the local IP address and port or the Tor onion service of your full node.

Wasabi Wallet remote Bitcoin P2P full node endpoint

Verify that Wasabi is connected to your full node

There are two ways to confirm that your Wasabi client is connected to your own full node.

First, in the Wasabi logs. Once you receive a transaction Wasabi downloads the block containing that transaction from your node, and in the logs you should see: Block {hash} acquired from node '{node}'.

Second, by checking the connected peers inside your full node. Wasabi will show up as one of the connected peers while it is downloading a block. You can check this in the Bitcoin Core / Knots GUI by clicking on Window -> Peers. During the period when Wasabi is fetching a block, it will show up in the User Agent column. Alternatively, you can use the Bitcoin RPC call bitcoin-cli getpeerinfo and see the Wasabi client listed.

',10);function U(A,L){const i=s("router-link"),a=s("ExternalLinkIcon"),r=s("RouterLink");return u(),h("div",null,[y,e("nav",p,[e("ul",null,[e("li",null,[n(i,{to:"#the-importance-of-running-a-full-node"},{default:t(()=>[o("The importance of running a full node")]),_:1})]),e("li",null,[n(i,{to:"#how-does-wasabi-use-your-bitcoin-full-node"},{default:t(()=>[o("How does Wasabi use your Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#bitcoind-within-wasabi"},{default:t(()=>[o("bitcoind within Wasabi")]),_:1})]),e("li",null,[n(i,{to:"#using-an-already-existing-local-bitcoin-full-node"},{default:t(()=>[o("Using an already existing local Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#using-an-already-existing-remote-bitcoin-full-node"},{default:t(()=>[o("Using an already existing remote Bitcoin full node")]),_:1})]),e("li",null,[n(i,{to:"#verify-that-wasabi-is-connected-to-your-full-node"},{default:t(()=>[o("Verify that Wasabi is connected to your full node")]),_:1})])])]),g,m,w,_,e("p",null,[o("There are several software implementations that function as a full node, for example, "),e("a",v,[o("Bitcoin Core"),n(a)]),o(", "),e("a",k,[o("Bitcoin Knots"),n(a)]),o(", or "),e("a",W,[o("LibBitcoin"),n(a)]),o(".")]),B,e("p",null,[o("Wasabi currently has a work in progress partial Bitcoin Knots integration. As of now, the zkSNACKs coordinating server broadcasts "),e("a",x,[o("BIP 158 block filters"),n(a)]),o(" to all Wasabi clients, who locally check if the filter hits for their public keys. Then you know that this block has a transaction of yours included, or maybe it is a false positive.")]),T,e("p",null,[o("If a full node is connected to Wasabi, then the relevant block is fetched from this trusted node, and not from a random P2P node. Wasabi also queries if your local mempool has unconfirmed transactions that are of interest to you. Further, your full node is used to estimate the current mining fee level based on the bitcoind "),P,o(" algorithm. Your full node is not used to broadcast your transactions, as this is done through a random peer-to-peer node with a new tor identity, which is better for your "),n(r,{to:"/why-wasabi/NetworkLevelPrivacy.html"},{default:t(()=>[o("network-level privacy")]),_:1}),o(".")]),I,N,e("p",null,[o("Wasabi Wallet ships with "),e("a",C,[o("Bitcoin Knots"),n(a)]),o(". This means that every Wasabi client has the necessary software to run a Bitcoin full node and define, verify, and enforce monetary consensus with bitcoind, but this verification is not yet used within Wasabi itself, it is a work in progress. By default, bitcoind is not started together with Wasabi. This must be activated explicitly in the settings because this is a bandwidth, CPU and storage-intensive program. It is optional to keep bitcoind running even after Wasabi Wallet is shut down, so as to verify blocks as soon as they are received.")]),K])}const S=c(b,[["render",U],["__file","BitcoinFullNode.html.vue"]]);export{S as default}; diff --git a/assets/BuildSource.html.4c0a7387.js b/assets/BuildSource.html.16ab564a.js similarity index 97% rename from assets/BuildSource.html.4c0a7387.js rename to assets/BuildSource.html.16ab564a.js index 94562679cd..b5d6ce4ea1 100644 --- a/assets/BuildSource.html.4c0a7387.js +++ b/assets/BuildSource.html.16ab564a.js @@ -1,4 +1,4 @@ -import{_ as c,r as o,o as d,c as u,a as e,d as t,w as n,b as a,e as l}from"./app.a5b7c2b2.js";const h={},p=e("h1",{id:"build-from-source-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#build-from-source-code","aria-hidden":"true"},"#"),a(" Build from source code")],-1),b={class:"table-of-contents"},m=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),a(" Introduction")],-1),f=e("h2",{id:"get-the-requirements",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#get-the-requirements","aria-hidden":"true"},"#"),a(" Get The Requirements")],-1),_={href:"https://git-scm.com/downloads",target:"_blank",rel:"noopener noreferrer"},g={href:"https://dotnet.microsoft.com/download",target:"_blank",rel:"noopener noreferrer"},v=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Optional for privacy"),e("p",null,"You can disable .NET's telemetry, which is sending some usage information to Microsoft, by typing:"),e("p",null,[e("code",null,"export DOTNET_CLI_TELEMETRY_OPTOUT=1"),a(" on Linux and macOS.")]),e("p",null,[e("code",null,"setx DOTNET_CLI_TELEMETRY_OPTOUT 1"),a(" to disable it permanently on Windows.")])],-1),k=l(`

Get Wasabi

Clone Wasabi repository:

git clone https://github.com/zkSNACKs/WalletWasabi.git
+import{_ as c,r as o,o as d,c as u,a as e,d as t,w as n,b as a,e as l}from"./app.65e5b6fd.js";const h={},p=e("h1",{id:"build-from-source-code",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#build-from-source-code","aria-hidden":"true"},"#"),a(" Build from source code")],-1),b={class:"table-of-contents"},m=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),a(" Introduction")],-1),f=e("h2",{id:"get-the-requirements",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#get-the-requirements","aria-hidden":"true"},"#"),a(" Get The Requirements")],-1),_={href:"https://git-scm.com/downloads",target:"_blank",rel:"noopener noreferrer"},g={href:"https://dotnet.microsoft.com/download",target:"_blank",rel:"noopener noreferrer"},v=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Optional for privacy"),e("p",null,"You can disable .NET's telemetry, which is sending some usage information to Microsoft, by typing:"),e("p",null,[e("code",null,"export DOTNET_CLI_TELEMETRY_OPTOUT=1"),a(" on Linux and macOS.")]),e("p",null,[e("code",null,"setx DOTNET_CLI_TELEMETRY_OPTOUT 1"),a(" to disable it permanently on Windows.")])],-1),k=l(`
 Get Wasabi
Clone Wasabi repository:
git clone https://github.com/zkSNACKs/WalletWasabi.git
 cd WalletWasabi/WalletWasabi.Fluent.Desktop
 
 Run Wasabi
Build and run the Wasabi client application from the WalletWasabi.Fluent.Desktop folder:
dotnet run
 
 Update Wasabi
git pull
@@ -6,4 +6,4 @@ import{_ as c,r as o,o as d,c as u,a as e,d as t,w as n,b as a,e as l}from"./app
 git fetch nopara73
 git checkout branchname
 git pull
-
`,2);function W(E,B){const s=o("router-link"),i=o("RouterLink"),r=o("ExternalLinkIcon");return d(),u("div",null,[p,e("nav",b,[e("ul",null,[e("li",null,[t(s,{to:"#introduction"},{default:n(()=>[a("Introduction")]),_:1})]),e("li",null,[t(s,{to:"#get-the-requirements"},{default:n(()=>[a("Get The Requirements")]),_:1})]),e("li",null,[t(s,{to:"#get-wasabi"},{default:n(()=>[a("Get Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#run-wasabi"},{default:n(()=>[a("Run Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#update-wasabi"},{default:n(()=>[a("Update Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#check-out-a-developer-branch"},{default:n(()=>[a("Check out a developer branch")]),_:1})])])]),m,e("p",null,[a("You can compile the source code in order to get the most recent commits by the developers. This enables you to try out features or fixes that are not yet released. This can be the main repository master branch for those changes that should be in the next release, or developer branches for cutting edge features. Be aware that these branches might be unstable and can include bugs that lead to a loss of funds, so use with caution and on "),t(i,{to:"/using-wasabi/Testnet.html"},{default:n(()=>[a("testnet")]),_:1}),a(".")]),f,e("ol",null,[e("li",null,[e("p",null,[a("Install "),e("a",_,[a("Git"),t(r)])])]),e("li",null,[e("p",null,[a("Install "),e("a",g,[a(".NET 7.0 SDK"),t(r)]),a(' for "Build apps"')]),v])]),k,e("div",w,[x,T,e("p",null,[a("These developer branches are not thoroughly reviewed by other contributors, and there might be critical bugs in the software that can even cause loss of funds. So only compile these branches if you know what you are doing, and run them at your own risk only on "),t(i,{to:"/using-wasabi/Testnet.html"},{default:n(()=>[a("testnet")]),_:1}),a(".")])]),y])}const N=c(h,[["render",W],["__file","BuildSource.html.vue"]]);export{N as default};
+
`,2);function W(E,B){const s=o("router-link"),i=o("RouterLink"),r=o("ExternalLinkIcon");return d(),u("div",null,[p,e("nav",b,[e("ul",null,[e("li",null,[t(s,{to:"#introduction"},{default:n(()=>[a("Introduction")]),_:1})]),e("li",null,[t(s,{to:"#get-the-requirements"},{default:n(()=>[a("Get The Requirements")]),_:1})]),e("li",null,[t(s,{to:"#get-wasabi"},{default:n(()=>[a("Get Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#run-wasabi"},{default:n(()=>[a("Run Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#update-wasabi"},{default:n(()=>[a("Update Wasabi")]),_:1})]),e("li",null,[t(s,{to:"#check-out-a-developer-branch"},{default:n(()=>[a("Check out a developer branch")]),_:1})])])]),m,e("p",null,[a("You can compile the source code in order to get the most recent commits by the developers. This enables you to try out features or fixes that are not yet released. This can be the main repository master branch for those changes that should be in the next release, or developer branches for cutting edge features. Be aware that these branches might be unstable and can include bugs that lead to a loss of funds, so use with caution and on "),t(i,{to:"/using-wasabi/Testnet.html"},{default:n(()=>[a("testnet")]),_:1}),a(".")]),f,e("ol",null,[e("li",null,[e("p",null,[a("Install "),e("a",_,[a("Git"),t(r)])])]),e("li",null,[e("p",null,[a("Install "),e("a",g,[a(".NET 8.0 SDK"),t(r)]),a(' for "Build apps"')]),v])]),k,e("div",w,[x,T,e("p",null,[a("These developer branches are not thoroughly reviewed by other contributors, and there might be critical bugs in the software that can even cause loss of funds. So only compile these branches if you know what you are doing, and run them at your own risk only on "),t(i,{to:"/using-wasabi/Testnet.html"},{default:n(()=>[a("testnet")]),_:1}),a(".")])]),y])}const N=c(h,[["render",W],["__file","BuildSource.html.vue"]]);export{N as default}; diff --git a/assets/ChangeCoins.html.5adcd926.js b/assets/ChangeCoins.html.c8dc09c4.js similarity index 99% rename from assets/ChangeCoins.html.5adcd926.js rename to assets/ChangeCoins.html.c8dc09c4.js index 3c8f4fb15d..5fa6892699 100644 --- a/assets/ChangeCoins.html.5adcd926.js +++ b/assets/ChangeCoins.html.c8dc09c4.js @@ -1 +1 @@ -import{_ as c,r as s,o as r,c as l,a as e,d as n,w as a,b as t,e as o}from"./app.a5b7c2b2.js";const d={},u=e("h1",{id:"change-coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-coins","aria-hidden":"true"},"#"),t(" Change coins")],-1),y={class:"table-of-contents"},g=o('

Types of change

Non-Coinjoin change

Let's assume you want to send 0.5 bitcoin to Alice. You enter Alice's address in the To field (destination address), and set the Amount to 0.5 BTC. This will be one output of the transaction.

Since your chosen UTXO is worth 2 bitcoins, after sending 0.5 bitcoin to Alice there will be 1.5 bitcoins change from the original amount. This leftover amount will automatically go to a new address in your wallet, and this is called the change output.

This leftover 1.5 bitcoins change UTXO is connected to the input UTXO of the transaction, and thus also has an anonymity set of 1. As a result, when you send this leftover/change coin in a new transaction, it is clear to any observer that you were part of the transaction that sent 0.5 bitcoin to someone.

This process is applicable to any Bitcoin transaction where the sent amount is less than the total value of the input UTXO.

Coinjoin change

In some few cases, especially for the wealthiest user of a coinjoin, there will be an anonymity score 1 output in a coinjoin transaction. Eventhough it is not trivial to link those to the inputs of the same user, they should be handled with care. Wasabi will not automatically spend those change coins in a payment, but instead register them again in a future coinjoin round.

Why change is an issue

Change is not inherently bad, it's a fundamental part of how Bitcoin and the UTXO model works. However, when sending a coin that is change from an earlier transaction, then the receiver can easily deduce that the sender was also part of the previous transaction that generated the change.

',10),f=o('

You want to avoid merging coins with different anonymity set values whenever possible, because this will link these coins and reduce their anonymity set to the lowest value.

Your options to use change privately

Avoid change in the first place

Whenever possible, choose UTXO's for transactions where the destination addresses receive the entire value of your UTXO's, and you don't get any change back. This can easily be done by clicking the shield icon in the top right corner of the transaction preview screen, and adjusting the payment amount to be slightly higher or lower. This might not be possible in some cases where you have to pay a specific value of a payment request.

Make it difficult to deduce the change

',5),p=o('

Spend the change to the same entity as in the initial transaction

If in the first transaction you have 0.10 bitcoin and send Alice 0.04 bitcoin, you get 0.06 bitcoin back as change in a new address, which Alice can see belongs to you. Now, in a second transaction where you want to send Alice 0.05 bitcoin, you can select that 0.06 bitcoin change coin without losing any privacy, because Alice already knows this is your coin.

In this second transaction you will get back 0.01 bitcoin as change, which again, will still be known to Alice. If in a third transaction you want to send Alice 0.02 bitcoin, then you can consolidate the 0.01 bitcoin change with a new 0.10 bitcoin mixed coin, thus getting 0.09 bitcoin change.

Now Alice will know that you owned the 0.10 bitcoin and that you currently own the 0.09 bitcoin change, but she cannot find out about your premix transaction history.

Wasabi will automatically check if you have a coin with the same label for the current payment recipient, and will use those coins to be spent.

Spend the change with another entity, where you don't mind if each of the two know that you transact with the other entity

When you send a transaction to Alice, then she knows that the change output goes back to you. You can use this change to send bitcoin to Bob, and if he has bad privacy habits, Alice can find out you sent to him. But if you have a trusted relationship with the two, then this is alright, and not part of your threat model.

Coinjoin more

Since Wasabi 2.0 has a minimum amount for coinjoin of only 5000 sats, any change coin with an amount larger than that will be registered in a future coinjoin round. If you wait long enough, Wasabi will make sure that you don't have any anonscore 1 change coin in your wallet, but only private coins not linked to any previous payment.

',9);function w(m,b){const i=s("router-link"),h=s("RouterLink");return r(),l("div",null,[u,e("nav",y,[e("ul",null,[e("li",null,[n(i,{to:"#types-of-change"},{default:a(()=>[t("Types of change")]),_:1}),e("ul",null,[e("li",null,[n(i,{to:"#non-coinjoin-change"},{default:a(()=>[t("Non-Coinjoin change")]),_:1})]),e("li",null,[n(i,{to:"#coinjoin-change"},{default:a(()=>[t("Coinjoin change")]),_:1})])])]),e("li",null,[n(i,{to:"#why-change-is-an-issue"},{default:a(()=>[t("Why change is an issue")]),_:1})]),e("li",null,[n(i,{to:"#your-options-to-use-change-privately"},{default:a(()=>[t("Your options to use change privately")]),_:1}),e("ul",null,[e("li",null,[n(i,{to:"#avoid-change-in-the-first-place"},{default:a(()=>[t("Avoid change in the first place")]),_:1})]),e("li",null,[n(i,{to:"#make-it-difficult-to-deduce-the-change"},{default:a(()=>[t("Make it difficult to deduce the change")]),_:1})]),e("li",null,[n(i,{to:"#spend-the-change-to-the-same-entity-as-in-the-initial-transaction"},{default:a(()=>[t("Spend the change to the same entity as in the initial transaction")]),_:1})]),e("li",null,[n(i,{to:"#spend-the-change-with-another-entity-where-you-don-t-mind-if-each-of-the-two-know-that-you-transact-with-the-other-entity"},{default:a(()=>[t("Spend the change with another entity, where you don't mind if each of the two know that you transact with the other entity")]),_:1})]),e("li",null,[n(i,{to:"#coinjoin-more"},{default:a(()=>[t("Coinjoin more")]),_:1})])])])])]),g,e("p",null,[t("Whenever you are merging coins in one transaction, it becomes clear to any outside observer that these coins belong to the same entity, thus linking the previous transaction history. Thus "),n(h,{to:"/why-wasabi/Coins.html#heuristics-identifying-change"},{default:a(()=>[t("identifying change")]),_:1}),t(" based on some heuristics is a top goal of transaction surveillance.")]),f,e("p",null,[t("There are "),n(h,{to:"/why-wasabi/Coins.html#heuristics-identifying-change"},{default:a(()=>[t("common heuristics identifying change outputs")]),_:1}),t(", try to avoid these with every transaction. Don't reuse addresses, don't send precise amounts but randomize them, use replace by fee (RBF) only if necessary, and try to send to bech32 or bech32m addresses.")]),p])}const _=c(d,[["render",w],["__file","ChangeCoins.html.vue"]]);export{_ as default}; +import{_ as c,r as s,o as r,c as l,a as e,d as n,w as a,b as t,e as o}from"./app.65e5b6fd.js";const d={},u=e("h1",{id:"change-coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-coins","aria-hidden":"true"},"#"),t(" Change coins")],-1),y={class:"table-of-contents"},g=o('

Types of change

Non-Coinjoin change

Let's assume you want to send 0.5 bitcoin to Alice. You enter Alice's address in the To field (destination address), and set the Amount to 0.5 BTC. This will be one output of the transaction.

Since your chosen UTXO is worth 2 bitcoins, after sending 0.5 bitcoin to Alice there will be 1.5 bitcoins change from the original amount. This leftover amount will automatically go to a new address in your wallet, and this is called the change output.

This leftover 1.5 bitcoins change UTXO is connected to the input UTXO of the transaction, and thus also has an anonymity set of 1. As a result, when you send this leftover/change coin in a new transaction, it is clear to any observer that you were part of the transaction that sent 0.5 bitcoin to someone.

This process is applicable to any Bitcoin transaction where the sent amount is less than the total value of the input UTXO.

Coinjoin change

In some few cases, especially for the wealthiest user of a coinjoin, there will be an anonymity score 1 output in a coinjoin transaction. Eventhough it is not trivial to link those to the inputs of the same user, they should be handled with care. Wasabi will not automatically spend those change coins in a payment, but instead register them again in a future coinjoin round.

Why change is an issue

Change is not inherently bad, it's a fundamental part of how Bitcoin and the UTXO model works. However, when sending a coin that is change from an earlier transaction, then the receiver can easily deduce that the sender was also part of the previous transaction that generated the change.

',10),f=o('

You want to avoid merging coins with different anonymity set values whenever possible, because this will link these coins and reduce their anonymity set to the lowest value.

Your options to use change privately

Avoid change in the first place

Whenever possible, choose UTXO's for transactions where the destination addresses receive the entire value of your UTXO's, and you don't get any change back. This can easily be done by clicking the shield icon in the top right corner of the transaction preview screen, and adjusting the payment amount to be slightly higher or lower. This might not be possible in some cases where you have to pay a specific value of a payment request.

Make it difficult to deduce the change

',5),p=o('

Spend the change to the same entity as in the initial transaction

If in the first transaction you have 0.10 bitcoin and send Alice 0.04 bitcoin, you get 0.06 bitcoin back as change in a new address, which Alice can see belongs to you. Now, in a second transaction where you want to send Alice 0.05 bitcoin, you can select that 0.06 bitcoin change coin without losing any privacy, because Alice already knows this is your coin.

In this second transaction you will get back 0.01 bitcoin as change, which again, will still be known to Alice. If in a third transaction you want to send Alice 0.02 bitcoin, then you can consolidate the 0.01 bitcoin change with a new 0.10 bitcoin mixed coin, thus getting 0.09 bitcoin change.

Now Alice will know that you owned the 0.10 bitcoin and that you currently own the 0.09 bitcoin change, but she cannot find out about your premix transaction history.

Wasabi will automatically check if you have a coin with the same label for the current payment recipient, and will use those coins to be spent.

Spend the change with another entity, where you don't mind if each of the two know that you transact with the other entity

When you send a transaction to Alice, then she knows that the change output goes back to you. You can use this change to send bitcoin to Bob, and if he has bad privacy habits, Alice can find out you sent to him. But if you have a trusted relationship with the two, then this is alright, and not part of your threat model.

Coinjoin more

Since Wasabi 2.0 has a minimum amount for coinjoin of only 5000 sats, any change coin with an amount larger than that will be registered in a future coinjoin round. If you wait long enough, Wasabi will make sure that you don't have any anonscore 1 change coin in your wallet, but only private coins not linked to any previous payment.

',9);function w(m,b){const i=s("router-link"),h=s("RouterLink");return r(),l("div",null,[u,e("nav",y,[e("ul",null,[e("li",null,[n(i,{to:"#types-of-change"},{default:a(()=>[t("Types of change")]),_:1}),e("ul",null,[e("li",null,[n(i,{to:"#non-coinjoin-change"},{default:a(()=>[t("Non-Coinjoin change")]),_:1})]),e("li",null,[n(i,{to:"#coinjoin-change"},{default:a(()=>[t("Coinjoin change")]),_:1})])])]),e("li",null,[n(i,{to:"#why-change-is-an-issue"},{default:a(()=>[t("Why change is an issue")]),_:1})]),e("li",null,[n(i,{to:"#your-options-to-use-change-privately"},{default:a(()=>[t("Your options to use change privately")]),_:1}),e("ul",null,[e("li",null,[n(i,{to:"#avoid-change-in-the-first-place"},{default:a(()=>[t("Avoid change in the first place")]),_:1})]),e("li",null,[n(i,{to:"#make-it-difficult-to-deduce-the-change"},{default:a(()=>[t("Make it difficult to deduce the change")]),_:1})]),e("li",null,[n(i,{to:"#spend-the-change-to-the-same-entity-as-in-the-initial-transaction"},{default:a(()=>[t("Spend the change to the same entity as in the initial transaction")]),_:1})]),e("li",null,[n(i,{to:"#spend-the-change-with-another-entity-where-you-don-t-mind-if-each-of-the-two-know-that-you-transact-with-the-other-entity"},{default:a(()=>[t("Spend the change with another entity, where you don't mind if each of the two know that you transact with the other entity")]),_:1})]),e("li",null,[n(i,{to:"#coinjoin-more"},{default:a(()=>[t("Coinjoin more")]),_:1})])])])])]),g,e("p",null,[t("Whenever you are merging coins in one transaction, it becomes clear to any outside observer that these coins belong to the same entity, thus linking the previous transaction history. Thus "),n(h,{to:"/why-wasabi/Coins.html#heuristics-identifying-change"},{default:a(()=>[t("identifying change")]),_:1}),t(" based on some heuristics is a top goal of transaction surveillance.")]),f,e("p",null,[t("There are "),n(h,{to:"/why-wasabi/Coins.html#heuristics-identifying-change"},{default:a(()=>[t("common heuristics identifying change outputs")]),_:1}),t(", try to avoid these with every transaction. Don't reuse addresses, don't send precise amounts but randomize them, use replace by fee (RBF) only if necessary, and try to send to bech32 or bech32m addresses.")]),p])}const _=c(d,[["render",w],["__file","ChangeCoins.html.vue"]]);export{_ as default}; diff --git a/assets/CoinJoin.html.d7f3ac7c.js b/assets/CoinJoin.html.ad2cbec7.js similarity index 99% rename from assets/CoinJoin.html.d7f3ac7c.js rename to assets/CoinJoin.html.ad2cbec7.js index c390707938..9b09a3b0c1 100644 --- a/assets/CoinJoin.html.d7f3ac7c.js +++ b/assets/CoinJoin.html.ad2cbec7.js @@ -1 +1 @@ -import{_ as c}from"./AutoStartCoinjoinThreshold.908ffaab.js";import{_ as h}from"./CoinjoinStrategy.5455b7fb.js";import{_ as d,r as l,o as u,c as p,a as e,d as o,w as i,b as t,e as r}from"./app.a5b7c2b2.js";const b="/MusicBoxAwaitingToAutoStartCoinjoin.png",f="/MusicBoxAwaitingOtherParticipants.png",m="/MusicBoxCoinjoinInProgress.png",g="/MusicBoxCoinjoinSuccessful.png",_="/CoinjoinSettings.png",y="/CoinjoinSettingsAutomaticallyStartCoinjoin.png",w="/CoinjoinStrategySettings.png",j={},v=e("h1",{id:"coinjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin","aria-hidden":"true"},"#"),t(" Coinjoin")],-1),x={class:"table-of-contents"},A=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),t(" Introduction")],-1),k={href:"https://en.bitcoin.it/Privacy#CoinJoin",target:"_blank",rel:"noopener noreferrer"},T={href:"https://bitcointalk.org/index.php?topic=279249.msg2983902",target:"_blank",rel:"noopener noreferrer"},C={href:"https://eprint.iacr.org/2021/206",target:"_blank",rel:"noopener noreferrer"},S={href:"https://youtu.be/dGATztn5Ql8",target:"_blank",rel:"noopener noreferrer"},W=e("img",{src:"https://img.youtube.com/vi/dGATztn5Ql8/maxresdefault.jpg",alt:"WabiSabi Coinjoin Explained in 3 Minutes"},null,-1),B=r('

Coinjoin step-by-step

  1. Launch Wasabi and open your wallet.
  2. Wait. Wasabi coinjoins automatically in the background.
  3. You're done! You can make private payments now.

Music box

After opening a hot wallet, it will automatically start a countdown to start coinjoining (±10 minutes). This and other coinjoin related information is shown in the music box.

Music Box Countdown

',5),I=e("em",null,"Waiting to auto-start coinjoin",-1),q=e("p",null,"A blue aura will show up at the the bottom of the wallet, which indicates that the wallet is coinjoining, and the music box message will change.",-1),M=e("p",null,[e("img",{src:f,alt:"Music Box Awaiting Other Participants",title:"Music Box Awaiting Other Participants"})],-1),F=e("p",null,"After some time the blue aura will change to an orange one, this indicates that the coinjoin process is now in a critical phase. Wasabi will prevent you from shutting down the app during the orange aura to not disrupt the coinjoin round.",-1),P=e("p",null,[e("img",{src:m,alt:"Music Box Coinjoin In Progress",title:"Music Box Coinjoin In Progress"})],-1),Q=r('

Music Box Success

Notice that the wallet might have to repeat the coinjoin steps multiple times before a successful coinjoin is created. So it is possible that the aura colors will change without a successful coinjoin. Please leave Wasabi Wallet running, and eventually there will be a successful coinjoin.

More Details

By default, Wasabi starts automatically coinjoining your funds when the total value of the non-private coins is equal to or above the Auto-start coinjoin threshold (0.01 BTC by default). Automatically start coinjoin can be disabled from the coinjoin settings. In case you want to start the process manually, then click the play button; if you want to stop coinjoin, then click the pause button.

Once a coin achieves enough privacy (reaches the Anonymity score target), then the corresponding amount will show up in the wallet's main view as "PRIVATE".

Notice that it is not yet possible to coinjoin from a hardware wallet, the keys must be "hot" on your computer.

Fees

A 0.3% coordination fee will be taken from fresh coins bigger than 0.01 BTC. Coins less than or equal to 0.01 BTC don't pay coordination fees at all, according to the PlebsDontPay threshold.

',8),z=e("h2",{id:"wabisabi-protocol-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wabisabi-protocol-step-by-step","aria-hidden":"true"},"#"),t(" WabiSabi protocol step-by-step")],-1),N=e("p",null,"WabiSabi protocol requires 5 steps to successfully create and broadcast a coinjoin transaction to the bitcoin network.",-1),O=e("p",null,"The round starts either as soon as the number of registered inputs reaches the maximum, or after the input registration time is reached and as long as the minimum number of inputs is satisfied.",-1),D=e("h3",{id:"input-registration",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#input-registration","aria-hidden":"true"},"#"),t(" Input registration")],-1),E={href:"https://tb-manual.torproject.org/managing-identities/",target:"_blank",rel:"noopener noreferrer"},L=e("strong",null,"Alice",-1),U=r('

The Wasabi coordinator now verifies that:

Only when all these checks are passed, does the coordinator allow this input to be registered. The coordinator creates and sends a credential back to Alice, which has the same amount as the input minus fees.

The input registration phase ends when either: the number of registered inputs reaches the maximum, or when the time elapsed and the minimum number of inputs is satisfied.

Connection confirmation

There are many users registering their inputs (with different Alice for each input) in the first phase, and this takes a while. The connection confirmation phase makes sure that all of them are still online and ready to continue. The coordinator verifies the unique ID from each Alice, and if everyone is still communicating. The coordinator sends a zero value credential to each Alice for each successful connection confirmation.

The round is abandoned and re-started if too many Alices have dropped, for example when their Wasabi is shut down, or when their Tor connection is temporarily broken. The connection confirmation phase ends when all Alices have provided their unique IDs, or after a timeout and the number of online Alices is still larger than the minimum number of inputs.

Output registration

',8),V=e("p",null,"First, every client needs to change the value of their credentials to the desired output values. For this, the client presents to the coordinator two old credentials, and two newly created ones. The coordinator does not know the amount value of any of those credentials, but it can verify, that the two pairs sum up to exactly the same value. For example, a user can present one 5 btc and one 0 btc credential, and redeem one 2 btc and one 3 btc credential. Or a user can present one 4 btc and one 1 btc credential, and redeem one 5 btc and one 0 btc credential. After potentially many rounds of reissuance, each client has exactly the amount credential it desires. Each of these reissuance is perfectly private, so the coordinator cannot link any of them to the same user.",-1),R=e("p",null,[t("Next, your Wasabi client generates multiple new Tor identities called "),e("strong",null,"Bob"),t(", which are in no way tied to any Alice. Bob sends to the Wasabi coordinator:")],-1),J=e("ul",null,[e("li",null,"An unblinded credential signed by the coordinator"),e("li",null,"A new (unused) bitcoin address")],-1),G=e("p",null,"Because the coordinator can verify its own credential, it knows that this credential came into existence after an input of at least this much value was registered. However, it cannot know which input exactly.",-1),H=e("p",null,"It is very important that the coordinator cannot link Alice to Bob. Because Alice has sent the cleartext input, and Bob sends the cleartext output. So, if the two were to be linked, then the coordinator can specifically link the input to the output, meaning that the anonymity set is 1. Because Alice received a credential from the coordinator, and because Bob is a new Tor identity not linked to Alice, the coordinator can verify that nobody is cheating, but it cannot deanonymize the peers.",-1),K=e("p",null,"The output registration phase ends when the value of cleartext outputs is equal to the value of inputs, meaning that all Bobs have registered. If after a timeout not all outputs are registered, then this round is abandoned, the missing inputs are temporarily banned, and a new round is started.",-1),Y={class:"custom-container tip"},$=e("p",{class:"custom-container-title"},"Possibility of Taproot outputs from coinjoin",-1),X={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.3",target:"_blank",rel:"noopener noreferrer"},Z=e("h3",{id:"signing",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#signing","aria-hidden":"true"},"#"),t(" Signing")],-1),ee=r('

Each Alice does the following:

The signing phase ends when the coordinator has received all the valid signatures for all the registered inputs.

Blame round

When the signing phase fails due to some Alices disrupting the round (failing to sign or send the signature to the coordinator), then the successful Alices will continue into a blame round. The blame round will redo the coinjoin phases in order to create a successful coinjoin.

This mecanism also prevents coinjoins from being DDoS-ed because bad actors that are willingly disturbing rounds won't be able to join the blame round. The client will keep going to the blame round until there are not enough Alices left to meet the minimum input count of 150.

The blame round is not a mandatory phase of the coinjoin process. It was introduced in order to have a higher coinjoin success rate.

Broadcasting

',8),te=r('

Coinjoin Settings

Wasabi Wallet has automatic coinjoin. It is done by the built-in automatic coinjoin "robot". The robot contains instructions/settings, like how often and when to coinjoin. The user is able to specify these settings in the Coinjoin Settings dialog, according to his own preferences. The wallet ships with default settings, which are good enough for most users.

Wasabi Wallet Coinjoin Settings

Coinjoin settings are wallet specific

As the coinjoin settings apply per individual wallet, it is possible to have multiple wallets with different coinjoin settings.

Automatically start coinjoin

This setting is enabled by default.

When this is enabled, the wallet will automatically start coinjoining soon after the wallet is loaded. The wallet will coinjoin until the privacy progress is 100%.

When this is not enabled, the user will have to manually press the Play button in order to start coinjoining.

Coinjoin Settings Automatically Start Coinjoin

Auto-start coinjoin threshold

The default Auto-start coinjoin threshold is 0.01 BTC.

The wallet will not automatically start coinjoining if the non-private balance is below the Auto-start coinjoin threshold, even if the Automatically start coinjoin is enabled. In this case the user has to manually press Play to start coinjoining. This setting can be used to prevent paying (relatively) high fees for smaller bitcoin amounts.

For example, if the non-private balance is 0.005 BTC and the Auto-start coinjoin threshold is 0.01 BTC, the user will have to manually press Play to start coinjoining.

Auto-start Coinjoin Threshold

It is OK to set the Auto-start coinjoin threshold to 0

If you have some small non-private left overs: you can coinjoin these by pressing Play, or wait until you receive more funds. If you want to always automatically coinjoin ALL your coins, this can be set to 0 BTC. Note that you might pay relatively more fees for coinjoining smaller amounts.

Coinjoin Strategy

',16),oe=e("code",null,"Minimize Costs",-1),ie=e("code",null,"Maximize Speed",-1),ne=e("code",null,"Maximize Privacy",-1),ae=e("code",null,"Anonymity score target",-1),se=e("code",null,"Coinjoin time preference",-1),re=e("code",null,"Red coin isolation",-1),le=e("p",null,[e("img",{src:w,alt:"Coinjoin Strategy Settings",title:"Coinjoin Strategy Settings"})],-1),ce=e("p",null,[t("The default strategy is "),e("code",null,"Maximize Speed"),t(".")],-1),he=e("p",null,"It is possible to make your own custom strategy by using the customize button.",-1),de=e("p",null,[e("img",{src:h,alt:"Coinjoin Strategy",title:"Coinjoin Strategy"})],-1),ue=e("h2",{id:"wasabi-coinjoin-examples",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wasabi-coinjoin-examples","aria-hidden":"true"},"#"),t(" Wasabi Coinjoin examples")],-1),pe=e("p",null,"Here's a list of Wasabi coinjoin examples and how they appear on a block explorer:",-1),be={href:"https://mempool.space/tx/198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70",target:"_blank",rel:"noopener noreferrer"},fe={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70",target:"_blank",rel:"noopener noreferrer"},me={href:"https://mempool.space/tx/b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e",target:"_blank",rel:"noopener noreferrer"},ge={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e",target:"_blank",rel:"noopener noreferrer"},_e={href:"https://mempool.space/tx/72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d",target:"_blank",rel:"noopener noreferrer"},ye={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d",target:"_blank",rel:"noopener noreferrer"},we={href:"https://mempool.space/tx/063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e",target:"_blank",rel:"noopener noreferrer"},je={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e",target:"_blank",rel:"noopener noreferrer"},ve={href:"https://mempool.space/tx/aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc",target:"_blank",rel:"noopener noreferrer"},xe={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc",target:"_blank",rel:"noopener noreferrer"};function Ae(ke,Te){const n=l("router-link"),a=l("ExternalLinkIcon"),s=l("RouterLink");return u(),p("div",null,[v,e("nav",x,[e("ul",null,[e("li",null,[o(n,{to:"#introduction"},{default:i(()=>[t("Introduction")]),_:1})]),e("li",null,[o(n,{to:"#coinjoin-step-by-step"},{default:i(()=>[t("Coinjoin step-by-step")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#music-box"},{default:i(()=>[t("Music box")]),_:1})]),e("li",null,[o(n,{to:"#more-details"},{default:i(()=>[t("More Details")]),_:1})]),e("li",null,[o(n,{to:"#fees"},{default:i(()=>[t("Fees")]),_:1})])])]),e("li",null,[o(n,{to:"#wabisabi-protocol-step-by-step"},{default:i(()=>[t("WabiSabi protocol step-by-step")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#input-registration"},{default:i(()=>[t("Input registration")]),_:1})]),e("li",null,[o(n,{to:"#connection-confirmation"},{default:i(()=>[t("Connection confirmation")]),_:1})]),e("li",null,[o(n,{to:"#output-registration"},{default:i(()=>[t("Output registration")]),_:1})]),e("li",null,[o(n,{to:"#signing"},{default:i(()=>[t("Signing")]),_:1})]),e("li",null,[o(n,{to:"#blame-round"},{default:i(()=>[t("Blame round")]),_:1})]),e("li",null,[o(n,{to:"#broadcasting"},{default:i(()=>[t("Broadcasting")]),_:1})])])]),e("li",null,[o(n,{to:"#coinjoin-settings"},{default:i(()=>[t("Coinjoin Settings")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#automatically-start-coinjoin"},{default:i(()=>[t("Automatically start coinjoin")]),_:1})]),e("li",null,[o(n,{to:"#auto-start-coinjoin-threshold"},{default:i(()=>[t("Auto-start coinjoin threshold")]),_:1})]),e("li",null,[o(n,{to:"#coinjoin-strategy"},{default:i(()=>[t("Coinjoin Strategy")]),_:1})])])]),e("li",null,[o(n,{to:"#wasabi-coinjoin-examples"},{default:i(()=>[t("Wasabi Coinjoin examples")]),_:1})])])]),A,e("p",null,[t("A "),e("a",k,[t("coinjoin"),o(a)]),t(" is a special Bitcoin transaction where several peers get together to literally join their coins in a single transaction. They collaboratively build a transaction where each of them provides some coins as inputs, and fresh addresses as outputs. The concept has been around since the early days of Bitcoin, and it was formalized by the great Greg Maxwell in "),e("a",T,[t("this awesome introductory thread"),o(a)]),t(".")]),e("p",null,[t('The goal is to gain privacy by breaking the link of which input "pays" which output so that none of the outputs can be attributed to the owner of the input. WabiSabi enables centrally coordinated coinjoins with variable amounts in a trustless (meaning nobody can steal) and private (meaning even the coordinator cannot spy) manner, as described in the '),e("a",C,[t("WabiSabi paper"),o(a)]),t(".")]),e("p",null,[e("a",S,[W,o(a)])]),B,e("p",null,[t("After the "),I,t(" countdown is finished the wallet should start participating in the "),o(s,{to:"/using-wasabi/CoinJoin.html#wabisabi-protocol-step-by-step"},{default:i(()=>[t("coinjoin process")]),_:1}),t(".")]),q,M,F,P,e("p",null,[t("If this is succesfull, the coinjoin is completed and the coinjoin "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#how-can-i-see-coinjoins-in-the-history-list"},{default:i(()=>[t("will show up in the history list")]),_:1}),t(".")]),Q,e("p",null,[t("Remixing is free, as well as coinjoining coins 1 hop from a coinjoin, although, Bitcoin mining fees still do apply, as shown in "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-fees-for-the-coinjoin"},{default:i(()=>[t("this table")]),_:1}),t(". So if you send a coinjoined coin and receive a change output, you will not be charged the coordination fee for this change output. The recipient of the payment will not have to pay the coordination fee, as long as he is making coinjoins with the same coordinator.")]),z,N,O,D,e("p",null,[t("During the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-input-registration-phase"},{default:i(()=>[t("input registration")]),_:1}),t(", the client selects how many and which coins will be registered for coinjoin. These coins need to be confirmed on the Bitcoin blockchain. In the background Wasabi generates input proofs, which are signatures over challenge messages, made with the private keys that lock up the coins. With this, the coordinator can verify that you actually own these coins.")]),e("p",null,[t("Wasabi wallet generates a new "),e("a",E,[t("Tor identity"),o(a)]),t(" called "),L,t(" for each input. She is a separate entity, and for every round you use a new Alice who is not linked to any other input or previous connection. With Alice, you send the input ownership proof to the coordinator.")]),U,e("p",null,[t("Now that all peers are online, we are ready to proceed with the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-output-registration-phase"},{default:i(()=>[t("output registration phase")]),_:1}),t(" of the round.")]),V,R,J,G,H,K,e("div",Y,[$,e("p",null,[t("Since Wasabi "),e("a",X,[t("version 2.0.3"),o(a)]),t(" coinjoin outputs can be SegWit v0 and SegWit v1 (Taproot). If running this version or higher, the client registers the output type in a semi-random way (~50% chance of receiving Taproot output).")])]),Z,e("p",null,[t("Now that all inputs and outputs are registered, the coordinator can start the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-signing-phase"},{default:i(()=>[t("signing phase")]),_:1}),t(", by building the coinjoin transaction with all the registered inputs and outputs. It sends this transaction to all the Alices of the round.")]),ee,e("p",null,[t("The coinjoin transaction has been successfully built and signed, and it is now ready to be "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-broadcasting-phase"},{default:i(()=>[t("broadcast")]),_:1}),t(" to the peers of the Bitcoin network. The coordinator sends this transaction over the Tor network to random Bitcoin P2P nodes, and from there it is gossiped to other nodes and miners. To save on mining fees, the target confirmation time is roughly 24 hours.")]),te,e("p",null,[t("Wasabi ships with 3 coinjoin strategies: "),oe,t(", "),ie,t(", and "),ne,t(". Each of these contain different configurations, as shown in "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-differences-settings-per-coinjoin-strategy"},{default:i(()=>[t("this table")]),_:1}),t(". They determine the "),ae,t(", "),se,t(", and if "),re,t(" is enabled or not.")]),le,ce,he,de,ue,pe,e("ul",null,[e("li",null,[e("a",be,[t("198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70"),o(a)]),t(" | "),e("a",fe,[t(".onion version"),o(a)])]),e("li",null,[e("a",me,[t("b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e"),o(a)]),t(" | "),e("a",ge,[t(".onion version"),o(a)])]),e("li",null,[e("a",_e,[t("72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d"),o(a)]),t(" | "),e("a",ye,[t(".onion version"),o(a)])]),e("li",null,[e("a",we,[t("063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e"),o(a)]),t(" | "),e("a",je,[t(".onion version"),o(a)])]),e("li",null,[e("a",ve,[t("aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc"),o(a)]),t(" | "),e("a",xe,[t(".onion version"),o(a)])])])])}const Be=d(j,[["render",Ae],["__file","CoinJoin.html.vue"]]);export{Be as default}; +import{_ as c}from"./AutoStartCoinjoinThreshold.908ffaab.js";import{_ as h}from"./CoinjoinStrategy.5455b7fb.js";import{_ as d,r as l,o as u,c as p,a as e,d as o,w as i,b as t,e as r}from"./app.65e5b6fd.js";const b="/MusicBoxAwaitingToAutoStartCoinjoin.png",f="/MusicBoxAwaitingOtherParticipants.png",m="/MusicBoxCoinjoinInProgress.png",g="/MusicBoxCoinjoinSuccessful.png",_="/CoinjoinSettings.png",y="/CoinjoinSettingsAutomaticallyStartCoinjoin.png",w="/CoinjoinStrategySettings.png",j={},v=e("h1",{id:"coinjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin","aria-hidden":"true"},"#"),t(" Coinjoin")],-1),x={class:"table-of-contents"},A=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),t(" Introduction")],-1),k={href:"https://en.bitcoin.it/Privacy#CoinJoin",target:"_blank",rel:"noopener noreferrer"},T={href:"https://bitcointalk.org/index.php?topic=279249.msg2983902",target:"_blank",rel:"noopener noreferrer"},C={href:"https://eprint.iacr.org/2021/206",target:"_blank",rel:"noopener noreferrer"},S={href:"https://youtu.be/dGATztn5Ql8",target:"_blank",rel:"noopener noreferrer"},W=e("img",{src:"https://img.youtube.com/vi/dGATztn5Ql8/maxresdefault.jpg",alt:"WabiSabi Coinjoin Explained in 3 Minutes"},null,-1),B=r('

Coinjoin step-by-step

  1. Launch Wasabi and open your wallet.
  2. Wait. Wasabi coinjoins automatically in the background.
  3. You're done! You can make private payments now.

Music box

After opening a hot wallet, it will automatically start a countdown to start coinjoining (±10 minutes). This and other coinjoin related information is shown in the music box.

Music Box Countdown

',5),I=e("em",null,"Waiting to auto-start coinjoin",-1),q=e("p",null,"A blue aura will show up at the the bottom of the wallet, which indicates that the wallet is coinjoining, and the music box message will change.",-1),M=e("p",null,[e("img",{src:f,alt:"Music Box Awaiting Other Participants",title:"Music Box Awaiting Other Participants"})],-1),F=e("p",null,"After some time the blue aura will change to an orange one, this indicates that the coinjoin process is now in a critical phase. Wasabi will prevent you from shutting down the app during the orange aura to not disrupt the coinjoin round.",-1),P=e("p",null,[e("img",{src:m,alt:"Music Box Coinjoin In Progress",title:"Music Box Coinjoin In Progress"})],-1),Q=r('

Music Box Success

Notice that the wallet might have to repeat the coinjoin steps multiple times before a successful coinjoin is created. So it is possible that the aura colors will change without a successful coinjoin. Please leave Wasabi Wallet running, and eventually there will be a successful coinjoin.

More Details

By default, Wasabi starts automatically coinjoining your funds when the total value of the non-private coins is equal to or above the Auto-start coinjoin threshold (0.01 BTC by default). Automatically start coinjoin can be disabled from the coinjoin settings. In case you want to start the process manually, then click the play button; if you want to stop coinjoin, then click the pause button.

Once a coin achieves enough privacy (reaches the Anonymity score target), then the corresponding amount will show up in the wallet's main view as "PRIVATE".

Notice that it is not yet possible to coinjoin from a hardware wallet, the keys must be "hot" on your computer.

Fees

A 0.3% coordination fee will be taken from fresh coins bigger than 0.01 BTC. Coins less than or equal to 0.01 BTC don't pay coordination fees at all, according to the PlebsDontPay threshold.

',8),z=e("h2",{id:"wabisabi-protocol-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wabisabi-protocol-step-by-step","aria-hidden":"true"},"#"),t(" WabiSabi protocol step-by-step")],-1),N=e("p",null,"WabiSabi protocol requires 5 steps to successfully create and broadcast a coinjoin transaction to the bitcoin network.",-1),O=e("p",null,"The round starts either as soon as the number of registered inputs reaches the maximum, or after the input registration time is reached and as long as the minimum number of inputs is satisfied.",-1),D=e("h3",{id:"input-registration",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#input-registration","aria-hidden":"true"},"#"),t(" Input registration")],-1),E={href:"https://tb-manual.torproject.org/managing-identities/",target:"_blank",rel:"noopener noreferrer"},L=e("strong",null,"Alice",-1),U=r('

The Wasabi coordinator now verifies that:

Only when all these checks are passed, does the coordinator allow this input to be registered. The coordinator creates and sends a credential back to Alice, which has the same amount as the input minus fees.

The input registration phase ends when either: the number of registered inputs reaches the maximum, or when the time elapsed and the minimum number of inputs is satisfied.

Connection confirmation

There are many users registering their inputs (with different Alice for each input) in the first phase, and this takes a while. The connection confirmation phase makes sure that all of them are still online and ready to continue. The coordinator verifies the unique ID from each Alice, and if everyone is still communicating. The coordinator sends a zero value credential to each Alice for each successful connection confirmation.

The round is abandoned and re-started if too many Alices have dropped, for example when their Wasabi is shut down, or when their Tor connection is temporarily broken. The connection confirmation phase ends when all Alices have provided their unique IDs, or after a timeout and the number of online Alices is still larger than the minimum number of inputs.

Output registration

',8),V=e("p",null,"First, every client needs to change the value of their credentials to the desired output values. For this, the client presents to the coordinator two old credentials, and two newly created ones. The coordinator does not know the amount value of any of those credentials, but it can verify, that the two pairs sum up to exactly the same value. For example, a user can present one 5 btc and one 0 btc credential, and redeem one 2 btc and one 3 btc credential. Or a user can present one 4 btc and one 1 btc credential, and redeem one 5 btc and one 0 btc credential. After potentially many rounds of reissuance, each client has exactly the amount credential it desires. Each of these reissuance is perfectly private, so the coordinator cannot link any of them to the same user.",-1),R=e("p",null,[t("Next, your Wasabi client generates multiple new Tor identities called "),e("strong",null,"Bob"),t(", which are in no way tied to any Alice. Bob sends to the Wasabi coordinator:")],-1),J=e("ul",null,[e("li",null,"An unblinded credential signed by the coordinator"),e("li",null,"A new (unused) bitcoin address")],-1),G=e("p",null,"Because the coordinator can verify its own credential, it knows that this credential came into existence after an input of at least this much value was registered. However, it cannot know which input exactly.",-1),H=e("p",null,"It is very important that the coordinator cannot link Alice to Bob. Because Alice has sent the cleartext input, and Bob sends the cleartext output. So, if the two were to be linked, then the coordinator can specifically link the input to the output, meaning that the anonymity set is 1. Because Alice received a credential from the coordinator, and because Bob is a new Tor identity not linked to Alice, the coordinator can verify that nobody is cheating, but it cannot deanonymize the peers.",-1),K=e("p",null,"The output registration phase ends when the value of cleartext outputs is equal to the value of inputs, meaning that all Bobs have registered. If after a timeout not all outputs are registered, then this round is abandoned, the missing inputs are temporarily banned, and a new round is started.",-1),Y={class:"custom-container tip"},$=e("p",{class:"custom-container-title"},"Possibility of Taproot outputs from coinjoin",-1),X={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.3",target:"_blank",rel:"noopener noreferrer"},Z=e("h3",{id:"signing",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#signing","aria-hidden":"true"},"#"),t(" Signing")],-1),ee=r('

Each Alice does the following:

The signing phase ends when the coordinator has received all the valid signatures for all the registered inputs.

Blame round

When the signing phase fails due to some Alices disrupting the round (failing to sign or send the signature to the coordinator), then the successful Alices will continue into a blame round. The blame round will redo the coinjoin phases in order to create a successful coinjoin.

This mecanism also prevents coinjoins from being DDoS-ed because bad actors that are willingly disturbing rounds won't be able to join the blame round. The client will keep going to the blame round until there are not enough Alices left to meet the minimum input count of 150.

The blame round is not a mandatory phase of the coinjoin process. It was introduced in order to have a higher coinjoin success rate.

Broadcasting

',8),te=r('

Coinjoin Settings

Wasabi Wallet has automatic coinjoin. It is done by the built-in automatic coinjoin "robot". The robot contains instructions/settings, like how often and when to coinjoin. The user is able to specify these settings in the Coinjoin Settings dialog, according to his own preferences. The wallet ships with default settings, which are good enough for most users.

Wasabi Wallet Coinjoin Settings

Coinjoin settings are wallet specific

As the coinjoin settings apply per individual wallet, it is possible to have multiple wallets with different coinjoin settings.

Automatically start coinjoin

This setting is enabled by default.

When this is enabled, the wallet will automatically start coinjoining soon after the wallet is loaded. The wallet will coinjoin until the privacy progress is 100%.

When this is not enabled, the user will have to manually press the Play button in order to start coinjoining.

Coinjoin Settings Automatically Start Coinjoin

Auto-start coinjoin threshold

The default Auto-start coinjoin threshold is 0.01 BTC.

The wallet will not automatically start coinjoining if the non-private balance is below the Auto-start coinjoin threshold, even if the Automatically start coinjoin is enabled. In this case the user has to manually press Play to start coinjoining. This setting can be used to prevent paying (relatively) high fees for smaller bitcoin amounts.

For example, if the non-private balance is 0.005 BTC and the Auto-start coinjoin threshold is 0.01 BTC, the user will have to manually press Play to start coinjoining.

Auto-start Coinjoin Threshold

It is OK to set the Auto-start coinjoin threshold to 0

If you have some small non-private left overs: you can coinjoin these by pressing Play, or wait until you receive more funds. If you want to always automatically coinjoin ALL your coins, this can be set to 0 BTC. Note that you might pay relatively more fees for coinjoining smaller amounts.

Coinjoin Strategy

',16),oe=e("code",null,"Minimize Costs",-1),ie=e("code",null,"Maximize Speed",-1),ne=e("code",null,"Maximize Privacy",-1),ae=e("code",null,"Anonymity score target",-1),se=e("code",null,"Coinjoin time preference",-1),re=e("code",null,"Red coin isolation",-1),le=e("p",null,[e("img",{src:w,alt:"Coinjoin Strategy Settings",title:"Coinjoin Strategy Settings"})],-1),ce=e("p",null,[t("The default strategy is "),e("code",null,"Maximize Speed"),t(".")],-1),he=e("p",null,"It is possible to make your own custom strategy by using the customize button.",-1),de=e("p",null,[e("img",{src:h,alt:"Coinjoin Strategy",title:"Coinjoin Strategy"})],-1),ue=e("h2",{id:"wasabi-coinjoin-examples",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wasabi-coinjoin-examples","aria-hidden":"true"},"#"),t(" Wasabi Coinjoin examples")],-1),pe=e("p",null,"Here's a list of Wasabi coinjoin examples and how they appear on a block explorer:",-1),be={href:"https://mempool.space/tx/198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70",target:"_blank",rel:"noopener noreferrer"},fe={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70",target:"_blank",rel:"noopener noreferrer"},me={href:"https://mempool.space/tx/b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e",target:"_blank",rel:"noopener noreferrer"},ge={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e",target:"_blank",rel:"noopener noreferrer"},_e={href:"https://mempool.space/tx/72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d",target:"_blank",rel:"noopener noreferrer"},ye={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d",target:"_blank",rel:"noopener noreferrer"},we={href:"https://mempool.space/tx/063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e",target:"_blank",rel:"noopener noreferrer"},je={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e",target:"_blank",rel:"noopener noreferrer"},ve={href:"https://mempool.space/tx/aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc",target:"_blank",rel:"noopener noreferrer"},xe={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/tx/aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc",target:"_blank",rel:"noopener noreferrer"};function Ae(ke,Te){const n=l("router-link"),a=l("ExternalLinkIcon"),s=l("RouterLink");return u(),p("div",null,[v,e("nav",x,[e("ul",null,[e("li",null,[o(n,{to:"#introduction"},{default:i(()=>[t("Introduction")]),_:1})]),e("li",null,[o(n,{to:"#coinjoin-step-by-step"},{default:i(()=>[t("Coinjoin step-by-step")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#music-box"},{default:i(()=>[t("Music box")]),_:1})]),e("li",null,[o(n,{to:"#more-details"},{default:i(()=>[t("More Details")]),_:1})]),e("li",null,[o(n,{to:"#fees"},{default:i(()=>[t("Fees")]),_:1})])])]),e("li",null,[o(n,{to:"#wabisabi-protocol-step-by-step"},{default:i(()=>[t("WabiSabi protocol step-by-step")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#input-registration"},{default:i(()=>[t("Input registration")]),_:1})]),e("li",null,[o(n,{to:"#connection-confirmation"},{default:i(()=>[t("Connection confirmation")]),_:1})]),e("li",null,[o(n,{to:"#output-registration"},{default:i(()=>[t("Output registration")]),_:1})]),e("li",null,[o(n,{to:"#signing"},{default:i(()=>[t("Signing")]),_:1})]),e("li",null,[o(n,{to:"#blame-round"},{default:i(()=>[t("Blame round")]),_:1})]),e("li",null,[o(n,{to:"#broadcasting"},{default:i(()=>[t("Broadcasting")]),_:1})])])]),e("li",null,[o(n,{to:"#coinjoin-settings"},{default:i(()=>[t("Coinjoin Settings")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#automatically-start-coinjoin"},{default:i(()=>[t("Automatically start coinjoin")]),_:1})]),e("li",null,[o(n,{to:"#auto-start-coinjoin-threshold"},{default:i(()=>[t("Auto-start coinjoin threshold")]),_:1})]),e("li",null,[o(n,{to:"#coinjoin-strategy"},{default:i(()=>[t("Coinjoin Strategy")]),_:1})])])]),e("li",null,[o(n,{to:"#wasabi-coinjoin-examples"},{default:i(()=>[t("Wasabi Coinjoin examples")]),_:1})])])]),A,e("p",null,[t("A "),e("a",k,[t("coinjoin"),o(a)]),t(" is a special Bitcoin transaction where several peers get together to literally join their coins in a single transaction. They collaboratively build a transaction where each of them provides some coins as inputs, and fresh addresses as outputs. The concept has been around since the early days of Bitcoin, and it was formalized by the great Greg Maxwell in "),e("a",T,[t("this awesome introductory thread"),o(a)]),t(".")]),e("p",null,[t('The goal is to gain privacy by breaking the link of which input "pays" which output so that none of the outputs can be attributed to the owner of the input. WabiSabi enables centrally coordinated coinjoins with variable amounts in a trustless (meaning nobody can steal) and private (meaning even the coordinator cannot spy) manner, as described in the '),e("a",C,[t("WabiSabi paper"),o(a)]),t(".")]),e("p",null,[e("a",S,[W,o(a)])]),B,e("p",null,[t("After the "),I,t(" countdown is finished the wallet should start participating in the "),o(s,{to:"/using-wasabi/CoinJoin.html#wabisabi-protocol-step-by-step"},{default:i(()=>[t("coinjoin process")]),_:1}),t(".")]),q,M,F,P,e("p",null,[t("If this is succesfull, the coinjoin is completed and the coinjoin "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#how-can-i-see-coinjoins-in-the-history-list"},{default:i(()=>[t("will show up in the history list")]),_:1}),t(".")]),Q,e("p",null,[t("Remixing is free, as well as coinjoining coins 1 hop from a coinjoin, although, Bitcoin mining fees still do apply, as shown in "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-fees-for-the-coinjoin"},{default:i(()=>[t("this table")]),_:1}),t(". So if you send a coinjoined coin and receive a change output, you will not be charged the coordination fee for this change output. The recipient of the payment will not have to pay the coordination fee, as long as he is making coinjoins with the same coordinator.")]),z,N,O,D,e("p",null,[t("During the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-input-registration-phase"},{default:i(()=>[t("input registration")]),_:1}),t(", the client selects how many and which coins will be registered for coinjoin. These coins need to be confirmed on the Bitcoin blockchain. In the background Wasabi generates input proofs, which are signatures over challenge messages, made with the private keys that lock up the coins. With this, the coordinator can verify that you actually own these coins.")]),e("p",null,[t("Wasabi wallet generates a new "),e("a",E,[t("Tor identity"),o(a)]),t(" called "),L,t(" for each input. She is a separate entity, and for every round you use a new Alice who is not linked to any other input or previous connection. With Alice, you send the input ownership proof to the coordinator.")]),U,e("p",null,[t("Now that all peers are online, we are ready to proceed with the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-output-registration-phase"},{default:i(()=>[t("output registration phase")]),_:1}),t(" of the round.")]),V,R,J,G,H,K,e("div",Y,[$,e("p",null,[t("Since Wasabi "),e("a",X,[t("version 2.0.3"),o(a)]),t(" coinjoin outputs can be SegWit v0 and SegWit v1 (Taproot). If running this version or higher, the client registers the output type in a semi-random way (~50% chance of receiving Taproot output).")])]),Z,e("p",null,[t("Now that all inputs and outputs are registered, the coordinator can start the "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-signing-phase"},{default:i(()=>[t("signing phase")]),_:1}),t(", by building the coinjoin transaction with all the registered inputs and outputs. It sends this transaction to all the Alices of the round.")]),ee,e("p",null,[t("The coinjoin transaction has been successfully built and signed, and it is now ready to be "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-is-happening-in-the-broadcasting-phase"},{default:i(()=>[t("broadcast")]),_:1}),t(" to the peers of the Bitcoin network. The coordinator sends this transaction over the Tor network to random Bitcoin P2P nodes, and from there it is gossiped to other nodes and miners. To save on mining fees, the target confirmation time is roughly 24 hours.")]),te,e("p",null,[t("Wasabi ships with 3 coinjoin strategies: "),oe,t(", "),ie,t(", and "),ne,t(". Each of these contain different configurations, as shown in "),o(s,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-differences-settings-per-coinjoin-strategy"},{default:i(()=>[t("this table")]),_:1}),t(". They determine the "),ae,t(", "),se,t(", and if "),re,t(" is enabled or not.")]),le,ce,he,de,ue,pe,e("ul",null,[e("li",null,[e("a",be,[t("198aee6e1b2cad9b7c3e4cd12962980fbaab0b20c07016031d0c2416b3ef9b70"),o(a)]),t(" | "),e("a",fe,[t(".onion version"),o(a)])]),e("li",null,[e("a",me,[t("b77cb1ad9a1c164c868f89927193178ec44f1006ca154f8b97008d14bf2c4a6e"),o(a)]),t(" | "),e("a",ge,[t(".onion version"),o(a)])]),e("li",null,[e("a",_e,[t("72f4b05845564c59982b4b5ae0d8aa7322d08907198fbcdae48390fbe0538e8d"),o(a)]),t(" | "),e("a",ye,[t(".onion version"),o(a)])]),e("li",null,[e("a",we,[t("063f001403aaa4e44f9f35faf44507f373824657a7ef39907a6907298d9ee56e"),o(a)]),t(" | "),e("a",je,[t(".onion version"),o(a)])]),e("li",null,[e("a",ve,[t("aabb0a2b43b274c9ae287e3837f9f8a8d8a378ce93153dc52de9978d2bb72cbc"),o(a)]),t(" | "),e("a",xe,[t(".onion version"),o(a)])])])])}const Be=d(j,[["render",Ae],["__file","CoinJoin.html.vue"]]);export{Be as default}; diff --git a/assets/Coins.html.6eed3b2b.js b/assets/Coins.html.d44b27c7.js similarity index 99% rename from assets/Coins.html.6eed3b2b.js rename to assets/Coins.html.d44b27c7.js index 76841a568f..5e9f188ff8 100644 --- a/assets/Coins.html.6eed3b2b.js +++ b/assets/Coins.html.d44b27c7.js @@ -1,4 +1,4 @@ -import{_ as c,r as l,o as h,c as d,a as e,b as n,d as t,w as a,e as o}from"./app.a5b7c2b2.js";const u={},b=e("h1",{id:"coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coins","aria-hidden":"true"},"#"),n(" Coins")],-1),p={href:"https://developer.bitcoin.org/devguide/block_chain.html",target:"_blank",rel:"noopener noreferrer"},g={href:"https://en.bitcoin.it/wiki/Coinbase",target:"_blank",rel:"noopener noreferrer"},m={class:"table-of-contents"},f=o('

Problem

UTXOs are not fungible

Each UTXO is a unique snowflake with a public transaction history. For example, when Alice sends a coin to Bob, then Bob does not just have any random UTXO, but he has specifically the coin that Alice has sent him. When Bob sends this coin to Charlie, then Charlie can check the history of the coin and see the transaction from Alice to Bob. But due to the pseudonymity of Bitcoin, he does not necessarily find out that Alice is involved.

Further, when Alice has one non-private coin and one private coin, and she selects both of them as the inputs of a transaction, the linking of these two coins strongly suggests that the coin that was private also belongs to Alice. This means that coin consolidation can lead to an overall decrease in privacy, especially when using an automatic coin selection algorithm.

Wasabi's Solution

Manual coin labeling and selection

Using Wasabi it is mandatory to label every receiving and destination address. This helps the user to know where their coins came from so that they can judge whether there are privacy concerns when sending a specific coin to a specific receiver. The default Send workflow uses the auto coin selection algorithm, which is based on the labeling system.

',8),v=e("h3",{id:"change-avoidance-suggestion",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-avoidance-suggestion","aria-hidden":"true"},"#"),n(" Change avoidance suggestion")],-1),_=e("em",null,"Preview Transaction",-1),y=e("h2",{id:"heuristics-identifying-change",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#heuristics-identifying-change","aria-hidden":"true"},"#"),n(" Heuristics identifying change")],-1),w=e("h3",{id:"address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address-reuse","aria-hidden":"true"},"#"),n(" Address reuse")],-1),x=e("p",null,"When several coins have the same address, then they are owned by the same entity. Thus if a transaction has a reused address in the output, it is very likely to be the payment amount from one entity to another. Thus the other output of this transaction is likely to be the change of the entity providing the inputs of the transaction.",-1),k={class:"custom-container warning"},C=e("p",{class:"custom-container-title"},"Remember",-1),T=o(`

Wallet fingerprinting

Different software wallets have different methods of creating Bitcoin transactions. So if it is known that a transaction was created by a specific wallet, then it can be checked how this wallet handles change.

Wasabi tries to build the most common form of transaction structure, thus reducing the likelihood of identifying any given transaction as being from Wasabi. However, Wasabi CoinJoins are very easily fingerprinted, and any coin associated is clearly managed with Wasabi Wallet.

Round numbers

When making a payment, then often the destination address receives a round number of bitcoin. Because the input is usually a non-round number, the other output will also be a non-round number. This makes it clear that the non-round number output is the change back to the sender.

A [0.1293 0112 btc]  -->  B [0.0500 0000 btc]
+import{_ as c,r as l,o as h,c as d,a as e,b as n,d as t,w as a,e as o}from"./app.65e5b6fd.js";const u={},b=e("h1",{id:"coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coins","aria-hidden":"true"},"#"),n(" Coins")],-1),p={href:"https://developer.bitcoin.org/devguide/block_chain.html",target:"_blank",rel:"noopener noreferrer"},g={href:"https://en.bitcoin.it/wiki/Coinbase",target:"_blank",rel:"noopener noreferrer"},m={class:"table-of-contents"},f=o('
 Problem
 UTXOs are not fungible
Each UTXO is a unique snowflake with a public transaction history. For example, when Alice sends a coin to Bob, then Bob does not just have any random UTXO, but he has specifically the coin that Alice has sent him. When Bob sends this coin to Charlie, then Charlie can check the history of the coin and see the transaction from Alice to Bob. But due to the pseudonymity of Bitcoin, he does not necessarily find out that Alice is involved.
Further, when Alice has one non-private coin and one private coin, and she selects both of them as the inputs of a transaction, the linking of these two coins strongly suggests that the coin that was private also belongs to Alice. This means that coin consolidation can lead to an overall decrease in privacy, especially when using an automatic coin selection algorithm.
 Wasabi's Solution
 Manual coin labeling and selection
Using Wasabi it is mandatory to label every receiving and destination address. This helps the user to know where their coins came from so that they can judge whether there are privacy concerns when sending a specific coin to a specific receiver. The default Send workflow uses the auto coin selection algorithm, which is based on the labeling system.
',8),v=e("h3",{id:"change-avoidance-suggestion",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-avoidance-suggestion","aria-hidden":"true"},"#"),n(" Change avoidance suggestion")],-1),_=e("em",null,"Preview Transaction",-1),y=e("h2",{id:"heuristics-identifying-change",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#heuristics-identifying-change","aria-hidden":"true"},"#"),n(" Heuristics identifying change")],-1),w=e("h3",{id:"address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address-reuse","aria-hidden":"true"},"#"),n(" Address reuse")],-1),x=e("p",null,"When several coins have the same address, then they are owned by the same entity. Thus if a transaction has a reused address in the output, it is very likely to be the payment amount from one entity to another. Thus the other output of this transaction is likely to be the change of the entity providing the inputs of the transaction.",-1),k={class:"custom-container warning"},C=e("p",{class:"custom-container-title"},"Remember",-1),T=o(`
 Wallet fingerprinting
Different software wallets have different methods of creating Bitcoin transactions. So if it is known that a transaction was created by a specific wallet, then it can be checked how this wallet handles change.
Wasabi tries to build the most common form of transaction structure, thus reducing the likelihood of identifying any given transaction as being from Wasabi. However, Wasabi CoinJoins are very easily fingerprinted, and any coin associated is clearly managed with Wasabi Wallet.
 Round numbers
When making a payment, then often the destination address receives a round number of bitcoin. Because the input is usually a non-round number, the other output will also be a non-round number. This makes it clear that the non-round number output is the change back to the sender.
A [0.1293 0112 btc]  -->  B [0.0500 0000 btc]
                           C [0.0792 9962 btc] (= change)
 
TIP
In order to protect your privacy, add or remove (when possible) a couple of sats from the payment amount to obfuscate which output is your change and which one is the payment.
 CoinJoin
A CoinJoin has many unequal value inputs, and creates several equal value anonset outputs, as well as unequal value outputs, making it clear that these are the change outputs.
`,9),B={class:"custom-container tip"},W=e("p",{class:"custom-container-title"},"TIP",-1),A=o(`
                C [1 btc]
 A [6 btc]  -->  D [1 btc]
diff --git a/assets/ColdWasabi.html.54e9c212.js b/assets/ColdWasabi.html.37d7673c.js
similarity index 99%
rename from assets/ColdWasabi.html.54e9c212.js
rename to assets/ColdWasabi.html.37d7673c.js
index 57dcc1278c..329b51b793 100644
--- a/assets/ColdWasabi.html.54e9c212.js
+++ b/assets/ColdWasabi.html.37d7673c.js
@@ -1 +1 @@
-import{_ as d,r as s,o as c,c as h,a as t,d as a,w as o,b as e,e as l}from"./app.a5b7c2b2.js";const u={},w=t("h1",{id:"cold-wasabi-hardware-wallet-mode",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#cold-wasabi-hardware-wallet-mode","aria-hidden":"true"},"#"),e(" Cold-Wasabi Hardware Wallet Mode")],-1),p={class:"table-of-contents"},b=t("h2",{id:"using-hardware-wallet-step-by-step",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#using-hardware-wallet-step-by-step","aria-hidden":"true"},"#"),e(" Using hardware wallet step-by-step")],-1),m=l("
  • Start your Wasabi Wallet and go to Add Wallet.
  • Click on Connect to hardware wallet and then connect the hardware wallet via cable. Alternatively, you can import a Coldcard skeleton file via SD card by using Import Wallet at the Add Wallet dialog.
  • Confirm that the detected hardware wallet is correct.
  • Click Open, and wait for the wallet to load.
    • ",4),f=t("code",null,"Send",-1),g={class:"custom-container warning"},y=t("p",{class:"custom-container-title"},"No coinjoin",-1),v=l('
     What is Cold Storage
    Cold storage refers to generating and storing private keys completely offline. This is an often-used security precaution, especially dealing with large amounts of bitcoin. Because the private keys are not on a computer that is connected to the internet, many remote attack vectors are nullified.
    Methods of cold storage include keeping private keys on a:
    • USB drive or other data storage medium
    • Paper wallet
    • Bearer item such as a physical bitcoin
    • Hardware wallet
    Use a hardware wallet for cold storage
    There are multiple ways to exercise cold storage, however it is highly reccommended to use a hardware wallet. This is by far the best and most secure way of using bitcoin for almost all users.
     Hardware Wallet with Wasabi
    ',6),_={href:"https://github.com/bitcoin-core/hwi",target:"_blank",rel:"noopener noreferrer"},k={href:"https://trezor.io",target:"_blank",rel:"noopener noreferrer"},W={href:"https://ledger.com",target:"_blank",rel:"noopener noreferrer"},S={href:"https://coldcard.com",target:"_blank",rel:"noopener noreferrer"},C=l('
     Connecting via USB
     Import the wallet
    1. Go to Add wallet.
    2. Click on Connect to hardware wallet.
    3. Give the wallet a name.
    4. Connect the hardware wallet to the PC and enter the pin on the hardware wallet to unlock it.
    5. Confirm that the correct hardware wallet is detected.
    6. Open the wallet.
    This wallet can be used as a watch-only wallet when the hardware wallet device is not connected.
    Wasabi remembers the wallet's information like xpub, wallet fingerprint and addresses etc. But it never knows the private keys, which are on the hardware wallet. So, you can see the balance and all it's transactions in Wasabi and you can generate addresses, but you cannot send without the hardware wallet being connected. Because you need to sign (confirm) the outgoing transactions on the hardware wallet.
     Receiving bitcoin
    ',5),x=t("div",{class:"custom-container tip"},[t("p",{class:"custom-container-title"},"Verify the receive address on the hardware wallet for extra security"),t("p",null,[e("It's always a good practice to verify that the receive address on Wasabi corresponds to the one on the hardware wallet, before receiving (large amounts of) bitcoin. This could prevent malicious firmware which replaces a receive address with a fake one. You can do this by clicking on "),t("code",null,"Show on the hardware wallet"),e(" at a receive address. The address will now be displayed on the hardware wallet, check that the addresses correspond and then confirm this on the hardware wallet.")])],-1),T=t("h4",{id:"sending-bitcoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#sending-bitcoin","aria-hidden":"true"},"#"),e(" Sending bitcoin")],-1),B=l('
    1. Click the Send button.
    2. Enter the amount and destination address.
    3. Enter the label of whom you are sending to.
    4. At the Preview Transaction screen, check that everything is correct.
    5. Click Send Now.
    6. Connect the hardware wallet & unlock it.
    7. Check on the hardware wallet that everything is correct.
    8. Confirm on the hardware wallet.
    9. The transaction is sent!
    The private keys are not on the computer, thus the transaction is signed on the hardware wallet after you confirm with a physical button click. The final transaction is automatically broadcast over Tor with Wasabi Wallet.
     Connecting Coldcard via SD card
    ',3),j={href:"https://coldcard.com/docs/microsd",target:"_blank",rel:"noopener noreferrer"},I=l('
     Import the skeleton wallet
    Power your Coldcard on a power bank or electricity socket, then unlock it with your pin. Put in a MicroSD card and go to Advanced > MicroSD Card > Export Wallet > Wasabi Wallet. This will write the public keys, wallet fingerprint, derivation path and other metadata to a skeleton file new-wallet.json.
    Protect your public keys!
    This file does not include your private keys, so an attacker cannot use it to spend your bitcoin. However, he can use it to derive a full transaction history, thus it is a potential privacy leak.
    Now insert the SD card to your computer, and open Wasabi Wallet. Go to the Add Wallet dialog, and click Import a wallet, browse to the SD card and select the new-wallet.json file. Wasabi will automatically import and modify this skeleton file and store it in your Wallets and WalletBackups folders.
     Receiving bitcoin
    ',5),P=t("code",null,"NavBar",-1),A=l('
     Sending bitcoin
    Sending bitcoin airgapped works as follows:
    1. Enable PSBT workflow in the Wallet Settings
    2. Click the Send button.
    3. Enter the amount and destination address.
    4. Enter the label of whom you are sending to.
    5. At the Preview Transaction screen, check that everything is correct.
    6. Click Save PSBT file, and save the file on the MicroSD card.
    7. Remove the MicroSD card from the computer and put it into your Coldcard.
    8. On the Coldcard, click Ready to Sign.
    9. Verify the transaction details shown on the Coldcard, and approve to sign the transaction.
    10. Remove the MicroSD card from Coldcard and insert it into the computer.
    11. In Wasabi, click on Broadcaster (in the search bar).
    12. Select Import Transaction.
    13. Select the final signed transaction, which looks like this xxx-final.txn.
    14. Broadcast the transaction.
    Enable PSBT workflow in the settings
    You need to have PSBT workflow enabled in the wallet settings in order to have Save PSBT file show up at the Preview Transaction screen. After it is enabled, a Broadcast button will appear next to the Send button for an easier workflow.
     Cold-Wasabi protocol
    This is how you can safely eat cold Wasabi, or store your coins on a hardware wallet after coinjoining with Wasabi Wallet. Because you cannot do coinjoin with the private keys on the hardware wallet, you will need to generate and load two different wallets in Wasabi. A 'hot' (coinjoin) and a 'cold' (storage) wallet will both be running in parallel, label them accordingly so you don't mix them up.
     GUI tutorial
     Coinjoin on the hot Wasabi
    First
    You should make your existing coins private. It is useful to generate a complete new hot wallet for this, so as to keep the coinjoin transaction history separate from other wallets.
    ',9),N=t("li",null,"Send bitcoin into this Hot-Wasabi Wallet.",-1),R=l('
     Set up your cold-Wasabi
    Second
    In order to separate these new private coins, you should generate a fresh wallet on your hardware device.
    1. Generate a new set of keys on your hardware wallet and make a backup.
    2. Load your hardware wallet device to Wasabi, either via USB or SD card.
    3. Label and generate a receive address for the hardware wallet. For the first setup, you need to connect the hardware wallet to the computer that runs Wasabi, afterwards, you can generate receive addresses without the device being connected.
    4. Copy the receiving address from the cold-Wasabi.
     Send bitcoins from hot to cold Wasabi
    Third
    When your coins are private, it is a good practice to send them out in multiple batches in order to not consolidate all your coins. Wait some time in-between sending them, so that timing analysis becomes more difficult.
    1. Go to the hot-Wasabi Send dialog and enter the amount.
    2. Paste the cold-Wasabi address.
     Send bitcoins from cold Wasabi
    Finally
    You can at any time spend the bitcoin from the cold-Wasabi.
    1. Connect your hardware wallet to the computer.
    2. Load the cold Wasabi wallet.
    3. Go to the Send dialog, enter the amount and the destination address, then sign the transaction with the hardware wallet.
    Success!
    おめでとうございます!
    You are now eating Cold Wasabi!
    WARNING
    The anonymity score is tied to the wallet that you used to coinjoin, if you send a mixed coin to another Wasabi Wallet (in this case your hardware wallet), it will have an anonymity score of 1 (and will be marked as non-private) because this wallet doesn't know that the coin was coinjoined.
    You should use a meaningful label when you generate a receive address in your hardware wallet, e.g. "Myself coinjoin private" (something that reminds you that you got this utxo from your Wasabi Wallet and it was coinjoined).
    ',11);function U(D,G){const i=s("router-link"),n=s("RouterLink"),r=s("ExternalLinkIcon");return c(),h("div",null,[w,t("nav",p,[t("ul",null,[t("li",null,[a(i,{to:"#using-hardware-wallet-step-by-step"},{default:o(()=>[e("Using hardware wallet step-by-step")]),_:1})]),t("li",null,[a(i,{to:"#what-is-cold-storage"},{default:o(()=>[e("What is Cold Storage")]),_:1})]),t("li",null,[a(i,{to:"#hardware-wallet-with-wasabi"},{default:o(()=>[e("Hardware Wallet with Wasabi")]),_:1}),t("ul",null,[t("li",null,[a(i,{to:"#connecting-via-usb"},{default:o(()=>[e("Connecting via USB")]),_:1})]),t("li",null,[a(i,{to:"#connecting-coldcard-via-sd-card"},{default:o(()=>[e("Connecting Coldcard via SD card")]),_:1})])])]),t("li",null,[a(i,{to:"#cold-wasabi-protocol"},{default:o(()=>[e("Cold-Wasabi protocol")]),_:1})]),t("li",null,[a(i,{to:"#gui-tutorial"},{default:o(()=>[e("GUI tutorial")]),_:1}),t("ul",null,[t("li",null,[a(i,{to:"#coinjoin-on-the-hot-wasabi"},{default:o(()=>[e("Coinjoin on the hot Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#set-up-your-cold-wasabi"},{default:o(()=>[e("Set up your cold-Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#send-bitcoins-from-hot-to-cold-wasabi"},{default:o(()=>[e("Send bitcoins from hot to cold Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#send-bitcoins-from-cold-wasabi"},{default:o(()=>[e("Send bitcoins from cold Wasabi")]),_:1})])])])])]),b,t("ol",null,[m,t("li",null,[e("Now you can "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive")]),_:1}),e(" bitcoin to addresses controlled by the hardware wallet.")]),t("li",null,[e("You can "),a(n,{to:"/using-wasabi/Send.html"},{default:o(()=>[e("spend")]),_:1}),e(" these coins in the "),f,e(" dialog, though the hardware wallet must be connected via USB to sign the transaction. Alternatively, you can "),a(n,{to:"/using-wasabi/ColdWasabi.html#connecting-coldcard-via-sd-card"},{default:o(()=>[e("build a PSBT")]),_:1}),e(", export this via SD card to your Coldcard wallet for signing, then import the final transaction to Wasabi for broadcasting.")])]),t("div",g,[y,t("p",null,[e("Unfortunately, as of now, you cannot "),a(n,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("coinjoin")]),_:1}),e(" with just the private keys on your hardware wallet. The keys need to be on the internet-connected computer to be able to coinjoin.")])]),v,t("p",null,[e("You can use Wasabi Wallet with almost any hardware wallet out there because Wasabi utilizes "),t("a",_,[e("Bitcoin Core Hardware Wallet Interface [HWI]"),a(r)]),e(". The setup is thoroughly tested for "),t("a",k,[e("Trezor model T"),a(r)]),e(", "),t("a",W,[e("Ledger Nano S, Nano S Plus and Nano X"),a(r)]),e(", and "),t("a",S,[e("Coldcard"),a(r)]),e(".")]),C,t("p",null,[e("After the first time you loaded a new device, the public keys will be stored locally on the computer, and you can use Wasabi to "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive bitcoin")]),_:1}),e(" to the hardware wallet without having it connected.")]),x,T,t("p",null,[e("Only when you want to "),a(n,{to:"/using-wasabi/Send.html"},{default:o(()=>[e("send bitcoin")]),_:1}),e(" you need to connect the device over USB again.")]),B,t("p",null,[e("You can use Wasabi Wallet together with Coldcard without ever connecting it via USB, thus further reducing possible attack vectors. For more details see the "),t("a",j,[e("Coldcard documentation"),a(r)]),e(".")]),I,t("p",null,[e("After the skeleton wallet is imported, you can open the wallet from the wallet list at the "),P,e(", without having to power on the Coldcard. Generate a "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive address")]),_:1}),e(" as usual. The private key corresponding to this address is on the hardware wallet.")]),A,t("ol",null,[t("li",null,[a(n,{to:"/using-wasabi/WalletGeneration.html"},{default:o(()=>[e("Generate a new hot-Wasabi Wallet")]),_:1}),e(".")]),t("li",null,[e("Open the "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("Receive")]),_:1}),e(" dialog to get a new address.")]),N,t("li",null,[e("Start the automatic "),a(n,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("coinjoin")]),_:1}),e(" process and wait for the coinjoin to be done (i.e. privacy progress 100%).")])]),R])}const Y=d(u,[["render",U],["__file","ColdWasabi.html.vue"]]);export{Y as default};
+import{_ as d,r as s,o as c,c as h,a as t,d as a,w as o,b as e,e as l}from"./app.65e5b6fd.js";const u={},w=t("h1",{id:"cold-wasabi-hardware-wallet-mode",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#cold-wasabi-hardware-wallet-mode","aria-hidden":"true"},"#"),e(" Cold-Wasabi Hardware Wallet Mode")],-1),p={class:"table-of-contents"},b=t("h2",{id:"using-hardware-wallet-step-by-step",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#using-hardware-wallet-step-by-step","aria-hidden":"true"},"#"),e(" Using hardware wallet step-by-step")],-1),m=l("
  • Start your Wasabi Wallet and go to Add Wallet.
  • Click on Connect to hardware wallet and then connect the hardware wallet via cable. Alternatively, you can import a Coldcard skeleton file via SD card by using Import Wallet at the Add Wallet dialog.
  • Confirm that the detected hardware wallet is correct.
  • Click Open, and wait for the wallet to load.
    • ",4),f=t("code",null,"Send",-1),g={class:"custom-container warning"},y=t("p",{class:"custom-container-title"},"No coinjoin",-1),v=l('
     What is Cold Storage
    Cold storage refers to generating and storing private keys completely offline. This is an often-used security precaution, especially dealing with large amounts of bitcoin. Because the private keys are not on a computer that is connected to the internet, many remote attack vectors are nullified.
    Methods of cold storage include keeping private keys on a:
    • USB drive or other data storage medium
    • Paper wallet
    • Bearer item such as a physical bitcoin
    • Hardware wallet
    Use a hardware wallet for cold storage
    There are multiple ways to exercise cold storage, however it is highly reccommended to use a hardware wallet. This is by far the best and most secure way of using bitcoin for almost all users.
     Hardware Wallet with Wasabi
    ',6),_={href:"https://github.com/bitcoin-core/hwi",target:"_blank",rel:"noopener noreferrer"},k={href:"https://trezor.io",target:"_blank",rel:"noopener noreferrer"},W={href:"https://ledger.com",target:"_blank",rel:"noopener noreferrer"},S={href:"https://coldcard.com",target:"_blank",rel:"noopener noreferrer"},C=l('
     Connecting via USB
     Import the wallet
    1. Go to Add wallet.
    2. Click on Connect to hardware wallet.
    3. Give the wallet a name.
    4. Connect the hardware wallet to the PC and enter the pin on the hardware wallet to unlock it.
    5. Confirm that the correct hardware wallet is detected.
    6. Open the wallet.
    This wallet can be used as a watch-only wallet when the hardware wallet device is not connected.
    Wasabi remembers the wallet's information like xpub, wallet fingerprint and addresses etc. But it never knows the private keys, which are on the hardware wallet. So, you can see the balance and all it's transactions in Wasabi and you can generate addresses, but you cannot send without the hardware wallet being connected. Because you need to sign (confirm) the outgoing transactions on the hardware wallet.
     Receiving bitcoin
    ',5),x=t("div",{class:"custom-container tip"},[t("p",{class:"custom-container-title"},"Verify the receive address on the hardware wallet for extra security"),t("p",null,[e("It's always a good practice to verify that the receive address on Wasabi corresponds to the one on the hardware wallet, before receiving (large amounts of) bitcoin. This could prevent malicious firmware which replaces a receive address with a fake one. You can do this by clicking on "),t("code",null,"Show on the hardware wallet"),e(" at a receive address. The address will now be displayed on the hardware wallet, check that the addresses correspond and then confirm this on the hardware wallet.")])],-1),T=t("h4",{id:"sending-bitcoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#sending-bitcoin","aria-hidden":"true"},"#"),e(" Sending bitcoin")],-1),B=l('
    1. Click the Send button.
    2. Enter the amount and destination address.
    3. Enter the label of whom you are sending to.
    4. At the Preview Transaction screen, check that everything is correct.
    5. Click Send Now.
    6. Connect the hardware wallet & unlock it.
    7. Check on the hardware wallet that everything is correct.
    8. Confirm on the hardware wallet.
    9. The transaction is sent!
    The private keys are not on the computer, thus the transaction is signed on the hardware wallet after you confirm with a physical button click. The final transaction is automatically broadcast over Tor with Wasabi Wallet.
     Connecting Coldcard via SD card
    ',3),j={href:"https://coldcard.com/docs/microsd",target:"_blank",rel:"noopener noreferrer"},I=l('
     Import the skeleton wallet
    Power your Coldcard on a power bank or electricity socket, then unlock it with your pin. Put in a MicroSD card and go to Advanced > MicroSD Card > Export Wallet > Wasabi Wallet. This will write the public keys, wallet fingerprint, derivation path and other metadata to a skeleton file new-wallet.json.
    Protect your public keys!
    This file does not include your private keys, so an attacker cannot use it to spend your bitcoin. However, he can use it to derive a full transaction history, thus it is a potential privacy leak.
    Now insert the SD card to your computer, and open Wasabi Wallet. Go to the Add Wallet dialog, and click Import a wallet, browse to the SD card and select the new-wallet.json file. Wasabi will automatically import and modify this skeleton file and store it in your Wallets and WalletBackups folders.
     Receiving bitcoin
    ',5),P=t("code",null,"NavBar",-1),A=l('
     Sending bitcoin
    Sending bitcoin airgapped works as follows:
    1. Enable PSBT workflow in the Wallet Settings
    2. Click the Send button.
    3. Enter the amount and destination address.
    4. Enter the label of whom you are sending to.
    5. At the Preview Transaction screen, check that everything is correct.
    6. Click Save PSBT file, and save the file on the MicroSD card.
    7. Remove the MicroSD card from the computer and put it into your Coldcard.
    8. On the Coldcard, click Ready to Sign.
    9. Verify the transaction details shown on the Coldcard, and approve to sign the transaction.
    10. Remove the MicroSD card from Coldcard and insert it into the computer.
    11. In Wasabi, click on Broadcaster (in the search bar).
    12. Select Import Transaction.
    13. Select the final signed transaction, which looks like this xxx-final.txn.
    14. Broadcast the transaction.
    Enable PSBT workflow in the settings
    You need to have PSBT workflow enabled in the wallet settings in order to have Save PSBT file show up at the Preview Transaction screen. After it is enabled, a Broadcast button will appear next to the Send button for an easier workflow.
     Cold-Wasabi protocol
    This is how you can safely eat cold Wasabi, or store your coins on a hardware wallet after coinjoining with Wasabi Wallet. Because you cannot do coinjoin with the private keys on the hardware wallet, you will need to generate and load two different wallets in Wasabi. A 'hot' (coinjoin) and a 'cold' (storage) wallet will both be running in parallel, label them accordingly so you don't mix them up.
     GUI tutorial
     Coinjoin on the hot Wasabi
    First
    You should make your existing coins private. It is useful to generate a complete new hot wallet for this, so as to keep the coinjoin transaction history separate from other wallets.
    ',9),N=t("li",null,"Send bitcoin into this Hot-Wasabi Wallet.",-1),R=l('
     Set up your cold-Wasabi
    Second
    In order to separate these new private coins, you should generate a fresh wallet on your hardware device.
    1. Generate a new set of keys on your hardware wallet and make a backup.
    2. Load your hardware wallet device to Wasabi, either via USB or SD card.
    3. Label and generate a receive address for the hardware wallet. For the first setup, you need to connect the hardware wallet to the computer that runs Wasabi, afterwards, you can generate receive addresses without the device being connected.
    4. Copy the receiving address from the cold-Wasabi.
     Send bitcoins from hot to cold Wasabi
    Third
    When your coins are private, it is a good practice to send them out in multiple batches in order to not consolidate all your coins. Wait some time in-between sending them, so that timing analysis becomes more difficult.
    1. Go to the hot-Wasabi Send dialog and enter the amount.
    2. Paste the cold-Wasabi address.
     Send bitcoins from cold Wasabi
    Finally
    You can at any time spend the bitcoin from the cold-Wasabi.
    1. Connect your hardware wallet to the computer.
    2. Load the cold Wasabi wallet.
    3. Go to the Send dialog, enter the amount and the destination address, then sign the transaction with the hardware wallet.
    Success!
    おめでとうございます!
    You are now eating Cold Wasabi!
    WARNING
    The anonymity score is tied to the wallet that you used to coinjoin, if you send a mixed coin to another Wasabi Wallet (in this case your hardware wallet), it will have an anonymity score of 1 (and will be marked as non-private) because this wallet doesn't know that the coin was coinjoined.
    You should use a meaningful label when you generate a receive address in your hardware wallet, e.g. "Myself coinjoin private" (something that reminds you that you got this utxo from your Wasabi Wallet and it was coinjoined).
    ',11);function U(D,G){const i=s("router-link"),n=s("RouterLink"),r=s("ExternalLinkIcon");return c(),h("div",null,[w,t("nav",p,[t("ul",null,[t("li",null,[a(i,{to:"#using-hardware-wallet-step-by-step"},{default:o(()=>[e("Using hardware wallet step-by-step")]),_:1})]),t("li",null,[a(i,{to:"#what-is-cold-storage"},{default:o(()=>[e("What is Cold Storage")]),_:1})]),t("li",null,[a(i,{to:"#hardware-wallet-with-wasabi"},{default:o(()=>[e("Hardware Wallet with Wasabi")]),_:1}),t("ul",null,[t("li",null,[a(i,{to:"#connecting-via-usb"},{default:o(()=>[e("Connecting via USB")]),_:1})]),t("li",null,[a(i,{to:"#connecting-coldcard-via-sd-card"},{default:o(()=>[e("Connecting Coldcard via SD card")]),_:1})])])]),t("li",null,[a(i,{to:"#cold-wasabi-protocol"},{default:o(()=>[e("Cold-Wasabi protocol")]),_:1})]),t("li",null,[a(i,{to:"#gui-tutorial"},{default:o(()=>[e("GUI tutorial")]),_:1}),t("ul",null,[t("li",null,[a(i,{to:"#coinjoin-on-the-hot-wasabi"},{default:o(()=>[e("Coinjoin on the hot Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#set-up-your-cold-wasabi"},{default:o(()=>[e("Set up your cold-Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#send-bitcoins-from-hot-to-cold-wasabi"},{default:o(()=>[e("Send bitcoins from hot to cold Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#send-bitcoins-from-cold-wasabi"},{default:o(()=>[e("Send bitcoins from cold Wasabi")]),_:1})])])])])]),b,t("ol",null,[m,t("li",null,[e("Now you can "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive")]),_:1}),e(" bitcoin to addresses controlled by the hardware wallet.")]),t("li",null,[e("You can "),a(n,{to:"/using-wasabi/Send.html"},{default:o(()=>[e("spend")]),_:1}),e(" these coins in the "),f,e(" dialog, though the hardware wallet must be connected via USB to sign the transaction. Alternatively, you can "),a(n,{to:"/using-wasabi/ColdWasabi.html#connecting-coldcard-via-sd-card"},{default:o(()=>[e("build a PSBT")]),_:1}),e(", export this via SD card to your Coldcard wallet for signing, then import the final transaction to Wasabi for broadcasting.")])]),t("div",g,[y,t("p",null,[e("Unfortunately, as of now, you cannot "),a(n,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("coinjoin")]),_:1}),e(" with just the private keys on your hardware wallet. The keys need to be on the internet-connected computer to be able to coinjoin.")])]),v,t("p",null,[e("You can use Wasabi Wallet with almost any hardware wallet out there because Wasabi utilizes "),t("a",_,[e("Bitcoin Core Hardware Wallet Interface [HWI]"),a(r)]),e(". The setup is thoroughly tested for "),t("a",k,[e("Trezor model T"),a(r)]),e(", "),t("a",W,[e("Ledger Nano S, Nano S Plus and Nano X"),a(r)]),e(", and "),t("a",S,[e("Coldcard"),a(r)]),e(".")]),C,t("p",null,[e("After the first time you loaded a new device, the public keys will be stored locally on the computer, and you can use Wasabi to "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive bitcoin")]),_:1}),e(" to the hardware wallet without having it connected.")]),x,T,t("p",null,[e("Only when you want to "),a(n,{to:"/using-wasabi/Send.html"},{default:o(()=>[e("send bitcoin")]),_:1}),e(" you need to connect the device over USB again.")]),B,t("p",null,[e("You can use Wasabi Wallet together with Coldcard without ever connecting it via USB, thus further reducing possible attack vectors. For more details see the "),t("a",j,[e("Coldcard documentation"),a(r)]),e(".")]),I,t("p",null,[e("After the skeleton wallet is imported, you can open the wallet from the wallet list at the "),P,e(", without having to power on the Coldcard. Generate a "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive address")]),_:1}),e(" as usual. The private key corresponding to this address is on the hardware wallet.")]),A,t("ol",null,[t("li",null,[a(n,{to:"/using-wasabi/WalletGeneration.html"},{default:o(()=>[e("Generate a new hot-Wasabi Wallet")]),_:1}),e(".")]),t("li",null,[e("Open the "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("Receive")]),_:1}),e(" dialog to get a new address.")]),N,t("li",null,[e("Start the automatic "),a(n,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("coinjoin")]),_:1}),e(" process and wait for the coinjoin to be done (i.e. privacy progress 100%).")])]),R])}const Y=d(u,[["render",U],["__file","ColdWasabi.html.vue"]]);export{Y as default};
diff --git a/assets/ContributionChecklist.html.d5d11b35.js b/assets/ContributionChecklist.html.4f884c6d.js
similarity index 99%
rename from assets/ContributionChecklist.html.d5d11b35.js
rename to assets/ContributionChecklist.html.4f884c6d.js
index 29d611b983..78b65e0ad2 100644
--- a/assets/ContributionChecklist.html.d5d11b35.js
+++ b/assets/ContributionChecklist.html.4f884c6d.js
@@ -1 +1 @@
-import{_ as l,r,o as c,c as u,a as e,d as o,w as a,b as t,e as h}from"./app.a5b7c2b2.js";const d={},b=e("h1",{id:"contribution-checklist",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#contribution-checklist","aria-hidden":"true"},"#"),t(" Contribution Checklist")],-1),w=e("p",null,"So you're interested in contributing to Wasabi - welcome!",-1),p=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Embrace the open-source crypto-anarchy!"),e("p",null,"No one is here to tell you what to do, and it is not required to work on an existing issue to contribute to Wasabi. Contributors are free to work on their own forked versions on whatever they want, however they wish and without any permission from anyone. With that being said, in order to maximize the usefulness/impact of your work, it's a good idea to consult with other Wasabikas via Slack, GitHub, or other communication channels before setting out on any serious contribution effort.")],-1),m=e("p",null,"This checklist will get you plugged in and productive as quickly as possible.",-1),g={class:"table-of-contents"},_=h('
     Who is a contributor?
    A contributor is any individual who works to improve and add value to Wasabi and its users.
    You can become a Wasabika!
    Wasabi Wallet is free and open-source software, but contributing is not just about writing code. This means anything from fixing typos in documentation, answering questions of fellow Wasabikas, creating videos, podcasts and memes, implementing new Wasabi features and everything in-between. All such contributions are very welcomed and greatly appreciated.
     Say hello and get started
    ',4),f={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/zkSnacks/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},y=e("li",null,"Introduce yourself, say a bit about your skills and interests. This will help others point you in the right direction.",-1),v=e("li",null,"Explore the communication channels and find out what the peers are tinkering on, learn about the project and who is contributing in what way. This will help you to find the interesting challenges you can work on.",-1),W=e("li",null,"Wasabi Research Club is a weekly online call, focused mainly on Bitcoin privacy. Everyone is welcome to join the discussions. However, being familiar with the topic (if there is any) is recommended.",-1),T={href:"https://www.youtube.com/c/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},z={href:"https://github.com/zkSNACKs/WasabiResearchClub/",target:"_blank",rel:"noopener noreferrer"},x=e("h2",{id:"learn-how-wasabikas-work",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#learn-how-wasabikas-work","aria-hidden":"true"},"#"),t(" Learn how Wasabikas work")],-1),C={href:"https://eprint.iacr.org/2021/206",target:"_blank",rel:"noopener noreferrer"},N={href:"https://rfc.zeromq.org/spec/42/",target:"_blank",rel:"noopener noreferrer"},M=e("p",null,"It’s a simple set of collaboration rules based on GitHub’s fork and pull request model, and a foundational part of how we work together.",-1),Y=e("h2",{id:"what-to-work-on",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-to-work-on","aria-hidden":"true"},"#"),t(" What to work on")],-1),A=e("p",null,"Education and development are vitally important aspects of Bitcoin privacy and Wasabi Wallet specifically.",-1),Q={href:"https://www.freehaven.net/anonbib/cache/usability:weis2006.pdf",target:"_blank",rel:"noopener noreferrer"},S={href:"https://en.wikipedia.org/wiki/Network_effect",target:"_blank",rel:"noopener noreferrer"},j=e("h3",{id:"education-contributor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#education-contributor","aria-hidden":"true"},"#"),t(" Education Contributor")],-1),E=e("ol",null,[e("li",null,[e("strong",null,"Videos, podcasts, memes and articles"),t(" are great ways of sharing information to your peers. You can create wallet tutorials, record insightful discussions, write articles or make memes about Wasabi and privacy.")]),e("li",null,[e("strong",null,"Organizing events and doing presentations"),t(" about Wasabi Wallet and Bitcoin privacy. Connecting like-minded individuals, who want to take control of their own financial privacy and teaching them about the awesome tools that are available, can be life changing.")]),e("li",null,[e("strong",null,"Helping and teaching new users"),t(", once you are familiar with the software, is something that can't be underestimated. You can do this in any social media like Twitter, Telegram, Reddit etc or in your own neighborhood.")])],-1),q={class:"custom-container tip"},I=e("p",{class:"custom-container-title"},"[zkSNACKs Ltd.](https://zksnacks.com/) is known for compensating educators who consistently help out new users or create good content.",-1),O={href:"https://blog.wasabiwallet.io/coming-soon-contribution-games/",target:"_blank",rel:"noopener noreferrer"},R={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},B=e("h3",{id:"github-contributor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#github-contributor","aria-hidden":"true"},"#"),t(" GitHub Contributor")],-1),L=e("strong",null,"Find a problem somewhere in Wasabi-land",-1),H={href:"https://github.com/zksnacks/walletwasabi/issues",target:"_blank",rel:"noopener noreferrer"},Z=e("strong",null,"Do work to fix that problem.",-1),D={href:"https://github.com/zkSNACKs/WalletWasabi/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},G={href:"https://github.com/zkSNACKs/WasabiDoc/pulls",target:"_blank",rel:"noopener noreferrer"},F={href:"https://github.com/zksnacks/walletwasabi/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},V=e("li",null,[e("strong",null,"Request that others review your work."),t(" The best way to do this is by writing good commit comments and pull request/issue descriptions that clearly explain the problem your work is intended to solve, why it’s important, and why you fixed it the way you did. Make it as easy as possible for others to review your work. Make it a "),e("em",null,"pleasure"),t(" for others to review your work.")],-1),K=e("li",null,[e("strong",null,"Incorporate review feedback"),t(" you get until your fix gets merged or is otherwise accepted.")],-1),J=e("li",null,"Repeat steps 1–4.",-1),U=e("p",null,[t("Remember: "),e("em",null,"every contributor"),t(" is free to work on what they want, including maintainers who may or may not want to review and merge your pull request if they don't have any prior context for it, or reason to believe it's worth spending their time on.")],-1),X=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Reviews are for everybody!"),e("p",null,"If you want to be really popular around here, don’t just submit your own work, but also spend time reviewing the work of others.")],-1);function P($,ee){const i=r("router-link"),n=r("ExternalLinkIcon"),s=r("RouterLink");return c(),u("div",null,[b,w,p,m,e("nav",g,[e("ul",null,[e("li",null,[o(i,{to:"#who-is-a-contributor"},{default:a(()=>[t("Who is a contributor?")]),_:1})]),e("li",null,[o(i,{to:"#say-hello-and-get-started"},{default:a(()=>[t("Say hello and get started")]),_:1})]),e("li",null,[o(i,{to:"#learn-how-wasabikas-work"},{default:a(()=>[t("Learn how Wasabikas work")]),_:1})]),e("li",null,[o(i,{to:"#what-to-work-on"},{default:a(()=>[t("What to work on")]),_:1}),e("ul",null,[e("li",null,[o(i,{to:"#education-contributor"},{default:a(()=>[t("Education Contributor")]),_:1})]),e("li",null,[o(i,{to:"#github-contributor"},{default:a(()=>[t("GitHub Contributor")]),_:1})])])])])]),_,e("ul",null,[e("li",null,[t("Join our "),e("a",f,[t("Slack"),o(n)]),t(" and especially check out our "),e("a",k,[t("GitHub repository"),o(n)]),t(".")]),y,v,W]),e("p",null,[t("Discussions might be recorded and published on the Wasabi Wallet "),e("a",T,[t("YouTube channel"),o(n)]),t(".")]),e("p",null,[t("You can find the schedule, call link, past recordings and more at the "),e("a",z,[t("Wasabi Research Club repository"),o(n)]),t(".")]),x,e("ul",null,[e("li",null,[t("Educate yourself about the software by reading through "),o(s,{to:"/using-wasabi/"},{default:a(()=>[t("Using Wasabi")]),_:1}),t(".")]),e("li",null,[t("To understand how Wasabi CoinJoins work, read "),e("a",C,[t("WabiSabi Framework"),o(n)]),t(".")]),e("li",null,[t("Familiarize yourself with "),e("a",N,[t("C4: The Collective Code Construction Contract"),o(n)]),t(".")])]),M,Y,A,e("p",null,[t("The more Wasabi users there are, the better their privacy, because "),e("a",Q,[t("anonymity loves company"),o(n)]),t(".")]),e("p",null,[t("The better UX and privacy Wasabi provides, the more there will be users, because of "),e("a",S,[t("network effect"),o(n)]),t(".")]),j,E,e("div",q,[I,e("p",null,[t("The company is actively sponsoring Bitcoin events and organizing "),e("a",O,[t("Contribution Games"),o(n)]),t(". In case you have been contributing already, feel free to let other Wasabikas know by sending us a link to your content in "),e("a",R,[t("Slack"),o(n)]),t(".")])]),B,e("ol",null,[e("li",null,[L,t(" that (a) needs fixing or improvement and (b) is a match for your skills and interests. Browse "),e("a",H,[t("open issues"),o(n)]),t(" and ask around about what other contributors think needs fixing. Because while you don’t need anybody’s permission and you can work on whatever you want, you’ll want to know up front whether anybody else is going to care about the work you do.")]),e("li",null,[Z,t(" Submit your fix for review with a pull request (for "),e("a",D,[t("code"),o(n)]),t(" and "),e("a",G,[t("documentation"),o(n)]),t(" changes) or with a GitHub "),e("a",F,[t("issue"),o(n)]),t(" (for everything else).")]),V,K,J]),U,X])}const oe=l(d,[["render",P],["__file","ContributionChecklist.html.vue"]]);export{oe as default};
+import{_ as l,r,o as c,c as u,a as e,d as o,w as a,b as t,e as h}from"./app.65e5b6fd.js";const d={},b=e("h1",{id:"contribution-checklist",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#contribution-checklist","aria-hidden":"true"},"#"),t(" Contribution Checklist")],-1),w=e("p",null,"So you're interested in contributing to Wasabi - welcome!",-1),p=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Embrace the open-source crypto-anarchy!"),e("p",null,"No one is here to tell you what to do, and it is not required to work on an existing issue to contribute to Wasabi. Contributors are free to work on their own forked versions on whatever they want, however they wish and without any permission from anyone. With that being said, in order to maximize the usefulness/impact of your work, it's a good idea to consult with other Wasabikas via Slack, GitHub, or other communication channels before setting out on any serious contribution effort.")],-1),m=e("p",null,"This checklist will get you plugged in and productive as quickly as possible.",-1),g={class:"table-of-contents"},_=h('
     Who is a contributor?
    A contributor is any individual who works to improve and add value to Wasabi and its users.
    You can become a Wasabika!
    Wasabi Wallet is free and open-source software, but contributing is not just about writing code. This means anything from fixing typos in documentation, answering questions of fellow Wasabikas, creating videos, podcasts and memes, implementing new Wasabi features and everything in-between. All such contributions are very welcomed and greatly appreciated.
     Say hello and get started
    ',4),f={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/zkSnacks/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},y=e("li",null,"Introduce yourself, say a bit about your skills and interests. This will help others point you in the right direction.",-1),v=e("li",null,"Explore the communication channels and find out what the peers are tinkering on, learn about the project and who is contributing in what way. This will help you to find the interesting challenges you can work on.",-1),W=e("li",null,"Wasabi Research Club is a weekly online call, focused mainly on Bitcoin privacy. Everyone is welcome to join the discussions. However, being familiar with the topic (if there is any) is recommended.",-1),T={href:"https://www.youtube.com/c/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},z={href:"https://github.com/zkSNACKs/WasabiResearchClub/",target:"_blank",rel:"noopener noreferrer"},x=e("h2",{id:"learn-how-wasabikas-work",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#learn-how-wasabikas-work","aria-hidden":"true"},"#"),t(" Learn how Wasabikas work")],-1),C={href:"https://eprint.iacr.org/2021/206",target:"_blank",rel:"noopener noreferrer"},N={href:"https://rfc.zeromq.org/spec/42/",target:"_blank",rel:"noopener noreferrer"},M=e("p",null,"It’s a simple set of collaboration rules based on GitHub’s fork and pull request model, and a foundational part of how we work together.",-1),Y=e("h2",{id:"what-to-work-on",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-to-work-on","aria-hidden":"true"},"#"),t(" What to work on")],-1),A=e("p",null,"Education and development are vitally important aspects of Bitcoin privacy and Wasabi Wallet specifically.",-1),Q={href:"https://www.freehaven.net/anonbib/cache/usability:weis2006.pdf",target:"_blank",rel:"noopener noreferrer"},S={href:"https://en.wikipedia.org/wiki/Network_effect",target:"_blank",rel:"noopener noreferrer"},j=e("h3",{id:"education-contributor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#education-contributor","aria-hidden":"true"},"#"),t(" Education Contributor")],-1),E=e("ol",null,[e("li",null,[e("strong",null,"Videos, podcasts, memes and articles"),t(" are great ways of sharing information to your peers. You can create wallet tutorials, record insightful discussions, write articles or make memes about Wasabi and privacy.")]),e("li",null,[e("strong",null,"Organizing events and doing presentations"),t(" about Wasabi Wallet and Bitcoin privacy. Connecting like-minded individuals, who want to take control of their own financial privacy and teaching them about the awesome tools that are available, can be life changing.")]),e("li",null,[e("strong",null,"Helping and teaching new users"),t(", once you are familiar with the software, is something that can't be underestimated. You can do this in any social media like Twitter, Telegram, Reddit etc or in your own neighborhood.")])],-1),q={class:"custom-container tip"},I=e("p",{class:"custom-container-title"},"[zkSNACKs Ltd.](https://zksnacks.com/) is known for compensating educators who consistently help out new users or create good content.",-1),O={href:"https://blog.wasabiwallet.io/coming-soon-contribution-games/",target:"_blank",rel:"noopener noreferrer"},R={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},B=e("h3",{id:"github-contributor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#github-contributor","aria-hidden":"true"},"#"),t(" GitHub Contributor")],-1),L=e("strong",null,"Find a problem somewhere in Wasabi-land",-1),H={href:"https://github.com/zksnacks/walletwasabi/issues",target:"_blank",rel:"noopener noreferrer"},Z=e("strong",null,"Do work to fix that problem.",-1),D={href:"https://github.com/zkSNACKs/WalletWasabi/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},G={href:"https://github.com/zkSNACKs/WasabiDoc/pulls",target:"_blank",rel:"noopener noreferrer"},F={href:"https://github.com/zksnacks/walletwasabi/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},V=e("li",null,[e("strong",null,"Request that others review your work."),t(" The best way to do this is by writing good commit comments and pull request/issue descriptions that clearly explain the problem your work is intended to solve, why it’s important, and why you fixed it the way you did. Make it as easy as possible for others to review your work. Make it a "),e("em",null,"pleasure"),t(" for others to review your work.")],-1),K=e("li",null,[e("strong",null,"Incorporate review feedback"),t(" you get until your fix gets merged or is otherwise accepted.")],-1),J=e("li",null,"Repeat steps 1–4.",-1),U=e("p",null,[t("Remember: "),e("em",null,"every contributor"),t(" is free to work on what they want, including maintainers who may or may not want to review and merge your pull request if they don't have any prior context for it, or reason to believe it's worth spending their time on.")],-1),X=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Reviews are for everybody!"),e("p",null,"If you want to be really popular around here, don’t just submit your own work, but also spend time reviewing the work of others.")],-1);function P($,ee){const i=r("router-link"),n=r("ExternalLinkIcon"),s=r("RouterLink");return c(),u("div",null,[b,w,p,m,e("nav",g,[e("ul",null,[e("li",null,[o(i,{to:"#who-is-a-contributor"},{default:a(()=>[t("Who is a contributor?")]),_:1})]),e("li",null,[o(i,{to:"#say-hello-and-get-started"},{default:a(()=>[t("Say hello and get started")]),_:1})]),e("li",null,[o(i,{to:"#learn-how-wasabikas-work"},{default:a(()=>[t("Learn how Wasabikas work")]),_:1})]),e("li",null,[o(i,{to:"#what-to-work-on"},{default:a(()=>[t("What to work on")]),_:1}),e("ul",null,[e("li",null,[o(i,{to:"#education-contributor"},{default:a(()=>[t("Education Contributor")]),_:1})]),e("li",null,[o(i,{to:"#github-contributor"},{default:a(()=>[t("GitHub Contributor")]),_:1})])])])])]),_,e("ul",null,[e("li",null,[t("Join our "),e("a",f,[t("Slack"),o(n)]),t(" and especially check out our "),e("a",k,[t("GitHub repository"),o(n)]),t(".")]),y,v,W]),e("p",null,[t("Discussions might be recorded and published on the Wasabi Wallet "),e("a",T,[t("YouTube channel"),o(n)]),t(".")]),e("p",null,[t("You can find the schedule, call link, past recordings and more at the "),e("a",z,[t("Wasabi Research Club repository"),o(n)]),t(".")]),x,e("ul",null,[e("li",null,[t("Educate yourself about the software by reading through "),o(s,{to:"/using-wasabi/"},{default:a(()=>[t("Using Wasabi")]),_:1}),t(".")]),e("li",null,[t("To understand how Wasabi CoinJoins work, read "),e("a",C,[t("WabiSabi Framework"),o(n)]),t(".")]),e("li",null,[t("Familiarize yourself with "),e("a",N,[t("C4: The Collective Code Construction Contract"),o(n)]),t(".")])]),M,Y,A,e("p",null,[t("The more Wasabi users there are, the better their privacy, because "),e("a",Q,[t("anonymity loves company"),o(n)]),t(".")]),e("p",null,[t("The better UX and privacy Wasabi provides, the more there will be users, because of "),e("a",S,[t("network effect"),o(n)]),t(".")]),j,E,e("div",q,[I,e("p",null,[t("The company is actively sponsoring Bitcoin events and organizing "),e("a",O,[t("Contribution Games"),o(n)]),t(". In case you have been contributing already, feel free to let other Wasabikas know by sending us a link to your content in "),e("a",R,[t("Slack"),o(n)]),t(".")])]),B,e("ol",null,[e("li",null,[L,t(" that (a) needs fixing or improvement and (b) is a match for your skills and interests. Browse "),e("a",H,[t("open issues"),o(n)]),t(" and ask around about what other contributors think needs fixing. Because while you don’t need anybody’s permission and you can work on whatever you want, you’ll want to know up front whether anybody else is going to care about the work you do.")]),e("li",null,[Z,t(" Submit your fix for review with a pull request (for "),e("a",D,[t("code"),o(n)]),t(" and "),e("a",G,[t("documentation"),o(n)]),t(" changes) or with a GitHub "),e("a",F,[t("issue"),o(n)]),t(" (for everything else).")]),V,K,J]),U,X])}const oe=l(d,[["render",P],["__file","ContributionChecklist.html.vue"]]);export{oe as default};
diff --git a/assets/Daemon.html.7884d930.js b/assets/Daemon.html.463c6cd1.js
similarity index 99%
rename from assets/Daemon.html.7884d930.js
rename to assets/Daemon.html.463c6cd1.js
index ffdd7cb907..ae8db65286 100644
--- a/assets/Daemon.html.7884d930.js
+++ b/assets/Daemon.html.463c6cd1.js
@@ -1,4 +1,4 @@
-import{_ as d,r as s,o as l,c as u,a as t,d as a,w as n,b as e,e as c}from"./app.a5b7c2b2.js";const p={},h=t("h1",{id:"headless-wasabi-daemon",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#headless-wasabi-daemon","aria-hidden":"true"},"#"),e(" Headless Wasabi Daemon")],-1),b={class:"table-of-contents"},m=t("h2",{id:"introduction",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),e(" Introduction")],-1),q={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},v=c(`
    The desktop app (GUI) is built on top of the daemon. Meaning that command line arguments/variables can also be used to configure the desktop app.
     Available commands
    When entering the commands on the command line, they are capital letter insensitive.
     Config file configurations
    All configuration options available via the Config.json file are also available as command line arguments:
    Config FileCommand LineEnvironment variable
    ""Network": "TestNet"--network=testnetWASABI-NETWORK=testnet
    "MainNetBackendUri": "https://api.wasabiwallet.io/"--mainnetbackenduri="https://api.wasabiwallet.io/"WASABI-MAINNETBACKENDURI="https://api.wasabiwallet.io/"
    "TestNetClearnetBackendUri": "https://api.wasabiwallet.co/"--testnetbackenduri="https://api.wasabiwallet.co/"WASABI-TESTNETBACKENDURI="https://api.wasabiwallet.co/"
    "RegTestBackendUri": "http://localhost:37127/"--regtestbackenduri="http://localhost:37127/"WASABI-REGTESTBACKENDURI="http://localhost:37127/"
    ""UseTor": ""true"--usetor=trueWASABI-USETOR=true
    "TerminateTorOnExit": ""false"--terminatetoronexit=falseWASABI-TERMINATETORONEXIT=false
    "DownloadNewVersion": true--downloadnewversion=trueWASABI-DOWNLOADNEWVERSION=true
    "StartLocalBitcoinCoreOnStartup": false--startlocalbitcoincoreonstartup=falseWASABI-STARTLOCALBITCOINCOREONSTARTUP=false
    "StopLocalBitcoinCoreOnShutdown": true--stoplocalbitcoincoreonshutdown=trueWASABI-STOPLOCALBITCOINCOREONSHUTDOWN=true
    "LocalBitcoinCoreDataDir": "/home/UserName/.bitcoin"--localbitcoincoredatadir="/home/UserName/.bitcoin"WASABI-LOCALBITCOINCOREDATADIR="/home/UserName/.bitcoin"
    "MainNetBitcoinP2pEndPoint": "127.0.0.1:8333"--mainnetbitcoinp2pendpoint="127.0.0.1:8333"WASABI-MAINNETBITCOINP2PENDPOINT="127.0.0.1:8333"
    "TestNetBitcoinP2pEndPoint": "127.0.0.1:18333"--testnetbitcoinp2pendpoint="127.0.0.1:18333"WASABI-TESTNETBITCOINP2PENDPOINT="127.0.0.1:18333"
    "RegTestBitcoinP2pEndPoint": "127.0.0.1:18444"--regtestbitcoinp2pendpoint="127.0.0.1:18444"WASABI-REGTESTBITCOINP2PENDPOINT="127.0.0.1:18444"
    "JsonRpcServerEnabled": "true"--jsonrpcserverenabled=trueWASABI-JSONRPCSERVERENABLED=true
    "JsonRpcUser": ""--jsonrpcuser=""WASABI-JSONRPCUSER=""
    "JsonRpcPassword": ""--jsonrpcpassword=""WASABI-JSONRPCPASSWORD=""
    "JsonRpcServerPrefixes":["http://127.0.0.1:37128/", "http://localhost:37128/"]--jsonrpcserverprefixes=["http://127.0.0.1:37128/", "http://localhost:37128/"]WASABI-JSONRPCSERVERPREFIXES=["http://127.0.0.1:37128/", "http://localhost:37128/"]
    "DustThreshold": "0.00005"--dustthreshold=0.00005WASABI-DUSTTHRESHOLD=0.00005
    "EnableGpu": true--enablegpu=trueWASABI-ENABLEGPU=true
    "CoordinatorIdentifier": "CoinJoinCoordinatorIdentifier"--coordinatoridentifier="coinjoincoordinatoridentifier"WASABI-COORDINATORIDENTIFIER="coinjoincoordinatoridentifier"
     Non-Config file configurations
    There are a few special switches that are not present in the Config.json file and are only available using the command line:
    SwitchCommand LineEnvironment variable
    Ignore P2P transactions--blockonly=trueWASABI-BLOCKONLY=true
    The level of detail used during logging--loglevel=traceWASABI-LOGLEVEL=trace
    The path to the directory used during runtime--datadir="$HOME/temp/wasabi-1"WASABI-DATADIR="$HOME/temp/wasabi-1"
    Open wallet "WalletName"--wallet=WalletNameWASABI--WALLET=WalletName
     How to run
     If the package is installed
    Depending on your operating system, open the command line and execute:
     Linux
    wassabeed --wallet=WalletName --jsonrpcserverenabled=true
+import{_ as d,r as s,o as l,c as u,a as t,d as a,w as n,b as e,e as c}from"./app.65e5b6fd.js";const p={},h=t("h1",{id:"headless-wasabi-daemon",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#headless-wasabi-daemon","aria-hidden":"true"},"#"),e(" Headless Wasabi Daemon")],-1),b={class:"table-of-contents"},m=t("h2",{id:"introduction",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),e(" Introduction")],-1),q={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},v=c(`
    The desktop app (GUI) is built on top of the daemon. Meaning that command line arguments/variables can also be used to configure the desktop app.
     Available commands
    When entering the commands on the command line, they are capital letter insensitive.
     Config file configurations
    All configuration options available via the Config.json file are also available as command line arguments:
    Config FileCommand LineEnvironment variable
    ""Network": "TestNet"--network=testnetWASABI-NETWORK=testnet
    "MainNetBackendUri": "https://api.wasabiwallet.io/"--mainnetbackenduri="https://api.wasabiwallet.io/"WASABI-MAINNETBACKENDURI="https://api.wasabiwallet.io/"
    "TestNetClearnetBackendUri": "https://api.wasabiwallet.co/"--testnetbackenduri="https://api.wasabiwallet.co/"WASABI-TESTNETBACKENDURI="https://api.wasabiwallet.co/"
    "RegTestBackendUri": "http://localhost:37127/"--regtestbackenduri="http://localhost:37127/"WASABI-REGTESTBACKENDURI="http://localhost:37127/"
    ""UseTor": ""true"--usetor=trueWASABI-USETOR=true
    "TerminateTorOnExit": ""false"--terminatetoronexit=falseWASABI-TERMINATETORONEXIT=false
    "DownloadNewVersion": true--downloadnewversion=trueWASABI-DOWNLOADNEWVERSION=true
    "StartLocalBitcoinCoreOnStartup": false--startlocalbitcoincoreonstartup=falseWASABI-STARTLOCALBITCOINCOREONSTARTUP=false
    "StopLocalBitcoinCoreOnShutdown": true--stoplocalbitcoincoreonshutdown=trueWASABI-STOPLOCALBITCOINCOREONSHUTDOWN=true
    "LocalBitcoinCoreDataDir": "/home/UserName/.bitcoin"--localbitcoincoredatadir="/home/UserName/.bitcoin"WASABI-LOCALBITCOINCOREDATADIR="/home/UserName/.bitcoin"
    "MainNetBitcoinP2pEndPoint": "127.0.0.1:8333"--mainnetbitcoinp2pendpoint="127.0.0.1:8333"WASABI-MAINNETBITCOINP2PENDPOINT="127.0.0.1:8333"
    "TestNetBitcoinP2pEndPoint": "127.0.0.1:18333"--testnetbitcoinp2pendpoint="127.0.0.1:18333"WASABI-TESTNETBITCOINP2PENDPOINT="127.0.0.1:18333"
    "RegTestBitcoinP2pEndPoint": "127.0.0.1:18444"--regtestbitcoinp2pendpoint="127.0.0.1:18444"WASABI-REGTESTBITCOINP2PENDPOINT="127.0.0.1:18444"
    "JsonRpcServerEnabled": "true"--jsonrpcserverenabled=trueWASABI-JSONRPCSERVERENABLED=true
    "JsonRpcUser": ""--jsonrpcuser=""WASABI-JSONRPCUSER=""
    "JsonRpcPassword": ""--jsonrpcpassword=""WASABI-JSONRPCPASSWORD=""
    "JsonRpcServerPrefixes":["http://127.0.0.1:37128/", "http://localhost:37128/"]--jsonrpcserverprefixes=["http://127.0.0.1:37128/", "http://localhost:37128/"]WASABI-JSONRPCSERVERPREFIXES=["http://127.0.0.1:37128/", "http://localhost:37128/"]
    "DustThreshold": "0.00005"--dustthreshold=0.00005WASABI-DUSTTHRESHOLD=0.00005
    "EnableGpu": true--enablegpu=trueWASABI-ENABLEGPU=true
    "CoordinatorIdentifier": "CoinJoinCoordinatorIdentifier"--coordinatoridentifier="coinjoincoordinatoridentifier"WASABI-COORDINATORIDENTIFIER="coinjoincoordinatoridentifier"
     Non-Config file configurations
    There are a few special switches that are not present in the Config.json file and are only available using the command line:
    SwitchCommand LineEnvironment variable
    Ignore P2P transactions--blockonly=trueWASABI-BLOCKONLY=true
    The level of detail used during logging--loglevel=traceWASABI-LOGLEVEL=trace
    The path to the directory used during runtime--datadir="$HOME/temp/wasabi-1"WASABI-DATADIR="$HOME/temp/wasabi-1"
    Open wallet "WalletName"--wallet=WalletNameWASABI--WALLET=WalletName
     How to run
     If the package is installed
    Depending on your operating system, open the command line and execute:
     Linux
    wassabeed --wallet=WalletName --jsonrpcserverenabled=true
 
     macOS
    cd /Applications/Wasabi\\ Wallet.app/Contents/MacOs
 ./wassabeed --wallet=WalletName --jsonrpcserverenabled=true
 
     Windows
    cd C:\\Program Files\\WasabiWallet
diff --git a/assets/DeterministicBuild.html.f5a63f91.js b/assets/DeterministicBuild.html.2edc6512.js
similarity index 82%
rename from assets/DeterministicBuild.html.f5a63f91.js
rename to assets/DeterministicBuild.html.2edc6512.js
index 3a434ab4d6..a87cf3318b 100644
--- a/assets/DeterministicBuild.html.f5a63f91.js
+++ b/assets/DeterministicBuild.html.2edc6512.js
@@ -1 +1 @@
-import{_ as n,r,o as a,c as o,a as t,b as e,d as s}from"./app.a5b7c2b2.js";const c={},l=t("h1",{id:"deterministic-build",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#deterministic-build","aria-hidden":"true"},"#"),e(" Deterministic Build")],-1),d={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Guides/DeterministicBuildGuide.md",target:"_blank",rel:"noopener noreferrer"};function u(m,_){const i=r("ExternalLinkIcon");return a(),o("div",null,[l,t("p",null,[e("The guide for the deterministic builds can be found in the "),t("a",d,[e("WalletWasabi repository"),s(i)]),e(".")])])}const b=n(c,[["render",u],["__file","DeterministicBuild.html.vue"]]);export{b as default};
+import{_ as n,r,o as a,c as o,a as t,b as e,d as s}from"./app.65e5b6fd.js";const c={},l=t("h1",{id:"deterministic-build",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#deterministic-build","aria-hidden":"true"},"#"),e(" Deterministic Build")],-1),d={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Guides/DeterministicBuildGuide.md",target:"_blank",rel:"noopener noreferrer"};function u(m,_){const i=r("ExternalLinkIcon");return a(),o("div",null,[l,t("p",null,[e("The guide for the deterministic builds can be found in the "),t("a",d,[e("WalletWasabi repository"),s(i)]),e(".")])])}const b=n(c,[["render",u],["__file","DeterministicBuild.html.vue"]]);export{b as default};
diff --git a/assets/DiscreetMode.html.11ff0e7b.js b/assets/DiscreetMode.html.8c0def53.js
similarity index 97%
rename from assets/DiscreetMode.html.11ff0e7b.js
rename to assets/DiscreetMode.html.8c0def53.js
index 86333bca9b..688e8fae58 100644
--- a/assets/DiscreetMode.html.11ff0e7b.js
+++ b/assets/DiscreetMode.html.8c0def53.js
@@ -1 +1 @@
-import{_ as r}from"./DiscreetModeActivate.e372f614.js";import{_ as c,r as a,o as l,c as d,a as e,d as o,w as s,b as t,e as h}from"./app.a5b7c2b2.js";const m="/WalletDiscreetModeActive.png",_="/DiscreetModeDeactivate.png",u={},f=e("h1",{id:"discreet-mode",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#discreet-mode","aria-hidden":"true"},"#"),t(" Discreet Mode")],-1),b=e("p",null,"Discreet Mode is a Wasabi Wallet feature that hides sensitive and critical information from physical observers and allows you to post screenshots without worrying about your privacy.",-1),p=e("p",null,[e("img",{src:m,alt:"Wasabi Wallet Discreet Mode",title:"Wasabi Wallet Discreet Mode"})],-1),v={class:"table-of-contents"},D=h('
     How to activate/deactivate Discreet Mode
    You can activate or deactivate by clicking the Discreet Mode icon in the bottom left corner of the main view.
    Enable Discreet Mode in Wasabi Wallet
    Disable Discreet Mode in Wasabi Wallet
     More information on Discreet Mode
    ',6),M=e("li",null,"In Discreet Mode the wallet is still usable, meaning that you can send and receive payments, as well as coinjoin.",-1),w=e("li",null,"Discreet Mode only masks the surface. This means that when you click to see more Details, some information (which wasn't visible at first) will be shown.",-1),W=e("li",null,"When hovering over the ### chars with the cursor, the content will be visible for a short amount of time.",-1),g={href:"https://github.com/zkSNACKs/WalletWasabi/issues/2234",target:"_blank",rel:"noopener noreferrer"};function k(x,y){const i=a("router-link"),n=a("ExternalLinkIcon");return l(),d("div",null,[f,b,p,e("nav",v,[e("ul",null,[e("li",null,[o(i,{to:"#how-to-activate-deactivate-discreet-mode"},{default:s(()=>[t("How to activate/deactivate Discreet Mode")]),_:1})]),e("li",null,[o(i,{to:"#more-information-on-discreet-mode"},{default:s(()=>[t("More information on Discreet Mode")]),_:1})])])]),D,e("ul",null,[M,w,W,e("li",null,[t("Some justification of design decisions can be seen "),e("a",g,[t("here"),o(n)]),t(".")])])])}const V=c(u,[["render",k],["__file","DiscreetMode.html.vue"]]);export{V as default};
+import{_ as r}from"./DiscreetModeActivate.e372f614.js";import{_ as c,r as a,o as l,c as d,a as e,d as o,w as s,b as t,e as h}from"./app.65e5b6fd.js";const m="/WalletDiscreetModeActive.png",_="/DiscreetModeDeactivate.png",u={},f=e("h1",{id:"discreet-mode",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#discreet-mode","aria-hidden":"true"},"#"),t(" Discreet Mode")],-1),b=e("p",null,"Discreet Mode is a Wasabi Wallet feature that hides sensitive and critical information from physical observers and allows you to post screenshots without worrying about your privacy.",-1),p=e("p",null,[e("img",{src:m,alt:"Wasabi Wallet Discreet Mode",title:"Wasabi Wallet Discreet Mode"})],-1),v={class:"table-of-contents"},D=h('
     How to activate/deactivate Discreet Mode
    You can activate or deactivate by clicking the Discreet Mode icon in the bottom left corner of the main view.
    Enable Discreet Mode in Wasabi Wallet
    Disable Discreet Mode in Wasabi Wallet
     More information on Discreet Mode
    ',6),M=e("li",null,"In Discreet Mode the wallet is still usable, meaning that you can send and receive payments, as well as coinjoin.",-1),w=e("li",null,"Discreet Mode only masks the surface. This means that when you click to see more Details, some information (which wasn't visible at first) will be shown.",-1),W=e("li",null,"When hovering over the ### chars with the cursor, the content will be visible for a short amount of time.",-1),g={href:"https://github.com/zkSNACKs/WalletWasabi/issues/2234",target:"_blank",rel:"noopener noreferrer"};function k(x,y){const i=a("router-link"),n=a("ExternalLinkIcon");return l(),d("div",null,[f,b,p,e("nav",v,[e("ul",null,[e("li",null,[o(i,{to:"#how-to-activate-deactivate-discreet-mode"},{default:s(()=>[t("How to activate/deactivate Discreet Mode")]),_:1})]),e("li",null,[o(i,{to:"#more-information-on-discreet-mode"},{default:s(()=>[t("More information on Discreet Mode")]),_:1})])])]),D,e("ul",null,[M,w,W,e("li",null,[t("Some justification of design decisions can be seen "),e("a",g,[t("here"),o(n)]),t(".")])])])}const V=c(u,[["render",k],["__file","DiscreetMode.html.vue"]]);export{V as default};
diff --git a/assets/ELI5.html.14e7fa96.js b/assets/ELI5.html.ba29f3b5.js
similarity index 99%
rename from assets/ELI5.html.14e7fa96.js
rename to assets/ELI5.html.ba29f3b5.js
index 1d8c63a78c..9a2239101d 100644
--- a/assets/ELI5.html.14e7fa96.js
+++ b/assets/ELI5.html.ba29f3b5.js
@@ -1 +1 @@
-import{_ as l,r as s,o as c,c as h,a as e,d as t,w as i,b as o,e as d}from"./app.a5b7c2b2.js";const u={},p=e("h1",{id:"explain-wasabi-like-i-m-5",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#explain-wasabi-like-i-m-5","aria-hidden":"true"},"#"),o(" Explain Wasabi like I'm 5")],-1),w={class:"table-of-contents"},y=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),o(" Introduction")],-1),b=e("p",null,"Wasabi Wallet is an open-source, non-custodial, privacy-focused Bitcoin wallet with built-in coinjoins. It is a piece of software that runs on your computer and helps you to manage your bitcoins. Although Wasabi has some very advanced magic under the hood, it is rather easy to use. You can generate a new set of seed words, or import already existing ones. With Wasabi you can receive bitcoins into your full control, and you can send them to someone else without needing permission from any other person or entity. There is also a powerful auto-coinjoin feature to help obfuscate your transaction history. You can use Wasabi to manage your hardware wallet, and it even connects to your own full node. Of course, Wasabi is libre and open-source, which means you have full control over the software you manage your money with.",-1),f=e("h2",{id:"installing-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#installing-wasabi","aria-hidden":"true"},"#"),o(" Installing Wasabi")],-1),m={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},g=e("h2",{id:"generating-a-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#generating-a-wallet","aria-hidden":"true"},"#"),o(" Generating a Wallet")],-1),_=e("p",null,"When you start Wasabi for the first time, the dialog to generate a new wallet will be open. You can set a unique name for the wallet so that you remember what it is for. In the next step, Wasabi will show your 12 recovery words. These must be carefully backed up, in the correct order, as they are needed to recover your wallet (together with the password) on another computer or in another wallet software. Next, choose a very secure password, as this encrypts the secrets, and should not be guessed by others. You will always need this password in order to spend your bitcoins, so take great care to back it up properly. Make sure you store the backup of your recovery words in a different location than the backup of your password.",-1),v=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"Backup both!"),e("p",null,"If you ever need to restore your wallet in Wasabi, or any other wallet, you will need both: your password AND your 12 recovery words.")],-1),k=e("h2",{id:"receiving-bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receiving-bitcoin","aria-hidden":"true"},"#"),o(" Receiving bitcoin")],-1),W=e("p",null,[o("In order to receive bitcoin, you need to generate an address in the "),e("code",null,"Receive"),o(" dialog. But first, you must label it with the names of any observers who know that this address is yours. For example, if Alice pays you back for last nights pizza, then the label is "),e("code",null,"Alice"),o(". This is an important feature for you and the wallet to know which coin is from whom, and it will help with your privacy in the future. Once this newly generated address receives some coins, Wasabi Wallet will automatically hide this used address, so you don't reuse it by accident.")],-1),x=d('
     Sending bitcoin
    Sending process is different depending on the privacy of coins you have. Assuming you have enough private coins the sending process is the following:
    1. Click the Send button (top right corner) at the main view.
    2. Insert the address of the receiver and type in the amount the receiver should get, then click Continue.
    3. Enter the name of the person or company receiving the payment and click Continue.
    4. Make sure everything is filled in correctly in Preview Transaction window and click Confirm.
    5. Type in your password and click Continue.
    You will now see a pop-up window telling you that the transaction is broadcasted to the Bitcoin network.
    ',4),I=e("h2",{id:"coinjoin-with-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-with-wasabi","aria-hidden":"true"},"#"),o(" Coinjoin with Wasabi")],-1),j=e("p",null,[o("If you don't like that your employer knows where you spend your money, or that a merchant can find out how much money you have, then you should coinjoin your bitcoin, as this breaks link to its transaction history. Although the coinjoin protocol is a bit complex, it is very easy to use in Wasabi. The wallet automatically coinjoins all your funds, so that your money becomes private. This process might take some time (hours/days). You can still use your wallet in the mean time, however it is a best practice to only use private funds, which the wallet does automatically when possible. At the wallet's homescreen the percentage indicates the progress to making your wallet fully private. The exact available private amount of bitcoin is listed as "),e("code",null,"PRIVATE"),o(".")],-1);function S(C,T){const a=s("router-link"),r=s("ExternalLinkIcon"),n=s("RouterLink");return c(),h("div",null,[p,e("nav",w,[e("ul",null,[e("li",null,[t(a,{to:"#introduction"},{default:i(()=>[o("Introduction")]),_:1})]),e("li",null,[t(a,{to:"#installing-wasabi"},{default:i(()=>[o("Installing Wasabi")]),_:1})]),e("li",null,[t(a,{to:"#generating-a-wallet"},{default:i(()=>[o("Generating a Wallet")]),_:1})]),e("li",null,[t(a,{to:"#receiving-bitcoin"},{default:i(()=>[o("Receiving bitcoin")]),_:1})]),e("li",null,[t(a,{to:"#sending-bitcoin"},{default:i(()=>[o("Sending bitcoin")]),_:1})]),e("li",null,[t(a,{to:"#coinjoin-with-wasabi"},{default:i(()=>[o("Coinjoin with Wasabi")]),_:1})])])]),y,b,f,e("p",null,[o("Installing Wasabi is super-easy. Go to the official website "),e("a",m,[o("wasabiwallet.io"),t(r)]),o(" and download the version for your operating system. You can then install Wasabi as you would do any other software on your computer.")]),e("p",null,[o("See "),t(n,{to:"/using-wasabi/InstallPackage.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a detailed step-by-step tutorial for all operating systems, and also how to verify the PGP signature.")]),g,_,v,e("p",null,[o("See "),t(n,{to:"/using-wasabi/WalletGeneration.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for more information on how to securely generate your wallet.")]),k,W,e("p",null,[o("See "),t(n,{to:"/using-wasabi/Receive.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a tutorial on how to properly label your addresses and receive bitcoin.")]),x,e("p",null,[o("See "),t(n,{to:"/using-wasabi/Send.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for more details about sending bitcoin and the privacy nuances of it.")]),I,j,e("p",null,[o("See "),t(n,{to:"/using-wasabi/CoinJoin.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a thorough analysis of coinjoin, details on the Wasabi implementation and best practices on how to use it properly.")])])}const E=l(u,[["render",S],["__file","ELI5.html.vue"]]);export{E as default};
+import{_ as l,r as s,o as c,c as h,a as e,d as t,w as i,b as o,e as d}from"./app.65e5b6fd.js";const u={},p=e("h1",{id:"explain-wasabi-like-i-m-5",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#explain-wasabi-like-i-m-5","aria-hidden":"true"},"#"),o(" Explain Wasabi like I'm 5")],-1),w={class:"table-of-contents"},y=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),o(" Introduction")],-1),b=e("p",null,"Wasabi Wallet is an open-source, non-custodial, privacy-focused Bitcoin wallet with built-in coinjoins. It is a piece of software that runs on your computer and helps you to manage your bitcoins. Although Wasabi has some very advanced magic under the hood, it is rather easy to use. You can generate a new set of seed words, or import already existing ones. With Wasabi you can receive bitcoins into your full control, and you can send them to someone else without needing permission from any other person or entity. There is also a powerful auto-coinjoin feature to help obfuscate your transaction history. You can use Wasabi to manage your hardware wallet, and it even connects to your own full node. Of course, Wasabi is libre and open-source, which means you have full control over the software you manage your money with.",-1),f=e("h2",{id:"installing-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#installing-wasabi","aria-hidden":"true"},"#"),o(" Installing Wasabi")],-1),m={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},g=e("h2",{id:"generating-a-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#generating-a-wallet","aria-hidden":"true"},"#"),o(" Generating a Wallet")],-1),_=e("p",null,"When you start Wasabi for the first time, the dialog to generate a new wallet will be open. You can set a unique name for the wallet so that you remember what it is for. In the next step, Wasabi will show your 12 recovery words. These must be carefully backed up, in the correct order, as they are needed to recover your wallet (together with the password) on another computer or in another wallet software. Next, choose a very secure password, as this encrypts the secrets, and should not be guessed by others. You will always need this password in order to spend your bitcoins, so take great care to back it up properly. Make sure you store the backup of your recovery words in a different location than the backup of your password.",-1),v=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"Backup both!"),e("p",null,"If you ever need to restore your wallet in Wasabi, or any other wallet, you will need both: your password AND your 12 recovery words.")],-1),k=e("h2",{id:"receiving-bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receiving-bitcoin","aria-hidden":"true"},"#"),o(" Receiving bitcoin")],-1),W=e("p",null,[o("In order to receive bitcoin, you need to generate an address in the "),e("code",null,"Receive"),o(" dialog. But first, you must label it with the names of any observers who know that this address is yours. For example, if Alice pays you back for last nights pizza, then the label is "),e("code",null,"Alice"),o(". This is an important feature for you and the wallet to know which coin is from whom, and it will help with your privacy in the future. Once this newly generated address receives some coins, Wasabi Wallet will automatically hide this used address, so you don't reuse it by accident.")],-1),x=d('
     Sending bitcoin
    Sending process is different depending on the privacy of coins you have. Assuming you have enough private coins the sending process is the following:
    1. Click the Send button (top right corner) at the main view.
    2. Insert the address of the receiver and type in the amount the receiver should get, then click Continue.
    3. Enter the name of the person or company receiving the payment and click Continue.
    4. Make sure everything is filled in correctly in Preview Transaction window and click Confirm.
    5. Type in your password and click Continue.
    You will now see a pop-up window telling you that the transaction is broadcasted to the Bitcoin network.
    ',4),I=e("h2",{id:"coinjoin-with-wasabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-with-wasabi","aria-hidden":"true"},"#"),o(" Coinjoin with Wasabi")],-1),j=e("p",null,[o("If you don't like that your employer knows where you spend your money, or that a merchant can find out how much money you have, then you should coinjoin your bitcoin, as this breaks link to its transaction history. Although the coinjoin protocol is a bit complex, it is very easy to use in Wasabi. The wallet automatically coinjoins all your funds, so that your money becomes private. This process might take some time (hours/days). You can still use your wallet in the mean time, however it is a best practice to only use private funds, which the wallet does automatically when possible. At the wallet's homescreen the percentage indicates the progress to making your wallet fully private. The exact available private amount of bitcoin is listed as "),e("code",null,"PRIVATE"),o(".")],-1);function S(C,T){const a=s("router-link"),r=s("ExternalLinkIcon"),n=s("RouterLink");return c(),h("div",null,[p,e("nav",w,[e("ul",null,[e("li",null,[t(a,{to:"#introduction"},{default:i(()=>[o("Introduction")]),_:1})]),e("li",null,[t(a,{to:"#installing-wasabi"},{default:i(()=>[o("Installing Wasabi")]),_:1})]),e("li",null,[t(a,{to:"#generating-a-wallet"},{default:i(()=>[o("Generating a Wallet")]),_:1})]),e("li",null,[t(a,{to:"#receiving-bitcoin"},{default:i(()=>[o("Receiving bitcoin")]),_:1})]),e("li",null,[t(a,{to:"#sending-bitcoin"},{default:i(()=>[o("Sending bitcoin")]),_:1})]),e("li",null,[t(a,{to:"#coinjoin-with-wasabi"},{default:i(()=>[o("Coinjoin with Wasabi")]),_:1})])])]),y,b,f,e("p",null,[o("Installing Wasabi is super-easy. Go to the official website "),e("a",m,[o("wasabiwallet.io"),t(r)]),o(" and download the version for your operating system. You can then install Wasabi as you would do any other software on your computer.")]),e("p",null,[o("See "),t(n,{to:"/using-wasabi/InstallPackage.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a detailed step-by-step tutorial for all operating systems, and also how to verify the PGP signature.")]),g,_,v,e("p",null,[o("See "),t(n,{to:"/using-wasabi/WalletGeneration.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for more information on how to securely generate your wallet.")]),k,W,e("p",null,[o("See "),t(n,{to:"/using-wasabi/Receive.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a tutorial on how to properly label your addresses and receive bitcoin.")]),x,e("p",null,[o("See "),t(n,{to:"/using-wasabi/Send.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for more details about sending bitcoin and the privacy nuances of it.")]),I,j,e("p",null,[o("See "),t(n,{to:"/using-wasabi/CoinJoin.html"},{default:i(()=>[o("this chapter")]),_:1}),o(" for a thorough analysis of coinjoin, details on the Wasabi implementation and best practices on how to use it properly.")])])}const E=l(u,[["render",S],["__file","ELI5.html.vue"]]);export{E as default};
diff --git a/assets/FAQ-Contribution.html.07903300.js b/assets/FAQ-Contribution.html.cf858cfb.js
similarity index 99%
rename from assets/FAQ-Contribution.html.07903300.js
rename to assets/FAQ-Contribution.html.cf858cfb.js
index bbe025ed90..698201eb88 100644
--- a/assets/FAQ-Contribution.html.07903300.js
+++ b/assets/FAQ-Contribution.html.cf858cfb.js
@@ -1 +1 @@
-import{_ as r}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as h,r as s,o as l,c,a as t,b as e,d as o,w as i,e as u}from"./app.a5b7c2b2.js";const d={},p=t("h1",{id:"contributions-to-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#contributions-to-wasabi","aria-hidden":"true"},"#"),e(" Contributions to Wasabi")],-1),b=t("h3",{id:"how-to-donate-to-wasabi-wallet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-to-donate-to-wasabi-wallet","aria-hidden":"true"},"#"),e(" How to donate to Wasabi Wallet?")],-1),f=t("h2",{id:"the-wasabikas",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#the-wasabikas","aria-hidden":"true"},"#"),e(" The Wasabikas")],-1),m=t("h3",{id:"who-is-contributing-to-wasabi-already",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#who-is-contributing-to-wasabi-already","aria-hidden":"true"},"#"),e(" Who is contributing to Wasabi already?")],-1),_={href:"https://github.com/zkSNACKs/WalletWasabi/graphs/contributors",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/nopara73",target:"_blank",rel:"noopener noreferrer"},k={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/nopara73/ZeroLink",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/lontivero",target:"_blank",rel:"noopener noreferrer"},v={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/molnard",target:"_blank",rel:"noopener noreferrer"},C={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},A={href:"https://github.com/danwalmsley",target:"_blank",rel:"noopener noreferrer"},z={href:"https://github.com/AvaloniaUI/Avalonia",target:"_blank",rel:"noopener noreferrer"},N={href:"https://youtu.be/F8xNSOhbWrw",target:"_blank",rel:"noopener noreferrer"},x=t("img",{src:r,alt:"Watch the video"},null,-1),T={href:"https://youtu.be/Yg7_3LIutJA",target:"_blank",rel:"noopener noreferrer"},I=t("img",{src:r,alt:"Watch the video"},null,-1),S={href:"https://youtu.be/X9BB_9faJE8",target:"_blank",rel:"noopener noreferrer"},q=t("img",{src:r,alt:"Watch the video"},null,-1),K=t("h3",{id:"who-reviews-and-merges-the-pull-requests",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#who-reviews-and-merges-the-pull-requests","aria-hidden":"true"},"#"),e(" Who reviews and merges the pull requests?")],-1),j={href:"https://github.com/zkSNACKs/WalletWasabi/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},L={href:"https://help.github.com/en/github/administering-a-repository/about-required-reviews-for-pull-requests",target:"_blank",rel:"noopener noreferrer"},Y={href:"https://github.com/nopara73",target:"_blank",rel:"noopener noreferrer"},O={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://github.com/nopara73/ZeroLink",target:"_blank",rel:"noopener noreferrer"},E={href:"https://github.com/lontivero",target:"_blank",rel:"noopener noreferrer"},F={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},D={href:"https://github.com/molnard",target:"_blank",rel:"noopener noreferrer"},Q={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},M={href:"https://github.com/danwalmsley",target:"_blank",rel:"noopener noreferrer"},H={href:"https://github.com/AvaloniaUI/Avalonia/",target:"_blank",rel:"noopener noreferrer"},J=u('
     What is on the future roadmap of Wasabi development?
    Wasabi is far from complete, there are many Wasabikas contributing every day to make this tool of self-defense even more powerful. Because Wasabi is libre and open-source software, anyone can support the project without asking for permission. Thus it is relatively tricky to give a precise roadmap with what will be implemented in the near and distant future.
     You can become a Wasabika
     How should I start contributing to Wasabi?
    ',4),Z={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},G={href:"https://github.com/zkSNACKs/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},R=t("h3",{id:"is-there-a-bounty-program",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-there-a-bounty-program","aria-hidden":"true"},"#"),e(" Is there a bounty program?")],-1),U={href:"https://zksnacks.com",target:"_blank",rel:"noopener noreferrer"},P=t("h3",{id:"how-can-i-report-a-bug",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-report-a-bug","aria-hidden":"true"},"#"),e(" How can I report a bug?")],-1),V=t("p",null,"Code is speech, and can never be perfect. Thus it is expected that there are many known and unknown bugs, quirks and issues in Wasabi. Such a complex software requires constant and rigorous review by the developers and the users, this is everyone's responsibility working with Wasabi.",-1),X={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},$={href:"https://github.com/zkSNACKs/WalletWasabi/pulls",target:"_blank",rel:"noopener noreferrer"},ee={href:"https://github.com/zkSNACKs/WalletWasabi/issues/new?template=bug-report.md",target:"_blank",rel:"noopener noreferrer"},te={class:"custom-container danger"},oe=t("p",{class:"custom-container-title"},"DANGER",-1),ae=t("a",{href:"mailto:adam.ficsor73@gmail.com"},"adam.ficsor73@gmail.com",-1),re={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/SECURITY.md",target:"_blank",rel:"noopener noreferrer"},ne=t("h3",{id:"how-can-i-request-a-feature",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-request-a-feature","aria-hidden":"true"},"#"),e(" How can I request a feature?")],-1),se=t("p",null,"Wasabi is a quite beautiful piece of software already. Yet there are also 1001 things that could be just a little better, or even quite substantially superior. The beauty and bane of libre and open-source software is that it is never complete, there is always more work to be done.",-1),ie={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},he={href:"https://github.com/zkSNACKs/WalletWasabi/pulls",target:"_blank",rel:"noopener noreferrer"},le={href:"https://github.com/zkSNACKs/WalletWasabi/issues/new?template=feature-request.md",target:"_blank",rel:"noopener noreferrer"},ce=t("h3",{id:"how-can-i-get-help-and-support",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-get-help-and-support","aria-hidden":"true"},"#"),e(" How can I get help and support?")],-1),ue={href:"https://docs.wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},de={href:"https://github.com/zkSNACKs/WalletWasabi/discussions/5185",target:"_blank",rel:"noopener noreferrer"},pe={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},be=t("h3",{id:"what-does-the-wasabi-project-need-help-with",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-does-the-wasabi-project-need-help-with","aria-hidden":"true"},"#"),e(" What does the Wasabi project need help with?")],-1),fe=t("p",null,"Wasabi is libre and open-source software, thus it relies on the support of several contributors on all fronts. Of course, this includes coding new features, bug fixes and stability improvements. Yet just equally important is the review of the commits of all other Wasabikas. It's not just the contributions to the code, but also to the documentation and the effort to educate peers using Wasabi. This includes education in meatspace tribe gatherings, but also in cyberspace peer support. So basically, we need help with building and shilling Wasabi!",-1);function me(_e,ge){const n=s("RouterLink"),a=s("ExternalLinkIcon");return l(),c("div",null,[p,b,t("p",null,[e("Adam Ficsor had a donation address for a few years while he was working alone on Wasabi. It's not the case anymore. Though it's most likely not an issue to accept Bitcoin donations, zkSNACKs team discontinued accepting donations because they don't want to get into accidental legal gray areas. Wasabi has a coordination fee that is capped at 0.3% for every CoinJoin and it became zkSNACKs' main income. To help Wasabi development, just CoinJoin your bitcoins via Wasabi! If you want to read more about fees here is a nice explanation: "),o(n,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-fees-for-the-coinjoin"},{default:i(()=>[e("What are the fees for the CoinJoin")]),_:1}),e(".")]),f,m,t("p",null,[e("There are many Wasabikas working with great effort and care to manifest this powerful tool of self-defense. "),t("a",_,[e("Over 50 peers"),o(a)]),e(" have already contributed to the repository. Four of the main contributors are "),t("a",g,[e("Ádám Ficsor"),o(a)]),e(" [co-founder and former CTO of "),t("a",k,[e("zkSNACKs Ltd"),o(a)]),e(", co-author of the "),t("a",w,[e("zero link Bitcoin fungibility framework"),o(a)]),e("], "),t("a",y,[e("Lucas Ontivero"),o(a)]),e(" [lead engineer of "),t("a",v,[e("zkSNACKs Ltd"),o(a)]),e("], "),t("a",W,[e("Dávid Molnár"),o(a)]),e(" [CTO of "),t("a",C,[e("zkSNACKs Ltd"),o(a)]),e("], and "),t("a",A,[e("Dan Walmsley"),o(a)]),e(" [co-maintainer of "),t("a",z,[e("Avalonia UI Framework"),o(a)]),e("].")]),t("p",null,[t("a",N,[x,o(a)])]),t("p",null,[t("a",T,[I,o(a)])]),t("p",null,[t("a",S,[q,o(a)])]),K,t("p",null,[e("As the Wasabi code is libre and open-source, anyone has access to review the latest contributions and browse the "),t("a",j,[e("open pull requests"),o(a)]),e(". The review of any Wasabika is not just deeply appreciated, but desperately needed! Wasabi is cutting-edge, high security software, and there can never be enough eyes seeking and squashing bugs. Especially review by experienced C# developers are vitally important, yet even typo and grammar fixes are necessary.")]),t("p",null,[e("There are four developers who have the ability to merge code into master branch. Per default, they "),t("a",L,[e("require at least one approving review"),o(a)]),e(" by one of the other maintainers before a pull request can be merged. However, since all four are administrators, they can still force the merge without the approval of others, but this will be noticed by many contributors.")]),t("ul",null,[t("li",null,[t("a",Y,[e("Ádám Ficsor"),o(a)]),e(", co-founder and former CTO of "),t("a",O,[e("zkSNACKs Ltd"),o(a)]),e(", co-author of the "),t("a",B,[e("zero link Bitcoin fungibility framework"),o(a)]),e(".")]),t("li",null,[t("a",E,[e("Lucas Ontivero"),o(a)]),e(", lead engineer of "),t("a",F,[e("zkSNACKs Ltd"),o(a)]),e(".")]),t("li",null,[t("a",D,[e("Dávid Molnár"),o(a)]),e(", CTO of "),t("a",Q,[e("zkSNACKs Ltd"),o(a)]),e(".")]),t("li",null,[t("a",M,[e("Dan Walmsley"),o(a)]),e(", co-maintainer of "),t("a",H,[e("Avalonia"),o(a)]),e(".")])]),J,t("p",null,[e("Thank you for considering to support this beautiful libre and open-source project! It is the responsibility of everyone using the software to contribute to its growth. Your help is deeply appreciated, and very much needed! First please read the "),o(n,{to:"/building-wasabi/ContributionChecklist.html"},{default:i(()=>[e("contribution checklist")]),_:1}),e(" to get introduced to the project and to start out in the right direction. Join our "),t("a",Z,[e("Slack"),o(a)]),e(" and check out our "),t("a",G,[e("GitHub repository"),o(a)]),e(", so that you can stay up-to-date with the latest contributions.")]),R,t("p",null,[e("Yes! The beauty of Wasabi is that it's not just a very awesome wallet by default, but it has the additional opt-in CoinJoin service. This is provided by "),t("a",U,[e("zkSNACKs Ltd."),o(a)]),e(", and in exchange for this service, the user pays a coordination fee. In return, zkSNACKs is supporting several developers to dedicate their full time to contribute to this open-source project. There are also contribution games where a bounty is paid out to any contributor worthy the prize.")]),P,V,t("p",null,[e("When you stumble upon an issue that needs fixing, please first check the open "),t("a",X,[e("issues"),o(a)]),e(" and "),t("a",$,[e("pull requests"),o(a)]),e(" if there is already someone working on it. If yes, then you can comment your situation and bug report under the open issue. If no, then please consider to "),t("a",ee,[e("open a new issue"),o(a)]),e(" and give a detailed report on the problem. It is especially helpful when you provide a step-by-step guide on how to reproduce what you have found. There is constantly a lot of work done to the code base, thus it's good to know which version of Wasabi, and what operating system you are using. In some cases it might be useful to see your logs, though please consider your privacy and encrypt this data properly in direct communication with the developers.")]),t("div",te,[oe,t("p",null,[e("If you find a bug that puts users' privacy or security at serious risk, please take great care with responsible disclosure! Send an email to "),ae,e(", preferably using PGP encryption "),t("a",re,[e("21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E"),o(a)]),e(".")])]),ne,se,t("p",null,[e("Regardless if you are a new user of Wasabi, or a veteran black belt Wasabika, any suggestions on how to improve are very welcome. Please first check the existing "),t("a",ie,[e("issues"),o(a)]),e(" and "),t("a",he,[e("pull requests"),o(a)]),e(" if someone has the same feature request as you. If yes, then you can comment your desired improvement under the open issue. If no, then please consider to "),t("a",le,[e("open a new issue"),o(a)]),e(" and give a detailed request. It makes sense to first explain the problem you have in the incumbent version of Wasabi, this is the place to express your frustrations and annoyances. Then describe the solution that you have envisioned, with all the nuances and details of how this would fix your problem. To flesh our your argument, please consider alternatives and different approaches to this feature request.")]),ce,t("p",null,[e("You are already on the right track by first checking "),t("a",ue,[e("this documentation"),o(a)]),e(" for the knowledge you are seeking. It's likely that you are not the first person who has an issue or a question, and hopefully someone has curated the answer in here already. You can use the search function in the top navbar to look for a specific topic, and the sidebar menu as a table of content. You can also use our "),t("a",de,[e("GitHub Discussions"),o(a)]),e(" to find solutions to different issues and to ask questions if necessary. If your trouble is specific to the code, then it might also be suitable to check the existing "),t("a",pe,[e("GitHub issues"),o(a)]),e(" and open a new one.")]),be,fe])}const ye=h(d,[["render",me],["__file","FAQ-Contribution.html.vue"]]);export{ye as default};
+import{_ as r}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as h,r as s,o as l,c,a as t,b as e,d as o,w as i,e as u}from"./app.65e5b6fd.js";const d={},p=t("h1",{id:"contributions-to-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#contributions-to-wasabi","aria-hidden":"true"},"#"),e(" Contributions to Wasabi")],-1),b=t("h3",{id:"how-to-donate-to-wasabi-wallet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-to-donate-to-wasabi-wallet","aria-hidden":"true"},"#"),e(" How to donate to Wasabi Wallet?")],-1),f=t("h2",{id:"the-wasabikas",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#the-wasabikas","aria-hidden":"true"},"#"),e(" The Wasabikas")],-1),m=t("h3",{id:"who-is-contributing-to-wasabi-already",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#who-is-contributing-to-wasabi-already","aria-hidden":"true"},"#"),e(" Who is contributing to Wasabi already?")],-1),_={href:"https://github.com/zkSNACKs/WalletWasabi/graphs/contributors",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/nopara73",target:"_blank",rel:"noopener noreferrer"},k={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/nopara73/ZeroLink",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/lontivero",target:"_blank",rel:"noopener noreferrer"},v={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/molnard",target:"_blank",rel:"noopener noreferrer"},C={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},A={href:"https://github.com/danwalmsley",target:"_blank",rel:"noopener noreferrer"},z={href:"https://github.com/AvaloniaUI/Avalonia",target:"_blank",rel:"noopener noreferrer"},N={href:"https://youtu.be/F8xNSOhbWrw",target:"_blank",rel:"noopener noreferrer"},x=t("img",{src:r,alt:"Watch the video"},null,-1),T={href:"https://youtu.be/Yg7_3LIutJA",target:"_blank",rel:"noopener noreferrer"},I=t("img",{src:r,alt:"Watch the video"},null,-1),S={href:"https://youtu.be/X9BB_9faJE8",target:"_blank",rel:"noopener noreferrer"},q=t("img",{src:r,alt:"Watch the video"},null,-1),K=t("h3",{id:"who-reviews-and-merges-the-pull-requests",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#who-reviews-and-merges-the-pull-requests","aria-hidden":"true"},"#"),e(" Who reviews and merges the pull requests?")],-1),j={href:"https://github.com/zkSNACKs/WalletWasabi/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc",target:"_blank",rel:"noopener noreferrer"},L={href:"https://help.github.com/en/github/administering-a-repository/about-required-reviews-for-pull-requests",target:"_blank",rel:"noopener noreferrer"},Y={href:"https://github.com/nopara73",target:"_blank",rel:"noopener noreferrer"},O={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://github.com/nopara73/ZeroLink",target:"_blank",rel:"noopener noreferrer"},E={href:"https://github.com/lontivero",target:"_blank",rel:"noopener noreferrer"},F={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},D={href:"https://github.com/molnard",target:"_blank",rel:"noopener noreferrer"},Q={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},M={href:"https://github.com/danwalmsley",target:"_blank",rel:"noopener noreferrer"},H={href:"https://github.com/AvaloniaUI/Avalonia/",target:"_blank",rel:"noopener noreferrer"},J=u('
     What is on the future roadmap of Wasabi development?
    Wasabi is far from complete, there are many Wasabikas contributing every day to make this tool of self-defense even more powerful. Because Wasabi is libre and open-source software, anyone can support the project without asking for permission. Thus it is relatively tricky to give a precise roadmap with what will be implemented in the near and distant future.
     You can become a Wasabika
     How should I start contributing to Wasabi?
    ',4),Z={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},G={href:"https://github.com/zkSNACKs/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},R=t("h3",{id:"is-there-a-bounty-program",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-there-a-bounty-program","aria-hidden":"true"},"#"),e(" Is there a bounty program?")],-1),U={href:"https://zksnacks.com",target:"_blank",rel:"noopener noreferrer"},P=t("h3",{id:"how-can-i-report-a-bug",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-report-a-bug","aria-hidden":"true"},"#"),e(" How can I report a bug?")],-1),V=t("p",null,"Code is speech, and can never be perfect. Thus it is expected that there are many known and unknown bugs, quirks and issues in Wasabi. Such a complex software requires constant and rigorous review by the developers and the users, this is everyone's responsibility working with Wasabi.",-1),X={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},$={href:"https://github.com/zkSNACKs/WalletWasabi/pulls",target:"_blank",rel:"noopener noreferrer"},ee={href:"https://github.com/zkSNACKs/WalletWasabi/issues/new?template=bug-report.md",target:"_blank",rel:"noopener noreferrer"},te={class:"custom-container danger"},oe=t("p",{class:"custom-container-title"},"DANGER",-1),ae=t("a",{href:"mailto:adam.ficsor73@gmail.com"},"adam.ficsor73@gmail.com",-1),re={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/SECURITY.md",target:"_blank",rel:"noopener noreferrer"},ne=t("h3",{id:"how-can-i-request-a-feature",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-request-a-feature","aria-hidden":"true"},"#"),e(" How can I request a feature?")],-1),se=t("p",null,"Wasabi is a quite beautiful piece of software already. Yet there are also 1001 things that could be just a little better, or even quite substantially superior. The beauty and bane of libre and open-source software is that it is never complete, there is always more work to be done.",-1),ie={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},he={href:"https://github.com/zkSNACKs/WalletWasabi/pulls",target:"_blank",rel:"noopener noreferrer"},le={href:"https://github.com/zkSNACKs/WalletWasabi/issues/new?template=feature-request.md",target:"_blank",rel:"noopener noreferrer"},ce=t("h3",{id:"how-can-i-get-help-and-support",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-can-i-get-help-and-support","aria-hidden":"true"},"#"),e(" How can I get help and support?")],-1),ue={href:"https://docs.wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},de={href:"https://github.com/zkSNACKs/WalletWasabi/discussions/5185",target:"_blank",rel:"noopener noreferrer"},pe={href:"https://github.com/zkSNACKs/WalletWasabi/issues/",target:"_blank",rel:"noopener noreferrer"},be=t("h3",{id:"what-does-the-wasabi-project-need-help-with",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-does-the-wasabi-project-need-help-with","aria-hidden":"true"},"#"),e(" What does the Wasabi project need help with?")],-1),fe=t("p",null,"Wasabi is libre and open-source software, thus it relies on the support of several contributors on all fronts. Of course, this includes coding new features, bug fixes and stability improvements. Yet just equally important is the review of the commits of all other Wasabikas. It's not just the contributions to the code, but also to the documentation and the effort to educate peers using Wasabi. This includes education in meatspace tribe gatherings, but also in cyberspace peer support. So basically, we need help with building and shilling Wasabi!",-1);function me(_e,ge){const n=s("RouterLink"),a=s("ExternalLinkIcon");return l(),c("div",null,[p,b,t("p",null,[e("Adam Ficsor had a donation address for a few years while he was working alone on Wasabi. It's not the case anymore. Though it's most likely not an issue to accept Bitcoin donations, zkSNACKs team discontinued accepting donations because they don't want to get into accidental legal gray areas. Wasabi has a coordination fee that is capped at 0.3% for every CoinJoin and it became zkSNACKs' main income. To help Wasabi development, just CoinJoin your bitcoins via Wasabi! If you want to read more about fees here is a nice explanation: "),o(n,{to:"/FAQ/FAQ-UseWasabi.html#what-are-the-fees-for-the-coinjoin"},{default:i(()=>[e("What are the fees for the CoinJoin")]),_:1}),e(".")]),f,m,t("p",null,[e("There are many Wasabikas working with great effort and care to manifest this powerful tool of self-defense. "),t("a",_,[e("Over 50 peers"),o(a)]),e(" have already contributed to the repository. Four of the main contributors are "),t("a",g,[e("Ádám Ficsor"),o(a)]),e(" [co-founder and former CTO of "),t("a",k,[e("zkSNACKs Ltd"),o(a)]),e(", co-author of the "),t("a",w,[e("zero link Bitcoin fungibility framework"),o(a)]),e("], "),t("a",y,[e("Lucas Ontivero"),o(a)]),e(" [lead engineer of "),t("a",v,[e("zkSNACKs Ltd"),o(a)]),e("], "),t("a",W,[e("Dávid Molnár"),o(a)]),e(" [CTO of "),t("a",C,[e("zkSNACKs Ltd"),o(a)]),e("], and "),t("a",A,[e("Dan Walmsley"),o(a)]),e(" [co-maintainer of "),t("a",z,[e("Avalonia UI Framework"),o(a)]),e("].")]),t("p",null,[t("a",N,[x,o(a)])]),t("p",null,[t("a",T,[I,o(a)])]),t("p",null,[t("a",S,[q,o(a)])]),K,t("p",null,[e("As the Wasabi code is libre and open-source, anyone has access to review the latest contributions and browse the "),t("a",j,[e("open pull requests"),o(a)]),e(". The review of any Wasabika is not just deeply appreciated, but desperately needed! Wasabi is cutting-edge, high security software, and there can never be enough eyes seeking and squashing bugs. Especially review by experienced C# developers are vitally important, yet even typo and grammar fixes are necessary.")]),t("p",null,[e("There are four developers who have the ability to merge code into master branch. Per default, they "),t("a",L,[e("require at least one approving review"),o(a)]),e(" by one of the other maintainers before a pull request can be merged. However, since all four are administrators, they can still force the merge without the approval of others, but this will be noticed by many contributors.")]),t("ul",null,[t("li",null,[t("a",Y,[e("Ádám Ficsor"),o(a)]),e(", co-founder and former CTO of "),t("a",O,[e("zkSNACKs Ltd"),o(a)]),e(", co-author of the "),t("a",B,[e("zero link Bitcoin fungibility framework"),o(a)]),e(".")]),t("li",null,[t("a",E,[e("Lucas Ontivero"),o(a)]),e(", lead engineer of "),t("a",F,[e("zkSNACKs Ltd"),o(a)]),e(".")]),t("li",null,[t("a",D,[e("Dávid Molnár"),o(a)]),e(", CTO of "),t("a",Q,[e("zkSNACKs Ltd"),o(a)]),e(".")]),t("li",null,[t("a",M,[e("Dan Walmsley"),o(a)]),e(", co-maintainer of "),t("a",H,[e("Avalonia"),o(a)]),e(".")])]),J,t("p",null,[e("Thank you for considering to support this beautiful libre and open-source project! It is the responsibility of everyone using the software to contribute to its growth. Your help is deeply appreciated, and very much needed! First please read the "),o(n,{to:"/building-wasabi/ContributionChecklist.html"},{default:i(()=>[e("contribution checklist")]),_:1}),e(" to get introduced to the project and to start out in the right direction. Join our "),t("a",Z,[e("Slack"),o(a)]),e(" and check out our "),t("a",G,[e("GitHub repository"),o(a)]),e(", so that you can stay up-to-date with the latest contributions.")]),R,t("p",null,[e("Yes! The beauty of Wasabi is that it's not just a very awesome wallet by default, but it has the additional opt-in CoinJoin service. This is provided by "),t("a",U,[e("zkSNACKs Ltd."),o(a)]),e(", and in exchange for this service, the user pays a coordination fee. In return, zkSNACKs is supporting several developers to dedicate their full time to contribute to this open-source project. There are also contribution games where a bounty is paid out to any contributor worthy the prize.")]),P,V,t("p",null,[e("When you stumble upon an issue that needs fixing, please first check the open "),t("a",X,[e("issues"),o(a)]),e(" and "),t("a",$,[e("pull requests"),o(a)]),e(" if there is already someone working on it. If yes, then you can comment your situation and bug report under the open issue. If no, then please consider to "),t("a",ee,[e("open a new issue"),o(a)]),e(" and give a detailed report on the problem. It is especially helpful when you provide a step-by-step guide on how to reproduce what you have found. There is constantly a lot of work done to the code base, thus it's good to know which version of Wasabi, and what operating system you are using. In some cases it might be useful to see your logs, though please consider your privacy and encrypt this data properly in direct communication with the developers.")]),t("div",te,[oe,t("p",null,[e("If you find a bug that puts users' privacy or security at serious risk, please take great care with responsible disclosure! Send an email to "),ae,e(", preferably using PGP encryption "),t("a",re,[e("21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E"),o(a)]),e(".")])]),ne,se,t("p",null,[e("Regardless if you are a new user of Wasabi, or a veteran black belt Wasabika, any suggestions on how to improve are very welcome. Please first check the existing "),t("a",ie,[e("issues"),o(a)]),e(" and "),t("a",he,[e("pull requests"),o(a)]),e(" if someone has the same feature request as you. If yes, then you can comment your desired improvement under the open issue. If no, then please consider to "),t("a",le,[e("open a new issue"),o(a)]),e(" and give a detailed request. It makes sense to first explain the problem you have in the incumbent version of Wasabi, this is the place to express your frustrations and annoyances. Then describe the solution that you have envisioned, with all the nuances and details of how this would fix your problem. To flesh our your argument, please consider alternatives and different approaches to this feature request.")]),ce,t("p",null,[e("You are already on the right track by first checking "),t("a",ue,[e("this documentation"),o(a)]),e(" for the knowledge you are seeking. It's likely that you are not the first person who has an issue or a question, and hopefully someone has curated the answer in here already. You can use the search function in the top navbar to look for a specific topic, and the sidebar menu as a table of content. You can also use our "),t("a",de,[e("GitHub Discussions"),o(a)]),e(" to find solutions to different issues and to ask questions if necessary. If your trouble is specific to the code, then it might also be suitable to check the existing "),t("a",pe,[e("GitHub issues"),o(a)]),e(" and open a new one.")]),be,fe])}const ye=h(d,[["render",me],["__file","FAQ-Contribution.html.vue"]]);export{ye as default};
diff --git a/assets/FAQ-GeneralBitcoinPrivacy.html.29415500.js b/assets/FAQ-GeneralBitcoinPrivacy.html.f2082e67.js
similarity index 99%
rename from assets/FAQ-GeneralBitcoinPrivacy.html.29415500.js
rename to assets/FAQ-GeneralBitcoinPrivacy.html.f2082e67.js
index b9827e5608..f3614b6ad2 100644
--- a/assets/FAQ-GeneralBitcoinPrivacy.html.29415500.js
+++ b/assets/FAQ-GeneralBitcoinPrivacy.html.f2082e67.js
@@ -1,4 +1,4 @@
-import{_ as s,r as a,o as c,c as l,a as e,b as o,d as t,w as h,e as n}from"./app.a5b7c2b2.js";const d={},u=n('
     General Bitcoin Privacy
     Why Privacy matters
     I have nothing to hide, do I still need financial privacy?
    What did you say to your spouse in bed last night? How much money did you earn last month? What websites have you visited yesterday?
    TIP
    It's not that I have nothing to hide, it's that I have nothing to share.
    There are many tasks in everyday life that are simply none of your business. Knowledge you choose not to share with others, things you only tell one individual, actions that you do while nobody is watching. How much money you earn, and where you spend it, is only your business, and of no concern to most other individuals.
     How is financial privacy an essential element to fungibility in Bitcoin?
    Fungibility is the possibility for an individual receiving bitcoin to safely ignore any connection between this bitcoin and any particular individual or use case it interacted with in the past. If you can meaningfully distinguish one coin from another, then their fungibility is weak. If Bitcoin fungibility is too weak in practice, then it cannot be decentralized: if someone important announces a list of stolen coins they won't accept coins derived from, you must carefully check coins you receive against that list and return the ones that fail. Everyone gets stuck checking blacklists issued by various authorities because in that world we'd all not like to get stuck with bad coins. This adds friction and transactional costs and makes Bitcoin less valuable as money.
     How is financial privacy essential for entrepreneurs?
    If you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.
     How is financial privacy essential for personal safety?
    If thieves can see your income, holdings, and spending, they can use this information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your large purchases off your doorstep, or impersonate businesses you transact with towards you. They can tell exactly how much to try to scam you for. If thieves don't know how much bitcoin you have, then they don't know if you are worth the effort to attack.
     How is financial privacy essential for human dignity?
    No one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.
    Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.
     The Privacy of Bitcoin
     How is Bitcoin good in terms of privacy?
    Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.
    Instead, in Bitcoin pseudonyms protect your identity. In the Bitcoin ecosystem, everyone can see the history of every account balance, but they cannot see who controls an account. All addresses and transactions are recorded in Bitcoin’s publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.
     How is Bitcoin bad in terms of privacy?
    Bitcoin is by default a transparent system, in which every piece of information is available to the public. As such, every Bitcoin user requires some level of protection. Anyone with substantial wealth in Bitcoin would not want to advertise their funds to every person they transact with, for obvious reasons. But every time you spend just a tiny portion of your bitcoin, you might reveal your wealth to the other party. Doing that on the internet is like flashing large stacks of cash in a dark back alley, so obviously it’s not advisable! A criminal might see how much you have and decide to come after it. Distributing your wealth between several wallets and using a different address for each transaction is a common practice that prevents others from knowing how much bitcoin you have.
    Each Bitcoin transaction contains at least one input (where the Bitcoin are from) and at least one output (where the Bitcoin are being sent). This means that once a single address is known, there is a trail to follow the Bitcoin.
    Another characteristic of Bitcoin transactions is that the value of the input always needs to match the value of the previous transaction output. If you previously received 1 bitcoin, and you want to spend 0.4 bitcoin, the transaction needs to spend the whole 1 bitcoin. 0.4 bitcoin will go as payment, then 0.6 bitcoin will return to you as change. Your Bitcoin wallet will handle this process automatically, but it is important to understand the principle in order to use it anonymously.
    The owner of the original bitcoin doesn't know whom you paid the money or what you did with it, but they can see the amounts and addresses involved. They can see two outputs of the transaction: one worth 0.4 bitcoin and one worth 0.6 bitcoin. They might not know for certain which is the purchase and which is the change, but they can apply heuristics to estimate it.
    Similarly, if you receive 0.5 bitcoin but want to spend 1 bitcoin, you need to own additional coins with a combined value of at least 0.5 bitcoin in them. When spending two coins within one transaction, it is often assumed that both of these coins belong to the same entity, this is the common input ownership heuristic.
     Why is it important to run a full node?
    TIP
    Not your node ~ not your rules
    ',27),p={href:"https://github.com/bitcoin/bitcoin",target:"_blank",rel:"noopener noreferrer"},y=e("h3",{id:"how-does-a-full-node-protect-my-privacy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-does-a-full-node-protect-my-privacy","aria-hidden":"true"},"#"),o(" How does a full node protect my privacy?")],-1),b={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},f=e("h3",{id:"how-can-i-set-up-a-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-can-i-set-up-a-full-node","aria-hidden":"true"},"#"),o(" How can I set up a full node?")],-1),m={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/libbitcoin/libbitcoin-node",target:"_blank",rel:"noopener noreferrer"},v=e("p",null,"Instead, if you prefer to use some dedicated hardware solutions, these are some of the most reliable projects:",-1),k={href:"https://github.com/rootzoll/raspiblitz",target:"_blank",rel:"noopener noreferrer"},_={href:"https://raspibolt.org/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://nixbitcoin.org/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://www.nodl.eu/",target:"_blank",rel:"noopener noreferrer"},x={href:"https://mynodebtc.com/",target:"_blank",rel:"noopener noreferrer"},I={href:"https://start9.com/",target:"_blank",rel:"noopener noreferrer"},W=e("h3",{id:"why-is-it-important-to-use-a-new-address-for-every-payment",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-is-it-important-to-use-a-new-address-for-every-payment","aria-hidden":"true"},"#"),o(" Why is it important to use a new address for every payment?")],-1),A=e("p",null,"Addresses being used more than once is very damaging to privacy because that links together more blockchain transactions with proof that they were created by the same entity. The most private and secure way to use bitcoin is to send a brand new address to each person who pays you. After an address has received a coin, it should never be used again. Also, a brand new bitcoin address should be demanded from the recipient when sending bitcoin. Wasabi has a user interface which discourages address reuse by removing from the GUI addresses which have received a coin.",-1),j=e("p",null,'It has been argued that the phrase "bitcoin address" was a bad name for this object because it implies it can be reused like an email address. A better name would be something like "bitcoin invoice".',-1),F=e("p",null,"Bitcoin isn't anonymous but pseudonymous, and the pseudonyms are bitcoin addresses. Avoiding address reuse is like throwing away a pseudonym after it has been used.",-1),S=e("h3",{id:"what-is-a-coinjoin-sudoku",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-a-coinjoin-sudoku","aria-hidden":"true"},"#"),o(" What is a coinjoin Sudoku?")],-1),C={href:"https://www.coinjoinsudoku.com/advisory/",target:"_blank",rel:"noopener noreferrer"},D=n('
     The Privacy of Tor
     How does Tor protect my network-level privacy?
    When you make a Bitcoin transaction, you are essentially creating a message on your phone or computer and sending it to the Bitcoin network. Someone operating a large number of nodes on the Bitcoin network might be able to match some of your transactions to your IP address, then deanonymize your stack of bitcoin.
    It is relatively easy to avoid this on a computer by relaying all transactions through the Tor network. Wasabi routes all traffic via Tor’s SOCKS5 proxy, by default.
    To maintain your anonymity, use the Tor Browser or the Tails operating system, if possible. Route everything through Tor by default.
    It is also good practice to route your chats through the Tor network. You can also configure many cloud storage providers in this way.
     Why does Tor process keep running after closing Wasabi Wallet?
    There are two main reasons: user experience and privacy.
    If a user closes Wasabi and then starts it again, he's already connected to Tor and he does not need to build a new Tor circuit. This means that Wasabi's startup will be much faster, because the Tor circuit is already established.
    Regarding the privacy, this is done to avoid time correlation attacks when using Wasabi Wallet. In fact, if a user creates a new Tor circuit every time he opens Wasabi Wallet, he would send a series of information to the Bitcoin network, which could allow a correlation and deanonymization of the user himself.
     My country/ISP is blocking/censoring Tor, how can I use Wasabi with Tor bridges?
    WARNING
    Feature not yet ported to Wasabi 2.0
    ',12),P={href:"https://www.torproject.org/docs/bridges",target:"_blank",rel:"noopener noreferrer"},N=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,"If you are using Tor Browser Bundle it is extremely easy to configure it to use bridges. Configuring Tor bridges running in a daemon mode is more difficult and takes more time.")],-1),R=e("p",null,[e("strong",null,"Steps with Tor Browser:")],-1),E={href:"https://www.torproject.org/",target:"_blank",rel:"noopener noreferrer"},H=n("
  • Change the Settings of the Tor Browser to use one of the bridges or pluggable transports
  • Leave Tor Browser running after connecting with a bridge
  • Change the Settings of Wasabi Wallet and edit TorSocks5 Endpoint from 127.0.0.1:9050 to 127.0.0.1:9150
  • Restart Wasabi
    • ",4),Y=e("p",null,"After this, Wasabi will connect to Tor using the Tor Browser's connection via a random bridge.",-1),z=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"WARNING"),e("p",null,"To make use of Tor bridges on Wasabi, you must always keep Tor Browser open.")],-1),G=e("p",null,[e("strong",null,"Steps with Tor Daemon on Linux:")],-1),L=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,"These are commands for Debian. Feel free to edit these commands according to your distribution.")],-1),O={href:"https://bridges.torproject.org/bridges",target:"_blank",rel:"noopener noreferrer"},K=e("li",null,[o("Install Tor daemon with "),e("code",null,"sudo apt-get install tor")],-1),U=e("li",null,[o("Install OBFS4 support (needed to connect to bridges), by editing your "),e("code",null,"/etc/apt/sources.list"),o(" and adding this line:")],-1),V=n(`
    # Tor Bridges
+import{_ as s,r as a,o as c,c as l,a as e,b as o,d as t,w as h,e as n}from"./app.65e5b6fd.js";const d={},u=n('
     General Bitcoin Privacy
     Why Privacy matters
     I have nothing to hide, do I still need financial privacy?
    What did you say to your spouse in bed last night? How much money did you earn last month? What websites have you visited yesterday?
    TIP
    It's not that I have nothing to hide, it's that I have nothing to share.
    There are many tasks in everyday life that are simply none of your business. Knowledge you choose not to share with others, things you only tell one individual, actions that you do while nobody is watching. How much money you earn, and where you spend it, is only your business, and of no concern to most other individuals.
     How is financial privacy an essential element to fungibility in Bitcoin?
    Fungibility is the possibility for an individual receiving bitcoin to safely ignore any connection between this bitcoin and any particular individual or use case it interacted with in the past. If you can meaningfully distinguish one coin from another, then their fungibility is weak. If Bitcoin fungibility is too weak in practice, then it cannot be decentralized: if someone important announces a list of stolen coins they won't accept coins derived from, you must carefully check coins you receive against that list and return the ones that fail. Everyone gets stuck checking blacklists issued by various authorities because in that world we'd all not like to get stuck with bad coins. This adds friction and transactional costs and makes Bitcoin less valuable as money.
     How is financial privacy essential for entrepreneurs?
    If you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.
     How is financial privacy essential for personal safety?
    If thieves can see your income, holdings, and spending, they can use this information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your large purchases off your doorstep, or impersonate businesses you transact with towards you. They can tell exactly how much to try to scam you for. If thieves don't know how much bitcoin you have, then they don't know if you are worth the effort to attack.
     How is financial privacy essential for human dignity?
    No one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.
    Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.
     The Privacy of Bitcoin
     How is Bitcoin good in terms of privacy?
    Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.
    Instead, in Bitcoin pseudonyms protect your identity. In the Bitcoin ecosystem, everyone can see the history of every account balance, but they cannot see who controls an account. All addresses and transactions are recorded in Bitcoin’s publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.
     How is Bitcoin bad in terms of privacy?
    Bitcoin is by default a transparent system, in which every piece of information is available to the public. As such, every Bitcoin user requires some level of protection. Anyone with substantial wealth in Bitcoin would not want to advertise their funds to every person they transact with, for obvious reasons. But every time you spend just a tiny portion of your bitcoin, you might reveal your wealth to the other party. Doing that on the internet is like flashing large stacks of cash in a dark back alley, so obviously it’s not advisable! A criminal might see how much you have and decide to come after it. Distributing your wealth between several wallets and using a different address for each transaction is a common practice that prevents others from knowing how much bitcoin you have.
    Each Bitcoin transaction contains at least one input (where the Bitcoin are from) and at least one output (where the Bitcoin are being sent). This means that once a single address is known, there is a trail to follow the Bitcoin.
    Another characteristic of Bitcoin transactions is that the value of the input always needs to match the value of the previous transaction output. If you previously received 1 bitcoin, and you want to spend 0.4 bitcoin, the transaction needs to spend the whole 1 bitcoin. 0.4 bitcoin will go as payment, then 0.6 bitcoin will return to you as change. Your Bitcoin wallet will handle this process automatically, but it is important to understand the principle in order to use it anonymously.
    The owner of the original bitcoin doesn't know whom you paid the money or what you did with it, but they can see the amounts and addresses involved. They can see two outputs of the transaction: one worth 0.4 bitcoin and one worth 0.6 bitcoin. They might not know for certain which is the purchase and which is the change, but they can apply heuristics to estimate it.
    Similarly, if you receive 0.5 bitcoin but want to spend 1 bitcoin, you need to own additional coins with a combined value of at least 0.5 bitcoin in them. When spending two coins within one transaction, it is often assumed that both of these coins belong to the same entity, this is the common input ownership heuristic.
     Why is it important to run a full node?
    TIP
    Not your node ~ not your rules
    ',27),p={href:"https://github.com/bitcoin/bitcoin",target:"_blank",rel:"noopener noreferrer"},y=e("h3",{id:"how-does-a-full-node-protect-my-privacy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-does-a-full-node-protect-my-privacy","aria-hidden":"true"},"#"),o(" How does a full node protect my privacy?")],-1),b={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},f=e("h3",{id:"how-can-i-set-up-a-full-node",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-can-i-set-up-a-full-node","aria-hidden":"true"},"#"),o(" How can I set up a full node?")],-1),m={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/libbitcoin/libbitcoin-node",target:"_blank",rel:"noopener noreferrer"},v=e("p",null,"Instead, if you prefer to use some dedicated hardware solutions, these are some of the most reliable projects:",-1),k={href:"https://github.com/rootzoll/raspiblitz",target:"_blank",rel:"noopener noreferrer"},_={href:"https://raspibolt.org/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://nixbitcoin.org/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://www.nodl.eu/",target:"_blank",rel:"noopener noreferrer"},x={href:"https://mynodebtc.com/",target:"_blank",rel:"noopener noreferrer"},I={href:"https://start9.com/",target:"_blank",rel:"noopener noreferrer"},W=e("h3",{id:"why-is-it-important-to-use-a-new-address-for-every-payment",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-is-it-important-to-use-a-new-address-for-every-payment","aria-hidden":"true"},"#"),o(" Why is it important to use a new address for every payment?")],-1),A=e("p",null,"Addresses being used more than once is very damaging to privacy because that links together more blockchain transactions with proof that they were created by the same entity. The most private and secure way to use bitcoin is to send a brand new address to each person who pays you. After an address has received a coin, it should never be used again. Also, a brand new bitcoin address should be demanded from the recipient when sending bitcoin. Wasabi has a user interface which discourages address reuse by removing from the GUI addresses which have received a coin.",-1),j=e("p",null,'It has been argued that the phrase "bitcoin address" was a bad name for this object because it implies it can be reused like an email address. A better name would be something like "bitcoin invoice".',-1),F=e("p",null,"Bitcoin isn't anonymous but pseudonymous, and the pseudonyms are bitcoin addresses. Avoiding address reuse is like throwing away a pseudonym after it has been used.",-1),S=e("h3",{id:"what-is-a-coinjoin-sudoku",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-is-a-coinjoin-sudoku","aria-hidden":"true"},"#"),o(" What is a coinjoin Sudoku?")],-1),C={href:"https://www.coinjoinsudoku.com/advisory/",target:"_blank",rel:"noopener noreferrer"},D=n('
     The Privacy of Tor
     How does Tor protect my network-level privacy?
    When you make a Bitcoin transaction, you are essentially creating a message on your phone or computer and sending it to the Bitcoin network. Someone operating a large number of nodes on the Bitcoin network might be able to match some of your transactions to your IP address, then deanonymize your stack of bitcoin.
    It is relatively easy to avoid this on a computer by relaying all transactions through the Tor network. Wasabi routes all traffic via Tor’s SOCKS5 proxy, by default.
    To maintain your anonymity, use the Tor Browser or the Tails operating system, if possible. Route everything through Tor by default.
    It is also good practice to route your chats through the Tor network. You can also configure many cloud storage providers in this way.
     Why does Tor process keep running after closing Wasabi Wallet?
    There are two main reasons: user experience and privacy.
    If a user closes Wasabi and then starts it again, he's already connected to Tor and he does not need to build a new Tor circuit. This means that Wasabi's startup will be much faster, because the Tor circuit is already established.
    Regarding the privacy, this is done to avoid time correlation attacks when using Wasabi Wallet. In fact, if a user creates a new Tor circuit every time he opens Wasabi Wallet, he would send a series of information to the Bitcoin network, which could allow a correlation and deanonymization of the user himself.
     My country/ISP is blocking/censoring Tor, how can I use Wasabi with Tor bridges?
    WARNING
    Feature not yet ported to Wasabi 2.0
    ',12),P={href:"https://www.torproject.org/docs/bridges",target:"_blank",rel:"noopener noreferrer"},N=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,"If you are using Tor Browser Bundle it is extremely easy to configure it to use bridges. Configuring Tor bridges running in a daemon mode is more difficult and takes more time.")],-1),R=e("p",null,[e("strong",null,"Steps with Tor Browser:")],-1),E={href:"https://www.torproject.org/",target:"_blank",rel:"noopener noreferrer"},H=n("
  • Change the Settings of the Tor Browser to use one of the bridges or pluggable transports
  • Leave Tor Browser running after connecting with a bridge
  • Change the Settings of Wasabi Wallet and edit TorSocks5 Endpoint from 127.0.0.1:9050 to 127.0.0.1:9150
  • Restart Wasabi
    • ",4),Y=e("p",null,"After this, Wasabi will connect to Tor using the Tor Browser's connection via a random bridge.",-1),z=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"WARNING"),e("p",null,"To make use of Tor bridges on Wasabi, you must always keep Tor Browser open.")],-1),G=e("p",null,[e("strong",null,"Steps with Tor Daemon on Linux:")],-1),L=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,"These are commands for Debian. Feel free to edit these commands according to your distribution.")],-1),O={href:"https://bridges.torproject.org/bridges",target:"_blank",rel:"noopener noreferrer"},K=e("li",null,[o("Install Tor daemon with "),e("code",null,"sudo apt-get install tor")],-1),U=e("li",null,[o("Install OBFS4 support (needed to connect to bridges), by editing your "),e("code",null,"/etc/apt/sources.list"),o(" and adding this line:")],-1),V=n(`
    # Tor Bridges
 deb http://deb.torproject.org/torproject.org obfs4proxy main
 
    1. Update package list with sudo apt-get update and install OBFS4 with sudo apt-get install obfs4proxy
    2. Configure Tor by editing your /etc/tor/torrc file and adding these lines:
    UseBridges 1
 
diff --git a/assets/FAQ-Installation.html.0c83c076.js b/assets/FAQ-Installation.html.6cf698ef.js
similarity index 99%
rename from assets/FAQ-Installation.html.0c83c076.js
rename to assets/FAQ-Installation.html.6cf698ef.js
index dcdc32689c..ac2c166076 100644
--- a/assets/FAQ-Installation.html.0c83c076.js
+++ b/assets/FAQ-Installation.html.6cf698ef.js
@@ -1 +1 @@
-import{_ as s}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,a as h,b as c,c as u,d as b}from"./DownloadMac.90ece9d0.js";import{_ as w,r as l,o as p,c as f,a,b as e,d as t,w as i,e as r}from"./app.a5b7c2b2.js";const g="/UpdateAvailable.png",_={},m=r('
     Installation of Wasabi
     Installing the Package
     Where can I download Wasabi?
    ',3),y={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},k={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/zksnacks/walletwasabi/releases",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/zksnacks/walletwasabi",target:"_blank",rel:"noopener noreferrer"},x={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},P=a("h3",{id:"why-is-it-important-to-verify-pgp-signatures",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#why-is-it-important-to-verify-pgp-signatures","aria-hidden":"true"},"#"),e(" Why is it important to verify PGP signatures?")],-1),A=a("div",{class:"custom-container danger"},[a("p",{class:"custom-container-title"},"DANGER"),a("p",null,[a("strong",null,"Don't trust ~ verify.")])],-1),I=a("p",null,[e("These are not just empty words. Self sovereignty is at the core of Bitcoin in general, and Wasabi specifically. You have powerful tools at your disposal, yet they only work when used as they are designed. Wasabi is tailor made so that you do "),a("strong",null,"not"),e(" have to trust anyone, but you have the power to verify everything.")],-1),S={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},z={href:"https://pgp.key-server.io/search/zksnacks",target:"_blank",rel:"noopener noreferrer"},D={href:"https://en.wikipedia.org/wiki/Web_of_trust",target:"_blank",rel:"noopener noreferrer"},N={href:"https://youtu.be/psl35MisYxo?list=PLPj3KCksGbSZkVpgAZjAFfFp4D0SHLnFw",target:"_blank",rel:"noopener noreferrer"},C=a("img",{src:s,alt:"Watch the video"},null,-1),F=a("h3",{id:"how-can-i-verify-pgp-signatures",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-can-i-verify-pgp-signatures","aria-hidden":"true"},"#"),e(" How can I verify PGP signatures?")],-1),G={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},B=a("code",null,".asc",-1),K=a("code",null,"gpg --verify",-1),j=a("p",null,[e("Everything is valid if it returns "),a("code",null,"Good signature from zkSNACKs"),e(" and that it was signed with the "),a("code",null,"Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),e(".")],-1),H={href:"https://youtu.be/mTrClVA_o5A",target:"_blank",rel:"noopener noreferrer"},L=a("img",{src:s,alt:"Watch the video"},null,-1),O=a("h3",{id:"how-do-i-install-wasabi-on-debian-and-ubuntu",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-debian-and-ubuntu","aria-hidden":"true"},"#"),e(" How do I install Wasabi on Debian and Ubuntu?")],-1),E=a("code",null,".deb",-1),U=a("code",null,".deb.asc",-1),Q={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},V={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},X=a("p",null,[a("img",{src:d,alt:"Download Wasabi Wallet for Debian",title:"Download Wasabi Wallet for Debian"})],-1),Y=a("code",null,"gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb",-1),q={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},M=a("code",null,"sudo apt install ./Wasabi-2.0.5.deb",-1),R=a("code",null,"wassabee",-1),Z={href:"https://youtu.be/mTrClVA_o5A?t=122",target:"_blank",rel:"noopener noreferrer"},J=a("img",{src:s,alt:"Watch the video"},null,-1),$=a("h3",{id:"how-do-i-install-wasabi-on-other-linux",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-other-linux","aria-hidden":"true"},"#"),e(" How do I install Wasabi on other Linux?")],-1),ee=a("code",null,".tar.gz",-1),ae=a("code",null,".tar.gz.asc",-1),te={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},oe={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},ne=a("p",null,[a("img",{src:h,alt:"Download Wasabi Wallet for Linux",title:"Download Wasabi Wallet for Linux"})],-1),ie=a("code",null,"gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz",-1),se={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},re=a("code",null,"sudo tar -pxzf Wasabi-2.0.5.tar.gz",-1),le=a("code",null,"./wassabee",-1),de=a("h3",{id:"how-do-i-install-wasabi-on-windows",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-windows","aria-hidden":"true"},"#"),e(" How do I install Wasabi on Windows?")],-1),he=a("code",null,".msi",-1),ce=a("code",null,".msi.asc",-1),ue={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},be={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},we=a("p",null,[a("img",{src:c,alt:"Download Wasabi Wallet for Windows",title:"Download Wasabi Wallet for Windows"})],-1),pe=a("p",null,"The Wasabi package is signed and automatically verified on Windows upon installation.",-1),fe=a("p",null,[a("img",{src:u,alt:"Wasabi Wallet Windows signature verification",title:"Wasabi Wallet Windows signature verification"})],-1),ge=a("code",null,"right-clicking on the signature file > More GpgEX options > Verify",-1),_e={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},me=a("code",null,".msi",-1),ye=a("h3",{id:"how-do-i-install-wasabi-on-macos",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-macos","aria-hidden":"true"},"#"),e(" How do I install Wasabi on macOS?")],-1),ke=a("code",null,".dmg",-1),ve=a("code",null,".dmg.asc",-1),We={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},xe={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},Pe=a("p",null,[a("img",{src:b,alt:"Download Wasabi Wallet for macOS",title:"Download Wasabi Wallet for macOS"})],-1),Ae=a("p",null,"The Wasabi package is signed and automatically verified on macOS upon installation.",-1),Ie=a("code",null,"sudo gpg2 --verify Wasabi-2.0.5.dmg.asc",-1),Se={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},Te=a("code",null,".dmg",-1),ze={href:"https://youtu.be/_Zmc54XYzBA",target:"_blank",rel:"noopener noreferrer"},De=a("img",{src:s,alt:"Watch the video"},null,-1),Ne=r('
     Why are there two different packages for macOS (intel and Apple Silicon)?
    Intel and Apple Silicon are two different processors types that Apple uses for their computers. These processors work a bit differently from each other. With the architecture that Wasabi uses, these two different processors need their own specific code binary in order to make it work.
     What happens when I install the wrong package for macOS?
    Wasabi will crash on startup or run significantly slower than it should. This will not harm your computer.
     Do I need to install Tor separately?
    No, because Wasabi has Tor built into the software. All Wasabi network traffic goes via Tor by default - no need to set up Tor yourself.
    You can turn off Tor in the Settings. Be careful, as this will compromise your privacy. When you coinjoin over clearnet, the coordinator would know the links between your inputs and outputs based on your IP address. When you broadcast a transaction over clearnet, the connected full node will know the link between your transaction and your IP address.
     Can I use Wasabi on Tails?
    No, it is not possible to install Wasabi on Tails, because Wasabi uses the Tor control port, which is not exposed in this operating system.
     Can I use Wasabi on Whonix?
    No, it is not possible to install Wasabi on Whonix, because Wasabi uses the Tor control port, which is not exposed in this operating system.
     What are the differences between the Debian/Ubuntu version and the "Other Linux" version?
    Debian/Ubuntu version contains .deb package. Other Linux version contains .tar.gz package.
    The advantages of the .deb format is solely packaging related. It installs Wasabi in your computer, so you're able to access it from start menu, remove it through apt, and so on.
    The "Other Linux" option is just a generic install method not targeted to Debian/Ubuntu specifically but that works on it anyway because it is still linux.
    There's no difference in the code, the same binaries are being delivered in different formats.
     Update Wasabi
     Why should I update Wasabi?
    Wasabi is cutting edge software and is being worked on by the developers on a daily basis. Once in a while (+- every month) all the changes/improvements are being released in a new Wasabi version. The changes can contain (critical) bug fixes, small improvements, new features etc. It's always a good idea to run (one of) the latest Wasabi versions.
     How do I check the current version of Wasabi?
    In the GUI, go to the SearchBar at the top of the screen and click on About Wasabi. Here the current version of your Wasabi is displayed. Wasabi is cutting edge software, so it is well-advised to stay up-to-date.
     How do I know about a new version of Wasabi?
    When a new major version [v2.X.X] has been released, you'll see an orange update icon in the bottom right, upon hovering over it you can see Version 2.X.X is now available.
    Wasabi Update Available
    ',24),Ce=a("code",null,"Update",-1),Fe={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},Ge={href:"https://twitter.com/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},Be={href:"https://reddit.com/r/WasabiWallet/",target:"_blank",rel:"noopener noreferrer"},Ke=a("h3",{id:"how-do-i-securely-upgrade-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-securely-upgrade-wasabi","aria-hidden":"true"},"#"),e(" How do I securely upgrade Wasabi?")],-1),je=a("p",null,"To upgrade Wasabi, you need to download the new version. Downloading and installing the newer Wasabi package will overwrite the previous one, while preserving your files like your wallets etc. So to upgrade Wasabi, simply download and install the new version like at first install.",-1),He={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},Le={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},Oe={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},Ee={href:"https://youtu.be/DUc9A76rwX4",target:"_blank",rel:"noopener noreferrer"},Ue=a("img",{src:s,alt:"Watch the video"},null,-1),Qe=r('
     What does Auto download new version in the settings mean?
    If enabled, the software will automatically download the new version's installer upon a new release. If disabled, the software will only signal, but not automatically download, that there is a new version available.
    Auto download new version is currently only available for Windows and macOS
    For Linux, this setting does not work. A new version will have to be installed manually.
     How does the Auto download new version work?
    ',4),Ve={href:"https://github.com/zkSNACKs/WalletWasabi/",target:"_blank",rel:"noopener noreferrer"},Xe=a("h2",{id:"advanced-installation",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-installation","aria-hidden":"true"},"#"),e(" Advanced Installation")],-1),Ye=a("h3",{id:"how-do-i-compile-wasabi-from-source",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-compile-wasabi-from-source","aria-hidden":"true"},"#"),e(" How do I compile Wasabi from source?")],-1),qe={href:"https://git-scm.com/downloads",target:"_blank",rel:"noopener noreferrer"},Me={href:"https://dotnet.microsoft.com/download",target:"_blank",rel:"noopener noreferrer"},Re=a("code",null,"git clone https://github.com/zkSNACKs/WalletWasabi.git",-1),Ze=a("code",null,"WalletWasabi",-1),Je=a("code",null,"cd WalletWasabi/WalletWasabi.Fluent.Desktop",-1),$e=a("code",null,"dotnet run",-1),ea=a("code",null,"WalletWasabi.Fluent.Desktop",-1),aa=a("code",null,"git pull",-1),ta=a("h3",{id:"how-can-i-verify-the-deterministic-build",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-can-i-verify-the-deterministic-build","aria-hidden":"true"},"#"),e(" How can I verify the deterministic build?")],-1),oa={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Guides/DeterministicBuildGuide.md",target:"_blank",rel:"noopener noreferrer"},na=a("h3",{id:"my-antivirus-marks-wasabi-wallet-as-a-virus-am-i-downloading-the-right-software",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#my-antivirus-marks-wasabi-wallet-as-a-virus-am-i-downloading-the-right-software","aria-hidden":"true"},"#"),e(" My antivirus marks Wasabi Wallet as a virus. Am I downloading the right software?")],-1),ia={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},sa={href:"https://github.com/zkSNACKs/WalletWasabi/releases",target:"_blank",rel:"noopener noreferrer"},ra=a("p",null,"If you have downloaded and verified digital signatures and your antivirus continues to report Wasabi as positive, you don't have to worry about anything; it is a false positive.",-1),la={href:"https://www.virustotal.com/",target:"_blank",rel:"noopener noreferrer"},da=r('
    TIP
    Remember to report Wasabi as a safe software/false positive to your antivirus. In doing so you will help users who use the same antivirus.
     Why is the executable called wassabee?
    The most obvious thing would be to call the executable Wasabi Wallet.exe on Windows and Wasabi Wallet on Linux and Mac.
    However launching Wasabi Wallet from certain terminals/command lines is problematic, so we should remove the spacing: WasabiWallet, and the case sensitivity differences between the operating systems can also cause issues, so that must go too: wasabiwallet.
    But it's too long, it needs a faster way to launch: wasabi.
    However this is too generic, it'll certainly cause conflicts, we need to make it unique: wassabee.
    ',6),ha={href:"https://www.youtube.com/watch?v=dLzFKx6ONZQ",target:"_blank",rel:"noopener noreferrer"};function ca(ua,ba){const o=l("ExternalLinkIcon"),n=l("RouterLink");return p(),f("div",null,[m,a("p",null,[e("You can find the recent version of the compiled packages for Linux, Windows and Mac available on the official "),a("a",y,[e("wasabiwallet.io"),t(o)]),e(". It's always best to download software directly from the official source acknowledged by the developers. In order to preserve your network level privacy from the very first step on, please consider visiting the Tor onion service "),a("a",k,[e("wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),t(o)]),e(". The old versions of the software can be found in the "),a("a",v,[e("releases"),t(o)]),e(" of the GitHub repository, "),a("a",W,[e("here"),t(o)]),e(" you also find the libre & open source code for when you want to "),t(n,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[e("build it yourself")]),_:1}),e(". Please take special care to verify the PGP signatures of zkSNACKs' PGP public key "),a("a",x,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(" over the software packages and code commits.")]),P,A,I,a("p",null,[e("With PGP signatures you can verify that the software package you download is actually the one by the developers. Every release of Wasabi is signed by "),a("a",S,[e("zkSNACKs"),t(o)]),e(", the company behind Wasabi. You can verify that the PGP public key "),a("a",T,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(" is actually the one of "),a("a",z,[e("zkSNACKs"),t(o)]),e(" by exploring the "),a("a",D,[e("web of trust"),t(o)]),e(". When you have a software package that was signed by this PGP public key, then you can be sure that this is an official release approved by zkSNACKs. This protects you against malicious man in the middle attacks where bad guys give you a fake version of Wasabi with malicious code.")]),a("p",null,[a("a",N,[C,t(o)])]),F,a("p",null,[e("On the "),a("a",G,[e("WasabiWallet.io"),t(o)]),e(" website you can download the packages of the latest release. To verify the signature you also need to download the separate signature "),B,e(" file. In the terminal, change the directory to the one with the downloaded files, and verify the signature with "),K,e(" + the corresponding signature file name, depending on which operating system you are.")]),j,a("p",null,[e("For an in-depth guide for "),t(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:i(()=>[e("Debian and Ubuntu")]),_:1}),e(", "),t(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:i(()=>[e("other Linux")]),_:1}),e(", "),t(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:i(()=>[e("Windows")]),_:1}),e(", and "),t(n,{to:"/using-wasabi/InstallPackage.html#macOS"},{default:i(()=>[e("macOS")]),_:1}),e(" see the main documentation.")]),a("p",null,[a("a",H,[L,t(o)])]),O,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),E,e(" package and the "),U,e(" signature file from the "),a("a",Q,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",V,[e("Tor onion service"),t(o)]),e(".")]),X,a("p",null,[e("Verify the signature of the package with "),Y,e(" and ensure that the software was signed by zkSNACKs' PGP public key "),a("a",q,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(".")]),a("p",null,[e("Now install Wasabi with "),M,e(", and run it with "),R,e(". Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),a("p",null,[a("a",Z,[J,t(o)])]),$,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),ee,e(" package and the "),ae,e(" signature file from the "),a("a",te,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",oe,[e("Tor onion service"),t(o)]),e(".")]),ne,a("p",null,[e("Verify the signature of the package with "),ie,e(" and ensure that the software was signed by zkSNACKs' PGP public key "),a("a",se,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi with "),re,e(", and run it with "),le,e(". Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),de,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),he,e(" package and the "),ce,e(" signature file from the "),a("a",ue,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",be,[e("Tor onion service"),t(o)]),e(".")]),we,pe,fe,a("p",null,[e("Optionally, you can still verify the PGP signature of the package by "),ge,e(" and ensure the software was signed by zkSNACKs' PGP public key "),a("a",_e,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi by double-clicking the "),me,e(" file. Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),ye,a("p",null,[t(n,{to:"/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),ke,e(" package and the "),ve,e(" signature file from the "),a("a",We,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",xe,[e("Tor onion service"),t(o)]),e(".")]),Pe,Ae,a("p",null,[e("Optionally, you can still verify the PGP signature of the package with "),Ie,e(" and ensure that the software has been signed by zkSNACKs' PGP public key "),a("a",Se,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi by double-clicking the "),Te,e(" file. Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),a("p",null,[a("a",ze,[De,t(o)])]),Ne,a("p",null,[e("Clicking on "),Ce,e(" uses the default browser to go to the website, where you can download this new version. There are occasional silent releases like [v2.X.X.X] which fix small issues, and these are not announced in the GUI, so you will not see the orange update icon. The "),a("a",Fe,[e("website"),t(o)]),e(" always contains the most recent version. All releases (major and minor) are announced on the social media like "),a("a",Ge,[e("Twitter"),t(o)]),e(" and "),a("a",Be,[e("Reddit"),t(o)]),e(".")]),Ke,je,a("p",null,[e("You can download the software build for the different operating systems on the main "),a("a",He,[e("website"),t(o)]),e(" or better over "),a("a",Le,[e("Tor"),t(o)]),e(". For extra security, it is reccommended to also download the signatures of the build and verify them with "),a("a",Oe,[e("zkSNACKs' PGP public key"),t(o)]),e(". For step-by-step instructions, follow "),t(n,{to:"/using-wasabi/InstallPackage.html"},{default:i(()=>[e("this guide")]),_:1}),e(" or see this video: "),a("a",Ee,[Ue,t(o)])]),Qe,a("p",null,[e(`The software will automatically download the new version's installer upon a new release. After it is downloaded, the user can press "Update on Close" to run the installer when closing Wasabi. The installer is downloaded from `),a("a",Ve,[e("GitHub"),t(o)]),e(".")]),Xe,Ye,a("p",null,[e("If you cannot wait until the next release, and you want to experience the most cutting-edge version of Wasabi, then you can "),t(n,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[e("build the source code")]),_:1}),e(".")]),a("p",null,[e("The only two required tools are "),a("a",qe,[e("Git"),t(o)]),e(" and "),a("a",Me,[e(".NET 7.0 SDK"),t(o)]),e(' for "Build apps". You can download every line of the Wasabi code by '),Re,e(", this will create a new directory called "),Ze,e(". In order to build and run the Wallet software, change directory to "),Je,e(". Wasabi is written in C# with the .NET framework, and it is very easy to run it. Simply execute "),$e,e(" from the "),ea,e(" folder. You can update the master branch with "),aa,e(".")]),ta,a("p",null,[e("The guide for the deterministic builds can be found in the "),a("a",oa,[e("WalletWasabi repository"),t(o)]),e(".")]),na,a("p",null,[e("After you have downloaded Wasabi from the "),a("a",ia,[e("official website"),t(o)]),e(" or from the "),a("a",sa,[e("official GitHub repository"),t(o)]),e(", make sure you have "),t(n,{to:"/FAQ/FAQ-Installation.html#how-can-i-verify-pgp-signatures"},{default:i(()=>[e("verified the PGP signatures")]),_:1}),e(".")]),ra,a("p",null,[e("If you are still not sure, before starting Wasabi, you can check that it is safe by uploading and scan it via "),a("a",la,[e("VirusTotal"),t(o)]),e(".")]),da,a("p",null,[e("Also, this sounds awesome and is a "),a("a",ha,[e("fun inside joke"),t(o)]),e(".")])])}const ga=w(_,[["render",ca],["__file","FAQ-Installation.html.vue"]]);export{ga as default};
+import{_ as s}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,a as h,b as c,c as u,d as b}from"./DownloadMac.90ece9d0.js";import{_ as w,r as l,o as p,c as f,a,b as e,d as t,w as i,e as r}from"./app.65e5b6fd.js";const g="/UpdateAvailable.png",_={},m=r('
     Installation of Wasabi
     Installing the Package
     Where can I download Wasabi?
    ',3),y={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},k={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/zksnacks/walletwasabi/releases",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/zksnacks/walletwasabi",target:"_blank",rel:"noopener noreferrer"},x={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},P=a("h3",{id:"why-is-it-important-to-verify-pgp-signatures",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#why-is-it-important-to-verify-pgp-signatures","aria-hidden":"true"},"#"),e(" Why is it important to verify PGP signatures?")],-1),A=a("div",{class:"custom-container danger"},[a("p",{class:"custom-container-title"},"DANGER"),a("p",null,[a("strong",null,"Don't trust ~ verify.")])],-1),I=a("p",null,[e("These are not just empty words. Self sovereignty is at the core of Bitcoin in general, and Wasabi specifically. You have powerful tools at your disposal, yet they only work when used as they are designed. Wasabi is tailor made so that you do "),a("strong",null,"not"),e(" have to trust anyone, but you have the power to verify everything.")],-1),S={href:"https://zksnacks.com/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},z={href:"https://pgp.key-server.io/search/zksnacks",target:"_blank",rel:"noopener noreferrer"},D={href:"https://en.wikipedia.org/wiki/Web_of_trust",target:"_blank",rel:"noopener noreferrer"},N={href:"https://youtu.be/psl35MisYxo?list=PLPj3KCksGbSZkVpgAZjAFfFp4D0SHLnFw",target:"_blank",rel:"noopener noreferrer"},C=a("img",{src:s,alt:"Watch the video"},null,-1),F=a("h3",{id:"how-can-i-verify-pgp-signatures",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-can-i-verify-pgp-signatures","aria-hidden":"true"},"#"),e(" How can I verify PGP signatures?")],-1),G={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},B=a("code",null,".asc",-1),K=a("code",null,"gpg --verify",-1),j=a("p",null,[e("Everything is valid if it returns "),a("code",null,"Good signature from zkSNACKs"),e(" and that it was signed with the "),a("code",null,"Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),e(".")],-1),H={href:"https://youtu.be/mTrClVA_o5A",target:"_blank",rel:"noopener noreferrer"},L=a("img",{src:s,alt:"Watch the video"},null,-1),O=a("h3",{id:"how-do-i-install-wasabi-on-debian-and-ubuntu",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-debian-and-ubuntu","aria-hidden":"true"},"#"),e(" How do I install Wasabi on Debian and Ubuntu?")],-1),E=a("code",null,".deb",-1),U=a("code",null,".deb.asc",-1),Q={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},V={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},X=a("p",null,[a("img",{src:d,alt:"Download Wasabi Wallet for Debian",title:"Download Wasabi Wallet for Debian"})],-1),Y=a("code",null,"gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb",-1),q={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},M=a("code",null,"sudo apt install ./Wasabi-2.0.5.deb",-1),R=a("code",null,"wassabee",-1),Z={href:"https://youtu.be/mTrClVA_o5A?t=122",target:"_blank",rel:"noopener noreferrer"},J=a("img",{src:s,alt:"Watch the video"},null,-1),$=a("h3",{id:"how-do-i-install-wasabi-on-other-linux",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-other-linux","aria-hidden":"true"},"#"),e(" How do I install Wasabi on other Linux?")],-1),ee=a("code",null,".tar.gz",-1),ae=a("code",null,".tar.gz.asc",-1),te={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},oe={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},ne=a("p",null,[a("img",{src:h,alt:"Download Wasabi Wallet for Linux",title:"Download Wasabi Wallet for Linux"})],-1),ie=a("code",null,"gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz",-1),se={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},re=a("code",null,"sudo tar -pxzf Wasabi-2.0.5.tar.gz",-1),le=a("code",null,"./wassabee",-1),de=a("h3",{id:"how-do-i-install-wasabi-on-windows",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-windows","aria-hidden":"true"},"#"),e(" How do I install Wasabi on Windows?")],-1),he=a("code",null,".msi",-1),ce=a("code",null,".msi.asc",-1),ue={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},be={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},we=a("p",null,[a("img",{src:c,alt:"Download Wasabi Wallet for Windows",title:"Download Wasabi Wallet for Windows"})],-1),pe=a("p",null,"The Wasabi package is signed and automatically verified on Windows upon installation.",-1),fe=a("p",null,[a("img",{src:u,alt:"Wasabi Wallet Windows signature verification",title:"Wasabi Wallet Windows signature verification"})],-1),ge=a("code",null,"right-clicking on the signature file > More GpgEX options > Verify",-1),_e={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},me=a("code",null,".msi",-1),ye=a("h3",{id:"how-do-i-install-wasabi-on-macos",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-install-wasabi-on-macos","aria-hidden":"true"},"#"),e(" How do I install Wasabi on macOS?")],-1),ke=a("code",null,".dmg",-1),ve=a("code",null,".dmg.asc",-1),We={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},xe={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},Pe=a("p",null,[a("img",{src:b,alt:"Download Wasabi Wallet for macOS",title:"Download Wasabi Wallet for macOS"})],-1),Ae=a("p",null,"The Wasabi package is signed and automatically verified on macOS upon installation.",-1),Ie=a("code",null,"sudo gpg2 --verify Wasabi-2.0.5.dmg.asc",-1),Se={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},Te=a("code",null,".dmg",-1),ze={href:"https://youtu.be/_Zmc54XYzBA",target:"_blank",rel:"noopener noreferrer"},De=a("img",{src:s,alt:"Watch the video"},null,-1),Ne=r('
     Why are there two different packages for macOS (intel and Apple Silicon)?
    Intel and Apple Silicon are two different processors types that Apple uses for their computers. These processors work a bit differently from each other. With the architecture that Wasabi uses, these two different processors need their own specific code binary in order to make it work.
     What happens when I install the wrong package for macOS?
    Wasabi will crash on startup or run significantly slower than it should. This will not harm your computer.
     Do I need to install Tor separately?
    No, because Wasabi has Tor built into the software. All Wasabi network traffic goes via Tor by default - no need to set up Tor yourself.
    You can turn off Tor in the Settings. Be careful, as this will compromise your privacy. When you coinjoin over clearnet, the coordinator would know the links between your inputs and outputs based on your IP address. When you broadcast a transaction over clearnet, the connected full node will know the link between your transaction and your IP address.
     Can I use Wasabi on Tails?
    No, it is not possible to install Wasabi on Tails, because Wasabi uses the Tor control port, which is not exposed in this operating system.
     Can I use Wasabi on Whonix?
    No, it is not possible to install Wasabi on Whonix, because Wasabi uses the Tor control port, which is not exposed in this operating system.
     What are the differences between the Debian/Ubuntu version and the "Other Linux" version?
    Debian/Ubuntu version contains .deb package. Other Linux version contains .tar.gz package.
    The advantages of the .deb format is solely packaging related. It installs Wasabi in your computer, so you're able to access it from start menu, remove it through apt, and so on.
    The "Other Linux" option is just a generic install method not targeted to Debian/Ubuntu specifically but that works on it anyway because it is still linux.
    There's no difference in the code, the same binaries are being delivered in different formats.
     Update Wasabi
     Why should I update Wasabi?
    Wasabi is cutting edge software and is being worked on by the developers on a daily basis. Once in a while (+- every month) all the changes/improvements are being released in a new Wasabi version. The changes can contain (critical) bug fixes, small improvements, new features etc. It's always a good idea to run (one of) the latest Wasabi versions.
     How do I check the current version of Wasabi?
    In the GUI, go to the SearchBar at the top of the screen and click on About Wasabi. Here the current version of your Wasabi is displayed. Wasabi is cutting edge software, so it is well-advised to stay up-to-date.
     How do I know about a new version of Wasabi?
    When a new major version [v2.X.X] has been released, you'll see an orange update icon in the bottom right, upon hovering over it you can see Version 2.X.X is now available.
    Wasabi Update Available
    ',24),Ce=a("code",null,"Update",-1),Fe={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},Ge={href:"https://twitter.com/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},Be={href:"https://reddit.com/r/WasabiWallet/",target:"_blank",rel:"noopener noreferrer"},Ke=a("h3",{id:"how-do-i-securely-upgrade-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-securely-upgrade-wasabi","aria-hidden":"true"},"#"),e(" How do I securely upgrade Wasabi?")],-1),je=a("p",null,"To upgrade Wasabi, you need to download the new version. Downloading and installing the newer Wasabi package will overwrite the previous one, while preserving your files like your wallets etc. So to upgrade Wasabi, simply download and install the new version like at first install.",-1),He={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},Le={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},Oe={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},Ee={href:"https://youtu.be/DUc9A76rwX4",target:"_blank",rel:"noopener noreferrer"},Ue=a("img",{src:s,alt:"Watch the video"},null,-1),Qe=r('
     What does Auto download new version in the settings mean?
    If enabled, the software will automatically download the new version's installer upon a new release. If disabled, the software will only signal, but not automatically download, that there is a new version available.
    Auto download new version is currently only available for Windows and macOS
    For Linux, this setting does not work. A new version will have to be installed manually.
     How does the Auto download new version work?
    ',4),Ve={href:"https://github.com/zkSNACKs/WalletWasabi/",target:"_blank",rel:"noopener noreferrer"},Xe=a("h2",{id:"advanced-installation",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-installation","aria-hidden":"true"},"#"),e(" Advanced Installation")],-1),Ye=a("h3",{id:"how-do-i-compile-wasabi-from-source",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-do-i-compile-wasabi-from-source","aria-hidden":"true"},"#"),e(" How do I compile Wasabi from source?")],-1),qe={href:"https://git-scm.com/downloads",target:"_blank",rel:"noopener noreferrer"},Me={href:"https://dotnet.microsoft.com/download",target:"_blank",rel:"noopener noreferrer"},Re=a("code",null,"git clone https://github.com/zkSNACKs/WalletWasabi.git",-1),Ze=a("code",null,"WalletWasabi",-1),Je=a("code",null,"cd WalletWasabi/WalletWasabi.Fluent.Desktop",-1),$e=a("code",null,"dotnet run",-1),ea=a("code",null,"WalletWasabi.Fluent.Desktop",-1),aa=a("code",null,"git pull",-1),ta=a("h3",{id:"how-can-i-verify-the-deterministic-build",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#how-can-i-verify-the-deterministic-build","aria-hidden":"true"},"#"),e(" How can I verify the deterministic build?")],-1),oa={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/Guides/DeterministicBuildGuide.md",target:"_blank",rel:"noopener noreferrer"},na=a("h3",{id:"my-antivirus-marks-wasabi-wallet-as-a-virus-am-i-downloading-the-right-software",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#my-antivirus-marks-wasabi-wallet-as-a-virus-am-i-downloading-the-right-software","aria-hidden":"true"},"#"),e(" My antivirus marks Wasabi Wallet as a virus. Am I downloading the right software?")],-1),ia={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},sa={href:"https://github.com/zkSNACKs/WalletWasabi/releases",target:"_blank",rel:"noopener noreferrer"},ra=a("p",null,"If you have downloaded and verified digital signatures and your antivirus continues to report Wasabi as positive, you don't have to worry about anything; it is a false positive.",-1),la={href:"https://www.virustotal.com/",target:"_blank",rel:"noopener noreferrer"},da=r('
    TIP
    Remember to report Wasabi as a safe software/false positive to your antivirus. In doing so you will help users who use the same antivirus.
     Why is the executable called wassabee?
    The most obvious thing would be to call the executable Wasabi Wallet.exe on Windows and Wasabi Wallet on Linux and Mac.
    However launching Wasabi Wallet from certain terminals/command lines is problematic, so we should remove the spacing: WasabiWallet, and the case sensitivity differences between the operating systems can also cause issues, so that must go too: wasabiwallet.
    But it's too long, it needs a faster way to launch: wasabi.
    However this is too generic, it'll certainly cause conflicts, we need to make it unique: wassabee.
    ',6),ha={href:"https://www.youtube.com/watch?v=dLzFKx6ONZQ",target:"_blank",rel:"noopener noreferrer"};function ca(ua,ba){const o=l("ExternalLinkIcon"),n=l("RouterLink");return p(),f("div",null,[m,a("p",null,[e("You can find the recent version of the compiled packages for Linux, Windows and Mac available on the official "),a("a",y,[e("wasabiwallet.io"),t(o)]),e(". It's always best to download software directly from the official source acknowledged by the developers. In order to preserve your network level privacy from the very first step on, please consider visiting the Tor onion service "),a("a",k,[e("wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),t(o)]),e(". The old versions of the software can be found in the "),a("a",v,[e("releases"),t(o)]),e(" of the GitHub repository, "),a("a",W,[e("here"),t(o)]),e(" you also find the libre & open source code for when you want to "),t(n,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[e("build it yourself")]),_:1}),e(". Please take special care to verify the PGP signatures of zkSNACKs' PGP public key "),a("a",x,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(" over the software packages and code commits.")]),P,A,I,a("p",null,[e("With PGP signatures you can verify that the software package you download is actually the one by the developers. Every release of Wasabi is signed by "),a("a",S,[e("zkSNACKs"),t(o)]),e(", the company behind Wasabi. You can verify that the PGP public key "),a("a",T,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(" is actually the one of "),a("a",z,[e("zkSNACKs"),t(o)]),e(" by exploring the "),a("a",D,[e("web of trust"),t(o)]),e(". When you have a software package that was signed by this PGP public key, then you can be sure that this is an official release approved by zkSNACKs. This protects you against malicious man in the middle attacks where bad guys give you a fake version of Wasabi with malicious code.")]),a("p",null,[a("a",N,[C,t(o)])]),F,a("p",null,[e("On the "),a("a",G,[e("WasabiWallet.io"),t(o)]),e(" website you can download the packages of the latest release. To verify the signature you also need to download the separate signature "),B,e(" file. In the terminal, change the directory to the one with the downloaded files, and verify the signature with "),K,e(" + the corresponding signature file name, depending on which operating system you are.")]),j,a("p",null,[e("For an in-depth guide for "),t(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:i(()=>[e("Debian and Ubuntu")]),_:1}),e(", "),t(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:i(()=>[e("other Linux")]),_:1}),e(", "),t(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:i(()=>[e("Windows")]),_:1}),e(", and "),t(n,{to:"/using-wasabi/InstallPackage.html#macOS"},{default:i(()=>[e("macOS")]),_:1}),e(" see the main documentation.")]),a("p",null,[a("a",H,[L,t(o)])]),O,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),E,e(" package and the "),U,e(" signature file from the "),a("a",Q,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",V,[e("Tor onion service"),t(o)]),e(".")]),X,a("p",null,[e("Verify the signature of the package with "),Y,e(" and ensure that the software was signed by zkSNACKs' PGP public key "),a("a",q,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(".")]),a("p",null,[e("Now install Wasabi with "),M,e(", and run it with "),R,e(". Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),a("p",null,[a("a",Z,[J,t(o)])]),$,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),ee,e(" package and the "),ae,e(" signature file from the "),a("a",te,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",oe,[e("Tor onion service"),t(o)]),e(".")]),ne,a("p",null,[e("Verify the signature of the package with "),ie,e(" and ensure that the software was signed by zkSNACKs' PGP public key "),a("a",se,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi with "),re,e(", and run it with "),le,e(". Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),de,a("p",null,[t(n,{to:"/FAQ/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),he,e(" package and the "),ce,e(" signature file from the "),a("a",ue,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",be,[e("Tor onion service"),t(o)]),e(".")]),we,pe,fe,a("p",null,[e("Optionally, you can still verify the PGP signature of the package by "),ge,e(" and ensure the software was signed by zkSNACKs' PGP public key "),a("a",_e,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi by double-clicking the "),me,e(" file. Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),ye,a("p",null,[t(n,{to:"/FAQ-Installation.html#where-can-i-download-wasabi"},{default:i(()=>[e("Download")]),_:1}),e(" the most recent "),ke,e(" package and the "),ve,e(" signature file from the "),a("a",We,[e("wasabiwallet.io"),t(o)]),e(" or the "),a("a",xe,[e("Tor onion service"),t(o)]),e(".")]),Pe,Ae,a("p",null,[e("Optionally, you can still verify the PGP signature of the package with "),Ie,e(" and ensure that the software has been signed by zkSNACKs' PGP public key "),a("a",Se,[e("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(o)]),e(". Now install Wasabi by double-clicking the "),Te,e(" file. Check out the main documentation for a "),t(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:i(()=>[e("step-by-step guide")]),_:1}),e(".")]),a("p",null,[a("a",ze,[De,t(o)])]),Ne,a("p",null,[e("Clicking on "),Ce,e(" uses the default browser to go to the website, where you can download this new version. There are occasional silent releases like [v2.X.X.X] which fix small issues, and these are not announced in the GUI, so you will not see the orange update icon. The "),a("a",Fe,[e("website"),t(o)]),e(" always contains the most recent version. All releases (major and minor) are announced on the social media like "),a("a",Ge,[e("Twitter"),t(o)]),e(" and "),a("a",Be,[e("Reddit"),t(o)]),e(".")]),Ke,je,a("p",null,[e("You can download the software build for the different operating systems on the main "),a("a",He,[e("website"),t(o)]),e(" or better over "),a("a",Le,[e("Tor"),t(o)]),e(". For extra security, it is reccommended to also download the signatures of the build and verify them with "),a("a",Oe,[e("zkSNACKs' PGP public key"),t(o)]),e(". For step-by-step instructions, follow "),t(n,{to:"/using-wasabi/InstallPackage.html"},{default:i(()=>[e("this guide")]),_:1}),e(" or see this video: "),a("a",Ee,[Ue,t(o)])]),Qe,a("p",null,[e(`The software will automatically download the new version's installer upon a new release. After it is downloaded, the user can press "Update on Close" to run the installer when closing Wasabi. The installer is downloaded from `),a("a",Ve,[e("GitHub"),t(o)]),e(".")]),Xe,Ye,a("p",null,[e("If you cannot wait until the next release, and you want to experience the most cutting-edge version of Wasabi, then you can "),t(n,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[e("build the source code")]),_:1}),e(".")]),a("p",null,[e("The only two required tools are "),a("a",qe,[e("Git"),t(o)]),e(" and "),a("a",Me,[e(".NET 8.0 SDK"),t(o)]),e(' for "Build apps". You can download every line of the Wasabi code by '),Re,e(", this will create a new directory called "),Ze,e(". In order to build and run the Wallet software, change directory to "),Je,e(". Wasabi is written in C# with the .NET framework, and it is very easy to run it. Simply execute "),$e,e(" from the "),ea,e(" folder. You can update the master branch with "),aa,e(".")]),ta,a("p",null,[e("The guide for the deterministic builds can be found in the "),a("a",oa,[e("WalletWasabi repository"),t(o)]),e(".")]),na,a("p",null,[e("After you have downloaded Wasabi from the "),a("a",ia,[e("official website"),t(o)]),e(" or from the "),a("a",sa,[e("official GitHub repository"),t(o)]),e(", make sure you have "),t(n,{to:"/FAQ/FAQ-Installation.html#how-can-i-verify-pgp-signatures"},{default:i(()=>[e("verified the PGP signatures")]),_:1}),e(".")]),ra,a("p",null,[e("If you are still not sure, before starting Wasabi, you can check that it is safe by uploading and scan it via "),a("a",la,[e("VirusTotal"),t(o)]),e(".")]),da,a("p",null,[e("Also, this sounds awesome and is a "),a("a",ha,[e("fun inside joke"),t(o)]),e(".")])])}const ga=w(_,[["render",ca],["__file","FAQ-Installation.html.vue"]]);export{ga as default};
diff --git a/assets/FAQ-Introduction.html.e96f1243.js b/assets/FAQ-Introduction.html.ecbd8a2f.js
similarity index 99%
rename from assets/FAQ-Introduction.html.e96f1243.js
rename to assets/FAQ-Introduction.html.ecbd8a2f.js
index f019877edb..4f3d08017f 100644
--- a/assets/FAQ-Introduction.html.e96f1243.js
+++ b/assets/FAQ-Introduction.html.ecbd8a2f.js
@@ -1 +1 @@
-import{_ as h}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as l,r,o as c,c as d,a as t,b as e,d as a,w as n,e as s}from"./app.a5b7c2b2.js";const u={},p=s('
     Introduction to Wasabi
     The Basics
     Who can use Wasabi?
    ',3),b={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Fluent.Desktop",target:"_blank",rel:"noopener noreferrer"},m={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Daemon",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Tests",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Packager",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},_={href:"https://wasabiwallet.io/swagger/",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/zkSNACKs/WasabiDoc",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/LICENSE.md",target:"_blank",rel:"noopener noreferrer"},v=t("p",null,"Wasabi is used by individuals to make everyday payments, to manage their hardware wallet long term hodlings, and to CoinJoin their sats for added privacy. Entrepreneurs may use Wasabi to defend their customers from spies and to ensure a private business relationship. While kids may use Wasabi to stack the sats gifted by grandma, and learn the importance of hodling.",-1),x=t("div",{class:"custom-container tip"},[t("p",{class:"custom-container-title"},"TIP"),t("p",null,"Wasabi is a tool for everyone.")],-1),T=t("h3",{id:"what-is-a-coinjoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-a-coinjoin","aria-hidden":"true"},"#"),e(" What is a coinjoin?")],-1),S=t("p",null,"Coinjoin is a mechanism by which multiple participants combine their coins (or UTXOs, to be more precise) into one large transaction with multiple inputs and multiple outputs. An observer cannot determine which output belongs to which input, and neither can the participants themselves. This makes it difficult for outside parties to trace where a particular coin originated from and where it was sent to (as opposed to regular bitcoin transactions, where there is usually one sender and one receiver).",-1),A=t("p",null,"This can be done with non-custodial software like Wasabi that eliminates the risk of funds disappearing or being stolen. Each of the signatures are created on the participants’ computers after thorough verification, so nobody can alter the transaction or redirect the funds. The funds will always be in a Bitcoin address that you control.",-1),C=t("p",null,"In very simple terms, coinjoin means: “when you want to make a transaction, find someone else who also wants to make a transaction and make a joint transaction together”.",-1),N={href:"https://en.bitcoin.it/wiki/CoinJoin",target:"_blank",rel:"noopener noreferrer"},z=t("h3",{id:"do-i-need-to-trust-wasabi-with-my-coins",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#do-i-need-to-trust-wasabi-with-my-coins","aria-hidden":"true"},"#"),e(" Do I need to trust Wasabi with my coins?")],-1),B=t("h3",{id:"what-is-the-privacy-i-get-after-mixing-with-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-the-privacy-i-get-after-mixing-with-wasabi","aria-hidden":"true"},"#"),e(" What is the privacy I get after mixing with Wasabi?")],-1),I=s('
     Why is Wasabi Bitcoin-only?
    There are countless reasons why it is the only logical choice to be bitcoin-only. With Bitcoin we have a once in a lifetime opportunity to manifest libre sound money. If we succeed, then an utmost beautiful agora of sovereign individuals may emerge. If we fail, then this will conjure up the most horrific Orwellian nightmare. There is no room for wasted time and energy, this great work requires our full attention. Any line of code written to support a random shitcoin takes away scarce developer time to work on real problems.
     What is considered a sufficient anonymity score?
    It is difficult to determine a sufficient anonymity score since enough research hasn’t been conducted to provide a definitive answer. The right anonymity score depends on your own personal threat model. However, to be on the safe side, with Wasabi Wallet 2.0 an anonymity score of 5 and above could be considered sufficient.
     Is there a way to check Wasabi's uptime status?
    ',5),j={href:"https://stats.uptimerobot.com/YQqGyUL8A7",target:"_blank",rel:"noopener noreferrer"},K=t("h3",{id:"what-software-supplies-the-block-filters-that-wasabi-uses",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-software-supplies-the-block-filters-that-wasabi-uses","aria-hidden":"true"},"#"),e(" What software supplies the block filters that Wasabi uses?")],-1),F={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},M=t("h3",{id:"is-the-backend-s-coordinator-code-open-source",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-the-backend-s-coordinator-code-open-source","aria-hidden":"true"},"#"),e(" Is the Backend's (Coordinator) code open-source?")],-1),O={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},E=t("h3",{id:"is-there-an-android-ios-version",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-there-an-android-ios-version","aria-hidden":"true"},"#"),e(" Is there an Android/iOs version?")],-1),Q=t("p",null,"No, Wasabi and CoinJoin features require considerable computational power, not currently replicable on a smartphone.",-1),q=t("h3",{id:"where-can-i-find-wasabi-wallet-on-social-media",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#where-can-i-find-wasabi-wallet-on-social-media","aria-hidden":"true"},"#"),e(" Where can I find Wasabi Wallet on social media?")],-1),Y={href:"https://twitter.com/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},D={href:"https://www.reddit.com/r/WasabiWallet/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://www.youtube.com/c/WasabiWallet",target:"_blank",rel:"noopener noreferrer"},U={href:"https://www.facebook.com/officialwasabiwallet/",target:"_blank",rel:"noopener noreferrer"},P={href:"https://www.instagram.com/wasabi_wallet/",target:"_blank",rel:"noopener noreferrer"},R={href:"https://discord.com/invite/nm7YHEZnJs",target:"_blank",rel:"noopener noreferrer"},H={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},J={href:"https://t.me/WasabiWallet",target:"_blank",rel:"noopener noreferrer"},V={href:"https://keybase.io/team/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},Z={href:"https://blog.wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},G=t("h2",{id:"for-advanced-wasabikas",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#for-advanced-wasabikas","aria-hidden":"true"},"#"),e(" For advanced Wasabikas")],-1),X=t("h3",{id:"can-the-coordinator-attack-me",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#can-the-coordinator-attack-me","aria-hidden":"true"},"#"),e(" Can the coordinator attack me?")],-1),$=t("p",null,"The developers have gone to great lengths to ensure that the coordinator cannot steal funds nor link inputs to outputs. The nature of Wasabi is that you should not need to trust the developers or the Wasabi coordinating server, as you can verify that the code does not leak information to anyone. Due to the nature of coinjoin transactions users don't need to trust other users or the coordinator against theft, leaving denial of service and attacks on privacy as the main concerns",-1),ee=t("p",null,[e("The only known possible 'malicious' actions that the server "),t("em",null,"could"),e(" perform are two sides of the same coin;")],-1),te=t("li",null,[t("strong",null,"Blacklisted UTXO's"),e(": Though this would not affect the users who are able to successfully mix with other 'honest/real' peers.")],-1),ae=t("strong",null,"Targeted Sybil Attack",-1),oe=t("em",null,"only",-1),ie=t("strong",null,"but does not worsen the existing privacy of the coin",-1),ne={href:"https://github.com/zkSNACKs/WabiSabi/blob/master/protocol.md#attacks-on-privacy",target:"_blank",rel:"noopener noreferrer"},se=t("h3",{id:"what-is-the-history-of-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-the-history-of-wasabi","aria-hidden":"true"},"#"),e(" What is the history of Wasabi?")],-1),re={href:"https://docs.google.com/drawings/d/1wLL7aSgYBWNoyzllg6_haisFt-gQCf-QUzVzQPkARts/edit",target:"_blank",rel:"noopener noreferrer"},he=t("ul",null,[t("li",null,"The 1.0 Beta release was on August 1, 2018 (on the first anniversary of UASF)"),t("li",null,"The 1.0 release was on October 31, 2018 (on the tenth anniversary of the Bitcoin Whitepaper)"),t("li",null,"The 2.0 Testnet release was on March 1, 2022"),t("li",null,"The 2.0 release was on June 15, 2022")],-1),le={href:"https://youtu.be/XORDEX-RrAI?t=6420",target:"_blank",rel:"noopener noreferrer"},ce=t("img",{src:h,alt:"Watch the video"},null,-1),de={href:"https://youtu.be/b1Vligm0SO8",target:"_blank",rel:"noopener noreferrer"},ue=t("img",{src:h,alt:"Watch the video"},null,-1),pe=t("h3",{id:"why-is-wasabi-libre-and-open-source-software",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#why-is-wasabi-libre-and-open-source-software","aria-hidden":"true"},"#"),e(" Why is Wasabi libre and open-source software?")],-1),be={href:"https://github.com/zkSNACKs/WalletWasabi/",target:"_blank",rel:"noopener noreferrer"},me={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/LICENSE.md",target:"_blank",rel:"noopener noreferrer"},fe=s('
    Control
    Many people prefer open-source software because they have more control over the software they run.
    They can examine the code to make sure it's not doing anything they don't want it to do, and they can change parts of it they don't like. Users who aren't programmers also benefit from open-source software, since they can use this software for any purpose.
    Training
    Other people like open-source software because it helps them become better programmers.
    Open-source code is publicly accessible. Students can easily study it as they learn to make better software. Students can also share their work with others, inviting comments and critique, as they develop their skills. When people discover mistakes in programs' source code, they can share those mistakes with others to help them avoid making those same mistakes themselves.
    Security
    Some people prefer open-source software because they consider it more secure and stable than proprietary software.
    Anyone can view and modify open-source software. Other users may spot and correct errors or omissions that a program's original authors might have missed. And because so many programmers can work on a piece of open-source software without asking for permission from original authors, they can fix, update, and upgrade open-source software more quickly than they can proprietary software.
    Stability
    Many users prefer open-source software to proprietary software for important, long-term projects.
    Programmers publicly distribute the source code for open-source software. Users relying on that software for critical tasks can be sure their tools won't disappear or fall into disrepair if their original creators stop working on them. Additionally, open-source software tends to both incorporate and operate according to open standards.
     What is the general idea of WabiSabi coinjoin?
    While fungibility is an essential property of good money, Bitcoin has its limitations in this area. Numerous fungibility improvements have been proposed; however, none of them have addressed the privacy issues in full. WabiSabi is designed so that no participant, outside observer or even the coordinator can spy on the user. The scope of WabiSabi is not limited to a single transaction, it extends to transaction chains and it addresses various network layer deanonymizations. However, its scope is limited to Bitcoin's first layer. Even if an off-chain anonymity solution gets widely adopted, ultimately the entrance and exit transactions will always be settled on-chain. Therefore, there will always be need for on-chain privacy.
    Ideal fungibility requires every Bitcoin transaction to be indistinguishable from each other, but it is an unrealistic goal. WabiSabi's objective is to break all links between coins. Thus, WabiSabi enables the usage of Bitcoin in a fully anonymous way.
    ',11),we={href:"https://github.com/zksnacks/wabisabi",target:"_blank",rel:"noopener noreferrer"},ye=t("h3",{id:"what-are-the-supported-operating-systems",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-are-the-supported-operating-systems","aria-hidden":"true"},"#"),e(" What are the supported operating systems?")],-1),ge={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems",target:"_blank",rel:"noopener noreferrer"},_e=t("h3",{id:"what-are-the-minimal-requirements-to-run-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-are-the-minimal-requirements-to-run-wasabi","aria-hidden":"true"},"#"),e(" What are the minimal requirements to run Wasabi?")],-1),ke={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems",target:"_blank",rel:"noopener noreferrer"},We={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Daemon",target:"_blank",rel:"noopener noreferrer"};function ve(xe,Te){const o=r("ExternalLinkIcon"),i=r("RouterLink");return c(),d("div",null,[p,t("p",null,[e("Every single line of code in Wasabi, the "),t("a",b,[e("wallet"),a(o)]),e(", the "),t("a",m,[e("backend server"),a(o)]),e(", the "),t("a",f,[e("daemon"),a(o)]),e(", the "),t("a",w,[e("tests"),a(o)]),e(", the "),t("a",y,[e("packager"),a(o)]),e(", the "),t("a",g,[e("library"),a(o)]),e(", the "),t("a",_,[e("api"),a(o)]),e(", the "),t("a",k,[e("documentation"),a(o)]),e(" - has always been and will always be libre and open-source under the "),t("a",W,[e("MIT license"),a(o)]),e(". This means that anyone, yes, ANYONE can use Wasabi without permission, for any use case, free of charge.")]),v,x,T,S,A,C,t("p",null,[e("See also the "),t("a",N,[e("Bitcoin Wiki on coinjoins"),a(o)])]),z,t("p",null,[e("Since Wasabi's coinjoin implementation is trustless by design, there is no need for participants to trust each other or a third party. Both the sending address (the coinjoin input) and the receiving address (the coinjoin output) are controlled by your own private keys. The Wasabi server merely coordinates the process of combining each participant's input into one single transaction, but the Wasabi Wallet can neither steal your coins, nor figure out which outputs belong to which inputs (look up “"),a(i,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[e("WabiSabi coinjoin")]),_:1}),e("” if you want to know more).")]),B,t("p",null,[e("This depends on how you handle your outputs after the coinjoin. There are some ways how you can unintentionally undo the mixing by being careless. For example, if you send a mixed coin to an already used address, then anyone can see that both coins are controlled by the same entity. More importantly, anyone who knows that the address belongs to you knows that you own that mixed coin. "),a(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[e("Address reuse")]),_:1}),e(" compromises your privacy. Another deanonymizing scenario occurs when you combine mixed outputs with unmixed ones when sending: a third party will be able to make the connection between them as belonging to the same sender. This is why you need to be careful with non-private/"),a(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[e("change coins")]),_:1}),e(".")]),t("p",null,[e("The practice of being careful with your post-mix outputs is commonly facilitated through coin control. Find out more about coin control in "),a(i,{to:"/why-wasabi/Coins.html"},{default:n(()=>[e("here")]),_:1}),e(". However, Wasabi Wallet is build in a way to help the user to avoid privacy leaks when using the wallet.")]),I,t("p",null,[e("Yes, you can check the status of Wasabi-related services and websites (like APIs, Backend, etc.) via "),t("a",j,[e("UptimeRobot Wasabi Status Page"),a(o)]),e(".")]),K,t("p",null,[e("The zkSNACKs coordinator supplies identical filters to every client. This means that you rely on the "),t("a",F,[e("Wasabi backend"),a(o)]),e(" to provide valid filters. But because you download the blocks from a random Bitcoin peer-to-peer node - or your own node - the coordinator cannot spy on which blocks you are interested in. Furthermore, the random node will only know which block is needed but it won't have any clue which transaction(s) belongs to the wallet.")]),M,t("p",null,[e("Yes, you can verify the code on "),t("a",O,[e("GitHub"),a(o)]),e(".")]),E,Q,q,t("p",null,[e("You can find us on "),t("a",Y,[e("Twitter"),a(o)]),e(", "),t("a",D,[e("Reddit"),a(o)]),e(", "),t("a",L,[e("YouTube"),a(o)]),e(", "),t("a",U,[e("Facebook"),a(o)]),e(", "),t("a",P,[e("Instagram"),a(o)]),e(" and "),t("a",R,[e("Discord"),a(o)]),e(". For chat groups you can find us on "),t("a",H,[e("Slack"),a(o)]),e(", "),t("a",J,[e("Telegram"),a(o)]),e(" and "),t("a",V,[e("Keybase"),a(o)]),e(".")]),t("p",null,[e("Also, remember to follow our "),t("a",Z,[e("blog"),a(o)]),e(" to get the latest insights and information about Wasabi Wallet and Bitcoin privacy.")]),G,X,$,ee,t("ul",null,[te,t("li",null,[ae,e(": The follow-up concern is the inverse of the above. It is possible that the server could "),oe,e(" include one 'honest/real' coin in the mix and supply the other coins themselves. This gives a false sense of security, "),ie,e(". It would also be noticeable to all users excluding the user being targeted as their coins would not be mixed. It has been argued that this 'attack' would be very costly in terms of fees because the number of coins being mixed is verifiable. Though it is true that remixes pay zero coordination fee to zkSNACKs, they do pay mining fees. See "),t("a",ne,[e("here"),a(o)]),e(" for more info.")])]),se,t("p",null,[e("Ádám Ficsor worked with several others on a privacy-focused Bitcoin wallet called Hidden Wallet all the way "),t("a",re,[e("back in December 2015"),a(o)]),e(". Wasabi 1.0 was unveiled in 2018 at the Building on Bitcoin conference by Ádám. At the time, Wasabi was essentially HiddenWallet rebranded and rewritten from scratch with some new features. Key dates:")]),he,t("p",null,[t("a",le,[ce,a(o)])]),t("p",null,[t("a",de,[ue,a(o)])]),pe,t("p",null,[e("Wasabi follows Bitcoin's philosophy by making the software "),t("a",be,[e("open-source"),a(o)]),e(" and by publishing it under "),t("a",me,[e("MIT license"),a(o)]),e(". Bitcoin users prefer open-source software to proprietary software for a number of reasons, including:")]),fe,t("p",null,[e("WabiSabi defines a pre-mix and a post-mix wallet and a mixing technique. Pre-mix wallet functionality can be added to any Bitcoin wallet without much overhead. Post-mix wallets on the other hand have strong privacy requirements, regarding coin selection, private transaction and balance retrieval, transaction input and output indexing and broadcasting. The requirements and recommendations for pre and post-mix wallets together define the Wallet Privacy Framework. Coins from pre-mix wallets to post-mix wallets are moved by mixing. Most on-chain mixing techniques, like CoinShuffle, CoinShuffle++, TumbleBit's Classic Tumbler mode, or ZeroLink can be used. However WabiSabi defines its own mixing technique: "),a(i,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[e("WabiSabi coinjoin")]),_:1}),e(".")]),t("p",null,[e("For more info please see "),t("a",we,[e("WabiSabi"),a(o)]),e(".")]),ye,t("p",null,[e("Wasabi runs in most operating systems with 64-bit architecture. For the complete list of all the officially supported operating systems, click "),t("a",ge,[e("here"),a(o)]),e(".")]),_e,t("p",null,[e("As long as your operating system is "),t("a",ke,[e("supported"),a(o)]),e(", Wasabi should be able to run on your hardware. The more transactions a wallet has made, the more resources Wasabi will consume, particularly RAM. The software can also consume a significant amount of CPU for specific tasks, such as coinjoins or wallet loading. Approximately 3 GB of disk space are also needed, mainly to store the "),a(i,{to:"/FAQ/FAQ-UseWasabi.html#what-are-bip-158-block-filters"},{default:n(()=>[e("block filters")]),_:1}),e(". If you are running the wallet on a system with scarce resources, consider using the "),t("a",We,[e("daemon"),a(o)]),e(" instead of the GUI application.")])])}const Ce=l(u,[["render",ve],["__file","FAQ-Introduction.html.vue"]]);export{Ce as default};
+import{_ as h}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as l,r,o as c,c as d,a as t,b as e,d as a,w as n,e as s}from"./app.65e5b6fd.js";const u={},p=s('
     Introduction to Wasabi
     The Basics
     Who can use Wasabi?
    ',3),b={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Fluent.Desktop",target:"_blank",rel:"noopener noreferrer"},m={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},f={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Daemon",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Tests",target:"_blank",rel:"noopener noreferrer"},y={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Packager",target:"_blank",rel:"noopener noreferrer"},g={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi",target:"_blank",rel:"noopener noreferrer"},_={href:"https://wasabiwallet.io/swagger/",target:"_blank",rel:"noopener noreferrer"},k={href:"https://github.com/zkSNACKs/WasabiDoc",target:"_blank",rel:"noopener noreferrer"},W={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/LICENSE.md",target:"_blank",rel:"noopener noreferrer"},v=t("p",null,"Wasabi is used by individuals to make everyday payments, to manage their hardware wallet long term hodlings, and to CoinJoin their sats for added privacy. Entrepreneurs may use Wasabi to defend their customers from spies and to ensure a private business relationship. While kids may use Wasabi to stack the sats gifted by grandma, and learn the importance of hodling.",-1),x=t("div",{class:"custom-container tip"},[t("p",{class:"custom-container-title"},"TIP"),t("p",null,"Wasabi is a tool for everyone.")],-1),T=t("h3",{id:"what-is-a-coinjoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-a-coinjoin","aria-hidden":"true"},"#"),e(" What is a coinjoin?")],-1),S=t("p",null,"Coinjoin is a mechanism by which multiple participants combine their coins (or UTXOs, to be more precise) into one large transaction with multiple inputs and multiple outputs. An observer cannot determine which output belongs to which input, and neither can the participants themselves. This makes it difficult for outside parties to trace where a particular coin originated from and where it was sent to (as opposed to regular bitcoin transactions, where there is usually one sender and one receiver).",-1),A=t("p",null,"This can be done with non-custodial software like Wasabi that eliminates the risk of funds disappearing or being stolen. Each of the signatures are created on the participants’ computers after thorough verification, so nobody can alter the transaction or redirect the funds. The funds will always be in a Bitcoin address that you control.",-1),C=t("p",null,"In very simple terms, coinjoin means: “when you want to make a transaction, find someone else who also wants to make a transaction and make a joint transaction together”.",-1),N={href:"https://en.bitcoin.it/wiki/CoinJoin",target:"_blank",rel:"noopener noreferrer"},z=t("h3",{id:"do-i-need-to-trust-wasabi-with-my-coins",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#do-i-need-to-trust-wasabi-with-my-coins","aria-hidden":"true"},"#"),e(" Do I need to trust Wasabi with my coins?")],-1),B=t("h3",{id:"what-is-the-privacy-i-get-after-mixing-with-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-the-privacy-i-get-after-mixing-with-wasabi","aria-hidden":"true"},"#"),e(" What is the privacy I get after mixing with Wasabi?")],-1),I=s('
     Why is Wasabi Bitcoin-only?
    There are countless reasons why it is the only logical choice to be bitcoin-only. With Bitcoin we have a once in a lifetime opportunity to manifest libre sound money. If we succeed, then an utmost beautiful agora of sovereign individuals may emerge. If we fail, then this will conjure up the most horrific Orwellian nightmare. There is no room for wasted time and energy, this great work requires our full attention. Any line of code written to support a random shitcoin takes away scarce developer time to work on real problems.
     What is considered a sufficient anonymity score?
    It is difficult to determine a sufficient anonymity score since enough research hasn’t been conducted to provide a definitive answer. The right anonymity score depends on your own personal threat model. However, to be on the safe side, with Wasabi Wallet 2.0 an anonymity score of 5 and above could be considered sufficient.
     Is there a way to check Wasabi's uptime status?
    ',5),j={href:"https://stats.uptimerobot.com/YQqGyUL8A7",target:"_blank",rel:"noopener noreferrer"},K=t("h3",{id:"what-software-supplies-the-block-filters-that-wasabi-uses",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-software-supplies-the-block-filters-that-wasabi-uses","aria-hidden":"true"},"#"),e(" What software supplies the block filters that Wasabi uses?")],-1),F={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},M=t("h3",{id:"is-the-backend-s-coordinator-code-open-source",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-the-backend-s-coordinator-code-open-source","aria-hidden":"true"},"#"),e(" Is the Backend's (Coordinator) code open-source?")],-1),O={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Backend",target:"_blank",rel:"noopener noreferrer"},E=t("h3",{id:"is-there-an-android-ios-version",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#is-there-an-android-ios-version","aria-hidden":"true"},"#"),e(" Is there an Android/iOs version?")],-1),Q=t("p",null,"No, Wasabi and CoinJoin features require considerable computational power, not currently replicable on a smartphone.",-1),q=t("h3",{id:"where-can-i-find-wasabi-wallet-on-social-media",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#where-can-i-find-wasabi-wallet-on-social-media","aria-hidden":"true"},"#"),e(" Where can I find Wasabi Wallet on social media?")],-1),Y={href:"https://twitter.com/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},D={href:"https://www.reddit.com/r/WasabiWallet/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://www.youtube.com/c/WasabiWallet",target:"_blank",rel:"noopener noreferrer"},U={href:"https://www.facebook.com/officialwasabiwallet/",target:"_blank",rel:"noopener noreferrer"},P={href:"https://www.instagram.com/wasabi_wallet/",target:"_blank",rel:"noopener noreferrer"},R={href:"https://discord.com/invite/nm7YHEZnJs",target:"_blank",rel:"noopener noreferrer"},H={href:"https://join.slack.com/t/tumblebit/shared_invite/enQtNjQ1MTQ2NzQ1ODI0LWIzOTg5YTM3YmNkOTg1NjZmZTQ3NmM1OTAzYmQyYzk1M2M0MTdlZDk2OTQwNzFiNTg1ZmExNzM0NjgzY2M0Yzg",target:"_blank",rel:"noopener noreferrer"},J={href:"https://t.me/WasabiWallet",target:"_blank",rel:"noopener noreferrer"},V={href:"https://keybase.io/team/wasabiwallet",target:"_blank",rel:"noopener noreferrer"},Z={href:"https://blog.wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},G=t("h2",{id:"for-advanced-wasabikas",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#for-advanced-wasabikas","aria-hidden":"true"},"#"),e(" For advanced Wasabikas")],-1),X=t("h3",{id:"can-the-coordinator-attack-me",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#can-the-coordinator-attack-me","aria-hidden":"true"},"#"),e(" Can the coordinator attack me?")],-1),$=t("p",null,"The developers have gone to great lengths to ensure that the coordinator cannot steal funds nor link inputs to outputs. The nature of Wasabi is that you should not need to trust the developers or the Wasabi coordinating server, as you can verify that the code does not leak information to anyone. Due to the nature of coinjoin transactions users don't need to trust other users or the coordinator against theft, leaving denial of service and attacks on privacy as the main concerns",-1),ee=t("p",null,[e("The only known possible 'malicious' actions that the server "),t("em",null,"could"),e(" perform are two sides of the same coin;")],-1),te=t("li",null,[t("strong",null,"Blacklisted UTXO's"),e(": Though this would not affect the users who are able to successfully mix with other 'honest/real' peers.")],-1),ae=t("strong",null,"Targeted Sybil Attack",-1),oe=t("em",null,"only",-1),ie=t("strong",null,"but does not worsen the existing privacy of the coin",-1),ne={href:"https://github.com/zkSNACKs/WabiSabi/blob/master/protocol.md#attacks-on-privacy",target:"_blank",rel:"noopener noreferrer"},se=t("h3",{id:"what-is-the-history-of-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-is-the-history-of-wasabi","aria-hidden":"true"},"#"),e(" What is the history of Wasabi?")],-1),re={href:"https://docs.google.com/drawings/d/1wLL7aSgYBWNoyzllg6_haisFt-gQCf-QUzVzQPkARts/edit",target:"_blank",rel:"noopener noreferrer"},he=t("ul",null,[t("li",null,"The 1.0 Beta release was on August 1, 2018 (on the first anniversary of UASF)"),t("li",null,"The 1.0 release was on October 31, 2018 (on the tenth anniversary of the Bitcoin Whitepaper)"),t("li",null,"The 2.0 Testnet release was on March 1, 2022"),t("li",null,"The 2.0 release was on June 15, 2022")],-1),le={href:"https://youtu.be/XORDEX-RrAI?t=6420",target:"_blank",rel:"noopener noreferrer"},ce=t("img",{src:h,alt:"Watch the video"},null,-1),de={href:"https://youtu.be/b1Vligm0SO8",target:"_blank",rel:"noopener noreferrer"},ue=t("img",{src:h,alt:"Watch the video"},null,-1),pe=t("h3",{id:"why-is-wasabi-libre-and-open-source-software",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#why-is-wasabi-libre-and-open-source-software","aria-hidden":"true"},"#"),e(" Why is Wasabi libre and open-source software?")],-1),be={href:"https://github.com/zkSNACKs/WalletWasabi/",target:"_blank",rel:"noopener noreferrer"},me={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/LICENSE.md",target:"_blank",rel:"noopener noreferrer"},fe=s('
    Control
    Many people prefer open-source software because they have more control over the software they run.
    They can examine the code to make sure it's not doing anything they don't want it to do, and they can change parts of it they don't like. Users who aren't programmers also benefit from open-source software, since they can use this software for any purpose.
    Training
    Other people like open-source software because it helps them become better programmers.
    Open-source code is publicly accessible. Students can easily study it as they learn to make better software. Students can also share their work with others, inviting comments and critique, as they develop their skills. When people discover mistakes in programs' source code, they can share those mistakes with others to help them avoid making those same mistakes themselves.
    Security
    Some people prefer open-source software because they consider it more secure and stable than proprietary software.
    Anyone can view and modify open-source software. Other users may spot and correct errors or omissions that a program's original authors might have missed. And because so many programmers can work on a piece of open-source software without asking for permission from original authors, they can fix, update, and upgrade open-source software more quickly than they can proprietary software.
    Stability
    Many users prefer open-source software to proprietary software for important, long-term projects.
    Programmers publicly distribute the source code for open-source software. Users relying on that software for critical tasks can be sure their tools won't disappear or fall into disrepair if their original creators stop working on them. Additionally, open-source software tends to both incorporate and operate according to open standards.
     What is the general idea of WabiSabi coinjoin?
    While fungibility is an essential property of good money, Bitcoin has its limitations in this area. Numerous fungibility improvements have been proposed; however, none of them have addressed the privacy issues in full. WabiSabi is designed so that no participant, outside observer or even the coordinator can spy on the user. The scope of WabiSabi is not limited to a single transaction, it extends to transaction chains and it addresses various network layer deanonymizations. However, its scope is limited to Bitcoin's first layer. Even if an off-chain anonymity solution gets widely adopted, ultimately the entrance and exit transactions will always be settled on-chain. Therefore, there will always be need for on-chain privacy.
    Ideal fungibility requires every Bitcoin transaction to be indistinguishable from each other, but it is an unrealistic goal. WabiSabi's objective is to break all links between coins. Thus, WabiSabi enables the usage of Bitcoin in a fully anonymous way.
    ',11),we={href:"https://github.com/zksnacks/wabisabi",target:"_blank",rel:"noopener noreferrer"},ye=t("h3",{id:"what-are-the-supported-operating-systems",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-are-the-supported-operating-systems","aria-hidden":"true"},"#"),e(" What are the supported operating systems?")],-1),ge={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems",target:"_blank",rel:"noopener noreferrer"},_e=t("h3",{id:"what-are-the-minimal-requirements-to-run-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#what-are-the-minimal-requirements-to-run-wasabi","aria-hidden":"true"},"#"),e(" What are the minimal requirements to run Wasabi?")],-1),ke={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems",target:"_blank",rel:"noopener noreferrer"},We={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/WalletWasabi.Daemon",target:"_blank",rel:"noopener noreferrer"};function ve(xe,Te){const o=r("ExternalLinkIcon"),i=r("RouterLink");return c(),d("div",null,[p,t("p",null,[e("Every single line of code in Wasabi, the "),t("a",b,[e("wallet"),a(o)]),e(", the "),t("a",m,[e("backend server"),a(o)]),e(", the "),t("a",f,[e("daemon"),a(o)]),e(", the "),t("a",w,[e("tests"),a(o)]),e(", the "),t("a",y,[e("packager"),a(o)]),e(", the "),t("a",g,[e("library"),a(o)]),e(", the "),t("a",_,[e("api"),a(o)]),e(", the "),t("a",k,[e("documentation"),a(o)]),e(" - has always been and will always be libre and open-source under the "),t("a",W,[e("MIT license"),a(o)]),e(". This means that anyone, yes, ANYONE can use Wasabi without permission, for any use case, free of charge.")]),v,x,T,S,A,C,t("p",null,[e("See also the "),t("a",N,[e("Bitcoin Wiki on coinjoins"),a(o)])]),z,t("p",null,[e("Since Wasabi's coinjoin implementation is trustless by design, there is no need for participants to trust each other or a third party. Both the sending address (the coinjoin input) and the receiving address (the coinjoin output) are controlled by your own private keys. The Wasabi server merely coordinates the process of combining each participant's input into one single transaction, but the Wasabi Wallet can neither steal your coins, nor figure out which outputs belong to which inputs (look up “"),a(i,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[e("WabiSabi coinjoin")]),_:1}),e("” if you want to know more).")]),B,t("p",null,[e("This depends on how you handle your outputs after the coinjoin. There are some ways how you can unintentionally undo the mixing by being careless. For example, if you send a mixed coin to an already used address, then anyone can see that both coins are controlled by the same entity. More importantly, anyone who knows that the address belongs to you knows that you own that mixed coin. "),a(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[e("Address reuse")]),_:1}),e(" compromises your privacy. Another deanonymizing scenario occurs when you combine mixed outputs with unmixed ones when sending: a third party will be able to make the connection between them as belonging to the same sender. This is why you need to be careful with non-private/"),a(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[e("change coins")]),_:1}),e(".")]),t("p",null,[e("The practice of being careful with your post-mix outputs is commonly facilitated through coin control. Find out more about coin control in "),a(i,{to:"/why-wasabi/Coins.html"},{default:n(()=>[e("here")]),_:1}),e(". However, Wasabi Wallet is build in a way to help the user to avoid privacy leaks when using the wallet.")]),I,t("p",null,[e("Yes, you can check the status of Wasabi-related services and websites (like APIs, Backend, etc.) via "),t("a",j,[e("UptimeRobot Wasabi Status Page"),a(o)]),e(".")]),K,t("p",null,[e("The zkSNACKs coordinator supplies identical filters to every client. This means that you rely on the "),t("a",F,[e("Wasabi backend"),a(o)]),e(" to provide valid filters. But because you download the blocks from a random Bitcoin peer-to-peer node - or your own node - the coordinator cannot spy on which blocks you are interested in. Furthermore, the random node will only know which block is needed but it won't have any clue which transaction(s) belongs to the wallet.")]),M,t("p",null,[e("Yes, you can verify the code on "),t("a",O,[e("GitHub"),a(o)]),e(".")]),E,Q,q,t("p",null,[e("You can find us on "),t("a",Y,[e("Twitter"),a(o)]),e(", "),t("a",D,[e("Reddit"),a(o)]),e(", "),t("a",L,[e("YouTube"),a(o)]),e(", "),t("a",U,[e("Facebook"),a(o)]),e(", "),t("a",P,[e("Instagram"),a(o)]),e(" and "),t("a",R,[e("Discord"),a(o)]),e(". For chat groups you can find us on "),t("a",H,[e("Slack"),a(o)]),e(", "),t("a",J,[e("Telegram"),a(o)]),e(" and "),t("a",V,[e("Keybase"),a(o)]),e(".")]),t("p",null,[e("Also, remember to follow our "),t("a",Z,[e("blog"),a(o)]),e(" to get the latest insights and information about Wasabi Wallet and Bitcoin privacy.")]),G,X,$,ee,t("ul",null,[te,t("li",null,[ae,e(": The follow-up concern is the inverse of the above. It is possible that the server could "),oe,e(" include one 'honest/real' coin in the mix and supply the other coins themselves. This gives a false sense of security, "),ie,e(". It would also be noticeable to all users excluding the user being targeted as their coins would not be mixed. It has been argued that this 'attack' would be very costly in terms of fees because the number of coins being mixed is verifiable. Though it is true that remixes pay zero coordination fee to zkSNACKs, they do pay mining fees. See "),t("a",ne,[e("here"),a(o)]),e(" for more info.")])]),se,t("p",null,[e("Ádám Ficsor worked with several others on a privacy-focused Bitcoin wallet called Hidden Wallet all the way "),t("a",re,[e("back in December 2015"),a(o)]),e(". Wasabi 1.0 was unveiled in 2018 at the Building on Bitcoin conference by Ádám. At the time, Wasabi was essentially HiddenWallet rebranded and rewritten from scratch with some new features. Key dates:")]),he,t("p",null,[t("a",le,[ce,a(o)])]),t("p",null,[t("a",de,[ue,a(o)])]),pe,t("p",null,[e("Wasabi follows Bitcoin's philosophy by making the software "),t("a",be,[e("open-source"),a(o)]),e(" and by publishing it under "),t("a",me,[e("MIT license"),a(o)]),e(". Bitcoin users prefer open-source software to proprietary software for a number of reasons, including:")]),fe,t("p",null,[e("WabiSabi defines a pre-mix and a post-mix wallet and a mixing technique. Pre-mix wallet functionality can be added to any Bitcoin wallet without much overhead. Post-mix wallets on the other hand have strong privacy requirements, regarding coin selection, private transaction and balance retrieval, transaction input and output indexing and broadcasting. The requirements and recommendations for pre and post-mix wallets together define the Wallet Privacy Framework. Coins from pre-mix wallets to post-mix wallets are moved by mixing. Most on-chain mixing techniques, like CoinShuffle, CoinShuffle++, TumbleBit's Classic Tumbler mode, or ZeroLink can be used. However WabiSabi defines its own mixing technique: "),a(i,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[e("WabiSabi coinjoin")]),_:1}),e(".")]),t("p",null,[e("For more info please see "),t("a",we,[e("WabiSabi"),a(o)]),e(".")]),ye,t("p",null,[e("Wasabi runs in most operating systems with 64-bit architecture. For the complete list of all the officially supported operating systems, click "),t("a",ge,[e("here"),a(o)]),e(".")]),_e,t("p",null,[e("As long as your operating system is "),t("a",ke,[e("supported"),a(o)]),e(", Wasabi should be able to run on your hardware. The more transactions a wallet has made, the more resources Wasabi will consume, particularly RAM. The software can also consume a significant amount of CPU for specific tasks, such as coinjoins or wallet loading. Approximately 3 GB of disk space are also needed, mainly to store the "),a(i,{to:"/FAQ/FAQ-UseWasabi.html#what-are-bip-158-block-filters"},{default:n(()=>[e("block filters")]),_:1}),e(". If you are running the wallet on a system with scarce resources, consider using the "),t("a",We,[e("daemon"),a(o)]),e(" instead of the GUI application.")])])}const Ce=l(u,[["render",ve],["__file","FAQ-Introduction.html.vue"]]);export{Ce as default};
diff --git a/assets/FAQ-UseWasabi.html.f98cdbbe.js b/assets/FAQ-UseWasabi.html.6e912125.js
similarity index 99%
rename from assets/FAQ-UseWasabi.html.f98cdbbe.js
rename to assets/FAQ-UseWasabi.html.6e912125.js
index b2b2f7fb4e..4628ed63f8 100644
--- a/assets/FAQ-UseWasabi.html.f98cdbbe.js
+++ b/assets/FAQ-UseWasabi.html.6e912125.js
@@ -1,4 +1,4 @@
-import{_ as p}from"./AddWalletButton.98ad9c28.js";import{_ as m,a as w,b as y}from"./AddWalletAddPassword.45b736a5.js";import{_ as l,a as f}from"./AddWalletConfirmRecoveryWords.2792528c.js";import{_ as c}from"./CoinjoinStrategy.5455b7fb.js";import{_ as b}from"./WalletSynchronizing.d188367c.js";import{_ as h,a as g}from"./AddressAwaitingPayment.1f3f0347.js";import{_ as v,a as _,b as k,c as u}from"./HistoryRightClick.a729d6cb.js";import{_ as r}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as W}from"./AutoStartCoinjoinThreshold.908ffaab.js";import{_ as x,a as T}from"./SettingsBitcoinCore.fab2a9f8.js";import{_ as C}from"./DiscreetModeActivate.e372f614.js";import{_ as I,r as d,o as A,c as j,a as e,d as a,w as n,b as t,e as s}from"./app.a5b7c2b2.js";const S="/PrivacyBar.png",B="/FeeDisplayUnit.png",P="/MusicBoxCoinjoinStopped.png",q="/TorStatusWarningIcon.png",F="/AddressesAwaitingPayment.png",H="/AddressesAwaitingPaymentEditLabel.png",R="/AddressesAwaitingPaymentQRCodeIcon.png",N="/SendFeeIcon.png",D="/SendCustomFee.png",U="/SpeedUpTxConfirm.png",z="/CancelTxConfirm.png",E="/PrivacyProgressTile.png",Q="/RedCoinIsolation.png",M="/VerifyRecoveryWords.png",O="/History.png",Y="/HistoryCoinjoin.png",L="/HistoryCoinjoinExpanded.png",J="/HistorySortDateColumn.png",G="/SearchBarTXIDSearch.png",K="/AnonymityScoreTarget.png",V="/SettingsDustThreshold.png",X="/SearchBarHelpSupportOpen.png",$="/WhiteMode.png",Z="/SendPreviewTransactionReviewCoins.png",ee="/WalletCoinsSendSelectedCoins.png",te={},ae=s('
     Use of Wasabi
     General
     How do I start using Wasabi?
    ',3),oe={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},ne=e("h3",{id:"how-do-i-generate-a-new-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-do-i-generate-a-new-wallet","aria-hidden":"true"},"#"),t(" How do I generate a new wallet?")],-1),ie=s('
    Click the Add Wallet button in the bottom left corner of the main view or in the searchbar.
    Add new wallet in Wasabi
    Click Create a new wallet.
    Create a new wallet in Wasabi
    As with everything in Wasabi, you are required to label this new wallet. Make sure that you are precise so that you know what this wallet is for and click Continue.
    Name a new wallet in Wasabi
    Now you will see the 12 recovery words. This is the mnemonic seed that you should back up, together with the password you create in the next phase, in order to recover your wallet. When you've backed everything up, click Continue.
    Wasabi Wallet recovery words
    In this page you should confirm the words, as a check that you've written down your mnemonic seed in the correct order. Once you're done, click Continue.
    Confirm recovery words
    Add a password. It is used to encrypt the private key (extracted from the extended private key) on the computer and needed to open the wallet and to recovered it in the future. Make sure that you properly back up and write down this password.
    Confirm the password and click Continue.
    Add a password in Wasabi
    Careful!!
    Without knowledge of the password, you CANNOT spend your bitcoin!!
    Make sure, and triple-check that you have done a proper backup of BOTH the password AND the mnemonic. If you only have the recovery words, but not the password, then you will NOT be able to open your wallet or to recover it.
    In order to protect your backup, consider storing the password and recovery words in different locations.
    Now you get to choose your wallets coinjoin strategy. Select one and click Continue.
    Wasabi Wallet coinjoin strategies
     Can I rename my Wallet?
    ',19),se=e("code",null,"Wallet Folder",-1),re=e("code",null,"Wallets",-1),de=e("code",null,".json",-1),le=e("code",null,"Wallets",-1),ce=e("code",null,".json",-1),he=e("code",null,"WalletBackups",-1),ue=e("code",null,".json",-1),pe=s('
    TIP
    You need to mark the “show hidden files” setting to see the Wasabi data folder.
    WARNING
    To avoid problems, make sure you close Wasabi Wallet before proceeding to rename any of your wallets.
     What is the password used for?
    The password you set is used:
    ',4),me={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},we={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},ye=e("p",null,"Wasabi stores only the BIP38 encrypted blob, so you'll need to type in the password to open the wallet and to spend from Wasabi.",-1),fe=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"DANGER"),e("p",null,"The password will unlock your bitcoin to anyone who has access to the recovery words backup or the computer! If your backup gets compromised, this password is the only thing protecting your precious sats.")],-1),be=e("h3",{id:"what-password-should-i-use",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-password-should-i-use","aria-hidden":"true"},"#"),t(" What password should I use?")],-1),ge={class:"custom-container danger"},ve=e("p",{class:"custom-container-title"},"DANGER",-1),_e=e("strong",null,"VERY",-1),ke={href:"https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases",target:"_blank",rel:"noopener noreferrer"},We=s('
     Where can I find the Wasabi data folder?
    You can easily reach it from inside Wasabi by typing Data Folder in the search bar at the top of the main view.
    Or you can manually navigate to it (depending on which OS you have):
    • Windows: /Users/{your username}/AppData/Roaming/WalletWasabi/Client
    • Linux: /home/{your username}/.walletwasabi/client
    • macOS: /Users/{your username}/.walletwasabi/client
    TIP
    You need to mark the “show hidden files” setting to see it.
     Can I spend my bitcoin without the password?
    DANGER
    NO!!! Without knowledge of your password, even when you have the wallet file and recovery words, you CANNOT spend your bitcoin!
    When creating a new wallet, after labeling it properly, the next step is to select a long and random password. Every time you want to spend your coins from Wasabi, you MUST provide this password. So even if you have these words securely engraved in metal, without the password, you cannot restore the backup of your wallet.
    TIP
    Always back up your mnemonic recovery words, and your password in two separate secure locations.
     Why BIP 38?
    ',10),xe={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},Te={href:"https://github.com/MetacoSA/NBitcoin",target:"_blank",rel:"noopener noreferrer"},Ce=e("h3",{id:"what-are-the-terms-and-conditions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-are-the-terms-and-conditions","aria-hidden":"true"},"#"),t(" What are the terms and conditions?")],-1),Ie=e("p",null,"The most important parts of the legal documents are summarized in the following points:",-1),Ae=e("ul",null,[e("li",null,"The service is open-source under the MIT license."),e("li",null,"The service is provided on a non-custodial basis. Safekeeping of keys are the sole responsibility of the user."),e("li",null,"The user is solely responsible to act according to their local laws and regulations."),e("li",null,"We do not store any personally identifiable information. Moreover, our trustless software architecture prevents us from gathering this information in the first place."),e("li",null,"A transaction fee is only charged by the service provider for CoinJoin transactions."),e("li",null,"We only provide written support, and NEVER ask for recovery words, passwords or similar security critical information.")],-1),je={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi/Legal/Assets/LegalDocumentsWw2.txt",target:"_blank",rel:"noopener noreferrer"},Se=s(`
     Can I import a watch-only extended public key?
    Yes, but not yet in the GUI, you will need to manually create a new wallet file.
    Open a text editor and paste the following wallet structure:
    {
+import{_ as p}from"./AddWalletButton.98ad9c28.js";import{_ as m,a as w,b as y}from"./AddWalletAddPassword.45b736a5.js";import{_ as l,a as f}from"./AddWalletConfirmRecoveryWords.2792528c.js";import{_ as c}from"./CoinjoinStrategy.5455b7fb.js";import{_ as b}from"./WalletSynchronizing.d188367c.js";import{_ as h,a as g}from"./AddressAwaitingPayment.1f3f0347.js";import{_ as v,a as _,b as k,c as u}from"./HistoryRightClick.a729d6cb.js";import{_ as r}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as W}from"./AutoStartCoinjoinThreshold.908ffaab.js";import{_ as x,a as T}from"./SettingsBitcoinCore.fab2a9f8.js";import{_ as C}from"./DiscreetModeActivate.e372f614.js";import{_ as I,r as d,o as A,c as j,a as e,d as a,w as n,b as t,e as s}from"./app.65e5b6fd.js";const S="/PrivacyBar.png",B="/FeeDisplayUnit.png",P="/MusicBoxCoinjoinStopped.png",q="/TorStatusWarningIcon.png",F="/AddressesAwaitingPayment.png",H="/AddressesAwaitingPaymentEditLabel.png",R="/AddressesAwaitingPaymentQRCodeIcon.png",N="/SendFeeIcon.png",D="/SendCustomFee.png",U="/SpeedUpTxConfirm.png",z="/CancelTxConfirm.png",E="/PrivacyProgressTile.png",Q="/RedCoinIsolation.png",M="/VerifyRecoveryWords.png",O="/History.png",Y="/HistoryCoinjoin.png",L="/HistoryCoinjoinExpanded.png",J="/HistorySortDateColumn.png",G="/SearchBarTXIDSearch.png",K="/AnonymityScoreTarget.png",V="/SettingsDustThreshold.png",X="/SearchBarHelpSupportOpen.png",$="/WhiteMode.png",Z="/SendPreviewTransactionReviewCoins.png",ee="/WalletCoinsSendSelectedCoins.png",te={},ae=s('
     Use of Wasabi
     General
     How do I start using Wasabi?
    ',3),oe={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},ne=e("h3",{id:"how-do-i-generate-a-new-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-do-i-generate-a-new-wallet","aria-hidden":"true"},"#"),t(" How do I generate a new wallet?")],-1),ie=s('
    Click the Add Wallet button in the bottom left corner of the main view or in the searchbar.
    Add new wallet in Wasabi
    Click Create a new wallet.
    Create a new wallet in Wasabi
    As with everything in Wasabi, you are required to label this new wallet. Make sure that you are precise so that you know what this wallet is for and click Continue.
    Name a new wallet in Wasabi
    Now you will see the 12 recovery words. This is the mnemonic seed that you should back up, together with the password you create in the next phase, in order to recover your wallet. When you've backed everything up, click Continue.
    Wasabi Wallet recovery words
    In this page you should confirm the words, as a check that you've written down your mnemonic seed in the correct order. Once you're done, click Continue.
    Confirm recovery words
    Add a password. It is used to encrypt the private key (extracted from the extended private key) on the computer and needed to open the wallet and to recovered it in the future. Make sure that you properly back up and write down this password.
    Confirm the password and click Continue.
    Add a password in Wasabi
    Careful!!
    Without knowledge of the password, you CANNOT spend your bitcoin!!
    Make sure, and triple-check that you have done a proper backup of BOTH the password AND the mnemonic. If you only have the recovery words, but not the password, then you will NOT be able to open your wallet or to recover it.
    In order to protect your backup, consider storing the password and recovery words in different locations.
    Now you get to choose your wallets coinjoin strategy. Select one and click Continue.
    Wasabi Wallet coinjoin strategies
     Can I rename my Wallet?
    ',19),se=e("code",null,"Wallet Folder",-1),re=e("code",null,"Wallets",-1),de=e("code",null,".json",-1),le=e("code",null,"Wallets",-1),ce=e("code",null,".json",-1),he=e("code",null,"WalletBackups",-1),ue=e("code",null,".json",-1),pe=s('
    TIP
    You need to mark the “show hidden files” setting to see the Wasabi data folder.
    WARNING
    To avoid problems, make sure you close Wasabi Wallet before proceeding to rename any of your wallets.
     What is the password used for?
    The password you set is used:
    ',4),me={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},we={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},ye=e("p",null,"Wasabi stores only the BIP38 encrypted blob, so you'll need to type in the password to open the wallet and to spend from Wasabi.",-1),fe=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"DANGER"),e("p",null,"The password will unlock your bitcoin to anyone who has access to the recovery words backup or the computer! If your backup gets compromised, this password is the only thing protecting your precious sats.")],-1),be=e("h3",{id:"what-password-should-i-use",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-password-should-i-use","aria-hidden":"true"},"#"),t(" What password should I use?")],-1),ge={class:"custom-container danger"},ve=e("p",{class:"custom-container-title"},"DANGER",-1),_e=e("strong",null,"VERY",-1),ke={href:"https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases",target:"_blank",rel:"noopener noreferrer"},We=s('
     Where can I find the Wasabi data folder?
    You can easily reach it from inside Wasabi by typing Data Folder in the search bar at the top of the main view.
    Or you can manually navigate to it (depending on which OS you have):
    • Windows: /Users/{your username}/AppData/Roaming/WalletWasabi/Client
    • Linux: /home/{your username}/.walletwasabi/client
    • macOS: /Users/{your username}/.walletwasabi/client
    TIP
    You need to mark the “show hidden files” setting to see it.
     Can I spend my bitcoin without the password?
    DANGER
    NO!!! Without knowledge of your password, even when you have the wallet file and recovery words, you CANNOT spend your bitcoin!
    When creating a new wallet, after labeling it properly, the next step is to select a long and random password. Every time you want to spend your coins from Wasabi, you MUST provide this password. So even if you have these words securely engraved in metal, without the password, you cannot restore the backup of your wallet.
    TIP
    Always back up your mnemonic recovery words, and your password in two separate secure locations.
     Why BIP 38?
    ',10),xe={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},Te={href:"https://github.com/MetacoSA/NBitcoin",target:"_blank",rel:"noopener noreferrer"},Ce=e("h3",{id:"what-are-the-terms-and-conditions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-are-the-terms-and-conditions","aria-hidden":"true"},"#"),t(" What are the terms and conditions?")],-1),Ie=e("p",null,"The most important parts of the legal documents are summarized in the following points:",-1),Ae=e("ul",null,[e("li",null,"The service is open-source under the MIT license."),e("li",null,"The service is provided on a non-custodial basis. Safekeeping of keys are the sole responsibility of the user."),e("li",null,"The user is solely responsible to act according to their local laws and regulations."),e("li",null,"We do not store any personally identifiable information. Moreover, our trustless software architecture prevents us from gathering this information in the first place."),e("li",null,"A transaction fee is only charged by the service provider for CoinJoin transactions."),e("li",null,"We only provide written support, and NEVER ask for recovery words, passwords or similar security critical information.")],-1),je={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi/Legal/Assets/LegalDocumentsWw2.txt",target:"_blank",rel:"noopener noreferrer"},Se=s(`
     Can I import a watch-only extended public key?
    Yes, but not yet in the GUI, you will need to manually create a new wallet file.
    Open a text editor and paste the following wallet structure:
    {
   "EncryptedSecret": null,
   "ChainCode": null,
   "MasterFingerprint": null,
diff --git a/assets/Glossary-GeneralBitcoin.html.ec5f1d03.js b/assets/Glossary-GeneralBitcoin.html.2952954a.js
similarity index 99%
rename from assets/Glossary-GeneralBitcoin.html.ec5f1d03.js
rename to assets/Glossary-GeneralBitcoin.html.2952954a.js
index 30204534c6..e68b1c636b 100644
--- a/assets/Glossary-GeneralBitcoin.html.ec5f1d03.js
+++ b/assets/Glossary-GeneralBitcoin.html.2952954a.js
@@ -1 +1 @@
-import{_ as h,r as s,o as c,c as d,a as e,b as a,d as t,w as n,e as o}from"./app.a5b7c2b2.js";const l={},u=e("h2",{id:"bitcoin-in-general",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-in-general","aria-hidden":"true"},"#"),a(" Bitcoin in general")],-1),p=e("h3",{id:"address",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address","aria-hidden":"true"},"#"),a(" Address")],-1),f=e("h3",{id:"bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin","aria-hidden":"true"},"#"),a(" Bitcoin")],-1),b=e("p",null,"Bitcoin is a peer-to-peer electronic cash system. An innovative payment network and a new kind of money. It is a decentralized digital currency without a central bank or single administrator that can be sent from user to user on the peer-to-peer bitcoin blockchain network without the need for intermediaries.",-1),m=e("h3",{id:"bitcoin-core",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-core","aria-hidden":"true"},"#"),a(" Bitcoin Core")],-1),y=e("p",null,[a("Bitcoin Core is an open-source project which maintains and releases Bitcoin client software called "),e("code",null,"Bitcoin Core"),a(", considered to be Bitcoin's reference implementation. It is a direct descendant of the original Bitcoin software client released by Satoshi Nakamoto after he published the famous Bitcoin whitepaper.")],-1),g=e("code",null,"full-node",-1),w={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},k=e("h3",{id:"bitcoin-improvement-proposal-bip",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-improvement-proposal-bip","aria-hidden":"true"},"#"),a(" Bitcoin Improvement Proposal (BIP)")],-1),v=e("h3",{id:"bitcoin-knots",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-knots","aria-hidden":"true"},"#"),a(" Bitcoin Knots")],-1),_={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},x=o('
     Block
    A block is a batch of valid Bitcoin transactions and its hash must be a value below a certain difficulty target to prove the work of the miner. Each block references the hash of the previous block, thus creating a hash chain of blocks. On average a new block is mined every 10 minutes.
     Blockchain
    The blockchain is the one chain of valid Bitcoin blocks with the most accumulated proof of work. It is an append-only data structure with new blocks being added on average every 10 minutes. Because of its uniquely verifiable and global consensus, it is a revolutionary standard for time, thus some call it timechain.
     Change
    ',5),B=o('
     Child Pays For Parent (CPFP)
    Child Pays For Parent (CPFP) is a fee bumping technique where a user spends an output from a low fee rate unconfirmed transaction in a child transaction with a high fee rate in order to encourage miners to include both transactions in a block.
     Coinbase
    A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
     Coinbase Transaction
    The first transaction in a block. Always created by a miner, it includes a single coinbase.
     Cold Storage
    ',7),P=o('
     Confirmations
    Once a transaction is included in a block, it has one confirmation. As soon as another block is mined on the same blockchain, the transaction has two confirmations, and so on. Six or more confirmations is considered sufficient proof that a transaction cannot be reversed.
     Consensus
    When several nodes, usually most nodes on the network, all have the same blocks in their locally-validated best blockchain.
     Consensus Rules
    The block validation rules that full nodes follow to stay in consensus with other nodes.
     Custodial (Wallet or Mixer)
    A custodial wallet is any wallet where the private keys of your coins are in the hands of a third party. In essence, they operate similarly to traditional banks.
    A custodial mixer needs you to send your bitcoins to a central part before mixing. This means that you are at risk of being stolen from.
     Difficulty
    A network-wide setting that controls how much computation is required to produce a proof of work.
     Difficulty Retargeting (Difficulty Adjustment)
    A network-wide recalculation of the difficulty that occurs once every 2,016 blocks and considers the hashing power of the previous 2,016 blocks.
     Difficulty Target
    A difficulty at which all the computation in the network will find blocks approximately every 10 minutes. It specifies the numeric value the hash of a block must not be above to be considered a valid block.
     ECDSA
    ECDSA (Elliptic Curve Digital Signature Algorithm) is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners.
     Fork
    Fork, also known as accidental fork, occurs when two or more blocks have the same block height, forking the blockchain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
     Full node
    Any computer that connects to the Bitcoin network is called a node. Nodes that fully verify all of the rules of Bitcoin are called full nodes. Full nodes download every block and transaction and check them against Bitcoin's consensus rules.
     Fungibility
    ',22),T=o('
     Genesis Block
    The first block in the blockchain, used to initialize the cryptocurrency.
     Hard Fork
    Hard fork, also known as hard-forking change, is a permanent divergence in the blockchain, it occurs when non-upgraded nodes can not validate blocks created by upgraded nodes that follow newer consensus rules. The upgraded nodes break the rules of the legacy nodes. Not to be confused with fork, soft fork, software fork or Git fork.
     Hardware Wallet (HWW)
    ',5),A=o('
     Hash
    A cryptographic hash function takes any input of arbitrary size [the message] and computes a value of fixed size that is unique to the input, which is called a hash or a digest. If one bit of the input changes, the output will be completely different [avalanche effect]. And there are no two messages that result in the same hash [collision resistance]. The only way to get any given input, is by computing all possible inputs, it is a one-way function [pre-image resistance]. Bitcoin uses the SHA256 in many parts of the protocol.
     Hierarchical Deterministic (HD) Protocol
    The Hierarchical Deterministic key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy.
     Hierarchical Deterministitc (HD) Wallet
    Wallets using the Hierarchical Deterministic Protocol key creation and transfer protocol (BIP32).
     Hot Wallet
    A hot wallet is a software wallet that runs on a device which is connected to the Internet. Wasabi is a hot wallet by default.
     Input
    Input, transaction input, or TxIn is an input in a Bitcoin transaction which contains two fields: a unique transaction hash and an index number, which references one utxo of a previous transaction which is spent in this transaction.
     Lightning Network (LN)
    Lightning Network is a proposed implementation of Hashed Timelock Contracts (HTLCs) with bi-directional payment channels which allows payments to be securely routed across multiple peer-to-peer payment channels. This allows the formation of a network where any peer on the network can pay any other peer even if they don't directly have a channel open between each other.
     Mainnet
    The original and main network for Bitcoin transactions, where satoshis have real economic value.
     Mempool
    ',15),S=o('
     Merkle Root
    The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
     Merkle Tree
    A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
     Miner
    A Bitcoin user that attempts to find valid proof of work for new candidate blocks, by repeated hashing until the difficulty target is met.
     Mining Reward
    An amount of satoshis included in each new block as a reward by the network to the miner who found the proof of work solution. Initially it was 50 bitcoin per block, which is halved every 210 000 blocks, or roughly 4 years. This leads to a total money supply of just below 21 million bitcoin.
     Multisignature (multisig)
    ',9),W=e("code",null,"m",-1),I=e("code",null,"n",-1),C=o('
     Non-Custodial (Wallet or Mixer)
    A non-custodial wallet is any wallet where the private keys of your coins are in your hands. Non-custodial wallets give you full control over your bitcoins.
    A non-custodial mixer like Wasabi eliminates the risk that the coordinator can steal your bitcoin. Each participant verifies the proposed transaction, and signs it only if it is valid. This signature is only valid for this transaction, so any attempt to change the transaction after the fact is futile. The funds will always be in a Bitcoin address that you control.
     Nonce
    The nonce in a Bitcoin block is a 32-bit (4-byte) field whose value is set so that the hash of the block will contain a run of leading zeros. The rest of the fields may not be changed, as they have a defined meaning.
     Off-chain Transaction
    An off-chain transaction is the movement of value outside of the blockchain. While an on-chain transaction - usually referred to as simply a transaction - modifies the blockchain and depends on the blockchain to determine its validity. An off-chain transaction relies on other methods to record and validate the transaction.
     Output
    Output, transaction output, or TxOut is an output in a Bitcoin transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
     P2PKH
    Many transactions processed on the Bitcoin network spend outputs locked with a Pay-to-Public-Key-Hash or P2PKH script. These outputs contain a locking script that locks the output to a public key hash, more commonly known as a Bitcoin address. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key.
     P2SH
    P2SH or Pay-to-Script-Hash is a type of transaction that simplifies the use of complex transaction scripts. With P2SH the complex script that details the spending conditions (redeem script) is committed to with a hash in the locking script.
     P2TR
    A pay-to-taproot (P2TR), also known as a Taproot or Bech32m address, is the most recent and advanced bitcoin address format. Taproot introduces more advanced security, privacy, flexibility and scaling to bitcoin.
     P2WPKH
    The signature of a P2WPKH (Pay-to-Witness-Public-Key-Hash) contains the same information as a P2PKH spending, but is located in the witness field instead of the scriptSig field.
     Paper Wallet
    In the most specific sense, a paper wallet is a document containing all the secrets to spend a Bitcoin UTXO. It is a way of storing bitcoin offline as a physical document.
     Partially Signed Bitcoin Transaction (PSBT)
    ',20),H={href:"https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki",target:"_blank",rel:"noopener noreferrer"},R=e("h3",{id:"pay-to-witness-public-key-hash-p2wpkh",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#pay-to-witness-public-key-hash-p2wpkh","aria-hidden":"true"},"#"),a(" Pay-to-Witness-Public-Key-Hash (P2WPKH)")],-1),F={href:"https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki",target:"_blank",rel:"noopener noreferrer"},K=o('
     Payment Channels
    A payment channel is class of techniques designed to allow users to make multiple Bitcoin transactions without committing all of the transactions to the Bitcoin blockchain. In a typical payment channel, only two transactions are added to the blockchain, one funding and one closing transaction, but a nearly unlimited number of payments can be made between the participants.
     Plausible deniability
    Plausible deniability is the ability to deny knowledge of or responsibility for any damnable actions committed by others in an organizational hierarchy because of a lack of evidence that can confirm their participation, even if they were personally involved in or at least willfully ignorant of the actions.
     Private Key
    ',5),D=e("h3",{id:"proof-of-work-pow",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#proof-of-work-pow","aria-hidden":"true"},"#"),a(" Proof of Work (POW)")],-1),N=e("p",null,"One of the requirements for a Bitcoin block to be valid is its hash should be below a certain difficulty target. In order to create a valid block, a miner must repeatedly hash a candidate block with a changing nonce until by sheer luck he finds a hash with low value. By providing this pre-image block, anyone can verify the amount of computational energy that a miner on average should have invested in order to find this block, and this is what is known as Proof of Work.",-1),O=e("h3",{id:"public-key",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#public-key","aria-hidden":"true"},"#"),a(" Public Key")],-1),M=o('
     Regtest
    A local testing environment in which developers can instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
     Replace by Fee (RBF)
    Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee.
     satoshi (sat)
    A satoshi is the smallest denomination of bitcoin that can be recorded on the blockchain. It is the equivalent of 0.00000001 bitcoin and is named after the creator of Bitcoin, Satoshi Nakamoto.
     Satoshi Nakamoto
    Satoshi Nakamoto is the name used by the person or group of people who designed Bitcoin and created its original reference implementation. As a part of the implementation, they also devised the first blockchain database. In the process they were the first to solve the double-spending problem for digital currency in a decentralized and self verifying nature. Their real identity remains unknown.
     Schnorr Digital Signature Scheme
    Schnorr Digital Signature Scheme is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners. Schnorr signatures and public keys can be aggregated, meaning that multiple parties with unique private keys can sign the same message, which can be verified in batches instead of individually.
     Script
    Bitcoin uses a scripting system for transactions. Forth-like, Script is simple, stack-based and processed from left to right. It is purposefully not Turing-complete, with no loops.
     ScriptPubKey
    ScriptPubKey or pubkey script, is a script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script.
     ScriptSig
    ScriptSig or signature script, is the data generated by a spender which is almost always used as variables to satisfy a pubkey script.
     Segregated Witness (SegWit)
    ',17),U=o('
     Simplified Payment Verification (SPV)
    SPV is a method for verifying particular transactions were included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
     Soft Fork
    A soft fork is a change to the Bitcoin consensus rules that is backwards compatible. Users of this update do not break the rules of legacy users, but rather restrict themselves to a more narrow rule set.
     Taproot
    Taproot is an upgrade to Bitcoin which introduces several new features. Taproot integrates the Schnorr digital signature scheme into Bitcoin, upgrading Bitcoin’s core cryptography. Taproot builds on the SegWit upgrade to improve Bitcoin’s privacy and lower transaction fees. Taproot makes future Bitcoin upgrades easier by reforming Bitcoin’s scripting language.
     Testnet
    A testing environment in which users can obtain and spend satoshis that have no real-world value on a global network that is very similar to the Bitcoin mainnet.
     Timechain
    ',9),Q=e("h3",{id:"transaction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction","aria-hidden":"true"},"#"),a(" Transaction")],-1),G=e("p",null,"In simple terms, a transfer of bitcoin. More precisely, a transaction is a signed data structure expressing a transfer of value and consisting mainly of inputs and outputs. Transactions are transmitted over the Bitcoin network, collected by miners, and included into blocks, made permanent on the blockchain.",-1),q=e("h3",{id:"transaction-fees",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-fees","aria-hidden":"true"},"#"),a(" Transaction Fees")],-1),z=e("code",null,"inputs - outputs",-1),E=e("h3",{id:"unspent-transaction-output-utxo",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#unspent-transaction-output-utxo","aria-hidden":"true"},"#"),a(" Unspent Transaction Output (UTXO)")],-1),L=e("h3",{id:"wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet","aria-hidden":"true"},"#"),a(" Wallet")],-1),j=e("p",null,"Software that holds all your Bitcoin addresses and secret keys. Use it to send, receive, and store your bitcoin.",-1);function V(X,J){const i=s("RouterLink"),r=s("ExternalLinkIcon");return c(),d("div",null,[u,p,e("p",null,[a("A Bitcoin invoice address commits to a public key or script which defines who can spend the coin. It is specified in the output of a transaction, and it should only be used once. Wasabi uses the bech32 and bech32m format to encode native segregated witness addresses. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin addresses")]),_:1})]),f,b,m,y,e("p",null,[a("Bitcoin Core consists of both "),g,a(" software for fully validating the blockchain as well as a Bitcoin wallet. The project also currently maintains related software such as the cryptography library libsecp256k1 and others located at GitHub. Read more: "),e("a",w,[a("Bitcoin Core Website"),t(r)])]),k,e("p",null,[a("Bitcoin Improvement Proposal. A design document for introducing features or information to Bitcoin. Read more: "),t(i,{to:"/using-wasabi/BIPs.html"},{default:n(()=>[a("Wasabi Supported BIPs")]),_:1})]),v,e("p",null,[a("Bitcoin Knots is a derivative of Bitcoin Core with a collection of improvements backported from and sometimes maintained outside of Core's master git tree. Since version 1.1.11, Wasabi has partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything. Read more: "),e("a",_,[a("Bitcoin Knots Website"),t(r)])]),x,e("p",null,[a("In a transaction where the provided input coins are larger than the value sent to the destination address, then the leftover change is sent to a new address of the same wallet. Read more: "),t(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[a("Change coins")]),_:1})]),B,e("p",null,[a("Refers to keeping a reserve of important Bitcoin secrets offline. Cold storage is achieved when Bitcoin private keys are created and stored in a secure offline environment. Cold storage is important for anyone with bitcoin holdings. Online computers are vulnerable to hackers and should not be used to store a significant amount of bitcoin. Read more: "),t(i,{to:"/using-wasabi/ColdWasabi.html"},{default:n(()=>[a("Cold Wasabi Protocol")]),_:1})]),P,e("p",null,[a("Fungibility is a desirable property of Bitcoin UTXOs that are indistinguishable from each other. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#attempt-to-destroy-fungibility"},{default:n(()=>[a("Transaction surveillance companies attempting to destroy fungibility")]),_:1})]),T,e("p",null,[a("A hardware wallet is a special type of Bitcoin wallet which generates and stores the user's private keys on a dedicated hardware device. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#hardware-wallet"},{default:n(()=>[a("Hardware Wallet FAQs")]),_:1})]),A,e("p",null,[a("The Bitcoin Mempool (memory pool) is a collection of all transaction data in a block that have been verified by Bitcoin nodes, but are not yet confirmed. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-does-wasabi-know-of-incoming-transactions-to-the-mempool"},{default:n(()=>[a("How does Wasabi know of incoming transactions to the mempool?")]),_:1})]),S,e("p",null,[a("Multisignature (m-of-n multisig) refers to requiring more than one key to authorize a Bitcoin transaction. Only with "),W,a(" signatures of "),I,a(" public keys can the bitcoin be spent. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#can-i-generate-a-multi-signature-script"},{default:n(()=>[a("Can I generate a multi signature script?")]),_:1})]),C,e("p",null,[a("PSBT is a binary transaction format which contains the information necessary for a signer to produce signatures for the transaction and holds the signatures for an input while the input does not have a complete set of signatures. The signer can be offline as all necessary information will be provided in the transaction. Read more: "),e("a",H,[a("BIP 174 Partially Signed Bitcoin Transaction Format"),t(r)])]),R,e("p",null,[a("The signature of a P2WPKH contains the same information as a Pay-to-Public-Key-Hash (P2PKH) spending, but is located in the witness field instead of the scriptSig field. The scriptPubKey is also modified. Read more: "),e("a",F,[a("BIP 84 derivation scheme for P2WPKH based accounts"),t(r)])]),K,e("p",null,[a("A private key is a large number that must be chosen at random, it is thus a very secure password and should be kept secret. With knowledge of this number, anyone can easily compute the public key, and a signature over any message. It can also be used to decrypt any message that was encrypted to the public key corresponding to the private key. In Bitcoin, a signature over a valid transaction message gives the right to spend a coin, thus knowledge of the private key corresponds to ownership of the bitcoin. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin private keys")]),_:1})]),D,N,O,e("p",null,[a("A public key is calculated by multiplying the private key to the generator point of an elliptic curve. Given only the public key, the private key cannot be calculated. Anyone can encrypt a message using a public key. This encrypted message (cyphertext) can only be decrypted through the related private key. Given a public key and a signature over a message, anyone can verify that the signer had the private key and the message. In Bitcoin, the public key is the pseudonymous identity of the owner of a coin. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin private keys")]),_:1})]),M,e("p",null,[a("Segregated Witness is a structure where the witness [signature or redeem script] is stored separately from the transaction Merkle tree. This is separated because the witness contains only data concerning transaction validity, but not about transaction effect. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#why-does-wasabi-only-use-segwit-bech32-addresses"},{default:n(()=>[a("Why Wasabi uses only SegWit")]),_:1})]),U,e("p",null,[a("Timechain is a synonym of "),t(i,{to:"/glossary/Glossary-GeneralBitcoin.html#blockchain"},{default:n(()=>[a("blockchain")]),_:1}),a(". It emphasizes the achievement of the Bitcoin protocol to establish consensus on the temporal order of transactions so to prevent double-spends.")]),Q,G,q,e("p",null,[a("A transaction has a fee payment to the miner who includes the transaction in a valid block. It is implied by the difference of "),z,a(". Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-fee-should-i-select"},{default:n(()=>[a("What fee should I select?")]),_:1})]),E,e("p",null,[a("UTXO is an unspent transaction output that can be spent as an input in a new transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-can-i-select-utxos-for-coinjoin"},{default:n(()=>[a("How can I select UTXOs for CoinJoin?")]),_:1})]),L,j])}const Z=h(l,[["render",V],["__file","Glossary-GeneralBitcoin.html.vue"]]);export{Z as default};
+import{_ as h,r as s,o as c,c as d,a as e,b as a,d as t,w as n,e as o}from"./app.65e5b6fd.js";const l={},u=e("h2",{id:"bitcoin-in-general",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-in-general","aria-hidden":"true"},"#"),a(" Bitcoin in general")],-1),p=e("h3",{id:"address",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#address","aria-hidden":"true"},"#"),a(" Address")],-1),f=e("h3",{id:"bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin","aria-hidden":"true"},"#"),a(" Bitcoin")],-1),b=e("p",null,"Bitcoin is a peer-to-peer electronic cash system. An innovative payment network and a new kind of money. It is a decentralized digital currency without a central bank or single administrator that can be sent from user to user on the peer-to-peer bitcoin blockchain network without the need for intermediaries.",-1),m=e("h3",{id:"bitcoin-core",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-core","aria-hidden":"true"},"#"),a(" Bitcoin Core")],-1),y=e("p",null,[a("Bitcoin Core is an open-source project which maintains and releases Bitcoin client software called "),e("code",null,"Bitcoin Core"),a(", considered to be Bitcoin's reference implementation. It is a direct descendant of the original Bitcoin software client released by Satoshi Nakamoto after he published the famous Bitcoin whitepaper.")],-1),g=e("code",null,"full-node",-1),w={href:"https://bitcoincore.org/",target:"_blank",rel:"noopener noreferrer"},k=e("h3",{id:"bitcoin-improvement-proposal-bip",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-improvement-proposal-bip","aria-hidden":"true"},"#"),a(" Bitcoin Improvement Proposal (BIP)")],-1),v=e("h3",{id:"bitcoin-knots",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bitcoin-knots","aria-hidden":"true"},"#"),a(" Bitcoin Knots")],-1),_={href:"https://bitcoinknots.org/",target:"_blank",rel:"noopener noreferrer"},x=o('
     Block
    A block is a batch of valid Bitcoin transactions and its hash must be a value below a certain difficulty target to prove the work of the miner. Each block references the hash of the previous block, thus creating a hash chain of blocks. On average a new block is mined every 10 minutes.
     Blockchain
    The blockchain is the one chain of valid Bitcoin blocks with the most accumulated proof of work. It is an append-only data structure with new blocks being added on average every 10 minutes. Because of its uniquely verifiable and global consensus, it is a revolutionary standard for time, thus some call it timechain.
     Change
    ',5),B=o('
     Child Pays For Parent (CPFP)
    Child Pays For Parent (CPFP) is a fee bumping technique where a user spends an output from a low fee rate unconfirmed transaction in a child transaction with a high fee rate in order to encourage miners to include both transactions in a block.
     Coinbase
    A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
     Coinbase Transaction
    The first transaction in a block. Always created by a miner, it includes a single coinbase.
     Cold Storage
    ',7),P=o('
     Confirmations
    Once a transaction is included in a block, it has one confirmation. As soon as another block is mined on the same blockchain, the transaction has two confirmations, and so on. Six or more confirmations is considered sufficient proof that a transaction cannot be reversed.
     Consensus
    When several nodes, usually most nodes on the network, all have the same blocks in their locally-validated best blockchain.
     Consensus Rules
    The block validation rules that full nodes follow to stay in consensus with other nodes.
     Custodial (Wallet or Mixer)
    A custodial wallet is any wallet where the private keys of your coins are in the hands of a third party. In essence, they operate similarly to traditional banks.
    A custodial mixer needs you to send your bitcoins to a central part before mixing. This means that you are at risk of being stolen from.
     Difficulty
    A network-wide setting that controls how much computation is required to produce a proof of work.
     Difficulty Retargeting (Difficulty Adjustment)
    A network-wide recalculation of the difficulty that occurs once every 2,016 blocks and considers the hashing power of the previous 2,016 blocks.
     Difficulty Target
    A difficulty at which all the computation in the network will find blocks approximately every 10 minutes. It specifies the numeric value the hash of a block must not be above to be considered a valid block.
     ECDSA
    ECDSA (Elliptic Curve Digital Signature Algorithm) is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners.
     Fork
    Fork, also known as accidental fork, occurs when two or more blocks have the same block height, forking the blockchain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
     Full node
    Any computer that connects to the Bitcoin network is called a node. Nodes that fully verify all of the rules of Bitcoin are called full nodes. Full nodes download every block and transaction and check them against Bitcoin's consensus rules.
     Fungibility
    ',22),T=o('
     Genesis Block
    The first block in the blockchain, used to initialize the cryptocurrency.
     Hard Fork
    Hard fork, also known as hard-forking change, is a permanent divergence in the blockchain, it occurs when non-upgraded nodes can not validate blocks created by upgraded nodes that follow newer consensus rules. The upgraded nodes break the rules of the legacy nodes. Not to be confused with fork, soft fork, software fork or Git fork.
     Hardware Wallet (HWW)
    ',5),A=o('
     Hash
    A cryptographic hash function takes any input of arbitrary size [the message] and computes a value of fixed size that is unique to the input, which is called a hash or a digest. If one bit of the input changes, the output will be completely different [avalanche effect]. And there are no two messages that result in the same hash [collision resistance]. The only way to get any given input, is by computing all possible inputs, it is a one-way function [pre-image resistance]. Bitcoin uses the SHA256 in many parts of the protocol.
     Hierarchical Deterministic (HD) Protocol
    The Hierarchical Deterministic key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy.
     Hierarchical Deterministitc (HD) Wallet
    Wallets using the Hierarchical Deterministic Protocol key creation and transfer protocol (BIP32).
     Hot Wallet
    A hot wallet is a software wallet that runs on a device which is connected to the Internet. Wasabi is a hot wallet by default.
     Input
    Input, transaction input, or TxIn is an input in a Bitcoin transaction which contains two fields: a unique transaction hash and an index number, which references one utxo of a previous transaction which is spent in this transaction.
     Lightning Network (LN)
    Lightning Network is a proposed implementation of Hashed Timelock Contracts (HTLCs) with bi-directional payment channels which allows payments to be securely routed across multiple peer-to-peer payment channels. This allows the formation of a network where any peer on the network can pay any other peer even if they don't directly have a channel open between each other.
     Mainnet
    The original and main network for Bitcoin transactions, where satoshis have real economic value.
     Mempool
    ',15),S=o('
     Merkle Root
    The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
     Merkle Tree
    A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
     Miner
    A Bitcoin user that attempts to find valid proof of work for new candidate blocks, by repeated hashing until the difficulty target is met.
     Mining Reward
    An amount of satoshis included in each new block as a reward by the network to the miner who found the proof of work solution. Initially it was 50 bitcoin per block, which is halved every 210 000 blocks, or roughly 4 years. This leads to a total money supply of just below 21 million bitcoin.
     Multisignature (multisig)
    ',9),W=e("code",null,"m",-1),I=e("code",null,"n",-1),C=o('
     Non-Custodial (Wallet or Mixer)
    A non-custodial wallet is any wallet where the private keys of your coins are in your hands. Non-custodial wallets give you full control over your bitcoins.
    A non-custodial mixer like Wasabi eliminates the risk that the coordinator can steal your bitcoin. Each participant verifies the proposed transaction, and signs it only if it is valid. This signature is only valid for this transaction, so any attempt to change the transaction after the fact is futile. The funds will always be in a Bitcoin address that you control.
     Nonce
    The nonce in a Bitcoin block is a 32-bit (4-byte) field whose value is set so that the hash of the block will contain a run of leading zeros. The rest of the fields may not be changed, as they have a defined meaning.
     Off-chain Transaction
    An off-chain transaction is the movement of value outside of the blockchain. While an on-chain transaction - usually referred to as simply a transaction - modifies the blockchain and depends on the blockchain to determine its validity. An off-chain transaction relies on other methods to record and validate the transaction.
     Output
    Output, transaction output, or TxOut is an output in a Bitcoin transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
     P2PKH
    Many transactions processed on the Bitcoin network spend outputs locked with a Pay-to-Public-Key-Hash or P2PKH script. These outputs contain a locking script that locks the output to a public key hash, more commonly known as a Bitcoin address. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key.
     P2SH
    P2SH or Pay-to-Script-Hash is a type of transaction that simplifies the use of complex transaction scripts. With P2SH the complex script that details the spending conditions (redeem script) is committed to with a hash in the locking script.
     P2TR
    A pay-to-taproot (P2TR), also known as a Taproot or Bech32m address, is the most recent and advanced bitcoin address format. Taproot introduces more advanced security, privacy, flexibility and scaling to bitcoin.
     P2WPKH
    The signature of a P2WPKH (Pay-to-Witness-Public-Key-Hash) contains the same information as a P2PKH spending, but is located in the witness field instead of the scriptSig field.
     Paper Wallet
    In the most specific sense, a paper wallet is a document containing all the secrets to spend a Bitcoin UTXO. It is a way of storing bitcoin offline as a physical document.
     Partially Signed Bitcoin Transaction (PSBT)
    ',20),H={href:"https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki",target:"_blank",rel:"noopener noreferrer"},R=e("h3",{id:"pay-to-witness-public-key-hash-p2wpkh",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#pay-to-witness-public-key-hash-p2wpkh","aria-hidden":"true"},"#"),a(" Pay-to-Witness-Public-Key-Hash (P2WPKH)")],-1),F={href:"https://github.com/bitcoin/bips/blob/master/bip-0084.mediawiki",target:"_blank",rel:"noopener noreferrer"},K=o('
     Payment Channels
    A payment channel is class of techniques designed to allow users to make multiple Bitcoin transactions without committing all of the transactions to the Bitcoin blockchain. In a typical payment channel, only two transactions are added to the blockchain, one funding and one closing transaction, but a nearly unlimited number of payments can be made between the participants.
     Plausible deniability
    Plausible deniability is the ability to deny knowledge of or responsibility for any damnable actions committed by others in an organizational hierarchy because of a lack of evidence that can confirm their participation, even if they were personally involved in or at least willfully ignorant of the actions.
     Private Key
    ',5),D=e("h3",{id:"proof-of-work-pow",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#proof-of-work-pow","aria-hidden":"true"},"#"),a(" Proof of Work (POW)")],-1),N=e("p",null,"One of the requirements for a Bitcoin block to be valid is its hash should be below a certain difficulty target. In order to create a valid block, a miner must repeatedly hash a candidate block with a changing nonce until by sheer luck he finds a hash with low value. By providing this pre-image block, anyone can verify the amount of computational energy that a miner on average should have invested in order to find this block, and this is what is known as Proof of Work.",-1),O=e("h3",{id:"public-key",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#public-key","aria-hidden":"true"},"#"),a(" Public Key")],-1),M=o('
     Regtest
    A local testing environment in which developers can instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
     Replace by Fee (RBF)
    Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee.
     satoshi (sat)
    A satoshi is the smallest denomination of bitcoin that can be recorded on the blockchain. It is the equivalent of 0.00000001 bitcoin and is named after the creator of Bitcoin, Satoshi Nakamoto.
     Satoshi Nakamoto
    Satoshi Nakamoto is the name used by the person or group of people who designed Bitcoin and created its original reference implementation. As a part of the implementation, they also devised the first blockchain database. In the process they were the first to solve the double-spending problem for digital currency in a decentralized and self verifying nature. Their real identity remains unknown.
     Schnorr Digital Signature Scheme
    Schnorr Digital Signature Scheme is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners. Schnorr signatures and public keys can be aggregated, meaning that multiple parties with unique private keys can sign the same message, which can be verified in batches instead of individually.
     Script
    Bitcoin uses a scripting system for transactions. Forth-like, Script is simple, stack-based and processed from left to right. It is purposefully not Turing-complete, with no loops.
     ScriptPubKey
    ScriptPubKey or pubkey script, is a script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script.
     ScriptSig
    ScriptSig or signature script, is the data generated by a spender which is almost always used as variables to satisfy a pubkey script.
     Segregated Witness (SegWit)
    ',17),U=o('
     Simplified Payment Verification (SPV)
    SPV is a method for verifying particular transactions were included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
     Soft Fork
    A soft fork is a change to the Bitcoin consensus rules that is backwards compatible. Users of this update do not break the rules of legacy users, but rather restrict themselves to a more narrow rule set.
     Taproot
    Taproot is an upgrade to Bitcoin which introduces several new features. Taproot integrates the Schnorr digital signature scheme into Bitcoin, upgrading Bitcoin’s core cryptography. Taproot builds on the SegWit upgrade to improve Bitcoin’s privacy and lower transaction fees. Taproot makes future Bitcoin upgrades easier by reforming Bitcoin’s scripting language.
     Testnet
    A testing environment in which users can obtain and spend satoshis that have no real-world value on a global network that is very similar to the Bitcoin mainnet.
     Timechain
    ',9),Q=e("h3",{id:"transaction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction","aria-hidden":"true"},"#"),a(" Transaction")],-1),G=e("p",null,"In simple terms, a transfer of bitcoin. More precisely, a transaction is a signed data structure expressing a transfer of value and consisting mainly of inputs and outputs. Transactions are transmitted over the Bitcoin network, collected by miners, and included into blocks, made permanent on the blockchain.",-1),q=e("h3",{id:"transaction-fees",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-fees","aria-hidden":"true"},"#"),a(" Transaction Fees")],-1),z=e("code",null,"inputs - outputs",-1),E=e("h3",{id:"unspent-transaction-output-utxo",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#unspent-transaction-output-utxo","aria-hidden":"true"},"#"),a(" Unspent Transaction Output (UTXO)")],-1),L=e("h3",{id:"wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet","aria-hidden":"true"},"#"),a(" Wallet")],-1),j=e("p",null,"Software that holds all your Bitcoin addresses and secret keys. Use it to send, receive, and store your bitcoin.",-1);function V(X,J){const i=s("RouterLink"),r=s("ExternalLinkIcon");return c(),d("div",null,[u,p,e("p",null,[a("A Bitcoin invoice address commits to a public key or script which defines who can spend the coin. It is specified in the output of a transaction, and it should only be used once. Wasabi uses the bech32 and bech32m format to encode native segregated witness addresses. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin addresses")]),_:1})]),f,b,m,y,e("p",null,[a("Bitcoin Core consists of both "),g,a(" software for fully validating the blockchain as well as a Bitcoin wallet. The project also currently maintains related software such as the cryptography library libsecp256k1 and others located at GitHub. Read more: "),e("a",w,[a("Bitcoin Core Website"),t(r)])]),k,e("p",null,[a("Bitcoin Improvement Proposal. A design document for introducing features or information to Bitcoin. Read more: "),t(i,{to:"/using-wasabi/BIPs.html"},{default:n(()=>[a("Wasabi Supported BIPs")]),_:1})]),v,e("p",null,[a("Bitcoin Knots is a derivative of Bitcoin Core with a collection of improvements backported from and sometimes maintained outside of Core's master git tree. Since version 1.1.11, Wasabi has partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything. Read more: "),e("a",_,[a("Bitcoin Knots Website"),t(r)])]),x,e("p",null,[a("In a transaction where the provided input coins are larger than the value sent to the destination address, then the leftover change is sent to a new address of the same wallet. Read more: "),t(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[a("Change coins")]),_:1})]),B,e("p",null,[a("Refers to keeping a reserve of important Bitcoin secrets offline. Cold storage is achieved when Bitcoin private keys are created and stored in a secure offline environment. Cold storage is important for anyone with bitcoin holdings. Online computers are vulnerable to hackers and should not be used to store a significant amount of bitcoin. Read more: "),t(i,{to:"/using-wasabi/ColdWasabi.html"},{default:n(()=>[a("Cold Wasabi Protocol")]),_:1})]),P,e("p",null,[a("Fungibility is a desirable property of Bitcoin UTXOs that are indistinguishable from each other. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#attempt-to-destroy-fungibility"},{default:n(()=>[a("Transaction surveillance companies attempting to destroy fungibility")]),_:1})]),T,e("p",null,[a("A hardware wallet is a special type of Bitcoin wallet which generates and stores the user's private keys on a dedicated hardware device. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#hardware-wallet"},{default:n(()=>[a("Hardware Wallet FAQs")]),_:1})]),A,e("p",null,[a("The Bitcoin Mempool (memory pool) is a collection of all transaction data in a block that have been verified by Bitcoin nodes, but are not yet confirmed. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-does-wasabi-know-of-incoming-transactions-to-the-mempool"},{default:n(()=>[a("How does Wasabi know of incoming transactions to the mempool?")]),_:1})]),S,e("p",null,[a("Multisignature (m-of-n multisig) refers to requiring more than one key to authorize a Bitcoin transaction. Only with "),W,a(" signatures of "),I,a(" public keys can the bitcoin be spent. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#can-i-generate-a-multi-signature-script"},{default:n(()=>[a("Can I generate a multi signature script?")]),_:1})]),C,e("p",null,[a("PSBT is a binary transaction format which contains the information necessary for a signer to produce signatures for the transaction and holds the signatures for an input while the input does not have a complete set of signatures. The signer can be offline as all necessary information will be provided in the transaction. Read more: "),e("a",H,[a("BIP 174 Partially Signed Bitcoin Transaction Format"),t(r)])]),R,e("p",null,[a("The signature of a P2WPKH contains the same information as a Pay-to-Public-Key-Hash (P2PKH) spending, but is located in the witness field instead of the scriptSig field. The scriptPubKey is also modified. Read more: "),e("a",F,[a("BIP 84 derivation scheme for P2WPKH based accounts"),t(r)])]),K,e("p",null,[a("A private key is a large number that must be chosen at random, it is thus a very secure password and should be kept secret. With knowledge of this number, anyone can easily compute the public key, and a signature over any message. It can also be used to decrypt any message that was encrypted to the public key corresponding to the private key. In Bitcoin, a signature over a valid transaction message gives the right to spend a coin, thus knowledge of the private key corresponds to ownership of the bitcoin. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin private keys")]),_:1})]),D,N,O,e("p",null,[a("A public key is calculated by multiplying the private key to the generator point of an elliptic curve. Given only the public key, the private key cannot be calculated. Anyone can encrypt a message using a public key. This encrypted message (cyphertext) can only be decrypted through the related private key. Given a public key and a signature over a message, anyone can verify that the signer had the private key and the message. In Bitcoin, the public key is the pseudonymous identity of the owner of a coin. Read more: "),t(i,{to:"/using-wasabi/Receive.html#bitcoin-public-keys-and-addresses"},{default:n(()=>[a("Bitcoin private keys")]),_:1})]),M,e("p",null,[a("Segregated Witness is a structure where the witness [signature or redeem script] is stored separately from the transaction Merkle tree. This is separated because the witness contains only data concerning transaction validity, but not about transaction effect. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#why-does-wasabi-only-use-segwit-bech32-addresses"},{default:n(()=>[a("Why Wasabi uses only SegWit")]),_:1})]),U,e("p",null,[a("Timechain is a synonym of "),t(i,{to:"/glossary/Glossary-GeneralBitcoin.html#blockchain"},{default:n(()=>[a("blockchain")]),_:1}),a(". It emphasizes the achievement of the Bitcoin protocol to establish consensus on the temporal order of transactions so to prevent double-spends.")]),Q,G,q,e("p",null,[a("A transaction has a fee payment to the miner who includes the transaction in a valid block. It is implied by the difference of "),z,a(". Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-fee-should-i-select"},{default:n(()=>[a("What fee should I select?")]),_:1})]),E,e("p",null,[a("UTXO is an unspent transaction output that can be spent as an input in a new transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-can-i-select-utxos-for-coinjoin"},{default:n(()=>[a("How can I select UTXOs for CoinJoin?")]),_:1})]),L,j])}const Z=h(l,[["render",V],["__file","Glossary-GeneralBitcoin.html.vue"]]);export{Z as default};
diff --git a/assets/Glossary-PrivacyWasabi.html.33993b7b.js b/assets/Glossary-PrivacyWasabi.html.0d4c3e98.js
similarity index 99%
rename from assets/Glossary-PrivacyWasabi.html.33993b7b.js
rename to assets/Glossary-PrivacyWasabi.html.0d4c3e98.js
index 4d18af19ca..30de16ee5e 100644
--- a/assets/Glossary-PrivacyWasabi.html.33993b7b.js
+++ b/assets/Glossary-PrivacyWasabi.html.0d4c3e98.js
@@ -1 +1 @@
-import{_ as h,r,o as c,c as d,a as e,b as a,d as t,w as n,e as s}from"./app.a5b7c2b2.js";const l={},u=s('
     Privacy and Wasabi
     #twoweeks
    The #twoweeks is a fun inside joke often used in the Wasabi documentation and, more generally, in the Internet community. In the case of Wasabi documentation, it usually indicates the arrival of a new function or update, to which the future date is still uncertain.
    E.g. "Lightning Network is coming to Wasabi in #twoweeks"
     Address Reuse
    ',5),m=e("h3",{id:"anonymity-score-anonscore",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-score-anonscore","aria-hidden":"true"},"#"),a(" Anonymity Score (anonscore)")],-1),b=e("h3",{id:"anonymity-set-anonset",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-set-anonset","aria-hidden":"true"},"#"),a(" Anonymity Set (anonset)")],-1),p=e("h3",{id:"backend",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#backend","aria-hidden":"true"},"#"),a(" Backend")],-1),f={href:"https://www.merriam-webster.com/dictionary/back%20end",target:"_blank",rel:"noopener noreferrer"},y=e("h3",{id:"block-filters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#block-filters","aria-hidden":"true"},"#"),a(" Block filters")],-1),w={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},_=e("h3",{id:"blockchain-analysis",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#blockchain-analysis","aria-hidden":"true"},"#"),a(" Blockchain Analysis")],-1),g=e("h3",{id:"bloom-filter",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bloom-filter","aria-hidden":"true"},"#"),a(" Bloom Filter")],-1),k={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=e("h3",{id:"change-address-detection",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-address-detection","aria-hidden":"true"},"#"),a(" Change Address Detection")],-1),x=e("h3",{id:"chaumian-coinjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#chaumian-coinjoin","aria-hidden":"true"},"#"),a(" Chaumian CoinJoin")],-1),C=e("h3",{id:"client",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#client","aria-hidden":"true"},"#"),a(" Client")],-1),W={href:"https://www.merriam-webster.com/dictionary/client",target:"_blank",rel:"noopener noreferrer"},A=e("h3",{id:"cluster",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#cluster","aria-hidden":"true"},"#"),a(" Cluster")],-1),T=e("h3",{id:"coin-control",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coin-control","aria-hidden":"true"},"#"),a(" Coin Control")],-1),R=e("h3",{id:"coinjoin-cj",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-cj","aria-hidden":"true"},"#"),a(" CoinJoin (CJ)")],-1),B=e("h3",{id:"coinjoin-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-strategy","aria-hidden":"true"},"#"),a(" Coinjoin Strategy")],-1),P=e("em",null,"Coinjoin Strategy",-1),F=e("h3",{id:"coinjoined-coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoined-coins","aria-hidden":"true"},"#"),a(" CoinJoined coins")],-1),I=e("h3",{id:"common-input-ownership-heuristic",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#common-input-ownership-heuristic","aria-hidden":"true"},"#"),a(" Common-Input-Ownership heuristic")],-1),j=e("p",null,"This is a heuristic or assumption which says that if a transaction has more than one input then all those inputs are owned by the same entity.",-1),S=e("h3",{id:"coordinator",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coordinator","aria-hidden":"true"},"#"),a(" Coordinator")],-1),Q=e("h3",{id:"daemon",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#daemon","aria-hidden":"true"},"#"),a(" Daemon")],-1),J=e("h3",{id:"discreet-mode",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#discreet-mode","aria-hidden":"true"},"#"),a(" Discreet Mode")],-1),U=e("h3",{id:"dust",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#dust","aria-hidden":"true"},"#"),a(" Dust")],-1),L=e("code",null,"forced address reuse attack",-1),z=e("h3",{id:"label",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#label","aria-hidden":"true"},"#"),a(" Label")],-1),D=e("h3",{id:"know-your-customer-kyc",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#know-your-customer-kyc","aria-hidden":"true"},"#"),a(" Know Your Customer (KYC)")],-1),q=e("h3",{id:"observers",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#observers","aria-hidden":"true"},"#"),a(" Observers")],-1),E=s('
     Pay to EndPoint (P2EP)
    Pay to EndPoint is when the receiver is reachable over the internet and the sender communicates with the receiver to coordinate a more advanced transaction. The Tor onion service, IP address or domain of the receiver is included in a BIP21 Bitcoin URI payment link.
     Peers
    Peers in our documentation refers mainly to Bitcoin and Wasabi Wallet users, but it also means people. They are literally peers in the network, or in the CoinJoin.
     RPC
    ',5),K=e("h3",{id:"taint",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#taint","aria-hidden":"true"},"#"),a(" Taint")],-1),O=e("h3",{id:"the-onion-router-tor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-onion-router-tor","aria-hidden":"true"},"#"),a(" The Onion Router (Tor)")],-1),G=e("h3",{id:"transaction-surveillance-company",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-surveillance-company","aria-hidden":"true"},"#"),a(" Transaction Surveillance Company")],-1),M=e("h3",{id:"tumbling-tumbler",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#tumbling-tumbler","aria-hidden":"true"},"#"),a(" Tumbling / Tumbler")],-1),N=e("p",null,"Tumbling is a synonym of 'Mixing'. Similarly, Tumbler is the synonym of 'Mixer'.",-1),X=e("h3",{id:"turbosync",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#turbosync","aria-hidden":"true"},"#"),a(" TurboSync")],-1),Y=e("h3",{id:"wabisabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wabisabi","aria-hidden":"true"},"#"),a(" WabiSabi")],-1),V={href:"https://github.com/zkSNACKs/WabiSabi/releases/latest/download/WabiSabi.pdf",target:"_blank",rel:"noopener noreferrer"},H=s('
     Wallet fingerprinting
    A careful analyst sometimes deduces which software created a certain transaction, because many different wallet softwares don't always create transactions in exactly the same way.
     Wasabika
    Wasabikas are builders, users and supporters of Wasabi in general.
     XPUB (Extended Public Key)
    An xpub, also known as Extended Public Key, is a part of BIP-32 that will allow you to observe your wallet without the private key (xpriv).
    ',7);function Z($,ee){const i=r("RouterLink"),o=r("ExternalLinkIcon");return c(),d("div",null,[u,e("p",null,[a("Address reuse refers to the use of the same address for multiple transactions, this is very bad for privacy. Read more: "),t(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[a("Address reuse")]),_:1})]),m,e("p",null,[a("Anonymity score is a new way to estimate the entropy level of a UTXO in an unequal-but-highly-composable output value coinjoin. The anonymity score is a metric to help the wallet decide when it's time to stop the coinjoining process. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-anonymity-score"},{default:n(()=>[a("What is the anonymity score?")]),_:1})]),b,e("p",null,[a("The anonymity set is effectively the size of the group you are hiding in during a CoinJoin. It's the quantity of equal value outputs of one CoinJoin transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-anonymity-set"},{default:n(()=>[a("What is the anonymity set?")]),_:1})]),p,e("p",null,[e("a",f,[a("The part of a software system that is not usually visible or accessible to a user of that system"),t(o)]),a(". In the case of Wasabi, the backend functions as the coinjoin coordinator and provides data to the "),t(i,{to:"/glossary/Glossary-PrivacyWasabi.html#Client"},{default:n(()=>[a("client")]),_:1}),a(" (user) like block filters, exchange rate, and network estimations (mempool).")]),y,e("p",null,[a("A filter representing a compact list of addresses in one block. Wasabi checks locally if any block filter contains transactions with addresses of the wallet. No public keys are sent to any third party server, thus it is very private. Read more: "),e("a",w,[a("BIP 158: Compact Block Filters for Light Clients"),t(o)])]),_,e("p",null,[a("Blockchain analysis is used by transaction surveillance companies to follow the transaction history of coins. Techniques like the common-input-ownership heuristic or change detection are used to create a cluster of transactions belonging to one user. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#blockchain-analysis"},{default:n(()=>[a("Blockchain Analysis")]),_:1})]),g,e("p",null,[a("A filter used primarily by SPV clients to request only block headers and merkle proofs of a given transaction from full nodes. This is very bad for privacy, as third party servers learn about which addresses you are interested in. Read more: "),e("a",k,[a("BIP 37: Connection Bloom Filtering"),t(o)])]),v,e("p",null,[a("Many Bitcoin transactions have change outputs. It would be a serious privacy leak if the change address can be somehow found, as it would link the ownership of the (now spent) inputs with a new output. Read more: "),t(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[a("Change coins")]),_:1})]),x,e("p",null,[a("A Chaumian CoinJoin is a special type of CoinJoin that utilizes Chaumian [or Schnorr] blind signatures to prevent the central coordinator from spying on the linkage between inputs and outputs. Read more: "),t(i,{to:"/using-wasabi/CoinJoin.html#zerolink-protocol-step-by-step"},{default:n(()=>[a("Use of blind signatures in CoinJoin")]),_:1})]),C,e("p",null,[e("a",W,[a("A software that allows a computer to function as a client in a network"),t(o)]),a(". In the case of Wasabi, the client is a Wasabi Wallet software version which a user has on his own local machine. The client can communicate with the "),t(i,{to:"/glossary/Glossary-PrivacyWasabi.html#Backend"},{default:n(()=>[a("backend")]),_:1}),a(".")]),A,e("p",null,[a("Which entities know about which coins. For example, this coin belongs to a cluster that is known by a KYC exchange and Alice. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-cluster-history"},{default:n(()=>[a("What is the cluster history?")]),_:1})]),T,e("p",null,[a("The possiblity for the user to manually select UTXO's. It is mostly used for sending, so the user can select which UTXO's should be used as the inputs of the transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#coin-control-best-practices"},{default:n(()=>[a("Coin Control Best Practices")]),_:1})]),R,e("p",null,[a("CoinJoin is a trustless method for combining multiple Bitcoin payments from multiple spenders into a single transaction to make it more difficult for outside parties to determine which spender paid which recipient. Read more: "),t(i,{to:"/FAQ/FAQ-Introduction.html#what-is-a-coinjoin"},{default:n(()=>[a("What is a CoinJoin?")]),_:1})]),B,e("p",null,[a("A "),P,a(' contains instructions for the automatic "coinjoin robot" about configurations like when and how much to coinjoin. Read more: '),t(i,{to:"/Using-Wasabi/CoinJoin.html#coinjoin-strategy"},{default:n(()=>[a("Coinjoin Strategy")]),_:1})]),F,e("p",null,[a("Coins that have successfully participated in a CoinJoin (with the exception of the change) and thus lose their association to a previous cluster. Read more: "),t(i,{to:"/FAQ/FAQ-Introduction.html#what-is-the-privacy-i-get-after-mixing-with-wasabi"},{default:n(()=>[a("What is the privacy I get after mixing with Wasabi?")]),_:1})]),I,j,S,e("p",null,[a("The coordinator is a server which creates CoinJoins and accepts UTXOs in the mix. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-does-my-wallet-communicate-with-the-wasabi-coordinator-server"},{default:n(()=>[a("How does my wallet communicate with the Wasabi coordinator server?")]),_:1})]),Q,e("p",null,[a("A daemon is a command line interface to run Wasabi without the GUI (Graphical User Interface). Read more: "),t(i,{to:"/using-wasabi/Daemon.html"},{default:n(()=>[a("Headless Wasabi Daemon")]),_:1})]),J,e("p",null,[a("Discreet Mode is a Wasabi feature that hides sensitive and critical information on the wallet itself, which is useful for screenshots. Read more: "),t(i,{to:"/using-wasabi/DiscreetMode.html"},{default:n(()=>[a("Discreet Mode")]),_:1})]),U,e("p",null,[a("Dust is an UTXO that is uneconomical to spend. Also, small portions of bitcoin can lead to serious consequences for one's privacy, for example the so called "),L,a(". Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-dust-threshold"},{default:n(()=>[a("What is the dust threshold")]),_:1})]),z,e("p",null,[a("A label can be added to a coin, as a small note on who knows this coin belongs to you. Good labelling can help the user and the wallet to make better privacy conscious decisions later on when spending. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#why-do-i-have-to-label-my-address"},{default:n(()=>[a("Why do I have to label my address")]),_:1})]),D,e("p",null,[a("KYC (Know Your Customer) is the process of a business being forced to identify and verify the identity of its clients, and to share this information with a government. The term is also used to refer to the bank regulation which governs these activities. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#aml-kyc-information"},{default:n(()=>[a("AML/KYC Information")]),_:1})]),q,e("p",null,[a("A way to track who knows about the ownership of your coins. Not to be confused with a description of a transaction. Read more: "),t(i,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[a("The importance of labeling")]),_:1})]),E,e("p",null,[a("RPC, or Remote Procedure Call, is an interface to interact with Wasabi Wallet programmatically. Read more: "),t(i,{to:"/using-wasabi/RPC.html"},{default:n(()=>[a("RPC Interface")]),_:1})]),K,e("p",null,[a("Taint is equivalent to the 'trail' that a Bitcoin transaction leaves during the course of its journey. The taint analysis of a Bitcoin transaction evaluates the association between an address involved in the chain of transactions. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#blockchain-analysis"},{default:n(()=>[a("Blockchain Analysis")]),_:1})]),O,e("p",null,[a("Tor (The Onion Router) is free and open-source software for enabling anonymous communication. It is widely used by Wasabi. Read more: "),t(i,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html#how-does-tor-protect-my-network-level-privacy"},{default:n(()=>[a("How does Tor protect my network level privacy?")]),_:1})]),G,e("p",null,[a("A transaction surveillance company is one which attempts to spy on all Bitcoin users. Their business model is usually to sell the data to any government, corporation or individual willing to pay for their services. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html"},{default:n(()=>[a("Transaction Surveillance Companies")]),_:1})]),M,N,X,e("p",null,[a("A feature in Wasabi to reduce wallet loading time. With TurboSync, some addresses (internal keys only) are skipped and tested in the background. Read more: "),t(i,{to:"/using-wasabi/WalletLoad.html#turbosync"},{default:n(()=>[a("TurboSync")]),_:1})]),Y,e("p",null,[a("WabiSabi is a protocol for constructing coinjoin transactions with the aid of a centralized coordinator. It utilizes keyed-verification anonymous credentials, homomorphic value commitments, and zero knowledge proofs to achieve privacy and flexibility. Read more: "),e("a",V,[a("WabiSabi"),t(o)])]),H,e("p",null,[a("ZeroLink is a framework to holistically design a privacy and fungibility setup for Bitcoin. This encompasses more than just a single CoinJoin transaction, but also includes network level privacy defense against third party spying. Read more: "),t(i,{to:"/using-wasabi/CoinJoin.html#zerolink-protocol-step-by-step"},{default:n(()=>[a("ZeroLink: the Bitcoin Fungibility Framework")]),_:1})])])}const te=h(l,[["render",Z],["__file","Glossary-PrivacyWasabi.html.vue"]]);export{te as default};
+import{_ as h,r,o as c,c as d,a as e,b as a,d as t,w as n,e as s}from"./app.65e5b6fd.js";const l={},u=s('
     Privacy and Wasabi
     #twoweeks
    The #twoweeks is a fun inside joke often used in the Wasabi documentation and, more generally, in the Internet community. In the case of Wasabi documentation, it usually indicates the arrival of a new function or update, to which the future date is still uncertain.
    E.g. "Lightning Network is coming to Wasabi in #twoweeks"
     Address Reuse
    ',5),m=e("h3",{id:"anonymity-score-anonscore",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-score-anonscore","aria-hidden":"true"},"#"),a(" Anonymity Score (anonscore)")],-1),b=e("h3",{id:"anonymity-set-anonset",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-set-anonset","aria-hidden":"true"},"#"),a(" Anonymity Set (anonset)")],-1),p=e("h3",{id:"backend",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#backend","aria-hidden":"true"},"#"),a(" Backend")],-1),f={href:"https://www.merriam-webster.com/dictionary/back%20end",target:"_blank",rel:"noopener noreferrer"},y=e("h3",{id:"block-filters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#block-filters","aria-hidden":"true"},"#"),a(" Block filters")],-1),w={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},_=e("h3",{id:"blockchain-analysis",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#blockchain-analysis","aria-hidden":"true"},"#"),a(" Blockchain Analysis")],-1),g=e("h3",{id:"bloom-filter",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#bloom-filter","aria-hidden":"true"},"#"),a(" Bloom Filter")],-1),k={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=e("h3",{id:"change-address-detection",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#change-address-detection","aria-hidden":"true"},"#"),a(" Change Address Detection")],-1),x=e("h3",{id:"chaumian-coinjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#chaumian-coinjoin","aria-hidden":"true"},"#"),a(" Chaumian CoinJoin")],-1),C=e("h3",{id:"client",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#client","aria-hidden":"true"},"#"),a(" Client")],-1),W={href:"https://www.merriam-webster.com/dictionary/client",target:"_blank",rel:"noopener noreferrer"},A=e("h3",{id:"cluster",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#cluster","aria-hidden":"true"},"#"),a(" Cluster")],-1),T=e("h3",{id:"coin-control",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coin-control","aria-hidden":"true"},"#"),a(" Coin Control")],-1),R=e("h3",{id:"coinjoin-cj",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-cj","aria-hidden":"true"},"#"),a(" CoinJoin (CJ)")],-1),B=e("h3",{id:"coinjoin-strategy",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-strategy","aria-hidden":"true"},"#"),a(" Coinjoin Strategy")],-1),P=e("em",null,"Coinjoin Strategy",-1),F=e("h3",{id:"coinjoined-coins",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoined-coins","aria-hidden":"true"},"#"),a(" CoinJoined coins")],-1),I=e("h3",{id:"common-input-ownership-heuristic",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#common-input-ownership-heuristic","aria-hidden":"true"},"#"),a(" Common-Input-Ownership heuristic")],-1),j=e("p",null,"This is a heuristic or assumption which says that if a transaction has more than one input then all those inputs are owned by the same entity.",-1),S=e("h3",{id:"coordinator",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coordinator","aria-hidden":"true"},"#"),a(" Coordinator")],-1),Q=e("h3",{id:"daemon",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#daemon","aria-hidden":"true"},"#"),a(" Daemon")],-1),J=e("h3",{id:"discreet-mode",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#discreet-mode","aria-hidden":"true"},"#"),a(" Discreet Mode")],-1),U=e("h3",{id:"dust",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#dust","aria-hidden":"true"},"#"),a(" Dust")],-1),L=e("code",null,"forced address reuse attack",-1),z=e("h3",{id:"label",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#label","aria-hidden":"true"},"#"),a(" Label")],-1),D=e("h3",{id:"know-your-customer-kyc",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#know-your-customer-kyc","aria-hidden":"true"},"#"),a(" Know Your Customer (KYC)")],-1),q=e("h3",{id:"observers",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#observers","aria-hidden":"true"},"#"),a(" Observers")],-1),E=s('
     Pay to EndPoint (P2EP)
    Pay to EndPoint is when the receiver is reachable over the internet and the sender communicates with the receiver to coordinate a more advanced transaction. The Tor onion service, IP address or domain of the receiver is included in a BIP21 Bitcoin URI payment link.
     Peers
    Peers in our documentation refers mainly to Bitcoin and Wasabi Wallet users, but it also means people. They are literally peers in the network, or in the CoinJoin.
     RPC
    ',5),K=e("h3",{id:"taint",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#taint","aria-hidden":"true"},"#"),a(" Taint")],-1),O=e("h3",{id:"the-onion-router-tor",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-onion-router-tor","aria-hidden":"true"},"#"),a(" The Onion Router (Tor)")],-1),G=e("h3",{id:"transaction-surveillance-company",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-surveillance-company","aria-hidden":"true"},"#"),a(" Transaction Surveillance Company")],-1),M=e("h3",{id:"tumbling-tumbler",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#tumbling-tumbler","aria-hidden":"true"},"#"),a(" Tumbling / Tumbler")],-1),N=e("p",null,"Tumbling is a synonym of 'Mixing'. Similarly, Tumbler is the synonym of 'Mixer'.",-1),X=e("h3",{id:"turbosync",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#turbosync","aria-hidden":"true"},"#"),a(" TurboSync")],-1),Y=e("h3",{id:"wabisabi",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wabisabi","aria-hidden":"true"},"#"),a(" WabiSabi")],-1),V={href:"https://github.com/zkSNACKs/WabiSabi/releases/latest/download/WabiSabi.pdf",target:"_blank",rel:"noopener noreferrer"},H=s('
     Wallet fingerprinting
    A careful analyst sometimes deduces which software created a certain transaction, because many different wallet softwares don't always create transactions in exactly the same way.
     Wasabika
    Wasabikas are builders, users and supporters of Wasabi in general.
     XPUB (Extended Public Key)
    An xpub, also known as Extended Public Key, is a part of BIP-32 that will allow you to observe your wallet without the private key (xpriv).
    ',7);function Z($,ee){const i=r("RouterLink"),o=r("ExternalLinkIcon");return c(),d("div",null,[u,e("p",null,[a("Address reuse refers to the use of the same address for multiple transactions, this is very bad for privacy. Read more: "),t(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[a("Address reuse")]),_:1})]),m,e("p",null,[a("Anonymity score is a new way to estimate the entropy level of a UTXO in an unequal-but-highly-composable output value coinjoin. The anonymity score is a metric to help the wallet decide when it's time to stop the coinjoining process. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-anonymity-score"},{default:n(()=>[a("What is the anonymity score?")]),_:1})]),b,e("p",null,[a("The anonymity set is effectively the size of the group you are hiding in during a CoinJoin. It's the quantity of equal value outputs of one CoinJoin transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-anonymity-set"},{default:n(()=>[a("What is the anonymity set?")]),_:1})]),p,e("p",null,[e("a",f,[a("The part of a software system that is not usually visible or accessible to a user of that system"),t(o)]),a(". In the case of Wasabi, the backend functions as the coinjoin coordinator and provides data to the "),t(i,{to:"/glossary/Glossary-PrivacyWasabi.html#Client"},{default:n(()=>[a("client")]),_:1}),a(" (user) like block filters, exchange rate, and network estimations (mempool).")]),y,e("p",null,[a("A filter representing a compact list of addresses in one block. Wasabi checks locally if any block filter contains transactions with addresses of the wallet. No public keys are sent to any third party server, thus it is very private. Read more: "),e("a",w,[a("BIP 158: Compact Block Filters for Light Clients"),t(o)])]),_,e("p",null,[a("Blockchain analysis is used by transaction surveillance companies to follow the transaction history of coins. Techniques like the common-input-ownership heuristic or change detection are used to create a cluster of transactions belonging to one user. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#blockchain-analysis"},{default:n(()=>[a("Blockchain Analysis")]),_:1})]),g,e("p",null,[a("A filter used primarily by SPV clients to request only block headers and merkle proofs of a given transaction from full nodes. This is very bad for privacy, as third party servers learn about which addresses you are interested in. Read more: "),e("a",k,[a("BIP 37: Connection Bloom Filtering"),t(o)])]),v,e("p",null,[a("Many Bitcoin transactions have change outputs. It would be a serious privacy leak if the change address can be somehow found, as it would link the ownership of the (now spent) inputs with a new output. Read more: "),t(i,{to:"/using-wasabi/ChangeCoins.html"},{default:n(()=>[a("Change coins")]),_:1})]),x,e("p",null,[a("A Chaumian CoinJoin is a special type of CoinJoin that utilizes Chaumian [or Schnorr] blind signatures to prevent the central coordinator from spying on the linkage between inputs and outputs. Read more: "),t(i,{to:"/using-wasabi/CoinJoin.html#zerolink-protocol-step-by-step"},{default:n(()=>[a("Use of blind signatures in CoinJoin")]),_:1})]),C,e("p",null,[e("a",W,[a("A software that allows a computer to function as a client in a network"),t(o)]),a(". In the case of Wasabi, the client is a Wasabi Wallet software version which a user has on his own local machine. The client can communicate with the "),t(i,{to:"/glossary/Glossary-PrivacyWasabi.html#Backend"},{default:n(()=>[a("backend")]),_:1}),a(".")]),A,e("p",null,[a("Which entities know about which coins. For example, this coin belongs to a cluster that is known by a KYC exchange and Alice. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-cluster-history"},{default:n(()=>[a("What is the cluster history?")]),_:1})]),T,e("p",null,[a("The possiblity for the user to manually select UTXO's. It is mostly used for sending, so the user can select which UTXO's should be used as the inputs of the transaction. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#coin-control-best-practices"},{default:n(()=>[a("Coin Control Best Practices")]),_:1})]),R,e("p",null,[a("CoinJoin is a trustless method for combining multiple Bitcoin payments from multiple spenders into a single transaction to make it more difficult for outside parties to determine which spender paid which recipient. Read more: "),t(i,{to:"/FAQ/FAQ-Introduction.html#what-is-a-coinjoin"},{default:n(()=>[a("What is a CoinJoin?")]),_:1})]),B,e("p",null,[a("A "),P,a(' contains instructions for the automatic "coinjoin robot" about configurations like when and how much to coinjoin. Read more: '),t(i,{to:"/Using-Wasabi/CoinJoin.html#coinjoin-strategy"},{default:n(()=>[a("Coinjoin Strategy")]),_:1})]),F,e("p",null,[a("Coins that have successfully participated in a CoinJoin (with the exception of the change) and thus lose their association to a previous cluster. Read more: "),t(i,{to:"/FAQ/FAQ-Introduction.html#what-is-the-privacy-i-get-after-mixing-with-wasabi"},{default:n(()=>[a("What is the privacy I get after mixing with Wasabi?")]),_:1})]),I,j,S,e("p",null,[a("The coordinator is a server which creates CoinJoins and accepts UTXOs in the mix. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#how-does-my-wallet-communicate-with-the-wasabi-coordinator-server"},{default:n(()=>[a("How does my wallet communicate with the Wasabi coordinator server?")]),_:1})]),Q,e("p",null,[a("A daemon is a command line interface to run Wasabi without the GUI (Graphical User Interface). Read more: "),t(i,{to:"/using-wasabi/Daemon.html"},{default:n(()=>[a("Headless Wasabi Daemon")]),_:1})]),J,e("p",null,[a("Discreet Mode is a Wasabi feature that hides sensitive and critical information on the wallet itself, which is useful for screenshots. Read more: "),t(i,{to:"/using-wasabi/DiscreetMode.html"},{default:n(()=>[a("Discreet Mode")]),_:1})]),U,e("p",null,[a("Dust is an UTXO that is uneconomical to spend. Also, small portions of bitcoin can lead to serious consequences for one's privacy, for example the so called "),L,a(". Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#what-is-the-dust-threshold"},{default:n(()=>[a("What is the dust threshold")]),_:1})]),z,e("p",null,[a("A label can be added to a coin, as a small note on who knows this coin belongs to you. Good labelling can help the user and the wallet to make better privacy conscious decisions later on when spending. Read more: "),t(i,{to:"/FAQ/FAQ-UseWasabi.html#why-do-i-have-to-label-my-address"},{default:n(()=>[a("Why do I have to label my address")]),_:1})]),D,e("p",null,[a("KYC (Know Your Customer) is the process of a business being forced to identify and verify the identity of its clients, and to share this information with a government. The term is also used to refer to the bank regulation which governs these activities. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#aml-kyc-information"},{default:n(()=>[a("AML/KYC Information")]),_:1})]),q,e("p",null,[a("A way to track who knows about the ownership of your coins. Not to be confused with a description of a transaction. Read more: "),t(i,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[a("The importance of labeling")]),_:1})]),E,e("p",null,[a("RPC, or Remote Procedure Call, is an interface to interact with Wasabi Wallet programmatically. Read more: "),t(i,{to:"/using-wasabi/RPC.html"},{default:n(()=>[a("RPC Interface")]),_:1})]),K,e("p",null,[a("Taint is equivalent to the 'trail' that a Bitcoin transaction leaves during the course of its journey. The taint analysis of a Bitcoin transaction evaluates the association between an address involved in the chain of transactions. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html#blockchain-analysis"},{default:n(()=>[a("Blockchain Analysis")]),_:1})]),O,e("p",null,[a("Tor (The Onion Router) is free and open-source software for enabling anonymous communication. It is widely used by Wasabi. Read more: "),t(i,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html#how-does-tor-protect-my-network-level-privacy"},{default:n(()=>[a("How does Tor protect my network level privacy?")]),_:1})]),G,e("p",null,[a("A transaction surveillance company is one which attempts to spy on all Bitcoin users. Their business model is usually to sell the data to any government, corporation or individual willing to pay for their services. Read more: "),t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html"},{default:n(()=>[a("Transaction Surveillance Companies")]),_:1})]),M,N,X,e("p",null,[a("A feature in Wasabi to reduce wallet loading time. With TurboSync, some addresses (internal keys only) are skipped and tested in the background. Read more: "),t(i,{to:"/using-wasabi/WalletLoad.html#turbosync"},{default:n(()=>[a("TurboSync")]),_:1})]),Y,e("p",null,[a("WabiSabi is a protocol for constructing coinjoin transactions with the aid of a centralized coordinator. It utilizes keyed-verification anonymous credentials, homomorphic value commitments, and zero knowledge proofs to achieve privacy and flexibility. Read more: "),e("a",V,[a("WabiSabi"),t(o)])]),H,e("p",null,[a("ZeroLink is a framework to holistically design a privacy and fungibility setup for Bitcoin. This encompasses more than just a single CoinJoin transaction, but also includes network level privacy defense against third party spying. Read more: "),t(i,{to:"/using-wasabi/CoinJoin.html#zerolink-protocol-step-by-step"},{default:n(()=>[a("ZeroLink: the Bitcoin Fungibility Framework")]),_:1})])])}const te=h(l,[["render",Z],["__file","Glossary-PrivacyWasabi.html.vue"]]);export{te as default};
diff --git a/assets/InstallPackage.html.d192894b.js b/assets/InstallPackage.html.9c7f413a.js
similarity index 99%
rename from assets/InstallPackage.html.d192894b.js
rename to assets/InstallPackage.html.9c7f413a.js
index 1d0fcad52c..a3b852525e 100644
--- a/assets/InstallPackage.html.d192894b.js
+++ b/assets/InstallPackage.html.9c7f413a.js
@@ -1 +1 @@
-import{b as h,c as u,d,_ as p,a as f}from"./DownloadMac.90ece9d0.js";import{_ as c}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as b,r,o as _,c as g,a as e,d as o,w as i,b as t,e as s}from"./app.a5b7c2b2.js";const w="/DownloadAll.png",m={},y=e("h1",{id:"install-package",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-package","aria-hidden":"true"},"#"),t(" Install package")],-1),k={class:"table-of-contents"},W=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),t(" Introduction")],-1),v={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},P={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},A=e("p",null,[e("img",{src:w,alt:"Operating systems supported by Wasabi Wallet",title:"Operating systems supported by Wasabi Wallet"})],-1),x=e("strong",null,"VERIFY PGP SIGNATURES",-1),I={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},S={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},N={href:"https://security.stackexchange.com/questions/147447/gpg-why-is-my-trusted-key-not-certified-with-a-trusted-signature",target:"_blank",rel:"noopener noreferrer"},D={href:"https://www.gnupg.org/gph/en/manual/x334.html",target:"_blank",rel:"noopener noreferrer"},z=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Always"),e("p",null,"Don't trust - Verify!")],-1),G=e("h2",{id:"install-wasabi-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-wasabi-step-by-step","aria-hidden":"true"},"#"),t(" Install Wasabi step-by-step")],-1),C={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},K=e("li",null,"Verify the PGP signatures of the download.",-1),F=e("li",null,"Install Wasabi package as you would do any other software on your operating system.",-1),T=e("hr",null,null,-1),B=e("h2",{id:"windows",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#windows","aria-hidden":"true"},"#"),t(" Windows")],-1),E={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},O=e("code",null,".msi",-1),Q=e("p",null,[e("img",{src:h,alt:"Download Wasabi Wallet for Windows",title:"Download Wasabi Wallet for Windows"})],-1),V=e("ol",{start:"2"},[e("li",null,[e("p",null,[t("Install Wasabi by double-clicking the "),e("code",null,".msi"),t(" and following the GUI instructions.")])]),e("li",null,[e("p",null,"Make sure that you see this window that verifies the installer was signed by zkSNACKs Limited. Manual PGP verification is optional, as the package is signed and verified automatically on Windows.")])],-1),L=e("p",null,[e("img",{src:u,alt:"Wasabi Wallet Windows signature verification",title:"Wasabi Wallet Windows signature verification"})],-1),U=e("code",null,"C:\\Program Files\\WasabiWallet\\",-1),R=e("h2",{id:"debian-and-ubuntu",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#debian-and-ubuntu","aria-hidden":"true"},"#"),t(" Debian and Ubuntu")],-1),j=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 2.",-1),Y={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},M=e("code",null,"gpg --import PGP.txt",-1),q=e("p",null,[t("Verify that the fingerprint is "),e("code",null,"6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(" by running this command "),e("code",null,"gpg --list-keys zkSNACKs"),t(".")],-1),H={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},$=e("code",null,".deb",-1),J=e("code",null,".asc",-1),X=s('
    Download Wasabi Wallet for Debian
    1. Verify the signature in the Download repository with gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
      TIP
      The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    2. [GUI] Install by double-clicking and follow the GUI Instruction. 
       [CLI] In the Download repository, execute the command sudo apt install ./Wasabi-2.0.5.deb to install Wasabi and after that run Wasabi by executing wassabee.
    ',2),Z=e("h2",{id:"other-linux",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-linux","aria-hidden":"true"},"#"),t(" Other Linux")],-1),ee=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 2.",-1),te={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},oe=e("code",null,"gpg --import PGP.txt",-1),ae=e("p",null,[t("Verify that the fingerprint is "),e("code",null,"6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(" by running this command "),e("code",null,"gpg --list-keys zkSNACKs"),t(".")],-1),ie={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},ne=e("code",null,".tar.gz",-1),le=e("code",null,".asc",-1),se=s('
    Download Wasabi Wallet for Linux
    1. In the Download folder, run gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz.
      If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
      TIP
      The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    2. Extract the archive while keeping the file permissions: tar -pxzf Wasabi-2.0.5.tar.gz.
    3. Run Wasabi by executing ./wassabee.
    ',2),re=e("h2",{id:"macos",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#macos","aria-hidden":"true"},"#"),t(" macOS")],-1),de={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},ce=e("code",null,".dmg",-1),he={href:"https://www.howtogeek.com/706226/how-to-check-if-your-mac-is-using-an-intel-or-apple-silicon-processor/",target:"_blank",rel:"noopener noreferrer"},ue=s('
    Download Wasabi Wallet for macOS
    1. Double-click .dmg to open it.
    2. Install Wasabi by dragging it into your Applications folder.
    3. At first startup, there will be a pop-up that Wasabi was downloaded from the internet. Click on Open and restart Wasabi.
    ',2),pe=e("h3",{id:"optional-pgp-verification",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#optional-pgp-verification","aria-hidden":"true"},"#"),t(" Optional PGP Verification")],-1),fe=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 4.",-1),be={href:"https://www.gnupg.org/download/index.html",target:"_blank",rel:"noopener noreferrer"},_e={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},ge=e("code",null,"TextEdit",-1),we=e("code",null,"zkSNACKsPubKey.txt",-1),me=e("code",null,"Format / Make Plain Text",-1),ye=e("li",null,[e("p",null,[t("Open Terminal and go to the folder in which you saved the "),e("code",null,"zkSNACKsPubKey.txt"),t(" file and import the PGP public key with "),e("code",null,"sudo gpg --import zkSNACKsPubKey.txt"),t(". This should return the output: "),e("code",null,'key 856348328949861E: public key "zkSNACKs " imported'),t(".")])],-1),ke={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},We=e("code",null,".dmg",-1),ve=e("code",null,".asc",-1),Pe=e("p",null,[e("img",{src:d,alt:""})],-1),Ae=s('
  • In the Download folder, run sudo gpg --verify Wasabi-2.0.5.dmg.asc Wasabi-2.0.5.dmg. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
    TIP
    The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    • ',1),xe={href:"https://youtu.be/ry6qIyQmzRE",target:"_blank",rel:"noopener noreferrer"},Ie=e("img",{src:c,alt:"Watch the video"},null,-1),Se={href:"https://youtu.be/QHIpEYYqddE",target:"_blank",rel:"noopener noreferrer"},Ne=e("img",{src:c,alt:"Watch the video"},null,-1);function De(ze,Ge){const n=r("router-link"),l=r("RouterLink"),a=r("ExternalLinkIcon");return _(),g("div",null,[y,e("nav",k,[e("ul",null,[e("li",null,[o(n,{to:"#introduction"},{default:i(()=>[t("Introduction")]),_:1})]),e("li",null,[o(n,{to:"#install-wasabi-step-by-step"},{default:i(()=>[t("Install Wasabi step-by-step")]),_:1})]),e("li",null,[o(n,{to:"#windows"},{default:i(()=>[t("Windows")]),_:1})]),e("li",null,[o(n,{to:"#debian-and-ubuntu"},{default:i(()=>[t("Debian and Ubuntu")]),_:1})]),e("li",null,[o(n,{to:"#other-linux"},{default:i(()=>[t("Other Linux")]),_:1})]),e("li",null,[o(n,{to:"#macos"},{default:i(()=>[t("macOS")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#optional-pgp-verification"},{default:i(()=>[t("Optional PGP Verification")]),_:1})])])])])]),W,e("p",null,[t("The easiest way to start with Wasabi is to download, verify and install the released package. This is a version of the software that is thoroughly reviewed by the contributors. The package has the binary code that is needed to run the Wasabi Wallet client including the graphical user interface. For compiling the open-source code with cutting edge development features, also including the backend server, see this "),o(l,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[t("tutorial here")]),_:1}),t(".")]),e("p",null,[t("Download the packages either from the official "),e("a",v,[t("WasabiWallet.io"),o(a)]),t(" clearnet website or for your privacy's sake, from the official Tor onion service "),e("a",P,[t("http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),o(a)]),t(".")]),A,e("p",null,[t("Although there is automatic signature verification on Windows and macOS, it is still recommended to manually "),x,t(" of the downloaded package with zkSNACKs' PGP public key "),e("a",I,[t("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),o(a)]),t(" before installing Wasabi. This protects you against malicious phishing sites giving you back-doored wallet software. If you have personally verified zkSNACKs' PGP public key "),e("a",S,[t("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),o(a)]),t(" and you are familiar with the "),e("a",N,[t("Web Of Trust"),o(a)]),t(", please consider also "),e("a",D,[t("signing it"),o(a)]),t(".")]),z,G,e("ol",null,[e("li",null,[t("Download the Wasabi package relevant to your operating system from "),e("a",C,[t("wasabiwallet.io"),o(a)]),t(".")]),K,F]),T,B,e("ol",null,[e("li",null,[e("a",E,[t("Download"),o(a)]),t(" the "),O,t(" installer of the latest Wasabi release.")])]),Q,V,L,e("p",null,[t("Wasabi will be installed to your "),U,t(" folder. You will also have an icon in your Start Menu and on your Desktop. After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),R,j,e("ol",null,[e("li",null,[e("p",null,[t("Download zkSNACKs' PGP public key "),e("a",Y,[t("here"),o(a)]),t(", and then import it with "),M,t(".")]),q]),e("li",null,[e("p",null,[e("a",H,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),$,t(" package and the corresponding "),J,t(" signature file.")])])]),X,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),Z,ee,e("ol",null,[e("li",null,[e("p",null,[t("Download zkSNACKs' PGP public key "),e("a",te,[t("here"),o(a)]),t(", and then import it with "),oe,t(".")]),ae]),e("li",null,[e("p",null,[e("a",ie,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),ne,t(" archive and the corresponding "),le,t(" signature file.")])])]),se,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),re,e("ol",null,[e("li",null,[e("a",de,[t("Download"),o(a)]),t(" the "),ce,t(" package of Wasabi 2.0.5 for your machine's processor. "),o(l,{to:"/FAQ/FAQ-Installation.html#why-are-there-two-different-packages-for-macos-intel-and-apple-silicon"},{default:i(()=>[t("There are two types of packages for macOS")]),_:1}),t(", one for Intel and one for the Apple Silicon chip. If you're not sure what processor your device has, you can "),e("a",he,[t("check it"),o(a)]),t(".")])]),ue,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),pe,fe,e("ol",null,[e("li",null,[e("p",null,[e("a",be,[t("Get GnuPG"),o(a)]),t(".")])]),e("li",null,[e("p",null,[t("Copy "),e("a",_e,[t("zkSNACKs' PGP public key"),o(a)]),t(" into a new "),ge,t(" document and saving it as "),we,t(". Before saving, you need to go to "),me,t(" (otherwise TextEdit will not be able to save it as a .txt file).")])]),ye,e("li",null,[e("p",null,[e("a",ke,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),We,t(" package and the corresponding "),ve,t(" signature file.")]),Pe]),Ae]),e("p",null,[e("a",xe,[Ie,o(a)])]),e("p",null,[e("a",Se,[Ne,o(a)])])])}const Te=b(m,[["render",De],["__file","InstallPackage.html.vue"]]);export{Te as default};
+import{b as h,c as u,d,_ as p,a as f}from"./DownloadMac.90ece9d0.js";import{_ as c}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as b,r,o as _,c as g,a as e,d as o,w as i,b as t,e as s}from"./app.65e5b6fd.js";const w="/DownloadAll.png",m={},y=e("h1",{id:"install-package",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-package","aria-hidden":"true"},"#"),t(" Install package")],-1),k={class:"table-of-contents"},W=e("h2",{id:"introduction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#introduction","aria-hidden":"true"},"#"),t(" Introduction")],-1),v={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},P={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},A=e("p",null,[e("img",{src:w,alt:"Operating systems supported by Wasabi Wallet",title:"Operating systems supported by Wasabi Wallet"})],-1),x=e("strong",null,"VERIFY PGP SIGNATURES",-1),I={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},S={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},N={href:"https://security.stackexchange.com/questions/147447/gpg-why-is-my-trusted-key-not-certified-with-a-trusted-signature",target:"_blank",rel:"noopener noreferrer"},D={href:"https://www.gnupg.org/gph/en/manual/x334.html",target:"_blank",rel:"noopener noreferrer"},z=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"Always"),e("p",null,"Don't trust - Verify!")],-1),G=e("h2",{id:"install-wasabi-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-wasabi-step-by-step","aria-hidden":"true"},"#"),t(" Install Wasabi step-by-step")],-1),C={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},K=e("li",null,"Verify the PGP signatures of the download.",-1),F=e("li",null,"Install Wasabi package as you would do any other software on your operating system.",-1),T=e("hr",null,null,-1),B=e("h2",{id:"windows",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#windows","aria-hidden":"true"},"#"),t(" Windows")],-1),E={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},O=e("code",null,".msi",-1),Q=e("p",null,[e("img",{src:h,alt:"Download Wasabi Wallet for Windows",title:"Download Wasabi Wallet for Windows"})],-1),V=e("ol",{start:"2"},[e("li",null,[e("p",null,[t("Install Wasabi by double-clicking the "),e("code",null,".msi"),t(" and following the GUI instructions.")])]),e("li",null,[e("p",null,"Make sure that you see this window that verifies the installer was signed by zkSNACKs Limited. Manual PGP verification is optional, as the package is signed and verified automatically on Windows.")])],-1),L=e("p",null,[e("img",{src:u,alt:"Wasabi Wallet Windows signature verification",title:"Wasabi Wallet Windows signature verification"})],-1),U=e("code",null,"C:\\Program Files\\WasabiWallet\\",-1),R=e("h2",{id:"debian-and-ubuntu",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#debian-and-ubuntu","aria-hidden":"true"},"#"),t(" Debian and Ubuntu")],-1),j=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 2.",-1),Y={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},M=e("code",null,"gpg --import PGP.txt",-1),q=e("p",null,[t("Verify that the fingerprint is "),e("code",null,"6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(" by running this command "),e("code",null,"gpg --list-keys zkSNACKs"),t(".")],-1),H={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},$=e("code",null,".deb",-1),J=e("code",null,".asc",-1),X=s('
    Download Wasabi Wallet for Debian
    1. Verify the signature in the Download repository with gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
      TIP
      The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    2. [GUI] Install by double-clicking and follow the GUI Instruction. 
       [CLI] In the Download repository, execute the command sudo apt install ./Wasabi-2.0.5.deb to install Wasabi and after that run Wasabi by executing wassabee.
    ',2),Z=e("h2",{id:"other-linux",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#other-linux","aria-hidden":"true"},"#"),t(" Other Linux")],-1),ee=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 2.",-1),te={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},oe=e("code",null,"gpg --import PGP.txt",-1),ae=e("p",null,[t("Verify that the fingerprint is "),e("code",null,"6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),t(" by running this command "),e("code",null,"gpg --list-keys zkSNACKs"),t(".")],-1),ie={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},ne=e("code",null,".tar.gz",-1),le=e("code",null,".asc",-1),se=s('
    Download Wasabi Wallet for Linux
    1. In the Download folder, run gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz.
      If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
      TIP
      The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    2. Extract the archive while keeping the file permissions: tar -pxzf Wasabi-2.0.5.tar.gz.
    3. Run Wasabi by executing ./wassabee.
    ',2),re=e("h2",{id:"macos",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#macos","aria-hidden":"true"},"#"),t(" macOS")],-1),de={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},ce=e("code",null,".dmg",-1),he={href:"https://www.howtogeek.com/706226/how-to-check-if-your-mac-is-using-an-intel-or-apple-silicon-processor/",target:"_blank",rel:"noopener noreferrer"},ue=s('
    Download Wasabi Wallet for macOS
    1. Double-click .dmg to open it.
    2. Install Wasabi by dragging it into your Applications folder.
    3. At first startup, there will be a pop-up that Wasabi was downloaded from the internet. Click on Open and restart Wasabi.
    ',2),pe=e("h3",{id:"optional-pgp-verification",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#optional-pgp-verification","aria-hidden":"true"},"#"),t(" Optional PGP Verification")],-1),fe=e("p",null,"If you have already imported zkSNACKs' PGP public key, then jump to step 4.",-1),be={href:"https://www.gnupg.org/download/index.html",target:"_blank",rel:"noopener noreferrer"},_e={href:"https://github.com/zkSNACKs/WalletWasabi/blob/master/PGP.txt",target:"_blank",rel:"noopener noreferrer"},ge=e("code",null,"TextEdit",-1),we=e("code",null,"zkSNACKsPubKey.txt",-1),me=e("code",null,"Format / Make Plain Text",-1),ye=e("li",null,[e("p",null,[t("Open Terminal and go to the folder in which you saved the "),e("code",null,"zkSNACKsPubKey.txt"),t(" file and import the PGP public key with "),e("code",null,"sudo gpg --import zkSNACKsPubKey.txt"),t(". This should return the output: "),e("code",null,'key 856348328949861E: public key "zkSNACKs " imported'),t(".")])],-1),ke={href:"https://wasabiwallet.io/#download",target:"_blank",rel:"noopener noreferrer"},We=e("code",null,".dmg",-1),ve=e("code",null,".asc",-1),Pe=e("p",null,[e("img",{src:d,alt:""})],-1),Ae=s('
  • In the Download folder, run sudo gpg --verify Wasabi-2.0.5.dmg.asc Wasabi-2.0.5.dmg. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
    TIP
    The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
    • ',1),xe={href:"https://youtu.be/ry6qIyQmzRE",target:"_blank",rel:"noopener noreferrer"},Ie=e("img",{src:c,alt:"Watch the video"},null,-1),Se={href:"https://youtu.be/QHIpEYYqddE",target:"_blank",rel:"noopener noreferrer"},Ne=e("img",{src:c,alt:"Watch the video"},null,-1);function De(ze,Ge){const n=r("router-link"),l=r("RouterLink"),a=r("ExternalLinkIcon");return _(),g("div",null,[y,e("nav",k,[e("ul",null,[e("li",null,[o(n,{to:"#introduction"},{default:i(()=>[t("Introduction")]),_:1})]),e("li",null,[o(n,{to:"#install-wasabi-step-by-step"},{default:i(()=>[t("Install Wasabi step-by-step")]),_:1})]),e("li",null,[o(n,{to:"#windows"},{default:i(()=>[t("Windows")]),_:1})]),e("li",null,[o(n,{to:"#debian-and-ubuntu"},{default:i(()=>[t("Debian and Ubuntu")]),_:1})]),e("li",null,[o(n,{to:"#other-linux"},{default:i(()=>[t("Other Linux")]),_:1})]),e("li",null,[o(n,{to:"#macos"},{default:i(()=>[t("macOS")]),_:1}),e("ul",null,[e("li",null,[o(n,{to:"#optional-pgp-verification"},{default:i(()=>[t("Optional PGP Verification")]),_:1})])])])])]),W,e("p",null,[t("The easiest way to start with Wasabi is to download, verify and install the released package. This is a version of the software that is thoroughly reviewed by the contributors. The package has the binary code that is needed to run the Wasabi Wallet client including the graphical user interface. For compiling the open-source code with cutting edge development features, also including the backend server, see this "),o(l,{to:"/using-wasabi/BuildSource.html"},{default:i(()=>[t("tutorial here")]),_:1}),t(".")]),e("p",null,[t("Download the packages either from the official "),e("a",v,[t("WasabiWallet.io"),o(a)]),t(" clearnet website or for your privacy's sake, from the official Tor onion service "),e("a",P,[t("http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),o(a)]),t(".")]),A,e("p",null,[t("Although there is automatic signature verification on Windows and macOS, it is still recommended to manually "),x,t(" of the downloaded package with zkSNACKs' PGP public key "),e("a",I,[t("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),o(a)]),t(" before installing Wasabi. This protects you against malicious phishing sites giving you back-doored wallet software. If you have personally verified zkSNACKs' PGP public key "),e("a",S,[t("6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E"),o(a)]),t(" and you are familiar with the "),e("a",N,[t("Web Of Trust"),o(a)]),t(", please consider also "),e("a",D,[t("signing it"),o(a)]),t(".")]),z,G,e("ol",null,[e("li",null,[t("Download the Wasabi package relevant to your operating system from "),e("a",C,[t("wasabiwallet.io"),o(a)]),t(".")]),K,F]),T,B,e("ol",null,[e("li",null,[e("a",E,[t("Download"),o(a)]),t(" the "),O,t(" installer of the latest Wasabi release.")])]),Q,V,L,e("p",null,[t("Wasabi will be installed to your "),U,t(" folder. You will also have an icon in your Start Menu and on your Desktop. After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),R,j,e("ol",null,[e("li",null,[e("p",null,[t("Download zkSNACKs' PGP public key "),e("a",Y,[t("here"),o(a)]),t(", and then import it with "),M,t(".")]),q]),e("li",null,[e("p",null,[e("a",H,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),$,t(" package and the corresponding "),J,t(" signature file.")])])]),X,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),Z,ee,e("ol",null,[e("li",null,[e("p",null,[t("Download zkSNACKs' PGP public key "),e("a",te,[t("here"),o(a)]),t(", and then import it with "),oe,t(".")]),ae]),e("li",null,[e("p",null,[e("a",ie,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),ne,t(" archive and the corresponding "),le,t(" signature file.")])])]),se,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),re,e("ol",null,[e("li",null,[e("a",de,[t("Download"),o(a)]),t(" the "),ce,t(" package of Wasabi 2.0.5 for your machine's processor. "),o(l,{to:"/FAQ/FAQ-Installation.html#why-are-there-two-different-packages-for-macos-intel-and-apple-silicon"},{default:i(()=>[t("There are two types of packages for macOS")]),_:1}),t(", one for Intel and one for the Apple Silicon chip. If you're not sure what processor your device has, you can "),e("a",he,[t("check it"),o(a)]),t(".")])]),ue,e("p",null,[t("After the first run, a "),o(l,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:i(()=>[t("data folder")]),_:1}),t(" will be created. Among others, here is where your wallet files and your logs reside.")]),pe,fe,e("ol",null,[e("li",null,[e("p",null,[e("a",be,[t("Get GnuPG"),o(a)]),t(".")])]),e("li",null,[e("p",null,[t("Copy "),e("a",_e,[t("zkSNACKs' PGP public key"),o(a)]),t(" into a new "),ge,t(" document and saving it as "),we,t(". Before saving, you need to go to "),me,t(" (otherwise TextEdit will not be able to save it as a .txt file).")])]),ye,e("li",null,[e("p",null,[e("a",ke,[t("Download"),o(a)]),t(" the latest Wasabi release, both the "),We,t(" package and the corresponding "),ve,t(" signature file.")]),Pe]),Ae]),e("p",null,[e("a",xe,[Ie,o(a)])]),e("p",null,[e("a",Se,[Ne,o(a)])])])}const Te=b(m,[["render",De],["__file","InstallPackage.html.vue"]]);export{Te as default};
diff --git a/assets/LICENSE.html.005bab57.js b/assets/LICENSE.html.7be39d8d.js
similarity index 94%
rename from assets/LICENSE.html.005bab57.js
rename to assets/LICENSE.html.7be39d8d.js
index 4bf920d08e..e14224e126 100644
--- a/assets/LICENSE.html.005bab57.js
+++ b/assets/LICENSE.html.7be39d8d.js
@@ -1 +1 @@
-import{_ as n,r,o as a,c as o,a as e,b as t,d,e as s}from"./app.a5b7c2b2.js";const c={},l=s('
     MIT License
    Wasabi Wallet and Wasabi documentation is licensed under the MIT License.
    A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
    PermissionsLimitationsConditions
    Commercial useLiabilityLicense and copyright notice
    ModificationWarranty
    Distribution
    Private use
    ',4),h={href:"https://github.com/zkSNACKs/WasabiDoc/blob/master/LICENSE",target:"_blank",rel:"noopener noreferrer"};function m(u,_){const i=r("ExternalLinkIcon");return a(),o("div",null,[l,e("p",null,[t("You can check the license "),e("a",h,[t("here"),d(i)]),t(".")])])}const b=n(c,[["render",m],["__file","LICENSE.html.vue"]]);export{b as default};
+import{_ as n,r,o as a,c as o,a as e,b as t,d,e as s}from"./app.65e5b6fd.js";const c={},l=s('
     MIT License
    Wasabi Wallet and Wasabi documentation is licensed under the MIT License.
    A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
    PermissionsLimitationsConditions
    Commercial useLiabilityLicense and copyright notice
    ModificationWarranty
    Distribution
    Private use
    ',4),h={href:"https://github.com/zkSNACKs/WasabiDoc/blob/master/LICENSE",target:"_blank",rel:"noopener noreferrer"};function m(u,_){const i=r("ExternalLinkIcon");return a(),o("div",null,[l,e("p",null,[t("You can check the license "),e("a",h,[t("here"),d(i)]),t(".")])])}const b=n(c,[["render",m],["__file","LICENSE.html.vue"]]);export{b as default};
diff --git a/assets/LegalConcern.html.c1cbc8f2.js b/assets/LegalConcern.html.11293b2a.js
similarity index 99%
rename from assets/LegalConcern.html.c1cbc8f2.js
rename to assets/LegalConcern.html.11293b2a.js
index 140001b193..1dd2090f41 100644
--- a/assets/LegalConcern.html.c1cbc8f2.js
+++ b/assets/LegalConcern.html.11293b2a.js
@@ -1 +1 @@
-import{_ as c,r as s,o as l,c as h,a as e,d as n,w as a,b as i,e as o}from"./app.a5b7c2b2.js";const d="/AddressDistribution.png",p={},u=e("h1",{id:"coinjoin-legal-concern",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-legal-concern","aria-hidden":"true"},"#"),i(" CoinJoin Legal Concern")],-1),f={class:"table-of-contents"},m=o('
    Using Bitcoin and other cryptocurrencies in the everyday course of businesses is becoming more and more popular. Digital money has a lot of advantages, from unstoppable transactions to relatively low fees, and quick final settlement of international payments. But all come at a price: the blockchain stores sensitive information like the amount and involved addresses of a transaction, giving away too much business-related information to the public. However, this does not necessarily need to be the case.
     Overview
    A CoinJoin transaction obfuscates the history of a given coin, making it hard to trace the coin back to the originator of the funds. The implementation of Wasabi Wallet CoinJoin allows the original user to get back his funds with an obfuscated history.
    It is often assumed that the main problem with an obfuscated transaction history is that financial regulators may have concerns about money laundering. However, this is only the first impression, if we go into the details it can become more transparent why institutions should not worry about violating AML rules and why companies could have a direct competitive advantage using CoinJoin transactions.
    With a transparent financial track record, companies paying with cryptocurrencies may find themselves in a squeezing situation, where their suppliers, clients, and competitors are aware of all of their payment steps and prices. For institutional investors, each step would be scrutinized by the market causing intentional or unintentional price manipulation.
    While the Bitcoin blockchain does not store personal information about the owners of the specific Bitcoin addresses, using metadata makes it possible to link Bitcoin addresses to certain companies and individuals. If such a link can be established, all past and future transactions can be traced.
     CoinJoin transactions
     Difference between ordinary banking and blockchain
    The ordinary banking system is closed, a very non-transparent system, where the data inside this system is hidden from outside observers. “Only” the bank and the user know the transactions made inside the system. In opposition, the blockchain is transparent and open to everyone. This means not only the “bank” (custodial service provider) but also outsider 3rd party observers are capable of tracking these transactions.
     Service providers' obligations regarding privacy
    There is no question a service provider who keeps a record of personal information needs to deal with the different privacy regulations and act according to them. In the ordinary banking system personal financial information is handled as a secret thus preserving individual privacy from third parties. Whereas in the open blockchain system this information by the nature of the technology cannot be kept secret, so there is a large risk of a privacy leak of sensitive financial information. This is obviously not intentional and even though the personal information might be protected, the financial information is nevertheless leaked due to the pseudonym nature of the system. This information has similar sensitivity as name, address, gender, etc. so it should be handled with great care.
     CoinJoin as a privacy-preserving tool
    Since the Bitcoin blockchain is transparent, transactions cannot be kept secret. Currently, one prevalent solution in Bitcoin to gain privacy is to CoinJoin the different coins to obfuscate their history. By the use of this tool, a custodial service provider can at least start to protect its users' financial privacy.
     Privacy perspective from the companies' point of view
    The essence of competitive advantages is to keep and hold business secrets. Each and every successful company has developed its own mechanism to deliver the best products and services to its customers. To reach this, they usually use a secret sauce, called the business secret to deliver the results. If anything, when a financial payment becomes fully transparent this business secret is evaporating Let’s look a bit deeper into what exactly this means for companies, who would like to use Bitcoin as the payment method, where all transactions are recorded on the blockchain.
     Suppliers
    Companies use suppliers to acquire products and services they use in their own production stages. For these products and services, of course, they pay a reasonable price. However, this price is usually negotiable, especially in B2B relationships or large scale orders. What would happen if all of a sudden, the price of raw materials for a company becomes fully public? Other competitors can now demand similar discounts, forcing industries into a vicious cycle of price reduction. As each and every price discount is negotiated on a case by case basis, considering factors as creditworthiness and timing of payment, transparent supplier prices would only cause enormous pressure on suppliers to deal with negotiations.
    Beyond the price of products, the timing of payments is also fully transparent on the blockchain. However, in certain circumstances, it is also a crucial business secret to keep the information on the sequence of invoice payments indoors. Considering cash flow implications, it can happen that one invoice is paid on time, while other invoices are still pending payment. In the case of blockchain transactions however all payments are transparent, so it can be clear for each counterparty that only a selected number of invoices has been paid even if the sufficient funds are available which can cause unnecessary tension between business partners.
    Additionally, if all historical transactions of a company are known, its creditworthiness might be considered incorrectly. It can happen that the creditworthiness is considered better than it is if the incoming funds to a specific address are extraordinarily high, but these funds are needed in other parts of the business, so the overall solvency of the business can be still negative despite the large funds. On the other hand, creditworthiness can be considered worse than it actually is, if only a handful of addresses are taken into consideration for the solvency analysis, neglecting other forms of wealth, like other Bitcoin addresses, or fiat accounts.
     Clients
    From the client’s perspective, the factors listed under suppliers are all applicable. If a client knows the revenue stream of the company, they can draw an incorrect conclusion about the actual financial situation of a company and make a decision of purchasing a product based on this assumed financial situation. If for example, there are no incoming funds for a given period, clients may stay away from purchasing products and services, solely because they might consider the company dormant or insolvent. But in reality, the seasonality of incoming funds is not disclosed for all companies, so it can be a perfectly stable business situation to receive incoming funds only in a given period of a year, while still being able to deliver service throughout the year.
    Another aspect is the possible price negotiations on the client-side. If a client finds out that another client is paying less for a service or product, they can demand similar discounts which can result in downward price pressure in the industry. This can ultimately result in companies going out of businesses if they cannot adjust to the lower price levels which are below the equilibrium prices.
     Competitors
    Everyone can agree that the pricing structure of services is a very sensitive topic and is the core of the business secret which makes a company successful. If all competitors can look at the transactions of the company, it also means they can adjust their own pricing structure to follow the successful market leaders in the industry, causing turbulence in competition. Each company has its own pricing structure which should be coming from the internal processes, know-how, and resources. Although external factors should be considered in pricing, they should not be the main driving force in pricing decisions.
     Employees
    There is now a growing number of companies that are paying their employees salaries in bitcoin due to the trustless transactions with relatively low fees, especially with international transactions.
    With transparent transaction history, employees would be aware of each other’s salaries without the company disclosing this information. Although there are some theories supporting a transparent salary structure, up to now the majority of the companies prefer to keep salaries as secret and obligate employees to keep salary and wage information confidential. Obfuscated transaction history can help companies to keep salary information confidential which can keep a relaxed atmosphere among employees with no wage pressures.
     Phishing attacks
    Disclosing financial information for a company makes them more vulnerable to phishing attacks. If the exact time and amount of payment are publicly known, attackers can use this information to build trust with the company and squeeze out other crucial business information pretending to be a trusted partner.
     Privacy perspective from the institutional investor’s point of view
    ',31),y={href:"https://bitinfocharts.com/top-100-richest-bitcoin-addresses.html",target:"_blank",rel:"noopener noreferrer"},v=o('
    Bitcoin address distribution
    Institutional investors and cryptocurrency exchanges are holding large sums of bitcoin on a blockchain where transactions are completely transparent. These so-called whales sometimes need to move large amounts of coins for any reason which can often lead to unintentional price manipulation. If a large bitcoin holding is on the move, it can always raise concern in the media regarding the future of Bitcoin, causing unnecessary price fluctuations. In the case of unintentional price manipulation, it is difficult to prove there has been no insider trading on the institutional side, which can cause loss of faith from the clients.
    Using obfuscated transaction history in large bitcoin transactions can help to keep the market stable and avoid unintentional price manipulations.
     Resolving AML conflicts
    Privacy is not just for criminals. One of the major critiques against using CoinJoin is that if the transaction history is not known for a company, it may be used as a way to launder money. From the above-listed cases, we already see that currently using fiat payments, during the normal course of businesses, companies do not disclose all financial information as that would result in a loss of business secrets. Why would they need to do this if they are just using a new method of payment, called Bitcoin? Using privacy tools to obfuscate Bitcoin transactions is completely legal and in accordance with the current legal framework.
     User privacy
    In all jurisdictions, there are different laws and acts that are made to protect customers privacy. This is not limited only to personal data but also financial data. In the EU there is GDPR, in the USA there is the Privacy Act of 1974, in Canada, there is the Privacy Act of 1985, etc. These set different rules to be kept in order to preserve individual privacy both on personal and financial levels.
     KYC/AML
    By now in mainly all jurisdictions, custodial cryptocurrency service providers (wallet, exchange, payment processor, etc.) are requested to run KYC/AML checks on users and their transactions. The KYC process and inner policies should ensure personal data protection. The accounts are assigned to these individual users, who are verified by the provider. This means the provider identifies the user just like a legacy bank would do. The different AML checks are run on deposits or withdrawals. The suspicious transactions can be linked to users based on the transactions that are initiated by them personally. KYC and AML procedures now ensure that all transactions involving fiat (like buying and selling bitcoin on exchanges for fiat currency) have a detailed background in terms of who is sending what money to whom, the identification of transactions are even more strict than in the current banking world, where two companies or individuals can send even large funds without the need to verify their source.
     Using CoinJoin as a custodial service provider
    As soon as a user deposits the funds to any of these service providers, the funds are in one large cluster. From now on the funds are possessed by the service provider and the actual user balances are only kept on internal records. At this point all KYC/AML procedures are done, funds should be considered “clean”. The funds are controlled by the service provider and different policies are set for securing these funds (hot and cold storage, multisig, etc.). The record system of the provider will show the exact value of funds belonging to the different users. This is the time when a provider could preserve its users’ privacy by applying CoinJoin on these funds. In case of a withdrawal, coinjoined UTXOs could be sent to the user. Again, this user is already KYC-ed, the provider has full knowledge about the user. In case of a law enforcement request, all data can be provided, since the deposit history of the user in question is still available. The only thing CoinJoin does, in this case, is protecting the user from third-party observers, while the service provider is still enabled to provide data for law enforcement if requested.
     Conclusion
    Companies using Bitcoin as a method of payment currently do not have sufficient privacy regarding their financial information. Outsiders can get valuable business-related information by studying the public transaction history of a company, causing economic damage in the long run. Using CoinJoin transactions can help businesses to keep their privacy while still enjoying the benefits that Bitcoin transactions can provide. Concerns from the AML perspective are not valid, as the necessary data can be provided to authorities upon investigation requests.
    ',13);function g(b,w){const t=s("router-link"),r=s("ExternalLinkIcon");return l(),h("div",null,[u,e("nav",f,[e("ul",null,[e("li",null,[n(t,{to:"#overview"},{default:a(()=>[i("Overview")]),_:1})]),e("li",null,[n(t,{to:"#coinjoin-transactions"},{default:a(()=>[i("CoinJoin transactions")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#difference-between-ordinary-banking-and-blockchain"},{default:a(()=>[i("Difference between ordinary banking and blockchain")]),_:1})]),e("li",null,[n(t,{to:"#service-providers-obligations-regarding-privacy"},{default:a(()=>[i("Service providers' obligations regarding privacy")]),_:1})]),e("li",null,[n(t,{to:"#coinjoin-as-a-privacy-preserving-tool"},{default:a(()=>[i("CoinJoin as a privacy-preserving tool")]),_:1})])])]),e("li",null,[n(t,{to:"#privacy-perspective-from-the-companies-point-of-view"},{default:a(()=>[i("Privacy perspective from the companies' point of view")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#suppliers"},{default:a(()=>[i("Suppliers")]),_:1})]),e("li",null,[n(t,{to:"#clients"},{default:a(()=>[i("Clients")]),_:1})]),e("li",null,[n(t,{to:"#competitors"},{default:a(()=>[i("Competitors")]),_:1})]),e("li",null,[n(t,{to:"#employees"},{default:a(()=>[i("Employees")]),_:1})]),e("li",null,[n(t,{to:"#phishing-attacks"},{default:a(()=>[i("Phishing attacks")]),_:1})])])]),e("li",null,[n(t,{to:"#privacy-perspective-from-the-institutional-investor-s-point-of-view"},{default:a(()=>[i("Privacy perspective from the institutional investor’s point of view")]),_:1})]),e("li",null,[n(t,{to:"#resolving-aml-conflicts"},{default:a(()=>[i("Resolving AML conflicts")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#user-privacy"},{default:a(()=>[i("User privacy")]),_:1})]),e("li",null,[n(t,{to:"#kyc-aml"},{default:a(()=>[i("KYC/AML")]),_:1})]),e("li",null,[n(t,{to:"#using-coinjoin-as-a-custodial-service-provider"},{default:a(()=>[i("Using CoinJoin as a custodial service provider")]),_:1})])])]),e("li",null,[n(t,{to:"#conclusion"},{default:a(()=>[i("Conclusion")]),_:1})])])]),m,e("p",null,[i("The Bitcoin market is considered "),e("a",y,[i("fairly concentrated"),n(r)]),i(" in the sense that out of the millions of Bitcoin addresses, less than 1% holds 87% of bitcoins.")]),v])}const _=c(p,[["render",g],["__file","LegalConcern.html.vue"]]);export{_ as default};
+import{_ as c,r as s,o as l,c as h,a as e,d as n,w as a,b as i,e as o}from"./app.65e5b6fd.js";const d="/AddressDistribution.png",p={},u=e("h1",{id:"coinjoin-legal-concern",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#coinjoin-legal-concern","aria-hidden":"true"},"#"),i(" CoinJoin Legal Concern")],-1),f={class:"table-of-contents"},m=o('
    Using Bitcoin and other cryptocurrencies in the everyday course of businesses is becoming more and more popular. Digital money has a lot of advantages, from unstoppable transactions to relatively low fees, and quick final settlement of international payments. But all come at a price: the blockchain stores sensitive information like the amount and involved addresses of a transaction, giving away too much business-related information to the public. However, this does not necessarily need to be the case.
     Overview
    A CoinJoin transaction obfuscates the history of a given coin, making it hard to trace the coin back to the originator of the funds. The implementation of Wasabi Wallet CoinJoin allows the original user to get back his funds with an obfuscated history.
    It is often assumed that the main problem with an obfuscated transaction history is that financial regulators may have concerns about money laundering. However, this is only the first impression, if we go into the details it can become more transparent why institutions should not worry about violating AML rules and why companies could have a direct competitive advantage using CoinJoin transactions.
    With a transparent financial track record, companies paying with cryptocurrencies may find themselves in a squeezing situation, where their suppliers, clients, and competitors are aware of all of their payment steps and prices. For institutional investors, each step would be scrutinized by the market causing intentional or unintentional price manipulation.
    While the Bitcoin blockchain does not store personal information about the owners of the specific Bitcoin addresses, using metadata makes it possible to link Bitcoin addresses to certain companies and individuals. If such a link can be established, all past and future transactions can be traced.
     CoinJoin transactions
     Difference between ordinary banking and blockchain
    The ordinary banking system is closed, a very non-transparent system, where the data inside this system is hidden from outside observers. “Only” the bank and the user know the transactions made inside the system. In opposition, the blockchain is transparent and open to everyone. This means not only the “bank” (custodial service provider) but also outsider 3rd party observers are capable of tracking these transactions.
     Service providers' obligations regarding privacy
    There is no question a service provider who keeps a record of personal information needs to deal with the different privacy regulations and act according to them. In the ordinary banking system personal financial information is handled as a secret thus preserving individual privacy from third parties. Whereas in the open blockchain system this information by the nature of the technology cannot be kept secret, so there is a large risk of a privacy leak of sensitive financial information. This is obviously not intentional and even though the personal information might be protected, the financial information is nevertheless leaked due to the pseudonym nature of the system. This information has similar sensitivity as name, address, gender, etc. so it should be handled with great care.
     CoinJoin as a privacy-preserving tool
    Since the Bitcoin blockchain is transparent, transactions cannot be kept secret. Currently, one prevalent solution in Bitcoin to gain privacy is to CoinJoin the different coins to obfuscate their history. By the use of this tool, a custodial service provider can at least start to protect its users' financial privacy.
     Privacy perspective from the companies' point of view
    The essence of competitive advantages is to keep and hold business secrets. Each and every successful company has developed its own mechanism to deliver the best products and services to its customers. To reach this, they usually use a secret sauce, called the business secret to deliver the results. If anything, when a financial payment becomes fully transparent this business secret is evaporating Let’s look a bit deeper into what exactly this means for companies, who would like to use Bitcoin as the payment method, where all transactions are recorded on the blockchain.
     Suppliers
    Companies use suppliers to acquire products and services they use in their own production stages. For these products and services, of course, they pay a reasonable price. However, this price is usually negotiable, especially in B2B relationships or large scale orders. What would happen if all of a sudden, the price of raw materials for a company becomes fully public? Other competitors can now demand similar discounts, forcing industries into a vicious cycle of price reduction. As each and every price discount is negotiated on a case by case basis, considering factors as creditworthiness and timing of payment, transparent supplier prices would only cause enormous pressure on suppliers to deal with negotiations.
    Beyond the price of products, the timing of payments is also fully transparent on the blockchain. However, in certain circumstances, it is also a crucial business secret to keep the information on the sequence of invoice payments indoors. Considering cash flow implications, it can happen that one invoice is paid on time, while other invoices are still pending payment. In the case of blockchain transactions however all payments are transparent, so it can be clear for each counterparty that only a selected number of invoices has been paid even if the sufficient funds are available which can cause unnecessary tension between business partners.
    Additionally, if all historical transactions of a company are known, its creditworthiness might be considered incorrectly. It can happen that the creditworthiness is considered better than it is if the incoming funds to a specific address are extraordinarily high, but these funds are needed in other parts of the business, so the overall solvency of the business can be still negative despite the large funds. On the other hand, creditworthiness can be considered worse than it actually is, if only a handful of addresses are taken into consideration for the solvency analysis, neglecting other forms of wealth, like other Bitcoin addresses, or fiat accounts.
     Clients
    From the client’s perspective, the factors listed under suppliers are all applicable. If a client knows the revenue stream of the company, they can draw an incorrect conclusion about the actual financial situation of a company and make a decision of purchasing a product based on this assumed financial situation. If for example, there are no incoming funds for a given period, clients may stay away from purchasing products and services, solely because they might consider the company dormant or insolvent. But in reality, the seasonality of incoming funds is not disclosed for all companies, so it can be a perfectly stable business situation to receive incoming funds only in a given period of a year, while still being able to deliver service throughout the year.
    Another aspect is the possible price negotiations on the client-side. If a client finds out that another client is paying less for a service or product, they can demand similar discounts which can result in downward price pressure in the industry. This can ultimately result in companies going out of businesses if they cannot adjust to the lower price levels which are below the equilibrium prices.
     Competitors
    Everyone can agree that the pricing structure of services is a very sensitive topic and is the core of the business secret which makes a company successful. If all competitors can look at the transactions of the company, it also means they can adjust their own pricing structure to follow the successful market leaders in the industry, causing turbulence in competition. Each company has its own pricing structure which should be coming from the internal processes, know-how, and resources. Although external factors should be considered in pricing, they should not be the main driving force in pricing decisions.
     Employees
    There is now a growing number of companies that are paying their employees salaries in bitcoin due to the trustless transactions with relatively low fees, especially with international transactions.
    With transparent transaction history, employees would be aware of each other’s salaries without the company disclosing this information. Although there are some theories supporting a transparent salary structure, up to now the majority of the companies prefer to keep salaries as secret and obligate employees to keep salary and wage information confidential. Obfuscated transaction history can help companies to keep salary information confidential which can keep a relaxed atmosphere among employees with no wage pressures.
     Phishing attacks
    Disclosing financial information for a company makes them more vulnerable to phishing attacks. If the exact time and amount of payment are publicly known, attackers can use this information to build trust with the company and squeeze out other crucial business information pretending to be a trusted partner.
     Privacy perspective from the institutional investor’s point of view
    ',31),y={href:"https://bitinfocharts.com/top-100-richest-bitcoin-addresses.html",target:"_blank",rel:"noopener noreferrer"},v=o('
    Bitcoin address distribution
    Institutional investors and cryptocurrency exchanges are holding large sums of bitcoin on a blockchain where transactions are completely transparent. These so-called whales sometimes need to move large amounts of coins for any reason which can often lead to unintentional price manipulation. If a large bitcoin holding is on the move, it can always raise concern in the media regarding the future of Bitcoin, causing unnecessary price fluctuations. In the case of unintentional price manipulation, it is difficult to prove there has been no insider trading on the institutional side, which can cause loss of faith from the clients.
    Using obfuscated transaction history in large bitcoin transactions can help to keep the market stable and avoid unintentional price manipulations.
     Resolving AML conflicts
    Privacy is not just for criminals. One of the major critiques against using CoinJoin is that if the transaction history is not known for a company, it may be used as a way to launder money. From the above-listed cases, we already see that currently using fiat payments, during the normal course of businesses, companies do not disclose all financial information as that would result in a loss of business secrets. Why would they need to do this if they are just using a new method of payment, called Bitcoin? Using privacy tools to obfuscate Bitcoin transactions is completely legal and in accordance with the current legal framework.
     User privacy
    In all jurisdictions, there are different laws and acts that are made to protect customers privacy. This is not limited only to personal data but also financial data. In the EU there is GDPR, in the USA there is the Privacy Act of 1974, in Canada, there is the Privacy Act of 1985, etc. These set different rules to be kept in order to preserve individual privacy both on personal and financial levels.
     KYC/AML
    By now in mainly all jurisdictions, custodial cryptocurrency service providers (wallet, exchange, payment processor, etc.) are requested to run KYC/AML checks on users and their transactions. The KYC process and inner policies should ensure personal data protection. The accounts are assigned to these individual users, who are verified by the provider. This means the provider identifies the user just like a legacy bank would do. The different AML checks are run on deposits or withdrawals. The suspicious transactions can be linked to users based on the transactions that are initiated by them personally. KYC and AML procedures now ensure that all transactions involving fiat (like buying and selling bitcoin on exchanges for fiat currency) have a detailed background in terms of who is sending what money to whom, the identification of transactions are even more strict than in the current banking world, where two companies or individuals can send even large funds without the need to verify their source.
     Using CoinJoin as a custodial service provider
    As soon as a user deposits the funds to any of these service providers, the funds are in one large cluster. From now on the funds are possessed by the service provider and the actual user balances are only kept on internal records. At this point all KYC/AML procedures are done, funds should be considered “clean”. The funds are controlled by the service provider and different policies are set for securing these funds (hot and cold storage, multisig, etc.). The record system of the provider will show the exact value of funds belonging to the different users. This is the time when a provider could preserve its users’ privacy by applying CoinJoin on these funds. In case of a withdrawal, coinjoined UTXOs could be sent to the user. Again, this user is already KYC-ed, the provider has full knowledge about the user. In case of a law enforcement request, all data can be provided, since the deposit history of the user in question is still available. The only thing CoinJoin does, in this case, is protecting the user from third-party observers, while the service provider is still enabled to provide data for law enforcement if requested.
     Conclusion
    Companies using Bitcoin as a method of payment currently do not have sufficient privacy regarding their financial information. Outsiders can get valuable business-related information by studying the public transaction history of a company, causing economic damage in the long run. Using CoinJoin transactions can help businesses to keep their privacy while still enjoying the benefits that Bitcoin transactions can provide. Concerns from the AML perspective are not valid, as the necessary data can be provided to authorities upon investigation requests.
    ',13);function g(b,w){const t=s("router-link"),r=s("ExternalLinkIcon");return l(),h("div",null,[u,e("nav",f,[e("ul",null,[e("li",null,[n(t,{to:"#overview"},{default:a(()=>[i("Overview")]),_:1})]),e("li",null,[n(t,{to:"#coinjoin-transactions"},{default:a(()=>[i("CoinJoin transactions")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#difference-between-ordinary-banking-and-blockchain"},{default:a(()=>[i("Difference between ordinary banking and blockchain")]),_:1})]),e("li",null,[n(t,{to:"#service-providers-obligations-regarding-privacy"},{default:a(()=>[i("Service providers' obligations regarding privacy")]),_:1})]),e("li",null,[n(t,{to:"#coinjoin-as-a-privacy-preserving-tool"},{default:a(()=>[i("CoinJoin as a privacy-preserving tool")]),_:1})])])]),e("li",null,[n(t,{to:"#privacy-perspective-from-the-companies-point-of-view"},{default:a(()=>[i("Privacy perspective from the companies' point of view")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#suppliers"},{default:a(()=>[i("Suppliers")]),_:1})]),e("li",null,[n(t,{to:"#clients"},{default:a(()=>[i("Clients")]),_:1})]),e("li",null,[n(t,{to:"#competitors"},{default:a(()=>[i("Competitors")]),_:1})]),e("li",null,[n(t,{to:"#employees"},{default:a(()=>[i("Employees")]),_:1})]),e("li",null,[n(t,{to:"#phishing-attacks"},{default:a(()=>[i("Phishing attacks")]),_:1})])])]),e("li",null,[n(t,{to:"#privacy-perspective-from-the-institutional-investor-s-point-of-view"},{default:a(()=>[i("Privacy perspective from the institutional investor’s point of view")]),_:1})]),e("li",null,[n(t,{to:"#resolving-aml-conflicts"},{default:a(()=>[i("Resolving AML conflicts")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#user-privacy"},{default:a(()=>[i("User privacy")]),_:1})]),e("li",null,[n(t,{to:"#kyc-aml"},{default:a(()=>[i("KYC/AML")]),_:1})]),e("li",null,[n(t,{to:"#using-coinjoin-as-a-custodial-service-provider"},{default:a(()=>[i("Using CoinJoin as a custodial service provider")]),_:1})])])]),e("li",null,[n(t,{to:"#conclusion"},{default:a(()=>[i("Conclusion")]),_:1})])])]),m,e("p",null,[i("The Bitcoin market is considered "),e("a",y,[i("fairly concentrated"),n(r)]),i(" in the sense that out of the millions of Bitcoin addresses, less than 1% holds 87% of bitcoins.")]),v])}const _=c(p,[["render",g],["__file","LegalConcern.html.vue"]]);export{_ as default};
diff --git a/assets/NetworkLevelPrivacy.html.73464f1b.js b/assets/NetworkLevelPrivacy.html.384b39be.js
similarity index 99%
rename from assets/NetworkLevelPrivacy.html.73464f1b.js
rename to assets/NetworkLevelPrivacy.html.384b39be.js
index 0c915264cf..4ff169a3cf 100644
--- a/assets/NetworkLevelPrivacy.html.73464f1b.js
+++ b/assets/NetworkLevelPrivacy.html.384b39be.js
@@ -1 +1 @@
-import{_ as c}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,r as s,o as h,c as u,a as e,d as a,w as i,b as t,e as r}from"./app.a5b7c2b2.js";const f={},b=e("h1",{id:"network-level-privacy-bitcoin-core-vs-wasabi-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#network-level-privacy-bitcoin-core-vs-wasabi-wallet","aria-hidden":"true"},"#"),t(" Network-Level Privacy - Bitcoin Core vs Wasabi Wallet")],-1),p=e("p",null,"Bitcoin is a peer-to-peer network of full nodes that define, verify, and enforce the Bitcoin consensus rules. There is a lot of communication between them and metadata can be used to de-anonymize Bitcoin users.",-1),m={class:"table-of-contents"},v=e("h2",{id:"problem",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#problem","aria-hidden":"true"},"#"),t(" Problem")],-1),g=e("h3",{id:"clearnet-light-clients",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#clearnet-light-clients","aria-hidden":"true"},"#"),t(" Clearnet light clients")],-1),y=e("p",null,"When the communication to the network is unencrypted over clearnet, then there is an easy correlation of the Bitcoin transactions to the IP address of the peer who sent it. The IP address can even be used to find the physical location of the user!",-1),w=e("p",null,"A Bitcoin full node broadcasts not just the transactions of its user, but it also gossips all of the other transactions that it has received from its peers. Thus it is very difficult to find out which transactions originated from which full node. However, when a node or a wallet does not gossip all transactions, but only the transactions of its user, then it is easier to find out which node has sent those specific transactions.",-1),k={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},_={href:"https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://www.reddit.com/r/Bitcoin/comments/2feox9/electrum_securityprivacy_model/ck8szc0/",target:"_blank",rel:"noopener noreferrer"},B=r('
    DANGER
    When the user sends the extended public key or a filter of all the addresses to the central server, then the server can COMPLETELY deanonymize the users.
     Wasabi's solution
     Full node by default & block filters over Tor
    Wasabi checks if there is a local Tor instance installed, and if so, it uses this to onion-route all the traffic to and from the network. If Tor is not already installed, then it is accessed automatically from within Wasabi. This means that by default, all network communication is secured from outside snooping and the IP address is hidden.
    ',4),P={href:"https://github.com/bitcoin/bitcoin",target:"_blank",rel:"noopener noreferrer"},x={class:"custom-container tip"},W=e("p",{class:"custom-container-title"},"Wasabi ships with Bitcoin Knots!",-1),I={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},C=r('
    Privacy by default!
    Wasabi has network-level privacy as good as a Bitcoin full node.
     In-depth comparison
    Furthermore, network-level privacy consists of two sub-categories.
    • Private UTXO Retrieval
    • Private Transaction Broadcasting
     Bitcoin Core
     Private UTXO retrieval
    Bitcoin Core downloads all the blocks ever created and establishes your wallet balances locally. This is as good as it gets.
     Private transaction broadcasting
    Bitcoin Core broadcasts transactions to other peers on the clearnet, unencrypted. Other peers cannot figure out which transaction originates from a specific node because Core does not only broadcast its own transactions but also propagates every other transaction that hits its mempool. However, some papers note it’s not bulletproof:
    ',9),A={href:"https://github.com/bitcoin/bips/blob/master/bip-0156.mediawiki",target:"_blank",rel:"noopener noreferrer"},N=r('
     Adversaries identified
    • Malicious Peer
    • Supernode
     Bitcoin Core + Tor
    You can use Bitcoin Core with Tor, which solves some of the above-mentioned issues. In this case, a supernode cannot track back transactions to your IP address.
    An entity that can break Tor is a universal adversary, however, most Tor attacks are not possible if exit nodes are not involved. It is reasonable to assume that this entity can break the onion routing, not Tor's encryption itself.
     Adversaries identified
    • Tor breaker
     Wasabi Wallet light node
     Private UTXO retrieval
    The backend server serves block filters to all the clients over Tor. From those filters, the clients figure out which blocks they are interested in and download them [and some false positive blocks] from peers. One block per peer, and always over a fresh Tor stream. When a block is acquired, the peer gets disconnected. Because of the end-to-end encryption of the onion network, it immediately defeats an ISP adversary and makes the already impossible job of the Sybil adversary even more impossible. The only adversary that could possibly overcome this would have to setup thousands of full nodes over Tor and also break Tor itself.
     Private transaction broadcasting
    All Wasabi traffic is tunneled through Tor. Wasabi connects only to onion nodes, so end-to-end encryption is enforced between the wallet and peers. All this without involving any exit node. Wasabi connects to each peer through a different Tor stream. A new Bitcoin peer is chosen for every transaction broadcast.
    Everything over Tor!
    Wasabi broadcast transactions to only one peer over Tor, and immediately after that the peer is disconnected.
     Adversaries identified
    • ISP
    • Tor Breaker Sybil Attacker With Thousands Of Full Nodes Over Onion
     Wasabi Wallet + full node
    TIP
    Wasabi has a partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.
     Private UTXO retrieval
    If you have a listening full node running in the background (not only Bitcoin Core, any full node) then Wasabi automatically picks it up and instead of asking peers for blocks, it asks for blocks from your own node. Using Wasabi this way results in the same privacy model as Bitcoin Core's, regarding Private UTXO Retrieval.
     Private transaction broadcasting
    Even when Wasabi is connected to your own node, it will broadcast the transaction in the above-described way: to one new peer over Tor.
     Universal Attacks
    Every time you use software that interacts with a Bitcoin network, and especially a Bitcoin node, you leave a sticky fingerprint in your traffic. It comes in the form of a small but unavoidable spike in volume every time a new block is mined and the nodes start gossiping about it. The blocks in Bitcoin are quite big, and the propagation speed is critical for consensus (greater delay means more frequent accidental forks), so such effect is predictable, and, in a sense, inherent to the Bitcoin architecture.
    ',23),S={href:"https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki",target:"_blank",rel:"noopener noreferrer"},E={href:"https://m417z.com/bitsniff/",target:"_blank",rel:"noopener noreferrer"},q=r('
     Protection
    There are many ways to go about it, but staying completely undetected is far from trivial - traditional privacy-enhancing tools mostly focus on the packet level, which is orthogonal to the technique. Let’s break down the potential defense vectors.
    • VPN / Tor - unlikely to affect the time series shape much, and therefore for larger traffic lengths the statistical significance of block-related spikes will inevitably become overwhelming.
    • Traffic mixing - for traffic volumes that are orders of magnitude higher than Bitcoin P2P communications, mixing is likely to be very effective. That would, however, demand constant shielding of both upstream and downstream communications, and couldn't be done effectively by just running the node on a general-purpose machine - any noticeably long unshielded period may be enough for detection.
    • Being your own ISP - too spicy for most, but that should work.
    • Blockstream Satellite - the ultimate solution. Eliminates the traffic analysis threat altogether.
    Beyond active measures available now, both the privacy and the bandwidth efficiency of Bitcoin communications are actively worked on. It is entirely possible that the messaging protocol will get to the point where block propagation doesn't trigger any significant spikes in traffic volume.
    ',4),O={href:"https://79jke.github.io/BitSniff/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://m417z.com/bitsniff/",target:"_blank",rel:"noopener noreferrer"},U={href:"https://youtu.be/9S8xsDq3PTU",target:"_blank",rel:"noopener noreferrer"},V=e("img",{src:c,alt:"Watch the video"},null,-1);function j(F,K){const o=s("router-link"),n=s("ExternalLinkIcon"),l=s("RouterLink");return h(),u("div",null,[b,p,e("nav",m,[e("ul",null,[e("li",null,[a(o,{to:"#problem"},{default:i(()=>[t("Problem")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#clearnet-light-clients"},{default:i(()=>[t("Clearnet light clients")]),_:1})])])]),e("li",null,[a(o,{to:"#wasabi-s-solution"},{default:i(()=>[t("Wasabi's solution")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#full-node-by-default-block-filters-over-tor"},{default:i(()=>[t("Full node by default & block filters over Tor")]),_:1})])])]),e("li",null,[a(o,{to:"#in-depth-comparison"},{default:i(()=>[t("In-depth comparison")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#bitcoin-core"},{default:i(()=>[t("Bitcoin Core")]),_:1})]),e("li",null,[a(o,{to:"#bitcoin-core-tor"},{default:i(()=>[t("Bitcoin Core + Tor")]),_:1})]),e("li",null,[a(o,{to:"#wasabi-wallet-light-node"},{default:i(()=>[t("Wasabi Wallet light node")]),_:1})]),e("li",null,[a(o,{to:"#wasabi-wallet-full-node"},{default:i(()=>[t("Wasabi Wallet + full node")]),_:1})])])]),e("li",null,[a(o,{to:"#universal-attacks"},{default:i(()=>[t("Universal Attacks")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#protection"},{default:i(()=>[t("Protection")]),_:1})])])])])]),v,g,y,w,e("p",null,[t("There are light wallets, which query a backend server to get information regarding specific addresses or use "),e("a",k,[t("BIP 37"),a(n)]),t(" bloom filtering SPV wallet protocol, which is "),e("a",_,[t("extremely bad for privacy"),a(n)]),t(". And there is Electrum, which "),e("a",T,[t("sends your addresses"),a(n)]),t(" to random Electrum servers.")]),B,e("p",null,[t("In order to fully verify everything, running a full node is essential. If "),e("a",P,[t("bitcoind"),a(n)]),t(" is installed and run on the same computer as Wasabi, then it will automatically and by default connect to the full node. It is also possible to connect Wasabi to a remote full node on another computer by specifying the local IP address or Tor onion service in the settings. Then, Wasabi pulls the verified blocks and queries the mempool from the full node.")]),e("div",x,[W,e("p",null,[t("Wasabi has a "),a(l,{to:"/using-wasabi/BitcoinFullNode.html"},{default:i(()=>[t("partial Bitcoin Knots integration")]),_:1}),t(". This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.")])]),e("p",null,[t("However, even if no full node is installed, Wasabi has a light client mode based on "),e("a",I,[t("BIP 158 block filters"),a(n)]),t(". The Wasabi server sends a filter of all the transactions in each block to all the users. Then, users check locally if the block contains any transactions with their addresses. If not, then the filter is stored for later reference, and no block is downloaded. However, if there is a user transaction in that block, then Wasabi connects to a random Bitcoin P2P node over Tor and asks for this entire block, not only one transaction. This block request is indistinguishable from the regular P2P gossip, and thus nobody, neither the server nor the full node, know which addresses belong to the user.")]),C,e("blockquote",null,[e("p",null,[t("Bitcoin transaction propagation does not hide the source of a transaction very well, especially against a “supernode” eavesdropper that forms a large number of outgoing connections to reachable nodes on the network. "),e("a",A,[t("Dandelion: Privacy-Preserving Transaction Propagation"),a(n)]),t(".")])]),N,e("p",null,[t("Notably, the volume of block-related messages was drastically reduced since the introduction of Compact Block Relay ("),e("a",S,[t("BIP 152"),a(n)]),t(". Instead of requesting whole blocks, mostly consisting of transactions already known to the node, the peer informed of a new block is only requesting the missing transactions. Yet the amount of extra communications in the seconds following a new block is still considerable. This effect may not be noticeable for a single block, but over time it gets statistically significant and may get exploited.")]),e("p",null,[t("As reported by "),e("a",E,[t("Niko Kudriastev and Michael Maltsev"),a(n)]),t(", it is possible to detect Bitcoin communications using nothing but traffic volume over time - a piece of information even most privacy concerned individuals are likely leaking to their law-abiding Internet Service Provider. In this case, using a VPN and running the node over Tor may not be enough to avoid being detected.")]),q,e("p",null,[t("You can read more about BitSniff "),e("a",O,[t("here"),a(n)]),t(" and check the interactive demo "),e("a",L,[t("here"),a(n)]),t(".")]),e("p",null,[e("a",U,[V,a(n)])])])}const X=d(f,[["render",j],["__file","NetworkLevelPrivacy.html.vue"]]);export{X as default};
+import{_ as c}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,r as s,o as h,c as u,a as e,d as a,w as i,b as t,e as r}from"./app.65e5b6fd.js";const f={},b=e("h1",{id:"network-level-privacy-bitcoin-core-vs-wasabi-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#network-level-privacy-bitcoin-core-vs-wasabi-wallet","aria-hidden":"true"},"#"),t(" Network-Level Privacy - Bitcoin Core vs Wasabi Wallet")],-1),p=e("p",null,"Bitcoin is a peer-to-peer network of full nodes that define, verify, and enforce the Bitcoin consensus rules. There is a lot of communication between them and metadata can be used to de-anonymize Bitcoin users.",-1),m={class:"table-of-contents"},v=e("h2",{id:"problem",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#problem","aria-hidden":"true"},"#"),t(" Problem")],-1),g=e("h3",{id:"clearnet-light-clients",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#clearnet-light-clients","aria-hidden":"true"},"#"),t(" Clearnet light clients")],-1),y=e("p",null,"When the communication to the network is unencrypted over clearnet, then there is an easy correlation of the Bitcoin transactions to the IP address of the peer who sent it. The IP address can even be used to find the physical location of the user!",-1),w=e("p",null,"A Bitcoin full node broadcasts not just the transactions of its user, but it also gossips all of the other transactions that it has received from its peers. Thus it is very difficult to find out which transactions originated from which full node. However, when a node or a wallet does not gossip all transactions, but only the transactions of its user, then it is easier to find out which node has sent those specific transactions.",-1),k={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},_={href:"https://jonasnick.github.io/blog/2015/02/12/privacy-in-bitcoinj/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://www.reddit.com/r/Bitcoin/comments/2feox9/electrum_securityprivacy_model/ck8szc0/",target:"_blank",rel:"noopener noreferrer"},B=r('
    DANGER
    When the user sends the extended public key or a filter of all the addresses to the central server, then the server can COMPLETELY deanonymize the users.
     Wasabi's solution
     Full node by default & block filters over Tor
    Wasabi checks if there is a local Tor instance installed, and if so, it uses this to onion-route all the traffic to and from the network. If Tor is not already installed, then it is accessed automatically from within Wasabi. This means that by default, all network communication is secured from outside snooping and the IP address is hidden.
    ',4),P={href:"https://github.com/bitcoin/bitcoin",target:"_blank",rel:"noopener noreferrer"},x={class:"custom-container tip"},W=e("p",{class:"custom-container-title"},"Wasabi ships with Bitcoin Knots!",-1),I={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},C=r('
    Privacy by default!
    Wasabi has network-level privacy as good as a Bitcoin full node.
     In-depth comparison
    Furthermore, network-level privacy consists of two sub-categories.
    • Private UTXO Retrieval
    • Private Transaction Broadcasting
     Bitcoin Core
     Private UTXO retrieval
    Bitcoin Core downloads all the blocks ever created and establishes your wallet balances locally. This is as good as it gets.
     Private transaction broadcasting
    Bitcoin Core broadcasts transactions to other peers on the clearnet, unencrypted. Other peers cannot figure out which transaction originates from a specific node because Core does not only broadcast its own transactions but also propagates every other transaction that hits its mempool. However, some papers note it’s not bulletproof:
    ',9),A={href:"https://github.com/bitcoin/bips/blob/master/bip-0156.mediawiki",target:"_blank",rel:"noopener noreferrer"},N=r('
     Adversaries identified
    • Malicious Peer
    • Supernode
     Bitcoin Core + Tor
    You can use Bitcoin Core with Tor, which solves some of the above-mentioned issues. In this case, a supernode cannot track back transactions to your IP address.
    An entity that can break Tor is a universal adversary, however, most Tor attacks are not possible if exit nodes are not involved. It is reasonable to assume that this entity can break the onion routing, not Tor's encryption itself.
     Adversaries identified
    • Tor breaker
     Wasabi Wallet light node
     Private UTXO retrieval
    The backend server serves block filters to all the clients over Tor. From those filters, the clients figure out which blocks they are interested in and download them [and some false positive blocks] from peers. One block per peer, and always over a fresh Tor stream. When a block is acquired, the peer gets disconnected. Because of the end-to-end encryption of the onion network, it immediately defeats an ISP adversary and makes the already impossible job of the Sybil adversary even more impossible. The only adversary that could possibly overcome this would have to setup thousands of full nodes over Tor and also break Tor itself.
     Private transaction broadcasting
    All Wasabi traffic is tunneled through Tor. Wasabi connects only to onion nodes, so end-to-end encryption is enforced between the wallet and peers. All this without involving any exit node. Wasabi connects to each peer through a different Tor stream. A new Bitcoin peer is chosen for every transaction broadcast.
    Everything over Tor!
    Wasabi broadcast transactions to only one peer over Tor, and immediately after that the peer is disconnected.
     Adversaries identified
    • ISP
    • Tor Breaker Sybil Attacker With Thousands Of Full Nodes Over Onion
     Wasabi Wallet + full node
    TIP
    Wasabi has a partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.
     Private UTXO retrieval
    If you have a listening full node running in the background (not only Bitcoin Core, any full node) then Wasabi automatically picks it up and instead of asking peers for blocks, it asks for blocks from your own node. Using Wasabi this way results in the same privacy model as Bitcoin Core's, regarding Private UTXO Retrieval.
     Private transaction broadcasting
    Even when Wasabi is connected to your own node, it will broadcast the transaction in the above-described way: to one new peer over Tor.
     Universal Attacks
    Every time you use software that interacts with a Bitcoin network, and especially a Bitcoin node, you leave a sticky fingerprint in your traffic. It comes in the form of a small but unavoidable spike in volume every time a new block is mined and the nodes start gossiping about it. The blocks in Bitcoin are quite big, and the propagation speed is critical for consensus (greater delay means more frequent accidental forks), so such effect is predictable, and, in a sense, inherent to the Bitcoin architecture.
    ',23),S={href:"https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki",target:"_blank",rel:"noopener noreferrer"},E={href:"https://m417z.com/bitsniff/",target:"_blank",rel:"noopener noreferrer"},q=r('
     Protection
    There are many ways to go about it, but staying completely undetected is far from trivial - traditional privacy-enhancing tools mostly focus on the packet level, which is orthogonal to the technique. Let’s break down the potential defense vectors.
    • VPN / Tor - unlikely to affect the time series shape much, and therefore for larger traffic lengths the statistical significance of block-related spikes will inevitably become overwhelming.
    • Traffic mixing - for traffic volumes that are orders of magnitude higher than Bitcoin P2P communications, mixing is likely to be very effective. That would, however, demand constant shielding of both upstream and downstream communications, and couldn't be done effectively by just running the node on a general-purpose machine - any noticeably long unshielded period may be enough for detection.
    • Being your own ISP - too spicy for most, but that should work.
    • Blockstream Satellite - the ultimate solution. Eliminates the traffic analysis threat altogether.
    Beyond active measures available now, both the privacy and the bandwidth efficiency of Bitcoin communications are actively worked on. It is entirely possible that the messaging protocol will get to the point where block propagation doesn't trigger any significant spikes in traffic volume.
    ',4),O={href:"https://79jke.github.io/BitSniff/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://m417z.com/bitsniff/",target:"_blank",rel:"noopener noreferrer"},U={href:"https://youtu.be/9S8xsDq3PTU",target:"_blank",rel:"noopener noreferrer"},V=e("img",{src:c,alt:"Watch the video"},null,-1);function j(F,K){const o=s("router-link"),n=s("ExternalLinkIcon"),l=s("RouterLink");return h(),u("div",null,[b,p,e("nav",m,[e("ul",null,[e("li",null,[a(o,{to:"#problem"},{default:i(()=>[t("Problem")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#clearnet-light-clients"},{default:i(()=>[t("Clearnet light clients")]),_:1})])])]),e("li",null,[a(o,{to:"#wasabi-s-solution"},{default:i(()=>[t("Wasabi's solution")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#full-node-by-default-block-filters-over-tor"},{default:i(()=>[t("Full node by default & block filters over Tor")]),_:1})])])]),e("li",null,[a(o,{to:"#in-depth-comparison"},{default:i(()=>[t("In-depth comparison")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#bitcoin-core"},{default:i(()=>[t("Bitcoin Core")]),_:1})]),e("li",null,[a(o,{to:"#bitcoin-core-tor"},{default:i(()=>[t("Bitcoin Core + Tor")]),_:1})]),e("li",null,[a(o,{to:"#wasabi-wallet-light-node"},{default:i(()=>[t("Wasabi Wallet light node")]),_:1})]),e("li",null,[a(o,{to:"#wasabi-wallet-full-node"},{default:i(()=>[t("Wasabi Wallet + full node")]),_:1})])])]),e("li",null,[a(o,{to:"#universal-attacks"},{default:i(()=>[t("Universal Attacks")]),_:1}),e("ul",null,[e("li",null,[a(o,{to:"#protection"},{default:i(()=>[t("Protection")]),_:1})])])])])]),v,g,y,w,e("p",null,[t("There are light wallets, which query a backend server to get information regarding specific addresses or use "),e("a",k,[t("BIP 37"),a(n)]),t(" bloom filtering SPV wallet protocol, which is "),e("a",_,[t("extremely bad for privacy"),a(n)]),t(". And there is Electrum, which "),e("a",T,[t("sends your addresses"),a(n)]),t(" to random Electrum servers.")]),B,e("p",null,[t("In order to fully verify everything, running a full node is essential. If "),e("a",P,[t("bitcoind"),a(n)]),t(" is installed and run on the same computer as Wasabi, then it will automatically and by default connect to the full node. It is also possible to connect Wasabi to a remote full node on another computer by specifying the local IP address or Tor onion service in the settings. Then, Wasabi pulls the verified blocks and queries the mempool from the full node.")]),e("div",x,[W,e("p",null,[t("Wasabi has a "),a(l,{to:"/using-wasabi/BitcoinFullNode.html"},{default:i(()=>[t("partial Bitcoin Knots integration")]),_:1}),t(". This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.")])]),e("p",null,[t("However, even if no full node is installed, Wasabi has a light client mode based on "),e("a",I,[t("BIP 158 block filters"),a(n)]),t(". The Wasabi server sends a filter of all the transactions in each block to all the users. Then, users check locally if the block contains any transactions with their addresses. If not, then the filter is stored for later reference, and no block is downloaded. However, if there is a user transaction in that block, then Wasabi connects to a random Bitcoin P2P node over Tor and asks for this entire block, not only one transaction. This block request is indistinguishable from the regular P2P gossip, and thus nobody, neither the server nor the full node, know which addresses belong to the user.")]),C,e("blockquote",null,[e("p",null,[t("Bitcoin transaction propagation does not hide the source of a transaction very well, especially against a “supernode” eavesdropper that forms a large number of outgoing connections to reachable nodes on the network. "),e("a",A,[t("Dandelion: Privacy-Preserving Transaction Propagation"),a(n)]),t(".")])]),N,e("p",null,[t("Notably, the volume of block-related messages was drastically reduced since the introduction of Compact Block Relay ("),e("a",S,[t("BIP 152"),a(n)]),t(". Instead of requesting whole blocks, mostly consisting of transactions already known to the node, the peer informed of a new block is only requesting the missing transactions. Yet the amount of extra communications in the seconds following a new block is still considerable. This effect may not be noticeable for a single block, but over time it gets statistically significant and may get exploited.")]),e("p",null,[t("As reported by "),e("a",E,[t("Niko Kudriastev and Michael Maltsev"),a(n)]),t(", it is possible to detect Bitcoin communications using nothing but traffic volume over time - a piece of information even most privacy concerned individuals are likely leaking to their law-abiding Internet Service Provider. In this case, using a VPN and running the node over Tor may not be enough to avoid being detected.")]),q,e("p",null,[t("You can read more about BitSniff "),e("a",O,[t("here"),a(n)]),t(" and check the interactive demo "),e("a",L,[t("here"),a(n)]),t(".")]),e("p",null,[e("a",U,[V,a(n)])])])}const X=d(f,[["render",j],["__file","NetworkLevelPrivacy.html.vue"]]);export{X as default};
diff --git a/assets/PasswordBestPractices.html.d41d69dd.js b/assets/PasswordBestPractices.html.4683a4ab.js
similarity index 99%
rename from assets/PasswordBestPractices.html.d41d69dd.js
rename to assets/PasswordBestPractices.html.4683a4ab.js
index 9c7a2a6d87..d603db5422 100644
--- a/assets/PasswordBestPractices.html.d41d69dd.js
+++ b/assets/PasswordBestPractices.html.4683a4ab.js
@@ -1,3 +1,3 @@
-import{_ as d,r as l,o as c,c as p,a as e,d as a,w as o,b as s,e as n}from"./app.a5b7c2b2.js";const h={},u=e("h1",{id:"password-best-practices",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#password-best-practices","aria-hidden":"true"},"#"),s(" Password best practices")],-1),m={class:"table-of-contents"},w=n('
     Introduction
    You shouldn't try to re-invent the wheel for something as complicated and nuanced as cryptography, and especially in regards to entropy.
    These are some of the industry best practices:
    TIP
    Don't "roll your own" crypto.
     Password basics
    ',5),f=e("li",null,[e("p",null,'Randomness is the single-most important requirement for a strong password, because randomness means that the password has no predictable pattern to it. This makes it impossible to crack without doing an exhaustive, "brute-force" attack.')],-1),y=e("li",null,[e("p",null,[s("Assuming a password is constructed randomly, its length has the most impact on its strength. However, a password that is very long, but not randomly constructed, such as: "),e("code",null,"thequickbrownfoxjumpedoverthelazydogsback"),s(", or a passage from literature, is certain to be on every serious hacker's guess list.")])],-1),b=e("h2",{id:"what-not-to-do",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-not-to-do","aria-hidden":"true"},"#"),s(" What not to do")],-1),g=e("p",null,"Here are a few examples that do it completely wrong. You should not generate your password like this:",-1),v=e("code",null,"Emma1992",-1),_={href:"https://en.wikipedia.org/wiki/List_of_the_most_common_passwords#SplashData",target:"_blank",rel:"noopener noreferrer"},k=e("li",null,[e("p",null,"Do not use the same password that you have used in other places. Because if one password is leaked, then other ones are compromised.")],-1),x=e("li",null,[e("p",null,"Do try to use a mix of uppercase and lowercase letters, numbers, and special characters (&$%@ etc.) in your password.")],-1),q=e("p",null,'Do not take a famous quote, or well-known passage from literature and use it for a password. It will not fool any serious hacker, even if you throw in substitutions such as: "@" instead of "a", or "$" instead of "s".',-1),P={class:"custom-container danger"},D=e("p",{class:"custom-container-title"},"Make a secure password!!",-1),T=e("h2",{id:"use-diceware",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#use-diceware","aria-hidden":"true"},"#"),s(" Use Diceware")],-1),E=e("p",null,"Rolling dice is an easy and effective way to get high entropy and randomness in a password that can even be memorized.",-1),F=e("p",null,"The Diceware method is a great strategy for your most precious passwords (e.g. the password to your computer, your backups, or your encryption key). You can even use Diceware to create secure wallets.",-1),I={href:"https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases",target:"_blank",rel:"noopener noreferrer"},S=n("
    To start, roll the die five times. Record the number from each roll using the pen and paper. You will end up with a five-digit number. We got 52611. Now search on the Diceware list for the five digit number you just created. Write down the word the number corresponds to, in our case it is salvo. This word by itself is not a good password, it would only take about a thousandth of a second to crack. Repeat the dice rolling process at least five more times.
    After six sets of five rolls, we ended up with 52611 51631 63432 43123 21641 and 14146. This corresponds to the password salvo rhoda walton mudd croft bride.
    This six-word passphrase, even though easy to remember, is just one of 2.21 x 10^23, or 221 sextillion possible six-word combinations taken from the list of 7776 words. A computer capable of 1 trillion guesses/second would take, on average, over 3500 years to correctly guess this or any six-word combination of words from the list, if they are chosen randomly.
    ",3),B={href:"https://blog.securityevaluators.com/understanding-password-complexity-5e0d23643a2a",target:"_blank",rel:"noopener noreferrer"},L=n(`
     Use a dictionary
    All of the major languages have at least 100,000 words in their dictionaries. Most have over 300,000 words. You can take a dictionary in any language that you are comfortable with and create a very strong password by randomly selecting as few as 5 words from it.
    The quick, but not technically random way would be to flip open your chosen dictionary to any seemingly random page, close your eyes, and put your fingertip down on the page. Choose the word nearest your fingertip that has at least 4 letters. Repeat this process at least 4 more times.
    If you'd prefer a truly random way to select pages, and you are using either Windows or Linux, you can easily create random numbers in a selected range (such as the number of pages in your dictionary) from your terminal.
    Assuming your dictionary has, for example, 854 pages:
    Windows: Open a Powershell terminal and enter:
    [C:\\User>] get-random -maximum 854
+import{_ as d,r as l,o as c,c as p,a as e,d as a,w as o,b as s,e as n}from"./app.65e5b6fd.js";const h={},u=e("h1",{id:"password-best-practices",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#password-best-practices","aria-hidden":"true"},"#"),s(" Password best practices")],-1),m={class:"table-of-contents"},w=n('
     Introduction
    You shouldn't try to re-invent the wheel for something as complicated and nuanced as cryptography, and especially in regards to entropy.
    These are some of the industry best practices:
    TIP
    Don't "roll your own" crypto.
     Password basics
    ',5),f=e("li",null,[e("p",null,'Randomness is the single-most important requirement for a strong password, because randomness means that the password has no predictable pattern to it. This makes it impossible to crack without doing an exhaustive, "brute-force" attack.')],-1),y=e("li",null,[e("p",null,[s("Assuming a password is constructed randomly, its length has the most impact on its strength. However, a password that is very long, but not randomly constructed, such as: "),e("code",null,"thequickbrownfoxjumpedoverthelazydogsback"),s(", or a passage from literature, is certain to be on every serious hacker's guess list.")])],-1),b=e("h2",{id:"what-not-to-do",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#what-not-to-do","aria-hidden":"true"},"#"),s(" What not to do")],-1),g=e("p",null,"Here are a few examples that do it completely wrong. You should not generate your password like this:",-1),v=e("code",null,"Emma1992",-1),_={href:"https://en.wikipedia.org/wiki/List_of_the_most_common_passwords#SplashData",target:"_blank",rel:"noopener noreferrer"},k=e("li",null,[e("p",null,"Do not use the same password that you have used in other places. Because if one password is leaked, then other ones are compromised.")],-1),x=e("li",null,[e("p",null,"Do try to use a mix of uppercase and lowercase letters, numbers, and special characters (&$%@ etc.) in your password.")],-1),q=e("p",null,'Do not take a famous quote, or well-known passage from literature and use it for a password. It will not fool any serious hacker, even if you throw in substitutions such as: "@" instead of "a", or "$" instead of "s".',-1),P={class:"custom-container danger"},D=e("p",{class:"custom-container-title"},"Make a secure password!!",-1),T=e("h2",{id:"use-diceware",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#use-diceware","aria-hidden":"true"},"#"),s(" Use Diceware")],-1),E=e("p",null,"Rolling dice is an easy and effective way to get high entropy and randomness in a password that can even be memorized.",-1),F=e("p",null,"The Diceware method is a great strategy for your most precious passwords (e.g. the password to your computer, your backups, or your encryption key). You can even use Diceware to create secure wallets.",-1),I={href:"https://www.eff.org/deeplinks/2016/07/new-wordlists-random-passphrases",target:"_blank",rel:"noopener noreferrer"},S=n("
    To start, roll the die five times. Record the number from each roll using the pen and paper. You will end up with a five-digit number. We got 52611. Now search on the Diceware list for the five digit number you just created. Write down the word the number corresponds to, in our case it is salvo. This word by itself is not a good password, it would only take about a thousandth of a second to crack. Repeat the dice rolling process at least five more times.
    After six sets of five rolls, we ended up with 52611 51631 63432 43123 21641 and 14146. This corresponds to the password salvo rhoda walton mudd croft bride.
    This six-word passphrase, even though easy to remember, is just one of 2.21 x 10^23, or 221 sextillion possible six-word combinations taken from the list of 7776 words. A computer capable of 1 trillion guesses/second would take, on average, over 3500 years to correctly guess this or any six-word combination of words from the list, if they are chosen randomly.
    ",3),B={href:"https://blog.securityevaluators.com/understanding-password-complexity-5e0d23643a2a",target:"_blank",rel:"noopener noreferrer"},L=n(`
     Use a dictionary
    All of the major languages have at least 100,000 words in their dictionaries. Most have over 300,000 words. You can take a dictionary in any language that you are comfortable with and create a very strong password by randomly selecting as few as 5 words from it.
    The quick, but not technically random way would be to flip open your chosen dictionary to any seemingly random page, close your eyes, and put your fingertip down on the page. Choose the word nearest your fingertip that has at least 4 letters. Repeat this process at least 4 more times.
    If you'd prefer a truly random way to select pages, and you are using either Windows or Linux, you can easily create random numbers in a selected range (such as the number of pages in your dictionary) from your terminal.
    Assuming your dictionary has, for example, 854 pages:
    Windows: Open a Powershell terminal and enter:
    [C:\\User>] get-random -maximum 854
 
    Linux: Open a terminal and enter:
    [user@you:~$] echo $(( $RANDOM % 854 ))
 
    Each time you repeat this command, your operating system will return a random number somewhere in the range of available pages of your dictionary.
    Use this function to pick pages in a truly random manner, and select the needed words in the same way as before.
    Both this and the Diceware method are good ways to create a password with sufficient randomness that was generated completely off-line.
     Use an open-source password manager
    There are several well-known, cross-platform, and open-source password managers available. The main requirement besides being open-source, is a cryptographically secure random number generator, with the ability to generate significant entropy while using letters, numbers, and special characters.
    It is recommended that you use all available characters when generating a password, and the length of the password should be at least 12 characters for minimally sufficient entropy.
    It is up to the user to choose between a password manager that stores its data in the cloud, making it easy to stay in sync across various devices, or one that only stores its data locally.
    As it so often happens, more convenience means less security in this decision.
     Password entropy
    "Entropy" is a term commonly used to define password strength. It is typically used to describe the combined effect of randomness, length, and number of characters (lowercase/uppercase letters, numbers, and special characters) or words in a password or passphrase.
    Calculating entropy allows the strength of different randomly constructed passwords or phrases to be compared. It also defines the size of the search-space an attacker would need to cover to find the password by trying all possibilities.
     How to calculate entropy
    Assuming a password or passphrase is constructed randomly, its level of entropy can be calculated in this way:
    • For a password, the total number of possible outcomes given a specific length (L), and number of characters used (C), is: C raised to the power of L, or C^L.
       Example: jwodnrosqf is lowercase only (C = 26) and 10 characters long (L = 10). So, 26^10 = 141,000,000,000,000 (141 trillion).

       Including uppercase letters in the same password: jWoDNrosqF to double (C), results in 52^10 possible passwords = 145,000,000,000,000,000 (145 quadrillion).

       Including special characters in the same password: jW0DNro$qF raises (C) to 95, resulting in 95^10 possibilities = 59,900,000,000,000,000,000 (59.9 quintillion).
    • For a passphrase chosen randomly from a list of words, the total number of possible outcomes given a specific number of words (N) and wordlist size (S) is: S raised to the power of N, or S^N.
       Example: The EFF Diceware list contains 7776 words. Randomly selecting 5 words from the list results in 7776^5 possible passphrases = 28,400,000,000,000,000,000 (28.4 quintillion).
    Just knowing how to do these basic calculations allows you to compare the strength of different randomly-generated passwords or phrases.
     "Bits" of entropy
    `,25),N=e("code",null,"bits of entropy",-1),j={href:"https://miniwebtool.com/log-base-2-calculator/",target:"_blank",rel:"noopener noreferrer"},A=n('
    For example, there are 7776 words on the EFF wordlist commonly used with dice to create passphrases. Plugging 7776 into the calculator to get log2(7776), it is shown that each word taken randomly from the list contributes 12.92 bits of entropy to the strength of the passphrase. So, a 5-word passphrase selected randomly from the EFF list will have 5 x 12.92 = 64 bits of entropy.
    Since the combination of: lowercase + uppercase letters, numbers, and special characters = 95, a password constructed using all of these will have log2(95), or 6.57 bits of entropy for each character that comprises the password.
    From that, we can now calculate that, in order to get the same level of entropy with a password instead of a 5-word passphrase, the password must be at least 10 characters in length.
     How much entropy is needed
    Entropy matters because it allows one to compare the required search-space of a potential password with the search-speed known to be available to various potential adversaries. In doing so, it is possible to then know how long it would take an adversary with known resources to attempt every mathematically possible password or passphrase for a given level of entropy.
    Edward Snowden revealed in 2013 that the NSA had the ability to guess passwords at a rate of 1 trillion guesses/second. At that speed of guessing, the password in the above example (28.4 quintillion possibilities) could be guessed in at most, 11 months.
    Since there is an equal chance of finding the password in the first half of the total number of guesses as there is in finding it in the second half of the total number, it is accurate to assume that on average, a password will be found in 1/2 of the time required to do an exhaustive search. That means just over 5 months for the example just mentioned.
    Keep in mind that Snowden's information in quite old, in a processing-power context. We have no way of knowing what is currently possible, so if a State-Level attacker is a part of your assumed threat-model, it would be wise to assume that their tools are now much more powerful.
    Even if a given threat-model does not include State-Level attackers, it is still important to consider that there are GPU-based password hacking tools publicly available that are capable of guessing well into the billions of guesses/second.
    ',9);function C(R,U){const t=l("router-link"),i=l("RouterLink"),r=l("ExternalLinkIcon");return c(),p("div",null,[u,e("nav",m,[e("ul",null,[e("li",null,[a(t,{to:"#introduction"},{default:o(()=>[s("Introduction")]),_:1})]),e("li",null,[a(t,{to:"#password-basics"},{default:o(()=>[s("Password basics")]),_:1})]),e("li",null,[a(t,{to:"#what-not-to-do"},{default:o(()=>[s("What not to do")]),_:1})]),e("li",null,[a(t,{to:"#use-diceware"},{default:o(()=>[s("Use Diceware")]),_:1})]),e("li",null,[a(t,{to:"#use-a-dictionary"},{default:o(()=>[s("Use a dictionary")]),_:1})]),e("li",null,[a(t,{to:"#use-an-open-source-password-manager"},{default:o(()=>[s("Use an open-source password manager")]),_:1})]),e("li",null,[a(t,{to:"#password-entropy"},{default:o(()=>[s("Password entropy")]),_:1}),e("ul",null,[e("li",null,[a(t,{to:"#how-to-calculate-entropy"},{default:o(()=>[s("How to calculate entropy")]),_:1})]),e("li",null,[a(t,{to:"#bits-of-entropy"},{default:o(()=>[s('"Bits" of entropy')]),_:1})]),e("li",null,[a(t,{to:"#how-much-entropy-is-needed"},{default:o(()=>[s("How much entropy is needed")]),_:1})])])])])]),w,e("ol",null,[f,y,e("li",null,[e("p",null,[s('"Entropy" is a term commonly used to define the strength of a random password. There is a tutorial about how to calculate and evaluate entropy in your password '),a(i,{to:"/using-wasabi/PasswordBestPractices.html#how-to-calculate-entropy"},{default:o(()=>[s("here")]),_:1}),s(".")])])]),b,g,e("ol",null,[e("li",null,[e("p",null,[s("Do not use publicly known information like your grandma's maiden name and the birthday of your dog. "),v,s(" is a really, really, really bad password, because it can easily be guessed and it is very short. Here is a list of the worst and "),e("a",_,[s("most commonly used passwords"),a(r)]),s(" in recent years. Password hackers start with lists like this.")])]),k,x,e("li",null,[q,e("div",P,[D,e("p",null,[s("It is of utmost importance to generate a secure password following "),a(i,{to:"/using-wasabi/PasswordBestPractices.html"},{default:o(()=>[s("best practices")]),_:1}),s(".")])])])]),T,E,F,e("p",null,[s("To generate a password using Diceware, you just need a high-quality die, a pen, and some paper. You can find EFF's Diceware list at the "),e("a",I,[s("Electronic Frontier Foundation website"),a(r)]),s(". Make sure you are alone and there are no cameras nearby. For maximum protection, disconnect your computer from the internet (after you save the Diceware list) and cover your webcam.")]),S,e("p",null,[s("A 6-word passphrase derived as just discussed has 77 "),a(i,{to:"/using-wasabi/PasswordBestPractices.html#how-to-calculate-entropy"},{default:o(()=>[s("bits of entropy")]),_:1}),s(". Best practices for being secure against any adversary "),e("a",B,[s("currently recommend"),a(r)]),s(" a minimum of near 80 bits of entropy, so this example phrase barely qualifies.")]),L,e("p",null,[s("Password entropy is often discussed and compared in a context of "),N,s(". This is, of course, because computers can only process 0's and 1's, or bits, so everything related is expressed that way. To calculate bits of entropy, use a "),e("a",j,[s("calculator that does logarithms"),a(r)]),s(" and compute log2(x), where x = the total number of possible outcomes for an event.")]),A])}const H=d(h,[["render",C],["__file","PasswordBestPractices.html.vue"]]);export{H as default};
diff --git a/assets/PasswordFinder.html.3173dc09.js b/assets/PasswordFinder.html.fe34ca22.js
similarity index 97%
rename from assets/PasswordFinder.html.3173dc09.js
rename to assets/PasswordFinder.html.fe34ca22.js
index 935a852b8e..a0adf974a7 100644
--- a/assets/PasswordFinder.html.3173dc09.js
+++ b/assets/PasswordFinder.html.fe34ca22.js
@@ -1 +1 @@
-import{_ as n,r as o,o as l,c as d,a as e,d as s,w as i,b as t,e as c}from"./app.a5b7c2b2.js";const h="/ForgotPassword.png",p={},w=e("h1",{id:"password-finder",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#password-finder","aria-hidden":"true"},"#"),t(" Password Finder")],-1),u=e("p",null,"Wasabi Password Finder is a tool for helping those who made a mistake typing the password during the wallet creation process. This tool tries to find the password that decrypts the encrypted secret key stored in a given wallet file.",-1),m={class:"table-of-contents"},_=e("h2",{id:"limitations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations","aria-hidden":"true"},"#"),t(" Limitations")],-1),f={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},g=c('
    WARNING
    It is important to know that the Wasabi Password Finder is not for breaking wallet passwords but for finding errors (typos) in an already known password, and that it's success rate is limited.
     Usage
    After an incorrect password is entered when opening a wallet, Forgot Password will show up.
    Wasabi Wallet Forgot Password
    First you will be asked questions, like your most likely password, which language, which characters it contains etc. After that it will search if your password can be found.
    ',5);function b(k,y){const a=o("router-link"),r=o("ExternalLinkIcon");return l(),d("div",null,[w,u,e("nav",m,[e("ul",null,[e("li",null,[s(a,{to:"#limitations"},{default:i(()=>[t("Limitations")]),_:1})]),e("li",null,[s(a,{to:"#usage"},{default:i(()=>[t("Usage")]),_:1})])])]),_,e("p",null,[t("Wasabi Wallet protects the encrypted secret key with the same technology used to protect paper wallets ("),e("a",f,[t("BIP 38"),s(r)]),t(") and for that reason, it is computationally infeasible to brute force the password using all the possible combinations (assuming a secure password was chosen).")]),g])}const F=n(p,[["render",b],["__file","PasswordFinder.html.vue"]]);export{F as default};
+import{_ as n,r as o,o as l,c as d,a as e,d as s,w as i,b as t,e as c}from"./app.65e5b6fd.js";const h="/ForgotPassword.png",p={},w=e("h1",{id:"password-finder",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#password-finder","aria-hidden":"true"},"#"),t(" Password Finder")],-1),u=e("p",null,"Wasabi Password Finder is a tool for helping those who made a mistake typing the password during the wallet creation process. This tool tries to find the password that decrypts the encrypted secret key stored in a given wallet file.",-1),m={class:"table-of-contents"},_=e("h2",{id:"limitations",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#limitations","aria-hidden":"true"},"#"),t(" Limitations")],-1),f={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},g=c('
    WARNING
    It is important to know that the Wasabi Password Finder is not for breaking wallet passwords but for finding errors (typos) in an already known password, and that it's success rate is limited.
     Usage
    After an incorrect password is entered when opening a wallet, Forgot Password will show up.
    Wasabi Wallet Forgot Password
    First you will be asked questions, like your most likely password, which language, which characters it contains etc. After that it will search if your password can be found.
    ',5);function b(k,y){const a=o("router-link"),r=o("ExternalLinkIcon");return l(),d("div",null,[w,u,e("nav",m,[e("ul",null,[e("li",null,[s(a,{to:"#limitations"},{default:i(()=>[t("Limitations")]),_:1})]),e("li",null,[s(a,{to:"#usage"},{default:i(()=>[t("Usage")]),_:1})])])]),_,e("p",null,[t("Wasabi Wallet protects the encrypted secret key with the same technology used to protect paper wallets ("),e("a",f,[t("BIP 38"),s(r)]),t(") and for that reason, it is computationally infeasible to brute force the password using all the possible combinations (assuming a secure password was chosen).")]),g])}const F=n(p,[["render",b],["__file","PasswordFinder.html.vue"]]);export{F as default};
diff --git a/assets/PayJoin.html.60688e0c.js b/assets/PayJoin.html.46db34cb.js
similarity index 99%
rename from assets/PayJoin.html.60688e0c.js
rename to assets/PayJoin.html.46db34cb.js
index 1925559687..6e3462eecb 100644
--- a/assets/PayJoin.html.60688e0c.js
+++ b/assets/PayJoin.html.46db34cb.js
@@ -1,4 +1,4 @@
-import{_ as r,r as a,o as c,c as l,a as e,d as n,w as i,b as t,e as d}from"./app.a5b7c2b2.js";const h="/PayJoinSend.png",u="/PayJoinPreviewTransaction.png",p={},f=e("h1",{id:"payjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#payjoin","aria-hidden":"true"},"#"),t(" PayJoin")],-1),b={class:"table-of-contents"},v=e("h2",{id:"sending-payjoin-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#sending-payjoin-step-by-step","aria-hidden":"true"},"#"),t(" Sending PayJoin step-by-step")],-1),m=e("li",null,[e("p",null,[t("Load a wallet and open the "),e("code",null,"Send"),t(" dialog.")])],-1),y={href:"https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki",target:"_blank",rel:"noopener noreferrer"},g=e("code",null,"pj=",-1),_=e("code",null,"To",-1),P=e("code",null,"Send",-1),w=e("code",null,"bitcoin:tb1q0382a3m2jzvyk5lkea5h5jcht88xa6l0jufgwx?amount=0.00010727&pj=https://payjoin.test.kukks.org/BTC/pj",-1),k=d('
    Send Bitcoin PayJoin transaction in Wasabi Wallet
    1. Click Continue.
    2. Enter the label.
    3. At Preview Transaction, verify that the information is correct.
    PayJoinPreviewTransaction
    1. Click Confirm, and type in the password.
    The success of a PayJoin transaction is not something that depends on Wasabi.
    It may happen that the transaction is broadcast with success, but that it is not a PayJoin. This can happen for several reasons including:
    • The receiver did not have any utxos to contribute towards a PayJoin.
    • Your wallet does not use the same address format as the receiver's.
    • The PayJoin server is not available.
     The goal of PayJoin
    PayJoin is a collaborative transaction between the sender and the receiver of a payment, for example the merchant and the customer. The goal of the protocol is to break the common input ownership heuristic, while making it difficult to fingerprint that the transaction is in fact a CoinJoin. Further, it reduces the transaction fees paid by the merchant due to consolidation of coins.
     Coordination
    The coordination of this coinjoin is done with the PayToEndPoint [P2EP] concept. The receiver is reachable over the internet, either over a Tor onion service or clearnet IP address. The link is included in a BIP21 Bitcoin URI, and is provided to the sender as the payment invoice. The sender uses this onion service or IP address to connect to the server of the receiver and communicate the further protocol. The coordination is usually done within seconds, and will abort to the fallback transaction after some time if the connection breaks.
     Fallback transaction
    In the very first request to the receiving server, the sender provides a finalized signed transaction which has only the inputs of the sender, like any other Bitcoin transaction. The inputs are only from the sender. The outputs are the address of the receiver, as well as the change address of the sender. For example here, Alice pays Bob 0.2 bitcoin.
    Alice input   1 bitcoin   -->   Bob output            0.2 bitcoin
+import{_ as r,r as a,o as c,c as l,a as e,d as n,w as i,b as t,e as d}from"./app.65e5b6fd.js";const h="/PayJoinSend.png",u="/PayJoinPreviewTransaction.png",p={},f=e("h1",{id:"payjoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#payjoin","aria-hidden":"true"},"#"),t(" PayJoin")],-1),b={class:"table-of-contents"},v=e("h2",{id:"sending-payjoin-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#sending-payjoin-step-by-step","aria-hidden":"true"},"#"),t(" Sending PayJoin step-by-step")],-1),m=e("li",null,[e("p",null,[t("Load a wallet and open the "),e("code",null,"Send"),t(" dialog.")])],-1),y={href:"https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki",target:"_blank",rel:"noopener noreferrer"},g=e("code",null,"pj=",-1),_=e("code",null,"To",-1),P=e("code",null,"Send",-1),w=e("code",null,"bitcoin:tb1q0382a3m2jzvyk5lkea5h5jcht88xa6l0jufgwx?amount=0.00010727&pj=https://payjoin.test.kukks.org/BTC/pj",-1),k=d('
    Send Bitcoin PayJoin transaction in Wasabi Wallet
    1. Click Continue.
    2. Enter the label.
    3. At Preview Transaction, verify that the information is correct.
    PayJoinPreviewTransaction
    1. Click Confirm, and type in the password.
    The success of a PayJoin transaction is not something that depends on Wasabi.
    It may happen that the transaction is broadcast with success, but that it is not a PayJoin. This can happen for several reasons including:
    • The receiver did not have any utxos to contribute towards a PayJoin.
    • Your wallet does not use the same address format as the receiver's.
    • The PayJoin server is not available.
     The goal of PayJoin
    PayJoin is a collaborative transaction between the sender and the receiver of a payment, for example the merchant and the customer. The goal of the protocol is to break the common input ownership heuristic, while making it difficult to fingerprint that the transaction is in fact a CoinJoin. Further, it reduces the transaction fees paid by the merchant due to consolidation of coins.
     Coordination
    The coordination of this coinjoin is done with the PayToEndPoint [P2EP] concept. The receiver is reachable over the internet, either over a Tor onion service or clearnet IP address. The link is included in a BIP21 Bitcoin URI, and is provided to the sender as the payment invoice. The sender uses this onion service or IP address to connect to the server of the receiver and communicate the further protocol. The coordination is usually done within seconds, and will abort to the fallback transaction after some time if the connection breaks.
     Fallback transaction
    In the very first request to the receiving server, the sender provides a finalized signed transaction which has only the inputs of the sender, like any other Bitcoin transaction. The inputs are only from the sender. The outputs are the address of the receiver, as well as the change address of the sender. For example here, Alice pays Bob 0.2 bitcoin.
    Alice input   1 bitcoin   -->   Bob output            0.2 bitcoin
                                 Alice change output   0.8 bitcoin
 
    Both the sender and the receiver could broadcast this transaction.
     PayJoin transaction
    The receiving server responds to this initial proposal, with a transaction that adds more inputs to the transaction. Thus, the output belonging to the receiver increases in value, above the value that the payment amount is due.
    Alice input   1 bitcoin   -->   Bob output            0.7 bitcoin
 Bob input     0.5 bitcoin -->   Alice change output   0.8 bitcoin
diff --git a/assets/RPC.html.3799b39e.js b/assets/RPC.html.faf890c8.js
similarity index 99%
rename from assets/RPC.html.3799b39e.js
rename to assets/RPC.html.faf890c8.js
index 8acdf7433b..399231de61 100644
--- a/assets/RPC.html.3799b39e.js
+++ b/assets/RPC.html.faf890c8.js
@@ -1,4 +1,4 @@
-import{_ as l,r as u,o as i,c,a as s,d as a,w as e,b as n,e as p}from"./app.a5b7c2b2.js";const r={},d=s("h1",{id:"wasabi-remote-procedure-call-interface",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#wasabi-remote-procedure-call-interface","aria-hidden":"true"},"#"),n(" Wasabi Remote Procedure Call Interface")],-1),q=s("p",null,"Wasabi Wallet provides an RPC interface to interact with the wallet programmatically. The RPC server is listening by default on port 37128.",-1),k={class:"table-of-contents"},v=s("h2",{id:"limitations",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#limitations","aria-hidden":"true"},"#"),n(" Limitations")],-1),b={href:"https://github.com/dotnet/corefx/issues/14691",target:"_blank",rel:"noopener noreferrer"},m=s("code",null,"wcli",-1),h={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/Contrib/CLI",target:"_blank",rel:"noopener noreferrer"},g=p(`
     Configure RPC
    The RPC server has to be configured and enabled. This is done in the Config.json file and the relevant settings are:
    JsonRpcServerEnabled: [true | false] (default: false)
+import{_ as l,r as u,o as i,c,a as s,d as a,w as e,b as n,e as p}from"./app.65e5b6fd.js";const r={},d=s("h1",{id:"wasabi-remote-procedure-call-interface",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#wasabi-remote-procedure-call-interface","aria-hidden":"true"},"#"),n(" Wasabi Remote Procedure Call Interface")],-1),q=s("p",null,"Wasabi Wallet provides an RPC interface to interact with the wallet programmatically. The RPC server is listening by default on port 37128.",-1),k={class:"table-of-contents"},v=s("h2",{id:"limitations",tabindex:"-1"},[s("a",{class:"header-anchor",href:"#limitations","aria-hidden":"true"},"#"),n(" Limitations")],-1),b={href:"https://github.com/dotnet/corefx/issues/14691",target:"_blank",rel:"noopener noreferrer"},m=s("code",null,"wcli",-1),h={href:"https://github.com/zkSNACKs/WalletWasabi/tree/master/Contrib/CLI",target:"_blank",rel:"noopener noreferrer"},g=p(`
     Configure RPC
    The RPC server has to be configured and enabled. This is done in the Config.json file and the relevant settings are:
    JsonRpcServerEnabled: [true | false] (default: false)
 JsonRpcServerPrefixes: [an array of string with prefixes]
 	(default: [	"http://127.0.0.1:37128/", "http://localhost:37128/"])
 
    The RPC server can be configured to allow Anonymous access or Basic authentication just by editing:
    JsonRpcUser: [username] (default: empty)
diff --git a/assets/Receive.html.6bc14701.js b/assets/Receive.html.c7e036b6.js
similarity index 99%
rename from assets/Receive.html.6bc14701.js
rename to assets/Receive.html.c7e036b6.js
index 4f2fc260e1..48eb0d6ec7 100644
--- a/assets/Receive.html.6bc14701.js
+++ b/assets/Receive.html.c7e036b6.js
@@ -1,4 +1,4 @@
-import{_ as d}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as c,a as h}from"./AddressAwaitingPayment.1f3f0347.js";import{_ as u,r,o as p,c as b,a as e,d as a,w as i,b as t,e as l}from"./app.a5b7c2b2.js";const y={},m=e("h1",{id:"receive-bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receive-bitcoin","aria-hidden":"true"},"#"),t(" Receive bitcoin")],-1),w={class:"table-of-contents"},f={href:"https://youtu.be/Wjc00GBn-OQ",title:"Receive bitcoin in Wasabi Wallet",target:"_blank",rel:"noopener noreferrer"},g=e("img",{src:d,alt:"Receive bitcoin in Wasabi Wallet"},null,-1),v=l('
     Generating addresses step-by-step
    1. Start Wasabi and open the wallet that you want to receive coins into.
    2. Click the Receive button in the main view's top right corner.
    3. Type in the name of the entities who know that this address is yours. If you have already used a label before, simply choose it from the suggested labels.
    Receive label in Wasabi
    1. Press Continue and the wallet will generate a new address.
    Bitcoin address in Wasabi
     Bitcoin public keys and addresses
    ',6),k={href:"https://en.wikipedia.org/wiki/Public-key_cryptography",target:"_blank",rel:"noopener noreferrer"},_={href:"https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm",target:"_blank",rel:"noopener noreferrer"},x={href:"https://en.wikipedia.org/wiki/Cryptographic_hash_function",target:"_blank",rel:"noopener noreferrer"},C=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,'Wasabi Wallet does not "store your money", rather it stores your public keys and an encrypted secret that requires your password to derive the private keys. It creates addresses for receiving bitcoin, and it signs transactions that spend your bitcoin.')],-1),T=e("h2",{id:"the-problem-with-address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-problem-with-address-reuse","aria-hidden":"true"},"#"),t(" The problem with address reuse")],-1),W=l('
    TIP
    This is why Wasabi removes the address from the Addresses Awaiting Payment list as soon as it has received a coin.
     The importance of labeling
    Satoshis are the base unit currency of the Bitcoin network and are truly fungible, meaning that any 100 000 000 satoshis are always equal to 1 bitcoin. Just like with gold atoms, it doesn't matter which specific gold atoms you have, as long as it's gold, it's gold. However, an unspent transaction output, a bitcoin, is a chunk of money and is not fungible, because it has a different amount of satoshis in it, a different public key locking it up, a unique transaction history, and a unique index number. This is just like a gold coin, with a unique amount of gold atoms, and either a pretty mintage or an old chipped broken coin. Because UTXOs are not fungible, it is very important to know exactly which coin is which, and that is done by carefully labeling.
    For example, if I create a new address to receive a 0.5 BTC payment from Andrew for a laptop that I sold to him then the label has to be: Andrew.
    The label is not for describing the reason for payment, but rather to list those who know that this address is yours. Understanding this difference between labeling an address and describing a transaction is very important for your privacy.
    TIP
    In Wasabi it is mandatory to give every receive address a label of those who know that this address is yours, so that later you know what to do with it, and it also helps the auto coin selection algorithm when sending.
     Clusters
    Following the previous example, if I have to send a fraction (0.1 BTC) of the previously received coin to Charlie then in the Send tab the observers should be: Charlie. In that way, the change (0.4 BTC) will be known by Andrew and Charlie because they both will be able to follow the change. That's exactly what Wasabi displays in the coins list (cluster column), Wasabi tells us who are the ones that know about each of our coins in order to allow us to decide what to do with the coins.
    Let's take a look at another example: Imagine you have three coins, one known by Alice, one known by a KYC exchange and finally one known by Charlie. Imagine you need to sell a few sats to Charlie, which coin/s should you send? The obvious selection is the one already known by Charlie because by doing that he cannot learn anything new about our wallet, moreover, neither Alice nor the KYC exchange can learn anything new! But what if the coin is not big enough and we need to use more than one coin? You can use the one known by Alice or the one known by the KYC exchange, but are you okay with Charlie knowing about your deposit/withdrawal from the exchange? Are you okay with Alice knowing about your deal with Charlie? In case none of those combinations are acceptable for you then you should CoinJoin your coins.
     Coinjoined coins
    ',10),I=l(`
     Final words about labels and examples
    4 coins with good labels:
    Andrew
+import{_ as d}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as c,a as h}from"./AddressAwaitingPayment.1f3f0347.js";import{_ as u,r,o as p,c as b,a as e,d as a,w as i,b as t,e as l}from"./app.65e5b6fd.js";const y={},m=e("h1",{id:"receive-bitcoin",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receive-bitcoin","aria-hidden":"true"},"#"),t(" Receive bitcoin")],-1),w={class:"table-of-contents"},f={href:"https://youtu.be/Wjc00GBn-OQ",title:"Receive bitcoin in Wasabi Wallet",target:"_blank",rel:"noopener noreferrer"},g=e("img",{src:d,alt:"Receive bitcoin in Wasabi Wallet"},null,-1),v=l('
     Generating addresses step-by-step
    1. Start Wasabi and open the wallet that you want to receive coins into.
    2. Click the Receive button in the main view's top right corner.
    3. Type in the name of the entities who know that this address is yours. If you have already used a label before, simply choose it from the suggested labels.
    Receive label in Wasabi
    1. Press Continue and the wallet will generate a new address.
    Bitcoin address in Wasabi
     Bitcoin public keys and addresses
    ',6),k={href:"https://en.wikipedia.org/wiki/Public-key_cryptography",target:"_blank",rel:"noopener noreferrer"},_={href:"https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm",target:"_blank",rel:"noopener noreferrer"},x={href:"https://en.wikipedia.org/wiki/Cryptographic_hash_function",target:"_blank",rel:"noopener noreferrer"},C=e("div",{class:"custom-container tip"},[e("p",{class:"custom-container-title"},"TIP"),e("p",null,'Wasabi Wallet does not "store your money", rather it stores your public keys and an encrypted secret that requires your password to derive the private keys. It creates addresses for receiving bitcoin, and it signs transactions that spend your bitcoin.')],-1),T=e("h2",{id:"the-problem-with-address-reuse",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#the-problem-with-address-reuse","aria-hidden":"true"},"#"),t(" The problem with address reuse")],-1),W=l('
    TIP
    This is why Wasabi removes the address from the Addresses Awaiting Payment list as soon as it has received a coin.
     The importance of labeling
    Satoshis are the base unit currency of the Bitcoin network and are truly fungible, meaning that any 100 000 000 satoshis are always equal to 1 bitcoin. Just like with gold atoms, it doesn't matter which specific gold atoms you have, as long as it's gold, it's gold. However, an unspent transaction output, a bitcoin, is a chunk of money and is not fungible, because it has a different amount of satoshis in it, a different public key locking it up, a unique transaction history, and a unique index number. This is just like a gold coin, with a unique amount of gold atoms, and either a pretty mintage or an old chipped broken coin. Because UTXOs are not fungible, it is very important to know exactly which coin is which, and that is done by carefully labeling.
    For example, if I create a new address to receive a 0.5 BTC payment from Andrew for a laptop that I sold to him then the label has to be: Andrew.
    The label is not for describing the reason for payment, but rather to list those who know that this address is yours. Understanding this difference between labeling an address and describing a transaction is very important for your privacy.
    TIP
    In Wasabi it is mandatory to give every receive address a label of those who know that this address is yours, so that later you know what to do with it, and it also helps the auto coin selection algorithm when sending.
     Clusters
    Following the previous example, if I have to send a fraction (0.1 BTC) of the previously received coin to Charlie then in the Send tab the observers should be: Charlie. In that way, the change (0.4 BTC) will be known by Andrew and Charlie because they both will be able to follow the change. That's exactly what Wasabi displays in the coins list (cluster column), Wasabi tells us who are the ones that know about each of our coins in order to allow us to decide what to do with the coins.
    Let's take a look at another example: Imagine you have three coins, one known by Alice, one known by a KYC exchange and finally one known by Charlie. Imagine you need to sell a few sats to Charlie, which coin/s should you send? The obvious selection is the one already known by Charlie because by doing that he cannot learn anything new about our wallet, moreover, neither Alice nor the KYC exchange can learn anything new! But what if the coin is not big enough and we need to use more than one coin? You can use the one known by Alice or the one known by the KYC exchange, but are you okay with Charlie knowing about your deposit/withdrawal from the exchange? Are you okay with Alice knowing about your deal with Charlie? In case none of those combinations are acceptable for you then you should CoinJoin your coins.
     Coinjoined coins
    ',10),I=l(`
     Final words about labels and examples
    4 coins with good labels:
    Andrew
 David, Me
 Carlos, Sofia
 KYC exchange
diff --git a/assets/RestoreElectrum.html.0073b508.js b/assets/RestoreElectrum.html.2bddc161.js
similarity index 98%
rename from assets/RestoreElectrum.html.0073b508.js
rename to assets/RestoreElectrum.html.2bddc161.js
index 680e6454d3..ec68cc1038 100644
--- a/assets/RestoreElectrum.html.0073b508.js
+++ b/assets/RestoreElectrum.html.2bddc161.js
@@ -1,4 +1,4 @@
-import{_ as s,r,o as l,c as i,a as e,b as t,d as o,w as c,e as d}from"./app.a5b7c2b2.js";const u={},h=e("h1",{id:"restoring-wasabi-wallet-in-electrum",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#restoring-wasabi-wallet-in-electrum","aria-hidden":"true"},"#"),t(" Restoring Wasabi Wallet in Electrum")],-1),p={class:"custom-container danger"},m=e("p",{class:"custom-container-title"},"Potential privacy leak!",-1),_=e("p",null,"If you do not run your own Electrum server, you will leak all your addresses to random third-party servers, losing anonymity against those entities, so you must make a judgement call by being aware of this.",-1),g={href:"https://github.com/chris-belcher/electrum-personal-server",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/kyuupichan/electrumx",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/romanz/electrs",target:"_blank",rel:"noopener noreferrer"},b={class:"custom-container warning"},y=e("p",{class:"custom-container-title"},"Electrum does currently not support Taproot",-1),f={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.3",target:"_blank",rel:"noopener noreferrer"},E={class:"table-of-contents"},k=d(`
     Restoring Wasabi Wallet via Electrum GUI
    1. Launch Electrum.
      If you don't have a wallet created on Electrum it should automatically display an Install Wizard. If it opens your default wallet then go to File -> New/Restore.
    2. Name your new Electrum wallet.
    3. Choose Standard wallet.
    4. Choose I already have a seed.
    5. Type in your seed (recovery words).
    6. Click the Options button, then select BIP39 seed and if you created your Wasabi wallet with a password make sure to check Extend this seed with custom words and type your password in the Seed extension window.
    7. On the Script type and Derivation path window, choose native SegWit (p2wpkh) or manually insert m/84'/0'/0'.
    8. Increase the gap limit by opening Electrum's Console and execute the following commands:
      wallet.change_gap_limit(100)
+import{_ as s,r,o as l,c as i,a as e,b as t,d as o,w as c,e as d}from"./app.65e5b6fd.js";const u={},h=e("h1",{id:"restoring-wasabi-wallet-in-electrum",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#restoring-wasabi-wallet-in-electrum","aria-hidden":"true"},"#"),t(" Restoring Wasabi Wallet in Electrum")],-1),p={class:"custom-container danger"},m=e("p",{class:"custom-container-title"},"Potential privacy leak!",-1),_=e("p",null,"If you do not run your own Electrum server, you will leak all your addresses to random third-party servers, losing anonymity against those entities, so you must make a judgement call by being aware of this.",-1),g={href:"https://github.com/chris-belcher/electrum-personal-server",target:"_blank",rel:"noopener noreferrer"},w={href:"https://github.com/kyuupichan/electrumx",target:"_blank",rel:"noopener noreferrer"},v={href:"https://github.com/romanz/electrs",target:"_blank",rel:"noopener noreferrer"},b={class:"custom-container warning"},y=e("p",{class:"custom-container-title"},"Electrum does currently not support Taproot",-1),f={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.3",target:"_blank",rel:"noopener noreferrer"},E={class:"table-of-contents"},k=d(`
       Restoring Wasabi Wallet via Electrum GUI
      1. Launch Electrum.
        If you don't have a wallet created on Electrum it should automatically display an Install Wizard. If it opens your default wallet then go to File -> New/Restore.
      2. Name your new Electrum wallet.
      3. Choose Standard wallet.
      4. Choose I already have a seed.
      5. Type in your seed (recovery words).
      6. Click the Options button, then select BIP39 seed and if you created your Wasabi wallet with a password make sure to check Extend this seed with custom words and type your password in the Seed extension window.
      7. On the Script type and Derivation path window, choose native SegWit (p2wpkh) or manually insert m/84'/0'/0'.
      8. Increase the gap limit by opening Electrum's Console and execute the following commands:
        wallet.change_gap_limit(100)
 wallet.gap_limit_for_change = 100
 wallet.synchronize()
 
      `,2);function x(W,I){const a=r("ExternalLinkIcon"),n=r("router-link");return l(),i("div",null,[h,e("div",p,[m,_,e("p",null,[t("To gain some privacy by using Electrum you should set up Tor on Network preferences or by installing your own Electrum server via "),e("a",g,[t("Electrum Personal Server"),o(a)]),t(", "),e("a",w,[t("ElectrumX"),o(a)]),t(" or "),e("a",v,[t("Electrs"),o(a)]),t(".")])]),e("div",b,[y,e("p",null,[t("As of Wasabi "),e("a",f,[t("version 2.0.3"),o(a)]),t(", users may receive Taproot outputs from coinjoin or as a change output from a normal transaction. So when recovering a wallet from Wasabi in Electrum some funds might be missing, as the Taproot (SegWit v1) coins are not shown. An other wallet that does support Taproot should be used for recovering Taproot coins.")])]),e("nav",E,[e("ul",null,[e("li",null,[o(n,{to:"#restoring-wasabi-wallet-via-electrum-gui"},{default:c(()=>[t("Restoring Wasabi Wallet via Electrum GUI")]),_:1})])])]),k])}const T=s(u,[["render",x],["__file","RestoreElectrum.html.vue"]]);export{T as default};
diff --git a/assets/Security.html.83f2992c.js b/assets/Security.html.ea918cc8.js
similarity index 99%
rename from assets/Security.html.83f2992c.js
rename to assets/Security.html.ea918cc8.js
index 1049ddd67c..bfd871092d 100644
--- a/assets/Security.html.83f2992c.js
+++ b/assets/Security.html.ea918cc8.js
@@ -1,4 +1,4 @@
-import{_ as i,o as n,c as e,e as l}from"./app.a5b7c2b2.js";const d={},s=l(`
       Security Policy
      Feel free to report a vulnerability as a GitHub issue only if the vulnerability you found does not compromise users' privacy or security.
      If it does, then pay great care to responsible disclosure. Send an email to adam.ficsor73@gmail.com, preferably using PGP encryption: 21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E
      -----BEGIN PGP PUBLIC KEY BLOCK-----
+import{_ as i,o as n,c as e,e as l}from"./app.65e5b6fd.js";const d={},s=l(`
       Security Policy
      Feel free to report a vulnerability as a GitHub issue only if the vulnerability you found does not compromise users' privacy or security.
      If it does, then pay great care to responsible disclosure. Send an email to adam.ficsor73@gmail.com, preferably using PGP encryption: 21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E
      -----BEGIN PGP PUBLIC KEY BLOCK-----
 
 mQENBFVmnHQBCADH/ysozaiq7zLs2hXaCy7zyVHqMlm4z94yIxZAdklSk6dHDhcB
 IZSMnAQhISStBxioe8u+CXnviSBfRVHsiSiGYQ9OrDA/8Hod3pi/BWANLuUmkkTF
diff --git a/assets/Send.html.2b25f94b.js b/assets/Send.html.846a53f0.js
similarity index 99%
rename from assets/Send.html.2b25f94b.js
rename to assets/Send.html.846a53f0.js
index f9b868ba3a..bbb1cc613a 100644
--- a/assets/Send.html.2b25f94b.js
+++ b/assets/Send.html.846a53f0.js
@@ -1 +1 @@
-import{_ as h}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,c as u,a as p,b as c}from"./HistoryRightClick.a729d6cb.js";import{_ as m}from"./CoinjoinStrategy.5455b7fb.js";import{_ as f,r,o as b,c as g,a as e,d as i,w as n,b as t,e as l}from"./app.a5b7c2b2.js";const y="/SendButton.png",_="/Send.png",w="/SendRecipientLabel.png",v="/SendChangeFee.png",k="/SendPrivacySuggestion.png",W="/SendPreviewTransaction.png",S="/SendPassword.png",T="/PaymentSuccessful.png",x={},C=e("h1",{id:"send",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#send","aria-hidden":"true"},"#"),t(" Send")],-1),A={class:"table-of-contents"},P={href:"https://youtu.be/vCI5aza-lv0",title:"Send in Wasabi Wallet",target:"_blank",rel:"noopener noreferrer"},F=e("img",{src:h,alt:"Send in Wasabi Wallet"},null,-1),B=l('
       How to send bitcoin step-by-step
      1. Click the Send button.
      Wasabi Wallet Send Button
      1. Enter the destination address.
      Wasabi Wallet Send To Field
      1. Specify the amount of bitcoin to send to the destination address. Optionally, you can specify the dollar amount to send instead.
      Wasabi Wallet Send Amount Field
      1. Click Continue.
      Wasabi Wallet Send
      1. Label the recipient by entering the name of the person or company who you are sending to.
      Wasabi Wallet Send Recipient Label
      1. Preview Transaction.
        • Verify the amount, recipient, and the address.
        • Review the estimated time for confirmation and the transaction fee. Optionally, you can change the transaction fee or confirmation time by clicking on the edit fee icon.
        Wasabi Wallet Send Change Fee
        • Review the suggestions to improve your privacy by clicking the shield icon in the top right corner. For example, you may want to slightly increase or decrease your payment amount to avoid change.
        Wasabi Wallet Send Privacy Suggestion
      2. Click Confirm.
      Wasabi Wallet Send Preview Transaction
      1. Type in your password, then click Continue.
      Wasabi Wallet Send Password
      1. Transaction successfully sent!
      Wasabi Wallet Payment Successful
       Coins
      ',18),R=e("code",null,"Send",-1),I=e("h2",{id:"clusters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#clusters","aria-hidden":"true"},"#"),t(" Clusters")],-1),U=e("code",null,"Alice",-1),j=e("code",null,"Alice, Bob",-1),z=e("h2",{id:"anonymity-set",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-set","aria-hidden":"true"},"#"),t(" Anonymity Set")],-1),O=e("p",null,[t("A typical bitcoin transaction will contain one input and two outputs - one of the outputs is the coin you are sending and the other output is the change coin that goes back to your wallet. Your change coin can be linked to this one input. There is a 1 in 1 chance to find this link and no plausible deniability. Thus, Wasabi denotes this coin's anonymity set as "),e("code",null,"1"),t(".")],-1),E=e("p",null,[t("There are three coinjoin strategies to choose from in Wasabi Wallet which effect the target anonymity score for your coins. These three strategies are "),e("code",null,"Minimize Cost"),t(", "),e("code",null,"Maximize Speed"),t(", and "),e("code",null,"Maximize Privacy"),t(". Each of these strategies come with different trade-offs.")],-1),L=e("p",null,"Alternatively, custom coinjoin settings can be configured.",-1),N=e("p",null,[e("img",{src:m,alt:"Coinjoin Strategy",title:"Coinjoin Strategy"})],-1),H=e("h2",{id:"receiving-address",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receiving-address","aria-hidden":"true"},"#"),t(" Receiving Address")],-1),M=e("code",null,"1",-1),q=e("code",null,"3",-1),G=e("code",null,"bc1q",-1),V=e("code",null,"bc1p",-1),K=e("h2",{id:"observers",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#observers","aria-hidden":"true"},"#"),t(" Observers")],-1),Y=l('
       Amount
      In the Amount text box you can specify how many bitcoins the receiving address will gain. You can also see and enter the current US Dollar value of the sending amount.
      Avoid sending rounded values
      If you specify a rounded amount, like 0.0100 0000 bitcoin, then the change output will not be rounded, like 0.0896 8413 bitcoin. This makes it easy for an observer to conclude that the spending amount was the 0.01 bitcoin, and that the other output is the change back to the sender. So in order to increase your privacy, you can set a non-rounded amount, like 0.0101 6843.
      Send Amount Field
       Mining Fee
      ',5),X=e("code",null,"value of inputs - value of outputs",-1),Q=e("code",null,"smart fee",-1),D=e("p",null,[e("img",{src:d,alt:"Wasabi Wallet Fee Slider",title:"Wasabi Wallet Fee Slider"})],-1),J=e("p",null,[t("In some cases, there is very little demand for block space, and then Wasabi will set the minimum fee of "),e("code",null,"1 sat/vByte"),t(".")],-1),$={class:"custom-container tip"},Z=e("p",{class:"custom-container-title"},"High-priority transaction fees",-1),ee=e("p",null,"If you have a transaction that is high-priority and you really want it to be confirmed ASAP:",-1),te={href:"https://mempool.space",target:"_blank",rel:"noopener noreferrer"},ie={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/",target:"_blank",rel:"noopener noreferrer"},ne=e("li",null,"Select a fee that is well above the current highest fee (perhaps double or triple it) if it is very important to you that the transaction is confirmed soon.",-1),oe={href:"https://bitcointechtalk.com/an-introduction-to-bitcoin-core-fee-estimation-27920880ad0",target:"_blank",rel:"noopener noreferrer"},ae=e("h2",{id:"privacy-suggestions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-suggestions","aria-hidden":"true"},"#"),t(" Privacy Suggestions")],-1),se={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},re=e("em",null,"Preview Transaction",-1),le=l('
      There are warnings for:
      • Interlinking labels
      • Using non-private coins
      • Using semi-private coins
      • Creating change
      • Consolidating 10 coins or more
      • Using unconfirmed coins
      • Using coinjoining coins
      There are clickable suggestions to:
      • Manage labels (when interlinking labels)
      • Only use private coins
      • Not use non-private coins (only use private and semi-private)
      • Avoid change
      The suggestion to only use semi-private or private coins is only shown if the amount difference is less than or equal to 25%.
      TIP
      Each suggestion has a tooltip. Hover over the suggestion to see more information.
       Password
      ',7),ce=e("h2",{id:"broadcast",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#broadcast","aria-hidden":"true"},"#"),t(" Broadcast")],-1),he=e("p",null,"Once the transaction is signed, Wasabi will connect to a random Bitcoin P2P node over Tor and provide this transaction, then it will immediately disconnect. This first node will gossip the transaction throughout the network, then miners can include it in a block.",-1),de=e("h2",{id:"speed-up-or-cancel-transaction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#speed-up-or-cancel-transaction","aria-hidden":"true"},"#"),t(" Speed Up or Cancel Transaction")],-1),ue=e("p",null,'Pending (unconfirmed) Bitcoin transactions can be replaced by sending a new transaction that pays a higher fee rate using the same (or some) coins/UTXOs. This can be used to speed up or cancel a transaction. The miners are incentivized to mine the transaction with the higher fee rate, as this will earn them more money. If the new higher fee rate paying transaction is confirmed, the old transaction can be considered "replaced".',-1),pe={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},me=e("em",null,"Cancel Transaction",-1),fe=e("p",null,"Speeding up or cancelling a transaction costs additional fees, because a new bitcoin transaction with a higher fee rate (than the previous transaction) has to be sent.",-1),be=e("p",null,"To Speed Up or Cancel a Transaction, right-click on the pending transaction in the history.",-1),ge=e("p",null,[e("img",{src:u,alt:"History Right Click",title:"History Right Click"})],-1),ye=e("p",null,"Click one of the two options and then confirm that you want to pay the additional fee for this action. After which the succesfully speed up/cancelled dialog is displayed.",-1),_e=e("p",null,"In the history, the transaction will now have a rocket (speeded up) or a cross (cancelled) icon. The transaction is still pending, but it should be confirmed sooner than the initial transaction.",-1),we={href:"https://youtu.be/55KURak5r58",target:"_blank",rel:"noopener noreferrer"},ve=e("img",{src:"https://img.youtube.com/vi/55KURak5r58/maxresdefault.jpg",alt:"How to speed up Bitcoin transaction"},null,-1);function ke(We,Se){const o=r("router-link"),s=r("ExternalLinkIcon"),a=r("RouterLink");return b(),g("div",null,[C,e("nav",A,[e("ul",null,[e("li",null,[i(o,{to:"#how-to-send-bitcoin-step-by-step"},{default:n(()=>[t("How to send bitcoin step-by-step")]),_:1})]),e("li",null,[i(o,{to:"#coins"},{default:n(()=>[t("Coins")]),_:1})]),e("li",null,[i(o,{to:"#clusters"},{default:n(()=>[t("Clusters")]),_:1})]),e("li",null,[i(o,{to:"#anonymity-set"},{default:n(()=>[t("Anonymity Set")]),_:1})]),e("li",null,[i(o,{to:"#receiving-address"},{default:n(()=>[t("Receiving Address")]),_:1})]),e("li",null,[i(o,{to:"#observers"},{default:n(()=>[t("Observers")]),_:1})]),e("li",null,[i(o,{to:"#amount"},{default:n(()=>[t("Amount")]),_:1})]),e("li",null,[i(o,{to:"#mining-fee"},{default:n(()=>[t("Mining Fee")]),_:1})]),e("li",null,[i(o,{to:"#privacy-suggestions"},{default:n(()=>[t("Privacy Suggestions")]),_:1})]),e("li",null,[i(o,{to:"#password"},{default:n(()=>[t("Password")]),_:1})]),e("li",null,[i(o,{to:"#broadcast"},{default:n(()=>[t("Broadcast")]),_:1})]),e("li",null,[i(o,{to:"#speed-up-or-cancel-transaction"},{default:n(()=>[t("Speed Up or Cancel Transaction")]),_:1})])])]),e("p",null,[e("a",P,[F,i(s)])]),B,e("p",null,[t("A coin is an unspent transaction output (UTXO): a chunk of bitcoin that can be sent in a future transaction. Unlike fiat currencies which have fixed denominations, each UTXO contains a variable amount of bitcoin. You can get coins by first "),i(a,{to:"/using-wasabi/Receive.html"},{default:n(()=>[t("receiving")]),_:1}),t(" them from someone else. When you want to send some bitcoin you simply enter the amount to send and the address after clicking the "),R,t(" button. Wasabi Wallet does the job of automatically selecting the appropriate combination of coins to include as inputs in the transaction.")]),I,e("p",null,[t("Every time you receive a payment, you first must "),i(a,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[t("label the observers")]),_:1}),t(" who know this address is yours. This transaction metadata is used to build a cluster of which people know about your coins. For example, if you receive a coin from Alice, then the cluster is "),U,t(". If you now send half of this coin to Bob, then the cluster of your change coin is "),j,t(". The goal is to know the observers who know about your coins and try to reduce their number for each coin.")]),z,O,e("p",null,[t("In a Wasabi "),i(a,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[t("coinjoin")]),_:1}),t(", many peers register coins in the input of the transaction, and in the output there are several equal value coins. For example, the output may contain 20 coins worth exactly 0.3 bitcoin. This means that when looking at one of these coinjoin outputs, there is a 1 in 20 chance to find the corresponding input: thus an anonymity set of 20. Therefore, the higher the anonymity set, the more your post-coinjoin coin is delinked from the pre-coinjoin history.")]),E,L,N,H,e("p",null,[t("When sending bitcoin, you need to know the destination address of the receiver. This commits to the spending condition that the receiver agrees to have for this coin. The address can be a public key hash [starting with "),M,t("], a script hash [starting with "),q,t("], a native SegWit bech32 public key hash [starting with "),G,t("], or a Taproot bech32m public key [starting with "),V,t("]. Make sure that you ask the receiver for a "),i(a,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[t("new address")]),_:1}),t(" for every payment to protect your privacy and theirs. Wasabi will calculate the checksum and notify you if the provided address is wrong.")]),K,e("p",null,[t("In Wasabi it is mandatory to provide one or more "),i(a,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[t("labels")]),_:1}),t(" each time you initiate a transfer of bitcoin. These labels should be the observers of the transaction. An observer of a sending transaction is, of course, the receiver, as well as any other third party that knows that you are the sender of this transaction. For example, you should include as a label the payment processor or the bitcoin exchange if you use their services. This metadata will be used to build an accurate cluster of observers who know about your coins.")]),Y,e("p",null,[t("Every transaction must specify a fee which incentives the miner to include it in a block, it is calculated by "),X,t(". The higher the fee per virtual byte (vByte) transaction size, the more likely miners are to confirm this transaction. Wasabi uses Bitcoin Core's "),Q,t(" algorithm to estimate the time it will take to confirm at the given fee level. You can change the fee by moving the slider, or by manually setting the "),i(a,{to:"/FAQ/FAQ-UseWasabi.html#how-do-i-set-custom-fee-rate"},{default:n(()=>[t("transaction fee rate")]),_:1}),t(".")]),D,J,e("div",$,[Z,ee,e("ol",null,[e("li",null,[t("Use "),e("a",te,[t("a mempool monitor"),i(s)]),t(" (available "),e("a",ie,[t("Tor onion website"),i(s)]),t(") to see what fees are likely to get a transaction to be confirmed in the next block.")]),ne]),e("p",null,[t("For a deeper dive into the fee estimation process, "),e("a",oe,[t("this article"),i(s)]),t(" is worth reading.")])]),ae,e("p",null,[t("Since Wasabi version "),e("a",se,[t("2.0.4"),i(s)]),t(" the "),re,t(" dialog contains privacy suggestions. The privacy suggestions help the user to improve their transaction. They are displayed when hovering over the triangle or shield in the top right corner. The suggestions are based on the current coin selection for this transaction. For example, the suggestions will warn the user when the transaction contains non-private coins.")]),le,e("p",null,[t("In order to spend a coin, the transaction must be signed by the private key corresponding to that coin. Wasabi stores a secret on the computer, encrypted with the password that you specified during the "),i(a,{to:"/using-wasabi/WalletGeneration.html#important-info-about-your-wallet-password"},{default:n(()=>[t("wallet generation")]),_:1}),t(". To spend a coin you need to type in the password, which decrypts the encrypted secret, and then derive the child private key that signs the transaction. Afterwards, the password is wiped from memory.")]),ce,he,e("p",null,[t("If for some reason the first broadcast fails, then if you have Wasabi connected to "),i(a,{to:"/using-wasabi/BitcoinFullNode.html"},{default:n(()=>[t("your own Bitcoin full node")]),_:1}),t(" this node will broadcast the transaction to the network. If this also fails, then the transaction is sent to the backend coordinator with a new Tor identity, who then broadcasts the transaction to the network.")]),de,ue,e("p",null,[t("Since Wasabi version "),e("a",pe,[t("2.0.4"),i(s)]),t(" it is possible to easily speed up or cancel a pending transaction. Speeding up and cancelling are similar to each other, the main difference being that a "),me,t(` will send the coins to a new address owned by the user/wallet (this is all done automatically). The transaction is then "cancelled" because the bitcoin (minus the fees) is returned to the user's wallet.`)]),fe,e("p",null,[t("Wasabi first tries to utilize "),i(a,{to:"/using-wasabi/glossary/Glossary-GeneralBitcoin.html#replace-by-fee-rbf"},{default:n(()=>[t("RBF")]),_:1}),t(", if that's not possible it tries to do "),i(a,{to:"/using-wasabi/glossary/Glossary-GeneralBitcoin.html#child-pays-for-parent-cpfp"},{default:n(()=>[t("CPFP")]),_:1}),t(".")]),be,ge,ye,_e,e("p",null,[e("a",we,[ve,i(s)])])])}const Pe=f(x,[["render",ke],["__file","Send.html.vue"]]);export{Pe as default};
+import{_ as h}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as d,c as u,a as p,b as c}from"./HistoryRightClick.a729d6cb.js";import{_ as m}from"./CoinjoinStrategy.5455b7fb.js";import{_ as f,r,o as b,c as g,a as e,d as i,w as n,b as t,e as l}from"./app.65e5b6fd.js";const y="/SendButton.png",_="/Send.png",w="/SendRecipientLabel.png",v="/SendChangeFee.png",k="/SendPrivacySuggestion.png",W="/SendPreviewTransaction.png",S="/SendPassword.png",T="/PaymentSuccessful.png",x={},C=e("h1",{id:"send",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#send","aria-hidden":"true"},"#"),t(" Send")],-1),A={class:"table-of-contents"},P={href:"https://youtu.be/vCI5aza-lv0",title:"Send in Wasabi Wallet",target:"_blank",rel:"noopener noreferrer"},F=e("img",{src:h,alt:"Send in Wasabi Wallet"},null,-1),B=l('
       How to send bitcoin step-by-step
      1. Click the Send button.
      Wasabi Wallet Send Button
      1. Enter the destination address.
      Wasabi Wallet Send To Field
      1. Specify the amount of bitcoin to send to the destination address. Optionally, you can specify the dollar amount to send instead.
      Wasabi Wallet Send Amount Field
      1. Click Continue.
      Wasabi Wallet Send
      1. Label the recipient by entering the name of the person or company who you are sending to.
      Wasabi Wallet Send Recipient Label
      1. Preview Transaction.
        • Verify the amount, recipient, and the address.
        • Review the estimated time for confirmation and the transaction fee. Optionally, you can change the transaction fee or confirmation time by clicking on the edit fee icon.
        Wasabi Wallet Send Change Fee
        • Review the suggestions to improve your privacy by clicking the shield icon in the top right corner. For example, you may want to slightly increase or decrease your payment amount to avoid change.
        Wasabi Wallet Send Privacy Suggestion
      2. Click Confirm.
      Wasabi Wallet Send Preview Transaction
      1. Type in your password, then click Continue.
      Wasabi Wallet Send Password
      1. Transaction successfully sent!
      Wasabi Wallet Payment Successful
       Coins
      ',18),R=e("code",null,"Send",-1),I=e("h2",{id:"clusters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#clusters","aria-hidden":"true"},"#"),t(" Clusters")],-1),U=e("code",null,"Alice",-1),j=e("code",null,"Alice, Bob",-1),z=e("h2",{id:"anonymity-set",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#anonymity-set","aria-hidden":"true"},"#"),t(" Anonymity Set")],-1),O=e("p",null,[t("A typical bitcoin transaction will contain one input and two outputs - one of the outputs is the coin you are sending and the other output is the change coin that goes back to your wallet. Your change coin can be linked to this one input. There is a 1 in 1 chance to find this link and no plausible deniability. Thus, Wasabi denotes this coin's anonymity set as "),e("code",null,"1"),t(".")],-1),E=e("p",null,[t("There are three coinjoin strategies to choose from in Wasabi Wallet which effect the target anonymity score for your coins. These three strategies are "),e("code",null,"Minimize Cost"),t(", "),e("code",null,"Maximize Speed"),t(", and "),e("code",null,"Maximize Privacy"),t(". Each of these strategies come with different trade-offs.")],-1),L=e("p",null,"Alternatively, custom coinjoin settings can be configured.",-1),N=e("p",null,[e("img",{src:m,alt:"Coinjoin Strategy",title:"Coinjoin Strategy"})],-1),H=e("h2",{id:"receiving-address",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#receiving-address","aria-hidden":"true"},"#"),t(" Receiving Address")],-1),M=e("code",null,"1",-1),q=e("code",null,"3",-1),G=e("code",null,"bc1q",-1),V=e("code",null,"bc1p",-1),K=e("h2",{id:"observers",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#observers","aria-hidden":"true"},"#"),t(" Observers")],-1),Y=l('
       Amount
      In the Amount text box you can specify how many bitcoins the receiving address will gain. You can also see and enter the current US Dollar value of the sending amount.
      Avoid sending rounded values
      If you specify a rounded amount, like 0.0100 0000 bitcoin, then the change output will not be rounded, like 0.0896 8413 bitcoin. This makes it easy for an observer to conclude that the spending amount was the 0.01 bitcoin, and that the other output is the change back to the sender. So in order to increase your privacy, you can set a non-rounded amount, like 0.0101 6843.
      Send Amount Field
       Mining Fee
      ',5),X=e("code",null,"value of inputs - value of outputs",-1),Q=e("code",null,"smart fee",-1),D=e("p",null,[e("img",{src:d,alt:"Wasabi Wallet Fee Slider",title:"Wasabi Wallet Fee Slider"})],-1),J=e("p",null,[t("In some cases, there is very little demand for block space, and then Wasabi will set the minimum fee of "),e("code",null,"1 sat/vByte"),t(".")],-1),$={class:"custom-container tip"},Z=e("p",{class:"custom-container-title"},"High-priority transaction fees",-1),ee=e("p",null,"If you have a transaction that is high-priority and you really want it to be confirmed ASAP:",-1),te={href:"https://mempool.space",target:"_blank",rel:"noopener noreferrer"},ie={href:"http://mempoolhqx4isw62xs7abwphsq7ldayuidyx2v2oethdhhj6mlo2r6ad.onion/",target:"_blank",rel:"noopener noreferrer"},ne=e("li",null,"Select a fee that is well above the current highest fee (perhaps double or triple it) if it is very important to you that the transaction is confirmed soon.",-1),oe={href:"https://bitcointechtalk.com/an-introduction-to-bitcoin-core-fee-estimation-27920880ad0",target:"_blank",rel:"noopener noreferrer"},ae=e("h2",{id:"privacy-suggestions",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-suggestions","aria-hidden":"true"},"#"),t(" Privacy Suggestions")],-1),se={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},re=e("em",null,"Preview Transaction",-1),le=l('
      There are warnings for:
      • Interlinking labels
      • Using non-private coins
      • Using semi-private coins
      • Creating change
      • Consolidating 10 coins or more
      • Using unconfirmed coins
      • Using coinjoining coins
      There are clickable suggestions to:
      • Manage labels (when interlinking labels)
      • Only use private coins
      • Not use non-private coins (only use private and semi-private)
      • Avoid change
      The suggestion to only use semi-private or private coins is only shown if the amount difference is less than or equal to 25%.
      TIP
      Each suggestion has a tooltip. Hover over the suggestion to see more information.
       Password
      ',7),ce=e("h2",{id:"broadcast",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#broadcast","aria-hidden":"true"},"#"),t(" Broadcast")],-1),he=e("p",null,"Once the transaction is signed, Wasabi will connect to a random Bitcoin P2P node over Tor and provide this transaction, then it will immediately disconnect. This first node will gossip the transaction throughout the network, then miners can include it in a block.",-1),de=e("h2",{id:"speed-up-or-cancel-transaction",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#speed-up-or-cancel-transaction","aria-hidden":"true"},"#"),t(" Speed Up or Cancel Transaction")],-1),ue=e("p",null,'Pending (unconfirmed) Bitcoin transactions can be replaced by sending a new transaction that pays a higher fee rate using the same (or some) coins/UTXOs. This can be used to speed up or cancel a transaction. The miners are incentivized to mine the transaction with the higher fee rate, as this will earn them more money. If the new higher fee rate paying transaction is confirmed, the old transaction can be considered "replaced".',-1),pe={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},me=e("em",null,"Cancel Transaction",-1),fe=e("p",null,"Speeding up or cancelling a transaction costs additional fees, because a new bitcoin transaction with a higher fee rate (than the previous transaction) has to be sent.",-1),be=e("p",null,"To Speed Up or Cancel a Transaction, right-click on the pending transaction in the history.",-1),ge=e("p",null,[e("img",{src:u,alt:"History Right Click",title:"History Right Click"})],-1),ye=e("p",null,"Click one of the two options and then confirm that you want to pay the additional fee for this action. After which the succesfully speed up/cancelled dialog is displayed.",-1),_e=e("p",null,"In the history, the transaction will now have a rocket (speeded up) or a cross (cancelled) icon. The transaction is still pending, but it should be confirmed sooner than the initial transaction.",-1),we={href:"https://youtu.be/55KURak5r58",target:"_blank",rel:"noopener noreferrer"},ve=e("img",{src:"https://img.youtube.com/vi/55KURak5r58/maxresdefault.jpg",alt:"How to speed up Bitcoin transaction"},null,-1);function ke(We,Se){const o=r("router-link"),s=r("ExternalLinkIcon"),a=r("RouterLink");return b(),g("div",null,[C,e("nav",A,[e("ul",null,[e("li",null,[i(o,{to:"#how-to-send-bitcoin-step-by-step"},{default:n(()=>[t("How to send bitcoin step-by-step")]),_:1})]),e("li",null,[i(o,{to:"#coins"},{default:n(()=>[t("Coins")]),_:1})]),e("li",null,[i(o,{to:"#clusters"},{default:n(()=>[t("Clusters")]),_:1})]),e("li",null,[i(o,{to:"#anonymity-set"},{default:n(()=>[t("Anonymity Set")]),_:1})]),e("li",null,[i(o,{to:"#receiving-address"},{default:n(()=>[t("Receiving Address")]),_:1})]),e("li",null,[i(o,{to:"#observers"},{default:n(()=>[t("Observers")]),_:1})]),e("li",null,[i(o,{to:"#amount"},{default:n(()=>[t("Amount")]),_:1})]),e("li",null,[i(o,{to:"#mining-fee"},{default:n(()=>[t("Mining Fee")]),_:1})]),e("li",null,[i(o,{to:"#privacy-suggestions"},{default:n(()=>[t("Privacy Suggestions")]),_:1})]),e("li",null,[i(o,{to:"#password"},{default:n(()=>[t("Password")]),_:1})]),e("li",null,[i(o,{to:"#broadcast"},{default:n(()=>[t("Broadcast")]),_:1})]),e("li",null,[i(o,{to:"#speed-up-or-cancel-transaction"},{default:n(()=>[t("Speed Up or Cancel Transaction")]),_:1})])])]),e("p",null,[e("a",P,[F,i(s)])]),B,e("p",null,[t("A coin is an unspent transaction output (UTXO): a chunk of bitcoin that can be sent in a future transaction. Unlike fiat currencies which have fixed denominations, each UTXO contains a variable amount of bitcoin. You can get coins by first "),i(a,{to:"/using-wasabi/Receive.html"},{default:n(()=>[t("receiving")]),_:1}),t(" them from someone else. When you want to send some bitcoin you simply enter the amount to send and the address after clicking the "),R,t(" button. Wasabi Wallet does the job of automatically selecting the appropriate combination of coins to include as inputs in the transaction.")]),I,e("p",null,[t("Every time you receive a payment, you first must "),i(a,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[t("label the observers")]),_:1}),t(" who know this address is yours. This transaction metadata is used to build a cluster of which people know about your coins. For example, if you receive a coin from Alice, then the cluster is "),U,t(". If you now send half of this coin to Bob, then the cluster of your change coin is "),j,t(". The goal is to know the observers who know about your coins and try to reduce their number for each coin.")]),z,O,e("p",null,[t("In a Wasabi "),i(a,{to:"/using-wasabi/CoinJoin.html"},{default:n(()=>[t("coinjoin")]),_:1}),t(", many peers register coins in the input of the transaction, and in the output there are several equal value coins. For example, the output may contain 20 coins worth exactly 0.3 bitcoin. This means that when looking at one of these coinjoin outputs, there is a 1 in 20 chance to find the corresponding input: thus an anonymity set of 20. Therefore, the higher the anonymity set, the more your post-coinjoin coin is delinked from the pre-coinjoin history.")]),E,L,N,H,e("p",null,[t("When sending bitcoin, you need to know the destination address of the receiver. This commits to the spending condition that the receiver agrees to have for this coin. The address can be a public key hash [starting with "),M,t("], a script hash [starting with "),q,t("], a native SegWit bech32 public key hash [starting with "),G,t("], or a Taproot bech32m public key [starting with "),V,t("]. Make sure that you ask the receiver for a "),i(a,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[t("new address")]),_:1}),t(" for every payment to protect your privacy and theirs. Wasabi will calculate the checksum and notify you if the provided address is wrong.")]),K,e("p",null,[t("In Wasabi it is mandatory to provide one or more "),i(a,{to:"/using-wasabi/Receive.html#the-importance-of-labeling"},{default:n(()=>[t("labels")]),_:1}),t(" each time you initiate a transfer of bitcoin. These labels should be the observers of the transaction. An observer of a sending transaction is, of course, the receiver, as well as any other third party that knows that you are the sender of this transaction. For example, you should include as a label the payment processor or the bitcoin exchange if you use their services. This metadata will be used to build an accurate cluster of observers who know about your coins.")]),Y,e("p",null,[t("Every transaction must specify a fee which incentives the miner to include it in a block, it is calculated by "),X,t(". The higher the fee per virtual byte (vByte) transaction size, the more likely miners are to confirm this transaction. Wasabi uses Bitcoin Core's "),Q,t(" algorithm to estimate the time it will take to confirm at the given fee level. You can change the fee by moving the slider, or by manually setting the "),i(a,{to:"/FAQ/FAQ-UseWasabi.html#how-do-i-set-custom-fee-rate"},{default:n(()=>[t("transaction fee rate")]),_:1}),t(".")]),D,J,e("div",$,[Z,ee,e("ol",null,[e("li",null,[t("Use "),e("a",te,[t("a mempool monitor"),i(s)]),t(" (available "),e("a",ie,[t("Tor onion website"),i(s)]),t(") to see what fees are likely to get a transaction to be confirmed in the next block.")]),ne]),e("p",null,[t("For a deeper dive into the fee estimation process, "),e("a",oe,[t("this article"),i(s)]),t(" is worth reading.")])]),ae,e("p",null,[t("Since Wasabi version "),e("a",se,[t("2.0.4"),i(s)]),t(" the "),re,t(" dialog contains privacy suggestions. The privacy suggestions help the user to improve their transaction. They are displayed when hovering over the triangle or shield in the top right corner. The suggestions are based on the current coin selection for this transaction. For example, the suggestions will warn the user when the transaction contains non-private coins.")]),le,e("p",null,[t("In order to spend a coin, the transaction must be signed by the private key corresponding to that coin. Wasabi stores a secret on the computer, encrypted with the password that you specified during the "),i(a,{to:"/using-wasabi/WalletGeneration.html#important-info-about-your-wallet-password"},{default:n(()=>[t("wallet generation")]),_:1}),t(". To spend a coin you need to type in the password, which decrypts the encrypted secret, and then derive the child private key that signs the transaction. Afterwards, the password is wiped from memory.")]),ce,he,e("p",null,[t("If for some reason the first broadcast fails, then if you have Wasabi connected to "),i(a,{to:"/using-wasabi/BitcoinFullNode.html"},{default:n(()=>[t("your own Bitcoin full node")]),_:1}),t(" this node will broadcast the transaction to the network. If this also fails, then the transaction is sent to the backend coordinator with a new Tor identity, who then broadcasts the transaction to the network.")]),de,ue,e("p",null,[t("Since Wasabi version "),e("a",pe,[t("2.0.4"),i(s)]),t(" it is possible to easily speed up or cancel a pending transaction. Speeding up and cancelling are similar to each other, the main difference being that a "),me,t(` will send the coins to a new address owned by the user/wallet (this is all done automatically). The transaction is then "cancelled" because the bitcoin (minus the fees) is returned to the user's wallet.`)]),fe,e("p",null,[t("Wasabi first tries to utilize "),i(a,{to:"/using-wasabi/glossary/Glossary-GeneralBitcoin.html#replace-by-fee-rbf"},{default:n(()=>[t("RBF")]),_:1}),t(", if that's not possible it tries to do "),i(a,{to:"/using-wasabi/glossary/Glossary-GeneralBitcoin.html#child-pays-for-parent-cpfp"},{default:n(()=>[t("CPFP")]),_:1}),t(".")]),be,ge,ye,_e,e("p",null,[e("a",we,[ve,i(s)])])])}const Pe=f(x,[["render",ke],["__file","Send.html.vue"]]);export{Pe as default};
diff --git a/assets/Testnet.html.c098c41f.js b/assets/Testnet.html.8baf86af.js
similarity index 98%
rename from assets/Testnet.html.c098c41f.js
rename to assets/Testnet.html.8baf86af.js
index 0741966628..6ab8ed54d2 100644
--- a/assets/Testnet.html.c098c41f.js
+++ b/assets/Testnet.html.8baf86af.js
@@ -1 +1 @@
-import{_ as r,r as c,o as l,c as d,a as t,d as n,w as o,b as e,e as h}from"./app.a5b7c2b2.js";const u="/SettingsButton.png",_="/SettingsNetwork.png",b="/TestNetIndicator.png",f={},p=t("h1",{id:"testnet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#testnet","aria-hidden":"true"},"#"),e(" Testnet")],-1),g={class:"table-of-contents"},m=h('
       Bitcoin testnet
      The Bitcoin testnet is a network that behaves almost exactly the same as the Bitcoin mainnet. The major difference is that the bitcoin on the testnet do not have any economical value, they should not be used to buy or sell goods and services. This makes the network very useful for testing software and features, because there is no risk of losing precious "real" bitcoin from the main network.
      Don't loose your bitcoin
      When testing cutting edge software like Wasabi, use testnet to ensure that your mistakes don't cost you money!
       Activating testnet in Wasabi
      First, open your Wasabi Wallet and click the Settings button in the bottom left corner.
      Settings button
      Select the Bitcoin tab, click on the Network dropdown and select TestNet.
      Settings Network Dropdown
      Restart Wasabi to activate the change. After the restart, you should see the TestNet indicator in the top right corner of the wallet.
      Bitcoin testnet network activated in Wasabi Wallet
      ',10),w={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=t("p",null,"After the testing, set the settings back to mainnet, and close Wasabi. It will load on mainnet the next time you start it.",-1),k={class:"custom-container tip"},y=t("p",{class:"custom-container-title"},"TIP",-1),T=t("code",null,"Config.json",-1),W=t("code",null,'"Network":',-1),N=t("code",null,'"Main"',-1),x=t("code",null,'"TestNet"',-1),B=t("code",null,'"RegTest"',-1),S=t("h2",{id:"loading-a-wallet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#loading-a-wallet","aria-hidden":"true"},"#"),e(" Loading a wallet")],-1),j=t("p",null,"Wasabi differentiates between Mainnet and TestNet wallets. Meaning that a TestNet wallet will not show up when the Main network is active, and vice versa. You have to create a new wallet when you activate TestNet for the first time.",-1),R=t("h2",{id:"receiving-testnet-bitcoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#receiving-testnet-bitcoin","aria-hidden":"true"},"#"),e(" Receiving testnet bitcoin")],-1),A=t("code",null,"Receive",-1),C=t("code",null,"tb1q...",-1),I=t("code",null,"bc1q...",-1),L={href:"https://en.bitcoin.it/wiki/Testnet#Faucets",target:"_blank",rel:"noopener noreferrer"},F={href:"https://coinfaucet.eu/en/btc-testnet/",target:"_blank",rel:"noopener noreferrer"},q={href:"https://bitcoinfaucet.uo1.net/",target:"_blank",rel:"noopener noreferrer"},M=t("h2",{id:"coinjoin-on-testnet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#coinjoin-on-testnet","aria-hidden":"true"},"#"),e(" Coinjoin on testnet")],-1);function V(D,E){const i=c("router-link"),a=c("ExternalLinkIcon"),s=c("RouterLink");return l(),d("div",null,[p,t("nav",g,[t("ul",null,[t("li",null,[n(i,{to:"#bitcoin-testnet"},{default:o(()=>[e("Bitcoin testnet")]),_:1})]),t("li",null,[n(i,{to:"#activating-testnet-in-wasabi"},{default:o(()=>[e("Activating testnet in Wasabi")]),_:1})]),t("li",null,[n(i,{to:"#loading-a-wallet"},{default:o(()=>[e("Loading a wallet")]),_:1})]),t("li",null,[n(i,{to:"#receiving-testnet-bitcoin"},{default:o(()=>[e("Receiving testnet bitcoin")]),_:1})]),t("li",null,[n(i,{to:"#coinjoin-on-testnet"},{default:o(()=>[e("Coinjoin on testnet")]),_:1})])])]),m,t("p",null,[e("When Wasabi is started in testnet, it will fetch testnet "),t("a",w,[e("BIP 158 block filters"),n(a)]),e(" from the coordinator. For the first start, this may take a couple of minutes.")]),v,t("div",k,[y,t("p",null,[e("Alternatively, you can edit the "),T,e(" file in your "),n(s,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:o(()=>[e("Wasabi data folder")]),_:1}),e(". In the second line you can modify the value of "),W,e(", to "),N,e(", "),x,e(", or "),B,e(". The changes will apply on the next launch of Wasabi.")])]),S,j,R,t("p",null,[e("You can "),n(s,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("generate a receive address")]),_:1}),e(" the same way as on mainnet, by labeling the known by entities in the "),A,e(" dialog. Notice that testnet SegWit addresses start with "),C,e(", and not with "),I,e(" as mainnet addresses.")]),t("p",null,[e("Because testnet bitcoin don't have economical value, they are gifted by different sources. There are "),t("a",L,[e("faucets"),n(a)]),e(" like "),t("a",F,[e("this one"),n(a)]),e(" or "),t("a",q,[e("bitcoinfaucet.uo1.net"),n(a)]),e(" that give a certain amount of testnet bitcoin per time period. You may also ask other developers if they have a couple of spare testnet coins available.")]),M,t("p",null,[n(s,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("CoinJoin")]),_:1}),e(" on testnet is as easy as on mainnet. Usually there are other testers doing a coinjoin, but if you are the only one at the moment, then load two wallets and start coinjoining in both of them.")])])}const J=r(f,[["render",V],["__file","Testnet.html.vue"]]);export{J as default};
+import{_ as r,r as c,o as l,c as d,a as t,d as n,w as o,b as e,e as h}from"./app.65e5b6fd.js";const u="/SettingsButton.png",_="/SettingsNetwork.png",b="/TestNetIndicator.png",f={},p=t("h1",{id:"testnet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#testnet","aria-hidden":"true"},"#"),e(" Testnet")],-1),g={class:"table-of-contents"},m=h('
       Bitcoin testnet
      The Bitcoin testnet is a network that behaves almost exactly the same as the Bitcoin mainnet. The major difference is that the bitcoin on the testnet do not have any economical value, they should not be used to buy or sell goods and services. This makes the network very useful for testing software and features, because there is no risk of losing precious "real" bitcoin from the main network.
      Don't loose your bitcoin
      When testing cutting edge software like Wasabi, use testnet to ensure that your mistakes don't cost you money!
       Activating testnet in Wasabi
      First, open your Wasabi Wallet and click the Settings button in the bottom left corner.
      Settings button
      Select the Bitcoin tab, click on the Network dropdown and select TestNet.
      Settings Network Dropdown
      Restart Wasabi to activate the change. After the restart, you should see the TestNet indicator in the top right corner of the wallet.
      Bitcoin testnet network activated in Wasabi Wallet
      ',10),w={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=t("p",null,"After the testing, set the settings back to mainnet, and close Wasabi. It will load on mainnet the next time you start it.",-1),k={class:"custom-container tip"},y=t("p",{class:"custom-container-title"},"TIP",-1),T=t("code",null,"Config.json",-1),W=t("code",null,'"Network":',-1),N=t("code",null,'"Main"',-1),x=t("code",null,'"TestNet"',-1),B=t("code",null,'"RegTest"',-1),S=t("h2",{id:"loading-a-wallet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#loading-a-wallet","aria-hidden":"true"},"#"),e(" Loading a wallet")],-1),j=t("p",null,"Wasabi differentiates between Mainnet and TestNet wallets. Meaning that a TestNet wallet will not show up when the Main network is active, and vice versa. You have to create a new wallet when you activate TestNet for the first time.",-1),R=t("h2",{id:"receiving-testnet-bitcoin",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#receiving-testnet-bitcoin","aria-hidden":"true"},"#"),e(" Receiving testnet bitcoin")],-1),A=t("code",null,"Receive",-1),C=t("code",null,"tb1q...",-1),I=t("code",null,"bc1q...",-1),L={href:"https://en.bitcoin.it/wiki/Testnet#Faucets",target:"_blank",rel:"noopener noreferrer"},F={href:"https://coinfaucet.eu/en/btc-testnet/",target:"_blank",rel:"noopener noreferrer"},q={href:"https://bitcoinfaucet.uo1.net/",target:"_blank",rel:"noopener noreferrer"},M=t("h2",{id:"coinjoin-on-testnet",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#coinjoin-on-testnet","aria-hidden":"true"},"#"),e(" Coinjoin on testnet")],-1);function V(D,E){const i=c("router-link"),a=c("ExternalLinkIcon"),s=c("RouterLink");return l(),d("div",null,[p,t("nav",g,[t("ul",null,[t("li",null,[n(i,{to:"#bitcoin-testnet"},{default:o(()=>[e("Bitcoin testnet")]),_:1})]),t("li",null,[n(i,{to:"#activating-testnet-in-wasabi"},{default:o(()=>[e("Activating testnet in Wasabi")]),_:1})]),t("li",null,[n(i,{to:"#loading-a-wallet"},{default:o(()=>[e("Loading a wallet")]),_:1})]),t("li",null,[n(i,{to:"#receiving-testnet-bitcoin"},{default:o(()=>[e("Receiving testnet bitcoin")]),_:1})]),t("li",null,[n(i,{to:"#coinjoin-on-testnet"},{default:o(()=>[e("Coinjoin on testnet")]),_:1})])])]),m,t("p",null,[e("When Wasabi is started in testnet, it will fetch testnet "),t("a",w,[e("BIP 158 block filters"),n(a)]),e(" from the coordinator. For the first start, this may take a couple of minutes.")]),v,t("div",k,[y,t("p",null,[e("Alternatively, you can edit the "),T,e(" file in your "),n(s,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:o(()=>[e("Wasabi data folder")]),_:1}),e(". In the second line you can modify the value of "),W,e(", to "),N,e(", "),x,e(", or "),B,e(". The changes will apply on the next launch of Wasabi.")])]),S,j,R,t("p",null,[e("You can "),n(s,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("generate a receive address")]),_:1}),e(" the same way as on mainnet, by labeling the known by entities in the "),A,e(" dialog. Notice that testnet SegWit addresses start with "),C,e(", and not with "),I,e(" as mainnet addresses.")]),t("p",null,[e("Because testnet bitcoin don't have economical value, they are gifted by different sources. There are "),t("a",L,[e("faucets"),n(a)]),e(" like "),t("a",F,[e("this one"),n(a)]),e(" or "),t("a",q,[e("bitcoinfaucet.uo1.net"),n(a)]),e(" that give a certain amount of testnet bitcoin per time period. You may also ask other developers if they have a couple of spare testnet coins available.")]),M,t("p",null,[n(s,{to:"/using-wasabi/CoinJoin.html"},{default:o(()=>[e("CoinJoin")]),_:1}),e(" on testnet is as easy as on mainnet. Usually there are other testers doing a coinjoin, but if you are the only one at the moment, then load two wallets and start coinjoining in both of them.")])])}const J=r(f,[["render",V],["__file","Testnet.html.vue"]]);export{J as default};
diff --git a/assets/TransactionGraph.html.e4b715af.js b/assets/TransactionGraph.html.17dd6ae6.js
similarity index 97%
rename from assets/TransactionGraph.html.e4b715af.js
rename to assets/TransactionGraph.html.17dd6ae6.js
index 121a5fb39b..3f6e033e74 100644
--- a/assets/TransactionGraph.html.e4b715af.js
+++ b/assets/TransactionGraph.html.17dd6ae6.js
@@ -1 +1 @@
-import{_ as r,r as i,o as c,c as h,a as e,d as t,w as o,b as n,e as l}from"./app.a5b7c2b2.js";const d={},u=e("h1",{id:"transaction-graph",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-graph","aria-hidden":"true"},"#"),n(" Transaction Graph")],-1),b={class:"table-of-contents"},p=l('
       Problem
       Public transaction history
      Because of the input and output model of Bitcoin, there is a chain of digital signatures all the way from the coinbase reward to the current UTXO. This transaction history can reveal sensitive information about the spending patterns of individuals. The receiver of a coin can look back into the transaction history of the sender. And the sender can see the future spending of the receiver.
       Wasabi's Solution
       WabiSabi coinjoins
      ',5),f={href:"https://github.com/zkSNACKs/WabiSabi",target:"_blank",rel:"noopener noreferrer"},_=e("p",null,"This means that when sending an anonscore coin, the receiver does not know about the transaction history before the coinjoin. And when the receiver does a coinjoin himself, then the sender cannot spy on the later spending patterns. An outside observer can only guess the correct link at a rate of 1 in the anonscore, for example, 1-in-100, or 1%.",-1);function m(y,w){const a=i("router-link"),s=i("ExternalLinkIcon");return c(),h("div",null,[u,e("nav",b,[e("ul",null,[e("li",null,[t(a,{to:"#problem"},{default:o(()=>[n("Problem")]),_:1}),e("ul",null,[e("li",null,[t(a,{to:"#public-transaction-history"},{default:o(()=>[n("Public transaction history")]),_:1})])])]),e("li",null,[t(a,{to:"#wasabi-s-solution"},{default:o(()=>[n("Wasabi's Solution")]),_:1}),e("ul",null,[e("li",null,[t(a,{to:"#wabisabi-coinjoins"},{default:o(()=>[n("WabiSabi coinjoins")]),_:1})])])])])]),p,e("p",null,[n("In order to obfuscate the link between inputs and outputs, Wasabi uses the "),e("a",f,[n("WabiSabi"),t(s)]),n(" coinjoin protocol. The Wasabi central coordinator cannot steal and cannot spy, it simply helps many peers to build a huge transaction, with many inputs, and many outputs. The non-private inputs can be linked to their previous transaction history. However, the coinjoin outputs with an anonymity score cannot be tied to the inputs.")]),_])}const k=r(d,[["render",m],["__file","TransactionGraph.html.vue"]]);export{k as default};
+import{_ as r,r as i,o as c,c as h,a as e,d as t,w as o,b as n,e as l}from"./app.65e5b6fd.js";const d={},u=e("h1",{id:"transaction-graph",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-graph","aria-hidden":"true"},"#"),n(" Transaction Graph")],-1),b={class:"table-of-contents"},p=l('
       Problem
       Public transaction history
      Because of the input and output model of Bitcoin, there is a chain of digital signatures all the way from the coinbase reward to the current UTXO. This transaction history can reveal sensitive information about the spending patterns of individuals. The receiver of a coin can look back into the transaction history of the sender. And the sender can see the future spending of the receiver.
       Wasabi's Solution
       WabiSabi coinjoins
      ',5),f={href:"https://github.com/zkSNACKs/WabiSabi",target:"_blank",rel:"noopener noreferrer"},_=e("p",null,"This means that when sending an anonscore coin, the receiver does not know about the transaction history before the coinjoin. And when the receiver does a coinjoin himself, then the sender cannot spy on the later spending patterns. An outside observer can only guess the correct link at a rate of 1 in the anonscore, for example, 1-in-100, or 1%.",-1);function m(y,w){const a=i("router-link"),s=i("ExternalLinkIcon");return c(),h("div",null,[u,e("nav",b,[e("ul",null,[e("li",null,[t(a,{to:"#problem"},{default:o(()=>[n("Problem")]),_:1}),e("ul",null,[e("li",null,[t(a,{to:"#public-transaction-history"},{default:o(()=>[n("Public transaction history")]),_:1})])])]),e("li",null,[t(a,{to:"#wasabi-s-solution"},{default:o(()=>[n("Wasabi's Solution")]),_:1}),e("ul",null,[e("li",null,[t(a,{to:"#wabisabi-coinjoins"},{default:o(()=>[n("WabiSabi coinjoins")]),_:1})])])])])]),p,e("p",null,[n("In order to obfuscate the link between inputs and outputs, Wasabi uses the "),e("a",f,[n("WabiSabi"),t(s)]),n(" coinjoin protocol. The Wasabi central coordinator cannot steal and cannot spy, it simply helps many peers to build a huge transaction, with many inputs, and many outputs. The non-private inputs can be linked to their previous transaction history. However, the coinjoin outputs with an anonymity score cannot be tied to the inputs.")]),_])}const k=r(d,[["render",m],["__file","TransactionGraph.html.vue"]]);export{k as default};
diff --git a/assets/TransactionSurveillanceCompanies.html.f6da66b3.js b/assets/TransactionSurveillanceCompanies.html.39fabb04.js
similarity index 99%
rename from assets/TransactionSurveillanceCompanies.html.f6da66b3.js
rename to assets/TransactionSurveillanceCompanies.html.39fabb04.js
index ec4b553371..58c39b19b6 100644
--- a/assets/TransactionSurveillanceCompanies.html.f6da66b3.js
+++ b/assets/TransactionSurveillanceCompanies.html.39fabb04.js
@@ -1 +1 @@
-import{_ as c,r as s,o as h,c as d,a as e,d as t,w as i,b as n,e as l}from"./app.a5b7c2b2.js";const u={},p=e("h1",{id:"transaction-surveillance-companies",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-surveillance-companies","aria-hidden":"true"},"#"),n(" Transaction Surveillance Companies")],-1),y=e("p",null,"A transaction surveillance company is one that attempts to spy on bitcoin users. Their business model is usually to sell the data to any governments, corporations and individuals willing to pay for their services.",-1),m={class:"table-of-contents"},f=l('
       Spying technology
      There are a number of techniques probably used by transaction surveillance companies:
       AML/KYC information
      Many bitcoin exchanges require users to undergo Anti-Money Laundering (AML) and Know-Your-Customer (KYC) checks, which requires users to reveal all kinds of invasive personal information such as their real name, residence, occupation, net worth and income. All this information is usually passed onto the exchange's partner transaction surveillance company, which keeps a database linking the victim's personal information with their bitcoin addresses and transactions.
       Blockchain analysis
      ',5),b=e("h3",{id:"wallet-synchronization-analysis",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-synchronization-analysis","aria-hidden":"true"},"#"),n(" Wallet synchronization analysis")],-1),g={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=l('
       Transaction broadcasting
      Surveillance companies have been known to sybil and eclipse attack the bitcoin network, and specific nodes, in order to try to find the source IP addresses of unconfirmed transactions.
       Criticisms
       Attempt to invade privacy
      The right to privacy is recognized as a human right, for instance in the US constitution, European Union regulations and the Constitution of India.
      Financial privacy is an essential criteria for the efficient operation of a free market: if you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.
      Financial privacy is essential for personal safety: if thieves can see your income, holdings, and spending, they can use that information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your packages from your doorstep, or impersonate businesses you transact with. They also know exactly how much to try to scam you for.
      Financial privacy is essential for human dignity: no one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.
      Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.
      Globally visible public records in finance are completely unheard-of. They are undesirable and arguably intolerable. The Bitcoin whitepaper made a promise of how we could get around the visibility of the ledger with pseudonymous addresses, but the ecosystem has broken that promise in a bunch of places and we ought to fix it. Bitcoin could have coded your name or IP address into every transaction. It didn't. The whitepaper even has a section on privacy. Sufficient privacy is an essential prerequisite for a viable digital currency.
       Attempt to destroy fungibility
      ',11),w=l('
       No mechanism for oversight or appeal
      There appears to be no recourse for someone affected by false positive identification of exchange-disapproved transaction history. This could result in them wrongly having their coins confiscated.
       Jurisdiction
      Transaction surveillance company market themselves as a tool for finding "bad guys", but it's unclear which jurisdiction that applies to. For example, could one day the government of China pressure those companies into marking certain coins as "bad" because they belong to users who disagree with Chinese government policy?
       Incentivized to oppose bitcoin updates
      During the deployment of segregated witness, certain transaction surveillance companies were believed to have spread misinformation about it, because the update enables Lightning Network. The companies saw it as a threat to their business, since it can enable transacting with bitcoin more privately.
       Oversold effectiveness
      Transaction surveillance companies rely on heuristics or assumptions when analyzing the blockchain. These heuristics are sometimes not true, for example, the common-input-ownership heuristic is broken by CoinJoin. Even if that heuristic is true, it still requires actually identifying the cluster, which is not always possible.
      Laws surrounding anti-money-laundering typically require businesses to make reasonable efforts to investigate the source of funds. Usually, the transaction surveillance company's customers simply want to legally protect themselves, regardless of whether the surveillance actually works. There is a lot of money in this space from governments and other authorities, who usually don't understand the underlying technology and are happy to throw money at several startups who claim to be able to accurately track everything. Whether the activities of transaction surveillance companies actually help against money laundering is an open question.
      image
      ',10),_={href:"https://blog.chainalysis.com/reports/2021-crypto-crime-report-intro-ransomware-scams-darknet-markets",target:"_blank",rel:"noopener noreferrer"},k=e("h2",{id:"examples",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#examples","aria-hidden":"true"},"#"),n(" Examples")],-1),x={href:"https://www.chainalysis.com/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://www.elliptic.co/",target:"_blank",rel:"noopener noreferrer"},C={href:"https://www.neutrino.nu/",target:"_blank",rel:"noopener noreferrer"},z={href:"https://www.coinfirm.io/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://blockchaingroup.io/",target:"_blank",rel:"noopener noreferrer"},q={href:"https://ciphertrace.com/",target:"_blank",rel:"noopener noreferrer"},A={href:"https://complyadvantage.com/aml-crypto-compliance/",target:"_blank",rel:"noopener noreferrer"},I={href:"https://www.idology.com/solutions/compliance/",target:"_blank",rel:"noopener noreferrer"},E={href:"https://elementus.io/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://dmgblockchain.com/",target:"_blank",rel:"noopener noreferrer"},N={href:"https://www.scorechain.com/",target:"_blank",rel:"noopener noreferrer"},S={href:"https://crystalblockchain.com/",target:"_blank",rel:"noopener noreferrer"},P=e("li",null,"Coinvalidation",-1);function Y(F,G){const o=s("router-link"),r=s("RouterLink"),a=s("ExternalLinkIcon");return h(),d("div",null,[p,y,e("nav",m,[e("ul",null,[e("li",null,[t(o,{to:"#spying-technology"},{default:i(()=>[n("Spying technology")]),_:1}),e("ul",null,[e("li",null,[t(o,{to:"#aml-kyc-information"},{default:i(()=>[n("AML/KYC information")]),_:1})]),e("li",null,[t(o,{to:"#blockchain-analysis"},{default:i(()=>[n("Blockchain analysis")]),_:1})]),e("li",null,[t(o,{to:"#wallet-synchronization-analysis"},{default:i(()=>[n("Wallet synchronization analysis")]),_:1})]),e("li",null,[t(o,{to:"#transaction-broadcasting"},{default:i(()=>[n("Transaction broadcasting")]),_:1})])])]),e("li",null,[t(o,{to:"#criticisms"},{default:i(()=>[n("Criticisms")]),_:1}),e("ul",null,[e("li",null,[t(o,{to:"#attempt-to-invade-privacy"},{default:i(()=>[n("Attempt to invade privacy")]),_:1})]),e("li",null,[t(o,{to:"#attempt-to-destroy-fungibility"},{default:i(()=>[n("Attempt to destroy fungibility")]),_:1})]),e("li",null,[t(o,{to:"#no-mechanism-for-oversight-or-appeal"},{default:i(()=>[n("No mechanism for oversight or appeal")]),_:1})]),e("li",null,[t(o,{to:"#jurisdiction"},{default:i(()=>[n("Jurisdiction")]),_:1})]),e("li",null,[t(o,{to:"#incentivized-to-oppose-bitcoin-updates"},{default:i(()=>[n("Incentivized to oppose bitcoin updates")]),_:1})]),e("li",null,[t(o,{to:"#oversold-effectiveness"},{default:i(()=>[n("Oversold effectiveness")]),_:1})])])]),e("li",null,[t(o,{to:"#examples"},{default:i(()=>[n("Examples")]),_:1})])])]),f,e("p",null,[n("Bitcoin on-chain transactions are visible to all and so can be analyzed. Important techniques are the "),t(r,{to:"/glossary/Glossary-PrivacyWasabi.html#common-input-ownership-heuristic"},{default:i(()=>[n("common-input-ownership")]),_:1}),n(" heuristic and "),t(r,{to:"/why-wasabi/AddressReuse.html"},{default:i(()=>[n("address reuse")]),_:1}),n(".")]),b,e("p",null,[n("Bitcoin lightweight wallets often download their own history and balance by querying a third-party server. Transaction surveillance companies often try to exploit this to learn which addresses and transactions belong to certain wallets and IPs. The companies have been known to collect "),e("a",g,[n("BIP 37"),t(a)]),n(" filters from BIP37-enabled wallets. They almost-certainly also run many Electrum servers which can spy on any Electrum wallet that connects to them.")]),v,e("p",null,[n("Privacy invasions can lead to damaging or destroying bitcoin "),t(r,{to:"/glossary/Glossary-GeneralBitcoin.html#fungibility"},{default:i(()=>[n("fungibility")]),_:1}),n(". The aim of bitcoin is to be a decentralized digital currency, but if all users are eventually required to consult centralized blacklists before accepting bitcoin, then its decentralization will be destroyed.")]),e("p",null,[t(r,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html#how-is-financial-privacy-an-essential-element-to-fungibility-in-bitcoin"},{default:i(()=>[n("How is financial privacy an essential element to fungibility in Bitcoin?")]),_:1})]),w,e("p",null,[e("em",null,[n("According to an excerpt from Chainalysis in their "),e("a",_,[n("2021 report"),t(a)]),n(", in 2019, criminal activity represented only 2.1% of all cryptocurrency transaction volume.")])]),k,e("ul",null,[e("li",null,[e("a",x,[n("Chainanalysis"),t(a)])]),e("li",null,[e("a",T,[n("Elliptic"),t(a)])]),e("li",null,[e("a",C,[n("Neutrino"),t(a)])]),e("li",null,[e("a",z,[n("Coinfirm"),t(a)])]),e("li",null,[e("a",B,[n("Blockchain Group"),t(a)])]),e("li",null,[e("a",q,[n("Ciphertrace"),t(a)])]),e("li",null,[e("a",A,[n("Comply Advantage"),t(a)])]),e("li",null,[e("a",I,[n("Idology"),t(a)])]),e("li",null,[e("a",E,[n("Elementus"),t(a)])]),e("li",null,[e("a",L,[n("DmgBlockchain"),t(a)])]),e("li",null,[e("a",N,[n("ScoreChain"),t(a)])]),e("li",null,[e("a",S,[n("Crystal"),t(a)])]),P])])}const j=c(u,[["render",Y],["__file","TransactionSurveillanceCompanies.html.vue"]]);export{j as default};
+import{_ as c,r as s,o as h,c as d,a as e,d as t,w as i,b as n,e as l}from"./app.65e5b6fd.js";const u={},p=e("h1",{id:"transaction-surveillance-companies",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#transaction-surveillance-companies","aria-hidden":"true"},"#"),n(" Transaction Surveillance Companies")],-1),y=e("p",null,"A transaction surveillance company is one that attempts to spy on bitcoin users. Their business model is usually to sell the data to any governments, corporations and individuals willing to pay for their services.",-1),m={class:"table-of-contents"},f=l('
       Spying technology
      There are a number of techniques probably used by transaction surveillance companies:
       AML/KYC information
      Many bitcoin exchanges require users to undergo Anti-Money Laundering (AML) and Know-Your-Customer (KYC) checks, which requires users to reveal all kinds of invasive personal information such as their real name, residence, occupation, net worth and income. All this information is usually passed onto the exchange's partner transaction surveillance company, which keeps a database linking the victim's personal information with their bitcoin addresses and transactions.
       Blockchain analysis
      ',5),b=e("h3",{id:"wallet-synchronization-analysis",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-synchronization-analysis","aria-hidden":"true"},"#"),n(" Wallet synchronization analysis")],-1),g={href:"https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki",target:"_blank",rel:"noopener noreferrer"},v=l('
       Transaction broadcasting
      Surveillance companies have been known to sybil and eclipse attack the bitcoin network, and specific nodes, in order to try to find the source IP addresses of unconfirmed transactions.
       Criticisms
       Attempt to invade privacy
      The right to privacy is recognized as a human right, for instance in the US constitution, European Union regulations and the Constitution of India.
      Financial privacy is an essential criteria for the efficient operation of a free market: if you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.
      Financial privacy is essential for personal safety: if thieves can see your income, holdings, and spending, they can use that information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your packages from your doorstep, or impersonate businesses you transact with. They also know exactly how much to try to scam you for.
      Financial privacy is essential for human dignity: no one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.
      Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.
      Globally visible public records in finance are completely unheard-of. They are undesirable and arguably intolerable. The Bitcoin whitepaper made a promise of how we could get around the visibility of the ledger with pseudonymous addresses, but the ecosystem has broken that promise in a bunch of places and we ought to fix it. Bitcoin could have coded your name or IP address into every transaction. It didn't. The whitepaper even has a section on privacy. Sufficient privacy is an essential prerequisite for a viable digital currency.
       Attempt to destroy fungibility
      ',11),w=l('
       No mechanism for oversight or appeal
      There appears to be no recourse for someone affected by false positive identification of exchange-disapproved transaction history. This could result in them wrongly having their coins confiscated.
       Jurisdiction
      Transaction surveillance company market themselves as a tool for finding "bad guys", but it's unclear which jurisdiction that applies to. For example, could one day the government of China pressure those companies into marking certain coins as "bad" because they belong to users who disagree with Chinese government policy?
       Incentivized to oppose bitcoin updates
      During the deployment of segregated witness, certain transaction surveillance companies were believed to have spread misinformation about it, because the update enables Lightning Network. The companies saw it as a threat to their business, since it can enable transacting with bitcoin more privately.
       Oversold effectiveness
      Transaction surveillance companies rely on heuristics or assumptions when analyzing the blockchain. These heuristics are sometimes not true, for example, the common-input-ownership heuristic is broken by CoinJoin. Even if that heuristic is true, it still requires actually identifying the cluster, which is not always possible.
      Laws surrounding anti-money-laundering typically require businesses to make reasonable efforts to investigate the source of funds. Usually, the transaction surveillance company's customers simply want to legally protect themselves, regardless of whether the surveillance actually works. There is a lot of money in this space from governments and other authorities, who usually don't understand the underlying technology and are happy to throw money at several startups who claim to be able to accurately track everything. Whether the activities of transaction surveillance companies actually help against money laundering is an open question.
      image
      ',10),_={href:"https://blog.chainalysis.com/reports/2021-crypto-crime-report-intro-ransomware-scams-darknet-markets",target:"_blank",rel:"noopener noreferrer"},k=e("h2",{id:"examples",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#examples","aria-hidden":"true"},"#"),n(" Examples")],-1),x={href:"https://www.chainalysis.com/",target:"_blank",rel:"noopener noreferrer"},T={href:"https://www.elliptic.co/",target:"_blank",rel:"noopener noreferrer"},C={href:"https://www.neutrino.nu/",target:"_blank",rel:"noopener noreferrer"},z={href:"https://www.coinfirm.io/",target:"_blank",rel:"noopener noreferrer"},B={href:"https://blockchaingroup.io/",target:"_blank",rel:"noopener noreferrer"},q={href:"https://ciphertrace.com/",target:"_blank",rel:"noopener noreferrer"},A={href:"https://complyadvantage.com/aml-crypto-compliance/",target:"_blank",rel:"noopener noreferrer"},I={href:"https://www.idology.com/solutions/compliance/",target:"_blank",rel:"noopener noreferrer"},E={href:"https://elementus.io/",target:"_blank",rel:"noopener noreferrer"},L={href:"https://dmgblockchain.com/",target:"_blank",rel:"noopener noreferrer"},N={href:"https://www.scorechain.com/",target:"_blank",rel:"noopener noreferrer"},S={href:"https://crystalblockchain.com/",target:"_blank",rel:"noopener noreferrer"},P=e("li",null,"Coinvalidation",-1);function Y(F,G){const o=s("router-link"),r=s("RouterLink"),a=s("ExternalLinkIcon");return h(),d("div",null,[p,y,e("nav",m,[e("ul",null,[e("li",null,[t(o,{to:"#spying-technology"},{default:i(()=>[n("Spying technology")]),_:1}),e("ul",null,[e("li",null,[t(o,{to:"#aml-kyc-information"},{default:i(()=>[n("AML/KYC information")]),_:1})]),e("li",null,[t(o,{to:"#blockchain-analysis"},{default:i(()=>[n("Blockchain analysis")]),_:1})]),e("li",null,[t(o,{to:"#wallet-synchronization-analysis"},{default:i(()=>[n("Wallet synchronization analysis")]),_:1})]),e("li",null,[t(o,{to:"#transaction-broadcasting"},{default:i(()=>[n("Transaction broadcasting")]),_:1})])])]),e("li",null,[t(o,{to:"#criticisms"},{default:i(()=>[n("Criticisms")]),_:1}),e("ul",null,[e("li",null,[t(o,{to:"#attempt-to-invade-privacy"},{default:i(()=>[n("Attempt to invade privacy")]),_:1})]),e("li",null,[t(o,{to:"#attempt-to-destroy-fungibility"},{default:i(()=>[n("Attempt to destroy fungibility")]),_:1})]),e("li",null,[t(o,{to:"#no-mechanism-for-oversight-or-appeal"},{default:i(()=>[n("No mechanism for oversight or appeal")]),_:1})]),e("li",null,[t(o,{to:"#jurisdiction"},{default:i(()=>[n("Jurisdiction")]),_:1})]),e("li",null,[t(o,{to:"#incentivized-to-oppose-bitcoin-updates"},{default:i(()=>[n("Incentivized to oppose bitcoin updates")]),_:1})]),e("li",null,[t(o,{to:"#oversold-effectiveness"},{default:i(()=>[n("Oversold effectiveness")]),_:1})])])]),e("li",null,[t(o,{to:"#examples"},{default:i(()=>[n("Examples")]),_:1})])])]),f,e("p",null,[n("Bitcoin on-chain transactions are visible to all and so can be analyzed. Important techniques are the "),t(r,{to:"/glossary/Glossary-PrivacyWasabi.html#common-input-ownership-heuristic"},{default:i(()=>[n("common-input-ownership")]),_:1}),n(" heuristic and "),t(r,{to:"/why-wasabi/AddressReuse.html"},{default:i(()=>[n("address reuse")]),_:1}),n(".")]),b,e("p",null,[n("Bitcoin lightweight wallets often download their own history and balance by querying a third-party server. Transaction surveillance companies often try to exploit this to learn which addresses and transactions belong to certain wallets and IPs. The companies have been known to collect "),e("a",g,[n("BIP 37"),t(a)]),n(" filters from BIP37-enabled wallets. They almost-certainly also run many Electrum servers which can spy on any Electrum wallet that connects to them.")]),v,e("p",null,[n("Privacy invasions can lead to damaging or destroying bitcoin "),t(r,{to:"/glossary/Glossary-GeneralBitcoin.html#fungibility"},{default:i(()=>[n("fungibility")]),_:1}),n(". The aim of bitcoin is to be a decentralized digital currency, but if all users are eventually required to consult centralized blacklists before accepting bitcoin, then its decentralization will be destroyed.")]),e("p",null,[t(r,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html#how-is-financial-privacy-an-essential-element-to-fungibility-in-bitcoin"},{default:i(()=>[n("How is financial privacy an essential element to fungibility in Bitcoin?")]),_:1})]),w,e("p",null,[e("em",null,[n("According to an excerpt from Chainalysis in their "),e("a",_,[n("2021 report"),t(a)]),n(", in 2019, criminal activity represented only 2.1% of all cryptocurrency transaction volume.")])]),k,e("ul",null,[e("li",null,[e("a",x,[n("Chainanalysis"),t(a)])]),e("li",null,[e("a",T,[n("Elliptic"),t(a)])]),e("li",null,[e("a",C,[n("Neutrino"),t(a)])]),e("li",null,[e("a",z,[n("Coinfirm"),t(a)])]),e("li",null,[e("a",B,[n("Blockchain Group"),t(a)])]),e("li",null,[e("a",q,[n("Ciphertrace"),t(a)])]),e("li",null,[e("a",A,[n("Comply Advantage"),t(a)])]),e("li",null,[e("a",I,[n("Idology"),t(a)])]),e("li",null,[e("a",E,[n("Elementus"),t(a)])]),e("li",null,[e("a",L,[n("DmgBlockchain"),t(a)])]),e("li",null,[e("a",N,[n("ScoreChain"),t(a)])]),e("li",null,[e("a",S,[n("Crystal"),t(a)])]),P])])}const j=c(u,[["render",Y],["__file","TransactionSurveillanceCompanies.html.vue"]]);export{j as default};
diff --git a/assets/WalletGeneration.html.79c8be3e.js b/assets/WalletGeneration.html.91172f61.js
similarity index 99%
rename from assets/WalletGeneration.html.79c8be3e.js
rename to assets/WalletGeneration.html.91172f61.js
index 22ba66a747..2d9ff43aa8 100644
--- a/assets/WalletGeneration.html.79c8be3e.js
+++ b/assets/WalletGeneration.html.91172f61.js
@@ -1,4 +1,4 @@
-import{_ as d,a as c,b as u}from"./AddWalletAddPassword.45b736a5.js";import{_ as h,a as p}from"./AddWalletConfirmRecoveryWords.2792528c.js";import{_ as m}from"./CoinjoinStrategy.5455b7fb.js";import{_ as v,r as o,o as b,c as w,a as e,d as a,w as n,b as t,e as r}from"./app.a5b7c2b2.js";const y="/AddWalletSuccessfullyAdded.png",_={},f=e("h1",{id:"wallet-generation",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-generation","aria-hidden":"true"},"#"),t(" Wallet Generation")],-1),g={class:"table-of-contents"},k=r('
       Introduction
      With Wasabi you can generate an unlimited number of Bitcoin wallets very quickly, without any cost, and without asking anyone for permission. Each wallet has separate private and public keys in a unique backup, and they are not at all linked to the other wallets generated on the same computer. So, with several wallets, you can conveniently manage your bitcoin for different use cases without worrying about revealing that you control them.
       Generating the wallet step-by-step
      1. Launch Wasabi Wallet. The very first time you run the software the Add Wallet dialog will be open automatically, but you can also access it by clicking on Add Wallet in the NavBar or Searchbar.
      2. Click Create a new wallet to generate a new wallet.
      Add a Bitcoin wallet with Wasabi
      1. Give the wallet a name. This name is not shared with anyone, it is only stored locally on your computer. Click Continue.
      Add Wallet Wallet Name
      ',7),W={start:"4"},P=e("strong",null,"together with",-1),x={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},B=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"Back up your recovery words!"),e("p",null,"Without the recovery words (Seed phrase) AND the password, you cannot recover your wallet. So, triple-check that you have a proper backup! Make sure the backup of your recovery words is stored separately from the password backup.")],-1),S=e("p",null,[e("img",{src:h,alt:"Wasabi Wallet recovery words",title:"Wasabi Wallet recovery words"})],-1),A=e("ol",{start:"5"},[e("li",null,[t("You must confirm the Recovery Words by clicking on the right word in the right order, as a check to make sure that your Recovery Words are backed up. So, confirm the Recovery Words, and click "),e("code",null,"Continue"),t(".")])],-1),C=e("p",null,[e("img",{src:p,alt:"Wasabi Wallet confirm recovery words",title:"Wasabi Wallet confirm recovery words"})],-1),I={start:"6"},N=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"Back up your password!"),e("p",null,"Without the password, you cannot spend your bitcoin or recover your wallet, even if you have the recovery words (Seed phrase). So, triple-check that you have a proper backup!")],-1),E=e("li",null,[e("p",null,[t("Confirm the password and click the "),e("code",null,"Continue"),t(" button.")])],-1),G=r('
      Wasabi Wallet Add Password
      1. Select the coinjoin strategy for this wallet and click Continue.
      Add Wallet Coinjoin Strategy
      1. The wallet is succesfully added! Click Done.
      Wallet Successfully Added
       Important info about your wallet password
      ',6),T={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},L=e("strong",null,"both",-1),R=e("h2",{id:"how-are-the-secrets-created",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-are-the-secrets-created","aria-hidden":"true"},"#"),t(" How are the secrets created")],-1),V={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},j=r(`
                            +--------------+
+import{_ as d,a as c,b as u}from"./AddWalletAddPassword.45b736a5.js";import{_ as h,a as p}from"./AddWalletConfirmRecoveryWords.2792528c.js";import{_ as m}from"./CoinjoinStrategy.5455b7fb.js";import{_ as v,r as o,o as b,c as w,a as e,d as a,w as n,b as t,e as r}from"./app.65e5b6fd.js";const y="/AddWalletSuccessfullyAdded.png",_={},f=e("h1",{id:"wallet-generation",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-generation","aria-hidden":"true"},"#"),t(" Wallet Generation")],-1),g={class:"table-of-contents"},k=r('
       Introduction
      With Wasabi you can generate an unlimited number of Bitcoin wallets very quickly, without any cost, and without asking anyone for permission. Each wallet has separate private and public keys in a unique backup, and they are not at all linked to the other wallets generated on the same computer. So, with several wallets, you can conveniently manage your bitcoin for different use cases without worrying about revealing that you control them.
       Generating the wallet step-by-step
      1. Launch Wasabi Wallet. The very first time you run the software the Add Wallet dialog will be open automatically, but you can also access it by clicking on Add Wallet in the NavBar or Searchbar.
      2. Click Create a new wallet to generate a new wallet.
      Add a Bitcoin wallet with Wasabi
      1. Give the wallet a name. This name is not shared with anyone, it is only stored locally on your computer. Click Continue.
      Add Wallet Wallet Name
      ',7),W={start:"4"},P=e("strong",null,"together with",-1),x={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},B=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"Back up your recovery words!"),e("p",null,"Without the recovery words (Seed phrase) AND the password, you cannot recover your wallet. So, triple-check that you have a proper backup! Make sure the backup of your recovery words is stored separately from the password backup.")],-1),S=e("p",null,[e("img",{src:h,alt:"Wasabi Wallet recovery words",title:"Wasabi Wallet recovery words"})],-1),A=e("ol",{start:"5"},[e("li",null,[t("You must confirm the Recovery Words by clicking on the right word in the right order, as a check to make sure that your Recovery Words are backed up. So, confirm the Recovery Words, and click "),e("code",null,"Continue"),t(".")])],-1),C=e("p",null,[e("img",{src:p,alt:"Wasabi Wallet confirm recovery words",title:"Wasabi Wallet confirm recovery words"})],-1),I={start:"6"},N=e("div",{class:"custom-container danger"},[e("p",{class:"custom-container-title"},"Back up your password!"),e("p",null,"Without the password, you cannot spend your bitcoin or recover your wallet, even if you have the recovery words (Seed phrase). So, triple-check that you have a proper backup!")],-1),E=e("li",null,[e("p",null,[t("Confirm the password and click the "),e("code",null,"Continue"),t(" button.")])],-1),G=r('
      Wasabi Wallet Add Password
      1. Select the coinjoin strategy for this wallet and click Continue.
      Add Wallet Coinjoin Strategy
      1. The wallet is succesfully added! Click Done.
      Wallet Successfully Added
       Important info about your wallet password
      ',6),T={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},L=e("strong",null,"both",-1),R=e("h2",{id:"how-are-the-secrets-created",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#how-are-the-secrets-created","aria-hidden":"true"},"#"),t(" How are the secrets created")],-1),V={href:"https://github.com/bitcoin/bips/blob/master/bip-0038.mediawiki",target:"_blank",rel:"noopener noreferrer"},j=r(`
                            +--------------+
                       | Entropy      |
                       +--------------+
   +------------+             |
diff --git a/assets/WalletLoad.html.23ac7679.js b/assets/WalletLoad.html.3bdf69ef.js
similarity index 99%
rename from assets/WalletLoad.html.23ac7679.js
rename to assets/WalletLoad.html.3bdf69ef.js
index 9e195e041e..4a336829dc 100644
--- a/assets/WalletLoad.html.23ac7679.js
+++ b/assets/WalletLoad.html.3bdf69ef.js
@@ -1 +1 @@
-import{_ as d}from"./WalletSynchronizing.d188367c.js";import{_ as c,r as i,o as h,c as u,a as e,d as a,w as o,b as t,e as s}from"./app.a5b7c2b2.js";const f="/WalletOpen.png",p={},b=e("h1",{id:"wallet-load",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-load","aria-hidden":"true"},"#"),t(" Wallet Load")],-1),w={class:"table-of-contents"},y=e("h2",{id:"loading-wallet-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#loading-wallet-step-by-step","aria-hidden":"true"},"#"),t(" Loading wallet step-by-step")],-1),_=e("p",null,"To load a wallet and start the synchonization process, you need to open your wallet by typing in the password. The first time synchronization of your wallet might take some time depending on the size of its history.",-1),m=e("h3",{id:"wallet-list",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-list","aria-hidden":"true"},"#"),t(" Wallet list")],-1),g=e("code",null,"Wallet list",-1),k=s('
      Click the wallet you want to view, type in the password and press Open.
      Type your password to open the wallet
       Synchronization
       Filter download
      ',4),v={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},W=s('
      Wallet is synchronizing itself with the Bitcoin network
       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
      ',4),x=e("h3",{id:"turbosync",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#turbosync","aria-hidden":"true"},"#"),t(" TurboSync")],-1),z={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},T=e("em",null,"TurboSync",-1),B=e("em",null,"TurboSync",-1),S=s('
      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.
      ',5);function I(L,F){const n=i("router-link"),l=i("RouterLink"),r=i("ExternalLinkIcon");return h(),u("div",null,[b,e("nav",w,[e("ul",null,[e("li",null,[a(n,{to:"#loading-wallet-step-by-step"},{default:o(()=>[t("Loading wallet step-by-step")]),_:1}),e("ul",null,[e("li",null,[a(n,{to:"#wallet-list"},{default:o(()=>[t("Wallet list")]),_:1})])])]),e("li",null,[a(n,{to:"#synchronization"},{default:o(()=>[t("Synchronization")]),_:1}),e("ul",null,[e("li",null,[a(n,{to:"#filter-download"},{default:o(()=>[t("Filter download")]),_:1})]),e("li",null,[a(n,{to:"#filter-scanning"},{default:o(()=>[t("Filter scanning")]),_:1})]),e("li",null,[a(n,{to:"#block-download"},{default:o(()=>[t("Block download")]),_:1})]),e("li",null,[a(n,{to:"#turbosync"},{default:o(()=>[t("TurboSync")]),_:1})])])])])]),y,_,m,e("p",null,[t("On the left side of Wasabi Wallet is the "),g,t(", where you see an alphabetically sorted list of all the previously "),a(l,{to:"/using-wasabi/WalletGeneration.html"},{default:o(()=>[t("generated")]),_:1}),t(" wallets.")]),k,e("p",null,[t("As soon as you start Wasabi, it connects to the backend server with a new Tor identity and requests the "),e("a",v,[t("BIP 158 block filters"),a(r)]),t(". 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.")]),W,e("p",null,[t("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(l,{to:"/using-wasabi/BitcoinFullNode.html"},{default:o(()=>[t("a Bitcoin full node connected")]),_:1}),t(", 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.")]),x,e("p",null,[t("Since Wasabi version "),e("a",z,[t("2.0.4"),a(r)]),t(" a new feature is added called "),T,t(". "),B,t(" leads to a significant reduction of wallet loading time, especially for a big wallet.")]),S])}const q=c(p,[["render",I],["__file","WalletLoad.html.vue"]]);export{q as default};
+import{_ as d}from"./WalletSynchronizing.d188367c.js";import{_ as c,r as i,o as h,c as u,a as e,d as a,w as o,b as t,e as s}from"./app.65e5b6fd.js";const f="/WalletOpen.png",p={},b=e("h1",{id:"wallet-load",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-load","aria-hidden":"true"},"#"),t(" Wallet Load")],-1),w={class:"table-of-contents"},y=e("h2",{id:"loading-wallet-step-by-step",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#loading-wallet-step-by-step","aria-hidden":"true"},"#"),t(" Loading wallet step-by-step")],-1),_=e("p",null,"To load a wallet and start the synchonization process, you need to open your wallet by typing in the password. The first time synchronization of your wallet might take some time depending on the size of its history.",-1),m=e("h3",{id:"wallet-list",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wallet-list","aria-hidden":"true"},"#"),t(" Wallet list")],-1),g=e("code",null,"Wallet list",-1),k=s('
      Click the wallet you want to view, type in the password and press Open.
      Type your password to open the wallet
       Synchronization
       Filter download
      ',4),v={href:"https://github.com/bitcoin/bips/blob/master/bip-0158.mediawiki",target:"_blank",rel:"noopener noreferrer"},W=s('
      Wallet is synchronizing itself with the Bitcoin network
       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
      ',4),x=e("h3",{id:"turbosync",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#turbosync","aria-hidden":"true"},"#"),t(" TurboSync")],-1),z={href:"https://github.com/zkSNACKs/WalletWasabi/releases/tag/v2.0.4",target:"_blank",rel:"noopener noreferrer"},T=e("em",null,"TurboSync",-1),B=e("em",null,"TurboSync",-1),S=s('
      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.
      ',5);function I(L,F){const n=i("router-link"),l=i("RouterLink"),r=i("ExternalLinkIcon");return h(),u("div",null,[b,e("nav",w,[e("ul",null,[e("li",null,[a(n,{to:"#loading-wallet-step-by-step"},{default:o(()=>[t("Loading wallet step-by-step")]),_:1}),e("ul",null,[e("li",null,[a(n,{to:"#wallet-list"},{default:o(()=>[t("Wallet list")]),_:1})])])]),e("li",null,[a(n,{to:"#synchronization"},{default:o(()=>[t("Synchronization")]),_:1}),e("ul",null,[e("li",null,[a(n,{to:"#filter-download"},{default:o(()=>[t("Filter download")]),_:1})]),e("li",null,[a(n,{to:"#filter-scanning"},{default:o(()=>[t("Filter scanning")]),_:1})]),e("li",null,[a(n,{to:"#block-download"},{default:o(()=>[t("Block download")]),_:1})]),e("li",null,[a(n,{to:"#turbosync"},{default:o(()=>[t("TurboSync")]),_:1})])])])])]),y,_,m,e("p",null,[t("On the left side of Wasabi Wallet is the "),g,t(", where you see an alphabetically sorted list of all the previously "),a(l,{to:"/using-wasabi/WalletGeneration.html"},{default:o(()=>[t("generated")]),_:1}),t(" wallets.")]),k,e("p",null,[t("As soon as you start Wasabi, it connects to the backend server with a new Tor identity and requests the "),e("a",v,[t("BIP 158 block filters"),a(r)]),t(". 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.")]),W,e("p",null,[t("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(l,{to:"/using-wasabi/BitcoinFullNode.html"},{default:o(()=>[t("a Bitcoin full node connected")]),_:1}),t(", 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.")]),x,e("p",null,[t("Since Wasabi version "),e("a",z,[t("2.0.4"),a(r)]),t(" a new feature is added called "),T,t(". "),B,t(" leads to a significant reduction of wallet loading time, especially for a big wallet.")]),S])}const q=c(p,[["render",I],["__file","WalletLoad.html.vue"]]);export{q as default};
diff --git a/assets/WalletRecovery.html.1d4fe6d7.js b/assets/WalletRecovery.html.72f32cf9.js
similarity index 98%
rename from assets/WalletRecovery.html.1d4fe6d7.js
rename to assets/WalletRecovery.html.72f32cf9.js
index 3626b53365..6798cef59d 100644
--- a/assets/WalletRecovery.html.1d4fe6d7.js
+++ b/assets/WalletRecovery.html.72f32cf9.js
@@ -1 +1 @@
-import{_ as n}from"./AddWalletButton.98ad9c28.js";import{_ as c,a as d,b as p}from"./AddWalletAddPassword.45b736a5.js";import{_ as h,r as l,o as u,c as m,a as e,d as a,w as s,b as t,e as w}from"./app.a5b7c2b2.js";const _="/WalletRecovery.png",b="/WalletRecoveryAdvanced.png",W={},f=e("h1",{id:"recover-a-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#recover-a-wallet","aria-hidden":"true"},"#"),t(" Recover a Wallet")],-1),y=e("p",null,"There are two different ways that you can recover an already used wallet in Wasabi.",-1),v={class:"table-of-contents"},k=e("h2",{id:"mnemonic-recovery-words-and-password",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#mnemonic-recovery-words-and-password","aria-hidden":"true"},"#"),t(" Mnemonic Recovery Words and Password")],-1),g={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},A={href:"https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki",target:"_blank",rel:"noopener noreferrer"},R=e("strong",null,"Both",-1),x=e("strong",null,"and",-1),B={href:"https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt",target:"_blank",rel:"noopener noreferrer"},N=w('
      To recover a wallet:
      1. Click on Add Wallet at the bottom left corner of the main view.
      Wasabi Wallet Add Wallet
      1. Click on Recover a wallet.
      Wasabi Wallet Add Wallet
      1. Give the wallet a name for future recognition of the wallet.
      Wasabi Wallet Name Wallet
      1. Type in the Recovery Words in the correct order and click Continue.
      Wasabi Wallet Recover Wallet
      1. Type in the Password.
      Add Wallet Add Password
      Now Wasabi will recover your wallet.
      With this, only the private keys are imported, but not the labels of your addresses.
      DANGER
      At recovery, Wasabi is unable to check if your password is correct or not. If you type a wrong password a completely different wallet will be recovered.
      You can also use the Advanced Recovery Options to specify the gap limit. The gap limit is about how far Wasabi will check the HD wallet structure for consecutive addresses that have no coins, in some cases, you may want to increase this limit.
      Wasabi Wallet Recovery Advanced
      TIP
      With this method, you can recover a wallet that was generated with any BIP39 compatible software, not just a Wasabi generated wallet.
       Back up Wallet File and Password
      ',18),P=e("code",null,"WalletBackups",-1),I=e("code",null,"Add Wallet",-1),T=e("code",null,"Import a wallet",-1),C=e("p",null,[t("Alternitavely: copy the wallet file to the "),e("code",null,"Wallets"),t(" folder, and upon the next restart of Wasabi, it will show this wallet in the "),e("code",null,"NavBar"),t(", from there you can open it as usual.")],-1),E=e("p",null,"Using this method will also backup your address labels and cluster history.",-1),F=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"WARNING"),e("p",null,"Make sure to back up your password separately because it is necessary to spend your bitcoin.")],-1);function L(V,G){const r=l("router-link"),o=l("ExternalLinkIcon"),i=l("RouterLink");return u(),m("div",null,[f,y,e("nav",v,[e("ul",null,[e("li",null,[a(r,{to:"#mnemonic-recovery-words-and-password"},{default:s(()=>[t("Mnemonic Recovery Words and Password")]),_:1})]),e("li",null,[a(r,{to:"#back-up-wallet-file-and-password"},{default:s(()=>[t("Back up Wallet File and Password")]),_:1})])])]),k,e("p",null,[t("Wasabi uses the "),e("a",g,[t("BIP 39"),a(o)]),t(" mnemonic code for generating "),e("a",A,[t("BIP 32"),a(o)]),t(" hierarchical deterministic wallets. "),R,t(" your password "),x,t(" the generated 12 mnemonic recovery words are the necessary secrets to recover your wallet. The recovery words are spell checked based on the "),e("a",B,[t("official wordlist"),a(o)]),t(", with the right word shown below the text box.")]),N,e("p",null,[t("Wasabi Wallet creates a backup of your wallet file inside "),P,t(" in your "),a(i,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:s(()=>[t("Wasabi data folder")]),_:1}),t(". If you have done a backup of this file, then you can import it at "),I,t(", by clicking on "),T,t(".")]),C,E,F])}const U=h(W,[["render",L],["__file","WalletRecovery.html.vue"]]);export{U as default};
+import{_ as n}from"./AddWalletButton.98ad9c28.js";import{_ as c,a as d,b as p}from"./AddWalletAddPassword.45b736a5.js";import{_ as h,r as l,o as u,c as m,a as e,d as a,w as s,b as t,e as w}from"./app.65e5b6fd.js";const _="/WalletRecovery.png",b="/WalletRecoveryAdvanced.png",W={},f=e("h1",{id:"recover-a-wallet",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#recover-a-wallet","aria-hidden":"true"},"#"),t(" Recover a Wallet")],-1),y=e("p",null,"There are two different ways that you can recover an already used wallet in Wasabi.",-1),v={class:"table-of-contents"},k=e("h2",{id:"mnemonic-recovery-words-and-password",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#mnemonic-recovery-words-and-password","aria-hidden":"true"},"#"),t(" Mnemonic Recovery Words and Password")],-1),g={href:"https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki",target:"_blank",rel:"noopener noreferrer"},A={href:"https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki",target:"_blank",rel:"noopener noreferrer"},R=e("strong",null,"Both",-1),x=e("strong",null,"and",-1),B={href:"https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt",target:"_blank",rel:"noopener noreferrer"},N=w('
      To recover a wallet:
      1. Click on Add Wallet at the bottom left corner of the main view.
      Wasabi Wallet Add Wallet
      1. Click on Recover a wallet.
      Wasabi Wallet Add Wallet
      1. Give the wallet a name for future recognition of the wallet.
      Wasabi Wallet Name Wallet
      1. Type in the Recovery Words in the correct order and click Continue.
      Wasabi Wallet Recover Wallet
      1. Type in the Password.
      Add Wallet Add Password
      Now Wasabi will recover your wallet.
      With this, only the private keys are imported, but not the labels of your addresses.
      DANGER
      At recovery, Wasabi is unable to check if your password is correct or not. If you type a wrong password a completely different wallet will be recovered.
      You can also use the Advanced Recovery Options to specify the gap limit. The gap limit is about how far Wasabi will check the HD wallet structure for consecutive addresses that have no coins, in some cases, you may want to increase this limit.
      Wasabi Wallet Recovery Advanced
      TIP
      With this method, you can recover a wallet that was generated with any BIP39 compatible software, not just a Wasabi generated wallet.
       Back up Wallet File and Password
      ',18),P=e("code",null,"WalletBackups",-1),I=e("code",null,"Add Wallet",-1),T=e("code",null,"Import a wallet",-1),C=e("p",null,[t("Alternitavely: copy the wallet file to the "),e("code",null,"Wallets"),t(" folder, and upon the next restart of Wasabi, it will show this wallet in the "),e("code",null,"NavBar"),t(", from there you can open it as usual.")],-1),E=e("p",null,"Using this method will also backup your address labels and cluster history.",-1),F=e("div",{class:"custom-container warning"},[e("p",{class:"custom-container-title"},"WARNING"),e("p",null,"Make sure to back up your password separately because it is necessary to spend your bitcoin.")],-1);function L(V,G){const r=l("router-link"),o=l("ExternalLinkIcon"),i=l("RouterLink");return u(),m("div",null,[f,y,e("nav",v,[e("ul",null,[e("li",null,[a(r,{to:"#mnemonic-recovery-words-and-password"},{default:s(()=>[t("Mnemonic Recovery Words and Password")]),_:1})]),e("li",null,[a(r,{to:"#back-up-wallet-file-and-password"},{default:s(()=>[t("Back up Wallet File and Password")]),_:1})])])]),k,e("p",null,[t("Wasabi uses the "),e("a",g,[t("BIP 39"),a(o)]),t(" mnemonic code for generating "),e("a",A,[t("BIP 32"),a(o)]),t(" hierarchical deterministic wallets. "),R,t(" your password "),x,t(" the generated 12 mnemonic recovery words are the necessary secrets to recover your wallet. The recovery words are spell checked based on the "),e("a",B,[t("official wordlist"),a(o)]),t(", with the right word shown below the text box.")]),N,e("p",null,[t("Wasabi Wallet creates a backup of your wallet file inside "),P,t(" in your "),a(i,{to:"/FAQ/FAQ-UseWasabi.html#where-can-i-find-the-wasabi-data-folder"},{default:s(()=>[t("Wasabi data folder")]),_:1}),t(". If you have done a backup of this file, then you can import it at "),I,t(", by clicking on "),T,t(".")]),C,E,F])}const U=h(W,[["render",L],["__file","WalletRecovery.html.vue"]]);export{U as default};
diff --git a/assets/WasabiSetupVM.html.6d5d7c76.js b/assets/WasabiSetupVM.html.b4d60297.js
similarity index 99%
rename from assets/WasabiSetupVM.html.6d5d7c76.js
rename to assets/WasabiSetupVM.html.b4d60297.js
index dea7e75fe2..0771c5b4a9 100644
--- a/assets/WasabiSetupVM.html.6d5d7c76.js
+++ b/assets/WasabiSetupVM.html.b4d60297.js
@@ -1,4 +1,4 @@
-import{_ as u,r,o as d,c,a as e,d as n,w as s,b as a,e as o}from"./app.a5b7c2b2.js";const p="/Virtualbox.png",h={},m=e("h1",{id:"wasabi-setup-in-virtual-machines",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wasabi-setup-in-virtual-machines","aria-hidden":"true"},"#"),a(" Wasabi Setup in Virtual Machines")],-1),b={class:"table-of-contents"},v=o('
       Benefits of Virtual Machines
      Virtualization allows you to create and run as many virtual machines (VMs) on a single computer at one time as desired. The only constraints are the amount of RAM and hard disk space available on the host computer.
      Each VM is isolated from the host machine. Therefore, such things as corrupted files, configuration errors, malware, etc., encountered during the use of a VM do not affect the host computer.
      If you are a developer, using virtual machines gives you several powerful features. You can easily:
      • Create snapshots of a VM's state at any time. These snapshots can be restored later if a problem or undesired condition arises in the current state of the VM.
      • Set up a template VM with a desired development environment or configuration, and then quickly create lightweight, disposable clones of the template for specific tests.
      • Develop and/or test applications in Windows, Linux, and macOS at the same time, on the same computer. You can link them together in a customizable internal network if desired.
      For developers, the use of virtual machines offers some of the basic version control features of git but applied to operating systems rather than files or projects.
       Qubes
      ',7),f={href:"https://www.qubes-os.org/",target:"_blank",rel:"noopener noreferrer"},g={href:"https://www.qubes-os.org/downloads/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://www.qubes-os.org/doc/installation-guide/",target:"_blank",rel:"noopener noreferrer"},k=e("h3",{id:"generate-template-vm",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#generate-template-vm","aria-hidden":"true"},"#"),a(" Generate Template VM")],-1),_=e("code",null,"dom0",-1),y=o(`
      [user@dom0 ~]$ qvm-clone template-debian-10 template-wasabi
+import{_ as u,r,o as d,c,a as e,d as n,w as s,b as a,e as o}from"./app.65e5b6fd.js";const p="/Virtualbox.png",h={},m=e("h1",{id:"wasabi-setup-in-virtual-machines",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#wasabi-setup-in-virtual-machines","aria-hidden":"true"},"#"),a(" Wasabi Setup in Virtual Machines")],-1),b={class:"table-of-contents"},v=o('
       Benefits of Virtual Machines
      Virtualization allows you to create and run as many virtual machines (VMs) on a single computer at one time as desired. The only constraints are the amount of RAM and hard disk space available on the host computer.
      Each VM is isolated from the host machine. Therefore, such things as corrupted files, configuration errors, malware, etc., encountered during the use of a VM do not affect the host computer.
      If you are a developer, using virtual machines gives you several powerful features. You can easily:
      • Create snapshots of a VM's state at any time. These snapshots can be restored later if a problem or undesired condition arises in the current state of the VM.
      • Set up a template VM with a desired development environment or configuration, and then quickly create lightweight, disposable clones of the template for specific tests.
      • Develop and/or test applications in Windows, Linux, and macOS at the same time, on the same computer. You can link them together in a customizable internal network if desired.
      For developers, the use of virtual machines offers some of the basic version control features of git but applied to operating systems rather than files or projects.
       Qubes
      ',7),f={href:"https://www.qubes-os.org/",target:"_blank",rel:"noopener noreferrer"},g={href:"https://www.qubes-os.org/downloads/",target:"_blank",rel:"noopener noreferrer"},w={href:"https://www.qubes-os.org/doc/installation-guide/",target:"_blank",rel:"noopener noreferrer"},k=e("h3",{id:"generate-template-vm",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#generate-template-vm","aria-hidden":"true"},"#"),a(" Generate Template VM")],-1),_=e("code",null,"dom0",-1),y=o(`
      [user@dom0 ~]$ qvm-clone template-debian-10 template-wasabi
 
       Install Dependencies
      Start the gnome-terminal of template-wasabi.
      [user@dom0 ~]$ qvm-run -a template-wasabi gnome-terminal
 
      Update the template-wasabi.
      [user@template-wasabi ~]$ sudo apt update
 [user@template-wasabi ~]$ sudo apt upgrade
@@ -25,4 +25,4 @@ your@vm:~$ dotnet run
 your@vm:~$ git fetch nopara73
 your@vm:~$ git checkout <development branch>
 
      Pull the latest commits.
      your@vm:~$ git pull
-
      `,8),X={href:"https://git-scm.com/",target:"_blank",rel:"noopener noreferrer"},J=e("h3",{id:"install-latest-package",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-latest-package","aria-hidden":"true"},"#"),a(" Install Latest Package")],-1),Z=e("p",null,"Alternatively, you can also install the package in a new VM. This is a stable version suitable to use on mainnet and is separated from the development VM. There are no additional dependencies required to run this version.",-1),ee=e("code",null,"Wasabi-2.0.5",-1),ae=e("p",null,[e("strong",null,"Have fun, and please consider contributing to the Wasabi project!")],-1);function ne(se,te){const t=r("router-link"),i=r("ExternalLinkIcon"),l=r("RouterLink");return d(),c("div",null,[m,e("nav",b,[e("ul",null,[e("li",null,[n(t,{to:"#benefits-of-virtual-machines"},{default:s(()=>[a("Benefits of Virtual Machines")]),_:1})]),e("li",null,[n(t,{to:"#qubes"},{default:s(()=>[a("Qubes")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#generate-template-vm"},{default:s(()=>[a("Generate Template VM")]),_:1})]),e("li",null,[n(t,{to:"#install-dependencies"},{default:s(()=>[a("Install Dependencies")]),_:1})]),e("li",null,[n(t,{to:"#generate-app-vm"},{default:s(()=>[a("Generate App VM")]),_:1})]),e("li",null,[n(t,{to:"#compile-and-run-wasabi"},{default:s(()=>[a("Compile and Run Wasabi")]),_:1})]),e("li",null,[n(t,{to:"#install-package-in-app-vm"},{default:s(()=>[a("Install Package in App VM")]),_:1})])])]),e("li",null,[n(t,{to:"#virtualbox"},{default:s(()=>[a("VirtualBox")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#create-your-first-virtual-machine"},{default:s(()=>[a("Create Your First Virtual Machine")]),_:1})]),e("li",null,[n(t,{to:"#generate-a-template-vm"},{default:s(()=>[a("Generate a Template VM")]),_:1})]),e("li",null,[n(t,{to:"#install-required-dependencies"},{default:s(()=>[a("Install Required Dependencies")]),_:1})]),e("li",null,[n(t,{to:"#cloning-a-virtual-machine"},{default:s(()=>[a("Cloning a Virtual Machine")]),_:1})]),e("li",null,[n(t,{to:"#how-to-create-a-linked-clone"},{default:s(()=>[a("How to Create a Linked Clone")]),_:1})]),e("li",null,[n(t,{to:"#compile-and-run-wasabi-in-your-vm"},{default:s(()=>[a("Compile and Run Wasabi in Your VM")]),_:1})]),e("li",null,[n(t,{to:"#install-latest-package"},{default:s(()=>[a("Install Latest Package")]),_:1})])])])])]),v,e("p",null,[e("a",f,[a("Qubes"),n(i)]),a(" is a free and open-source security-oriented operating system meant for single-user desktop computing. Qubes OS leverages xen-based virtualization to allow for the creation and management of isolated virtual machines (VMs) called qubes. This is valuable for users of high security software like Wasabi Wallet, and especially useful for testers of cutting edge developer branches. There is a separation of the virtual machines running Wasabi on testnet, and those running on mainnet with valuable private keys. If a reviewer compiles a malicious developer branch, then his mainnet private keys are secure in a different qube.")]),e("p",null,[a("This is a step-by-step guide on how to properly compile Wasabi Wallet from source in independent qubes. For tutorials on how to "),e("a",g,[a("download"),n(i)]),a(" and "),e("a",w,[a("install"),n(i)]),a(" Qubes, please see their exhaustive documentation.")]),k,e("p",null,[a("The dependencies to "),n(l,{to:"/using-wasabi/BuildSource.html"},{default:s(()=>[a("compile Wasabi from source")]),_:1}),a(" will be downloaded and installed in a new template VM, which is generated by cloning the Debian template from the "),_,a(" terminal.")]),y,e("p",null,[a("Install "),e("a",x,[a(".NET 7.0 SDK"),n(i)]),a(' for "Build apps" in '),V,a(".")]),M,e("p",null,[n(l,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:s(()=>[a("Download, verify and install")]),_:1}),a(" the latest "),W,a(" package in "),T,a(", then start Wasabi.")]),q,e("p",null,[e("a",S,[a("VirtualBox"),n(i)]),a(' is a lightweight, powerful free and open-source virtualization tool that allows you to run one or more independent operating systems as "virtual machines" (VMs) on your computer. The computer on which VirtualBox is installed is referred to as the "host" machine, and the VMs that are created are referred to as "guests".')]),$,e("p",null,[a("You can download the latest Virtualbox binary for your host OS "),e("a",I,[a("here"),n(i)]),a(".")]),C,B,e("p",null,[a("Detailed instructions for installing VirtualBox on your host computer can be found "),e("a",O,[a("here"),n(i)]),a(".")]),e("p",null,[a("If you run into trouble or have special requirements, the complete User Manual can be found "),e("a",A,[a("here"),n(i)]),a(".")]),N,e("p",null,[a("Detailed instructions for creating various types of virtual machines can be found "),e("a",D,[a("here"),n(i)]),a(".")]),E,L,P,e("ul",null,[e("li",null,[a('Optional, but strongly recommended: Enable the built-in "Guest Additions" functions of Virtualbox. This step will give you a full-sized display, and make the usage of your mouse seamless when switching between different VMs that are running at the same time. Instruction for enabling "Guest Additions" can be found '),e("a",R,[a("here"),n(i)]),a(".")])]),Y,z,e("p",null,[a("Next, the dependencies to "),n(l,{to:"/using-wasabi/BuildSource.html"},{default:s(()=>[a("compile Wasabi from source")]),_:1}),a(" will be downloaded and installed in a new template VM, which can be based on your preferred OS.")]),G,U,F,e("p",null,[a("Install "),e("a",Q,[a(".NET 7.0 SDK"),n(i)]),a(' for "Build apps".')]),j,e("p",null,[a("Instructions on how to create linked clones in VirtualBox can be found "),e("a",K,[a("here"),n(i)]),a(".")]),H,e("p",null,[a("If you are comfortable with "),e("a",X,[a("Git"),n(i)]),a(", you can now have several versions of Wasabi running for testing purposes, at the same time, on the same computer.")]),J,Z,e("p",null,[n(l,{to:"/using-wasabi/InstallPackage.html"},{default:s(()=>[a("Download, verify and install")]),_:1}),a(" the latest "),ee,a(" package in your VM, then start Wasabi.")]),ae])}const oe=u(h,[["render",ne],["__file","WasabiSetupVM.html.vue"]]);export{oe as default};
+
      `,8),X={href:"https://git-scm.com/",target:"_blank",rel:"noopener noreferrer"},J=e("h3",{id:"install-latest-package",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#install-latest-package","aria-hidden":"true"},"#"),a(" Install Latest Package")],-1),Z=e("p",null,"Alternatively, you can also install the package in a new VM. This is a stable version suitable to use on mainnet and is separated from the development VM. There are no additional dependencies required to run this version.",-1),ee=e("code",null,"Wasabi-2.0.5",-1),ae=e("p",null,[e("strong",null,"Have fun, and please consider contributing to the Wasabi project!")],-1);function ne(se,te){const t=r("router-link"),i=r("ExternalLinkIcon"),l=r("RouterLink");return d(),c("div",null,[m,e("nav",b,[e("ul",null,[e("li",null,[n(t,{to:"#benefits-of-virtual-machines"},{default:s(()=>[a("Benefits of Virtual Machines")]),_:1})]),e("li",null,[n(t,{to:"#qubes"},{default:s(()=>[a("Qubes")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#generate-template-vm"},{default:s(()=>[a("Generate Template VM")]),_:1})]),e("li",null,[n(t,{to:"#install-dependencies"},{default:s(()=>[a("Install Dependencies")]),_:1})]),e("li",null,[n(t,{to:"#generate-app-vm"},{default:s(()=>[a("Generate App VM")]),_:1})]),e("li",null,[n(t,{to:"#compile-and-run-wasabi"},{default:s(()=>[a("Compile and Run Wasabi")]),_:1})]),e("li",null,[n(t,{to:"#install-package-in-app-vm"},{default:s(()=>[a("Install Package in App VM")]),_:1})])])]),e("li",null,[n(t,{to:"#virtualbox"},{default:s(()=>[a("VirtualBox")]),_:1}),e("ul",null,[e("li",null,[n(t,{to:"#create-your-first-virtual-machine"},{default:s(()=>[a("Create Your First Virtual Machine")]),_:1})]),e("li",null,[n(t,{to:"#generate-a-template-vm"},{default:s(()=>[a("Generate a Template VM")]),_:1})]),e("li",null,[n(t,{to:"#install-required-dependencies"},{default:s(()=>[a("Install Required Dependencies")]),_:1})]),e("li",null,[n(t,{to:"#cloning-a-virtual-machine"},{default:s(()=>[a("Cloning a Virtual Machine")]),_:1})]),e("li",null,[n(t,{to:"#how-to-create-a-linked-clone"},{default:s(()=>[a("How to Create a Linked Clone")]),_:1})]),e("li",null,[n(t,{to:"#compile-and-run-wasabi-in-your-vm"},{default:s(()=>[a("Compile and Run Wasabi in Your VM")]),_:1})]),e("li",null,[n(t,{to:"#install-latest-package"},{default:s(()=>[a("Install Latest Package")]),_:1})])])])])]),v,e("p",null,[e("a",f,[a("Qubes"),n(i)]),a(" is a free and open-source security-oriented operating system meant for single-user desktop computing. Qubes OS leverages xen-based virtualization to allow for the creation and management of isolated virtual machines (VMs) called qubes. This is valuable for users of high security software like Wasabi Wallet, and especially useful for testers of cutting edge developer branches. There is a separation of the virtual machines running Wasabi on testnet, and those running on mainnet with valuable private keys. If a reviewer compiles a malicious developer branch, then his mainnet private keys are secure in a different qube.")]),e("p",null,[a("This is a step-by-step guide on how to properly compile Wasabi Wallet from source in independent qubes. For tutorials on how to "),e("a",g,[a("download"),n(i)]),a(" and "),e("a",w,[a("install"),n(i)]),a(" Qubes, please see their exhaustive documentation.")]),k,e("p",null,[a("The dependencies to "),n(l,{to:"/using-wasabi/BuildSource.html"},{default:s(()=>[a("compile Wasabi from source")]),_:1}),a(" will be downloaded and installed in a new template VM, which is generated by cloning the Debian template from the "),_,a(" terminal.")]),y,e("p",null,[a("Install "),e("a",x,[a(".NET 8.0 SDK"),n(i)]),a(' for "Build apps" in '),V,a(".")]),M,e("p",null,[n(l,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:s(()=>[a("Download, verify and install")]),_:1}),a(" the latest "),W,a(" package in "),T,a(", then start Wasabi.")]),q,e("p",null,[e("a",S,[a("VirtualBox"),n(i)]),a(' is a lightweight, powerful free and open-source virtualization tool that allows you to run one or more independent operating systems as "virtual machines" (VMs) on your computer. The computer on which VirtualBox is installed is referred to as the "host" machine, and the VMs that are created are referred to as "guests".')]),$,e("p",null,[a("You can download the latest Virtualbox binary for your host OS "),e("a",I,[a("here"),n(i)]),a(".")]),C,B,e("p",null,[a("Detailed instructions for installing VirtualBox on your host computer can be found "),e("a",O,[a("here"),n(i)]),a(".")]),e("p",null,[a("If you run into trouble or have special requirements, the complete User Manual can be found "),e("a",A,[a("here"),n(i)]),a(".")]),N,e("p",null,[a("Detailed instructions for creating various types of virtual machines can be found "),e("a",D,[a("here"),n(i)]),a(".")]),E,L,P,e("ul",null,[e("li",null,[a('Optional, but strongly recommended: Enable the built-in "Guest Additions" functions of Virtualbox. This step will give you a full-sized display, and make the usage of your mouse seamless when switching between different VMs that are running at the same time. Instruction for enabling "Guest Additions" can be found '),e("a",R,[a("here"),n(i)]),a(".")])]),Y,z,e("p",null,[a("Next, the dependencies to "),n(l,{to:"/using-wasabi/BuildSource.html"},{default:s(()=>[a("compile Wasabi from source")]),_:1}),a(" will be downloaded and installed in a new template VM, which can be based on your preferred OS.")]),G,U,F,e("p",null,[a("Install "),e("a",Q,[a(".NET 8.0 SDK"),n(i)]),a(' for "Build apps".')]),j,e("p",null,[a("Instructions on how to create linked clones in VirtualBox can be found "),e("a",K,[a("here"),n(i)]),a(".")]),H,e("p",null,[a("If you are comfortable with "),e("a",X,[a("Git"),n(i)]),a(", you can now have several versions of Wasabi running for testing purposes, at the same time, on the same computer.")]),J,Z,e("p",null,[n(l,{to:"/using-wasabi/InstallPackage.html"},{default:s(()=>[a("Download, verify and install")]),_:1}),a(" the latest "),ee,a(" package in your VM, then start Wasabi.")]),ae])}const oe=u(h,[["render",ne],["__file","WasabiSetupVM.html.vue"]]);export{oe as default};
diff --git a/assets/WhyFinancialPrivacy.html.6e6ac971.js b/assets/WhyFinancialPrivacy.html.a6e0b453.js
similarity index 99%
rename from assets/WhyFinancialPrivacy.html.6e6ac971.js
rename to assets/WhyFinancialPrivacy.html.a6e0b453.js
index 97d1dd98eb..86a040a4e9 100644
--- a/assets/WhyFinancialPrivacy.html.6e6ac971.js
+++ b/assets/WhyFinancialPrivacy.html.a6e0b453.js
@@ -1 +1 @@
-import{_ as r,r as s,o as c,c as l,a as e,b as t,d as o,w as n,e as h}from"./app.a5b7c2b2.js";const d="/InfographicWhyWasabi.png",u={},y=e("h1",{id:"why-financial-privacy-is-especially-important",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-financial-privacy-is-especially-important","aria-hidden":"true"},"#"),t(" Why Financial Privacy is Especially Important")],-1),p=e("blockquote",null,[e("p",null,"The possibility to be anonymous or pseudonymous relies on you not revealing any identifying information about yourself in connection with the bitcoin addresses you use. If you post your bitcoin address on the web, then you're associating that address and any transactions with it with the name you posted under. If you posted under a handle that you haven't associated with your real identity, then you're still pseudonymous. For greater privacy, it's best to use bitcoin addresses only once.")],-1),m={href:"https://bitcointalk.org/index.php?topic=8.msg34#msg34",target:"_blank",rel:"noopener noreferrer"},f=e("p",null,[e("img",{src:d,alt:"Gaining privacy with Wasabi Wallet for Bitcoin transactions",title:"Wasabi Wallet infographic"})],-1),w={class:"table-of-contents"},g=h('
       Why it is important to keep your funds private
      One of the apparent contradictions of Bitcoin is the notion that your transactions can be private but have a public transaction record.
      As a financial system, Bitcoin functions completely differently from the established banking network. Bitcoin allows you to store funds yourself, without the need for a third party and therefore places the burden on you of keeping said funds secure and accessible.
      While opening an account with a traditional bank or other financial institution requires significant cost and effort, creating a Bitcoin wallet is quick and easy to do on your home computer. This speedy process makes it possible to create hundreds of separate wallets if you wish.
      Two aspects —in particular privacy and identity— function very differently with Bitcoin than in the legacy financial system.
       Pseudonyms protect your identity in Bitcoin
      A bank account, PayPal account, or credit card is always tied to a real identity, making it difficult for many people to open one. Bitcoin doesn't require any identity to be part of this network.
      Being able to use the internet anonymously or pseudonymously is the only way for many people to truly be themselves. Hundreds of millions of people around the globe are not accepted in their societies for reasons they cannot control.
      Maintaining an identity with a large following might require paid services such as blogs, logo designs, stock photos, VPNs, or translations. Without the ability to pay for these services anonymously, you would be forced to reveal your true identity in order to maintain your pseudonym situation. This clearly makes no sense and has potentially dangerous ramifications.
       How Bitcoin empowers anonymity
      Bitcoin is an important, empowering technology. Using Bitcoin protects your right to remain anonymous on the internet. It allows anonymous or pseudonymous fundraising. Groups can collectively control Bitcoin accounts and choose to either hide or reveal financial information at will.
      There are many positive reasons for a private and secure banking system like Bitcoin.
      For example, a workers' rights group could raise funds with Bitcoin. The money could be used for servers, flyers, remote helpers… and all without tying any transaction to the real identities of the volunteers.
      Likewise, a domestic abuse victim might use Bitcoin to securely stack away funds to prepare for an independent life.
       Privacy through pseudonymous accounts
      Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.
      In the Bitcoin ecosystem, everyone can see the history and balance of every address, but they cannot necessarily see who controls it. All addresses and transactions are recorded in Bitcoin's publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.
       Threat model
      When considering privacy you need to think about exactly who you're hiding from. You must examine how a hypothetical adversary could spy on you, what kind of information is most important to you and which technology you need to use to protect your privacy. The kind of behaviour needed to protect your privacy therefore depends on your threat model.
      Newcomers to privacy often think that they can simply download some software and all their privacy concerns will be solved. This is not so. Privacy requires a change in behaviour, however slight. For example, imagine if you had a perfectly private internet where who you're communicating with and what you say are completely private. You could still use this to communicate with a social media website to write your real name, upload a selfie and talk about what you're doing right now. Anybody on the internet could view that information so your privacy would be ruined even though you were using perfectly private technology.
      ',21),b={href:"https://www.slideshare.net/grugq/opsec-for-hackers",target:"_blank",rel:"noopener noreferrer"},v=e("p",null,"Most of the time plausible deniability is not good enough because lots of spying methods only need to work on a statistical level (e.g. targeted advertising).",-1);function k(_,B){const a=s("ExternalLinkIcon"),i=s("router-link");return c(),l("div",null,[y,p,e("p",null,[t("By Satoshi Nakamoto in "),e("a",m,[t("How anonymous are bitcoins? - Bitcointalk"),o(a)])]),f,e("nav",w,[e("ul",null,[e("li",null,[o(i,{to:"#why-it-is-important-to-keep-your-funds-private"},{default:n(()=>[t("Why it is important to keep your funds private")]),_:1})]),e("li",null,[o(i,{to:"#pseudonyms-protect-your-identity-in-bitcoin"},{default:n(()=>[t("Pseudonyms protect your identity in Bitcoin")]),_:1})]),e("li",null,[o(i,{to:"#how-bitcoin-empowers-anonymity"},{default:n(()=>[t("How Bitcoin empowers anonymity")]),_:1})]),e("li",null,[o(i,{to:"#privacy-through-pseudonymous-accounts"},{default:n(()=>[t("Privacy through pseudonymous accounts")]),_:1})]),e("li",null,[o(i,{to:"#threat-model"},{default:n(()=>[t("Threat model")]),_:1})])])]),g,e("p",null,[t("For details read the talk "),e("a",b,[t("Opsec for Hackers by grugq"),o(a)]),t(". The talk is aimed mostly at political activists who need privacy from governments, but the advice generally applies to all of us.")]),v])}const T=r(u,[["render",k],["__file","WhyFinancialPrivacy.html.vue"]]);export{T as default};
+import{_ as r,r as s,o as c,c as l,a as e,b as t,d as o,w as n,e as h}from"./app.65e5b6fd.js";const d="/InfographicWhyWasabi.png",u={},y=e("h1",{id:"why-financial-privacy-is-especially-important",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-financial-privacy-is-especially-important","aria-hidden":"true"},"#"),t(" Why Financial Privacy is Especially Important")],-1),p=e("blockquote",null,[e("p",null,"The possibility to be anonymous or pseudonymous relies on you not revealing any identifying information about yourself in connection with the bitcoin addresses you use. If you post your bitcoin address on the web, then you're associating that address and any transactions with it with the name you posted under. If you posted under a handle that you haven't associated with your real identity, then you're still pseudonymous. For greater privacy, it's best to use bitcoin addresses only once.")],-1),m={href:"https://bitcointalk.org/index.php?topic=8.msg34#msg34",target:"_blank",rel:"noopener noreferrer"},f=e("p",null,[e("img",{src:d,alt:"Gaining privacy with Wasabi Wallet for Bitcoin transactions",title:"Wasabi Wallet infographic"})],-1),w={class:"table-of-contents"},g=h('
       Why it is important to keep your funds private
      One of the apparent contradictions of Bitcoin is the notion that your transactions can be private but have a public transaction record.
      As a financial system, Bitcoin functions completely differently from the established banking network. Bitcoin allows you to store funds yourself, without the need for a third party and therefore places the burden on you of keeping said funds secure and accessible.
      While opening an account with a traditional bank or other financial institution requires significant cost and effort, creating a Bitcoin wallet is quick and easy to do on your home computer. This speedy process makes it possible to create hundreds of separate wallets if you wish.
      Two aspects —in particular privacy and identity— function very differently with Bitcoin than in the legacy financial system.
       Pseudonyms protect your identity in Bitcoin
      A bank account, PayPal account, or credit card is always tied to a real identity, making it difficult for many people to open one. Bitcoin doesn't require any identity to be part of this network.
      Being able to use the internet anonymously or pseudonymously is the only way for many people to truly be themselves. Hundreds of millions of people around the globe are not accepted in their societies for reasons they cannot control.
      Maintaining an identity with a large following might require paid services such as blogs, logo designs, stock photos, VPNs, or translations. Without the ability to pay for these services anonymously, you would be forced to reveal your true identity in order to maintain your pseudonym situation. This clearly makes no sense and has potentially dangerous ramifications.
       How Bitcoin empowers anonymity
      Bitcoin is an important, empowering technology. Using Bitcoin protects your right to remain anonymous on the internet. It allows anonymous or pseudonymous fundraising. Groups can collectively control Bitcoin accounts and choose to either hide or reveal financial information at will.
      There are many positive reasons for a private and secure banking system like Bitcoin.
      For example, a workers' rights group could raise funds with Bitcoin. The money could be used for servers, flyers, remote helpers… and all without tying any transaction to the real identities of the volunteers.
      Likewise, a domestic abuse victim might use Bitcoin to securely stack away funds to prepare for an independent life.
       Privacy through pseudonymous accounts
      Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.
      In the Bitcoin ecosystem, everyone can see the history and balance of every address, but they cannot necessarily see who controls it. All addresses and transactions are recorded in Bitcoin's publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.
       Threat model
      When considering privacy you need to think about exactly who you're hiding from. You must examine how a hypothetical adversary could spy on you, what kind of information is most important to you and which technology you need to use to protect your privacy. The kind of behaviour needed to protect your privacy therefore depends on your threat model.
      Newcomers to privacy often think that they can simply download some software and all their privacy concerns will be solved. This is not so. Privacy requires a change in behaviour, however slight. For example, imagine if you had a perfectly private internet where who you're communicating with and what you say are completely private. You could still use this to communicate with a social media website to write your real name, upload a selfie and talk about what you're doing right now. Anybody on the internet could view that information so your privacy would be ruined even though you were using perfectly private technology.
      ',21),b={href:"https://www.slideshare.net/grugq/opsec-for-hackers",target:"_blank",rel:"noopener noreferrer"},v=e("p",null,"Most of the time plausible deniability is not good enough because lots of spying methods only need to work on a statistical level (e.g. targeted advertising).",-1);function k(_,B){const a=s("ExternalLinkIcon"),i=s("router-link");return c(),l("div",null,[y,p,e("p",null,[t("By Satoshi Nakamoto in "),e("a",m,[t("How anonymous are bitcoins? - Bitcointalk"),o(a)])]),f,e("nav",w,[e("ul",null,[e("li",null,[o(i,{to:"#why-it-is-important-to-keep-your-funds-private"},{default:n(()=>[t("Why it is important to keep your funds private")]),_:1})]),e("li",null,[o(i,{to:"#pseudonyms-protect-your-identity-in-bitcoin"},{default:n(()=>[t("Pseudonyms protect your identity in Bitcoin")]),_:1})]),e("li",null,[o(i,{to:"#how-bitcoin-empowers-anonymity"},{default:n(()=>[t("How Bitcoin empowers anonymity")]),_:1})]),e("li",null,[o(i,{to:"#privacy-through-pseudonymous-accounts"},{default:n(()=>[t("Privacy through pseudonymous accounts")]),_:1})]),e("li",null,[o(i,{to:"#threat-model"},{default:n(()=>[t("Threat model")]),_:1})])])]),g,e("p",null,[t("For details read the talk "),e("a",b,[t("Opsec for Hackers by grugq"),o(a)]),t(". The talk is aimed mostly at political activists who need privacy from governments, but the advice generally applies to all of us.")]),v])}const T=r(u,[["render",k],["__file","WhyFinancialPrivacy.html.vue"]]);export{T as default};
diff --git a/assets/WhyPrivacyImportant.html.70fbf5db.js b/assets/WhyPrivacyImportant.html.4811188a.js
similarity index 99%
rename from assets/WhyPrivacyImportant.html.70fbf5db.js
rename to assets/WhyPrivacyImportant.html.4811188a.js
index 36efb4738b..8b91e065a7 100644
--- a/assets/WhyPrivacyImportant.html.70fbf5db.js
+++ b/assets/WhyPrivacyImportant.html.4811188a.js
@@ -1 +1 @@
-import{_ as s}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as h,r as i,o as l,c as d,a as e,d as o,w as r,b as t}from"./app.a5b7c2b2.js";const u={},c=e("h1",{id:"why-privacy-is-important",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-privacy-is-important","aria-hidden":"true"},"#"),t(" Why Privacy is Important")],-1),p=e("blockquote",null,[e("p",null,"It's not that I have something to hide. It's that I have nothing to share.")],-1),y=e("p",null,"Privacy is the selective revealing of your Self to your peers. You have many thoughts in your mind which you choose to never tell anyone, and many of your actions are never witnessed by another person. The ability to keep a secret is an essential part of the human experience.",-1),_=e("ul",null,[e("li",null,"Why do you draw the curtains at night?"),e("li",null,"Why do you close the door when in the shower?"),e("li",null,"Why do you send your love letters only to your spouse?")],-1),w={href:"https://youtu.be/laem7G6LPAM",target:"_blank",rel:"noopener noreferrer"},m=e("img",{src:s,alt:"Watch the video"},null,-1),g=e("p",null,"Economic trade of goods and services is based on mutual beneficial voluntary action. But when an outside authority demands that the peers reveal the details of their exchange, then they must beg for permission of every act. Yet individuals can use the tools of self-defense at their disposal to regain their sovereignty.",-1),f=e("blockquote",null,[e("p",null,"Without financial privacy, there is no human dignity.")],-1),v={class:"table-of-contents"},b=e("h2",{id:"privacy-i-don-t-have-anything-to-hide",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-i-don-t-have-anything-to-hide","aria-hidden":"true"},"#"),t(" Privacy? I don't have anything to hide")],-1),k={href:"https://www.ted.com/talks/glenn_greenwald_why_privacy_matters",target:"_blank",rel:"noopener noreferrer"},I={href:"https://github.com/cryptoseb/CryptoPaper#let-me-explain-further",target:"_blank",rel:"noopener noreferrer"},x=e("h2",{id:"read-also",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#read-also","aria-hidden":"true"},"#"),t(" Read also")],-1),W={href:"https://en.wikipedia.org/wiki/Nothing_to_hide_argument",target:"_blank",rel:"noopener noreferrer"},q={href:"https://www.reddit.com/r/privacy/comments/3hynvp/how_do_you_counter_the_i_have_nothing_to_hide/",target:"_blank",rel:"noopener noreferrer"},P={href:"https://papers.ssrn.com/sol3/papers.cfm?abstract_id=998565",target:"_blank",rel:"noopener noreferrer"},T=e("h2",{id:"quotes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#quotes","aria-hidden":"true"},"#"),t(" Quotes")],-1),N={href:"https://www.reddit.com/r/IAmA/comments/36ru89/just_days_left_to_kill_mass_surveillance_under/crglgh2",target:"_blank",rel:"noopener noreferrer"},E={href:"https://www.theguardian.com/world/2013/jun/09/nsa-whistleblower-edward-snowden-why",target:"_blank",rel:"noopener noreferrer"},G={href:"https://www.huffingtonpost.com/2014/06/20/glenn-greenwald-privacy_n_5509704.html",target:"_blank",rel:"noopener noreferrer"},j=e("iframe",{src:"https://anchor.fm/podcast-8f267c0/embed/episodes/Privacy-Matters-with-Max-Hillebrand-BEC008-e3e0qt/a-abhd5q",height:"102px",width:"400px",frameborder:"0",scrolling:"no"},null,-1);function A(S,B){const n=i("ExternalLinkIcon"),a=i("router-link");return l(),d("div",null,[c,p,y,_,e("p",null,[e("a",w,[m,o(n)])]),g,f,e("nav",v,[e("ul",null,[e("li",null,[o(a,{to:"#privacy-i-don-t-have-anything-to-hide"},{default:r(()=>[t("Privacy? I don't have anything to hide")]),_:1})]),e("li",null,[o(a,{to:"#read-also"},{default:r(()=>[t("Read also")]),_:1})]),e("li",null,[o(a,{to:"#quotes"},{default:r(()=>[t("Quotes")]),_:1})])])]),b,e("blockquote",null,[e("p",null,[t(`Over the last 16 months, as I've debated this issue around the world, every single time somebody has said to me, "I don't really worry about invasions of privacy because I don't have anything to hide." I always say the same thing to them. I get out a pen, I write down my email address. I say, "Here's my email address. What I want you to do when you get home is email me the passwords to all of your email accounts, not just the nice, respectable work one in your name, but all of them, because I want to be able to just troll through what it is you're doing online, read what I want to read and publish whatever I find interesting. After all, if you're not a bad person, if you're doing nothing wrong, you should have nothing to hide." Not a single person has taken me up on that offer. - Glenn Greenwald in `),e("a",k,[t("Why privacy matters - TED Talk"),o(n)])])]),e("blockquote",null,[e("p",null,[t("The primary reason for window curtains in our house, is to stop people from being able to see in. The reason we don’t want them to see in is because we consider much of what we do inside our homes to be private. Whether that be having dinner at the table, watching a movie with your kids, or even engaging in intimate or sexual acts with your partner. None of these things are illegal by any means but even knowing this, we still keep the curtains and blinds on our windows. We clearly have this strong desire for privacy when it comes to our personal life and the public. - Joshua in "),e("a",I,[t("The Crypto Paper"),o(n)])])]),x,e("ul",null,[e("li",null,[e("a",W,[t("Nothing to hide argument (Wikipedia)"),o(n)])]),e("li",null,[e("a",q,[t('How do you counter the "I have nothing to hide?" argument? (reddit.com)'),o(n)])]),e("li",null,[e("a",P,[t("'I've Got Nothing to Hide' and Other Misunderstandings of Privacy (Daniel J. Solove - San Diego Law Review)"),o(n)])])]),T,e("blockquote",null,[e("p",null,[t("Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. - Edward Snowden on "),e("a",N,[t("Reddit"),o(n)])])]),e("blockquote",null,[e("p",null,[t("The NSA has built an infrastructure that allows it to intercept almost everything. With this capability, the vast majority of human communications are automatically ingested without targeting. If I wanted to see your emails or your wife's phone, all I have to do is use intercepts. I can get your emails, passwords, phone records, credit cards. I don't want to live in a society that does these sort of things... I do not want to live in a world where everything I do and say is recorded. That is not something I am willing to support or live under. - Edward Snowden in "),e("a",E,[t("The Guardian"),o(n)])])]),e("blockquote",null,[e("p",null,[t("We all need places where we can go to explore without the judgmental eyes of other people being cast upon us, only in a realm where we're not being watched can we really test the limits of who we want to be. It's really in the private realm where dissent, creativity and personal exploration lie. - Glenn Greenwald in "),e("a",G,[t("Huffington Post"),o(n)])])]),j])}const L=h(u,[["render",A],["__file","WhyPrivacyImportant.html.vue"]]);export{L as default};
+import{_ as s}from"./Logo_without_text_with_bg_dark_with_yt.82339e58.js";import{_ as h,r as i,o as l,c as d,a as e,d as o,w as r,b as t}from"./app.65e5b6fd.js";const u={},c=e("h1",{id:"why-privacy-is-important",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#why-privacy-is-important","aria-hidden":"true"},"#"),t(" Why Privacy is Important")],-1),p=e("blockquote",null,[e("p",null,"It's not that I have something to hide. It's that I have nothing to share.")],-1),y=e("p",null,"Privacy is the selective revealing of your Self to your peers. You have many thoughts in your mind which you choose to never tell anyone, and many of your actions are never witnessed by another person. The ability to keep a secret is an essential part of the human experience.",-1),_=e("ul",null,[e("li",null,"Why do you draw the curtains at night?"),e("li",null,"Why do you close the door when in the shower?"),e("li",null,"Why do you send your love letters only to your spouse?")],-1),w={href:"https://youtu.be/laem7G6LPAM",target:"_blank",rel:"noopener noreferrer"},m=e("img",{src:s,alt:"Watch the video"},null,-1),g=e("p",null,"Economic trade of goods and services is based on mutual beneficial voluntary action. But when an outside authority demands that the peers reveal the details of their exchange, then they must beg for permission of every act. Yet individuals can use the tools of self-defense at their disposal to regain their sovereignty.",-1),f=e("blockquote",null,[e("p",null,"Without financial privacy, there is no human dignity.")],-1),v={class:"table-of-contents"},b=e("h2",{id:"privacy-i-don-t-have-anything-to-hide",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#privacy-i-don-t-have-anything-to-hide","aria-hidden":"true"},"#"),t(" Privacy? I don't have anything to hide")],-1),k={href:"https://www.ted.com/talks/glenn_greenwald_why_privacy_matters",target:"_blank",rel:"noopener noreferrer"},I={href:"https://github.com/cryptoseb/CryptoPaper#let-me-explain-further",target:"_blank",rel:"noopener noreferrer"},x=e("h2",{id:"read-also",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#read-also","aria-hidden":"true"},"#"),t(" Read also")],-1),W={href:"https://en.wikipedia.org/wiki/Nothing_to_hide_argument",target:"_blank",rel:"noopener noreferrer"},q={href:"https://www.reddit.com/r/privacy/comments/3hynvp/how_do_you_counter_the_i_have_nothing_to_hide/",target:"_blank",rel:"noopener noreferrer"},P={href:"https://papers.ssrn.com/sol3/papers.cfm?abstract_id=998565",target:"_blank",rel:"noopener noreferrer"},T=e("h2",{id:"quotes",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#quotes","aria-hidden":"true"},"#"),t(" Quotes")],-1),N={href:"https://www.reddit.com/r/IAmA/comments/36ru89/just_days_left_to_kill_mass_surveillance_under/crglgh2",target:"_blank",rel:"noopener noreferrer"},E={href:"https://www.theguardian.com/world/2013/jun/09/nsa-whistleblower-edward-snowden-why",target:"_blank",rel:"noopener noreferrer"},G={href:"https://www.huffingtonpost.com/2014/06/20/glenn-greenwald-privacy_n_5509704.html",target:"_blank",rel:"noopener noreferrer"},j=e("iframe",{src:"https://anchor.fm/podcast-8f267c0/embed/episodes/Privacy-Matters-with-Max-Hillebrand-BEC008-e3e0qt/a-abhd5q",height:"102px",width:"400px",frameborder:"0",scrolling:"no"},null,-1);function A(S,B){const n=i("ExternalLinkIcon"),a=i("router-link");return l(),d("div",null,[c,p,y,_,e("p",null,[e("a",w,[m,o(n)])]),g,f,e("nav",v,[e("ul",null,[e("li",null,[o(a,{to:"#privacy-i-don-t-have-anything-to-hide"},{default:r(()=>[t("Privacy? I don't have anything to hide")]),_:1})]),e("li",null,[o(a,{to:"#read-also"},{default:r(()=>[t("Read also")]),_:1})]),e("li",null,[o(a,{to:"#quotes"},{default:r(()=>[t("Quotes")]),_:1})])])]),b,e("blockquote",null,[e("p",null,[t(`Over the last 16 months, as I've debated this issue around the world, every single time somebody has said to me, "I don't really worry about invasions of privacy because I don't have anything to hide." I always say the same thing to them. I get out a pen, I write down my email address. I say, "Here's my email address. What I want you to do when you get home is email me the passwords to all of your email accounts, not just the nice, respectable work one in your name, but all of them, because I want to be able to just troll through what it is you're doing online, read what I want to read and publish whatever I find interesting. After all, if you're not a bad person, if you're doing nothing wrong, you should have nothing to hide." Not a single person has taken me up on that offer. - Glenn Greenwald in `),e("a",k,[t("Why privacy matters - TED Talk"),o(n)])])]),e("blockquote",null,[e("p",null,[t("The primary reason for window curtains in our house, is to stop people from being able to see in. The reason we don’t want them to see in is because we consider much of what we do inside our homes to be private. Whether that be having dinner at the table, watching a movie with your kids, or even engaging in intimate or sexual acts with your partner. None of these things are illegal by any means but even knowing this, we still keep the curtains and blinds on our windows. We clearly have this strong desire for privacy when it comes to our personal life and the public. - Joshua in "),e("a",I,[t("The Crypto Paper"),o(n)])])]),x,e("ul",null,[e("li",null,[e("a",W,[t("Nothing to hide argument (Wikipedia)"),o(n)])]),e("li",null,[e("a",q,[t('How do you counter the "I have nothing to hide?" argument? (reddit.com)'),o(n)])]),e("li",null,[e("a",P,[t("'I've Got Nothing to Hide' and Other Misunderstandings of Privacy (Daniel J. Solove - San Diego Law Review)"),o(n)])])]),T,e("blockquote",null,[e("p",null,[t("Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. - Edward Snowden on "),e("a",N,[t("Reddit"),o(n)])])]),e("blockquote",null,[e("p",null,[t("The NSA has built an infrastructure that allows it to intercept almost everything. With this capability, the vast majority of human communications are automatically ingested without targeting. If I wanted to see your emails or your wife's phone, all I have to do is use intercepts. I can get your emails, passwords, phone records, credit cards. I don't want to live in a society that does these sort of things... I do not want to live in a world where everything I do and say is recorded. That is not something I am willing to support or live under. - Edward Snowden in "),e("a",E,[t("The Guardian"),o(n)])])]),e("blockquote",null,[e("p",null,[t("We all need places where we can go to explore without the judgmental eyes of other people being cast upon us, only in a realm where we're not being watched can we really test the limits of who we want to be. It's really in the private realm where dissent, creativity and personal exploration lie. - Glenn Greenwald in "),e("a",G,[t("Huffington Post"),o(n)])])]),j])}const L=h(u,[["render",A],["__file","WhyPrivacyImportant.html.vue"]]);export{L as default};
diff --git a/assets/app.a5b7c2b2.js b/assets/app.65e5b6fd.js
similarity index 98%
rename from assets/app.a5b7c2b2.js
rename to assets/app.65e5b6fd.js
index b7fe69bae4..9698fc6414 100644
--- a/assets/app.a5b7c2b2.js
+++ b/assets/app.65e5b6fd.js
@@ -1,4 +1,4 @@
-const Na="modulepreload",za=function(e){return"/"+e},Vl={},x=function(t,n,i){return!n||n.length===0?t():Promise.all(n.map(l=>{if(l=za(l),l in Vl)return;Vl[l]=!0;const s=l.endsWith(".css"),o=s?'[rel="stylesheet"]':"";if(document.querySelector(`link[href="${l}"]${o}`))return;const a=document.createElement("link");if(a.rel=s?"stylesheet":Na,s||(a.as="script",a.crossOrigin=""),a.href=l,document.head.appendChild(a),s)return new Promise((r,u)=>{a.addEventListener("load",r),a.addEventListener("error",()=>u(new Error(`Unable to preload CSS for ${l}`)))})})).then(()=>t())},Va={"v-8daa1a0e":()=>x(()=>import("./index.html.efbdb3bf.js"),[]).then(({data:e})=>e),"v-5a6b3f40":()=>x(()=>import("./FAQ-Contribution.html.a5662063.js"),[]).then(({data:e})=>e),"v-6b95acd0":()=>x(()=>import("./FAQ-GeneralBitcoinPrivacy.html.f2cc196a.js"),[]).then(({data:e})=>e),"v-dbdf1f14":()=>x(()=>import("./FAQ-Installation.html.c6a7fa06.js"),[]).then(({data:e})=>e),"v-1a6aa296":()=>x(()=>import("./FAQ-Introduction.html.51f9b016.js"),[]).then(({data:e})=>e),"v-48b5cdc8":()=>x(()=>import("./FAQ-UseWasabi.html.1cefe63f.js"),[]).then(({data:e})=>e),"v-74379e72":()=>x(()=>import("./index.html.38c9d31b.js"),[]).then(({data:e})=>e),"v-daad2d5a":()=>x(()=>import("./ContributionChecklist.html.f454f51d.js"),[]).then(({data:e})=>e),"v-50472b68":()=>x(()=>import("./LICENSE.html.cca271db.js"),[]).then(({data:e})=>e),"v-1488a610":()=>x(()=>import("./index.html.51b0c8cf.js"),[]).then(({data:e})=>e),"v-7a003569":()=>x(()=>import("./Security.html.68fe1c05.js"),[]).then(({data:e})=>e),"v-ccdc4da0":()=>x(()=>import("./index.html.11c955f3.js"),[]).then(({data:e})=>e),"v-6fa52768":()=>x(()=>import("./Glossary-GeneralBitcoin.html.af0d3606.js"),[]).then(({data:e})=>e),"v-ceb6ce6e":()=>x(()=>import("./Glossary-PrivacyWasabi.html.ea52aaf7.js"),[]).then(({data:e})=>e),"v-338f4ef8":()=>x(()=>import("./index.html.f476e799.js"),[]).then(({data:e})=>e),"v-93f154be":()=>x(()=>import("./BIPs.html.d3a69602.js"),[]).then(({data:e})=>e),"v-9880f756":()=>x(()=>import("./BackupBestPractices.html.76bd62a5.js"),[]).then(({data:e})=>e),"v-35466110":()=>x(()=>import("./BitcoinFullNode.html.7483e163.js"),[]).then(({data:e})=>e),"v-9f999a04":()=>x(()=>import("./BuildSource.html.a974ba78.js"),[]).then(({data:e})=>e),"v-c0f49ad6":()=>x(()=>import("./ChangeCoins.html.c35ce720.js"),[]).then(({data:e})=>e),"v-9f951f20":()=>x(()=>import("./CoinJoin.html.25ac80dc.js"),[]).then(({data:e})=>e),"v-6ba5ff68":()=>x(()=>import("./ColdWasabi.html.220be9ba.js"),[]).then(({data:e})=>e),"v-dd3fd132":()=>x(()=>import("./Daemon.html.9923648f.js"),[]).then(({data:e})=>e),"v-53e5ec6f":()=>x(()=>import("./DeterministicBuild.html.0565f895.js"),[]).then(({data:e})=>e),"v-5d4dd2b1":()=>x(()=>import("./DiscreetMode.html.c246eee4.js"),[]).then(({data:e})=>e),"v-633fd810":()=>x(()=>import("./ELI5.html.3d49d084.js"),[]).then(({data:e})=>e),"v-18287a20":()=>x(()=>import("./InstallPackage.html.a6d7056b.js"),[]).then(({data:e})=>e),"v-2206b16e":()=>x(()=>import("./PasswordBestPractices.html.cb13edf6.js"),[]).then(({data:e})=>e),"v-10ab876a":()=>x(()=>import("./PasswordFinder.html.a9ebb851.js"),[]).then(({data:e})=>e),"v-28d891d5":()=>x(()=>import("./PayJoin.html.b30eddd3.js"),[]).then(({data:e})=>e),"v-019de88e":()=>x(()=>import("./index.html.5550cce2.js"),[]).then(({data:e})=>e),"v-cb675e7c":()=>x(()=>import("./RPC.html.9aba61fe.js"),[]).then(({data:e})=>e),"v-61c4fb84":()=>x(()=>import("./Receive.html.f15c1a36.js"),[]).then(({data:e})=>e),"v-34d39e44":()=>x(()=>import("./RestoreElectrum.html.15cce134.js"),[]).then(({data:e})=>e),"v-0495dd63":()=>x(()=>import("./Send.html.41ed2b96.js"),[]).then(({data:e})=>e),"v-03767b9c":()=>x(()=>import("./Testnet.html.aea4daa1.js"),[]).then(({data:e})=>e),"v-e69d74cc":()=>x(()=>import("./WalletGeneration.html.2062fbaf.js"),[]).then(({data:e})=>e),"v-74a0b14c":()=>x(()=>import("./WalletLoad.html.b25174fa.js"),[]).then(({data:e})=>e),"v-059a5106":()=>x(()=>import("./WalletRecovery.html.310647b0.js"),[]).then(({data:e})=>e),"v-abde19dc":()=>x(()=>import("./WasabiSetupVM.html.0044e6e5.js"),[]).then(({data:e})=>e),"v-91cac2f2":()=>x(()=>import("./AddressReuse.html.260e762c.js"),[]).then(({data:e})=>e),"v-e8d6a56e":()=>x(()=>import("./Coins.html.b6fb2be3.js"),[]).then(({data:e})=>e),"v-6b334fc0":()=>x(()=>import("./LegalConcern.html.900695db.js"),[]).then(({data:e})=>e),"v-e10ef9ce":()=>x(()=>import("./NetworkLevelPrivacy.html.f0783852.js"),[]).then(({data:e})=>e),"v-40d3d192":()=>x(()=>import("./index.html.5fa14c07.js"),[]).then(({data:e})=>e),"v-1038df57":()=>x(()=>import("./TransactionGraph.html.0e9dd3d6.js"),[]).then(({data:e})=>e),"v-35a4d9e3":()=>x(()=>import("./TransactionSurveillanceCompanies.html.388b9cd4.js"),[]).then(({data:e})=>e),"v-0b19ce44":()=>x(()=>import("./WhyFinancialPrivacy.html.d449301d.js"),[]).then(({data:e})=>e),"v-19b5df2e":()=>x(()=>import("./WhyPrivacyImportant.html.3c610b4f.js"),[]).then(({data:e})=>e),"v-3706649a":()=>x(()=>import("./404.html.d2dc3323.js"),[]).then(({data:e})=>e)};function ul(e,t){const n=Object.create(null),i=e.split(",");for(let l=0;l!!n[l.toLowerCase()]:l=>!!n[l]}function Hn(e){if(te(e)){const t={};for(let n=0;n{if(n){const i=n.split(qa);i.length>1&&(t[i[0].trim()]=i[1].trim())}}),t}function qe(e){let t="";if(ve(e))t=e;else if(te(e))for(let n=0;nve(e)?e:e==null?"":te(e)||Ie(e)&&(e.toString===uo||!ae(e.toString))?JSON.stringify(e,ao,2):String(e),ao=(e,t)=>t&&t.__v_isRef?ao(e,t.value):on(t)?{[`Map(${t.size})`]:[...t.entries()].reduce((n,[i,l])=>(n[`${i} =>`]=l,n),{})}:ro(t)?{[`Set(${t.size})`]:[...t.values()]}:Ie(t)&&!te(t)&&!ho(t)?String(t):t,Pe={},sn=[],st=()=>{},Ya=()=>!1,Xa=/^on[^a-z]/,jn=e=>Xa.test(e),dl=e=>e.startsWith("onUpdate:"),je=Object.assign,hl=(e,t)=>{const n=e.indexOf(t);n>-1&&e.splice(n,1)},Za=Object.prototype.hasOwnProperty,pe=(e,t)=>Za.call(e,t),te=Array.isArray,on=e=>vi(e)==="[object Map]",ro=e=>vi(e)==="[object Set]",ae=e=>typeof e=="function",ve=e=>typeof e=="string",fl=e=>typeof e=="symbol",Ie=e=>e!==null&&typeof e=="object",co=e=>Ie(e)&&ae(e.then)&&ae(e.catch),uo=Object.prototype.toString,vi=e=>uo.call(e),er=e=>vi(e).slice(8,-1),ho=e=>vi(e)==="[object Object]",pl=e=>ve(e)&&e!=="NaN"&&e[0]!=="-"&&""+parseInt(e,10)===e,Pn=ul(",key,ref,ref_for,ref_key,onVnodeBeforeMount,onVnodeMounted,onVnodeBeforeUpdate,onVnodeUpdated,onVnodeBeforeUnmount,onVnodeUnmounted"),bi=e=>{const t=Object.create(null);return n=>t[n]||(t[n]=e(n))},tr=/-(\w)/g,dt=bi(e=>e.replace(tr,(t,n)=>n?n.toUpperCase():"")),nr=/\B([A-Z])/g,Yt=bi(e=>e.replace(nr,"-$1").toLowerCase()),wi=bi(e=>e.charAt(0).toUpperCase()+e.slice(1)),Si=bi(e=>e?`on${wi(e)}`:""),Sn=(e,t)=>!Object.is(e,t),Ri=(e,t)=>{for(let n=0;n{Object.defineProperty(e,t,{configurable:!0,enumerable:!1,value:n})},gl=e=>{const t=parseFloat(e);return isNaN(t)?e:t};let Ul;const ir=()=>Ul||(Ul=typeof globalThis<"u"?globalThis:typeof self<"u"?self:typeof window<"u"?window:typeof global<"u"?global:{});let Ge;class lr{constructor(t=!1){this.detached=t,this.active=!0,this.effects=[],this.cleanups=[],this.parent=Ge,!t&&Ge&&(this.index=(Ge.scopes||(Ge.scopes=[])).push(this)-1)}run(t){if(this.active){const n=Ge;try{return Ge=this,t()}finally{Ge=n}}}on(){Ge=this}off(){Ge=this.parent}stop(t){if(this.active){let n,i;for(n=0,i=this.effects.length;n{const t=new Set(e);return t.w=0,t.n=0,t},fo=e=>(e.w&Tt)>0,po=e=>(e.n&Tt)>0,rr=({deps:e})=>{if(e.length)for(let t=0;t{const{deps:t}=e;if(t.length){let n=0;for(let i=0;i{(c==="length"||c>=r)&&a.push(u)})}else switch(n!==void 0&&a.push(o.get(n)),t){case"add":te(e)?pl(n)&&a.push(o.get("length")):(a.push(o.get(Qt)),on(e)&&a.push(o.get(Qi)));break;case"delete":te(e)||(a.push(o.get(Qt)),on(e)&&a.push(o.get(Qi)));break;case"set":on(e)&&a.push(o.get(Qt));break}if(a.length===1)a[0]&&Gi(a[0]);else{const r=[];for(const u of a)u&&r.push(...u);Gi(ml(r))}}function Gi(e,t){const n=te(e)?e:[...e];for(const i of n)i.computed&&Kl(i);for(const i of n)i.computed||Kl(i)}function Kl(e,t){(e!==it||e.allowRecurse)&&(e.scheduler?e.scheduler():e.run())}const ur=ul("__proto__,__v_isRef,__isVue"),vo=new Set(Object.getOwnPropertyNames(Symbol).filter(e=>e!=="arguments"&&e!=="caller").map(e=>Symbol[e]).filter(fl)),dr=bl(),hr=bl(!1,!0),fr=bl(!0),Ql=pr();function pr(){const e={};return["includes","indexOf","lastIndexOf"].forEach(t=>{e[t]=function(...n){const i=me(this);for(let s=0,o=this.length;s{e[t]=function(...n){mn();const i=me(this)[t].apply(this,n);return vn(),i}}),e}function bl(e=!1,t=!1){return function(i,l,s){if(l==="__v_isReactive")return!e;if(l==="__v_isReadonly")return e;if(l==="__v_isShallow")return t;if(l==="__v_raw"&&s===(e?t?Tr:ko:t?_o:yo).get(i))return i;const o=te(i);if(!e&&o&&pe(Ql,l))return Reflect.get(Ql,l,s);const a=Reflect.get(i,l,s);return(fl(l)?vo.has(l):ur(l))||(e||Ye(i,"get",l),t)?a:Fe(a)?o&&pl(l)?a:a.value:Ie(a)?e?_l(a):bn(a):a}}const gr=bo(),mr=bo(!0);function bo(e=!1){return function(n,i,l,s){let o=n[i];if(un(o)&&Fe(o)&&!Fe(l))return!1;if(!e&&(!si(l)&&!un(l)&&(o=me(o),l=me(l)),!te(n)&&Fe(o)&&!Fe(l)))return o.value=l,!0;const a=te(n)&&pl(i)?Number(i)e,yi=e=>Reflect.getPrototypeOf(e);function Un(e,t,n=!1,i=!1){e=e.__v_raw;const l=me(e),s=me(t);n||(t!==s&&Ye(l,"get",t),Ye(l,"get",s));const{has:o}=yi(l),a=i?wl:n?El:Rn;if(o.call(l,t))return a(e.get(t));if(o.call(l,s))return a(e.get(s));e!==l&&e.get(t)}function qn(e,t=!1){const n=this.__v_raw,i=me(n),l=me(e);return t||(e!==l&&Ye(i,"has",e),Ye(i,"has",l)),e===l?n.has(e):n.has(e)||n.has(l)}function Kn(e,t=!1){return e=e.__v_raw,!t&&Ye(me(e),"iterate",Qt),Reflect.get(e,"size",e)}function Gl(e){e=me(e);const t=me(this);return yi(t).has.call(t,e)||(t.add(e),vt(t,"add",e,e)),this}function Jl(e,t){t=me(t);const n=me(this),{has:i,get:l}=yi(n);let s=i.call(n,e);s||(e=me(e),s=i.call(n,e));const o=l.call(n,e);return n.set(e,t),s?Sn(t,o)&&vt(n,"set",e,t):vt(n,"add",e,t),this}function Yl(e){const t=me(this),{has:n,get:i}=yi(t);let l=n.call(t,e);l||(e=me(e),l=n.call(t,e)),i&&i.call(t,e);const s=t.delete(e);return l&&vt(t,"delete",e,void 0),s}function Xl(){const e=me(this),t=e.size!==0,n=e.clear();return t&&vt(e,"clear",void 0,void 0),n}function Qn(e,t){return function(i,l){const s=this,o=s.__v_raw,a=me(o),r=t?wl:e?El:Rn;return!e&&Ye(a,"iterate",Qt),o.forEach((u,c)=>i.call(l,r(u),r(c),s))}}function Gn(e,t,n){return function(...i){const l=this.__v_raw,s=me(l),o=on(s),a=e==="entries"||e===Symbol.iterator&&o,r=e==="keys"&&o,u=l[e](...i),c=n?wl:t?El:Rn;return!t&&Ye(s,"iterate",r?Qi:Qt),{next(){const{value:h,done:f}=u.next();return f?{value:h,done:f}:{value:a?[c(h[0]),c(h[1])]:c(h),done:f}},[Symbol.iterator](){return this}}}}function _t(e){return function(...t){return e==="delete"?!1:this}}function kr(){const e={get(s){return Un(this,s)},get size(){return Kn(this)},has:qn,add:Gl,set:Jl,delete:Yl,clear:Xl,forEach:Qn(!1,!1)},t={get(s){return Un(this,s,!1,!0)},get size(){return Kn(this)},has:qn,add:Gl,set:Jl,delete:Yl,clear:Xl,forEach:Qn(!1,!0)},n={get(s){return Un(this,s,!0)},get size(){return Kn(this,!0)},has(s){return qn.call(this,s,!0)},add:_t("add"),set:_t("set"),delete:_t("delete"),clear:_t("clear"),forEach:Qn(!0,!1)},i={get(s){return Un(this,s,!0,!0)},get size(){return Kn(this,!0)},has(s){return qn.call(this,s,!0)},add:_t("add"),set:_t("set"),delete:_t("delete"),clear:_t("clear"),forEach:Qn(!0,!0)};return["keys","values","entries",Symbol.iterator].forEach(s=>{e[s]=Gn(s,!1,!1),n[s]=Gn(s,!0,!1),t[s]=Gn(s,!1,!0),i[s]=Gn(s,!0,!0)}),[e,n,t,i]}const[Er,Cr,Pr,Ir]=kr();function yl(e,t){const n=t?e?Ir:Pr:e?Cr:Er;return(i,l,s)=>l==="__v_isReactive"?!e:l==="__v_isReadonly"?e:l==="__v_raw"?i:Reflect.get(pe(n,l)&&l in i?n:i,l,s)}const Lr={get:yl(!1,!1)},xr={get:yl(!1,!0)},Ar={get:yl(!0,!1)},yo=new WeakMap,_o=new WeakMap,ko=new WeakMap,Tr=new WeakMap;function Sr(e){switch(e){case"Object":case"Array":return 1;case"Map":case"Set":case"WeakMap":case"WeakSet":return 2;default:return 0}}function Rr(e){return e.__v_skip||!Object.isExtensible(e)?0:Sr(er(e))}function bn(e){return un(e)?e:kl(e,!1,wo,Lr,yo)}function Or(e){return kl(e,!1,_r,xr,_o)}function _l(e){return kl(e,!0,yr,Ar,ko)}function kl(e,t,n,i,l){if(!Ie(e)||e.__v_raw&&!(t&&e.__v_isReactive))return e;const s=l.get(e);if(s)return s;const o=Rr(e);if(o===0)return e;const a=new Proxy(e,o===2?i:n);return l.set(e,a),a}function an(e){return un(e)?an(e.__v_raw):!!(e&&e.__v_isReactive)}function un(e){return!!(e&&e.__v_isReadonly)}function si(e){return!!(e&&e.__v_isShallow)}function Eo(e){return an(e)||un(e)}function me(e){const t=e&&e.__v_raw;return t?me(t):e}function Co(e){return li(e,"__v_skip",!0),e}const Rn=e=>Ie(e)?bn(e):e,El=e=>Ie(e)?_l(e):e;function Po(e){Lt&&it&&(e=me(e),mo(e.dep||(e.dep=ml())))}function Io(e,t){e=me(e),e.dep&&Gi(e.dep)}function Fe(e){return!!(e&&e.__v_isRef===!0)}function be(e){return xo(e,!1)}function Lo(e){return xo(e,!0)}function xo(e,t){return Fe(e)?e:new Wr(e,t)}class Wr{constructor(t,n){this.__v_isShallow=n,this.dep=void 0,this.__v_isRef=!0,this._rawValue=n?t:me(t),this._value=n?t:Rn(t)}get value(){return Po(this),this._value}set value(t){const n=this.__v_isShallow||si(t)||un(t);t=n?t:me(t),Sn(t,this._rawValue)&&(this._rawValue=t,this._value=n?t:Rn(t),Io(this))}}function S(e){return Fe(e)?e.value:e}const Fr={get:(e,t,n)=>S(Reflect.get(e,t,n)),set:(e,t,n,i)=>{const l=e[t];return Fe(l)&&!Fe(n)?(l.value=n,!0):Reflect.set(e,t,n,i)}};function Ao(e){return an(e)?e:new Proxy(e,Fr)}function _i(e){const t=te(e)?new Array(e.length):{};for(const n in e)t[n]=Hr(e,n);return t}class Dr{constructor(t,n,i){this._object=t,this._key=n,this._defaultValue=i,this.__v_isRef=!0}get value(){const t=this._object[this._key];return t===void 0?this._defaultValue:t}set value(t){this._object[this._key]=t}}function Hr(e,t,n){const i=e[t];return Fe(i)?i:new Dr(e,t,n)}var To;class jr{constructor(t,n,i,l){this._setter=n,this.dep=void 0,this.__v_isRef=!0,this[To]=!1,this._dirty=!0,this.effect=new vl(t,()=>{this._dirty||(this._dirty=!0,Io(this))}),this.effect.computed=this,this.effect.active=this._cacheable=!l,this.__v_isReadonly=i}get value(){const t=me(this);return Po(t),(t._dirty||!t._cacheable)&&(t._dirty=!1,t._value=t.effect.run()),t._value}set value(t){this._setter(t)}}To="__v_isReadonly";function Br(e,t,n=!1){let i,l;const s=ae(e);return s?(i=e,l=st):(i=e.get,l=e.set),new jr(i,l,s||!l,n)}function xt(e,t,n,i){let l;try{l=i?e(...i):e()}catch(s){Bn(s,t,n)}return l}function et(e,t,n,i){if(ae(e)){const s=xt(e,t,n,i);return s&&co(s)&&s.catch(o=>{Bn(o,t,n)}),s}const l=[];for(let s=0;s>>1;Wn(Me[i])ct&&Me.splice(t,1)}function zr(e){te(e)?rn.push(...e):(!pt||!pt.includes(e,e.allowRecurse?Nt+1:Nt))&&rn.push(e),Ro()}function Zl(e,t=On?ct+1:0){for(;tWn(n)-Wn(i)),Nt=0;Nte.id==null?1/0:e.id,Vr=(e,t)=>{const n=Wn(e)-Wn(t);if(n===0){if(e.pre&&!t.pre)return-1;if(t.pre&&!e.pre)return 1}return n};function Oo(e){Ji=!1,On=!0,Me.sort(Vr);const t=st;try{for(ct=0;ctve(g)?g.trim():g)),h&&(l=n.map(gl))}let a,r=i[a=Si(t)]||i[a=Si(dt(t))];!r&&s&&(r=i[a=Si(Yt(t))]),r&&et(r,e,6,l);const u=i[a+"Once"];if(u){if(!e.emitted)e.emitted={};else if(e.emitted[a])return;e.emitted[a]=!0,et(u,e,6,l)}}function Wo(e,t,n=!1){const i=t.emitsCache,l=i.get(e);if(l!==void 0)return l;const s=e.emits;let o={},a=!1;if(!ae(e)){const r=u=>{const c=Wo(u,t,!0);c&&(a=!0,je(o,c))};!n&&t.mixins.length&&t.mixins.forEach(r),e.extends&&r(e.extends),e.mixins&&e.mixins.forEach(r)}return!s&&!a?(Ie(e)&&i.set(e,null),null):(te(s)?s.forEach(r=>o[r]=null):je(o,s),Ie(e)&&i.set(e,o),o)}function Ci(e,t){return!e||!jn(t)?!1:(t=t.slice(2).replace(/Once$/,""),pe(e,t[0].toLowerCase()+t.slice(1))||pe(e,Yt(t))||pe(e,t))}let He=null,Fo=null;function ai(e){const t=He;return He=e,Fo=e&&e.type.__scopeId||null,t}function De(e,t=He,n){if(!t||e._n)return e;const i=(...l)=>{i._d&&cs(-1);const s=ai(t);let o;try{o=e(...l)}finally{ai(s),i._d&&cs(1)}return o};return i._n=!0,i._c=!0,i._d=!0,i}function Oi(e){const{type:t,vnode:n,proxy:i,withProxy:l,props:s,propsOptions:[o],slots:a,attrs:r,emit:u,render:c,renderCache:h,data:f,setupState:g,ctx:b,inheritAttrs:k}=e;let I,m;const w=ai(e);try{if(n.shapeFlag&4){const F=l||i;I=nt(c.call(F,F,h,s,g,f,b)),m=r}else{const F=t;I=nt(F.length>1?F(s,{attrs:r,slots:a,emit:u}):F(s,null)),m=t.props?r:qr(r)}}catch(F){xn.length=0,Bn(F,e,1),I=ie(Je)}let _=I;if(m&&k!==!1){const F=Object.keys(m),{shapeFlag:U}=_;F.length&&U&7&&(o&&F.some(dl)&&(m=Kr(m,o)),_=Rt(_,m))}return n.dirs&&(_=Rt(_),_.dirs=_.dirs?_.dirs.concat(n.dirs):n.dirs),n.transition&&(_.transition=n.transition),I=_,ai(w),I}const qr=e=>{let t;for(const n in e)(n==="class"||n==="style"||jn(n))&&((t||(t={}))[n]=e[n]);return t},Kr=(e,t)=>{const n={};for(const i in e)(!dl(i)||!(i.slice(9)in t))&&(n[i]=e[i]);return n};function Qr(e,t,n){const{props:i,children:l,component:s}=e,{props:o,children:a,patchFlag:r}=t,u=s.emitsOptions;if(t.dirs||t.transition)return!0;if(n&&r>=0){if(r&1024)return!0;if(r&16)return i?es(i,o,u):!!o;if(r&8){const c=t.dynamicProps;for(let h=0;he.__isSuspense;function Do(e,t){t&&t.pendingBranch?te(e)?t.effects.push(...e):t.effects.push(e):zr(e)}function Gt(e,t){if(Re){let n=Re.provides;const i=Re.parent&&Re.parent.provides;i===n&&(n=Re.provides=Object.create(i)),n[e]=t}}function We(e,t,n=!1){const i=Re||He;if(i){const l=i.parent==null?i.vnode.appContext&&i.vnode.appContext.provides:i.parent.provides;if(l&&e in l)return l[e];if(arguments.length>1)return n&&ae(t)?t.call(i.proxy):t}}function Yr(e,t){return Pl(e,null,t)}const Jn={};function ut(e,t,n){return Pl(e,t,n)}function Pl(e,t,{immediate:n,deep:i,flush:l,onTrack:s,onTrigger:o}=Pe){const a=Re;let r,u=!1,c=!1;if(Fe(e)?(r=()=>e.value,u=si(e)):an(e)?(r=()=>e,i=!0):te(e)?(c=!0,u=e.some(_=>an(_)||si(_)),r=()=>e.map(_=>{if(Fe(_))return _.value;if(an(_))return qt(_);if(ae(_))return xt(_,a,2)})):ae(e)?t?r=()=>xt(e,a,2):r=()=>{if(!(a&&a.isUnmounted))return h&&h(),et(e,a,3,[f])}:r=st,t&&i){const _=r;r=()=>qt(_())}let h,f=_=>{h=m.onStop=()=>{xt(_,a,4)}},g;if(fn)if(f=st,t?n&&et(t,a,3,[r(),c?[]:void 0,f]):r(),l==="sync"){const _=Uc();g=_.__watcherHandles||(_.__watcherHandles=[])}else return st;let b=c?new Array(e.length).fill(Jn):Jn;const k=()=>{if(!!m.active)if(t){const _=m.run();(i||u||(c?_.some((F,U)=>Sn(F,b[U])):Sn(_,b)))&&(h&&h(),et(t,a,3,[_,b===Jn?void 0:c&&b[0]===Jn?[]:b,f]),b=_)}else m.run()};k.allowRecurse=!!t;let I;l==="sync"?I=k:l==="post"?I=()=>Ue(k,a&&a.suspense):(k.pre=!0,a&&(k.id=a.uid),I=()=>Ei(k));const m=new vl(r,I);t?n?k():b=m.run():l==="post"?Ue(m.run.bind(m),a&&a.suspense):m.run();const w=()=>{m.stop(),a&&a.scope&&hl(a.scope.effects,m)};return g&&g.push(w),w}function Xr(e,t,n){const i=this.proxy,l=ve(e)?e.includes(".")?Ho(i,e):()=>i[e]:e.bind(i,i);let s;ae(t)?s=t:(s=t.handler,n=t);const o=Re;hn(this);const a=Pl(l,s.bind(i),n);return o?hn(o):Jt(),a}function Ho(e,t){const n=t.split(".");return()=>{let i=e;for(let l=0;l{qt(n,t)});else if(ho(e))for(const n in e)qt(e[n],t);return e}function Zr(){const e={isMounted:!1,isLeaving:!1,isUnmounting:!1,leavingVNodes:new Map};return Ke(()=>{e.isMounted=!0}),Mn(()=>{e.isUnmounting=!0}),e}const Xe=[Function,Array],ec={name:"BaseTransition",props:{mode:String,appear:Boolean,persisted:Boolean,onBeforeEnter:Xe,onEnter:Xe,onAfterEnter:Xe,onEnterCancelled:Xe,onBeforeLeave:Xe,onLeave:Xe,onAfterLeave:Xe,onLeaveCancelled:Xe,onBeforeAppear:Xe,onAppear:Xe,onAfterAppear:Xe,onAppearCancelled:Xe},setup(e,{slots:t}){const n=ea(),i=Zr();let l;return()=>{const s=t.default&&$o(t.default(),!0);if(!s||!s.length)return;let o=s[0];if(s.length>1){for(const k of s)if(k.type!==Je){o=k;break}}const a=me(e),{mode:r}=a;if(i.isLeaving)return Wi(o);const u=ts(o);if(!u)return Wi(o);const c=Yi(u,a,i,n);Xi(u,c);const h=n.subTree,f=h&&ts(h);let g=!1;const{getTransitionKey:b}=u.type;if(b){const k=b();l===void 0?l=k:k!==l&&(l=k,g=!0)}if(f&&f.type!==Je&&(!zt(u,f)||g)){const k=Yi(f,a,i,n);if(Xi(f,k),r==="out-in")return i.isLeaving=!0,k.afterLeave=()=>{i.isLeaving=!1,n.update.active!==!1&&n.update()},Wi(o);r==="in-out"&&u.type!==Je&&(k.delayLeave=(I,m,w)=>{const _=Bo(i,f);_[String(f.key)]=f,I._leaveCb=()=>{m(),I._leaveCb=void 0,delete c.delayedLeave},c.delayedLeave=w})}return o}}},jo=ec;function Bo(e,t){const{leavingVNodes:n}=e;let i=n.get(t.type);return i||(i=Object.create(null),n.set(t.type,i)),i}function Yi(e,t,n,i){const{appear:l,mode:s,persisted:o=!1,onBeforeEnter:a,onEnter:r,onAfterEnter:u,onEnterCancelled:c,onBeforeLeave:h,onLeave:f,onAfterLeave:g,onLeaveCancelled:b,onBeforeAppear:k,onAppear:I,onAfterAppear:m,onAppearCancelled:w}=t,_=String(e.key),F=Bo(n,e),U=(v,G)=>{v&&et(v,i,9,G)},J=(v,G)=>{const V=G[1];U(v,G),te(v)?v.every(q=>q.length<=1)&&V():v.length<=1&&V()},A={mode:s,persisted:o,beforeEnter(v){let G=a;if(!n.isMounted)if(l)G=k||a;else return;v._leaveCb&&v._leaveCb(!0);const V=F[_];V&&zt(e,V)&&V.el._leaveCb&&V.el._leaveCb(),U(G,[v])},enter(v){let G=r,V=u,q=c;if(!n.isMounted)if(l)G=I||r,V=m||u,q=w||c;else return;let P=!1;const D=v._enterCb=R=>{P||(P=!0,R?U(q,[v]):U(V,[v]),A.delayedLeave&&A.delayedLeave(),v._enterCb=void 0)};G?J(G,[v,D]):D()},leave(v,G){const V=String(e.key);if(v._enterCb&&v._enterCb(!0),n.isUnmounting)return G();U(h,[v]);let q=!1;const P=v._leaveCb=D=>{q||(q=!0,G(),D?U(b,[v]):U(g,[v]),v._leaveCb=void 0,F[V]===e&&delete F[V])};F[V]=e,f?J(f,[v,P]):P()},clone(v){return Yi(v,t,n,i)}};return A}function Wi(e){if($n(e))return e=Rt(e),e.children=null,e}function ts(e){return $n(e)?e.children?e.children[0]:void 0:e}function Xi(e,t){e.shapeFlag&6&&e.component?Xi(e.component.subTree,t):e.shapeFlag&128?(e.ssContent.transition=t.clone(e.ssContent),e.ssFallback.transition=t.clone(e.ssFallback)):e.transition=t}function $o(e,t=!1,n){let i=[],l=0;for(let s=0;s1)for(let s=0;s!!e.type.__asyncLoader;function ee(e){ae(e)&&(e={loader:e});const{loader:t,loadingComponent:n,errorComponent:i,delay:l=200,timeout:s,suspensible:o=!0,onError:a}=e;let r=null,u,c=0;const h=()=>(c++,r=null,f()),f=()=>{let g;return r||(g=r=t().catch(b=>{if(b=b instanceof Error?b:new Error(String(b)),a)return new Promise((k,I)=>{a(b,()=>k(h()),()=>I(b),c+1)});throw b}).then(b=>g!==r&&r?r:(b&&(b.__esModule||b[Symbol.toStringTag]==="Module")&&(b=b.default),u=b,b)))};return he({name:"AsyncComponentWrapper",__asyncLoader:f,get __asyncResolved(){return u},setup(){const g=Re;if(u)return()=>Fi(u,g);const b=w=>{r=null,Bn(w,g,13,!i)};if(o&&g.suspense||fn)return f().then(w=>()=>Fi(w,g)).catch(w=>(b(w),()=>i?ie(i,{error:w}):null));const k=be(!1),I=be(),m=be(!!l);return l&&setTimeout(()=>{m.value=!1},l),s!=null&&setTimeout(()=>{if(!k.value&&!I.value){const w=new Error(`Async component timed out after ${s}ms.`);b(w),I.value=w}},s),f().then(()=>{k.value=!0,g.parent&&$n(g.parent.vnode)&&Ei(g.parent.update)}).catch(w=>{b(w),I.value=w}),()=>{if(k.value&&u)return Fi(u,g);if(I.value&&i)return ie(i,{error:I.value});if(n&&!m.value)return ie(n)}}})}function Fi(e,t){const{ref:n,props:i,children:l,ce:s}=t.vnode,o=ie(e,i,l);return o.ref=n,o.ce=s,delete t.vnode.ce,o}const $n=e=>e.type.__isKeepAlive;function tc(e,t){Mo(e,"a",t)}function nc(e,t){Mo(e,"da",t)}function Mo(e,t,n=Re){const i=e.__wdc||(e.__wdc=()=>{let l=n;for(;l;){if(l.isDeactivated)return;l=l.parent}return e()});if(Pi(t,i,n),n){let l=n.parent;for(;l&&l.parent;)$n(l.parent.vnode)&&ic(i,t,n,l),l=l.parent}}function ic(e,t,n,i){const l=Pi(t,e,i,!0);Ii(()=>{hl(i[t],l)},n)}function Pi(e,t,n=Re,i=!1){if(n){const l=n[e]||(n[e]=[]),s=t.__weh||(t.__weh=(...o)=>{if(n.isUnmounted)return;mn(),hn(n);const a=et(t,n,e,o);return Jt(),vn(),a});return i?l.unshift(s):l.push(s),s}}const wt=e=>(t,n=Re)=>(!fn||e==="sp")&&Pi(e,(...i)=>t(...i),n),lc=wt("bm"),Ke=wt("m"),sc=wt("bu"),oc=wt("u"),Mn=wt("bum"),Ii=wt("um"),ac=wt("sp"),rc=wt("rtg"),cc=wt("rtc");function uc(e,t=Re){Pi("ec",e,t)}function ri(e,t){const n=He;if(n===null)return e;const i=xi(n)||n.proxy,l=e.dirs||(e.dirs=[]);for(let s=0;st(o,a,void 0,s&&s[a]));else{const o=Object.keys(e);l=new Array(o.length);for(let a=0,r=o.length;adi(t)?!(t.type===Je||t.type===Ee&&!zo(t.children)):!0)?e:null}const Zi=e=>e?ta(e)?xi(e)||e.proxy:Zi(e.parent):null,In=je(Object.create(null),{$:e=>e,$el:e=>e.vnode.el,$data:e=>e.data,$props:e=>e.props,$attrs:e=>e.attrs,$slots:e=>e.slots,$refs:e=>e.refs,$parent:e=>Zi(e.parent),$root:e=>Zi(e.root),$emit:e=>e.emit,$options:e=>Il(e),$forceUpdate:e=>e.f||(e.f=()=>Ei(e.update)),$nextTick:e=>e.n||(e.n=ki.bind(e.proxy)),$watch:e=>Xr.bind(e)}),Di=(e,t)=>e!==Pe&&!e.__isScriptSetup&&pe(e,t),fc={get({_:e},t){const{ctx:n,setupState:i,data:l,props:s,accessCache:o,type:a,appContext:r}=e;let u;if(t[0]!=="$"){const g=o[t];if(g!==void 0)switch(g){case 1:return i[t];case 2:return l[t];case 4:return n[t];case 3:return s[t]}else{if(Di(i,t))return o[t]=1,i[t];if(l!==Pe&&pe(l,t))return o[t]=2,l[t];if((u=e.propsOptions[0])&&pe(u,t))return o[t]=3,s[t];if(n!==Pe&&pe(n,t))return o[t]=4,n[t];el&&(o[t]=0)}}const c=In[t];let h,f;if(c)return t==="$attrs"&&Ye(e,"get",t),c(e);if((h=a.__cssModules)&&(h=h[t]))return h;if(n!==Pe&&pe(n,t))return o[t]=4,n[t];if(f=r.config.globalProperties,pe(f,t))return f[t]},set({_:e},t,n){const{data:i,setupState:l,ctx:s}=e;return Di(l,t)?(l[t]=n,!0):i!==Pe&&pe(i,t)?(i[t]=n,!0):pe(e.props,t)||t[0]==="$"&&t.slice(1)in e?!1:(s[t]=n,!0)},has({_:{data:e,setupState:t,accessCache:n,ctx:i,appContext:l,propsOptions:s}},o){let a;return!!n[o]||e!==Pe&&pe(e,o)||Di(t,o)||(a=s[0])&&pe(a,o)||pe(i,o)||pe(In,o)||pe(l.config.globalProperties,o)},defineProperty(e,t,n){return n.get!=null?e._.accessCache[t]=0:pe(n,"value")&&this.set(e,t,n.value,null),Reflect.defineProperty(e,t,n)}};let el=!0;function pc(e){const t=Il(e),n=e.proxy,i=e.ctx;el=!1,t.beforeCreate&&is(t.beforeCreate,e,"bc");const{data:l,computed:s,methods:o,watch:a,provide:r,inject:u,created:c,beforeMount:h,mounted:f,beforeUpdate:g,updated:b,activated:k,deactivated:I,beforeDestroy:m,beforeUnmount:w,destroyed:_,unmounted:F,render:U,renderTracked:J,renderTriggered:A,errorCaptured:v,serverPrefetch:G,expose:V,inheritAttrs:q,components:P,directives:D,filters:R}=t;if(u&&gc(u,i,null,e.appContext.config.unwrapInjectedRef),o)for(const ne in o){const se=o[ne];ae(se)&&(i[ne]=se.bind(n))}if(l){const ne=l.call(n,n);Ie(ne)&&(e.data=bn(ne))}if(el=!0,s)for(const ne in s){const se=s[ne],Ae=ae(se)?se.bind(n,n):ae(se.get)?se.get.bind(n,n):st,Be=!ae(se)&&ae(se.set)?se.set.bind(n):st,Ne=$({get:Ae,set:Be});Object.defineProperty(i,ne,{enumerable:!0,configurable:!0,get:()=>Ne.value,set:$e=>Ne.value=$e})}if(a)for(const ne in a)Vo(a[ne],i,n,ne);if(r){const ne=ae(r)?r.call(n):r;Reflect.ownKeys(ne).forEach(se=>{Gt(se,ne[se])})}c&&is(c,e,"c");function N(ne,se){te(se)?se.forEach(Ae=>ne(Ae.bind(n))):se&&ne(se.bind(n))}if(N(lc,h),N(Ke,f),N(sc,g),N(oc,b),N(tc,k),N(nc,I),N(uc,v),N(cc,J),N(rc,A),N(Mn,w),N(Ii,F),N(ac,G),te(V))if(V.length){const ne=e.exposed||(e.exposed={});V.forEach(se=>{Object.defineProperty(ne,se,{get:()=>n[se],set:Ae=>n[se]=Ae})})}else e.exposed||(e.exposed={});U&&e.render===st&&(e.render=U),q!=null&&(e.inheritAttrs=q),P&&(e.components=P),D&&(e.directives=D)}function gc(e,t,n=st,i=!1){te(e)&&(e=tl(e));for(const l in e){const s=e[l];let o;Ie(s)?"default"in s?o=We(s.from||l,s.default,!0):o=We(s.from||l):o=We(s),Fe(o)&&i?Object.defineProperty(t,l,{enumerable:!0,configurable:!0,get:()=>o.value,set:a=>o.value=a}):t[l]=o}}function is(e,t,n){et(te(e)?e.map(i=>i.bind(t.proxy)):e.bind(t.proxy),t,n)}function Vo(e,t,n,i){const l=i.includes(".")?Ho(n,i):()=>n[i];if(ve(e)){const s=t[e];ae(s)&&ut(l,s)}else if(ae(e))ut(l,e.bind(n));else if(Ie(e))if(te(e))e.forEach(s=>Vo(s,t,n,i));else{const s=ae(e.handler)?e.handler.bind(n):t[e.handler];ae(s)&&ut(l,s,e)}}function Il(e){const t=e.type,{mixins:n,extends:i}=t,{mixins:l,optionsCache:s,config:{optionMergeStrategies:o}}=e.appContext,a=s.get(t);let r;return a?r=a:!l.length&&!n&&!i?r=t:(r={},l.length&&l.forEach(u=>ci(r,u,o,!0)),ci(r,t,o)),Ie(t)&&s.set(t,r),r}function ci(e,t,n,i=!1){const{mixins:l,extends:s}=t;s&&ci(e,s,n,!0),l&&l.forEach(o=>ci(e,o,n,!0));for(const o in t)if(!(i&&o==="expose")){const a=mc[o]||n&&n[o];e[o]=a?a(e[o],t[o]):t[o]}return e}const mc={data:ls,props:Bt,emits:Bt,methods:Bt,computed:Bt,beforeCreate:ze,created:ze,beforeMount:ze,mounted:ze,beforeUpdate:ze,updated:ze,beforeDestroy:ze,beforeUnmount:ze,destroyed:ze,unmounted:ze,activated:ze,deactivated:ze,errorCaptured:ze,serverPrefetch:ze,components:Bt,directives:Bt,watch:bc,provide:ls,inject:vc};function ls(e,t){return t?e?function(){return je(ae(e)?e.call(this,this):e,ae(t)?t.call(this,this):t)}:t:e}function vc(e,t){return Bt(tl(e),tl(t))}function tl(e){if(te(e)){const t={};for(let n=0;n0)&&!(o&16)){if(o&8){const c=e.vnode.dynamicProps;for(let h=0;h{r=!0;const[f,g]=qo(h,t,!0);je(o,f),g&&a.push(...g)};!n&&t.mixins.length&&t.mixins.forEach(c),e.extends&&c(e.extends),e.mixins&&e.mixins.forEach(c)}if(!s&&!r)return Ie(e)&&i.set(e,sn),sn;if(te(s))for(let c=0;c-1,g[1]=k<0||b-1||pe(g,"default"))&&a.push(h)}}}const u=[o,a];return Ie(e)&&i.set(e,u),u}function ss(e){return e[0]!=="$"}function os(e){const t=e&&e.toString().match(/^\s*function (\w+)/);return t?t[1]:e===null?"null":""}function as(e,t){return os(e)===os(t)}function rs(e,t){return te(t)?t.findIndex(n=>as(n,e)):ae(t)&&as(t,e)?0:-1}const Ko=e=>e[0]==="_"||e==="$stable",Ll=e=>te(e)?e.map(nt):[nt(e)],_c=(e,t,n)=>{if(t._n)return t;const i=De((...l)=>Ll(t(...l)),n);return i._c=!1,i},Qo=(e,t,n)=>{const i=e._ctx;for(const l in e){if(Ko(l))continue;const s=e[l];if(ae(s))t[l]=_c(l,s,i);else if(s!=null){const o=Ll(s);t[l]=()=>o}}},Go=(e,t)=>{const n=Ll(t);e.slots.default=()=>n},kc=(e,t)=>{if(e.vnode.shapeFlag&32){const n=t._;n?(e.slots=me(t),li(t,"_",n)):Qo(t,e.slots={})}else e.slots={},t&&Go(e,t);li(e.slots,Li,1)},Ec=(e,t,n)=>{const{vnode:i,slots:l}=e;let s=!0,o=Pe;if(i.shapeFlag&32){const a=t._;a?n&&a===1?s=!1:(je(l,t),!n&&a===1&&delete l._):(s=!t.$stable,Qo(t,l)),o=t}else t&&(Go(e,t),o={default:1});if(s)for(const a in l)!Ko(a)&&!(a in o)&&delete l[a]};function Jo(){return{app:null,config:{isNativeTag:Ya,performance:!1,globalProperties:{},optionMergeStrategies:{},errorHandler:void 0,warnHandler:void 0,compilerOptions:{}},mixins:[],components:{},directives:{},provides:Object.create(null),optionsCache:new WeakMap,propsCache:new WeakMap,emitsCache:new WeakMap}}let Cc=0;function Pc(e,t){return function(i,l=null){ae(i)||(i=Object.assign({},i)),l!=null&&!Ie(l)&&(l=null);const s=Jo(),o=new Set;let a=!1;const r=s.app={_uid:Cc++,_component:i,_props:l,_container:null,_context:s,_instance:null,version:qc,get config(){return s.config},set config(u){},use(u,...c){return o.has(u)||(u&&ae(u.install)?(o.add(u),u.install(r,...c)):ae(u)&&(o.add(u),u(r,...c))),r},mixin(u){return s.mixins.includes(u)||s.mixins.push(u),r},component(u,c){return c?(s.components[u]=c,r):s.components[u]},directive(u,c){return c?(s.directives[u]=c,r):s.directives[u]},mount(u,c,h){if(!a){const f=ie(i,l);return f.appContext=s,c&&t?t(f,u):e(f,u,h),a=!0,r._container=u,u.__vue_app__=r,xi(f.component)||f.component.proxy}},unmount(){a&&(e(null,r._container),delete r._container.__vue_app__)},provide(u,c){return s.provides[u]=c,r}};return r}}function ui(e,t,n,i,l=!1){if(te(e)){e.forEach((f,g)=>ui(f,t&&(te(t)?t[g]:t),n,i,l));return}if(cn(i)&&!l)return;const s=i.shapeFlag&4?xi(i.component)||i.component.proxy:i.el,o=l?null:s,{i:a,r}=e,u=t&&t.r,c=a.refs===Pe?a.refs={}:a.refs,h=a.setupState;if(u!=null&&u!==r&&(ve(u)?(c[u]=null,pe(h,u)&&(h[u]=null)):Fe(u)&&(u.value=null)),ae(r))xt(r,a,12,[o,c]);else{const f=ve(r),g=Fe(r);if(f||g){const b=()=>{if(e.f){const k=f?pe(h,r)?h[r]:c[r]:r.value;l?te(k)&&hl(k,s):te(k)?k.includes(s)||k.push(s):f?(c[r]=[s],pe(h,r)&&(h[r]=c[r])):(r.value=[s],e.k&&(c[e.k]=r.value))}else f?(c[r]=o,pe(h,r)&&(h[r]=o)):g&&(r.value=o,e.k&&(c[e.k]=o))};o?(b.id=-1,Ue(b,n)):b()}}}let kt=!1;const Yn=e=>/svg/.test(e.namespaceURI)&&e.tagName!=="foreignObject",Xn=e=>e.nodeType===8;function Ic(e){const{mt:t,p:n,o:{patchProp:i,createText:l,nextSibling:s,parentNode:o,remove:a,insert:r,createComment:u}}=e,c=(m,w)=>{if(!w.hasChildNodes()){n(null,m,w),oi(),w._vnode=m;return}kt=!1,h(w.firstChild,m,null,null,null),oi(),w._vnode=m,kt&&console.error("Hydration completed but contains mismatches.")},h=(m,w,_,F,U,J=!1)=>{const A=Xn(m)&&m.data==="[",v=()=>k(m,w,_,F,U,A),{type:G,ref:V,shapeFlag:q,patchFlag:P}=w;let D=m.nodeType;w.el=m,P===-2&&(J=!1,w.dynamicChildren=null);let R=null;switch(G){case dn:D!==3?w.children===""?(r(w.el=l(""),o(m),m),R=m):R=v():(m.data!==w.children&&(kt=!0,m.data=w.children),R=s(m));break;case Je:D!==8||A?R=v():R=s(m);break;case Ln:if(A&&(m=s(m),D=m.nodeType),D===1||D===3){R=m;const re=!w.children.length;for(let N=0;N{J=J||!!w.dynamicChildren;const{type:A,props:v,patchFlag:G,shapeFlag:V,dirs:q}=w,P=A==="input"&&q||A==="option";if(P||G!==-1){if(q&&rt(w,null,_,"created"),v)if(P||!J||G&48)for(const R in v)(P&&R.endsWith("value")||jn(R)&&!Pn(R))&&i(m,R,null,v[R],!1,void 0,_);else v.onClick&&i(m,"onClick",null,v.onClick,!1,void 0,_);let D;if((D=v&&v.onVnodeBeforeMount)&&Ze(D,_,w),q&&rt(w,null,_,"beforeMount"),((D=v&&v.onVnodeMounted)||q)&&Do(()=>{D&&Ze(D,_,w),q&&rt(w,null,_,"mounted")},F),V&16&&!(v&&(v.innerHTML||v.textContent))){let R=g(m.firstChild,w,m,_,F,U,J);for(;R;){kt=!0;const re=R;R=R.nextSibling,a(re)}}else V&8&&m.textContent!==w.children&&(kt=!0,m.textContent=w.children)}return m.nextSibling},g=(m,w,_,F,U,J,A)=>{A=A||!!w.dynamicChildren;const v=w.children,G=v.length;for(let V=0;V{const{slotScopeIds:A}=w;A&&(U=U?U.concat(A):A);const v=o(m),G=g(s(m),w,v,_,F,U,J);return G&&Xn(G)&&G.data==="]"?s(w.anchor=G):(kt=!0,r(w.anchor=u("]"),v,G),G)},k=(m,w,_,F,U,J)=>{if(kt=!0,w.el=null,J){const G=I(m);for(;;){const V=s(m);if(V&&V!==G)a(V);else break}}const A=s(m),v=o(m);return a(m),n(null,w,v,A,_,F,Yn(v),U),A},I=m=>{let w=0;for(;m;)if(m=s(m),m&&Xn(m)&&(m.data==="["&&w++,m.data==="]")){if(w===0)return s(m);w--}return m};return[c,h]}const Ue=Do;function Lc(e){return xc(e,Ic)}function xc(e,t){const n=ir();n.__VUE__=!0;const{insert:i,remove:l,patchProp:s,createElement:o,createText:a,createComment:r,setText:u,setElementText:c,parentNode:h,nextSibling:f,setScopeId:g=st,insertStaticContent:b}=e,k=(d,p,y,E=null,L=null,O=null,B=!1,W=null,H=!!p.dynamicChildren)=>{if(d===p)return;d&&!zt(d,p)&&(E=j(d),$e(d,L,O,!0),d=null),p.patchFlag===-2&&(H=!1,p.dynamicChildren=null);const{type:T,ref:Y,shapeFlag:K}=p;switch(T){case dn:I(d,p,y,E);break;case Je:m(d,p,y,E);break;case Ln:d==null&&w(p,y,E,B);break;case Ee:P(d,p,y,E,L,O,B,W,H);break;default:K&1?U(d,p,y,E,L,O,B,W,H):K&6?D(d,p,y,E,L,O,B,W,H):(K&64||K&128)&&T.process(d,p,y,E,L,O,B,W,H,ue)}Y!=null&&L&&ui(Y,d&&d.ref,O,p||d,!p)},I=(d,p,y,E)=>{if(d==null)i(p.el=a(p.children),y,E);else{const L=p.el=d.el;p.children!==d.children&&u(L,p.children)}},m=(d,p,y,E)=>{d==null?i(p.el=r(p.children||""),y,E):p.el=d.el},w=(d,p,y,E)=>{[d.el,d.anchor]=b(d.children,p,y,E,d.el,d.anchor)},_=({el:d,anchor:p},y,E)=>{let L;for(;d&&d!==p;)L=f(d),i(d,y,E),d=L;i(p,y,E)},F=({el:d,anchor:p})=>{let y;for(;d&&d!==p;)y=f(d),l(d),d=y;l(p)},U=(d,p,y,E,L,O,B,W,H)=>{B=B||p.type==="svg",d==null?J(p,y,E,L,O,B,W,H):G(d,p,L,O,B,W,H)},J=(d,p,y,E,L,O,B,W)=>{let H,T;const{type:Y,props:K,shapeFlag:X,transition:le,dirs:ce}=d;if(H=d.el=o(d.type,O,K&&K.is,K),X&8?c(H,d.children):X&16&&v(d.children,H,null,E,L,O&&Y!=="foreignObject",B,W),ce&&rt(d,null,E,"created"),K){for(const ye in K)ye!=="value"&&!Pn(ye)&&s(H,ye,null,K[ye],O,d.children,E,L,z);"value"in K&&s(H,"value",null,K.value),(T=K.onVnodeBeforeMount)&&Ze(T,E,d)}A(H,d,d.scopeId,B,E),ce&&rt(d,null,E,"beforeMount");const _e=(!L||L&&!L.pendingBranch)&&le&&!le.persisted;_e&&le.beforeEnter(H),i(H,p,y),((T=K&&K.onVnodeMounted)||_e||ce)&&Ue(()=>{T&&Ze(T,E,d),_e&&le.enter(H),ce&&rt(d,null,E,"mounted")},L)},A=(d,p,y,E,L)=>{if(y&&g(d,y),E)for(let O=0;O{for(let T=H;T{const W=p.el=d.el;let{patchFlag:H,dynamicChildren:T,dirs:Y}=p;H|=d.patchFlag&16;const K=d.props||Pe,X=p.props||Pe;let le;y&&Dt(y,!1),(le=X.onVnodeBeforeUpdate)&&Ze(le,y,p,d),Y&&rt(p,d,y,"beforeUpdate"),y&&Dt(y,!0);const ce=L&&p.type!=="foreignObject";if(T?V(d.dynamicChildren,T,W,y,E,ce,O):B||se(d,p,W,null,y,E,ce,O,!1),H>0){if(H&16)q(W,p,K,X,y,E,L);else if(H&2&&K.class!==X.class&&s(W,"class",null,X.class,L),H&4&&s(W,"style",K.style,X.style,L),H&8){const _e=p.dynamicProps;for(let ye=0;ye<_e.length;ye++){const Te=_e[ye],tt=K[Te],en=X[Te];(en!==tt||Te==="value")&&s(W,Te,tt,en,L,d.children,y,E,z)}}H&1&&d.children!==p.children&&c(W,p.children)}else!B&&T==null&&q(W,p,K,X,y,E,L);((le=X.onVnodeUpdated)||Y)&&Ue(()=>{le&&Ze(le,y,p,d),Y&&rt(p,d,y,"updated")},E)},V=(d,p,y,E,L,O,B)=>{for(let W=0;W{if(y!==E){if(y!==Pe)for(const W in y)!Pn(W)&&!(W in E)&&s(d,W,y[W],null,B,p.children,L,O,z);for(const W in E){if(Pn(W))continue;const H=E[W],T=y[W];H!==T&&W!=="value"&&s(d,W,T,H,B,p.children,L,O,z)}"value"in E&&s(d,"value",y.value,E.value)}},P=(d,p,y,E,L,O,B,W,H)=>{const T=p.el=d?d.el:a(""),Y=p.anchor=d?d.anchor:a("");let{patchFlag:K,dynamicChildren:X,slotScopeIds:le}=p;le&&(W=W?W.concat(le):le),d==null?(i(T,y,E),i(Y,y,E),v(p.children,y,Y,L,O,B,W,H)):K>0&&K&64&&X&&d.dynamicChildren?(V(d.dynamicChildren,X,y,L,O,B,W),(p.key!=null||L&&p===L.subTree)&&Yo(d,p,!0)):se(d,p,y,Y,L,O,B,W,H)},D=(d,p,y,E,L,O,B,W,H)=>{p.slotScopeIds=W,d==null?p.shapeFlag&512?L.ctx.activate(p,y,E,B,H):R(p,y,E,L,O,B,H):re(d,p,H)},R=(d,p,y,E,L,O,B)=>{const W=d.component=Hc(d,E,L);if($n(d)&&(W.ctx.renderer=ue),jc(W),W.asyncDep){if(L&&L.registerDep(W,N),!d.el){const H=W.subTree=ie(Je);m(null,H,p,y)}return}N(W,d,p,y,L,O,B)},re=(d,p,y)=>{const E=p.component=d.component;if(Qr(d,p,y))if(E.asyncDep&&!E.asyncResolved){ne(E,p,y);return}else E.next=p,Nr(E.update),E.update();else p.el=d.el,E.vnode=p},N=(d,p,y,E,L,O,B)=>{const W=()=>{if(d.isMounted){let{next:Y,bu:K,u:X,parent:le,vnode:ce}=d,_e=Y,ye;Dt(d,!1),Y?(Y.el=ce.el,ne(d,Y,B)):Y=ce,K&&Ri(K),(ye=Y.props&&Y.props.onVnodeBeforeUpdate)&&Ze(ye,le,Y,ce),Dt(d,!0);const Te=Oi(d),tt=d.subTree;d.subTree=Te,k(tt,Te,h(tt.el),j(tt),d,L,O),Y.el=Te.el,_e===null&&Gr(d,Te.el),X&&Ue(X,L),(ye=Y.props&&Y.props.onVnodeUpdated)&&Ue(()=>Ze(ye,le,Y,ce),L)}else{let Y;const{el:K,props:X}=p,{bm:le,m:ce,parent:_e}=d,ye=cn(p);if(Dt(d,!1),le&&Ri(le),!ye&&(Y=X&&X.onVnodeBeforeMount)&&Ze(Y,_e,p),Dt(d,!0),K&&oe){const Te=()=>{d.subTree=Oi(d),oe(K,d.subTree,d,L,null)};ye?p.type.__asyncLoader().then(()=>!d.isUnmounted&&Te()):Te()}else{const Te=d.subTree=Oi(d);k(null,Te,y,E,d,L,O),p.el=Te.el}if(ce&&Ue(ce,L),!ye&&(Y=X&&X.onVnodeMounted)){const Te=p;Ue(()=>Ze(Y,_e,Te),L)}(p.shapeFlag&256||_e&&cn(_e.vnode)&&_e.vnode.shapeFlag&256)&&d.a&&Ue(d.a,L),d.isMounted=!0,p=y=E=null}},H=d.effect=new vl(W,()=>Ei(T),d.scope),T=d.update=()=>H.run();T.id=d.uid,Dt(d,!0),T()},ne=(d,p,y)=>{p.component=d;const E=d.vnode.props;d.vnode=p,d.next=null,yc(d,p.props,E,y),Ec(d,p.children,y),mn(),Zl(),vn()},se=(d,p,y,E,L,O,B,W,H=!1)=>{const T=d&&d.children,Y=d?d.shapeFlag:0,K=p.children,{patchFlag:X,shapeFlag:le}=p;if(X>0){if(X&128){Be(T,K,y,E,L,O,B,W,H);return}else if(X&256){Ae(T,K,y,E,L,O,B,W,H);return}}le&8?(Y&16&&z(T,L,O),K!==T&&c(y,K)):Y&16?le&16?Be(T,K,y,E,L,O,B,W,H):z(T,L,O,!0):(Y&8&&c(y,""),le&16&&v(K,y,E,L,O,B,W,H))},Ae=(d,p,y,E,L,O,B,W,H)=>{d=d||sn,p=p||sn;const T=d.length,Y=p.length,K=Math.min(T,Y);let X;for(X=0;XY?z(d,L,O,!0,!1,K):v(p,y,E,L,O,B,W,H,K)},Be=(d,p,y,E,L,O,B,W,H)=>{let T=0;const Y=p.length;let K=d.length-1,X=Y-1;for(;T<=K&&T<=X;){const le=d[T],ce=p[T]=H?Pt(p[T]):nt(p[T]);if(zt(le,ce))k(le,ce,y,null,L,O,B,W,H);else break;T++}for(;T<=K&&T<=X;){const le=d[K],ce=p[X]=H?Pt(p[X]):nt(p[X]);if(zt(le,ce))k(le,ce,y,null,L,O,B,W,H);else break;K--,X--}if(T>K){if(T<=X){const le=X+1,ce=leX)for(;T<=K;)$e(d[T],L,O,!0),T++;else{const le=T,ce=T,_e=new Map;for(T=ce;T<=X;T++){const Qe=p[T]=H?Pt(p[T]):nt(p[T]);Qe.key!=null&&_e.set(Qe.key,T)}let ye,Te=0;const tt=X-ce+1;let en=!1,Ml=0;const wn=new Array(tt);for(T=0;T=tt){$e(Qe,L,O,!0);continue}let at;if(Qe.key!=null)at=_e.get(Qe.key);else for(ye=ce;ye<=X;ye++)if(wn[ye-ce]===0&&zt(Qe,p[ye])){at=ye;break}at===void 0?$e(Qe,L,O,!0):(wn[at-ce]=T+1,at>=Ml?Ml=at:en=!0,k(Qe,p[at],y,null,L,O,B,W,H),Te++)}const Nl=en?Ac(wn):sn;for(ye=Nl.length-1,T=tt-1;T>=0;T--){const Qe=ce+T,at=p[Qe],zl=Qe+1{const{el:O,type:B,transition:W,children:H,shapeFlag:T}=d;if(T&6){Ne(d.component.subTree,p,y,E);return}if(T&128){d.suspense.move(p,y,E);return}if(T&64){B.move(d,p,y,ue);return}if(B===Ee){i(O,p,y);for(let K=0;KW.enter(O),L);else{const{leave:K,delayLeave:X,afterLeave:le}=W,ce=()=>i(O,p,y),_e=()=>{K(O,()=>{ce(),le&&le()})};X?X(O,ce,_e):_e()}else i(O,p,y)},$e=(d,p,y,E=!1,L=!1)=>{const{type:O,props:B,ref:W,children:H,dynamicChildren:T,shapeFlag:Y,patchFlag:K,dirs:X}=d;if(W!=null&&ui(W,null,y,d,!0),Y&256){p.ctx.deactivate(d);return}const le=Y&1&&X,ce=!cn(d);let _e;if(ce&&(_e=B&&B.onVnodeBeforeUnmount)&&Ze(_e,p,d),Y&6)C(d.component,y,E);else{if(Y&128){d.suspense.unmount(y,E);return}le&&rt(d,null,p,"beforeUnmount"),Y&64?d.type.remove(d,p,y,L,ue,E):T&&(O!==Ee||K>0&&K&64)?z(T,p,y,!1,!0):(O===Ee&&K&384||!L&&Y&16)&&z(H,p,y),E&&yt(d)}(ce&&(_e=B&&B.onVnodeUnmounted)||le)&&Ue(()=>{_e&&Ze(_e,p,d),le&&rt(d,null,p,"unmounted")},y)},yt=d=>{const{type:p,el:y,anchor:E,transition:L}=d;if(p===Ee){Zt(y,E);return}if(p===Ln){F(d);return}const O=()=>{l(y),L&&!L.persisted&&L.afterLeave&&L.afterLeave()};if(d.shapeFlag&1&&L&&!L.persisted){const{leave:B,delayLeave:W}=L,H=()=>B(y,O);W?W(d.el,O,H):H()}else O()},Zt=(d,p)=>{let y;for(;d!==p;)y=f(d),l(d),d=y;l(p)},C=(d,p,y)=>{const{bum:E,scope:L,update:O,subTree:B,um:W}=d;E&&Ri(E),L.stop(),O&&(O.active=!1,$e(B,d,p,y)),W&&Ue(W,p),Ue(()=>{d.isUnmounted=!0},p),p&&p.pendingBranch&&!p.isUnmounted&&d.asyncDep&&!d.asyncResolved&&d.suspenseId===p.pendingId&&(p.deps--,p.deps===0&&p.resolve())},z=(d,p,y,E=!1,L=!1,O=0)=>{for(let B=O;Bd.shapeFlag&6?j(d.component.subTree):d.shapeFlag&128?d.suspense.next():f(d.anchor||d.el),Q=(d,p,y)=>{d==null?p._vnode&&$e(p._vnode,null,null,!0):k(p._vnode||null,d,p,null,null,null,y),Zl(),oi(),p._vnode=d},ue={p:k,um:$e,m:Ne,r:yt,mt:R,mc:v,pc:se,pbc:V,n:j,o:e};let Ce,oe;return t&&([Ce,oe]=t(ue)),{render:Q,hydrate:Ce,createApp:Pc(Q,Ce)}}function Dt({effect:e,update:t},n){e.allowRecurse=t.allowRecurse=n}function Yo(e,t,n=!1){const i=e.children,l=t.children;if(te(i)&&te(l))for(let s=0;s>1,e[n[a]]0&&(t[i]=n[s-1]),n[s]=i)}}for(s=n.length,o=n[s-1];s-- >0;)n[s]=o,o=t[o];return n}const Tc=e=>e.__isTeleport,Ee=Symbol(void 0),dn=Symbol(void 0),Je=Symbol(void 0),Ln=Symbol(void 0),xn=[];let lt=null;function M(e=!1){xn.push(lt=e?null:[])}function Sc(){xn.pop(),lt=xn[xn.length-1]||null}let Fn=1;function cs(e){Fn+=e}function Xo(e){return e.dynamicChildren=Fn>0?lt||sn:null,Sc(),Fn>0&<&<.push(e),e}function Z(e,t,n,i,l,s){return Xo(ge(e,t,n,i,l,s,!0))}function Se(e,t,n,i,l){return Xo(ie(e,t,n,i,l,!0))}function di(e){return e?e.__v_isVNode===!0:!1}function zt(e,t){return e.type===t.type&&e.key===t.key}const Li="__vInternal",Zo=({key:e})=>e!=null?e:null,ti=({ref:e,ref_key:t,ref_for:n})=>e!=null?ve(e)||Fe(e)||ae(e)?{i:He,r:e,k:t,f:!!n}:e:null;function ge(e,t=null,n=null,i=0,l=null,s=e===Ee?0:1,o=!1,a=!1){const r={__v_isVNode:!0,__v_skip:!0,type:e,props:t,key:t&&Zo(t),ref:t&&ti(t),scopeId:Fo,slotScopeIds:null,children:n,component:null,suspense:null,ssContent:null,ssFallback:null,dirs:null,transition:null,el:null,anchor:null,target:null,targetAnchor:null,staticCount:0,shapeFlag:s,patchFlag:i,dynamicProps:l,dynamicChildren:null,appContext:null,ctx:He};return a?(xl(r,n),s&128&&e.normalize(r)):n&&(r.shapeFlag|=ve(n)?8:16),Fn>0&&!o&<&&(r.patchFlag>0||s&6)&&r.patchFlag!==32&<.push(r),r}const ie=Rc;function Rc(e,t=null,n=null,i=0,l=null,s=!1){if((!e||e===dc)&&(e=Je),di(e)){const a=Rt(e,t,!0);return n&&xl(a,n),Fn>0&&!s&<&&(a.shapeFlag&6?lt[lt.indexOf(e)]=a:lt.push(a)),a.patchFlag|=-2,a}if(zc(e)&&(e=e.__vccOpts),t){t=Oc(t);let{class:a,style:r}=t;a&&!ve(a)&&(t.class=qe(a)),Ie(r)&&(Eo(r)&&!te(r)&&(r=je({},r)),t.style=Hn(r))}const o=ve(e)?1:Jr(e)?128:Tc(e)?64:Ie(e)?4:ae(e)?2:0;return ge(e,t,n,i,l,o,s,!0)}function Oc(e){return e?Eo(e)||Li in e?je({},e):e:null}function Rt(e,t,n=!1){const{props:i,ref:l,patchFlag:s,children:o}=e,a=t?il(i||{},t):i;return{__v_isVNode:!0,__v_skip:!0,type:e.type,props:a,key:a&&Zo(a),ref:t&&t.ref?n&&l?te(l)?l.concat(ti(t)):[l,ti(t)]:ti(t):l,scopeId:e.scopeId,slotScopeIds:e.slotScopeIds,children:o,target:e.target,targetAnchor:e.targetAnchor,staticCount:e.staticCount,shapeFlag:e.shapeFlag,patchFlag:t&&e.type!==Ee?s===-1?16:s|16:s,dynamicProps:e.dynamicProps,dynamicChildren:e.dynamicChildren,appContext:e.appContext,dirs:e.dirs,transition:e.transition,component:e.component,suspense:e.suspense,ssContent:e.ssContent&&Rt(e.ssContent),ssFallback:e.ssFallback&&Rt(e.ssFallback),el:e.el,anchor:e.anchor,ctx:e.ctx}}function Ot(e=" ",t=0){return ie(dn,null,e,t)}function Wc(e,t){const n=ie(Ln,null,e);return n.staticCount=t,n}function xe(e="",t=!1){return t?(M(),Se(Je,null,e)):ie(Je,null,e)}function nt(e){return e==null||typeof e=="boolean"?ie(Je):te(e)?ie(Ee,null,e.slice()):typeof e=="object"?Pt(e):ie(dn,null,String(e))}function Pt(e){return e.el===null&&e.patchFlag!==-1||e.memo?e:Rt(e)}function xl(e,t){let n=0;const{shapeFlag:i}=e;if(t==null)t=null;else if(te(t))n=16;else if(typeof t=="object")if(i&65){const l=t.default;l&&(l._c&&(l._d=!1),xl(e,l()),l._c&&(l._d=!0));return}else{n=32;const l=t._;!l&&!(Li in t)?t._ctx=He:l===3&&He&&(He.slots._===1?t._=1:(t._=2,e.patchFlag|=1024))}else ae(t)?(t={default:t,_ctx:He},n=32):(t=String(t),i&64?(n=16,t=[Ot(t)]):n=8);e.children=t,e.shapeFlag|=n}function il(...e){const t={};for(let n=0;nRe||He,hn=e=>{Re=e,e.scope.on()},Jt=()=>{Re&&Re.scope.off(),Re=null};function ta(e){return e.vnode.shapeFlag&4}let fn=!1;function jc(e,t=!1){fn=t;const{props:n,children:i}=e.vnode,l=ta(e);wc(e,n,l,t),kc(e,i);const s=l?Bc(e,t):void 0;return fn=!1,s}function Bc(e,t){const n=e.type;e.accessCache=Object.create(null),e.proxy=Co(new Proxy(e.ctx,fc));const{setup:i}=n;if(i){const l=e.setupContext=i.length>1?Mc(e):null;hn(e),mn();const s=xt(i,e,0,[e.props,l]);if(vn(),Jt(),co(s)){if(s.then(Jt,Jt),t)return s.then(o=>{us(e,o,t)}).catch(o=>{Bn(o,e,0)});e.asyncDep=s}else us(e,s,t)}else na(e,t)}function us(e,t,n){ae(t)?e.type.__ssrInlineRender?e.ssrRender=t:e.render=t:Ie(t)&&(e.setupState=Ao(t)),na(e,n)}let ds;function na(e,t,n){const i=e.type;if(!e.render){if(!t&&ds&&!i.render){const l=i.template||Il(e).template;if(l){const{isCustomElement:s,compilerOptions:o}=e.appContext.config,{delimiters:a,compilerOptions:r}=i,u=je(je({isCustomElement:s,delimiters:a},o),r);i.render=ds(l,u)}}e.render=i.render||st}hn(e),mn(),pc(e),vn(),Jt()}function $c(e){return new Proxy(e.attrs,{get(t,n){return Ye(e,"get","$attrs"),t[n]}})}function Mc(e){const t=i=>{e.exposed=i||{}};let n;return{get attrs(){return n||(n=$c(e))},slots:e.slots,emit:e.emit,expose:t}}function xi(e){if(e.exposed)return e.exposeProxy||(e.exposeProxy=new Proxy(Ao(Co(e.exposed)),{get(t,n){if(n in t)return t[n];if(n in In)return In[n](e)},has(t,n){return n in t||n in In}}))}function Nc(e,t=!0){return ae(e)?e.displayName||e.name:e.name||t&&e.__name}function zc(e){return ae(e)&&"__vccOpts"in e}const $=(e,t)=>Br(e,t,fn);function de(e,t,n){const i=arguments.length;return i===2?Ie(t)&&!te(t)?di(t)?ie(e,null,[t]):ie(e,t):ie(e,null,t):(i>3?n=Array.prototype.slice.call(arguments,2):i===3&&di(n)&&(n=[n]),ie(e,t,n))}const Vc=Symbol(""),Uc=()=>We(Vc),qc="3.2.45",Kc="http://www.w3.org/2000/svg",Vt=typeof document<"u"?document:null,hs=Vt&&Vt.createElement("template"),Qc={insert:(e,t,n)=>{t.insertBefore(e,n||null)},remove:e=>{const t=e.parentNode;t&&t.removeChild(e)},createElement:(e,t,n,i)=>{const l=t?Vt.createElementNS(Kc,e):Vt.createElement(e,n?{is:n}:void 0);return e==="select"&&i&&i.multiple!=null&&l.setAttribute("multiple",i.multiple),l},createText:e=>Vt.createTextNode(e),createComment:e=>Vt.createComment(e),setText:(e,t)=>{e.nodeValue=t},setElementText:(e,t)=>{e.textContent=t},parentNode:e=>e.parentNode,nextSibling:e=>e.nextSibling,querySelector:e=>Vt.querySelector(e),setScopeId(e,t){e.setAttribute(t,"")},insertStaticContent(e,t,n,i,l,s){const o=n?n.previousSibling:t.lastChild;if(l&&(l===s||l.nextSibling))for(;t.insertBefore(l.cloneNode(!0),n),!(l===s||!(l=l.nextSibling)););else{hs.innerHTML=i?`${e}`:e;const a=hs.content;if(i){const r=a.firstChild;for(;r.firstChild;)a.appendChild(r.firstChild);a.removeChild(r)}t.insertBefore(a,n)}return[o?o.nextSibling:t.firstChild,n?n.previousSibling:t.lastChild]}};function Gc(e,t,n){const i=e._vtc;i&&(t=(t?[t,...i]:[...i]).join(" ")),t==null?e.removeAttribute("class"):n?e.setAttribute("class",t):e.className=t}function Jc(e,t,n){const i=e.style,l=ve(n);if(n&&!l){for(const s in n)ll(i,s,n[s]);if(t&&!ve(t))for(const s in t)n[s]==null&&ll(i,s,"")}else{const s=i.display;l?t!==n&&(i.cssText=n):t&&e.removeAttribute("style"),"_vod"in e&&(i.display=s)}}const fs=/\s*!important$/;function ll(e,t,n){if(te(n))n.forEach(i=>ll(e,t,i));else if(n==null&&(n=""),t.startsWith("--"))e.setProperty(t,n);else{const i=Yc(e,t);fs.test(n)?e.setProperty(Yt(i),n.replace(fs,""),"important"):e[i]=n}}const ps=["Webkit","Moz","ms"],Hi={};function Yc(e,t){const n=Hi[t];if(n)return n;let i=dt(t);if(i!=="filter"&&i in e)return Hi[t]=i;i=wi(i);for(let l=0;lji||(lu.then(()=>ji=0),ji=Date.now());function ou(e,t){const n=i=>{if(!i._vts)i._vts=Date.now();else if(i._vts<=n.attached)return;et(au(i,n.value),t,5,[i])};return n.value=e,n.attached=su(),n}function au(e,t){if(te(t)){const n=e.stopImmediatePropagation;return e.stopImmediatePropagation=()=>{n.call(e),e._stopped=!0},t.map(i=>l=>!l._stopped&&i&&i(l))}else return t}const vs=/^on[a-z]/,ru=(e,t,n,i,l=!1,s,o,a,r)=>{t==="class"?Gc(e,i,l):t==="style"?Jc(e,n,i):jn(t)?dl(t)||nu(e,t,n,i,o):(t[0]==="."?(t=t.slice(1),!0):t[0]==="^"?(t=t.slice(1),!1):cu(e,t,i,l))?Zc(e,t,i,s,o,a,r):(t==="true-value"?e._trueValue=i:t==="false-value"&&(e._falseValue=i),Xc(e,t,i,l))};function cu(e,t,n,i){return i?!!(t==="innerHTML"||t==="textContent"||t in e&&vs.test(t)&&ae(n)):t==="spellcheck"||t==="draggable"||t==="translate"||t==="form"||t==="list"&&e.tagName==="INPUT"||t==="type"&&e.tagName==="TEXTAREA"||vs.test(t)&&ve(n)?!1:t in e}const Et="transition",yn="animation",Nn=(e,{slots:t})=>de(jo,uu(e),t);Nn.displayName="Transition";const ia={name:String,type:String,css:{type:Boolean,default:!0},duration:[String,Number,Object],enterFromClass:String,enterActiveClass:String,enterToClass:String,appearFromClass:String,appearActiveClass:String,appearToClass:String,leaveFromClass:String,leaveActiveClass:String,leaveToClass:String};Nn.props=je({},jo.props,ia);const Ht=(e,t=[])=>{te(e)?e.forEach(n=>n(...t)):e&&e(...t)},bs=e=>e?te(e)?e.some(t=>t.length>1):e.length>1:!1;function uu(e){const t={};for(const P in e)P in ia||(t[P]=e[P]);if(e.css===!1)return t;const{name:n="v",type:i,duration:l,enterFromClass:s=`${n}-enter-from`,enterActiveClass:o=`${n}-enter-active`,enterToClass:a=`${n}-enter-to`,appearFromClass:r=s,appearActiveClass:u=o,appearToClass:c=a,leaveFromClass:h=`${n}-leave-from`,leaveActiveClass:f=`${n}-leave-active`,leaveToClass:g=`${n}-leave-to`}=e,b=du(l),k=b&&b[0],I=b&&b[1],{onBeforeEnter:m,onEnter:w,onEnterCancelled:_,onLeave:F,onLeaveCancelled:U,onBeforeAppear:J=m,onAppear:A=w,onAppearCancelled:v=_}=t,G=(P,D,R)=>{jt(P,D?c:a),jt(P,D?u:o),R&&R()},V=(P,D)=>{P._isLeaving=!1,jt(P,h),jt(P,g),jt(P,f),D&&D()},q=P=>(D,R)=>{const re=P?A:w,N=()=>G(D,P,R);Ht(re,[D,N]),ws(()=>{jt(D,P?r:s),Ct(D,P?c:a),bs(re)||ys(D,i,k,N)})};return je(t,{onBeforeEnter(P){Ht(m,[P]),Ct(P,s),Ct(P,o)},onBeforeAppear(P){Ht(J,[P]),Ct(P,r),Ct(P,u)},onEnter:q(!1),onAppear:q(!0),onLeave(P,D){P._isLeaving=!0;const R=()=>V(P,D);Ct(P,h),pu(),Ct(P,f),ws(()=>{!P._isLeaving||(jt(P,h),Ct(P,g),bs(F)||ys(P,i,I,R))}),Ht(F,[P,R])},onEnterCancelled(P){G(P,!1),Ht(_,[P])},onAppearCancelled(P){G(P,!0),Ht(v,[P])},onLeaveCancelled(P){V(P),Ht(U,[P])}})}function du(e){if(e==null)return null;if(Ie(e))return[Bi(e.enter),Bi(e.leave)];{const t=Bi(e);return[t,t]}}function Bi(e){return gl(e)}function Ct(e,t){t.split(/\s+/).forEach(n=>n&&e.classList.add(n)),(e._vtc||(e._vtc=new Set)).add(t)}function jt(e,t){t.split(/\s+/).forEach(i=>i&&e.classList.remove(i));const{_vtc:n}=e;n&&(n.delete(t),n.size||(e._vtc=void 0))}function ws(e){requestAnimationFrame(()=>{requestAnimationFrame(e)})}let hu=0;function ys(e,t,n,i){const l=e._endId=++hu,s=()=>{l===e._endId&&i()};if(n)return setTimeout(s,n);const{type:o,timeout:a,propCount:r}=fu(e,t);if(!o)return i();const u=o+"end";let c=0;const h=()=>{e.removeEventListener(u,f),s()},f=g=>{g.target===e&&++c>=r&&h()};setTimeout(()=>{c(n[b]||"").split(", "),l=i(`${Et}Delay`),s=i(`${Et}Duration`),o=_s(l,s),a=i(`${yn}Delay`),r=i(`${yn}Duration`),u=_s(a,r);let c=null,h=0,f=0;t===Et?o>0&&(c=Et,h=o,f=s.length):t===yn?u>0&&(c=yn,h=u,f=r.length):(h=Math.max(o,u),c=h>0?o>u?Et:yn:null,f=c?c===Et?s.length:r.length:0);const g=c===Et&&/\b(transform|all)(,|$)/.test(i(`${Et}Property`).toString());return{type:c,timeout:h,propCount:f,hasTransform:g}}function _s(e,t){for(;e.lengthks(n)+ks(e[i])))}function ks(e){return Number(e.slice(0,-1).replace(",","."))*1e3}function pu(){return document.body.offsetHeight}const gu={esc:"escape",space:" ",up:"arrow-up",left:"arrow-left",right:"arrow-right",down:"arrow-down",delete:"backspace"},mu=(e,t)=>n=>{if(!("key"in n))return;const i=Yt(n.key);if(t.some(l=>l===i||gu[l]===i))return e(n)},hi={beforeMount(e,{value:t},{transition:n}){e._vod=e.style.display==="none"?"":e.style.display,n&&t?n.beforeEnter(e):_n(e,t)},mounted(e,{value:t},{transition:n}){n&&t&&n.enter(e)},updated(e,{value:t,oldValue:n},{transition:i}){!t!=!n&&(i?t?(i.beforeEnter(e),_n(e,!0),i.enter(e)):i.leave(e,()=>{_n(e,!1)}):_n(e,t))},beforeUnmount(e,{value:t}){_n(e,t)}};function _n(e,t){e.style.display=t?e._vod:"none"}const vu=je({patchProp:ru},Qc);let $i,Es=!1;function bu(){return $i=Es?$i:Lc(vu),Es=!0,$i}const wu=(...e)=>{const t=bu().createApp(...e),{mount:n}=t;return t.mount=i=>{const l=yu(i);if(l)return n(l,!0,l instanceof SVGElement)},t};function yu(e){return ve(e)?document.querySelector(e):e}const _u=JSON.parse('{"base":"/","lang":"en-US","title":"Wasabi Docs","description":"An archive of knowledge about Wasabi Wallet, an open-source, non-custodial and privacy-focused Bitcoin wallet for desktop.","head":[],"locales":{}}');var ku=([e,t,n])=>e==="meta"&&t.name?`${e}.${t.name}`:["title","base"].includes(e)?e:e==="template"&&t.id?`${e}.${t.id}`:JSON.stringify([e,t,n]),Eu=e=>{const t=new Set,n=[];return e.forEach(i=>{const l=ku(i);t.has(l)||(t.add(l),n.push(i))}),n},zn=e=>/^(https?:)?\/\//.test(e),Cu=e=>/^mailto:/.test(e),Pu=e=>/^tel:/.test(e),Al=e=>Object.prototype.toString.call(e)==="[object Object]",la=e=>e.replace(/\/$/,""),sa=e=>e.replace(/^\//,""),oa=(e,t)=>{const n=Object.keys(e).sort((i,l)=>{const s=l.split("/").length-i.split("/").length;return s!==0?s:l.length-i.length});for(const i of n)if(t.startsWith(i))return i;return"/"};const aa={"v-8daa1a0e":ee(()=>x(()=>import("./index.html.5ce1fb70.js"),[])),"v-5a6b3f40":ee(()=>x(()=>import("./FAQ-Contribution.html.07903300.js"),["assets/FAQ-Contribution.html.07903300.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-6b95acd0":ee(()=>x(()=>import("./FAQ-GeneralBitcoinPrivacy.html.29415500.js"),[])),"v-dbdf1f14":ee(()=>x(()=>import("./FAQ-Installation.html.0c83c076.js"),["assets/FAQ-Installation.html.0c83c076.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/DownloadMac.90ece9d0.js"])),"v-1a6aa296":ee(()=>x(()=>import("./FAQ-Introduction.html.e96f1243.js"),["assets/FAQ-Introduction.html.e96f1243.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-48b5cdc8":ee(()=>x(()=>import("./FAQ-UseWasabi.html.f98cdbbe.js"),["assets/FAQ-UseWasabi.html.f98cdbbe.js","assets/AddWalletButton.98ad9c28.js","assets/AddWalletAddPassword.45b736a5.js","assets/AddWalletConfirmRecoveryWords.2792528c.js","assets/CoinjoinStrategy.5455b7fb.js","assets/WalletSynchronizing.d188367c.js","assets/AddressAwaitingPayment.1f3f0347.js","assets/HistoryRightClick.a729d6cb.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/AutoStartCoinjoinThreshold.908ffaab.js","assets/SettingsBitcoinCore.fab2a9f8.js","assets/DiscreetModeActivate.e372f614.js"])),"v-74379e72":ee(()=>x(()=>import("./index.html.8ac9939d.js"),[])),"v-daad2d5a":ee(()=>x(()=>import("./ContributionChecklist.html.d5d11b35.js"),[])),"v-50472b68":ee(()=>x(()=>import("./LICENSE.html.005bab57.js"),[])),"v-1488a610":ee(()=>x(()=>import("./index.html.395ec914.js"),[])),"v-7a003569":ee(()=>x(()=>import("./Security.html.83f2992c.js"),[])),"v-ccdc4da0":ee(()=>x(()=>import("./index.html.b14d7a34.js"),[])),"v-6fa52768":ee(()=>x(()=>import("./Glossary-GeneralBitcoin.html.ec5f1d03.js"),[])),"v-ceb6ce6e":ee(()=>x(()=>import("./Glossary-PrivacyWasabi.html.33993b7b.js"),[])),"v-338f4ef8":ee(()=>x(()=>import("./index.html.f6c79981.js"),[])),"v-93f154be":ee(()=>x(()=>import("./BIPs.html.c05a0bab.js"),[])),"v-9880f756":ee(()=>x(()=>import("./BackupBestPractices.html.fdb12de8.js"),[])),"v-35466110":ee(()=>x(()=>import("./BitcoinFullNode.html.d412c934.js"),["assets/BitcoinFullNode.html.d412c934.js","assets/SettingsBitcoinCore.fab2a9f8.js"])),"v-9f999a04":ee(()=>x(()=>import("./BuildSource.html.4c0a7387.js"),[])),"v-c0f49ad6":ee(()=>x(()=>import("./ChangeCoins.html.5adcd926.js"),[])),"v-9f951f20":ee(()=>x(()=>import("./CoinJoin.html.d7f3ac7c.js"),["assets/CoinJoin.html.d7f3ac7c.js","assets/AutoStartCoinjoinThreshold.908ffaab.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-6ba5ff68":ee(()=>x(()=>import("./ColdWasabi.html.54e9c212.js"),[])),"v-dd3fd132":ee(()=>x(()=>import("./Daemon.html.7884d930.js"),[])),"v-53e5ec6f":ee(()=>x(()=>import("./DeterministicBuild.html.f5a63f91.js"),[])),"v-5d4dd2b1":ee(()=>x(()=>import("./DiscreetMode.html.11ff0e7b.js"),["assets/DiscreetMode.html.11ff0e7b.js","assets/DiscreetModeActivate.e372f614.js"])),"v-633fd810":ee(()=>x(()=>import("./ELI5.html.14e7fa96.js"),[])),"v-18287a20":ee(()=>x(()=>import("./InstallPackage.html.d192894b.js"),["assets/InstallPackage.html.d192894b.js","assets/DownloadMac.90ece9d0.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-2206b16e":ee(()=>x(()=>import("./PasswordBestPractices.html.d41d69dd.js"),[])),"v-10ab876a":ee(()=>x(()=>import("./PasswordFinder.html.3173dc09.js"),[])),"v-28d891d5":ee(()=>x(()=>import("./PayJoin.html.60688e0c.js"),[])),"v-019de88e":ee(()=>x(()=>import("./index.html.1b5ce783.js"),[])),"v-cb675e7c":ee(()=>x(()=>import("./RPC.html.3799b39e.js"),[])),"v-61c4fb84":ee(()=>x(()=>import("./Receive.html.6bc14701.js"),["assets/Receive.html.6bc14701.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/AddressAwaitingPayment.1f3f0347.js"])),"v-34d39e44":ee(()=>x(()=>import("./RestoreElectrum.html.0073b508.js"),[])),"v-0495dd63":ee(()=>x(()=>import("./Send.html.2b25f94b.js"),["assets/Send.html.2b25f94b.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/HistoryRightClick.a729d6cb.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-03767b9c":ee(()=>x(()=>import("./Testnet.html.c098c41f.js"),[])),"v-e69d74cc":ee(()=>x(()=>import("./WalletGeneration.html.79c8be3e.js"),["assets/WalletGeneration.html.79c8be3e.js","assets/AddWalletAddPassword.45b736a5.js","assets/AddWalletConfirmRecoveryWords.2792528c.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-74a0b14c":ee(()=>x(()=>import("./WalletLoad.html.23ac7679.js"),["assets/WalletLoad.html.23ac7679.js","assets/WalletSynchronizing.d188367c.js"])),"v-059a5106":ee(()=>x(()=>import("./WalletRecovery.html.1d4fe6d7.js"),["assets/WalletRecovery.html.1d4fe6d7.js","assets/AddWalletButton.98ad9c28.js","assets/AddWalletAddPassword.45b736a5.js"])),"v-abde19dc":ee(()=>x(()=>import("./WasabiSetupVM.html.6d5d7c76.js"),[])),"v-91cac2f2":ee(()=>x(()=>import("./AddressReuse.html.12293165.js"),[])),"v-e8d6a56e":ee(()=>x(()=>import("./Coins.html.6eed3b2b.js"),[])),"v-6b334fc0":ee(()=>x(()=>import("./LegalConcern.html.c1cbc8f2.js"),[])),"v-e10ef9ce":ee(()=>x(()=>import("./NetworkLevelPrivacy.html.73464f1b.js"),["assets/NetworkLevelPrivacy.html.73464f1b.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-40d3d192":ee(()=>x(()=>import("./index.html.91658148.js"),[])),"v-1038df57":ee(()=>x(()=>import("./TransactionGraph.html.e4b715af.js"),[])),"v-35a4d9e3":ee(()=>x(()=>import("./TransactionSurveillanceCompanies.html.f6da66b3.js"),[])),"v-0b19ce44":ee(()=>x(()=>import("./WhyFinancialPrivacy.html.6e6ac971.js"),[])),"v-19b5df2e":ee(()=>x(()=>import("./WhyPrivacyImportant.html.70fbf5db.js"),["assets/WhyPrivacyImportant.html.70fbf5db.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-3706649a":ee(()=>x(()=>import("./404.html.699a943a.js"),[]))};var Wt=(e={})=>e;function ra(e,t,n){var i,l,s;t===void 0&&(t=50),n===void 0&&(n={});var o=(i=n.isImmediate)!=null&&i,a=(l=n.callback)!=null&&l,r=n.maxWait,u=Date.now(),c=[];function h(){if(r!==void 0){var g=Date.now()-u;if(g+t>=r)return r-g}return t}var f=function(){var g=[].slice.call(arguments),b=this;return new Promise(function(k,I){var m=o&&s===void 0;if(s!==void 0&&clearTimeout(s),s=setTimeout(function(){if(s=void 0,u=Date.now(),!o){var _=e.apply(b,g);a&&a(_),c.forEach(function(F){return(0,F.resolve)(_)}),c=[]}},h()),m){var w=e.apply(b,g);return a&&a(w),k(w)}c.push({resolve:k,reject:I})})};return f.cancel=function(g){s!==void 0&&clearTimeout(s),c.forEach(function(b){return(0,b.reject)(g)}),c=[]},f}/*!
+const Na="modulepreload",za=function(e){return"/"+e},Vl={},x=function(t,n,i){return!n||n.length===0?t():Promise.all(n.map(l=>{if(l=za(l),l in Vl)return;Vl[l]=!0;const s=l.endsWith(".css"),o=s?'[rel="stylesheet"]':"";if(document.querySelector(`link[href="${l}"]${o}`))return;const a=document.createElement("link");if(a.rel=s?"stylesheet":Na,s||(a.as="script",a.crossOrigin=""),a.href=l,document.head.appendChild(a),s)return new Promise((r,u)=>{a.addEventListener("load",r),a.addEventListener("error",()=>u(new Error(`Unable to preload CSS for ${l}`)))})})).then(()=>t())},Va={"v-8daa1a0e":()=>x(()=>import("./index.html.efbdb3bf.js"),[]).then(({data:e})=>e),"v-5a6b3f40":()=>x(()=>import("./FAQ-Contribution.html.a5662063.js"),[]).then(({data:e})=>e),"v-6b95acd0":()=>x(()=>import("./FAQ-GeneralBitcoinPrivacy.html.f2cc196a.js"),[]).then(({data:e})=>e),"v-dbdf1f14":()=>x(()=>import("./FAQ-Installation.html.c6a7fa06.js"),[]).then(({data:e})=>e),"v-1a6aa296":()=>x(()=>import("./FAQ-Introduction.html.51f9b016.js"),[]).then(({data:e})=>e),"v-48b5cdc8":()=>x(()=>import("./FAQ-UseWasabi.html.1cefe63f.js"),[]).then(({data:e})=>e),"v-74379e72":()=>x(()=>import("./index.html.38c9d31b.js"),[]).then(({data:e})=>e),"v-daad2d5a":()=>x(()=>import("./ContributionChecklist.html.f454f51d.js"),[]).then(({data:e})=>e),"v-50472b68":()=>x(()=>import("./LICENSE.html.cca271db.js"),[]).then(({data:e})=>e),"v-1488a610":()=>x(()=>import("./index.html.51b0c8cf.js"),[]).then(({data:e})=>e),"v-7a003569":()=>x(()=>import("./Security.html.68fe1c05.js"),[]).then(({data:e})=>e),"v-ccdc4da0":()=>x(()=>import("./index.html.11c955f3.js"),[]).then(({data:e})=>e),"v-6fa52768":()=>x(()=>import("./Glossary-GeneralBitcoin.html.af0d3606.js"),[]).then(({data:e})=>e),"v-ceb6ce6e":()=>x(()=>import("./Glossary-PrivacyWasabi.html.ea52aaf7.js"),[]).then(({data:e})=>e),"v-338f4ef8":()=>x(()=>import("./index.html.f476e799.js"),[]).then(({data:e})=>e),"v-93f154be":()=>x(()=>import("./BIPs.html.d3a69602.js"),[]).then(({data:e})=>e),"v-9880f756":()=>x(()=>import("./BackupBestPractices.html.76bd62a5.js"),[]).then(({data:e})=>e),"v-35466110":()=>x(()=>import("./BitcoinFullNode.html.7483e163.js"),[]).then(({data:e})=>e),"v-9f999a04":()=>x(()=>import("./BuildSource.html.a974ba78.js"),[]).then(({data:e})=>e),"v-c0f49ad6":()=>x(()=>import("./ChangeCoins.html.c35ce720.js"),[]).then(({data:e})=>e),"v-9f951f20":()=>x(()=>import("./CoinJoin.html.25ac80dc.js"),[]).then(({data:e})=>e),"v-6ba5ff68":()=>x(()=>import("./ColdWasabi.html.220be9ba.js"),[]).then(({data:e})=>e),"v-dd3fd132":()=>x(()=>import("./Daemon.html.9923648f.js"),[]).then(({data:e})=>e),"v-53e5ec6f":()=>x(()=>import("./DeterministicBuild.html.0565f895.js"),[]).then(({data:e})=>e),"v-5d4dd2b1":()=>x(()=>import("./DiscreetMode.html.c246eee4.js"),[]).then(({data:e})=>e),"v-633fd810":()=>x(()=>import("./ELI5.html.3d49d084.js"),[]).then(({data:e})=>e),"v-18287a20":()=>x(()=>import("./InstallPackage.html.a6d7056b.js"),[]).then(({data:e})=>e),"v-2206b16e":()=>x(()=>import("./PasswordBestPractices.html.cb13edf6.js"),[]).then(({data:e})=>e),"v-10ab876a":()=>x(()=>import("./PasswordFinder.html.a9ebb851.js"),[]).then(({data:e})=>e),"v-28d891d5":()=>x(()=>import("./PayJoin.html.b30eddd3.js"),[]).then(({data:e})=>e),"v-019de88e":()=>x(()=>import("./index.html.5550cce2.js"),[]).then(({data:e})=>e),"v-cb675e7c":()=>x(()=>import("./RPC.html.9aba61fe.js"),[]).then(({data:e})=>e),"v-61c4fb84":()=>x(()=>import("./Receive.html.f15c1a36.js"),[]).then(({data:e})=>e),"v-34d39e44":()=>x(()=>import("./RestoreElectrum.html.15cce134.js"),[]).then(({data:e})=>e),"v-0495dd63":()=>x(()=>import("./Send.html.41ed2b96.js"),[]).then(({data:e})=>e),"v-03767b9c":()=>x(()=>import("./Testnet.html.aea4daa1.js"),[]).then(({data:e})=>e),"v-e69d74cc":()=>x(()=>import("./WalletGeneration.html.2062fbaf.js"),[]).then(({data:e})=>e),"v-74a0b14c":()=>x(()=>import("./WalletLoad.html.b25174fa.js"),[]).then(({data:e})=>e),"v-059a5106":()=>x(()=>import("./WalletRecovery.html.310647b0.js"),[]).then(({data:e})=>e),"v-abde19dc":()=>x(()=>import("./WasabiSetupVM.html.0044e6e5.js"),[]).then(({data:e})=>e),"v-91cac2f2":()=>x(()=>import("./AddressReuse.html.260e762c.js"),[]).then(({data:e})=>e),"v-e8d6a56e":()=>x(()=>import("./Coins.html.b6fb2be3.js"),[]).then(({data:e})=>e),"v-6b334fc0":()=>x(()=>import("./LegalConcern.html.900695db.js"),[]).then(({data:e})=>e),"v-e10ef9ce":()=>x(()=>import("./NetworkLevelPrivacy.html.f0783852.js"),[]).then(({data:e})=>e),"v-40d3d192":()=>x(()=>import("./index.html.5fa14c07.js"),[]).then(({data:e})=>e),"v-1038df57":()=>x(()=>import("./TransactionGraph.html.0e9dd3d6.js"),[]).then(({data:e})=>e),"v-35a4d9e3":()=>x(()=>import("./TransactionSurveillanceCompanies.html.388b9cd4.js"),[]).then(({data:e})=>e),"v-0b19ce44":()=>x(()=>import("./WhyFinancialPrivacy.html.d449301d.js"),[]).then(({data:e})=>e),"v-19b5df2e":()=>x(()=>import("./WhyPrivacyImportant.html.3c610b4f.js"),[]).then(({data:e})=>e),"v-3706649a":()=>x(()=>import("./404.html.d2dc3323.js"),[]).then(({data:e})=>e)};function ul(e,t){const n=Object.create(null),i=e.split(",");for(let l=0;l!!n[l.toLowerCase()]:l=>!!n[l]}function Hn(e){if(te(e)){const t={};for(let n=0;n{if(n){const i=n.split(qa);i.length>1&&(t[i[0].trim()]=i[1].trim())}}),t}function qe(e){let t="";if(ve(e))t=e;else if(te(e))for(let n=0;nve(e)?e:e==null?"":te(e)||Ie(e)&&(e.toString===uo||!ae(e.toString))?JSON.stringify(e,ao,2):String(e),ao=(e,t)=>t&&t.__v_isRef?ao(e,t.value):on(t)?{[`Map(${t.size})`]:[...t.entries()].reduce((n,[i,l])=>(n[`${i} =>`]=l,n),{})}:ro(t)?{[`Set(${t.size})`]:[...t.values()]}:Ie(t)&&!te(t)&&!ho(t)?String(t):t,Pe={},sn=[],st=()=>{},Ya=()=>!1,Xa=/^on[^a-z]/,jn=e=>Xa.test(e),dl=e=>e.startsWith("onUpdate:"),je=Object.assign,hl=(e,t)=>{const n=e.indexOf(t);n>-1&&e.splice(n,1)},Za=Object.prototype.hasOwnProperty,pe=(e,t)=>Za.call(e,t),te=Array.isArray,on=e=>vi(e)==="[object Map]",ro=e=>vi(e)==="[object Set]",ae=e=>typeof e=="function",ve=e=>typeof e=="string",fl=e=>typeof e=="symbol",Ie=e=>e!==null&&typeof e=="object",co=e=>Ie(e)&&ae(e.then)&&ae(e.catch),uo=Object.prototype.toString,vi=e=>uo.call(e),er=e=>vi(e).slice(8,-1),ho=e=>vi(e)==="[object Object]",pl=e=>ve(e)&&e!=="NaN"&&e[0]!=="-"&&""+parseInt(e,10)===e,Pn=ul(",key,ref,ref_for,ref_key,onVnodeBeforeMount,onVnodeMounted,onVnodeBeforeUpdate,onVnodeUpdated,onVnodeBeforeUnmount,onVnodeUnmounted"),bi=e=>{const t=Object.create(null);return n=>t[n]||(t[n]=e(n))},tr=/-(\w)/g,dt=bi(e=>e.replace(tr,(t,n)=>n?n.toUpperCase():"")),nr=/\B([A-Z])/g,Yt=bi(e=>e.replace(nr,"-$1").toLowerCase()),wi=bi(e=>e.charAt(0).toUpperCase()+e.slice(1)),Si=bi(e=>e?`on${wi(e)}`:""),Sn=(e,t)=>!Object.is(e,t),Ri=(e,t)=>{for(let n=0;n{Object.defineProperty(e,t,{configurable:!0,enumerable:!1,value:n})},gl=e=>{const t=parseFloat(e);return isNaN(t)?e:t};let Ul;const ir=()=>Ul||(Ul=typeof globalThis<"u"?globalThis:typeof self<"u"?self:typeof window<"u"?window:typeof global<"u"?global:{});let Ge;class lr{constructor(t=!1){this.detached=t,this.active=!0,this.effects=[],this.cleanups=[],this.parent=Ge,!t&&Ge&&(this.index=(Ge.scopes||(Ge.scopes=[])).push(this)-1)}run(t){if(this.active){const n=Ge;try{return Ge=this,t()}finally{Ge=n}}}on(){Ge=this}off(){Ge=this.parent}stop(t){if(this.active){let n,i;for(n=0,i=this.effects.length;n{const t=new Set(e);return t.w=0,t.n=0,t},fo=e=>(e.w&Tt)>0,po=e=>(e.n&Tt)>0,rr=({deps:e})=>{if(e.length)for(let t=0;t{const{deps:t}=e;if(t.length){let n=0;for(let i=0;i{(c==="length"||c>=r)&&a.push(u)})}else switch(n!==void 0&&a.push(o.get(n)),t){case"add":te(e)?pl(n)&&a.push(o.get("length")):(a.push(o.get(Qt)),on(e)&&a.push(o.get(Qi)));break;case"delete":te(e)||(a.push(o.get(Qt)),on(e)&&a.push(o.get(Qi)));break;case"set":on(e)&&a.push(o.get(Qt));break}if(a.length===1)a[0]&&Gi(a[0]);else{const r=[];for(const u of a)u&&r.push(...u);Gi(ml(r))}}function Gi(e,t){const n=te(e)?e:[...e];for(const i of n)i.computed&&Kl(i);for(const i of n)i.computed||Kl(i)}function Kl(e,t){(e!==it||e.allowRecurse)&&(e.scheduler?e.scheduler():e.run())}const ur=ul("__proto__,__v_isRef,__isVue"),vo=new Set(Object.getOwnPropertyNames(Symbol).filter(e=>e!=="arguments"&&e!=="caller").map(e=>Symbol[e]).filter(fl)),dr=bl(),hr=bl(!1,!0),fr=bl(!0),Ql=pr();function pr(){const e={};return["includes","indexOf","lastIndexOf"].forEach(t=>{e[t]=function(...n){const i=me(this);for(let s=0,o=this.length;s{e[t]=function(...n){mn();const i=me(this)[t].apply(this,n);return vn(),i}}),e}function bl(e=!1,t=!1){return function(i,l,s){if(l==="__v_isReactive")return!e;if(l==="__v_isReadonly")return e;if(l==="__v_isShallow")return t;if(l==="__v_raw"&&s===(e?t?Tr:ko:t?_o:yo).get(i))return i;const o=te(i);if(!e&&o&&pe(Ql,l))return Reflect.get(Ql,l,s);const a=Reflect.get(i,l,s);return(fl(l)?vo.has(l):ur(l))||(e||Ye(i,"get",l),t)?a:Fe(a)?o&&pl(l)?a:a.value:Ie(a)?e?_l(a):bn(a):a}}const gr=bo(),mr=bo(!0);function bo(e=!1){return function(n,i,l,s){let o=n[i];if(un(o)&&Fe(o)&&!Fe(l))return!1;if(!e&&(!si(l)&&!un(l)&&(o=me(o),l=me(l)),!te(n)&&Fe(o)&&!Fe(l)))return o.value=l,!0;const a=te(n)&&pl(i)?Number(i)e,yi=e=>Reflect.getPrototypeOf(e);function Un(e,t,n=!1,i=!1){e=e.__v_raw;const l=me(e),s=me(t);n||(t!==s&&Ye(l,"get",t),Ye(l,"get",s));const{has:o}=yi(l),a=i?wl:n?El:Rn;if(o.call(l,t))return a(e.get(t));if(o.call(l,s))return a(e.get(s));e!==l&&e.get(t)}function qn(e,t=!1){const n=this.__v_raw,i=me(n),l=me(e);return t||(e!==l&&Ye(i,"has",e),Ye(i,"has",l)),e===l?n.has(e):n.has(e)||n.has(l)}function Kn(e,t=!1){return e=e.__v_raw,!t&&Ye(me(e),"iterate",Qt),Reflect.get(e,"size",e)}function Gl(e){e=me(e);const t=me(this);return yi(t).has.call(t,e)||(t.add(e),vt(t,"add",e,e)),this}function Jl(e,t){t=me(t);const n=me(this),{has:i,get:l}=yi(n);let s=i.call(n,e);s||(e=me(e),s=i.call(n,e));const o=l.call(n,e);return n.set(e,t),s?Sn(t,o)&&vt(n,"set",e,t):vt(n,"add",e,t),this}function Yl(e){const t=me(this),{has:n,get:i}=yi(t);let l=n.call(t,e);l||(e=me(e),l=n.call(t,e)),i&&i.call(t,e);const s=t.delete(e);return l&&vt(t,"delete",e,void 0),s}function Xl(){const e=me(this),t=e.size!==0,n=e.clear();return t&&vt(e,"clear",void 0,void 0),n}function Qn(e,t){return function(i,l){const s=this,o=s.__v_raw,a=me(o),r=t?wl:e?El:Rn;return!e&&Ye(a,"iterate",Qt),o.forEach((u,c)=>i.call(l,r(u),r(c),s))}}function Gn(e,t,n){return function(...i){const l=this.__v_raw,s=me(l),o=on(s),a=e==="entries"||e===Symbol.iterator&&o,r=e==="keys"&&o,u=l[e](...i),c=n?wl:t?El:Rn;return!t&&Ye(s,"iterate",r?Qi:Qt),{next(){const{value:h,done:f}=u.next();return f?{value:h,done:f}:{value:a?[c(h[0]),c(h[1])]:c(h),done:f}},[Symbol.iterator](){return this}}}}function _t(e){return function(...t){return e==="delete"?!1:this}}function kr(){const e={get(s){return Un(this,s)},get size(){return Kn(this)},has:qn,add:Gl,set:Jl,delete:Yl,clear:Xl,forEach:Qn(!1,!1)},t={get(s){return Un(this,s,!1,!0)},get size(){return Kn(this)},has:qn,add:Gl,set:Jl,delete:Yl,clear:Xl,forEach:Qn(!1,!0)},n={get(s){return Un(this,s,!0)},get size(){return Kn(this,!0)},has(s){return qn.call(this,s,!0)},add:_t("add"),set:_t("set"),delete:_t("delete"),clear:_t("clear"),forEach:Qn(!0,!1)},i={get(s){return Un(this,s,!0,!0)},get size(){return Kn(this,!0)},has(s){return qn.call(this,s,!0)},add:_t("add"),set:_t("set"),delete:_t("delete"),clear:_t("clear"),forEach:Qn(!0,!0)};return["keys","values","entries",Symbol.iterator].forEach(s=>{e[s]=Gn(s,!1,!1),n[s]=Gn(s,!0,!1),t[s]=Gn(s,!1,!0),i[s]=Gn(s,!0,!0)}),[e,n,t,i]}const[Er,Cr,Pr,Ir]=kr();function yl(e,t){const n=t?e?Ir:Pr:e?Cr:Er;return(i,l,s)=>l==="__v_isReactive"?!e:l==="__v_isReadonly"?e:l==="__v_raw"?i:Reflect.get(pe(n,l)&&l in i?n:i,l,s)}const Lr={get:yl(!1,!1)},xr={get:yl(!1,!0)},Ar={get:yl(!0,!1)},yo=new WeakMap,_o=new WeakMap,ko=new WeakMap,Tr=new WeakMap;function Sr(e){switch(e){case"Object":case"Array":return 1;case"Map":case"Set":case"WeakMap":case"WeakSet":return 2;default:return 0}}function Rr(e){return e.__v_skip||!Object.isExtensible(e)?0:Sr(er(e))}function bn(e){return un(e)?e:kl(e,!1,wo,Lr,yo)}function Or(e){return kl(e,!1,_r,xr,_o)}function _l(e){return kl(e,!0,yr,Ar,ko)}function kl(e,t,n,i,l){if(!Ie(e)||e.__v_raw&&!(t&&e.__v_isReactive))return e;const s=l.get(e);if(s)return s;const o=Rr(e);if(o===0)return e;const a=new Proxy(e,o===2?i:n);return l.set(e,a),a}function an(e){return un(e)?an(e.__v_raw):!!(e&&e.__v_isReactive)}function un(e){return!!(e&&e.__v_isReadonly)}function si(e){return!!(e&&e.__v_isShallow)}function Eo(e){return an(e)||un(e)}function me(e){const t=e&&e.__v_raw;return t?me(t):e}function Co(e){return li(e,"__v_skip",!0),e}const Rn=e=>Ie(e)?bn(e):e,El=e=>Ie(e)?_l(e):e;function Po(e){Lt&&it&&(e=me(e),mo(e.dep||(e.dep=ml())))}function Io(e,t){e=me(e),e.dep&&Gi(e.dep)}function Fe(e){return!!(e&&e.__v_isRef===!0)}function be(e){return xo(e,!1)}function Lo(e){return xo(e,!0)}function xo(e,t){return Fe(e)?e:new Wr(e,t)}class Wr{constructor(t,n){this.__v_isShallow=n,this.dep=void 0,this.__v_isRef=!0,this._rawValue=n?t:me(t),this._value=n?t:Rn(t)}get value(){return Po(this),this._value}set value(t){const n=this.__v_isShallow||si(t)||un(t);t=n?t:me(t),Sn(t,this._rawValue)&&(this._rawValue=t,this._value=n?t:Rn(t),Io(this))}}function S(e){return Fe(e)?e.value:e}const Fr={get:(e,t,n)=>S(Reflect.get(e,t,n)),set:(e,t,n,i)=>{const l=e[t];return Fe(l)&&!Fe(n)?(l.value=n,!0):Reflect.set(e,t,n,i)}};function Ao(e){return an(e)?e:new Proxy(e,Fr)}function _i(e){const t=te(e)?new Array(e.length):{};for(const n in e)t[n]=Hr(e,n);return t}class Dr{constructor(t,n,i){this._object=t,this._key=n,this._defaultValue=i,this.__v_isRef=!0}get value(){const t=this._object[this._key];return t===void 0?this._defaultValue:t}set value(t){this._object[this._key]=t}}function Hr(e,t,n){const i=e[t];return Fe(i)?i:new Dr(e,t,n)}var To;class jr{constructor(t,n,i,l){this._setter=n,this.dep=void 0,this.__v_isRef=!0,this[To]=!1,this._dirty=!0,this.effect=new vl(t,()=>{this._dirty||(this._dirty=!0,Io(this))}),this.effect.computed=this,this.effect.active=this._cacheable=!l,this.__v_isReadonly=i}get value(){const t=me(this);return Po(t),(t._dirty||!t._cacheable)&&(t._dirty=!1,t._value=t.effect.run()),t._value}set value(t){this._setter(t)}}To="__v_isReadonly";function Br(e,t,n=!1){let i,l;const s=ae(e);return s?(i=e,l=st):(i=e.get,l=e.set),new jr(i,l,s||!l,n)}function xt(e,t,n,i){let l;try{l=i?e(...i):e()}catch(s){Bn(s,t,n)}return l}function et(e,t,n,i){if(ae(e)){const s=xt(e,t,n,i);return s&&co(s)&&s.catch(o=>{Bn(o,t,n)}),s}const l=[];for(let s=0;s>>1;Wn(Me[i])ct&&Me.splice(t,1)}function zr(e){te(e)?rn.push(...e):(!pt||!pt.includes(e,e.allowRecurse?Nt+1:Nt))&&rn.push(e),Ro()}function Zl(e,t=On?ct+1:0){for(;tWn(n)-Wn(i)),Nt=0;Nte.id==null?1/0:e.id,Vr=(e,t)=>{const n=Wn(e)-Wn(t);if(n===0){if(e.pre&&!t.pre)return-1;if(t.pre&&!e.pre)return 1}return n};function Oo(e){Ji=!1,On=!0,Me.sort(Vr);const t=st;try{for(ct=0;ctve(g)?g.trim():g)),h&&(l=n.map(gl))}let a,r=i[a=Si(t)]||i[a=Si(dt(t))];!r&&s&&(r=i[a=Si(Yt(t))]),r&&et(r,e,6,l);const u=i[a+"Once"];if(u){if(!e.emitted)e.emitted={};else if(e.emitted[a])return;e.emitted[a]=!0,et(u,e,6,l)}}function Wo(e,t,n=!1){const i=t.emitsCache,l=i.get(e);if(l!==void 0)return l;const s=e.emits;let o={},a=!1;if(!ae(e)){const r=u=>{const c=Wo(u,t,!0);c&&(a=!0,je(o,c))};!n&&t.mixins.length&&t.mixins.forEach(r),e.extends&&r(e.extends),e.mixins&&e.mixins.forEach(r)}return!s&&!a?(Ie(e)&&i.set(e,null),null):(te(s)?s.forEach(r=>o[r]=null):je(o,s),Ie(e)&&i.set(e,o),o)}function Ci(e,t){return!e||!jn(t)?!1:(t=t.slice(2).replace(/Once$/,""),pe(e,t[0].toLowerCase()+t.slice(1))||pe(e,Yt(t))||pe(e,t))}let He=null,Fo=null;function ai(e){const t=He;return He=e,Fo=e&&e.type.__scopeId||null,t}function De(e,t=He,n){if(!t||e._n)return e;const i=(...l)=>{i._d&&cs(-1);const s=ai(t);let o;try{o=e(...l)}finally{ai(s),i._d&&cs(1)}return o};return i._n=!0,i._c=!0,i._d=!0,i}function Oi(e){const{type:t,vnode:n,proxy:i,withProxy:l,props:s,propsOptions:[o],slots:a,attrs:r,emit:u,render:c,renderCache:h,data:f,setupState:g,ctx:b,inheritAttrs:k}=e;let I,m;const w=ai(e);try{if(n.shapeFlag&4){const F=l||i;I=nt(c.call(F,F,h,s,g,f,b)),m=r}else{const F=t;I=nt(F.length>1?F(s,{attrs:r,slots:a,emit:u}):F(s,null)),m=t.props?r:qr(r)}}catch(F){xn.length=0,Bn(F,e,1),I=ie(Je)}let _=I;if(m&&k!==!1){const F=Object.keys(m),{shapeFlag:U}=_;F.length&&U&7&&(o&&F.some(dl)&&(m=Kr(m,o)),_=Rt(_,m))}return n.dirs&&(_=Rt(_),_.dirs=_.dirs?_.dirs.concat(n.dirs):n.dirs),n.transition&&(_.transition=n.transition),I=_,ai(w),I}const qr=e=>{let t;for(const n in e)(n==="class"||n==="style"||jn(n))&&((t||(t={}))[n]=e[n]);return t},Kr=(e,t)=>{const n={};for(const i in e)(!dl(i)||!(i.slice(9)in t))&&(n[i]=e[i]);return n};function Qr(e,t,n){const{props:i,children:l,component:s}=e,{props:o,children:a,patchFlag:r}=t,u=s.emitsOptions;if(t.dirs||t.transition)return!0;if(n&&r>=0){if(r&1024)return!0;if(r&16)return i?es(i,o,u):!!o;if(r&8){const c=t.dynamicProps;for(let h=0;he.__isSuspense;function Do(e,t){t&&t.pendingBranch?te(e)?t.effects.push(...e):t.effects.push(e):zr(e)}function Gt(e,t){if(Re){let n=Re.provides;const i=Re.parent&&Re.parent.provides;i===n&&(n=Re.provides=Object.create(i)),n[e]=t}}function We(e,t,n=!1){const i=Re||He;if(i){const l=i.parent==null?i.vnode.appContext&&i.vnode.appContext.provides:i.parent.provides;if(l&&e in l)return l[e];if(arguments.length>1)return n&&ae(t)?t.call(i.proxy):t}}function Yr(e,t){return Pl(e,null,t)}const Jn={};function ut(e,t,n){return Pl(e,t,n)}function Pl(e,t,{immediate:n,deep:i,flush:l,onTrack:s,onTrigger:o}=Pe){const a=Re;let r,u=!1,c=!1;if(Fe(e)?(r=()=>e.value,u=si(e)):an(e)?(r=()=>e,i=!0):te(e)?(c=!0,u=e.some(_=>an(_)||si(_)),r=()=>e.map(_=>{if(Fe(_))return _.value;if(an(_))return qt(_);if(ae(_))return xt(_,a,2)})):ae(e)?t?r=()=>xt(e,a,2):r=()=>{if(!(a&&a.isUnmounted))return h&&h(),et(e,a,3,[f])}:r=st,t&&i){const _=r;r=()=>qt(_())}let h,f=_=>{h=m.onStop=()=>{xt(_,a,4)}},g;if(fn)if(f=st,t?n&&et(t,a,3,[r(),c?[]:void 0,f]):r(),l==="sync"){const _=Uc();g=_.__watcherHandles||(_.__watcherHandles=[])}else return st;let b=c?new Array(e.length).fill(Jn):Jn;const k=()=>{if(!!m.active)if(t){const _=m.run();(i||u||(c?_.some((F,U)=>Sn(F,b[U])):Sn(_,b)))&&(h&&h(),et(t,a,3,[_,b===Jn?void 0:c&&b[0]===Jn?[]:b,f]),b=_)}else m.run()};k.allowRecurse=!!t;let I;l==="sync"?I=k:l==="post"?I=()=>Ue(k,a&&a.suspense):(k.pre=!0,a&&(k.id=a.uid),I=()=>Ei(k));const m=new vl(r,I);t?n?k():b=m.run():l==="post"?Ue(m.run.bind(m),a&&a.suspense):m.run();const w=()=>{m.stop(),a&&a.scope&&hl(a.scope.effects,m)};return g&&g.push(w),w}function Xr(e,t,n){const i=this.proxy,l=ve(e)?e.includes(".")?Ho(i,e):()=>i[e]:e.bind(i,i);let s;ae(t)?s=t:(s=t.handler,n=t);const o=Re;hn(this);const a=Pl(l,s.bind(i),n);return o?hn(o):Jt(),a}function Ho(e,t){const n=t.split(".");return()=>{let i=e;for(let l=0;l{qt(n,t)});else if(ho(e))for(const n in e)qt(e[n],t);return e}function Zr(){const e={isMounted:!1,isLeaving:!1,isUnmounting:!1,leavingVNodes:new Map};return Ke(()=>{e.isMounted=!0}),Mn(()=>{e.isUnmounting=!0}),e}const Xe=[Function,Array],ec={name:"BaseTransition",props:{mode:String,appear:Boolean,persisted:Boolean,onBeforeEnter:Xe,onEnter:Xe,onAfterEnter:Xe,onEnterCancelled:Xe,onBeforeLeave:Xe,onLeave:Xe,onAfterLeave:Xe,onLeaveCancelled:Xe,onBeforeAppear:Xe,onAppear:Xe,onAfterAppear:Xe,onAppearCancelled:Xe},setup(e,{slots:t}){const n=ea(),i=Zr();let l;return()=>{const s=t.default&&$o(t.default(),!0);if(!s||!s.length)return;let o=s[0];if(s.length>1){for(const k of s)if(k.type!==Je){o=k;break}}const a=me(e),{mode:r}=a;if(i.isLeaving)return Wi(o);const u=ts(o);if(!u)return Wi(o);const c=Yi(u,a,i,n);Xi(u,c);const h=n.subTree,f=h&&ts(h);let g=!1;const{getTransitionKey:b}=u.type;if(b){const k=b();l===void 0?l=k:k!==l&&(l=k,g=!0)}if(f&&f.type!==Je&&(!zt(u,f)||g)){const k=Yi(f,a,i,n);if(Xi(f,k),r==="out-in")return i.isLeaving=!0,k.afterLeave=()=>{i.isLeaving=!1,n.update.active!==!1&&n.update()},Wi(o);r==="in-out"&&u.type!==Je&&(k.delayLeave=(I,m,w)=>{const _=Bo(i,f);_[String(f.key)]=f,I._leaveCb=()=>{m(),I._leaveCb=void 0,delete c.delayedLeave},c.delayedLeave=w})}return o}}},jo=ec;function Bo(e,t){const{leavingVNodes:n}=e;let i=n.get(t.type);return i||(i=Object.create(null),n.set(t.type,i)),i}function Yi(e,t,n,i){const{appear:l,mode:s,persisted:o=!1,onBeforeEnter:a,onEnter:r,onAfterEnter:u,onEnterCancelled:c,onBeforeLeave:h,onLeave:f,onAfterLeave:g,onLeaveCancelled:b,onBeforeAppear:k,onAppear:I,onAfterAppear:m,onAppearCancelled:w}=t,_=String(e.key),F=Bo(n,e),U=(v,G)=>{v&&et(v,i,9,G)},J=(v,G)=>{const V=G[1];U(v,G),te(v)?v.every(q=>q.length<=1)&&V():v.length<=1&&V()},A={mode:s,persisted:o,beforeEnter(v){let G=a;if(!n.isMounted)if(l)G=k||a;else return;v._leaveCb&&v._leaveCb(!0);const V=F[_];V&&zt(e,V)&&V.el._leaveCb&&V.el._leaveCb(),U(G,[v])},enter(v){let G=r,V=u,q=c;if(!n.isMounted)if(l)G=I||r,V=m||u,q=w||c;else return;let P=!1;const D=v._enterCb=R=>{P||(P=!0,R?U(q,[v]):U(V,[v]),A.delayedLeave&&A.delayedLeave(),v._enterCb=void 0)};G?J(G,[v,D]):D()},leave(v,G){const V=String(e.key);if(v._enterCb&&v._enterCb(!0),n.isUnmounting)return G();U(h,[v]);let q=!1;const P=v._leaveCb=D=>{q||(q=!0,G(),D?U(b,[v]):U(g,[v]),v._leaveCb=void 0,F[V]===e&&delete F[V])};F[V]=e,f?J(f,[v,P]):P()},clone(v){return Yi(v,t,n,i)}};return A}function Wi(e){if($n(e))return e=Rt(e),e.children=null,e}function ts(e){return $n(e)?e.children?e.children[0]:void 0:e}function Xi(e,t){e.shapeFlag&6&&e.component?Xi(e.component.subTree,t):e.shapeFlag&128?(e.ssContent.transition=t.clone(e.ssContent),e.ssFallback.transition=t.clone(e.ssFallback)):e.transition=t}function $o(e,t=!1,n){let i=[],l=0;for(let s=0;s1)for(let s=0;s!!e.type.__asyncLoader;function ee(e){ae(e)&&(e={loader:e});const{loader:t,loadingComponent:n,errorComponent:i,delay:l=200,timeout:s,suspensible:o=!0,onError:a}=e;let r=null,u,c=0;const h=()=>(c++,r=null,f()),f=()=>{let g;return r||(g=r=t().catch(b=>{if(b=b instanceof Error?b:new Error(String(b)),a)return new Promise((k,I)=>{a(b,()=>k(h()),()=>I(b),c+1)});throw b}).then(b=>g!==r&&r?r:(b&&(b.__esModule||b[Symbol.toStringTag]==="Module")&&(b=b.default),u=b,b)))};return he({name:"AsyncComponentWrapper",__asyncLoader:f,get __asyncResolved(){return u},setup(){const g=Re;if(u)return()=>Fi(u,g);const b=w=>{r=null,Bn(w,g,13,!i)};if(o&&g.suspense||fn)return f().then(w=>()=>Fi(w,g)).catch(w=>(b(w),()=>i?ie(i,{error:w}):null));const k=be(!1),I=be(),m=be(!!l);return l&&setTimeout(()=>{m.value=!1},l),s!=null&&setTimeout(()=>{if(!k.value&&!I.value){const w=new Error(`Async component timed out after ${s}ms.`);b(w),I.value=w}},s),f().then(()=>{k.value=!0,g.parent&&$n(g.parent.vnode)&&Ei(g.parent.update)}).catch(w=>{b(w),I.value=w}),()=>{if(k.value&&u)return Fi(u,g);if(I.value&&i)return ie(i,{error:I.value});if(n&&!m.value)return ie(n)}}})}function Fi(e,t){const{ref:n,props:i,children:l,ce:s}=t.vnode,o=ie(e,i,l);return o.ref=n,o.ce=s,delete t.vnode.ce,o}const $n=e=>e.type.__isKeepAlive;function tc(e,t){Mo(e,"a",t)}function nc(e,t){Mo(e,"da",t)}function Mo(e,t,n=Re){const i=e.__wdc||(e.__wdc=()=>{let l=n;for(;l;){if(l.isDeactivated)return;l=l.parent}return e()});if(Pi(t,i,n),n){let l=n.parent;for(;l&&l.parent;)$n(l.parent.vnode)&&ic(i,t,n,l),l=l.parent}}function ic(e,t,n,i){const l=Pi(t,e,i,!0);Ii(()=>{hl(i[t],l)},n)}function Pi(e,t,n=Re,i=!1){if(n){const l=n[e]||(n[e]=[]),s=t.__weh||(t.__weh=(...o)=>{if(n.isUnmounted)return;mn(),hn(n);const a=et(t,n,e,o);return Jt(),vn(),a});return i?l.unshift(s):l.push(s),s}}const wt=e=>(t,n=Re)=>(!fn||e==="sp")&&Pi(e,(...i)=>t(...i),n),lc=wt("bm"),Ke=wt("m"),sc=wt("bu"),oc=wt("u"),Mn=wt("bum"),Ii=wt("um"),ac=wt("sp"),rc=wt("rtg"),cc=wt("rtc");function uc(e,t=Re){Pi("ec",e,t)}function ri(e,t){const n=He;if(n===null)return e;const i=xi(n)||n.proxy,l=e.dirs||(e.dirs=[]);for(let s=0;st(o,a,void 0,s&&s[a]));else{const o=Object.keys(e);l=new Array(o.length);for(let a=0,r=o.length;adi(t)?!(t.type===Je||t.type===Ee&&!zo(t.children)):!0)?e:null}const Zi=e=>e?ta(e)?xi(e)||e.proxy:Zi(e.parent):null,In=je(Object.create(null),{$:e=>e,$el:e=>e.vnode.el,$data:e=>e.data,$props:e=>e.props,$attrs:e=>e.attrs,$slots:e=>e.slots,$refs:e=>e.refs,$parent:e=>Zi(e.parent),$root:e=>Zi(e.root),$emit:e=>e.emit,$options:e=>Il(e),$forceUpdate:e=>e.f||(e.f=()=>Ei(e.update)),$nextTick:e=>e.n||(e.n=ki.bind(e.proxy)),$watch:e=>Xr.bind(e)}),Di=(e,t)=>e!==Pe&&!e.__isScriptSetup&&pe(e,t),fc={get({_:e},t){const{ctx:n,setupState:i,data:l,props:s,accessCache:o,type:a,appContext:r}=e;let u;if(t[0]!=="$"){const g=o[t];if(g!==void 0)switch(g){case 1:return i[t];case 2:return l[t];case 4:return n[t];case 3:return s[t]}else{if(Di(i,t))return o[t]=1,i[t];if(l!==Pe&&pe(l,t))return o[t]=2,l[t];if((u=e.propsOptions[0])&&pe(u,t))return o[t]=3,s[t];if(n!==Pe&&pe(n,t))return o[t]=4,n[t];el&&(o[t]=0)}}const c=In[t];let h,f;if(c)return t==="$attrs"&&Ye(e,"get",t),c(e);if((h=a.__cssModules)&&(h=h[t]))return h;if(n!==Pe&&pe(n,t))return o[t]=4,n[t];if(f=r.config.globalProperties,pe(f,t))return f[t]},set({_:e},t,n){const{data:i,setupState:l,ctx:s}=e;return Di(l,t)?(l[t]=n,!0):i!==Pe&&pe(i,t)?(i[t]=n,!0):pe(e.props,t)||t[0]==="$"&&t.slice(1)in e?!1:(s[t]=n,!0)},has({_:{data:e,setupState:t,accessCache:n,ctx:i,appContext:l,propsOptions:s}},o){let a;return!!n[o]||e!==Pe&&pe(e,o)||Di(t,o)||(a=s[0])&&pe(a,o)||pe(i,o)||pe(In,o)||pe(l.config.globalProperties,o)},defineProperty(e,t,n){return n.get!=null?e._.accessCache[t]=0:pe(n,"value")&&this.set(e,t,n.value,null),Reflect.defineProperty(e,t,n)}};let el=!0;function pc(e){const t=Il(e),n=e.proxy,i=e.ctx;el=!1,t.beforeCreate&&is(t.beforeCreate,e,"bc");const{data:l,computed:s,methods:o,watch:a,provide:r,inject:u,created:c,beforeMount:h,mounted:f,beforeUpdate:g,updated:b,activated:k,deactivated:I,beforeDestroy:m,beforeUnmount:w,destroyed:_,unmounted:F,render:U,renderTracked:J,renderTriggered:A,errorCaptured:v,serverPrefetch:G,expose:V,inheritAttrs:q,components:P,directives:D,filters:R}=t;if(u&&gc(u,i,null,e.appContext.config.unwrapInjectedRef),o)for(const ne in o){const se=o[ne];ae(se)&&(i[ne]=se.bind(n))}if(l){const ne=l.call(n,n);Ie(ne)&&(e.data=bn(ne))}if(el=!0,s)for(const ne in s){const se=s[ne],Ae=ae(se)?se.bind(n,n):ae(se.get)?se.get.bind(n,n):st,Be=!ae(se)&&ae(se.set)?se.set.bind(n):st,Ne=$({get:Ae,set:Be});Object.defineProperty(i,ne,{enumerable:!0,configurable:!0,get:()=>Ne.value,set:$e=>Ne.value=$e})}if(a)for(const ne in a)Vo(a[ne],i,n,ne);if(r){const ne=ae(r)?r.call(n):r;Reflect.ownKeys(ne).forEach(se=>{Gt(se,ne[se])})}c&&is(c,e,"c");function N(ne,se){te(se)?se.forEach(Ae=>ne(Ae.bind(n))):se&&ne(se.bind(n))}if(N(lc,h),N(Ke,f),N(sc,g),N(oc,b),N(tc,k),N(nc,I),N(uc,v),N(cc,J),N(rc,A),N(Mn,w),N(Ii,F),N(ac,G),te(V))if(V.length){const ne=e.exposed||(e.exposed={});V.forEach(se=>{Object.defineProperty(ne,se,{get:()=>n[se],set:Ae=>n[se]=Ae})})}else e.exposed||(e.exposed={});U&&e.render===st&&(e.render=U),q!=null&&(e.inheritAttrs=q),P&&(e.components=P),D&&(e.directives=D)}function gc(e,t,n=st,i=!1){te(e)&&(e=tl(e));for(const l in e){const s=e[l];let o;Ie(s)?"default"in s?o=We(s.from||l,s.default,!0):o=We(s.from||l):o=We(s),Fe(o)&&i?Object.defineProperty(t,l,{enumerable:!0,configurable:!0,get:()=>o.value,set:a=>o.value=a}):t[l]=o}}function is(e,t,n){et(te(e)?e.map(i=>i.bind(t.proxy)):e.bind(t.proxy),t,n)}function Vo(e,t,n,i){const l=i.includes(".")?Ho(n,i):()=>n[i];if(ve(e)){const s=t[e];ae(s)&&ut(l,s)}else if(ae(e))ut(l,e.bind(n));else if(Ie(e))if(te(e))e.forEach(s=>Vo(s,t,n,i));else{const s=ae(e.handler)?e.handler.bind(n):t[e.handler];ae(s)&&ut(l,s,e)}}function Il(e){const t=e.type,{mixins:n,extends:i}=t,{mixins:l,optionsCache:s,config:{optionMergeStrategies:o}}=e.appContext,a=s.get(t);let r;return a?r=a:!l.length&&!n&&!i?r=t:(r={},l.length&&l.forEach(u=>ci(r,u,o,!0)),ci(r,t,o)),Ie(t)&&s.set(t,r),r}function ci(e,t,n,i=!1){const{mixins:l,extends:s}=t;s&&ci(e,s,n,!0),l&&l.forEach(o=>ci(e,o,n,!0));for(const o in t)if(!(i&&o==="expose")){const a=mc[o]||n&&n[o];e[o]=a?a(e[o],t[o]):t[o]}return e}const mc={data:ls,props:Bt,emits:Bt,methods:Bt,computed:Bt,beforeCreate:ze,created:ze,beforeMount:ze,mounted:ze,beforeUpdate:ze,updated:ze,beforeDestroy:ze,beforeUnmount:ze,destroyed:ze,unmounted:ze,activated:ze,deactivated:ze,errorCaptured:ze,serverPrefetch:ze,components:Bt,directives:Bt,watch:bc,provide:ls,inject:vc};function ls(e,t){return t?e?function(){return je(ae(e)?e.call(this,this):e,ae(t)?t.call(this,this):t)}:t:e}function vc(e,t){return Bt(tl(e),tl(t))}function tl(e){if(te(e)){const t={};for(let n=0;n0)&&!(o&16)){if(o&8){const c=e.vnode.dynamicProps;for(let h=0;h{r=!0;const[f,g]=qo(h,t,!0);je(o,f),g&&a.push(...g)};!n&&t.mixins.length&&t.mixins.forEach(c),e.extends&&c(e.extends),e.mixins&&e.mixins.forEach(c)}if(!s&&!r)return Ie(e)&&i.set(e,sn),sn;if(te(s))for(let c=0;c-1,g[1]=k<0||b-1||pe(g,"default"))&&a.push(h)}}}const u=[o,a];return Ie(e)&&i.set(e,u),u}function ss(e){return e[0]!=="$"}function os(e){const t=e&&e.toString().match(/^\s*function (\w+)/);return t?t[1]:e===null?"null":""}function as(e,t){return os(e)===os(t)}function rs(e,t){return te(t)?t.findIndex(n=>as(n,e)):ae(t)&&as(t,e)?0:-1}const Ko=e=>e[0]==="_"||e==="$stable",Ll=e=>te(e)?e.map(nt):[nt(e)],_c=(e,t,n)=>{if(t._n)return t;const i=De((...l)=>Ll(t(...l)),n);return i._c=!1,i},Qo=(e,t,n)=>{const i=e._ctx;for(const l in e){if(Ko(l))continue;const s=e[l];if(ae(s))t[l]=_c(l,s,i);else if(s!=null){const o=Ll(s);t[l]=()=>o}}},Go=(e,t)=>{const n=Ll(t);e.slots.default=()=>n},kc=(e,t)=>{if(e.vnode.shapeFlag&32){const n=t._;n?(e.slots=me(t),li(t,"_",n)):Qo(t,e.slots={})}else e.slots={},t&&Go(e,t);li(e.slots,Li,1)},Ec=(e,t,n)=>{const{vnode:i,slots:l}=e;let s=!0,o=Pe;if(i.shapeFlag&32){const a=t._;a?n&&a===1?s=!1:(je(l,t),!n&&a===1&&delete l._):(s=!t.$stable,Qo(t,l)),o=t}else t&&(Go(e,t),o={default:1});if(s)for(const a in l)!Ko(a)&&!(a in o)&&delete l[a]};function Jo(){return{app:null,config:{isNativeTag:Ya,performance:!1,globalProperties:{},optionMergeStrategies:{},errorHandler:void 0,warnHandler:void 0,compilerOptions:{}},mixins:[],components:{},directives:{},provides:Object.create(null),optionsCache:new WeakMap,propsCache:new WeakMap,emitsCache:new WeakMap}}let Cc=0;function Pc(e,t){return function(i,l=null){ae(i)||(i=Object.assign({},i)),l!=null&&!Ie(l)&&(l=null);const s=Jo(),o=new Set;let a=!1;const r=s.app={_uid:Cc++,_component:i,_props:l,_container:null,_context:s,_instance:null,version:qc,get config(){return s.config},set config(u){},use(u,...c){return o.has(u)||(u&&ae(u.install)?(o.add(u),u.install(r,...c)):ae(u)&&(o.add(u),u(r,...c))),r},mixin(u){return s.mixins.includes(u)||s.mixins.push(u),r},component(u,c){return c?(s.components[u]=c,r):s.components[u]},directive(u,c){return c?(s.directives[u]=c,r):s.directives[u]},mount(u,c,h){if(!a){const f=ie(i,l);return f.appContext=s,c&&t?t(f,u):e(f,u,h),a=!0,r._container=u,u.__vue_app__=r,xi(f.component)||f.component.proxy}},unmount(){a&&(e(null,r._container),delete r._container.__vue_app__)},provide(u,c){return s.provides[u]=c,r}};return r}}function ui(e,t,n,i,l=!1){if(te(e)){e.forEach((f,g)=>ui(f,t&&(te(t)?t[g]:t),n,i,l));return}if(cn(i)&&!l)return;const s=i.shapeFlag&4?xi(i.component)||i.component.proxy:i.el,o=l?null:s,{i:a,r}=e,u=t&&t.r,c=a.refs===Pe?a.refs={}:a.refs,h=a.setupState;if(u!=null&&u!==r&&(ve(u)?(c[u]=null,pe(h,u)&&(h[u]=null)):Fe(u)&&(u.value=null)),ae(r))xt(r,a,12,[o,c]);else{const f=ve(r),g=Fe(r);if(f||g){const b=()=>{if(e.f){const k=f?pe(h,r)?h[r]:c[r]:r.value;l?te(k)&&hl(k,s):te(k)?k.includes(s)||k.push(s):f?(c[r]=[s],pe(h,r)&&(h[r]=c[r])):(r.value=[s],e.k&&(c[e.k]=r.value))}else f?(c[r]=o,pe(h,r)&&(h[r]=o)):g&&(r.value=o,e.k&&(c[e.k]=o))};o?(b.id=-1,Ue(b,n)):b()}}}let kt=!1;const Yn=e=>/svg/.test(e.namespaceURI)&&e.tagName!=="foreignObject",Xn=e=>e.nodeType===8;function Ic(e){const{mt:t,p:n,o:{patchProp:i,createText:l,nextSibling:s,parentNode:o,remove:a,insert:r,createComment:u}}=e,c=(m,w)=>{if(!w.hasChildNodes()){n(null,m,w),oi(),w._vnode=m;return}kt=!1,h(w.firstChild,m,null,null,null),oi(),w._vnode=m,kt&&console.error("Hydration completed but contains mismatches.")},h=(m,w,_,F,U,J=!1)=>{const A=Xn(m)&&m.data==="[",v=()=>k(m,w,_,F,U,A),{type:G,ref:V,shapeFlag:q,patchFlag:P}=w;let D=m.nodeType;w.el=m,P===-2&&(J=!1,w.dynamicChildren=null);let R=null;switch(G){case dn:D!==3?w.children===""?(r(w.el=l(""),o(m),m),R=m):R=v():(m.data!==w.children&&(kt=!0,m.data=w.children),R=s(m));break;case Je:D!==8||A?R=v():R=s(m);break;case Ln:if(A&&(m=s(m),D=m.nodeType),D===1||D===3){R=m;const re=!w.children.length;for(let N=0;N{J=J||!!w.dynamicChildren;const{type:A,props:v,patchFlag:G,shapeFlag:V,dirs:q}=w,P=A==="input"&&q||A==="option";if(P||G!==-1){if(q&&rt(w,null,_,"created"),v)if(P||!J||G&48)for(const R in v)(P&&R.endsWith("value")||jn(R)&&!Pn(R))&&i(m,R,null,v[R],!1,void 0,_);else v.onClick&&i(m,"onClick",null,v.onClick,!1,void 0,_);let D;if((D=v&&v.onVnodeBeforeMount)&&Ze(D,_,w),q&&rt(w,null,_,"beforeMount"),((D=v&&v.onVnodeMounted)||q)&&Do(()=>{D&&Ze(D,_,w),q&&rt(w,null,_,"mounted")},F),V&16&&!(v&&(v.innerHTML||v.textContent))){let R=g(m.firstChild,w,m,_,F,U,J);for(;R;){kt=!0;const re=R;R=R.nextSibling,a(re)}}else V&8&&m.textContent!==w.children&&(kt=!0,m.textContent=w.children)}return m.nextSibling},g=(m,w,_,F,U,J,A)=>{A=A||!!w.dynamicChildren;const v=w.children,G=v.length;for(let V=0;V{const{slotScopeIds:A}=w;A&&(U=U?U.concat(A):A);const v=o(m),G=g(s(m),w,v,_,F,U,J);return G&&Xn(G)&&G.data==="]"?s(w.anchor=G):(kt=!0,r(w.anchor=u("]"),v,G),G)},k=(m,w,_,F,U,J)=>{if(kt=!0,w.el=null,J){const G=I(m);for(;;){const V=s(m);if(V&&V!==G)a(V);else break}}const A=s(m),v=o(m);return a(m),n(null,w,v,A,_,F,Yn(v),U),A},I=m=>{let w=0;for(;m;)if(m=s(m),m&&Xn(m)&&(m.data==="["&&w++,m.data==="]")){if(w===0)return s(m);w--}return m};return[c,h]}const Ue=Do;function Lc(e){return xc(e,Ic)}function xc(e,t){const n=ir();n.__VUE__=!0;const{insert:i,remove:l,patchProp:s,createElement:o,createText:a,createComment:r,setText:u,setElementText:c,parentNode:h,nextSibling:f,setScopeId:g=st,insertStaticContent:b}=e,k=(d,p,y,E=null,L=null,O=null,B=!1,W=null,H=!!p.dynamicChildren)=>{if(d===p)return;d&&!zt(d,p)&&(E=j(d),$e(d,L,O,!0),d=null),p.patchFlag===-2&&(H=!1,p.dynamicChildren=null);const{type:T,ref:Y,shapeFlag:K}=p;switch(T){case dn:I(d,p,y,E);break;case Je:m(d,p,y,E);break;case Ln:d==null&&w(p,y,E,B);break;case Ee:P(d,p,y,E,L,O,B,W,H);break;default:K&1?U(d,p,y,E,L,O,B,W,H):K&6?D(d,p,y,E,L,O,B,W,H):(K&64||K&128)&&T.process(d,p,y,E,L,O,B,W,H,ue)}Y!=null&&L&&ui(Y,d&&d.ref,O,p||d,!p)},I=(d,p,y,E)=>{if(d==null)i(p.el=a(p.children),y,E);else{const L=p.el=d.el;p.children!==d.children&&u(L,p.children)}},m=(d,p,y,E)=>{d==null?i(p.el=r(p.children||""),y,E):p.el=d.el},w=(d,p,y,E)=>{[d.el,d.anchor]=b(d.children,p,y,E,d.el,d.anchor)},_=({el:d,anchor:p},y,E)=>{let L;for(;d&&d!==p;)L=f(d),i(d,y,E),d=L;i(p,y,E)},F=({el:d,anchor:p})=>{let y;for(;d&&d!==p;)y=f(d),l(d),d=y;l(p)},U=(d,p,y,E,L,O,B,W,H)=>{B=B||p.type==="svg",d==null?J(p,y,E,L,O,B,W,H):G(d,p,L,O,B,W,H)},J=(d,p,y,E,L,O,B,W)=>{let H,T;const{type:Y,props:K,shapeFlag:X,transition:le,dirs:ce}=d;if(H=d.el=o(d.type,O,K&&K.is,K),X&8?c(H,d.children):X&16&&v(d.children,H,null,E,L,O&&Y!=="foreignObject",B,W),ce&&rt(d,null,E,"created"),K){for(const ye in K)ye!=="value"&&!Pn(ye)&&s(H,ye,null,K[ye],O,d.children,E,L,z);"value"in K&&s(H,"value",null,K.value),(T=K.onVnodeBeforeMount)&&Ze(T,E,d)}A(H,d,d.scopeId,B,E),ce&&rt(d,null,E,"beforeMount");const _e=(!L||L&&!L.pendingBranch)&&le&&!le.persisted;_e&&le.beforeEnter(H),i(H,p,y),((T=K&&K.onVnodeMounted)||_e||ce)&&Ue(()=>{T&&Ze(T,E,d),_e&&le.enter(H),ce&&rt(d,null,E,"mounted")},L)},A=(d,p,y,E,L)=>{if(y&&g(d,y),E)for(let O=0;O{for(let T=H;T{const W=p.el=d.el;let{patchFlag:H,dynamicChildren:T,dirs:Y}=p;H|=d.patchFlag&16;const K=d.props||Pe,X=p.props||Pe;let le;y&&Dt(y,!1),(le=X.onVnodeBeforeUpdate)&&Ze(le,y,p,d),Y&&rt(p,d,y,"beforeUpdate"),y&&Dt(y,!0);const ce=L&&p.type!=="foreignObject";if(T?V(d.dynamicChildren,T,W,y,E,ce,O):B||se(d,p,W,null,y,E,ce,O,!1),H>0){if(H&16)q(W,p,K,X,y,E,L);else if(H&2&&K.class!==X.class&&s(W,"class",null,X.class,L),H&4&&s(W,"style",K.style,X.style,L),H&8){const _e=p.dynamicProps;for(let ye=0;ye<_e.length;ye++){const Te=_e[ye],tt=K[Te],en=X[Te];(en!==tt||Te==="value")&&s(W,Te,tt,en,L,d.children,y,E,z)}}H&1&&d.children!==p.children&&c(W,p.children)}else!B&&T==null&&q(W,p,K,X,y,E,L);((le=X.onVnodeUpdated)||Y)&&Ue(()=>{le&&Ze(le,y,p,d),Y&&rt(p,d,y,"updated")},E)},V=(d,p,y,E,L,O,B)=>{for(let W=0;W{if(y!==E){if(y!==Pe)for(const W in y)!Pn(W)&&!(W in E)&&s(d,W,y[W],null,B,p.children,L,O,z);for(const W in E){if(Pn(W))continue;const H=E[W],T=y[W];H!==T&&W!=="value"&&s(d,W,T,H,B,p.children,L,O,z)}"value"in E&&s(d,"value",y.value,E.value)}},P=(d,p,y,E,L,O,B,W,H)=>{const T=p.el=d?d.el:a(""),Y=p.anchor=d?d.anchor:a("");let{patchFlag:K,dynamicChildren:X,slotScopeIds:le}=p;le&&(W=W?W.concat(le):le),d==null?(i(T,y,E),i(Y,y,E),v(p.children,y,Y,L,O,B,W,H)):K>0&&K&64&&X&&d.dynamicChildren?(V(d.dynamicChildren,X,y,L,O,B,W),(p.key!=null||L&&p===L.subTree)&&Yo(d,p,!0)):se(d,p,y,Y,L,O,B,W,H)},D=(d,p,y,E,L,O,B,W,H)=>{p.slotScopeIds=W,d==null?p.shapeFlag&512?L.ctx.activate(p,y,E,B,H):R(p,y,E,L,O,B,H):re(d,p,H)},R=(d,p,y,E,L,O,B)=>{const W=d.component=Hc(d,E,L);if($n(d)&&(W.ctx.renderer=ue),jc(W),W.asyncDep){if(L&&L.registerDep(W,N),!d.el){const H=W.subTree=ie(Je);m(null,H,p,y)}return}N(W,d,p,y,L,O,B)},re=(d,p,y)=>{const E=p.component=d.component;if(Qr(d,p,y))if(E.asyncDep&&!E.asyncResolved){ne(E,p,y);return}else E.next=p,Nr(E.update),E.update();else p.el=d.el,E.vnode=p},N=(d,p,y,E,L,O,B)=>{const W=()=>{if(d.isMounted){let{next:Y,bu:K,u:X,parent:le,vnode:ce}=d,_e=Y,ye;Dt(d,!1),Y?(Y.el=ce.el,ne(d,Y,B)):Y=ce,K&&Ri(K),(ye=Y.props&&Y.props.onVnodeBeforeUpdate)&&Ze(ye,le,Y,ce),Dt(d,!0);const Te=Oi(d),tt=d.subTree;d.subTree=Te,k(tt,Te,h(tt.el),j(tt),d,L,O),Y.el=Te.el,_e===null&&Gr(d,Te.el),X&&Ue(X,L),(ye=Y.props&&Y.props.onVnodeUpdated)&&Ue(()=>Ze(ye,le,Y,ce),L)}else{let Y;const{el:K,props:X}=p,{bm:le,m:ce,parent:_e}=d,ye=cn(p);if(Dt(d,!1),le&&Ri(le),!ye&&(Y=X&&X.onVnodeBeforeMount)&&Ze(Y,_e,p),Dt(d,!0),K&&oe){const Te=()=>{d.subTree=Oi(d),oe(K,d.subTree,d,L,null)};ye?p.type.__asyncLoader().then(()=>!d.isUnmounted&&Te()):Te()}else{const Te=d.subTree=Oi(d);k(null,Te,y,E,d,L,O),p.el=Te.el}if(ce&&Ue(ce,L),!ye&&(Y=X&&X.onVnodeMounted)){const Te=p;Ue(()=>Ze(Y,_e,Te),L)}(p.shapeFlag&256||_e&&cn(_e.vnode)&&_e.vnode.shapeFlag&256)&&d.a&&Ue(d.a,L),d.isMounted=!0,p=y=E=null}},H=d.effect=new vl(W,()=>Ei(T),d.scope),T=d.update=()=>H.run();T.id=d.uid,Dt(d,!0),T()},ne=(d,p,y)=>{p.component=d;const E=d.vnode.props;d.vnode=p,d.next=null,yc(d,p.props,E,y),Ec(d,p.children,y),mn(),Zl(),vn()},se=(d,p,y,E,L,O,B,W,H=!1)=>{const T=d&&d.children,Y=d?d.shapeFlag:0,K=p.children,{patchFlag:X,shapeFlag:le}=p;if(X>0){if(X&128){Be(T,K,y,E,L,O,B,W,H);return}else if(X&256){Ae(T,K,y,E,L,O,B,W,H);return}}le&8?(Y&16&&z(T,L,O),K!==T&&c(y,K)):Y&16?le&16?Be(T,K,y,E,L,O,B,W,H):z(T,L,O,!0):(Y&8&&c(y,""),le&16&&v(K,y,E,L,O,B,W,H))},Ae=(d,p,y,E,L,O,B,W,H)=>{d=d||sn,p=p||sn;const T=d.length,Y=p.length,K=Math.min(T,Y);let X;for(X=0;XY?z(d,L,O,!0,!1,K):v(p,y,E,L,O,B,W,H,K)},Be=(d,p,y,E,L,O,B,W,H)=>{let T=0;const Y=p.length;let K=d.length-1,X=Y-1;for(;T<=K&&T<=X;){const le=d[T],ce=p[T]=H?Pt(p[T]):nt(p[T]);if(zt(le,ce))k(le,ce,y,null,L,O,B,W,H);else break;T++}for(;T<=K&&T<=X;){const le=d[K],ce=p[X]=H?Pt(p[X]):nt(p[X]);if(zt(le,ce))k(le,ce,y,null,L,O,B,W,H);else break;K--,X--}if(T>K){if(T<=X){const le=X+1,ce=leX)for(;T<=K;)$e(d[T],L,O,!0),T++;else{const le=T,ce=T,_e=new Map;for(T=ce;T<=X;T++){const Qe=p[T]=H?Pt(p[T]):nt(p[T]);Qe.key!=null&&_e.set(Qe.key,T)}let ye,Te=0;const tt=X-ce+1;let en=!1,Ml=0;const wn=new Array(tt);for(T=0;T=tt){$e(Qe,L,O,!0);continue}let at;if(Qe.key!=null)at=_e.get(Qe.key);else for(ye=ce;ye<=X;ye++)if(wn[ye-ce]===0&&zt(Qe,p[ye])){at=ye;break}at===void 0?$e(Qe,L,O,!0):(wn[at-ce]=T+1,at>=Ml?Ml=at:en=!0,k(Qe,p[at],y,null,L,O,B,W,H),Te++)}const Nl=en?Ac(wn):sn;for(ye=Nl.length-1,T=tt-1;T>=0;T--){const Qe=ce+T,at=p[Qe],zl=Qe+1{const{el:O,type:B,transition:W,children:H,shapeFlag:T}=d;if(T&6){Ne(d.component.subTree,p,y,E);return}if(T&128){d.suspense.move(p,y,E);return}if(T&64){B.move(d,p,y,ue);return}if(B===Ee){i(O,p,y);for(let K=0;KW.enter(O),L);else{const{leave:K,delayLeave:X,afterLeave:le}=W,ce=()=>i(O,p,y),_e=()=>{K(O,()=>{ce(),le&&le()})};X?X(O,ce,_e):_e()}else i(O,p,y)},$e=(d,p,y,E=!1,L=!1)=>{const{type:O,props:B,ref:W,children:H,dynamicChildren:T,shapeFlag:Y,patchFlag:K,dirs:X}=d;if(W!=null&&ui(W,null,y,d,!0),Y&256){p.ctx.deactivate(d);return}const le=Y&1&&X,ce=!cn(d);let _e;if(ce&&(_e=B&&B.onVnodeBeforeUnmount)&&Ze(_e,p,d),Y&6)C(d.component,y,E);else{if(Y&128){d.suspense.unmount(y,E);return}le&&rt(d,null,p,"beforeUnmount"),Y&64?d.type.remove(d,p,y,L,ue,E):T&&(O!==Ee||K>0&&K&64)?z(T,p,y,!1,!0):(O===Ee&&K&384||!L&&Y&16)&&z(H,p,y),E&&yt(d)}(ce&&(_e=B&&B.onVnodeUnmounted)||le)&&Ue(()=>{_e&&Ze(_e,p,d),le&&rt(d,null,p,"unmounted")},y)},yt=d=>{const{type:p,el:y,anchor:E,transition:L}=d;if(p===Ee){Zt(y,E);return}if(p===Ln){F(d);return}const O=()=>{l(y),L&&!L.persisted&&L.afterLeave&&L.afterLeave()};if(d.shapeFlag&1&&L&&!L.persisted){const{leave:B,delayLeave:W}=L,H=()=>B(y,O);W?W(d.el,O,H):H()}else O()},Zt=(d,p)=>{let y;for(;d!==p;)y=f(d),l(d),d=y;l(p)},C=(d,p,y)=>{const{bum:E,scope:L,update:O,subTree:B,um:W}=d;E&&Ri(E),L.stop(),O&&(O.active=!1,$e(B,d,p,y)),W&&Ue(W,p),Ue(()=>{d.isUnmounted=!0},p),p&&p.pendingBranch&&!p.isUnmounted&&d.asyncDep&&!d.asyncResolved&&d.suspenseId===p.pendingId&&(p.deps--,p.deps===0&&p.resolve())},z=(d,p,y,E=!1,L=!1,O=0)=>{for(let B=O;Bd.shapeFlag&6?j(d.component.subTree):d.shapeFlag&128?d.suspense.next():f(d.anchor||d.el),Q=(d,p,y)=>{d==null?p._vnode&&$e(p._vnode,null,null,!0):k(p._vnode||null,d,p,null,null,null,y),Zl(),oi(),p._vnode=d},ue={p:k,um:$e,m:Ne,r:yt,mt:R,mc:v,pc:se,pbc:V,n:j,o:e};let Ce,oe;return t&&([Ce,oe]=t(ue)),{render:Q,hydrate:Ce,createApp:Pc(Q,Ce)}}function Dt({effect:e,update:t},n){e.allowRecurse=t.allowRecurse=n}function Yo(e,t,n=!1){const i=e.children,l=t.children;if(te(i)&&te(l))for(let s=0;s>1,e[n[a]]0&&(t[i]=n[s-1]),n[s]=i)}}for(s=n.length,o=n[s-1];s-- >0;)n[s]=o,o=t[o];return n}const Tc=e=>e.__isTeleport,Ee=Symbol(void 0),dn=Symbol(void 0),Je=Symbol(void 0),Ln=Symbol(void 0),xn=[];let lt=null;function M(e=!1){xn.push(lt=e?null:[])}function Sc(){xn.pop(),lt=xn[xn.length-1]||null}let Fn=1;function cs(e){Fn+=e}function Xo(e){return e.dynamicChildren=Fn>0?lt||sn:null,Sc(),Fn>0&<&<.push(e),e}function Z(e,t,n,i,l,s){return Xo(ge(e,t,n,i,l,s,!0))}function Se(e,t,n,i,l){return Xo(ie(e,t,n,i,l,!0))}function di(e){return e?e.__v_isVNode===!0:!1}function zt(e,t){return e.type===t.type&&e.key===t.key}const Li="__vInternal",Zo=({key:e})=>e!=null?e:null,ti=({ref:e,ref_key:t,ref_for:n})=>e!=null?ve(e)||Fe(e)||ae(e)?{i:He,r:e,k:t,f:!!n}:e:null;function ge(e,t=null,n=null,i=0,l=null,s=e===Ee?0:1,o=!1,a=!1){const r={__v_isVNode:!0,__v_skip:!0,type:e,props:t,key:t&&Zo(t),ref:t&&ti(t),scopeId:Fo,slotScopeIds:null,children:n,component:null,suspense:null,ssContent:null,ssFallback:null,dirs:null,transition:null,el:null,anchor:null,target:null,targetAnchor:null,staticCount:0,shapeFlag:s,patchFlag:i,dynamicProps:l,dynamicChildren:null,appContext:null,ctx:He};return a?(xl(r,n),s&128&&e.normalize(r)):n&&(r.shapeFlag|=ve(n)?8:16),Fn>0&&!o&<&&(r.patchFlag>0||s&6)&&r.patchFlag!==32&<.push(r),r}const ie=Rc;function Rc(e,t=null,n=null,i=0,l=null,s=!1){if((!e||e===dc)&&(e=Je),di(e)){const a=Rt(e,t,!0);return n&&xl(a,n),Fn>0&&!s&<&&(a.shapeFlag&6?lt[lt.indexOf(e)]=a:lt.push(a)),a.patchFlag|=-2,a}if(zc(e)&&(e=e.__vccOpts),t){t=Oc(t);let{class:a,style:r}=t;a&&!ve(a)&&(t.class=qe(a)),Ie(r)&&(Eo(r)&&!te(r)&&(r=je({},r)),t.style=Hn(r))}const o=ve(e)?1:Jr(e)?128:Tc(e)?64:Ie(e)?4:ae(e)?2:0;return ge(e,t,n,i,l,o,s,!0)}function Oc(e){return e?Eo(e)||Li in e?je({},e):e:null}function Rt(e,t,n=!1){const{props:i,ref:l,patchFlag:s,children:o}=e,a=t?il(i||{},t):i;return{__v_isVNode:!0,__v_skip:!0,type:e.type,props:a,key:a&&Zo(a),ref:t&&t.ref?n&&l?te(l)?l.concat(ti(t)):[l,ti(t)]:ti(t):l,scopeId:e.scopeId,slotScopeIds:e.slotScopeIds,children:o,target:e.target,targetAnchor:e.targetAnchor,staticCount:e.staticCount,shapeFlag:e.shapeFlag,patchFlag:t&&e.type!==Ee?s===-1?16:s|16:s,dynamicProps:e.dynamicProps,dynamicChildren:e.dynamicChildren,appContext:e.appContext,dirs:e.dirs,transition:e.transition,component:e.component,suspense:e.suspense,ssContent:e.ssContent&&Rt(e.ssContent),ssFallback:e.ssFallback&&Rt(e.ssFallback),el:e.el,anchor:e.anchor,ctx:e.ctx}}function Ot(e=" ",t=0){return ie(dn,null,e,t)}function Wc(e,t){const n=ie(Ln,null,e);return n.staticCount=t,n}function xe(e="",t=!1){return t?(M(),Se(Je,null,e)):ie(Je,null,e)}function nt(e){return e==null||typeof e=="boolean"?ie(Je):te(e)?ie(Ee,null,e.slice()):typeof e=="object"?Pt(e):ie(dn,null,String(e))}function Pt(e){return e.el===null&&e.patchFlag!==-1||e.memo?e:Rt(e)}function xl(e,t){let n=0;const{shapeFlag:i}=e;if(t==null)t=null;else if(te(t))n=16;else if(typeof t=="object")if(i&65){const l=t.default;l&&(l._c&&(l._d=!1),xl(e,l()),l._c&&(l._d=!0));return}else{n=32;const l=t._;!l&&!(Li in t)?t._ctx=He:l===3&&He&&(He.slots._===1?t._=1:(t._=2,e.patchFlag|=1024))}else ae(t)?(t={default:t,_ctx:He},n=32):(t=String(t),i&64?(n=16,t=[Ot(t)]):n=8);e.children=t,e.shapeFlag|=n}function il(...e){const t={};for(let n=0;nRe||He,hn=e=>{Re=e,e.scope.on()},Jt=()=>{Re&&Re.scope.off(),Re=null};function ta(e){return e.vnode.shapeFlag&4}let fn=!1;function jc(e,t=!1){fn=t;const{props:n,children:i}=e.vnode,l=ta(e);wc(e,n,l,t),kc(e,i);const s=l?Bc(e,t):void 0;return fn=!1,s}function Bc(e,t){const n=e.type;e.accessCache=Object.create(null),e.proxy=Co(new Proxy(e.ctx,fc));const{setup:i}=n;if(i){const l=e.setupContext=i.length>1?Mc(e):null;hn(e),mn();const s=xt(i,e,0,[e.props,l]);if(vn(),Jt(),co(s)){if(s.then(Jt,Jt),t)return s.then(o=>{us(e,o,t)}).catch(o=>{Bn(o,e,0)});e.asyncDep=s}else us(e,s,t)}else na(e,t)}function us(e,t,n){ae(t)?e.type.__ssrInlineRender?e.ssrRender=t:e.render=t:Ie(t)&&(e.setupState=Ao(t)),na(e,n)}let ds;function na(e,t,n){const i=e.type;if(!e.render){if(!t&&ds&&!i.render){const l=i.template||Il(e).template;if(l){const{isCustomElement:s,compilerOptions:o}=e.appContext.config,{delimiters:a,compilerOptions:r}=i,u=je(je({isCustomElement:s,delimiters:a},o),r);i.render=ds(l,u)}}e.render=i.render||st}hn(e),mn(),pc(e),vn(),Jt()}function $c(e){return new Proxy(e.attrs,{get(t,n){return Ye(e,"get","$attrs"),t[n]}})}function Mc(e){const t=i=>{e.exposed=i||{}};let n;return{get attrs(){return n||(n=$c(e))},slots:e.slots,emit:e.emit,expose:t}}function xi(e){if(e.exposed)return e.exposeProxy||(e.exposeProxy=new Proxy(Ao(Co(e.exposed)),{get(t,n){if(n in t)return t[n];if(n in In)return In[n](e)},has(t,n){return n in t||n in In}}))}function Nc(e,t=!0){return ae(e)?e.displayName||e.name:e.name||t&&e.__name}function zc(e){return ae(e)&&"__vccOpts"in e}const $=(e,t)=>Br(e,t,fn);function de(e,t,n){const i=arguments.length;return i===2?Ie(t)&&!te(t)?di(t)?ie(e,null,[t]):ie(e,t):ie(e,null,t):(i>3?n=Array.prototype.slice.call(arguments,2):i===3&&di(n)&&(n=[n]),ie(e,t,n))}const Vc=Symbol(""),Uc=()=>We(Vc),qc="3.2.45",Kc="http://www.w3.org/2000/svg",Vt=typeof document<"u"?document:null,hs=Vt&&Vt.createElement("template"),Qc={insert:(e,t,n)=>{t.insertBefore(e,n||null)},remove:e=>{const t=e.parentNode;t&&t.removeChild(e)},createElement:(e,t,n,i)=>{const l=t?Vt.createElementNS(Kc,e):Vt.createElement(e,n?{is:n}:void 0);return e==="select"&&i&&i.multiple!=null&&l.setAttribute("multiple",i.multiple),l},createText:e=>Vt.createTextNode(e),createComment:e=>Vt.createComment(e),setText:(e,t)=>{e.nodeValue=t},setElementText:(e,t)=>{e.textContent=t},parentNode:e=>e.parentNode,nextSibling:e=>e.nextSibling,querySelector:e=>Vt.querySelector(e),setScopeId(e,t){e.setAttribute(t,"")},insertStaticContent(e,t,n,i,l,s){const o=n?n.previousSibling:t.lastChild;if(l&&(l===s||l.nextSibling))for(;t.insertBefore(l.cloneNode(!0),n),!(l===s||!(l=l.nextSibling)););else{hs.innerHTML=i?`${e}`:e;const a=hs.content;if(i){const r=a.firstChild;for(;r.firstChild;)a.appendChild(r.firstChild);a.removeChild(r)}t.insertBefore(a,n)}return[o?o.nextSibling:t.firstChild,n?n.previousSibling:t.lastChild]}};function Gc(e,t,n){const i=e._vtc;i&&(t=(t?[t,...i]:[...i]).join(" ")),t==null?e.removeAttribute("class"):n?e.setAttribute("class",t):e.className=t}function Jc(e,t,n){const i=e.style,l=ve(n);if(n&&!l){for(const s in n)ll(i,s,n[s]);if(t&&!ve(t))for(const s in t)n[s]==null&&ll(i,s,"")}else{const s=i.display;l?t!==n&&(i.cssText=n):t&&e.removeAttribute("style"),"_vod"in e&&(i.display=s)}}const fs=/\s*!important$/;function ll(e,t,n){if(te(n))n.forEach(i=>ll(e,t,i));else if(n==null&&(n=""),t.startsWith("--"))e.setProperty(t,n);else{const i=Yc(e,t);fs.test(n)?e.setProperty(Yt(i),n.replace(fs,""),"important"):e[i]=n}}const ps=["Webkit","Moz","ms"],Hi={};function Yc(e,t){const n=Hi[t];if(n)return n;let i=dt(t);if(i!=="filter"&&i in e)return Hi[t]=i;i=wi(i);for(let l=0;lji||(lu.then(()=>ji=0),ji=Date.now());function ou(e,t){const n=i=>{if(!i._vts)i._vts=Date.now();else if(i._vts<=n.attached)return;et(au(i,n.value),t,5,[i])};return n.value=e,n.attached=su(),n}function au(e,t){if(te(t)){const n=e.stopImmediatePropagation;return e.stopImmediatePropagation=()=>{n.call(e),e._stopped=!0},t.map(i=>l=>!l._stopped&&i&&i(l))}else return t}const vs=/^on[a-z]/,ru=(e,t,n,i,l=!1,s,o,a,r)=>{t==="class"?Gc(e,i,l):t==="style"?Jc(e,n,i):jn(t)?dl(t)||nu(e,t,n,i,o):(t[0]==="."?(t=t.slice(1),!0):t[0]==="^"?(t=t.slice(1),!1):cu(e,t,i,l))?Zc(e,t,i,s,o,a,r):(t==="true-value"?e._trueValue=i:t==="false-value"&&(e._falseValue=i),Xc(e,t,i,l))};function cu(e,t,n,i){return i?!!(t==="innerHTML"||t==="textContent"||t in e&&vs.test(t)&&ae(n)):t==="spellcheck"||t==="draggable"||t==="translate"||t==="form"||t==="list"&&e.tagName==="INPUT"||t==="type"&&e.tagName==="TEXTAREA"||vs.test(t)&&ve(n)?!1:t in e}const Et="transition",yn="animation",Nn=(e,{slots:t})=>de(jo,uu(e),t);Nn.displayName="Transition";const ia={name:String,type:String,css:{type:Boolean,default:!0},duration:[String,Number,Object],enterFromClass:String,enterActiveClass:String,enterToClass:String,appearFromClass:String,appearActiveClass:String,appearToClass:String,leaveFromClass:String,leaveActiveClass:String,leaveToClass:String};Nn.props=je({},jo.props,ia);const Ht=(e,t=[])=>{te(e)?e.forEach(n=>n(...t)):e&&e(...t)},bs=e=>e?te(e)?e.some(t=>t.length>1):e.length>1:!1;function uu(e){const t={};for(const P in e)P in ia||(t[P]=e[P]);if(e.css===!1)return t;const{name:n="v",type:i,duration:l,enterFromClass:s=`${n}-enter-from`,enterActiveClass:o=`${n}-enter-active`,enterToClass:a=`${n}-enter-to`,appearFromClass:r=s,appearActiveClass:u=o,appearToClass:c=a,leaveFromClass:h=`${n}-leave-from`,leaveActiveClass:f=`${n}-leave-active`,leaveToClass:g=`${n}-leave-to`}=e,b=du(l),k=b&&b[0],I=b&&b[1],{onBeforeEnter:m,onEnter:w,onEnterCancelled:_,onLeave:F,onLeaveCancelled:U,onBeforeAppear:J=m,onAppear:A=w,onAppearCancelled:v=_}=t,G=(P,D,R)=>{jt(P,D?c:a),jt(P,D?u:o),R&&R()},V=(P,D)=>{P._isLeaving=!1,jt(P,h),jt(P,g),jt(P,f),D&&D()},q=P=>(D,R)=>{const re=P?A:w,N=()=>G(D,P,R);Ht(re,[D,N]),ws(()=>{jt(D,P?r:s),Ct(D,P?c:a),bs(re)||ys(D,i,k,N)})};return je(t,{onBeforeEnter(P){Ht(m,[P]),Ct(P,s),Ct(P,o)},onBeforeAppear(P){Ht(J,[P]),Ct(P,r),Ct(P,u)},onEnter:q(!1),onAppear:q(!0),onLeave(P,D){P._isLeaving=!0;const R=()=>V(P,D);Ct(P,h),pu(),Ct(P,f),ws(()=>{!P._isLeaving||(jt(P,h),Ct(P,g),bs(F)||ys(P,i,I,R))}),Ht(F,[P,R])},onEnterCancelled(P){G(P,!1),Ht(_,[P])},onAppearCancelled(P){G(P,!0),Ht(v,[P])},onLeaveCancelled(P){V(P),Ht(U,[P])}})}function du(e){if(e==null)return null;if(Ie(e))return[Bi(e.enter),Bi(e.leave)];{const t=Bi(e);return[t,t]}}function Bi(e){return gl(e)}function Ct(e,t){t.split(/\s+/).forEach(n=>n&&e.classList.add(n)),(e._vtc||(e._vtc=new Set)).add(t)}function jt(e,t){t.split(/\s+/).forEach(i=>i&&e.classList.remove(i));const{_vtc:n}=e;n&&(n.delete(t),n.size||(e._vtc=void 0))}function ws(e){requestAnimationFrame(()=>{requestAnimationFrame(e)})}let hu=0;function ys(e,t,n,i){const l=e._endId=++hu,s=()=>{l===e._endId&&i()};if(n)return setTimeout(s,n);const{type:o,timeout:a,propCount:r}=fu(e,t);if(!o)return i();const u=o+"end";let c=0;const h=()=>{e.removeEventListener(u,f),s()},f=g=>{g.target===e&&++c>=r&&h()};setTimeout(()=>{c(n[b]||"").split(", "),l=i(`${Et}Delay`),s=i(`${Et}Duration`),o=_s(l,s),a=i(`${yn}Delay`),r=i(`${yn}Duration`),u=_s(a,r);let c=null,h=0,f=0;t===Et?o>0&&(c=Et,h=o,f=s.length):t===yn?u>0&&(c=yn,h=u,f=r.length):(h=Math.max(o,u),c=h>0?o>u?Et:yn:null,f=c?c===Et?s.length:r.length:0);const g=c===Et&&/\b(transform|all)(,|$)/.test(i(`${Et}Property`).toString());return{type:c,timeout:h,propCount:f,hasTransform:g}}function _s(e,t){for(;e.lengthks(n)+ks(e[i])))}function ks(e){return Number(e.slice(0,-1).replace(",","."))*1e3}function pu(){return document.body.offsetHeight}const gu={esc:"escape",space:" ",up:"arrow-up",left:"arrow-left",right:"arrow-right",down:"arrow-down",delete:"backspace"},mu=(e,t)=>n=>{if(!("key"in n))return;const i=Yt(n.key);if(t.some(l=>l===i||gu[l]===i))return e(n)},hi={beforeMount(e,{value:t},{transition:n}){e._vod=e.style.display==="none"?"":e.style.display,n&&t?n.beforeEnter(e):_n(e,t)},mounted(e,{value:t},{transition:n}){n&&t&&n.enter(e)},updated(e,{value:t,oldValue:n},{transition:i}){!t!=!n&&(i?t?(i.beforeEnter(e),_n(e,!0),i.enter(e)):i.leave(e,()=>{_n(e,!1)}):_n(e,t))},beforeUnmount(e,{value:t}){_n(e,t)}};function _n(e,t){e.style.display=t?e._vod:"none"}const vu=je({patchProp:ru},Qc);let $i,Es=!1;function bu(){return $i=Es?$i:Lc(vu),Es=!0,$i}const wu=(...e)=>{const t=bu().createApp(...e),{mount:n}=t;return t.mount=i=>{const l=yu(i);if(l)return n(l,!0,l instanceof SVGElement)},t};function yu(e){return ve(e)?document.querySelector(e):e}const _u=JSON.parse('{"base":"/","lang":"en-US","title":"Wasabi Docs","description":"An archive of knowledge about Wasabi Wallet, an open-source, non-custodial and privacy-focused Bitcoin wallet for desktop.","head":[],"locales":{}}');var ku=([e,t,n])=>e==="meta"&&t.name?`${e}.${t.name}`:["title","base"].includes(e)?e:e==="template"&&t.id?`${e}.${t.id}`:JSON.stringify([e,t,n]),Eu=e=>{const t=new Set,n=[];return e.forEach(i=>{const l=ku(i);t.has(l)||(t.add(l),n.push(i))}),n},zn=e=>/^(https?:)?\/\//.test(e),Cu=e=>/^mailto:/.test(e),Pu=e=>/^tel:/.test(e),Al=e=>Object.prototype.toString.call(e)==="[object Object]",la=e=>e.replace(/\/$/,""),sa=e=>e.replace(/^\//,""),oa=(e,t)=>{const n=Object.keys(e).sort((i,l)=>{const s=l.split("/").length-i.split("/").length;return s!==0?s:l.length-i.length});for(const i of n)if(t.startsWith(i))return i;return"/"};const aa={"v-8daa1a0e":ee(()=>x(()=>import("./index.html.8f0d0be4.js"),[])),"v-5a6b3f40":ee(()=>x(()=>import("./FAQ-Contribution.html.cf858cfb.js"),["assets/FAQ-Contribution.html.cf858cfb.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-6b95acd0":ee(()=>x(()=>import("./FAQ-GeneralBitcoinPrivacy.html.f2082e67.js"),[])),"v-dbdf1f14":ee(()=>x(()=>import("./FAQ-Installation.html.6cf698ef.js"),["assets/FAQ-Installation.html.6cf698ef.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/DownloadMac.90ece9d0.js"])),"v-1a6aa296":ee(()=>x(()=>import("./FAQ-Introduction.html.ecbd8a2f.js"),["assets/FAQ-Introduction.html.ecbd8a2f.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-48b5cdc8":ee(()=>x(()=>import("./FAQ-UseWasabi.html.6e912125.js"),["assets/FAQ-UseWasabi.html.6e912125.js","assets/AddWalletButton.98ad9c28.js","assets/AddWalletAddPassword.45b736a5.js","assets/AddWalletConfirmRecoveryWords.2792528c.js","assets/CoinjoinStrategy.5455b7fb.js","assets/WalletSynchronizing.d188367c.js","assets/AddressAwaitingPayment.1f3f0347.js","assets/HistoryRightClick.a729d6cb.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/AutoStartCoinjoinThreshold.908ffaab.js","assets/SettingsBitcoinCore.fab2a9f8.js","assets/DiscreetModeActivate.e372f614.js"])),"v-74379e72":ee(()=>x(()=>import("./index.html.0c104434.js"),[])),"v-daad2d5a":ee(()=>x(()=>import("./ContributionChecklist.html.4f884c6d.js"),[])),"v-50472b68":ee(()=>x(()=>import("./LICENSE.html.7be39d8d.js"),[])),"v-1488a610":ee(()=>x(()=>import("./index.html.2fa1b77a.js"),[])),"v-7a003569":ee(()=>x(()=>import("./Security.html.ea918cc8.js"),[])),"v-ccdc4da0":ee(()=>x(()=>import("./index.html.7cb5d9f8.js"),[])),"v-6fa52768":ee(()=>x(()=>import("./Glossary-GeneralBitcoin.html.2952954a.js"),[])),"v-ceb6ce6e":ee(()=>x(()=>import("./Glossary-PrivacyWasabi.html.0d4c3e98.js"),[])),"v-338f4ef8":ee(()=>x(()=>import("./index.html.60500534.js"),[])),"v-93f154be":ee(()=>x(()=>import("./BIPs.html.4bd756fe.js"),[])),"v-9880f756":ee(()=>x(()=>import("./BackupBestPractices.html.675e45c1.js"),[])),"v-35466110":ee(()=>x(()=>import("./BitcoinFullNode.html.c430105c.js"),["assets/BitcoinFullNode.html.c430105c.js","assets/SettingsBitcoinCore.fab2a9f8.js"])),"v-9f999a04":ee(()=>x(()=>import("./BuildSource.html.16ab564a.js"),[])),"v-c0f49ad6":ee(()=>x(()=>import("./ChangeCoins.html.c8dc09c4.js"),[])),"v-9f951f20":ee(()=>x(()=>import("./CoinJoin.html.ad2cbec7.js"),["assets/CoinJoin.html.ad2cbec7.js","assets/AutoStartCoinjoinThreshold.908ffaab.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-6ba5ff68":ee(()=>x(()=>import("./ColdWasabi.html.37d7673c.js"),[])),"v-dd3fd132":ee(()=>x(()=>import("./Daemon.html.463c6cd1.js"),[])),"v-53e5ec6f":ee(()=>x(()=>import("./DeterministicBuild.html.2edc6512.js"),[])),"v-5d4dd2b1":ee(()=>x(()=>import("./DiscreetMode.html.8c0def53.js"),["assets/DiscreetMode.html.8c0def53.js","assets/DiscreetModeActivate.e372f614.js"])),"v-633fd810":ee(()=>x(()=>import("./ELI5.html.ba29f3b5.js"),[])),"v-18287a20":ee(()=>x(()=>import("./InstallPackage.html.9c7f413a.js"),["assets/InstallPackage.html.9c7f413a.js","assets/DownloadMac.90ece9d0.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-2206b16e":ee(()=>x(()=>import("./PasswordBestPractices.html.4683a4ab.js"),[])),"v-10ab876a":ee(()=>x(()=>import("./PasswordFinder.html.fe34ca22.js"),[])),"v-28d891d5":ee(()=>x(()=>import("./PayJoin.html.46db34cb.js"),[])),"v-019de88e":ee(()=>x(()=>import("./index.html.f474b7d6.js"),[])),"v-cb675e7c":ee(()=>x(()=>import("./RPC.html.faf890c8.js"),[])),"v-61c4fb84":ee(()=>x(()=>import("./Receive.html.c7e036b6.js"),["assets/Receive.html.c7e036b6.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/AddressAwaitingPayment.1f3f0347.js"])),"v-34d39e44":ee(()=>x(()=>import("./RestoreElectrum.html.2bddc161.js"),[])),"v-0495dd63":ee(()=>x(()=>import("./Send.html.846a53f0.js"),["assets/Send.html.846a53f0.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js","assets/HistoryRightClick.a729d6cb.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-03767b9c":ee(()=>x(()=>import("./Testnet.html.8baf86af.js"),[])),"v-e69d74cc":ee(()=>x(()=>import("./WalletGeneration.html.91172f61.js"),["assets/WalletGeneration.html.91172f61.js","assets/AddWalletAddPassword.45b736a5.js","assets/AddWalletConfirmRecoveryWords.2792528c.js","assets/CoinjoinStrategy.5455b7fb.js"])),"v-74a0b14c":ee(()=>x(()=>import("./WalletLoad.html.3bdf69ef.js"),["assets/WalletLoad.html.3bdf69ef.js","assets/WalletSynchronizing.d188367c.js"])),"v-059a5106":ee(()=>x(()=>import("./WalletRecovery.html.72f32cf9.js"),["assets/WalletRecovery.html.72f32cf9.js","assets/AddWalletButton.98ad9c28.js","assets/AddWalletAddPassword.45b736a5.js"])),"v-abde19dc":ee(()=>x(()=>import("./WasabiSetupVM.html.b4d60297.js"),[])),"v-91cac2f2":ee(()=>x(()=>import("./AddressReuse.html.93127d40.js"),[])),"v-e8d6a56e":ee(()=>x(()=>import("./Coins.html.d44b27c7.js"),[])),"v-6b334fc0":ee(()=>x(()=>import("./LegalConcern.html.11293b2a.js"),[])),"v-e10ef9ce":ee(()=>x(()=>import("./NetworkLevelPrivacy.html.384b39be.js"),["assets/NetworkLevelPrivacy.html.384b39be.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-40d3d192":ee(()=>x(()=>import("./index.html.ad7e1287.js"),[])),"v-1038df57":ee(()=>x(()=>import("./TransactionGraph.html.17dd6ae6.js"),[])),"v-35a4d9e3":ee(()=>x(()=>import("./TransactionSurveillanceCompanies.html.39fabb04.js"),[])),"v-0b19ce44":ee(()=>x(()=>import("./WhyFinancialPrivacy.html.a6e0b453.js"),[])),"v-19b5df2e":ee(()=>x(()=>import("./WhyPrivacyImportant.html.4811188a.js"),["assets/WhyPrivacyImportant.html.4811188a.js","assets/Logo_without_text_with_bg_dark_with_yt.82339e58.js"])),"v-3706649a":ee(()=>x(()=>import("./404.html.23597e55.js"),[]))};var Wt=(e={})=>e;function ra(e,t,n){var i,l,s;t===void 0&&(t=50),n===void 0&&(n={});var o=(i=n.isImmediate)!=null&&i,a=(l=n.callback)!=null&&l,r=n.maxWait,u=Date.now(),c=[];function h(){if(r!==void 0){var g=Date.now()-u;if(g+t>=r)return r-g}return t}var f=function(){var g=[].slice.call(arguments),b=this;return new Promise(function(k,I){var m=o&&s===void 0;if(s!==void 0&&clearTimeout(s),s=setTimeout(function(){if(s=void 0,u=Date.now(),!o){var _=e.apply(b,g);a&&a(_),c.forEach(function(F){return(0,F.resolve)(_)}),c=[]}},h()),m){var w=e.apply(b,g);return a&&a(w),k(w)}c.push({resolve:k,reject:I})})};return f.cancel=function(g){s!==void 0&&clearTimeout(s),c.forEach(function(b){return(0,b.reject)(g)}),c=[]},f}/*!
   * vue-router v4.1.6
   * (c) 2022 Eduardo San Martin Morote
   * @license MIT
diff --git a/assets/index.html.8ac9939d.js b/assets/index.html.0c104434.js
similarity index 95%
rename from assets/index.html.8ac9939d.js
rename to assets/index.html.0c104434.js
index 0f8cf4faa1..0a17c85a4f 100644
--- a/assets/index.html.8ac9939d.js
+++ b/assets/index.html.0c104434.js
@@ -1 +1 @@
-import{_ as l,r as o,o as s,c as r,a as t,d as a,w as i,b as e}from"./app.a5b7c2b2.js";const u={},c=t("h1",{id:"frequently-asked-questions",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#frequently-asked-questions","aria-hidden":"true"},"#"),e(" Frequently Asked Questions")],-1),d=t("p",null,"This is an archive with many questions that Wasabikas have asked most frequently, including:",-1),h=t("ul",null,[t("li",null,"Answers about the basics of privacy and Bitcoin in general."),t("li",null,"The important details of how to install Wasabi properly, and the best practices for using it."),t("li",null,"Further guidance for those who are interested in contributing to Wasabi.")],-1),_=t("h2",{id:"chapters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#chapters","aria-hidden":"true"},"#"),e(" Chapters")],-1);function f(A,F){const n=o("RouterLink");return s(),r("div",null,[c,d,h,_,t("ul",null,[t("li",null,[a(n,{to:"/FAQ/FAQ-Introduction.html"},{default:i(()=>[e("Introduction FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-Installation.html"},{default:i(()=>[e("Installation FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-UseWasabi.html"},{default:i(()=>[e("Use of Wasabi FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html"},{default:i(()=>[e("Bitcoin Privacy FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-Contribution.html"},{default:i(()=>[e("Contribution FAQ")]),_:1})])])])}const Q=l(u,[["render",f],["__file","index.html.vue"]]);export{Q as default};
+import{_ as l,r as o,o as s,c as r,a as t,d as a,w as i,b as e}from"./app.65e5b6fd.js";const u={},c=t("h1",{id:"frequently-asked-questions",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#frequently-asked-questions","aria-hidden":"true"},"#"),e(" Frequently Asked Questions")],-1),d=t("p",null,"This is an archive with many questions that Wasabikas have asked most frequently, including:",-1),h=t("ul",null,[t("li",null,"Answers about the basics of privacy and Bitcoin in general."),t("li",null,"The important details of how to install Wasabi properly, and the best practices for using it."),t("li",null,"Further guidance for those who are interested in contributing to Wasabi.")],-1),_=t("h2",{id:"chapters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#chapters","aria-hidden":"true"},"#"),e(" Chapters")],-1);function f(A,F){const n=o("RouterLink");return s(),r("div",null,[c,d,h,_,t("ul",null,[t("li",null,[a(n,{to:"/FAQ/FAQ-Introduction.html"},{default:i(()=>[e("Introduction FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-Installation.html"},{default:i(()=>[e("Installation FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-UseWasabi.html"},{default:i(()=>[e("Use of Wasabi FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-GeneralBitcoinPrivacy.html"},{default:i(()=>[e("Bitcoin Privacy FAQ")]),_:1})]),t("li",null,[a(n,{to:"/FAQ/FAQ-Contribution.html"},{default:i(()=>[e("Contribution FAQ")]),_:1})])])])}const Q=l(u,[["render",f],["__file","index.html.vue"]]);export{Q as default};
diff --git a/assets/index.html.395ec914.js b/assets/index.html.2fa1b77a.js
similarity index 95%
rename from assets/index.html.395ec914.js
rename to assets/index.html.2fa1b77a.js
index f5a62590b2..a728eb8d95 100644
--- a/assets/index.html.395ec914.js
+++ b/assets/index.html.2fa1b77a.js
@@ -1 +1 @@
-import{_ as o,r as s,o as r,c as l,a as e,d as t,w as n,b as a,e as d}from"./app.a5b7c2b2.js";const c={},h=d('
       Building Wasabi
      This is the place with all the nuances of how Wasabi Wallet is being built. You will also find some of the issues they are working on now, the research for future ideas, and all of the necessary information needed to quickly begin making your own invaluable contributions.
       Chapters
       Contributing to Wasabi
      ',4),u=e("h3",{id:"advanced",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#advanced","aria-hidden":"true"},"#"),a(" Advanced")],-1);function b(f,_){const i=s("RouterLink");return r(),l("div",null,[h,e("ul",null,[e("li",null,[t(i,{to:"/building-wasabi/ContributionChecklist.html"},{default:n(()=>[a("Contribution Checklist")]),_:1})])]),u,e("ul",null,[e("li",null,[t(i,{to:"/building-wasabi/Security.html"},{default:n(()=>[a("Security Policy")]),_:1})]),e("li",null,[t(i,{to:"/building-wasabi/LICENSE.html"},{default:n(()=>[a("MIT License")]),_:1})])])])}const m=o(c,[["render",b],["__file","index.html.vue"]]);export{m as default};
+import{_ as o,r as s,o as r,c as l,a as e,d as t,w as n,b as a,e as d}from"./app.65e5b6fd.js";const c={},h=d('
       Building Wasabi
      This is the place with all the nuances of how Wasabi Wallet is being built. You will also find some of the issues they are working on now, the research for future ideas, and all of the necessary information needed to quickly begin making your own invaluable contributions.
       Chapters
       Contributing to Wasabi
      ',4),u=e("h3",{id:"advanced",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#advanced","aria-hidden":"true"},"#"),a(" Advanced")],-1);function b(f,_){const i=s("RouterLink");return r(),l("div",null,[h,e("ul",null,[e("li",null,[t(i,{to:"/building-wasabi/ContributionChecklist.html"},{default:n(()=>[a("Contribution Checklist")]),_:1})])]),u,e("ul",null,[e("li",null,[t(i,{to:"/building-wasabi/Security.html"},{default:n(()=>[a("Security Policy")]),_:1})]),e("li",null,[t(i,{to:"/building-wasabi/LICENSE.html"},{default:n(()=>[a("MIT License")]),_:1})])])])}const m=o(c,[["render",b],["__file","index.html.vue"]]);export{m as default};
diff --git a/assets/index.html.f6c79981.js b/assets/index.html.60500534.js
similarity index 93%
rename from assets/index.html.f6c79981.js
rename to assets/index.html.60500534.js
index ce4bc8a41d..b076f0122a 100644
--- a/assets/index.html.f6c79981.js
+++ b/assets/index.html.60500534.js
@@ -1 +1 @@
-import{_ as o,r,o as i,c as l,a as e,d as t,w as n,b as a}from"./app.a5b7c2b2.js";const c={},d=e("h1",{id:"glossary",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#glossary","aria-hidden":"true"},"#"),a(" Glossary")],-1),h=e("p",null,"This glossary contains the explanations of common words used in Wasabi and regarding Bitcoin privacy in general. Every item contains a link to the respective full document for more details.",-1),_=e("h2",{id:"chapters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#chapters","aria-hidden":"true"},"#"),a(" Chapters")],-1);function u(m,f){const s=r("RouterLink");return i(),l("div",null,[d,h,_,e("ul",null,[e("li",null,[t(s,{to:"/glossary/Glossary-GeneralBitcoin.html"},{default:n(()=>[a("Bitcoin in general")]),_:1})]),e("li",null,[t(s,{to:"/glossary/Glossary-PrivacyWasabi.html"},{default:n(()=>[a("Privacy and Wasabi")]),_:1})])])])}const y=o(c,[["render",u],["__file","index.html.vue"]]);export{y as default};
+import{_ as o,r,o as i,c as l,a as e,d as t,w as n,b as a}from"./app.65e5b6fd.js";const c={},d=e("h1",{id:"glossary",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#glossary","aria-hidden":"true"},"#"),a(" Glossary")],-1),h=e("p",null,"This glossary contains the explanations of common words used in Wasabi and regarding Bitcoin privacy in general. Every item contains a link to the respective full document for more details.",-1),_=e("h2",{id:"chapters",tabindex:"-1"},[e("a",{class:"header-anchor",href:"#chapters","aria-hidden":"true"},"#"),a(" Chapters")],-1);function u(m,f){const s=r("RouterLink");return i(),l("div",null,[d,h,_,e("ul",null,[e("li",null,[t(s,{to:"/glossary/Glossary-GeneralBitcoin.html"},{default:n(()=>[a("Bitcoin in general")]),_:1})]),e("li",null,[t(s,{to:"/glossary/Glossary-PrivacyWasabi.html"},{default:n(()=>[a("Privacy and Wasabi")]),_:1})])])])}const y=o(c,[["render",u],["__file","index.html.vue"]]);export{y as default};
diff --git a/assets/index.html.b14d7a34.js b/assets/index.html.7cb5d9f8.js
similarity index 99%
rename from assets/index.html.b14d7a34.js
rename to assets/index.html.7cb5d9f8.js
index cf02c906ef..66ddb6a959 100644
--- a/assets/index.html.b14d7a34.js
+++ b/assets/index.html.7cb5d9f8.js
@@ -1 +1 @@
-import{_ as r,r as l,o as c,c as h,a as t,d as a,w as o,b as e,e as d}from"./app.a5b7c2b2.js";const u={},p=t("h1",{id:"getting-started",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#getting-started","aria-hidden":"true"},"#"),e(" Getting Started")],-1),w=t("p",null,"This is a short comprehensive guide on how to get started using Wasabi.",-1),b=t("p",null,"Please refer to the rest of the documentation for detailed explanations and best practices.",-1),f={class:"table-of-contents"},m=t("h2",{id:"download-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#download-wasabi","aria-hidden":"true"},"#"),e(" Download Wasabi")],-1),_={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},g={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},y=t("h2",{id:"verify-the-download",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#verify-the-download","aria-hidden":"true"},"#"),e(" Verify the Download")],-1),v=t("p",null,"Optionally, but highly recommended is to verify the downloaded package. This needs to be done in order to make sure that the just downloaded package is the authentic one and not a malicious one (replaced by a hacker etc...).",-1),k=t("h2",{id:"install-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#install-wasabi","aria-hidden":"true"},"#"),e(" Install Wasabi")],-1),x=t("p",null,"The downloaded Wasabi package needs to be installed on the computer so the application can be used.",-1),W=d('
       Welcome Screen
      The first time that you start Wasabi, you will be welcomed with information about the app. Read it and continue.
       Add Wallet
      You will be asked what kind of wallet you want to add. There are 4 options:
      • Create a new wallet
      • Connect hardware wallet
      • Import a wallet
      • Recover a wallet
      Select Create a new wallet.
      Now follow the next few steps/dialogs:
      • Give the wallet a name.
      • Write down the recovery words. (do not share these with anyone!)
      • Add a password. (do not forget it and also write it down on a separate place from the recovery words, without your password you cannot send your bitcoin!)
      • Select the coinjoin strategy: we select the default one Maximize Speed.
      DANGER
      The Recovery words can never be shown again.
      DANGER
      The password cannot be changed later on. If you lose your password you lose your bitcoin.
       Open Wallet
      Now open the wallet by entering the password.
       Receive bitcoin
      ',13),j=t("code",null,"Receive",-1),I=d('
       Coinjoin
      After you have received some bitcoin, Wasabi will automatically coinjoin the bitcoin for you.
      Coinjoin will automatically start after the incoming funds are confirmed. You need to manually press the play button in the musicbox (at the bottom of the wallet) if you received less than 0.01 BTC.
      You know that your wallet is coinjoining if you see the stop button in the musicbox and the spectrum ("waving" color animation) at the bottom of the wallet.
      Now wait while you leave Wasabi running so it can do some coinjoins. You might need to wait for (a couple of) hour(s) (sometimes less or sometimes more) to get successful coinjoins and to see your privacy percentage reach 100%.
       Funds 100% private
      After one or more coinjoins your funds should be made private as you can see in the Privacy Progress tile at the top. All your funds are private if it displays 100%. In the history you will see a shield icon(s), which indicates that you successfully participated in a coinjoin round(s).
       Use the private bitcoin
      Now that all your bitcoin is private you can use your bitcoin to:
      • Make a payment.
      • Send it to cold storage.
      TIP
      Congratulations you are now using Wasabi!
      ',11);function C(P,T){const i=l("router-link"),s=l("ExternalLinkIcon"),n=l("RouterLink");return c(),h("div",null,[p,w,b,t("nav",f,[t("ul",null,[t("li",null,[a(i,{to:"#download-wasabi"},{default:o(()=>[e("Download Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#verify-the-download"},{default:o(()=>[e("Verify the Download")]),_:1})]),t("li",null,[a(i,{to:"#install-wasabi"},{default:o(()=>[e("Install Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#welcome-screen"},{default:o(()=>[e("Welcome Screen")]),_:1})]),t("li",null,[a(i,{to:"#add-wallet"},{default:o(()=>[e("Add Wallet")]),_:1})]),t("li",null,[a(i,{to:"#open-wallet"},{default:o(()=>[e("Open Wallet")]),_:1})]),t("li",null,[a(i,{to:"#receive-bitcoin"},{default:o(()=>[e("Receive bitcoin")]),_:1})]),t("li",null,[a(i,{to:"#coinjoin"},{default:o(()=>[e("Coinjoin")]),_:1})]),t("li",null,[a(i,{to:"#funds-100-private"},{default:o(()=>[e("Funds 100% private")]),_:1})]),t("li",null,[a(i,{to:"#use-the-private-bitcoin"},{default:o(()=>[e("Use the private bitcoin")]),_:1})])])]),m,t("p",null,[e("Download Wasabi from the official website "),t("a",_,[e("wasabiwallet.io"),a(s)]),e(" or "),t("a",g,[e("wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),a(s)]),e(" if you're using the Tor Browser.")]),y,v,t("p",null,[e("How to do this depends on the desktop operating system, the detailed guides can be found here: "),a(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:o(()=>[e("Windows")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:o(()=>[e("Debian/Ubuntu")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:o(()=>[e("Other Linux")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:o(()=>[e("macOS")]),_:1})]),k,x,t("p",null,[e("How to do this depends on the desktop operating system, the detailed guides can be found here: "),a(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:o(()=>[e("Windows")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:o(()=>[e("Debian/Ubuntu")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:o(()=>[e("Other Linux")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:o(()=>[e("macOS")]),_:1})]),W,t("p",null,[e("As you can see, the new wallet is empty as it has 0.00000000 BTC. Click on "),j,e(" at the top right to "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive")]),_:1}),e(" some bitcoin to this new wallet.")]),I])}const N=r(u,[["render",C],["__file","index.html.vue"]]);export{N as default};
+import{_ as r,r as l,o as c,c as h,a as t,d as a,w as o,b as e,e as d}from"./app.65e5b6fd.js";const u={},p=t("h1",{id:"getting-started",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#getting-started","aria-hidden":"true"},"#"),e(" Getting Started")],-1),w=t("p",null,"This is a short comprehensive guide on how to get started using Wasabi.",-1),b=t("p",null,"Please refer to the rest of the documentation for detailed explanations and best practices.",-1),f={class:"table-of-contents"},m=t("h2",{id:"download-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#download-wasabi","aria-hidden":"true"},"#"),e(" Download Wasabi")],-1),_={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},g={href:"http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion",target:"_blank",rel:"noopener noreferrer"},y=t("h2",{id:"verify-the-download",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#verify-the-download","aria-hidden":"true"},"#"),e(" Verify the Download")],-1),v=t("p",null,"Optionally, but highly recommended is to verify the downloaded package. This needs to be done in order to make sure that the just downloaded package is the authentic one and not a malicious one (replaced by a hacker etc...).",-1),k=t("h2",{id:"install-wasabi",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#install-wasabi","aria-hidden":"true"},"#"),e(" Install Wasabi")],-1),x=t("p",null,"The downloaded Wasabi package needs to be installed on the computer so the application can be used.",-1),W=d('
       Welcome Screen
      The first time that you start Wasabi, you will be welcomed with information about the app. Read it and continue.
       Add Wallet
      You will be asked what kind of wallet you want to add. There are 4 options:
      • Create a new wallet
      • Connect hardware wallet
      • Import a wallet
      • Recover a wallet
      Select Create a new wallet.
      Now follow the next few steps/dialogs:
      • Give the wallet a name.
      • Write down the recovery words. (do not share these with anyone!)
      • Add a password. (do not forget it and also write it down on a separate place from the recovery words, without your password you cannot send your bitcoin!)
      • Select the coinjoin strategy: we select the default one Maximize Speed.
      DANGER
      The Recovery words can never be shown again.
      DANGER
      The password cannot be changed later on. If you lose your password you lose your bitcoin.
       Open Wallet
      Now open the wallet by entering the password.
       Receive bitcoin
      ',13),j=t("code",null,"Receive",-1),I=d('
       Coinjoin
      After you have received some bitcoin, Wasabi will automatically coinjoin the bitcoin for you.
      Coinjoin will automatically start after the incoming funds are confirmed. You need to manually press the play button in the musicbox (at the bottom of the wallet) if you received less than 0.01 BTC.
      You know that your wallet is coinjoining if you see the stop button in the musicbox and the spectrum ("waving" color animation) at the bottom of the wallet.
      Now wait while you leave Wasabi running so it can do some coinjoins. You might need to wait for (a couple of) hour(s) (sometimes less or sometimes more) to get successful coinjoins and to see your privacy percentage reach 100%.
       Funds 100% private
      After one or more coinjoins your funds should be made private as you can see in the Privacy Progress tile at the top. All your funds are private if it displays 100%. In the history you will see a shield icon(s), which indicates that you successfully participated in a coinjoin round(s).
       Use the private bitcoin
      Now that all your bitcoin is private you can use your bitcoin to:
      • Make a payment.
      • Send it to cold storage.
      TIP
      Congratulations you are now using Wasabi!
      ',11);function C(P,T){const i=l("router-link"),s=l("ExternalLinkIcon"),n=l("RouterLink");return c(),h("div",null,[p,w,b,t("nav",f,[t("ul",null,[t("li",null,[a(i,{to:"#download-wasabi"},{default:o(()=>[e("Download Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#verify-the-download"},{default:o(()=>[e("Verify the Download")]),_:1})]),t("li",null,[a(i,{to:"#install-wasabi"},{default:o(()=>[e("Install Wasabi")]),_:1})]),t("li",null,[a(i,{to:"#welcome-screen"},{default:o(()=>[e("Welcome Screen")]),_:1})]),t("li",null,[a(i,{to:"#add-wallet"},{default:o(()=>[e("Add Wallet")]),_:1})]),t("li",null,[a(i,{to:"#open-wallet"},{default:o(()=>[e("Open Wallet")]),_:1})]),t("li",null,[a(i,{to:"#receive-bitcoin"},{default:o(()=>[e("Receive bitcoin")]),_:1})]),t("li",null,[a(i,{to:"#coinjoin"},{default:o(()=>[e("Coinjoin")]),_:1})]),t("li",null,[a(i,{to:"#funds-100-private"},{default:o(()=>[e("Funds 100% private")]),_:1})]),t("li",null,[a(i,{to:"#use-the-private-bitcoin"},{default:o(()=>[e("Use the private bitcoin")]),_:1})])])]),m,t("p",null,[e("Download Wasabi from the official website "),t("a",_,[e("wasabiwallet.io"),a(s)]),e(" or "),t("a",g,[e("wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion"),a(s)]),e(" if you're using the Tor Browser.")]),y,v,t("p",null,[e("How to do this depends on the desktop operating system, the detailed guides can be found here: "),a(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:o(()=>[e("Windows")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:o(()=>[e("Debian/Ubuntu")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:o(()=>[e("Other Linux")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:o(()=>[e("macOS")]),_:1})]),k,x,t("p",null,[e("How to do this depends on the desktop operating system, the detailed guides can be found here: "),a(n,{to:"/using-wasabi/InstallPackage.html#windows"},{default:o(()=>[e("Windows")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#debian-and-ubuntu"},{default:o(()=>[e("Debian/Ubuntu")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#other-linux"},{default:o(()=>[e("Other Linux")]),_:1}),e(", "),a(n,{to:"/using-wasabi/InstallPackage.html#macos"},{default:o(()=>[e("macOS")]),_:1})]),W,t("p",null,[e("As you can see, the new wallet is empty as it has 0.00000000 BTC. Click on "),j,e(" at the top right to "),a(n,{to:"/using-wasabi/Receive.html"},{default:o(()=>[e("receive")]),_:1}),e(" some bitcoin to this new wallet.")]),I])}const N=r(u,[["render",C],["__file","index.html.vue"]]);export{N as default};
diff --git a/assets/index.html.5ce1fb70.js b/assets/index.html.8f0d0be4.js
similarity index 97%
rename from assets/index.html.5ce1fb70.js
rename to assets/index.html.8f0d0be4.js
index 46f06e2feb..20ee9f4c58 100644
--- a/assets/index.html.5ce1fb70.js
+++ b/assets/index.html.8f0d0be4.js
@@ -1 +1 @@
-import{_ as r,r as s,o as h,c,a as t,b as e,d as o,w as i}from"./app.a5b7c2b2.js";const l={},u=t("hr",null,null,-1),d={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},_={href:"https://github.com/zkSNACKs/WasabiDoc/",target:"_blank",rel:"noopener noreferrer"},f={href:"https://web.archive.org/web/20220804041943/https://docs.wasabiwallet.io/",target:"_blank",rel:"noopener noreferrer"},p=t("h2",{id:"how-to-use-this-documentation",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-to-use-this-documentation","aria-hidden":"true"},"#"),e(" How to use this documentation")],-1),b=t("p",null,"This documentation is a good place to start your education on how to use Wasabi Wallet, as it is a thorough archive about many nuances of Bitcoin privacy.",-1),m=t("h3",{id:"explain-like-i-m-5",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#explain-like-i-m-5","aria-hidden":"true"},"#"),e(" Explain Like I'm 5")],-1),w=t("h3",{id:"stand-alone-chapters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#stand-alone-chapters","aria-hidden":"true"},"#"),e(" Stand-alone chapters")],-1),k=t("h3",{id:"search-function",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#search-function","aria-hidden":"true"},"#"),e(" Search function")],-1);function x(y,g){const a=s("ExternalLinkIcon"),n=s("RouterLink");return h(),c("div",null,[u,t("p",null,[e("This is "),t("a",d,[e("Wasabi Wallet's"),o(a)]),e(" open source documentation. Here you will find information about the nuances of privacy in Bitcoin, how Wasabi solves some of the existing problems, and how you can use this tool to defend yourself. Everyone is welcome to make the Wasabi Wallet documentation better, by contributing "),t("a",_,[e("on GitHub"),o(a)]),e("! The documentation of Wasabi Wallet 1.0 is archived "),t("a",f,[e("here"),o(a)]),e(".")]),p,b,m,t("p",null,[e("If you are new to Wasabi and want to get a quick tutorial on how to use it, you may "),o(n,{to:"/using-wasabi/ELI5.html"},{default:i(()=>[e("start here")]),_:1}),e(".")]),w,t("p",null,[e("If you are interested in the nuances of how one specific aspect of Wasabi works, then check-out the "),o(n,{to:"/using-wasabi/"},{default:i(()=>[e("detailed chapters here")]),_:1}),e(".")]),k,t("p",null,[e("If you have a question about some particular detail, then use the search function at the top right corner to browse the entire archive, including the "),o(n,{to:"/FAQ/"},{default:i(()=>[e("frequently asked questions")]),_:1}),e(".")])])}const W=r(l,[["render",x],["__file","index.html.vue"]]);export{W as default};
+import{_ as r,r as s,o as h,c,a as t,b as e,d as o,w as i}from"./app.65e5b6fd.js";const l={},u=t("hr",null,null,-1),d={href:"https://wasabiwallet.io",target:"_blank",rel:"noopener noreferrer"},_={href:"https://github.com/zkSNACKs/WasabiDoc/",target:"_blank",rel:"noopener noreferrer"},f={href:"https://web.archive.org/web/20220804041943/https://docs.wasabiwallet.io/",target:"_blank",rel:"noopener noreferrer"},p=t("h2",{id:"how-to-use-this-documentation",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#how-to-use-this-documentation","aria-hidden":"true"},"#"),e(" How to use this documentation")],-1),b=t("p",null,"This documentation is a good place to start your education on how to use Wasabi Wallet, as it is a thorough archive about many nuances of Bitcoin privacy.",-1),m=t("h3",{id:"explain-like-i-m-5",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#explain-like-i-m-5","aria-hidden":"true"},"#"),e(" Explain Like I'm 5")],-1),w=t("h3",{id:"stand-alone-chapters",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#stand-alone-chapters","aria-hidden":"true"},"#"),e(" Stand-alone chapters")],-1),k=t("h3",{id:"search-function",tabindex:"-1"},[t("a",{class:"header-anchor",href:"#search-function","aria-hidden":"true"},"#"),e(" Search function")],-1);function x(y,g){const a=s("ExternalLinkIcon"),n=s("RouterLink");return h(),c("div",null,[u,t("p",null,[e("This is "),t("a",d,[e("Wasabi Wallet's"),o(a)]),e(" open source documentation. Here you will find information about the nuances of privacy in Bitcoin, how Wasabi solves some of the existing problems, and how you can use this tool to defend yourself. Everyone is welcome to make the Wasabi Wallet documentation better, by contributing "),t("a",_,[e("on GitHub"),o(a)]),e("! The documentation of Wasabi Wallet 1.0 is archived "),t("a",f,[e("here"),o(a)]),e(".")]),p,b,m,t("p",null,[e("If you are new to Wasabi and want to get a quick tutorial on how to use it, you may "),o(n,{to:"/using-wasabi/ELI5.html"},{default:i(()=>[e("start here")]),_:1}),e(".")]),w,t("p",null,[e("If you are interested in the nuances of how one specific aspect of Wasabi works, then check-out the "),o(n,{to:"/using-wasabi/"},{default:i(()=>[e("detailed chapters here")]),_:1}),e(".")]),k,t("p",null,[e("If you have a question about some particular detail, then use the search function at the top right corner to browse the entire archive, including the "),o(n,{to:"/FAQ/"},{default:i(()=>[e("frequently asked questions")]),_:1}),e(".")])])}const W=r(l,[["render",x],["__file","index.html.vue"]]);export{W as default};
diff --git a/assets/index.html.91658148.js b/assets/index.html.ad7e1287.js
similarity index 96%
rename from assets/index.html.91658148.js
rename to assets/index.html.ad7e1287.js
index 467cb221a2..780338e89f 100644
--- a/assets/index.html.91658148.js
+++ b/assets/index.html.ad7e1287.js
@@ -1 +1 @@
-import{_ as r,r as l,o,c as s,a,d as t,w as n,b as e,e as c}from"./app.a5b7c2b2.js";const h={},d=c('
       Why Wasabi
      This is the place with an introduction to privacy in general, and why especially financial privacy is so important. Here is covered how Bitcoin is already good for privacy, much better than the incumbent monetary system. And why Wasabi can make Bitcoin an even better tool of self-defense by default.
       Chapters
       Why Privacy
      ',4),y=a("h3",{id:"privacy-in-bitcoin",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#privacy-in-bitcoin","aria-hidden":"true"},"#"),e(" Privacy in Bitcoin")],-1);function u(w,p){const i=l("RouterLink");return o(),s("div",null,[d,a("ul",null,[a("li",null,[t(i,{to:"/why-wasabi/WhyPrivacyImportant.html"},{default:n(()=>[e("Why Privacy is Important")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/WhyFinancialPrivacy.html"},{default:n(()=>[e("Why Financial Privacy is Especially Important")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/LegalConcern.html"},{default:n(()=>[e("CoinJoin Legal Concern")]),_:1})])]),y,a("ul",null,[a("li",null,[t(i,{to:"/why-wasabi/Coins.html"},{default:n(()=>[e("Coins")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[e("Address Reuse")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/TransactionGraph.html"},{default:n(()=>[e("Transaction Graph")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/NetworkLevelPrivacy.html"},{default:n(()=>[e("Network-Level Privacy")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html"},{default:n(()=>[e("Transaction Surveillance Companies")]),_:1})])])])}const _=r(h,[["render",u],["__file","index.html.vue"]]);export{_ as default};
+import{_ as r,r as l,o,c as s,a,d as t,w as n,b as e,e as c}from"./app.65e5b6fd.js";const h={},d=c('
       Why Wasabi
      This is the place with an introduction to privacy in general, and why especially financial privacy is so important. Here is covered how Bitcoin is already good for privacy, much better than the incumbent monetary system. And why Wasabi can make Bitcoin an even better tool of self-defense by default.
       Chapters
       Why Privacy
      ',4),y=a("h3",{id:"privacy-in-bitcoin",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#privacy-in-bitcoin","aria-hidden":"true"},"#"),e(" Privacy in Bitcoin")],-1);function u(w,p){const i=l("RouterLink");return o(),s("div",null,[d,a("ul",null,[a("li",null,[t(i,{to:"/why-wasabi/WhyPrivacyImportant.html"},{default:n(()=>[e("Why Privacy is Important")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/WhyFinancialPrivacy.html"},{default:n(()=>[e("Why Financial Privacy is Especially Important")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/LegalConcern.html"},{default:n(()=>[e("CoinJoin Legal Concern")]),_:1})])]),y,a("ul",null,[a("li",null,[t(i,{to:"/why-wasabi/Coins.html"},{default:n(()=>[e("Coins")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/AddressReuse.html"},{default:n(()=>[e("Address Reuse")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/TransactionGraph.html"},{default:n(()=>[e("Transaction Graph")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/NetworkLevelPrivacy.html"},{default:n(()=>[e("Network-Level Privacy")]),_:1})]),a("li",null,[t(i,{to:"/why-wasabi/TransactionSurveillanceCompanies.html"},{default:n(()=>[e("Transaction Surveillance Companies")]),_:1})])])])}const _=r(h,[["render",u],["__file","index.html.vue"]]);export{_ as default};
diff --git a/assets/index.html.1b5ce783.js b/assets/index.html.f474b7d6.js
similarity index 98%
rename from assets/index.html.1b5ce783.js
rename to assets/index.html.f474b7d6.js
index 638e4c9ba1..3f880feeb9 100644
--- a/assets/index.html.1b5ce783.js
+++ b/assets/index.html.f474b7d6.js
@@ -1 +1 @@
-import{_ as s,r as n,o as u,c as d,a,d as l,w as t,b as e,e as o}from"./app.a5b7c2b2.js";const r={},h=o('
       Using Wasabi
      Here are all the nuances of how to use Wasabi Wallet in all regards. Starting with a step-by-step guide on how to verify and install the software. Further tutorials about the different parts of the wallet, for newbies and power users.
       Chapters
       Introducing Wasabi
      ',4),c=a("h3",{id:"installing-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#installing-wasabi","aria-hidden":"true"},"#"),e(" Installing Wasabi")],-1),b=a("h3",{id:"using-wasabi-1",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#using-wasabi-1","aria-hidden":"true"},"#"),e(" Using Wasabi")],-1),g=a("h3",{id:"best-practices",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#best-practices","aria-hidden":"true"},"#"),e(" Best Practices")],-1),w=a("h3",{id:"restoring-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#restoring-wasabi","aria-hidden":"true"},"#"),e(" Restoring Wasabi")],-1),_=a("h3",{id:"advanced-installing-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-installing-wasabi","aria-hidden":"true"},"#"),e(" Advanced Installing Wasabi")],-1),f=a("h3",{id:"advanced-using-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-using-wasabi","aria-hidden":"true"},"#"),e(" Advanced Using Wasabi")],-1);function m(p,W){const i=n("RouterLink");return u(),d("div",null,[h,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/ELI5.html"},{default:t(()=>[e("Explain Wasabi like I'm 5")]),_:1})])]),c,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/InstallPackage.html"},{default:t(()=>[e("Install package")]),_:1})])]),b,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/WalletGeneration.html"},{default:t(()=>[e("Wallet Generation")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/WalletLoad.html"},{default:t(()=>[e("Wallet Load")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Receive.html"},{default:t(()=>[e("Receive")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/CoinJoin.html"},{default:t(()=>[e("CoinJoin")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Send.html"},{default:t(()=>[e("Send")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/ColdWasabi.html"},{default:t(()=>[e("Hardware Wallet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BitcoinFullNode.html"},{default:t(()=>[e("Bitcoin Full Node")]),_:1})])]),g,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/PasswordBestPractices.html"},{default:t(()=>[e("Passwords")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BackupBestPractices.html"},{default:t(()=>[e("Backups")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/ChangeCoins.html"},{default:t(()=>[e("Change Coins")]),_:1})])]),w,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/WalletRecovery.html"},{default:t(()=>[e("Recover a Wallet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/RestoreElectrum.html"},{default:t(()=>[e("Restoring Wasabi Wallet to Electrum")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/PasswordFinder.html"},{default:t(()=>[e("Password Finder")]),_:1})])]),_,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/BuildSource.html"},{default:t(()=>[e("Build from source code")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/DeterministicBuild.html"},{default:t(()=>[e("Deterministic Build")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/WasabiSetupVM.html"},{default:t(()=>[e("Wasabi Setup using Virtual Machines")]),_:1})])]),f,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/Daemon.html"},{default:t(()=>[e("Headless Wasabi Daemon")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/RPC.html"},{default:t(()=>[e("RPC Interface")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/DiscreetMode.html"},{default:t(()=>[e("Discreet Mode")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/PayJoin.html"},{default:t(()=>[e("PayJoin")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Testnet.html"},{default:t(()=>[e("Testnet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BIPs.html"},{default:t(()=>[e("Supported BIPs")]),_:1})])])])}const B=s(r,[["render",m],["__file","index.html.vue"]]);export{B as default};
+import{_ as s,r as n,o as u,c as d,a,d as l,w as t,b as e,e as o}from"./app.65e5b6fd.js";const r={},h=o('
       Using Wasabi
      Here are all the nuances of how to use Wasabi Wallet in all regards. Starting with a step-by-step guide on how to verify and install the software. Further tutorials about the different parts of the wallet, for newbies and power users.
       Chapters
       Introducing Wasabi
      ',4),c=a("h3",{id:"installing-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#installing-wasabi","aria-hidden":"true"},"#"),e(" Installing Wasabi")],-1),b=a("h3",{id:"using-wasabi-1",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#using-wasabi-1","aria-hidden":"true"},"#"),e(" Using Wasabi")],-1),g=a("h3",{id:"best-practices",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#best-practices","aria-hidden":"true"},"#"),e(" Best Practices")],-1),w=a("h3",{id:"restoring-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#restoring-wasabi","aria-hidden":"true"},"#"),e(" Restoring Wasabi")],-1),_=a("h3",{id:"advanced-installing-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-installing-wasabi","aria-hidden":"true"},"#"),e(" Advanced Installing Wasabi")],-1),f=a("h3",{id:"advanced-using-wasabi",tabindex:"-1"},[a("a",{class:"header-anchor",href:"#advanced-using-wasabi","aria-hidden":"true"},"#"),e(" Advanced Using Wasabi")],-1);function m(p,W){const i=n("RouterLink");return u(),d("div",null,[h,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/ELI5.html"},{default:t(()=>[e("Explain Wasabi like I'm 5")]),_:1})])]),c,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/InstallPackage.html"},{default:t(()=>[e("Install package")]),_:1})])]),b,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/WalletGeneration.html"},{default:t(()=>[e("Wallet Generation")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/WalletLoad.html"},{default:t(()=>[e("Wallet Load")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Receive.html"},{default:t(()=>[e("Receive")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/CoinJoin.html"},{default:t(()=>[e("CoinJoin")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Send.html"},{default:t(()=>[e("Send")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/ColdWasabi.html"},{default:t(()=>[e("Hardware Wallet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BitcoinFullNode.html"},{default:t(()=>[e("Bitcoin Full Node")]),_:1})])]),g,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/PasswordBestPractices.html"},{default:t(()=>[e("Passwords")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BackupBestPractices.html"},{default:t(()=>[e("Backups")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/ChangeCoins.html"},{default:t(()=>[e("Change Coins")]),_:1})])]),w,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/WalletRecovery.html"},{default:t(()=>[e("Recover a Wallet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/RestoreElectrum.html"},{default:t(()=>[e("Restoring Wasabi Wallet to Electrum")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/PasswordFinder.html"},{default:t(()=>[e("Password Finder")]),_:1})])]),_,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/BuildSource.html"},{default:t(()=>[e("Build from source code")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/DeterministicBuild.html"},{default:t(()=>[e("Deterministic Build")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/WasabiSetupVM.html"},{default:t(()=>[e("Wasabi Setup using Virtual Machines")]),_:1})])]),f,a("ul",null,[a("li",null,[l(i,{to:"/using-wasabi/Daemon.html"},{default:t(()=>[e("Headless Wasabi Daemon")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/RPC.html"},{default:t(()=>[e("RPC Interface")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/DiscreetMode.html"},{default:t(()=>[e("Discreet Mode")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/PayJoin.html"},{default:t(()=>[e("PayJoin")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/Testnet.html"},{default:t(()=>[e("Testnet")]),_:1})]),a("li",null,[l(i,{to:"/using-wasabi/BIPs.html"},{default:t(()=>[e("Supported BIPs")]),_:1})])])])}const B=s(r,[["render",m],["__file","index.html.vue"]]);export{B as default};
diff --git a/building-wasabi/ContributionChecklist.html b/building-wasabi/ContributionChecklist.html
index 9dc124bc03..0001146375 100644
--- a/building-wasabi/ContributionChecklist.html
+++ b/building-wasabi/ContributionChecklist.html
@@ -24,10 +24,10 @@
     
     Contribution Checklist | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Contribution Checklist
      So you're interested in contributing to Wasabi - welcome!
      Embrace the open-source crypto-anarchy!
      No one is here to tell you what to do, and it is not required to work on an existing issue to contribute to Wasabi. Contributors are free to work on their own forked versions on whatever they want, however they wish and without any permission from anyone. With that being said, in order to maximize the usefulness/impact of your work, it's a good idea to consult with other Wasabikas via Slack, GitHub, or other communication channels before setting out on any serious contribution effort.
      This checklist will get you plugged in and productive as quickly as possible.
       Who is a contributor?
      A contributor is any individual who works to improve and add value to Wasabi and its users.
      You can become a Wasabika!
      Wasabi Wallet is free and open-source software, but contributing is not just about writing code. This means anything from fixing typos in documentation, answering questions of fellow Wasabikas, creating videos, podcasts and memes, implementing new Wasabi features and everything in-between. All such contributions are very welcomed and greatly appreciated.
       Say hello and get started
      • Join our Slackopen in new window and especially check out our GitHub repositoryopen in new window.
      • Introduce yourself, say a bit about your skills and interests. This will help others point you in the right direction.
      • Explore the communication channels and find out what the peers are tinkering on, learn about the project and who is contributing in what way. This will help you to find the interesting challenges you can work on.
      • Wasabi Research Club is a weekly online call, focused mainly on Bitcoin privacy. Everyone is welcome to join the discussions. However, being familiar with the topic (if there is any) is recommended.
      Discussions might be recorded and published on the Wasabi Wallet YouTube channelopen in new window.
      You can find the schedule, call link, past recordings and more at the Wasabi Research Club repositoryopen in new window.
       Learn how Wasabikas work
      It’s a simple set of collaboration rules based on GitHub’s fork and pull request model, and a foundational part of how we work together.
       What to work on
      Education and development are vitally important aspects of Bitcoin privacy and Wasabi Wallet specifically.
      The more Wasabi users there are, the better their privacy, because anonymity loves companyopen in new window.
      The better UX and privacy Wasabi provides, the more there will be users, because of network effectopen in new window.
       Education Contributor
      1. Videos, podcasts, memes and articles are great ways of sharing information to your peers. You can create wallet tutorials, record insightful discussions, write articles or make memes about Wasabi and privacy.
      2. Organizing events and doing presentations about Wasabi Wallet and Bitcoin privacy. Connecting like-minded individuals, who want to take control of their own financial privacy and teaching them about the awesome tools that are available, can be life changing.
      3. Helping and teaching new users, once you are familiar with the software, is something that can't be underestimated. You can do this in any social media like Twitter, Telegram, Reddit etc or in your own neighborhood.
      [zkSNACKs Ltd.](https://zksnacks.com/) is known for compensating educators who consistently help out new users or create good content.
      The company is actively sponsoring Bitcoin events and organizing Contribution Gamesopen in new window. In case you have been contributing already, feel free to let other Wasabikas know by sending us a link to your content in Slackopen in new window.
       GitHub Contributor
      1. Find a problem somewhere in Wasabi-land that (a) needs fixing or improvement and (b) is a match for your skills and interests. Browse open issuesopen in new window and ask around about what other contributors think needs fixing. Because while you don’t need anybody’s permission and you can work on whatever you want, you’ll want to know up front whether anybody else is going to care about the work you do.
      2. Do work to fix that problem. Submit your fix for review with a pull request (for codeopen in new window and documentationopen in new window changes) or with a GitHub issueopen in new window (for everything else).
      3. Request that others review your work. The best way to do this is by writing good commit comments and pull request/issue descriptions that clearly explain the problem your work is intended to solve, why it’s important, and why you fixed it the way you did. Make it as easy as possible for others to review your work. Make it a pleasure for others to review your work.
      4. Incorporate review feedback you get until your fix gets merged or is otherwise accepted.
      5. Repeat steps 1–4.
      Remember: every contributor is free to work on what they want, including maintainers who may or may not want to review and merge your pull request if they don't have any prior context for it, or reason to believe it's worth spending their time on.
      Reviews are for everybody!
      If you want to be really popular around here, don’t just submit your own work, but also spend time reviewing the work of others.
      
-    
+    
   
 
diff --git a/building-wasabi/LICENSE.html b/building-wasabi/LICENSE.html
index 7ca5cbbe71..43a9a87d71 100644
--- a/building-wasabi/LICENSE.html
+++ b/building-wasabi/LICENSE.html
@@ -24,10 +24,10 @@
     
     MIT License | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       MIT License
      Wasabi Wallet and Wasabi documentation is licensed under the MIT License.
      A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
      PermissionsLimitationsConditions
      Commercial useLiabilityLicense and copyright notice
      ModificationWarranty
      Distribution
      Private use
      You can check the license hereopen in new window.
      
-    
+    
   
 
diff --git a/building-wasabi/Security.html b/building-wasabi/Security.html
index 805703595b..4afe24285e 100644
--- a/building-wasabi/Security.html
+++ b/building-wasabi/Security.html
@@ -24,7 +24,7 @@
     
     Security Policy | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Security Policy
      Feel free to report a vulnerability as a GitHub issue only if the vulnerability you found does not compromise users' privacy or security.
      If it does, then pay great care to responsible disclosure. Send an email to adam.ficsor73@gmail.com, preferably using PGP encryption: 21D7 CA45 565D BCCE BE45 115D B4B7 2266 C47E 075E
      -----BEGIN PGP PUBLIC KEY BLOCK-----
@@ -234,6 +234,6 @@
 =9mRH
 -----END PGP PUBLIC KEY BLOCK-----
 
      
-    
+    
   
 
diff --git a/building-wasabi/index.html b/building-wasabi/index.html
index fb2e3d3ab6..bf104fcecc 100644
--- a/building-wasabi/index.html
+++ b/building-wasabi/index.html
@@ -24,10 +24,10 @@
     
     Building Wasabi | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Building Wasabi
      This is the place with all the nuances of how Wasabi Wallet is being built. You will also find some of the issues they are working on now, the research for future ideas, and all of the necessary information needed to quickly begin making your own invaluable contributions.
       Chapters
       Contributing to Wasabi
       Advanced
      
-    
+    
   
 
diff --git a/getting-started/index.html b/getting-started/index.html
index 9c5dd92e7d..fba819a823 100644
--- a/getting-started/index.html
+++ b/getting-started/index.html
@@ -24,10 +24,10 @@
     
     Getting Started | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Getting Started
      This is a short comprehensive guide on how to get started using Wasabi.
      Please refer to the rest of the documentation for detailed explanations and best practices.
       Download Wasabi
      Download Wasabi from the official website wasabiwallet.ioopen in new window or wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onionopen in new window if you're using the Tor Browser.
       Verify the Download
      Optionally, but highly recommended is to verify the downloaded package. This needs to be done in order to make sure that the just downloaded package is the authentic one and not a malicious one (replaced by a hacker etc...).
      How to do this depends on the desktop operating system, the detailed guides can be found here: Windows, Debian/Ubuntu, Other Linux, macOS
       Install Wasabi
      The downloaded Wasabi package needs to be installed on the computer so the application can be used.
      How to do this depends on the desktop operating system, the detailed guides can be found here: Windows, Debian/Ubuntu, Other Linux, macOS
       Welcome Screen
      The first time that you start Wasabi, you will be welcomed with information about the app. Read it and continue.
       Add Wallet
      You will be asked what kind of wallet you want to add. There are 4 options:
      • Create a new wallet
      • Connect hardware wallet
      • Import a wallet
      • Recover a wallet
      Select Create a new wallet.
      Now follow the next few steps/dialogs:
      • Give the wallet a name.
      • Write down the recovery words. (do not share these with anyone!)
      • Add a password. (do not forget it and also write it down on a separate place from the recovery words, without your password you cannot send your bitcoin!)
      • Select the coinjoin strategy: we select the default one Maximize Speed.
      DANGER
      The Recovery words can never be shown again.
      DANGER
      The password cannot be changed later on. If you lose your password you lose your bitcoin.
       Open Wallet
      Now open the wallet by entering the password.
       Receive bitcoin
      As you can see, the new wallet is empty as it has 0.00000000 BTC. Click on Receive at the top right to receive some bitcoin to this new wallet.
       Coinjoin
      After you have received some bitcoin, Wasabi will automatically coinjoin the bitcoin for you.
      Coinjoin will automatically start after the incoming funds are confirmed. You need to manually press the play button in the musicbox (at the bottom of the wallet) if you received less than 0.01 BTC.
      You know that your wallet is coinjoining if you see the stop button in the musicbox and the spectrum ("waving" color animation) at the bottom of the wallet.
      Now wait while you leave Wasabi running so it can do some coinjoins. You might need to wait for (a couple of) hour(s) (sometimes less or sometimes more) to get successful coinjoins and to see your privacy percentage reach 100%.
       Funds 100% private
      After one or more coinjoins your funds should be made private as you can see in the Privacy Progress tile at the top. All your funds are private if it displays 100%. In the history you will see a shield icon(s), which indicates that you successfully participated in a coinjoin round(s).
       Use the private bitcoin
      Now that all your bitcoin is private you can use your bitcoin to:
      • Make a payment.
      • Send it to cold storage.
      TIP
      Congratulations you are now using Wasabi!
      
-    
+    
   
 
diff --git a/glossary/Glossary-GeneralBitcoin.html b/glossary/Glossary-GeneralBitcoin.html
index 5d17016940..73158feae9 100644
--- a/glossary/Glossary-GeneralBitcoin.html
+++ b/glossary/Glossary-GeneralBitcoin.html
@@ -24,10 +24,10 @@
     
     Bitcoin in general | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Bitcoin in general
       Address
      A Bitcoin invoice address commits to a public key or script which defines who can spend the coin. It is specified in the output of a transaction, and it should only be used once. Wasabi uses the bech32 and bech32m format to encode native segregated witness addresses. Read more: Bitcoin addresses
       Bitcoin
      Bitcoin is a peer-to-peer electronic cash system. An innovative payment network and a new kind of money. It is a decentralized digital currency without a central bank or single administrator that can be sent from user to user on the peer-to-peer bitcoin blockchain network without the need for intermediaries.
       Bitcoin Core
      Bitcoin Core is an open-source project which maintains and releases Bitcoin client software called Bitcoin Core, considered to be Bitcoin's reference implementation. It is a direct descendant of the original Bitcoin software client released by Satoshi Nakamoto after he published the famous Bitcoin whitepaper.
      Bitcoin Core consists of both full-node software for fully validating the blockchain as well as a Bitcoin wallet. The project also currently maintains related software such as the cryptography library libsecp256k1 and others located at GitHub. Read more: Bitcoin Core Websiteopen in new window
       Bitcoin Improvement Proposal (BIP)
      Bitcoin Improvement Proposal. A design document for introducing features or information to Bitcoin. Read more: Wasabi Supported BIPs
       Bitcoin Knots
      Bitcoin Knots is a derivative of Bitcoin Core with a collection of improvements backported from and sometimes maintained outside of Core's master git tree. Since version 1.1.11, Wasabi has partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything. Read more: Bitcoin Knots Websiteopen in new window
       Block
      A block is a batch of valid Bitcoin transactions and its hash must be a value below a certain difficulty target to prove the work of the miner. Each block references the hash of the previous block, thus creating a hash chain of blocks. On average a new block is mined every 10 minutes.
       Blockchain
      The blockchain is the one chain of valid Bitcoin blocks with the most accumulated proof of work. It is an append-only data structure with new blocks being added on average every 10 minutes. Because of its uniquely verifiable and global consensus, it is a revolutionary standard for time, thus some call it timechain.
       Change
      In a transaction where the provided input coins are larger than the value sent to the destination address, then the leftover change is sent to a new address of the same wallet. Read more: Change coins
       Child Pays For Parent (CPFP)
      Child Pays For Parent (CPFP) is a fee bumping technique where a user spends an output from a low fee rate unconfirmed transaction in a child transaction with a high fee rate in order to encourage miners to include both transactions in a block.
       Coinbase
      A special field used as the sole input for coinbase transactions. The coinbase allows claiming the block reward and provides up to 100 bytes for arbitrary data.
       Coinbase Transaction
      The first transaction in a block. Always created by a miner, it includes a single coinbase.
       Cold Storage
      Refers to keeping a reserve of important Bitcoin secrets offline. Cold storage is achieved when Bitcoin private keys are created and stored in a secure offline environment. Cold storage is important for anyone with bitcoin holdings. Online computers are vulnerable to hackers and should not be used to store a significant amount of bitcoin. Read more: Cold Wasabi Protocol
       Confirmations
      Once a transaction is included in a block, it has one confirmation. As soon as another block is mined on the same blockchain, the transaction has two confirmations, and so on. Six or more confirmations is considered sufficient proof that a transaction cannot be reversed.
       Consensus
      When several nodes, usually most nodes on the network, all have the same blocks in their locally-validated best blockchain.
       Consensus Rules
      The block validation rules that full nodes follow to stay in consensus with other nodes.
       Custodial (Wallet or Mixer)
      A custodial wallet is any wallet where the private keys of your coins are in the hands of a third party. In essence, they operate similarly to traditional banks.
      A custodial mixer needs you to send your bitcoins to a central part before mixing. This means that you are at risk of being stolen from.
       Difficulty
      A network-wide setting that controls how much computation is required to produce a proof of work.
       Difficulty Retargeting (Difficulty Adjustment)
      A network-wide recalculation of the difficulty that occurs once every 2,016 blocks and considers the hashing power of the previous 2,016 blocks.
       Difficulty Target
      A difficulty at which all the computation in the network will find blocks approximately every 10 minutes. It specifies the numeric value the hash of a block must not be above to be considered a valid block.
       ECDSA
      ECDSA (Elliptic Curve Digital Signature Algorithm) is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners.
       Fork
      Fork, also known as accidental fork, occurs when two or more blocks have the same block height, forking the blockchain. Typically occurs when two or more miners find blocks at nearly the same time. Can also happen as part of an attack.
       Full node
      Any computer that connects to the Bitcoin network is called a node. Nodes that fully verify all of the rules of Bitcoin are called full nodes. Full nodes download every block and transaction and check them against Bitcoin's consensus rules.
       Fungibility
      Fungibility is a desirable property of Bitcoin UTXOs that are indistinguishable from each other. Read more: Transaction surveillance companies attempting to destroy fungibility
       Genesis Block
      The first block in the blockchain, used to initialize the cryptocurrency.
       Hard Fork
      Hard fork, also known as hard-forking change, is a permanent divergence in the blockchain, it occurs when non-upgraded nodes can not validate blocks created by upgraded nodes that follow newer consensus rules. The upgraded nodes break the rules of the legacy nodes. Not to be confused with fork, soft fork, software fork or Git fork.
       Hardware Wallet (HWW)
      A hardware wallet is a special type of Bitcoin wallet which generates and stores the user's private keys on a dedicated hardware device. Read more: Hardware Wallet FAQs
       Hash
      A cryptographic hash function takes any input of arbitrary size [the message] and computes a value of fixed size that is unique to the input, which is called a hash or a digest. If one bit of the input changes, the output will be completely different [avalanche effect]. And there are no two messages that result in the same hash [collision resistance]. The only way to get any given input, is by computing all possible inputs, it is a one-way function [pre-image resistance]. Bitcoin uses the SHA256 in many parts of the protocol.
       Hierarchical Deterministic (HD) Protocol
      The Hierarchical Deterministic key creation and transfer protocol (BIP32), which allows creating child keys from parent keys in a hierarchy.
       Hierarchical Deterministitc (HD) Wallet
      Wallets using the Hierarchical Deterministic Protocol key creation and transfer protocol (BIP32).
       Hot Wallet
      A hot wallet is a software wallet that runs on a device which is connected to the Internet. Wasabi is a hot wallet by default.
       Input
      Input, transaction input, or TxIn is an input in a Bitcoin transaction which contains two fields: a unique transaction hash and an index number, which references one utxo of a previous transaction which is spent in this transaction.
       Lightning Network (LN)
      Lightning Network is a proposed implementation of Hashed Timelock Contracts (HTLCs) with bi-directional payment channels which allows payments to be securely routed across multiple peer-to-peer payment channels. This allows the formation of a network where any peer on the network can pay any other peer even if they don't directly have a channel open between each other.
       Mainnet
      The original and main network for Bitcoin transactions, where satoshis have real economic value.
       Mempool
      The Bitcoin Mempool (memory pool) is a collection of all transaction data in a block that have been verified by Bitcoin nodes, but are not yet confirmed. Read more: How does Wasabi know of incoming transactions to the mempool?
       Merkle Root
      The root node of a merkle tree, a descendant of all the hashed pairs in the tree. Block headers must include a valid merkle root descended from all transactions in that block.
       Merkle Tree
      A tree constructed by hashing paired data (the leaves), then pairing and hashing the results until a single hash remains, the merkle root. In Bitcoin, the leaves are almost always transactions from a single block.
       Miner
      A Bitcoin user that attempts to find valid proof of work for new candidate blocks, by repeated hashing until the difficulty target is met.
       Mining Reward
      An amount of satoshis included in each new block as a reward by the network to the miner who found the proof of work solution. Initially it was 50 bitcoin per block, which is halved every 210 000 blocks, or roughly 4 years. This leads to a total money supply of just below 21 million bitcoin.
       Multisignature (multisig)
      Multisignature (m-of-n multisig) refers to requiring more than one key to authorize a Bitcoin transaction. Only with m signatures of n public keys can the bitcoin be spent. Read more: Can I generate a multi signature script?
       Non-Custodial (Wallet or Mixer)
      A non-custodial wallet is any wallet where the private keys of your coins are in your hands. Non-custodial wallets give you full control over your bitcoins.
      A non-custodial mixer like Wasabi eliminates the risk that the coordinator can steal your bitcoin. Each participant verifies the proposed transaction, and signs it only if it is valid. This signature is only valid for this transaction, so any attempt to change the transaction after the fact is futile. The funds will always be in a Bitcoin address that you control.
       Nonce
      The nonce in a Bitcoin block is a 32-bit (4-byte) field whose value is set so that the hash of the block will contain a run of leading zeros. The rest of the fields may not be changed, as they have a defined meaning.
       Off-chain Transaction
      An off-chain transaction is the movement of value outside of the blockchain. While an on-chain transaction - usually referred to as simply a transaction - modifies the blockchain and depends on the blockchain to determine its validity. An off-chain transaction relies on other methods to record and validate the transaction.
       Output
      Output, transaction output, or TxOut is an output in a Bitcoin transaction which contains two fields: a value field for transferring zero or more satoshis and a pubkey script for indicating what conditions must be fulfilled for those satoshis to be further spent.
       P2PKH
      Many transactions processed on the Bitcoin network spend outputs locked with a Pay-to-Public-Key-Hash or P2PKH script. These outputs contain a locking script that locks the output to a public key hash, more commonly known as a Bitcoin address. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key.
       P2SH
      P2SH or Pay-to-Script-Hash is a type of transaction that simplifies the use of complex transaction scripts. With P2SH the complex script that details the spending conditions (redeem script) is committed to with a hash in the locking script.
       P2TR
      A pay-to-taproot (P2TR), also known as a Taproot or Bech32m address, is the most recent and advanced bitcoin address format. Taproot introduces more advanced security, privacy, flexibility and scaling to bitcoin.
       P2WPKH
      The signature of a P2WPKH (Pay-to-Witness-Public-Key-Hash) contains the same information as a P2PKH spending, but is located in the witness field instead of the scriptSig field.
       Paper Wallet
      In the most specific sense, a paper wallet is a document containing all the secrets to spend a Bitcoin UTXO. It is a way of storing bitcoin offline as a physical document.
       Partially Signed Bitcoin Transaction (PSBT)
      PSBT is a binary transaction format which contains the information necessary for a signer to produce signatures for the transaction and holds the signatures for an input while the input does not have a complete set of signatures. The signer can be offline as all necessary information will be provided in the transaction. Read more: BIP 174 Partially Signed Bitcoin Transaction Formatopen in new window
       Pay-to-Witness-Public-Key-Hash (P2WPKH)
      The signature of a P2WPKH contains the same information as a Pay-to-Public-Key-Hash (P2PKH) spending, but is located in the witness field instead of the scriptSig field. The scriptPubKey is also modified. Read more: BIP 84 derivation scheme for P2WPKH based accountsopen in new window
       Payment Channels
      A payment channel is class of techniques designed to allow users to make multiple Bitcoin transactions without committing all of the transactions to the Bitcoin blockchain. In a typical payment channel, only two transactions are added to the blockchain, one funding and one closing transaction, but a nearly unlimited number of payments can be made between the participants.
       Plausible deniability
      Plausible deniability is the ability to deny knowledge of or responsibility for any damnable actions committed by others in an organizational hierarchy because of a lack of evidence that can confirm their participation, even if they were personally involved in or at least willfully ignorant of the actions.
       Private Key
      A private key is a large number that must be chosen at random, it is thus a very secure password and should be kept secret. With knowledge of this number, anyone can easily compute the public key, and a signature over any message. It can also be used to decrypt any message that was encrypted to the public key corresponding to the private key. In Bitcoin, a signature over a valid transaction message gives the right to spend a coin, thus knowledge of the private key corresponds to ownership of the bitcoin. Read more: Bitcoin private keys
       Proof of Work (POW)
      One of the requirements for a Bitcoin block to be valid is its hash should be below a certain difficulty target. In order to create a valid block, a miner must repeatedly hash a candidate block with a changing nonce until by sheer luck he finds a hash with low value. By providing this pre-image block, anyone can verify the amount of computational energy that a miner on average should have invested in order to find this block, and this is what is known as Proof of Work.
       Public Key
      A public key is calculated by multiplying the private key to the generator point of an elliptic curve. Given only the public key, the private key cannot be calculated. Anyone can encrypt a message using a public key. This encrypted message (cyphertext) can only be decrypted through the related private key. Given a public key and a signature over a message, anyone can verify that the signer had the private key and the message. In Bitcoin, the public key is the pseudonymous identity of the owner of a coin. Read more: Bitcoin private keys
       Regtest
      A local testing environment in which developers can instantly generate blocks on demand for testing events, and can create private satoshis with no real-world value.
       Replace by Fee (RBF)
      Replacing one version of an unconfirmed transaction with a different version of the transaction that pays a higher transaction fee.
       satoshi (sat)
      A satoshi is the smallest denomination of bitcoin that can be recorded on the blockchain. It is the equivalent of 0.00000001 bitcoin and is named after the creator of Bitcoin, Satoshi Nakamoto.
       Satoshi Nakamoto
      Satoshi Nakamoto is the name used by the person or group of people who designed Bitcoin and created its original reference implementation. As a part of the implementation, they also devised the first blockchain database. In the process they were the first to solve the double-spending problem for digital currency in a decentralized and self verifying nature. Their real identity remains unknown.
       Schnorr Digital Signature Scheme
      Schnorr Digital Signature Scheme is one of the digital signature algorithms used by Bitcoin to ensure that funds can only be spent by their rightful owners. Schnorr signatures and public keys can be aggregated, meaning that multiple parties with unique private keys can sign the same message, which can be verified in batches instead of individually.
       Script
      Bitcoin uses a scripting system for transactions. Forth-like, Script is simple, stack-based and processed from left to right. It is purposefully not Turing-complete, with no loops.
       ScriptPubKey
      ScriptPubKey or pubkey script, is a script included in outputs which sets the conditions that must be fulfilled for those satoshis to be spent. Data for fulfilling the conditions can be provided in a signature script.
       ScriptSig
      ScriptSig or signature script, is the data generated by a spender which is almost always used as variables to satisfy a pubkey script.
       Segregated Witness (SegWit)
      Segregated Witness is a structure where the witness [signature or redeem script] is stored separately from the transaction Merkle tree. This is separated because the witness contains only data concerning transaction validity, but not about transaction effect. Read more: Why Wasabi uses only SegWit
       Simplified Payment Verification (SPV)
      SPV is a method for verifying particular transactions were included in a block without downloading the entire block. The method is used by some lightweight Bitcoin clients.
       Soft Fork
      A soft fork is a change to the Bitcoin consensus rules that is backwards compatible. Users of this update do not break the rules of legacy users, but rather restrict themselves to a more narrow rule set.
       Taproot
      Taproot is an upgrade to Bitcoin which introduces several new features. Taproot integrates the Schnorr digital signature scheme into Bitcoin, upgrading Bitcoin’s core cryptography. Taproot builds on the SegWit upgrade to improve Bitcoin’s privacy and lower transaction fees. Taproot makes future Bitcoin upgrades easier by reforming Bitcoin’s scripting language.
       Testnet
      A testing environment in which users can obtain and spend satoshis that have no real-world value on a global network that is very similar to the Bitcoin mainnet.
       Timechain
      Timechain is a synonym of blockchain. It emphasizes the achievement of the Bitcoin protocol to establish consensus on the temporal order of transactions so to prevent double-spends.
       Transaction
      In simple terms, a transfer of bitcoin. More precisely, a transaction is a signed data structure expressing a transfer of value and consisting mainly of inputs and outputs. Transactions are transmitted over the Bitcoin network, collected by miners, and included into blocks, made permanent on the blockchain.
       Transaction Fees
      A transaction has a fee payment to the miner who includes the transaction in a valid block. It is implied by the difference of inputs - outputs. Read more: What fee should I select?
       Unspent Transaction Output (UTXO)
      UTXO is an unspent transaction output that can be spent as an input in a new transaction. Read more: How can I select UTXOs for CoinJoin?
       Wallet
      Software that holds all your Bitcoin addresses and secret keys. Use it to send, receive, and store your bitcoin.
      
-    
+    
   
 
diff --git a/glossary/Glossary-PrivacyWasabi.html b/glossary/Glossary-PrivacyWasabi.html
index b8b7376f38..0d03024cc1 100644
--- a/glossary/Glossary-PrivacyWasabi.html
+++ b/glossary/Glossary-PrivacyWasabi.html
@@ -24,10 +24,10 @@
     
     Privacy and Wasabi | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Privacy and Wasabi
       #twoweeks
      The #twoweeks is a fun inside joke often used in the Wasabi documentation and, more generally, in the Internet community. In the case of Wasabi documentation, it usually indicates the arrival of a new function or update, to which the future date is still uncertain.
      E.g. "Lightning Network is coming to Wasabi in #twoweeks"
       Address Reuse
      Address reuse refers to the use of the same address for multiple transactions, this is very bad for privacy. Read more: Address reuse
       Anonymity Score (anonscore)
      Anonymity score is a new way to estimate the entropy level of a UTXO in an unequal-but-highly-composable output value coinjoin. The anonymity score is a metric to help the wallet decide when it's time to stop the coinjoining process. Read more: What is the anonymity score?
       Anonymity Set (anonset)
      The anonymity set is effectively the size of the group you are hiding in during a CoinJoin. It's the quantity of equal value outputs of one CoinJoin transaction. Read more: What is the anonymity set?
       Backend
      The part of a software system that is not usually visible or accessible to a user of that systemopen in new window. In the case of Wasabi, the backend functions as the coinjoin coordinator and provides data to the client (user) like block filters, exchange rate, and network estimations (mempool).
       Block filters
      A filter representing a compact list of addresses in one block. Wasabi checks locally if any block filter contains transactions with addresses of the wallet. No public keys are sent to any third party server, thus it is very private. Read more: BIP 158: Compact Block Filters for Light Clientsopen in new window
       Blockchain Analysis
      Blockchain analysis is used by transaction surveillance companies to follow the transaction history of coins. Techniques like the common-input-ownership heuristic or change detection are used to create a cluster of transactions belonging to one user. Read more: Blockchain Analysis
       Bloom Filter
      A filter used primarily by SPV clients to request only block headers and merkle proofs of a given transaction from full nodes. This is very bad for privacy, as third party servers learn about which addresses you are interested in. Read more: BIP 37: Connection Bloom Filteringopen in new window
       Change Address Detection
      Many Bitcoin transactions have change outputs. It would be a serious privacy leak if the change address can be somehow found, as it would link the ownership of the (now spent) inputs with a new output. Read more: Change coins
       Chaumian CoinJoin
      A Chaumian CoinJoin is a special type of CoinJoin that utilizes Chaumian [or Schnorr] blind signatures to prevent the central coordinator from spying on the linkage between inputs and outputs. Read more: Use of blind signatures in CoinJoin
       Client
      A software that allows a computer to function as a client in a networkopen in new window. In the case of Wasabi, the client is a Wasabi Wallet software version which a user has on his own local machine. The client can communicate with the backend.
       Cluster
      Which entities know about which coins. For example, this coin belongs to a cluster that is known by a KYC exchange and Alice. Read more: What is the cluster history?
       Coin Control
      The possiblity for the user to manually select UTXO's. It is mostly used for sending, so the user can select which UTXO's should be used as the inputs of the transaction. Read more: Coin Control Best Practices
       CoinJoin (CJ)
      CoinJoin is a trustless method for combining multiple Bitcoin payments from multiple spenders into a single transaction to make it more difficult for outside parties to determine which spender paid which recipient. Read more: What is a CoinJoin?
       Coinjoin Strategy
      A Coinjoin Strategy contains instructions for the automatic "coinjoin robot" about configurations like when and how much to coinjoin. Read more: Coinjoin Strategy
       CoinJoined coins
      Coins that have successfully participated in a CoinJoin (with the exception of the change) and thus lose their association to a previous cluster. Read more: What is the privacy I get after mixing with Wasabi?
       Common-Input-Ownership heuristic
      This is a heuristic or assumption which says that if a transaction has more than one input then all those inputs are owned by the same entity.
       Coordinator
      The coordinator is a server which creates CoinJoins and accepts UTXOs in the mix. Read more: How does my wallet communicate with the Wasabi coordinator server?
       Daemon
      A daemon is a command line interface to run Wasabi without the GUI (Graphical User Interface). Read more: Headless Wasabi Daemon
       Discreet Mode
      Discreet Mode is a Wasabi feature that hides sensitive and critical information on the wallet itself, which is useful for screenshots. Read more: Discreet Mode
       Dust
      Dust is an UTXO that is uneconomical to spend. Also, small portions of bitcoin can lead to serious consequences for one's privacy, for example the so called forced address reuse attack. Read more: What is the dust threshold
       Label
      A label can be added to a coin, as a small note on who knows this coin belongs to you. Good labelling can help the user and the wallet to make better privacy conscious decisions later on when spending. Read more: Why do I have to label my address
       Know Your Customer (KYC)
      KYC (Know Your Customer) is the process of a business being forced to identify and verify the identity of its clients, and to share this information with a government. The term is also used to refer to the bank regulation which governs these activities. Read more: AML/KYC Information
       Observers
      A way to track who knows about the ownership of your coins. Not to be confused with a description of a transaction. Read more: The importance of labeling
       Pay to EndPoint (P2EP)
      Pay to EndPoint is when the receiver is reachable over the internet and the sender communicates with the receiver to coordinate a more advanced transaction. The Tor onion service, IP address or domain of the receiver is included in a BIP21 Bitcoin URI payment link.
       Peers
      Peers in our documentation refers mainly to Bitcoin and Wasabi Wallet users, but it also means people. They are literally peers in the network, or in the CoinJoin.
       RPC
      RPC, or Remote Procedure Call, is an interface to interact with Wasabi Wallet programmatically. Read more: RPC Interface
       Taint
      Taint is equivalent to the 'trail' that a Bitcoin transaction leaves during the course of its journey. The taint analysis of a Bitcoin transaction evaluates the association between an address involved in the chain of transactions. Read more: Blockchain Analysis
       The Onion Router (Tor)
      Tor (The Onion Router) is free and open-source software for enabling anonymous communication. It is widely used by Wasabi. Read more: How does Tor protect my network level privacy?
       Transaction Surveillance Company
      A transaction surveillance company is one which attempts to spy on all Bitcoin users. Their business model is usually to sell the data to any government, corporation or individual willing to pay for their services. Read more: Transaction Surveillance Companies
       Tumbling / Tumbler
      Tumbling is a synonym of 'Mixing'. Similarly, Tumbler is the synonym of 'Mixer'.
       TurboSync
      A feature in Wasabi to reduce wallet loading time. With TurboSync, some addresses (internal keys only) are skipped and tested in the background. Read more: TurboSync
       WabiSabi
      WabiSabi is a protocol for constructing coinjoin transactions with the aid of a centralized coordinator. It utilizes keyed-verification anonymous credentials, homomorphic value commitments, and zero knowledge proofs to achieve privacy and flexibility. Read more: WabiSabiopen in new window
       Wallet fingerprinting
      A careful analyst sometimes deduces which software created a certain transaction, because many different wallet softwares don't always create transactions in exactly the same way.
       Wasabika
      Wasabikas are builders, users and supporters of Wasabi in general.
       XPUB (Extended Public Key)
      An xpub, also known as Extended Public Key, is a part of BIP-32 that will allow you to observe your wallet without the private key (xpriv).
      ZeroLink is a framework to holistically design a privacy and fungibility setup for Bitcoin. This encompasses more than just a single CoinJoin transaction, but also includes network level privacy defense against third party spying. Read more: ZeroLink: the Bitcoin Fungibility Framework
      
-    
+    
   
 
diff --git a/glossary/index.html b/glossary/index.html
index 5a1ea3e3a8..3b6bd3a622 100644
--- a/glossary/index.html
+++ b/glossary/index.html
@@ -24,10 +24,10 @@
     
     Glossary | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Glossary
      This glossary contains the explanations of common words used in Wasabi and regarding Bitcoin privacy in general. Every item contains a link to the respective full document for more details.
       Chapters
      
-    
+    
   
 
diff --git a/index.html b/index.html
index f1a9c65f9e..6af4b5c826 100644
--- a/index.html
+++ b/index.html
@@ -24,10 +24,10 @@
     
      | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
      Wasabi Documentation
      An archive of knowledge about Wasabi Wallet, an open-source, non-custodial and privacy-focused Bitcoin wallet for desktop.
       Reclaim Your Privacy → 
      Open-source
      Don't trust, verify. Wasabi is libre and open source software under the MIT license. You have full access to every single line of code, and you can do with it as you please.
      Non-custodial
      Not your keys, not your bitcoin. With Wasabi, you are always in full control of your private and public keys, you never share them with any third party.
      Privacy-focused
      Privacy is the ability to choose what you reveal to others. Wasabi is designed with one goal in mind, to protect your sensitive financial data, on the network level and on the blockchain level.
      This is Wasabi Wallet'sopen in new window open source documentation. Here you will find information about the nuances of privacy in Bitcoin, how Wasabi solves some of the existing problems, and how you can use this tool to defend yourself. Everyone is welcome to make the Wasabi Wallet documentation better, by contributing on GitHubopen in new window! The documentation of Wasabi Wallet 1.0 is archived hereopen in new window.
       How to use this documentation
      This documentation is a good place to start your education on how to use Wasabi Wallet, as it is a thorough archive about many nuances of Bitcoin privacy.
       Explain Like I'm 5
      If you are new to Wasabi and want to get a quick tutorial on how to use it, you may start here.
       Stand-alone chapters
      If you are interested in the nuances of how one specific aspect of Wasabi works, then check-out the detailed chapters here.
       Search function
      If you have a question about some particular detail, then use the search function at the top right corner to browse the entire archive, including the frequently asked questions.
      
-    
+    
   
 
diff --git a/using-wasabi/BIPs.html b/using-wasabi/BIPs.html
index 606b3ef9b2..130bcc46e5 100644
--- a/using-wasabi/BIPs.html
+++ b/using-wasabi/BIPs.html
@@ -24,10 +24,10 @@
     
     Supported BIPs | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Supported BIPs
      Wasabi Wallet strives toward establishing solid industry best practices and standards. Here is a list of all the supported and integrated Bitcoin Improvement Proposals:
       What is supported
       What is not supported
      
-    
+    
   
 
diff --git a/using-wasabi/BackupBestPractices.html b/using-wasabi/BackupBestPractices.html
index 2895f1e43f..dd0281a020 100644
--- a/using-wasabi/BackupBestPractices.html
+++ b/using-wasabi/BackupBestPractices.html
@@ -24,10 +24,10 @@
     
     Backup Best Practices | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Backup Best Practices
       Common mediums for backups
       Written on a piece of paper
      • Anyone who can see it, can steal it
      • Handwriting can be hard to read or completely illegible
      • Human error in transcription can cause errors on the end product
      • Paper can rot, be torn, burn, or be smoke damaged
       Printed on a piece of paper
      • Anyone who can see it, can steal it
      • Type of printer - non-laser printers ink can run if the paper gets wet
      • Have to trust printer - some have internet connections, wifi, and memory
      • Paper can rot, be torn, burn, or be smoke damaged
       On laminated paper
      • Anyone who can see it, can steal it
      • Lamination is prone to degradation over time, as well as punctures or cuts that could allow moisture to get trapped in the paper and cause deterioration or rotting in some circumstances | store in cool dry place
      • Can burn or be smoke damaged
      • 'Fireproof' & 'Fire-resistant' boxes can help protect paper in a small house fire but be warned that they can sometimes fall apart in the fire and get wet if the fire is put out with water. Remember people can just carry out a small safe
       Engraved / etched / ablated / stamped on a piece of metal
      • Anyone who can see it, can steal it
      • Some metals can deteriorate or corrode, choose a good metal; also store your metal away from direct contact other metals.
      • Some metals that are corrosion resistant have low melting points, are extremely expensive, or hard to machine.
      • Metals can still deform or melt from heat, destroying any engraved SK. "Most house fires do not burn hotter than 1,200 degrees Fahrenheit. This temperature is typically associated with the hottest portion of a home, which is in the roof area. Homes that burn for longer than 30 minutes or consist of multiple levels sometimes burn at higher temperatures." You want to pick a metal that won't be destroyed by a fire. So magnesium, tin, and lead are all out as engraving materials.
      • Silver, gold, copper, brass, bronze, nickel, cobalt, would survive the housefire unmelted. Some Aluminium alloys can survive but you have to have the right ones. At around 1500° Steel and Nickel should be okay. Titanium is above the housefire range and so is tungsten, however tungsten rings are known to shatter due to the brittle nature of the very hard metal.
       Stored digitally on a computer
      • Computers can crash, making data recovery expensive
      • Data can still technically be recovered after a system is abandoned by the user. In some cases data can be recovered after multiple overwriting attempts and physical destruction (as long as the attacker can get all or most the of pieces) so if you copy files to a new computer and ditch the old one, be careful.
      • Can burn or be smoke damaged
      • A traditional hard disc drive can have data corrupted by powerful magnetic fields and can physically shatter
      • A non-negligible amount of HDDs suffer from factory defects that will cause them to fail unexpectedly during their lifetime
      • Accidents can happen that could result in loss of data
      • Solid state drives (SSDs) will lose data if unpowered, they may last years before this becomes a problem but it is unwise to store long-term data in unpowered SSDs
      • Connecting to the internet is another attack vector and the safety is only as good as the encryption used; I don't know what I would recommend but it wouldn't be BitLocker. Someone could be trying to break into the computer constantly. Even with good encryption if the machine or location is compromised the key could be stolen as soon as it is decrypted.
      • There are a lot of ongoing threats with computers, from 0-day exploits to firmware exploits and malicious USB cords
      • External HDDs are good for storage for a few years at least if stored properly
      • If not connected to internet, safety is only as good as the physical protection encryption used; could someone break into the location and copy the data without anyone noticing?
       Stored digitally on CD, floppy disk, laserdisc, or mini-disc
      • Plastics break down over time and with exposure to heat, humidity, regular light, all sorts of chemicals, even the oxygen in the air. This can lead to the loss of your data when stored on a medium made of plastic or written/printed on plastic.
      • Can burn or be smoke damaged
      • Can be physically damaged, making data recovery expensive or even impossible
      • Magnetic media (tapes, floppy disc) can be damaged by magnets
      • Data can become difficult to recover if the software and/or hardware to decode is old, don't use proprietary formats
       Stored digitally on a flash drive
      • Can break and have to be physically repaired before use
      • Rapidly changing magnetic fields (See MRIs) can damage the data stored on flash drives
      • Can burn, or be smoke damaged
      • Can become corroded from salt water or some atmospheric conditions
      • If they break apart, some lighting conditions can cause data corruption (you can also put them back together and often still get the data)
      • Different devices are inconsistent. Even similar devices from the same production batch can be different. There are large quality differences in drives, but I am assuming you aren't using these for anything but storage.
      • There are some fake flash drives that look like they saved the data but you can't get it back later.
      • Flash drives are not advised for long term storage; they can be used as one part of a multi-medium-location-format plan.
       A pre-funded physical bitcoin coin (where the manufacturer generates and installs the secret key)
      • The medium that the key is on is often paper/plastic which can burn or be smoke damaged
      • Trust in the manufacturer themselves, they could copy the key
      • Trust in their key generation procedure
      • Trust in the operational security of the manufacturer, they could be generating the keys on their everyday computer
      • Trust no one is successfully spying on them, electronically, looking through their documents while they are out of town, or with tiny tin foil hat cameras or long range ones
      • Trust that the object was not tampered with in delivery
      • Trust that no one has tampered with the object since you got it
      
-    
+    
   
 
diff --git a/using-wasabi/BitcoinFullNode.html b/using-wasabi/BitcoinFullNode.html
index 6ed10be741..ea662e411f 100644
--- a/using-wasabi/BitcoinFullNode.html
+++ b/using-wasabi/BitcoinFullNode.html
@@ -24,10 +24,10 @@
     
     Bitcoin Full Node | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Bitcoin Full Node
       The importance of running a full node
      When running a Bitcoin full node, you define the precise monetary rules that you voluntarily agree on. Nobody else forces this choice upon you. Thus any sovereign individual who wants to claim financial independence must run a full node. Once your own rules are firmly established, your software discovers other nodes in the Bitcoin peer-to-peer network which do not break your rules. These peers send you transactions and blocks which are valid according to their set of rules, and you verify for yourself if they are also correct for you. If one of the proposed transactions breaks your own rules, then you mark it as invalid, disconnect from and ban the node who sent you the malicious transaction.
      Claim your monetary sovereignty
      With your full node you define, verify, and enforce the rules of your sound money Bitcoin.
      Only by running a full node, do you verify by yourself that the money you receive is actually valid bitcoin. You do not trust an external third party, and thus you also do not leak any sensitive financial information.
      There are several software implementations that function as a full node, for example, Bitcoin Coreopen in new window, Bitcoin Knotsopen in new window, or LibBitcoinopen in new window.
       How does Wasabi use your Bitcoin full node
      Wasabi currently has a work in progress partial Bitcoin Knots integration. As of now, the zkSNACKs coordinating server broadcasts BIP 158 block filtersopen in new window to all Wasabi clients, who locally check if the filter hits for their public keys. Then you know that this block has a transaction of yours included, or maybe it is a false positive.
      Work in progress
      The zkSNACKs server has to be trusted to serve correct filters. This current work in progress integration does not verify consensus within Wasabi.
      If a full node is connected to Wasabi, then the relevant block is fetched from this trusted node, and not from a random P2P node. Wasabi also queries if your local mempool has unconfirmed transactions that are of interest to you. Further, your full node is used to estimate the current mining fee level based on the bitcoind smartfee algorithm. Your full node is not used to broadcast your transactions, as this is done through a random peer-to-peer node with a new tor identity, which is better for your network-level privacy.
      The future goal is that the local full node (Knots) is used to generate the BIP 158 block filters from the verified blocks. Only then is there full verification, and no trust in the zkSNACKs server.
       bitcoind within Wasabi
      Wasabi Wallet ships with Bitcoin Knotsopen in new window. This means that every Wasabi client has the necessary software to run a Bitcoin full node and define, verify, and enforce monetary consensus with bitcoind, but this verification is not yet used within Wasabi itself, it is a work in progress. By default, bitcoind is not started together with Wasabi. This must be activated explicitly in the settings because this is a bandwidth, CPU and storage-intensive program. It is optional to keep bitcoind running even after Wasabi Wallet is shut down, so as to verify blocks as soon as they are received.
      Wasabi Wallet Bitcoin Knots full node integration
       Using an already existing local Bitcoin full node
      If you have a Bitcoin full node already pre-installed on the same computer you use to run Wasabi Wallet, then Wasabi will use your node by default. You do not need to change anything in the settings, it should work plug and play. This is especially useful to save on bandwidth, as you have already downloaded and verified a block with your full node, so you don't need to download it again with Wasabi.
       Using an already existing remote Bitcoin full node
      If you have a Bitcoin full node already on a remote computer, then Wasabi Wallet can use this too. In the Bitcoin settings, specify the local IP address and port or the Tor onion service of your full node.
      Wasabi Wallet remote Bitcoin P2P full node endpoint
       Verify that Wasabi is connected to your full node
      There are two ways to confirm that your Wasabi client is connected to your own full node.
      First, in the Wasabi logs. Once you receive a transaction Wasabi downloads the block containing that transaction from your node, and in the logs you should see: Block {hash} acquired from node '{node}'.
      Second, by checking the connected peers inside your full node. Wasabi will show up as one of the connected peers while it is downloading a block. You can check this in the Bitcoin Core / Knots GUI by clicking on Window -> Peers. During the period when Wasabi is fetching a block, it will show up in the User Agent column. Alternatively, you can use the Bitcoin RPC call bitcoin-cli getpeerinfo and see the Wasabi client listed.
      
-    
+    
   
 
diff --git a/using-wasabi/BuildSource.html b/using-wasabi/BuildSource.html
index dd2b95fd1d..4a1f8c1a8b 100644
--- a/using-wasabi/BuildSource.html
+++ b/using-wasabi/BuildSource.html
@@ -24,10 +24,10 @@
     
     Build from source code | Wasabi Docs
     
-    
+    
   
   
-    
      Wasabi Docs
       Build from source code
       Introduction
      You can compile the source code in order to get the most recent commits by the developers. This enables you to try out features or fixes that are not yet released. This can be the main repository master branch for those changes that should be in the next release, or developer branches for cutting edge features. Be aware that these branches might be unstable and can include bugs that lead to a loss of funds, so use with caution and on testnet.
       Get The Requirements
      1. Install Gitopen in new window
      2. Install .NET 7.0 SDKopen in new window for "Build apps"
        Optional for privacy
        You can disable .NET's telemetry, which is sending some usage information to Microsoft, by typing:
        export DOTNET_CLI_TELEMETRY_OPTOUT=1 on Linux and macOS.
        setx DOTNET_CLI_TELEMETRY_OPTOUT 1 to disable it permanently on Windows.
       Get Wasabi
      Clone Wasabi repository:
      git clone https://github.com/zkSNACKs/WalletWasabi.git
+    
      Wasabi Docs
       Build from source code
       Introduction
      You can compile the source code in order to get the most recent commits by the developers. This enables you to try out features or fixes that are not yet released. This can be the main repository master branch for those changes that should be in the next release, or developer branches for cutting edge features. Be aware that these branches might be unstable and can include bugs that lead to a loss of funds, so use with caution and on testnet.
       Get The Requirements
      1. Install Gitopen in new window
      2. Install .NET 8.0 SDKopen in new window for "Build apps"
        Optional for privacy
        You can disable .NET's telemetry, which is sending some usage information to Microsoft, by typing:
        export DOTNET_CLI_TELEMETRY_OPTOUT=1 on Linux and macOS.
        setx DOTNET_CLI_TELEMETRY_OPTOUT 1 to disable it permanently on Windows.
       Get Wasabi
      Clone Wasabi repository:
      git clone https://github.com/zkSNACKs/WalletWasabi.git
 cd WalletWasabi/WalletWasabi.Fluent.Desktop
 
       Run Wasabi
      Build and run the Wasabi client application from the WalletWasabi.Fluent.Desktop folder:
      dotnet run
 
       Update Wasabi
      git pull
@@ -36,6 +36,6 @@
 git checkout branchname
 git pull
 
      
-    
+    
   
 
diff --git a/using-wasabi/ChangeCoins.html b/using-wasabi/ChangeCoins.html
index fe642733b4..0a90d4e35f 100644
--- a/using-wasabi/ChangeCoins.html
+++ b/using-wasabi/ChangeCoins.html
@@ -24,10 +24,10 @@
     
     Change Coins | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Change coins
       Types of change
       Non-Coinjoin change
      Let's assume you want to send 0.5 bitcoin to Alice. You enter Alice's address in the To field (destination address), and set the Amount to 0.5 BTC. This will be one output of the transaction.
      Since your chosen UTXO is worth 2 bitcoins, after sending 0.5 bitcoin to Alice there will be 1.5 bitcoins change from the original amount. This leftover amount will automatically go to a new address in your wallet, and this is called the change output.
      This leftover 1.5 bitcoins change UTXO is connected to the input UTXO of the transaction, and thus also has an anonymity set of 1. As a result, when you send this leftover/change coin in a new transaction, it is clear to any observer that you were part of the transaction that sent 0.5 bitcoin to someone.
      This process is applicable to any Bitcoin transaction where the sent amount is less than the total value of the input UTXO.
       Coinjoin change
      In some few cases, especially for the wealthiest user of a coinjoin, there will be an anonymity score 1 output in a coinjoin transaction. Eventhough it is not trivial to link those to the inputs of the same user, they should be handled with care. Wasabi will not automatically spend those change coins in a payment, but instead register them again in a future coinjoin round.
       Why change is an issue
      Change is not inherently bad, it's a fundamental part of how Bitcoin and the UTXO model works. However, when sending a coin that is change from an earlier transaction, then the receiver can easily deduce that the sender was also part of the previous transaction that generated the change.
      Whenever you are merging coins in one transaction, it becomes clear to any outside observer that these coins belong to the same entity, thus linking the previous transaction history. Thus identifying change based on some heuristics is a top goal of transaction surveillance.
      You want to avoid merging coins with different anonymity set values whenever possible, because this will link these coins and reduce their anonymity set to the lowest value.
       Your options to use change privately
       Avoid change in the first place
      Whenever possible, choose UTXO's for transactions where the destination addresses receive the entire value of your UTXO's, and you don't get any change back. This can easily be done by clicking the shield icon in the top right corner of the transaction preview screen, and adjusting the payment amount to be slightly higher or lower. This might not be possible in some cases where you have to pay a specific value of a payment request.
       Make it difficult to deduce the change
      There are common heuristics identifying change outputs, try to avoid these with every transaction. Don't reuse addresses, don't send precise amounts but randomize them, use replace by fee (RBF) only if necessary, and try to send to bech32 or bech32m addresses.
       Spend the change to the same entity as in the initial transaction
      If in the first transaction you have 0.10 bitcoin and send Alice 0.04 bitcoin, you get 0.06 bitcoin back as change in a new address, which Alice can see belongs to you. Now, in a second transaction where you want to send Alice 0.05 bitcoin, you can select that 0.06 bitcoin change coin without losing any privacy, because Alice already knows this is your coin.
      In this second transaction you will get back 0.01 bitcoin as change, which again, will still be known to Alice. If in a third transaction you want to send Alice 0.02 bitcoin, then you can consolidate the 0.01 bitcoin change with a new 0.10 bitcoin mixed coin, thus getting 0.09 bitcoin change.
      Now Alice will know that you owned the 0.10 bitcoin and that you currently own the 0.09 bitcoin change, but she cannot find out about your premix transaction history.
      Wasabi will automatically check if you have a coin with the same label for the current payment recipient, and will use those coins to be spent.
       Spend the change with another entity, where you don't mind if each of the two know that you transact with the other entity
      When you send a transaction to Alice, then she knows that the change output goes back to you. You can use this change to send bitcoin to Bob, and if he has bad privacy habits, Alice can find out you sent to him. But if you have a trusted relationship with the two, then this is alright, and not part of your threat model.
       Coinjoin more
      Since Wasabi 2.0 has a minimum amount for coinjoin of only 5000 sats, any change coin with an amount larger than that will be registered in a future coinjoin round. If you wait long enough, Wasabi will make sure that you don't have any anonscore 1 change coin in your wallet, but only private coins not linked to any previous payment.
      
-    
+    
   
 
diff --git a/using-wasabi/CoinJoin.html b/using-wasabi/CoinJoin.html
index a4d2c83cf7..5d1e930177 100644
--- a/using-wasabi/CoinJoin.html
+++ b/using-wasabi/CoinJoin.html
@@ -24,10 +24,10 @@
     
     Coinjoin | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Coinjoin
       Introduction
      A coinjoinopen in new window is a special Bitcoin transaction where several peers get together to literally join their coins in a single transaction. They collaboratively build a transaction where each of them provides some coins as inputs, and fresh addresses as outputs. The concept has been around since the early days of Bitcoin, and it was formalized by the great Greg Maxwell in this awesome introductory threadopen in new window.
      The goal is to gain privacy by breaking the link of which input "pays" which output so that none of the outputs can be attributed to the owner of the input. WabiSabi enables centrally coordinated coinjoins with variable amounts in a trustless (meaning nobody can steal) and private (meaning even the coordinator cannot spy) manner, as described in the WabiSabi paperopen in new window.
      WabiSabi Coinjoin Explained in 3 Minutesopen in new window
       Coinjoin step-by-step
      1. Launch Wasabi and open your wallet.
      2. Wait. Wasabi coinjoins automatically in the background.
      3. You're done! You can make private payments now.
       Music box
      After opening a hot wallet, it will automatically start a countdown to start coinjoining (±10 minutes). This and other coinjoin related information is shown in the music box.
      Music Box Countdown
      After the Waiting to auto-start coinjoin countdown is finished the wallet should start participating in the coinjoin process.
      A blue aura will show up at the the bottom of the wallet, which indicates that the wallet is coinjoining, and the music box message will change.
      Music Box Awaiting Other Participants
      After some time the blue aura will change to an orange one, this indicates that the coinjoin process is now in a critical phase. Wasabi will prevent you from shutting down the app during the orange aura to not disrupt the coinjoin round.
      Music Box Coinjoin In Progress
      If this is succesfull, the coinjoin is completed and the coinjoin will show up in the history list.
      Music Box Success
      Notice that the wallet might have to repeat the coinjoin steps multiple times before a successful coinjoin is created. So it is possible that the aura colors will change without a successful coinjoin. Please leave Wasabi Wallet running, and eventually there will be a successful coinjoin.
       More Details
      By default, Wasabi starts automatically coinjoining your funds when the total value of the non-private coins is equal to or above the Auto-start coinjoin threshold (0.01 BTC by default). Automatically start coinjoin can be disabled from the coinjoin settings. In case you want to start the process manually, then click the play button; if you want to stop coinjoin, then click the pause button.
      Once a coin achieves enough privacy (reaches the Anonymity score target), then the corresponding amount will show up in the wallet's main view as "PRIVATE".
      Notice that it is not yet possible to coinjoin from a hardware wallet, the keys must be "hot" on your computer.
       Fees
      A 0.3% coordination fee will be taken from fresh coins bigger than 0.01 BTC. Coins less than or equal to 0.01 BTC don't pay coordination fees at all, according to the PlebsDontPay threshold.
      Remixing is free, as well as coinjoining coins 1 hop from a coinjoin, although, Bitcoin mining fees still do apply, as shown in this table. So if you send a coinjoined coin and receive a change output, you will not be charged the coordination fee for this change output. The recipient of the payment will not have to pay the coordination fee, as long as he is making coinjoins with the same coordinator.
       WabiSabi protocol step-by-step
      WabiSabi protocol requires 5 steps to successfully create and broadcast a coinjoin transaction to the bitcoin network.
      The round starts either as soon as the number of registered inputs reaches the maximum, or after the input registration time is reached and as long as the minimum number of inputs is satisfied.
       Input registration
      During the input registration, the client selects how many and which coins will be registered for coinjoin. These coins need to be confirmed on the Bitcoin blockchain. In the background Wasabi generates input proofs, which are signatures over challenge messages, made with the private keys that lock up the coins. With this, the coordinator can verify that you actually own these coins.
      Wasabi wallet generates a new Tor identityopen in new window called Alice for each input. She is a separate entity, and for every round you use a new Alice who is not linked to any other input or previous connection. With Alice, you send the input ownership proof to the coordinator.
      The Wasabi coordinator now verifies that:
      • There is still room for more inputs on this coinjoin.
      • The input has not already been registered, is not banned, is unspent, and that the input proof is valid.
      • The input has at least 5000 sats value.
      Only when all these checks are passed, does the coordinator allow this input to be registered. The coordinator creates and sends a credential back to Alice, which has the same amount as the input minus fees.
      The input registration phase ends when either: the number of registered inputs reaches the maximum, or when the time elapsed and the minimum number of inputs is satisfied.
       Connection confirmation
      There are many users registering their inputs (with different Alice for each input) in the first phase, and this takes a while. The connection confirmation phase makes sure that all of them are still online and ready to continue. The coordinator verifies the unique ID from each Alice, and if everyone is still communicating. The coordinator sends a zero value credential to each Alice for each successful connection confirmation.
      The round is abandoned and re-started if too many Alices have dropped, for example when their Wasabi is shut down, or when their Tor connection is temporarily broken. The connection confirmation phase ends when all Alices have provided their unique IDs, or after a timeout and the number of online Alices is still larger than the minimum number of inputs.
       Output registration
      Now that all peers are online, we are ready to proceed with the output registration phase of the round.
      First, every client needs to change the value of their credentials to the desired output values. For this, the client presents to the coordinator two old credentials, and two newly created ones. The coordinator does not know the amount value of any of those credentials, but it can verify, that the two pairs sum up to exactly the same value. For example, a user can present one 5 btc and one 0 btc credential, and redeem one 2 btc and one 3 btc credential. Or a user can present one 4 btc and one 1 btc credential, and redeem one 5 btc and one 0 btc credential. After potentially many rounds of reissuance, each client has exactly the amount credential it desires. Each of these reissuance is perfectly private, so the coordinator cannot link any of them to the same user.
      Next, your Wasabi client generates multiple new Tor identities called Bob, which are in no way tied to any Alice. Bob sends to the Wasabi coordinator:
      • An unblinded credential signed by the coordinator
      • A new (unused) bitcoin address
      Because the coordinator can verify its own credential, it knows that this credential came into existence after an input of at least this much value was registered. However, it cannot know which input exactly.
      It is very important that the coordinator cannot link Alice to Bob. Because Alice has sent the cleartext input, and Bob sends the cleartext output. So, if the two were to be linked, then the coordinator can specifically link the input to the output, meaning that the anonymity set is 1. Because Alice received a credential from the coordinator, and because Bob is a new Tor identity not linked to Alice, the coordinator can verify that nobody is cheating, but it cannot deanonymize the peers.
      The output registration phase ends when the value of cleartext outputs is equal to the value of inputs, meaning that all Bobs have registered. If after a timeout not all outputs are registered, then this round is abandoned, the missing inputs are temporarily banned, and a new round is started.
      Possibility of Taproot outputs from coinjoin
      Since Wasabi version 2.0.3open in new window coinjoin outputs can be SegWit v0 and SegWit v1 (Taproot). If running this version or higher, the client registers the output type in a semi-random way (~50% chance of receiving Taproot output).
       Signing
      Now that all inputs and outputs are registered, the coordinator can start the signing phase, by building the coinjoin transaction with all the registered inputs and outputs. It sends this transaction to all the Alices of the round.
      Each Alice does the following:
      • Verifies that her input and output are included.
      • Signs the transaction with the private key of her input.
      • Sends the signature to the coordinator, who verifies this information.
      The signing phase ends when the coordinator has received all the valid signatures for all the registered inputs.
       Blame round
      When the signing phase fails due to some Alices disrupting the round (failing to sign or send the signature to the coordinator), then the successful Alices will continue into a blame round. The blame round will redo the coinjoin phases in order to create a successful coinjoin.
      This mecanism also prevents coinjoins from being DDoS-ed because bad actors that are willingly disturbing rounds won't be able to join the blame round. The client will keep going to the blame round until there are not enough Alices left to meet the minimum input count of 150.
      The blame round is not a mandatory phase of the coinjoin process. It was introduced in order to have a higher coinjoin success rate.
       Broadcasting
      The coinjoin transaction has been successfully built and signed, and it is now ready to be broadcast to the peers of the Bitcoin network. The coordinator sends this transaction over the Tor network to random Bitcoin P2P nodes, and from there it is gossiped to other nodes and miners. To save on mining fees, the target confirmation time is roughly 24 hours.
       Coinjoin Settings
      Wasabi Wallet has automatic coinjoin. It is done by the built-in automatic coinjoin "robot". The robot contains instructions/settings, like how often and when to coinjoin. The user is able to specify these settings in the Coinjoin Settings dialog, according to his own preferences. The wallet ships with default settings, which are good enough for most users.
      Wasabi Wallet Coinjoin Settings
      Coinjoin settings are wallet specific
      As the coinjoin settings apply per individual wallet, it is possible to have multiple wallets with different coinjoin settings.
       Automatically start coinjoin
      This setting is enabled by default.
      When this is enabled, the wallet will automatically start coinjoining soon after the wallet is loaded. The wallet will coinjoin until the privacy progress is 100%.
      When this is not enabled, the user will have to manually press the Play button in order to start coinjoining.
      Coinjoin Settings Automatically Start Coinjoin
       Auto-start coinjoin threshold
      The default Auto-start coinjoin threshold is 0.01 BTC.
      The wallet will not automatically start coinjoining if the non-private balance is below the Auto-start coinjoin threshold, even if the Automatically start coinjoin is enabled. In this case the user has to manually press Play to start coinjoining. This setting can be used to prevent paying (relatively) high fees for smaller bitcoin amounts.
      For example, if the non-private balance is 0.005 BTC and the Auto-start coinjoin threshold is 0.01 BTC, the user will have to manually press Play to start coinjoining.
      Auto-start Coinjoin Threshold
      It is OK to set the Auto-start coinjoin threshold to 0
      If you have some small non-private left overs: you can coinjoin these by pressing Play, or wait until you receive more funds. If you want to always automatically coinjoin ALL your coins, this can be set to 0 BTC. Note that you might pay relatively more fees for coinjoining smaller amounts.
       Coinjoin Strategy
      Wasabi ships with 3 coinjoin strategies: Minimize Costs, Maximize Speed, and Maximize Privacy. Each of these contain different configurations, as shown in this table. They determine the Anonymity score target, Coinjoin time preference, and if Red coin isolation is enabled or not.
      Coinjoin Strategy Settings
      The default strategy is Maximize Speed.
      It is possible to make your own custom strategy by using the customize button.
      Coinjoin Strategy
       Wasabi Coinjoin examples
      Here's a list of Wasabi coinjoin examples and how they appear on a block explorer:
      
-    
+    
   
 
diff --git a/using-wasabi/ColdWasabi.html b/using-wasabi/ColdWasabi.html
index 626f4e4fb8..b309024b5c 100644
--- a/using-wasabi/ColdWasabi.html
+++ b/using-wasabi/ColdWasabi.html
@@ -24,10 +24,10 @@
     
     Hardware Wallet | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Cold-Wasabi Hardware Wallet Mode
       Using hardware wallet step-by-step
      1. Start your Wasabi Wallet and go to Add Wallet.
      2. Click on Connect to hardware wallet and then connect the hardware wallet via cable. Alternatively, you can import a Coldcard skeleton file via SD card by using Import Wallet at the Add Wallet dialog.
      3. Confirm that the detected hardware wallet is correct.
      4. Click Open, and wait for the wallet to load.
      5. Now you can receive bitcoin to addresses controlled by the hardware wallet.
      6. You can spend these coins in the Send dialog, though the hardware wallet must be connected via USB to sign the transaction. Alternatively, you can build a PSBT, export this via SD card to your Coldcard wallet for signing, then import the final transaction to Wasabi for broadcasting.
      No coinjoin
      Unfortunately, as of now, you cannot coinjoin with just the private keys on your hardware wallet. The keys need to be on the internet-connected computer to be able to coinjoin.
       What is Cold Storage
      Cold storage refers to generating and storing private keys completely offline. This is an often-used security precaution, especially dealing with large amounts of bitcoin. Because the private keys are not on a computer that is connected to the internet, many remote attack vectors are nullified.
      Methods of cold storage include keeping private keys on a:
      • USB drive or other data storage medium
      • Paper wallet
      • Bearer item such as a physical bitcoin
      • Hardware wallet
      Use a hardware wallet for cold storage
      There are multiple ways to exercise cold storage, however it is highly reccommended to use a hardware wallet. This is by far the best and most secure way of using bitcoin for almost all users.
       Hardware Wallet with Wasabi
      You can use Wasabi Wallet with almost any hardware wallet out there because Wasabi utilizes Bitcoin Core Hardware Wallet Interface [HWI]open in new window. The setup is thoroughly tested for Trezor model Topen in new window, Ledger Nano S, Nano S Plus and Nano Xopen in new window, and Coldcardopen in new window.
       Connecting via USB
       Import the wallet
      1. Go to Add wallet.
      2. Click on Connect to hardware wallet.
      3. Give the wallet a name.
      4. Connect the hardware wallet to the PC and enter the pin on the hardware wallet to unlock it.
      5. Confirm that the correct hardware wallet is detected.
      6. Open the wallet.
      This wallet can be used as a watch-only wallet when the hardware wallet device is not connected.
      Wasabi remembers the wallet's information like xpub, wallet fingerprint and addresses etc. But it never knows the private keys, which are on the hardware wallet. So, you can see the balance and all it's transactions in Wasabi and you can generate addresses, but you cannot send without the hardware wallet being connected. Because you need to sign (confirm) the outgoing transactions on the hardware wallet.
       Receiving bitcoin
      After the first time you loaded a new device, the public keys will be stored locally on the computer, and you can use Wasabi to receive bitcoin to the hardware wallet without having it connected.
      Verify the receive address on the hardware wallet for extra security
      It's always a good practice to verify that the receive address on Wasabi corresponds to the one on the hardware wallet, before receiving (large amounts of) bitcoin. This could prevent malicious firmware which replaces a receive address with a fake one. You can do this by clicking on Show on the hardware wallet at a receive address. The address will now be displayed on the hardware wallet, check that the addresses correspond and then confirm this on the hardware wallet.
       Sending bitcoin
      Only when you want to send bitcoin you need to connect the device over USB again.
      1. Click the Send button.
      2. Enter the amount and destination address.
      3. Enter the label of whom you are sending to.
      4. At the Preview Transaction screen, check that everything is correct.
      5. Click Send Now.
      6. Connect the hardware wallet & unlock it.
      7. Check on the hardware wallet that everything is correct.
      8. Confirm on the hardware wallet.
      9. The transaction is sent!
      The private keys are not on the computer, thus the transaction is signed on the hardware wallet after you confirm with a physical button click. The final transaction is automatically broadcast over Tor with Wasabi Wallet.
       Connecting Coldcard via SD card
      You can use Wasabi Wallet together with Coldcard without ever connecting it via USB, thus further reducing possible attack vectors. For more details see the Coldcard documentationopen in new window.
       Import the skeleton wallet
      Power your Coldcard on a power bank or electricity socket, then unlock it with your pin. Put in a MicroSD card and go to Advanced > MicroSD Card > Export Wallet > Wasabi Wallet. This will write the public keys, wallet fingerprint, derivation path and other metadata to a skeleton file new-wallet.json.
      Protect your public keys!
      This file does not include your private keys, so an attacker cannot use it to spend your bitcoin. However, he can use it to derive a full transaction history, thus it is a potential privacy leak.
      Now insert the SD card to your computer, and open Wasabi Wallet. Go to the Add Wallet dialog, and click Import a wallet, browse to the SD card and select the new-wallet.json file. Wasabi will automatically import and modify this skeleton file and store it in your Wallets and WalletBackups folders.
       Receiving bitcoin
      After the skeleton wallet is imported, you can open the wallet from the wallet list at the NavBar, without having to power on the Coldcard. Generate a receive address as usual. The private key corresponding to this address is on the hardware wallet.
       Sending bitcoin
      Sending bitcoin airgapped works as follows:
      1. Enable PSBT workflow in the Wallet Settings
      2. Click the Send button.
      3. Enter the amount and destination address.
      4. Enter the label of whom you are sending to.
      5. At the Preview Transaction screen, check that everything is correct.
      6. Click Save PSBT file, and save the file on the MicroSD card.
      7. Remove the MicroSD card from the computer and put it into your Coldcard.
      8. On the Coldcard, click Ready to Sign.
      9. Verify the transaction details shown on the Coldcard, and approve to sign the transaction.
      10. Remove the MicroSD card from Coldcard and insert it into the computer.
      11. In Wasabi, click on Broadcaster (in the search bar).
      12. Select Import Transaction.
      13. Select the final signed transaction, which looks like this xxx-final.txn.
      14. Broadcast the transaction.
      Enable PSBT workflow in the settings
      You need to have PSBT workflow enabled in the wallet settings in order to have Save PSBT file show up at the Preview Transaction screen. After it is enabled, a Broadcast button will appear next to the Send button for an easier workflow.
       Cold-Wasabi protocol
      This is how you can safely eat cold Wasabi, or store your coins on a hardware wallet after coinjoining with Wasabi Wallet. Because you cannot do coinjoin with the private keys on the hardware wallet, you will need to generate and load two different wallets in Wasabi. A 'hot' (coinjoin) and a 'cold' (storage) wallet will both be running in parallel, label them accordingly so you don't mix them up.
       GUI tutorial
       Coinjoin on the hot Wasabi
      First
      You should make your existing coins private. It is useful to generate a complete new hot wallet for this, so as to keep the coinjoin transaction history separate from other wallets.
      1. Generate a new hot-Wasabi Wallet.
      2. Open the Receive dialog to get a new address.
      3. Send bitcoin into this Hot-Wasabi Wallet.
      4. Start the automatic coinjoin process and wait for the coinjoin to be done (i.e. privacy progress 100%).
       Set up your cold-Wasabi
      Second
      In order to separate these new private coins, you should generate a fresh wallet on your hardware device.
      1. Generate a new set of keys on your hardware wallet and make a backup.
      2. Load your hardware wallet device to Wasabi, either via USB or SD card.
      3. Label and generate a receive address for the hardware wallet. For the first setup, you need to connect the hardware wallet to the computer that runs Wasabi, afterwards, you can generate receive addresses without the device being connected.
      4. Copy the receiving address from the cold-Wasabi.
       Send bitcoins from hot to cold Wasabi
      Third
      When your coins are private, it is a good practice to send them out in multiple batches in order to not consolidate all your coins. Wait some time in-between sending them, so that timing analysis becomes more difficult.
      1. Go to the hot-Wasabi Send dialog and enter the amount.
      2. Paste the cold-Wasabi address.
       Send bitcoins from cold Wasabi
      Finally
      You can at any time spend the bitcoin from the cold-Wasabi.
      1. Connect your hardware wallet to the computer.
      2. Load the cold Wasabi wallet.
      3. Go to the Send dialog, enter the amount and the destination address, then sign the transaction with the hardware wallet.
      Success!
      おめでとうございます!
      You are now eating Cold Wasabi!
      WARNING
      The anonymity score is tied to the wallet that you used to coinjoin, if you send a mixed coin to another Wasabi Wallet (in this case your hardware wallet), it will have an anonymity score of 1 (and will be marked as non-private) because this wallet doesn't know that the coin was coinjoined.
      You should use a meaningful label when you generate a receive address in your hardware wallet, e.g. "Myself coinjoin private" (something that reminds you that you got this utxo from your Wasabi Wallet and it was coinjoined).
      
-    
+    
   
 
diff --git a/using-wasabi/Daemon.html b/using-wasabi/Daemon.html
index ad366d3124..f00c9d67d1 100644
--- a/using-wasabi/Daemon.html
+++ b/using-wasabi/Daemon.html
@@ -24,7 +24,7 @@
     
     Headless Wasabi Daemon | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Headless Wasabi Daemon
       Introduction
      The default of how to interact with your Wasabi wallet is the graphical user interface (GUI). There is also a headless daemon where you do not run a resource-intensive GUI, but only the command line interface. Running the daemon minimizes the usage of resources (CPU, GPU, Memory, Bandwidth) with the goal of making it more suitable for running all the time in the background. The RPC interface can be used to interact with the Daemon.
      The daemon is included in the package starting from Wasabi version 2.0.4open in new window and can be launched using the command line.
      The desktop app (GUI) is built on top of the daemon. Meaning that command line arguments/variables can also be used to configure the desktop app.
       Available commands
      When entering the commands on the command line, they are capital letter insensitive.
       Config file configurations
      All configuration options available via the Config.json file are also available as command line arguments:
      Config FileCommand LineEnvironment variable
      ""Network": "TestNet"--network=testnetWASABI-NETWORK=testnet
      "MainNetBackendUri": "https://api.wasabiwallet.io/"--mainnetbackenduri="https://api.wasabiwallet.io/"WASABI-MAINNETBACKENDURI="https://api.wasabiwallet.io/"
      "TestNetClearnetBackendUri": "https://api.wasabiwallet.co/"--testnetbackenduri="https://api.wasabiwallet.co/"WASABI-TESTNETBACKENDURI="https://api.wasabiwallet.co/"
      "RegTestBackendUri": "http://localhost:37127/"--regtestbackenduri="http://localhost:37127/"WASABI-REGTESTBACKENDURI="http://localhost:37127/"
      ""UseTor": ""true"--usetor=trueWASABI-USETOR=true
      "TerminateTorOnExit": ""false"--terminatetoronexit=falseWASABI-TERMINATETORONEXIT=false
      "DownloadNewVersion": true--downloadnewversion=trueWASABI-DOWNLOADNEWVERSION=true
      "StartLocalBitcoinCoreOnStartup": false--startlocalbitcoincoreonstartup=falseWASABI-STARTLOCALBITCOINCOREONSTARTUP=false
      "StopLocalBitcoinCoreOnShutdown": true--stoplocalbitcoincoreonshutdown=trueWASABI-STOPLOCALBITCOINCOREONSHUTDOWN=true
      "LocalBitcoinCoreDataDir": "/home/UserName/.bitcoin"--localbitcoincoredatadir="/home/UserName/.bitcoin"WASABI-LOCALBITCOINCOREDATADIR="/home/UserName/.bitcoin"
      "MainNetBitcoinP2pEndPoint": "127.0.0.1:8333"--mainnetbitcoinp2pendpoint="127.0.0.1:8333"WASABI-MAINNETBITCOINP2PENDPOINT="127.0.0.1:8333"
      "TestNetBitcoinP2pEndPoint": "127.0.0.1:18333"--testnetbitcoinp2pendpoint="127.0.0.1:18333"WASABI-TESTNETBITCOINP2PENDPOINT="127.0.0.1:18333"
      "RegTestBitcoinP2pEndPoint": "127.0.0.1:18444"--regtestbitcoinp2pendpoint="127.0.0.1:18444"WASABI-REGTESTBITCOINP2PENDPOINT="127.0.0.1:18444"
      "JsonRpcServerEnabled": "true"--jsonrpcserverenabled=trueWASABI-JSONRPCSERVERENABLED=true
      "JsonRpcUser": ""--jsonrpcuser=""WASABI-JSONRPCUSER=""
      "JsonRpcPassword": ""--jsonrpcpassword=""WASABI-JSONRPCPASSWORD=""
      "JsonRpcServerPrefixes":["http://127.0.0.1:37128/", "http://localhost:37128/"]--jsonrpcserverprefixes=["http://127.0.0.1:37128/", "http://localhost:37128/"]WASABI-JSONRPCSERVERPREFIXES=["http://127.0.0.1:37128/", "http://localhost:37128/"]
      "DustThreshold": "0.00005"--dustthreshold=0.00005WASABI-DUSTTHRESHOLD=0.00005
      "EnableGpu": true--enablegpu=trueWASABI-ENABLEGPU=true
      "CoordinatorIdentifier": "CoinJoinCoordinatorIdentifier"--coordinatoridentifier="coinjoincoordinatoridentifier"WASABI-COORDINATORIDENTIFIER="coinjoincoordinatoridentifier"
       Non-Config file configurations
      There are a few special switches that are not present in the Config.json file and are only available using the command line:
      SwitchCommand LineEnvironment variable
      Ignore P2P transactions--blockonly=trueWASABI-BLOCKONLY=true
      The level of detail used during logging--loglevel=traceWASABI-LOGLEVEL=trace
      The path to the directory used during runtime--datadir="$HOME/temp/wasabi-1"WASABI-DATADIR="$HOME/temp/wasabi-1"
      Open wallet "WalletName"--wallet=WalletNameWASABI--WALLET=WalletName
       How to run
       If the package is installed
      Depending on your operating system, open the command line and execute:
       Linux
      wassabeed --wallet=WalletName --jsonrpcserverenabled=true
@@ -39,6 +39,6 @@
 
      Check the Wasabi Daemon version
      $ wassabeed --version
 Wasabi Daemon 2.0.5
 
      
-    
+    
   
 
diff --git a/using-wasabi/DeterministicBuild.html b/using-wasabi/DeterministicBuild.html
index 6173c3e888..fbc701dcfe 100644
--- a/using-wasabi/DeterministicBuild.html
+++ b/using-wasabi/DeterministicBuild.html
@@ -24,10 +24,10 @@
     
     Deterministic Build | Wasabi Docs
     
-    
+    
   
   
     
-    
+    
   
 
diff --git a/using-wasabi/DiscreetMode.html b/using-wasabi/DiscreetMode.html
index 65c2e77ae0..ddaaed2008 100644
--- a/using-wasabi/DiscreetMode.html
+++ b/using-wasabi/DiscreetMode.html
@@ -24,10 +24,10 @@
     
     Discreet Mode | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Discreet Mode
      Discreet Mode is a Wasabi Wallet feature that hides sensitive and critical information from physical observers and allows you to post screenshots without worrying about your privacy.
      Wasabi Wallet Discreet Mode
       How to activate/deactivate Discreet Mode
      You can activate or deactivate by clicking the Discreet Mode icon in the bottom left corner of the main view.
      Enable Discreet Mode in Wasabi Wallet
      Disable Discreet Mode in Wasabi Wallet
       More information on Discreet Mode
      • In Discreet Mode the wallet is still usable, meaning that you can send and receive payments, as well as coinjoin.
      • Discreet Mode only masks the surface. This means that when you click to see more Details, some information (which wasn't visible at first) will be shown.
      • When hovering over the ### chars with the cursor, the content will be visible for a short amount of time.
      • Some justification of design decisions can be seen hereopen in new window.
      
-    
+    
   
 
diff --git a/using-wasabi/ELI5.html b/using-wasabi/ELI5.html
index 8dccd80830..dc021cb274 100644
--- a/using-wasabi/ELI5.html
+++ b/using-wasabi/ELI5.html
@@ -24,10 +24,10 @@
     
     Explain Wasabi like I'm 5 | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Explain Wasabi like I'm 5
       Introduction
      Wasabi Wallet is an open-source, non-custodial, privacy-focused Bitcoin wallet with built-in coinjoins. It is a piece of software that runs on your computer and helps you to manage your bitcoins. Although Wasabi has some very advanced magic under the hood, it is rather easy to use. You can generate a new set of seed words, or import already existing ones. With Wasabi you can receive bitcoins into your full control, and you can send them to someone else without needing permission from any other person or entity. There is also a powerful auto-coinjoin feature to help obfuscate your transaction history. You can use Wasabi to manage your hardware wallet, and it even connects to your own full node. Of course, Wasabi is libre and open-source, which means you have full control over the software you manage your money with.
       Installing Wasabi
      Installing Wasabi is super-easy. Go to the official website wasabiwallet.ioopen in new window and download the version for your operating system. You can then install Wasabi as you would do any other software on your computer.
      See this chapter for a detailed step-by-step tutorial for all operating systems, and also how to verify the PGP signature.
       Generating a Wallet
      When you start Wasabi for the first time, the dialog to generate a new wallet will be open. You can set a unique name for the wallet so that you remember what it is for. In the next step, Wasabi will show your 12 recovery words. These must be carefully backed up, in the correct order, as they are needed to recover your wallet (together with the password) on another computer or in another wallet software. Next, choose a very secure password, as this encrypts the secrets, and should not be guessed by others. You will always need this password in order to spend your bitcoins, so take great care to back it up properly. Make sure you store the backup of your recovery words in a different location than the backup of your password.
      Backup both!
      If you ever need to restore your wallet in Wasabi, or any other wallet, you will need both: your password AND your 12 recovery words.
      See this chapter for more information on how to securely generate your wallet.
       Receiving bitcoin
      In order to receive bitcoin, you need to generate an address in the Receive dialog. But first, you must label it with the names of any observers who know that this address is yours. For example, if Alice pays you back for last nights pizza, then the label is Alice. This is an important feature for you and the wallet to know which coin is from whom, and it will help with your privacy in the future. Once this newly generated address receives some coins, Wasabi Wallet will automatically hide this used address, so you don't reuse it by accident.
      See this chapter for a tutorial on how to properly label your addresses and receive bitcoin.
       Sending bitcoin
      Sending process is different depending on the privacy of coins you have. Assuming you have enough private coins the sending process is the following:
      1. Click the Send button (top right corner) at the main view.
      2. Insert the address of the receiver and type in the amount the receiver should get, then click Continue.
      3. Enter the name of the person or company receiving the payment and click Continue.
      4. Make sure everything is filled in correctly in Preview Transaction window and click Confirm.
      5. Type in your password and click Continue.
      You will now see a pop-up window telling you that the transaction is broadcasted to the Bitcoin network.
      See this chapter for more details about sending bitcoin and the privacy nuances of it.
       Coinjoin with Wasabi
      If you don't like that your employer knows where you spend your money, or that a merchant can find out how much money you have, then you should coinjoin your bitcoin, as this breaks link to its transaction history. Although the coinjoin protocol is a bit complex, it is very easy to use in Wasabi. The wallet automatically coinjoins all your funds, so that your money becomes private. This process might take some time (hours/days). You can still use your wallet in the mean time, however it is a best practice to only use private funds, which the wallet does automatically when possible. At the wallet's homescreen the percentage indicates the progress to making your wallet fully private. The exact available private amount of bitcoin is listed as PRIVATE.
      See this chapter for a thorough analysis of coinjoin, details on the Wasabi implementation and best practices on how to use it properly.
      
-    
+    
   
 
diff --git a/using-wasabi/InstallPackage.html b/using-wasabi/InstallPackage.html
index 5ea8f96170..eb185ec6e7 100644
--- a/using-wasabi/InstallPackage.html
+++ b/using-wasabi/InstallPackage.html
@@ -24,10 +24,10 @@
     
     Install-package | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Install package
       Introduction
      The easiest way to start with Wasabi is to download, verify and install the released package. This is a version of the software that is thoroughly reviewed by the contributors. The package has the binary code that is needed to run the Wasabi Wallet client including the graphical user interface. For compiling the open-source code with cutting edge development features, also including the backend server, see this tutorial here.
      Download the packages either from the official WasabiWallet.ioopen in new window clearnet website or for your privacy's sake, from the official Tor onion service http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onionopen in new window.
      Operating systems supported by Wasabi Wallet
      Although there is automatic signature verification on Windows and macOS, it is still recommended to manually VERIFY PGP SIGNATURES of the downloaded package with zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window before installing Wasabi. This protects you against malicious phishing sites giving you back-doored wallet software. If you have personally verified zkSNACKs' PGP public key 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861Eopen in new window and you are familiar with the Web Of Trustopen in new window, please consider also signing itopen in new window.
      Always
      Don't trust - Verify!
       Install Wasabi step-by-step
      1. Download the Wasabi package relevant to your operating system from wasabiwallet.ioopen in new window.
      2. Verify the PGP signatures of the download.
      3. Install Wasabi package as you would do any other software on your operating system.
       Windows
      1. Downloadopen in new window the .msi installer of the latest Wasabi release.
      Download Wasabi Wallet for Windows
      1. Install Wasabi by double-clicking the .msi and following the GUI instructions.
      2. Make sure that you see this window that verifies the installer was signed by zkSNACKs Limited. Manual PGP verification is optional, as the package is signed and verified automatically on Windows.
      Wasabi Wallet Windows signature verification
      Wasabi will be installed to your C:\Program Files\WasabiWallet\ folder. You will also have an icon in your Start Menu and on your Desktop. After the first run, a data folder will be created. Among others, here is where your wallet files and your logs reside.
       Debian and Ubuntu
      If you have already imported zkSNACKs' PGP public key, then jump to step 2.
      1. Download zkSNACKs' PGP public key hereopen in new window, and then import it with gpg --import PGP.txt.
        Verify that the fingerprint is 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E by running this command gpg --list-keys zkSNACKs.
      2. Downloadopen in new window the latest Wasabi release, both the .deb package and the corresponding .asc signature file.
      Download Wasabi Wallet for Debian
      1. Verify the signature in the Download repository with gpg --verify Wasabi-2.0.5.deb.asc Wasabi-2.0.5.deb. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
        TIP
        The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
      2. [GUI] Install by double-clicking and follow the GUI Instruction. 
         [CLI] In the Download repository, execute the command sudo apt install ./Wasabi-2.0.5.deb to install Wasabi and after that run Wasabi by executing wassabee.
      After the first run, a data folder will be created. Among others, here is where your wallet files and your logs reside.
       Other Linux
      If you have already imported zkSNACKs' PGP public key, then jump to step 2.
      1. Download zkSNACKs' PGP public key hereopen in new window, and then import it with gpg --import PGP.txt.
        Verify that the fingerprint is 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E by running this command gpg --list-keys zkSNACKs.
      2. Downloadopen in new window the latest Wasabi release, both the .tar.gz archive and the corresponding .asc signature file.
      Download Wasabi Wallet for Linux
      1. In the Download folder, run gpg --verify Wasabi-2.0.5.tar.gz.asc Wasabi-2.0.5.tar.gz.
        If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
        TIP
        The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
      2. Extract the archive while keeping the file permissions: tar -pxzf Wasabi-2.0.5.tar.gz.
      3. Run Wasabi by executing ./wassabee.
      After the first run, a data folder will be created. Among others, here is where your wallet files and your logs reside.
       macOS
      1. Downloadopen in new window the .dmg package of Wasabi 2.0.5 for your machine's processor. There are two types of packages for macOS, one for Intel and one for the Apple Silicon chip. If you're not sure what processor your device has, you can check itopen in new window.
      Download Wasabi Wallet for macOS
      1. Double-click .dmg to open it.
      2. Install Wasabi by dragging it into your Applications folder.
      3. At first startup, there will be a pop-up that Wasabi was downloaded from the internet. Click on Open and restart Wasabi.
      After the first run, a data folder will be created. Among others, here is where your wallet files and your logs reside.
       Optional PGP Verification
      If you have already imported zkSNACKs' PGP public key, then jump to step 4.
      1. Get GnuPGopen in new window.
      2. Copy zkSNACKs' PGP public keyopen in new window into a new TextEdit document and saving it as zkSNACKsPubKey.txt. Before saving, you need to go to Format / Make Plain Text (otherwise TextEdit will not be able to save it as a .txt file).
      3. Open Terminal and go to the folder in which you saved the zkSNACKsPubKey.txt file and import the PGP public key with sudo gpg --import zkSNACKsPubKey.txt. This should return the output: key 856348328949861E: public key "zkSNACKs <zksnacks@gmail.com>" imported.
      4. Downloadopen in new window the latest Wasabi release, both the .dmg package and the corresponding .asc signature file.
      5. In the Download folder, run sudo gpg --verify Wasabi-2.0.5.dmg.asc Wasabi-2.0.5.dmg. If the message returned says Good signature from zkSNACKs and that it was signed with Primary key fingerprint: 6FB3 872B 5D42 292F 5992 0797 8563 4832 8949 861E, then the software was not tampered with since the developer signed it.
        TIP
        The output from the verify command may contain WARNING: This key is not certified with a trusted signature!. You can ignore this, but if you want to fully verify your download, you need to ask people you trust to confirm that the key fingerprint belongs to zkSNACKs.
      Watch the videoopen in new window
      Watch the videoopen in new window
      
-    
+    
   
 
diff --git a/using-wasabi/PasswordBestPractices.html b/using-wasabi/PasswordBestPractices.html
index 495f058304..f682d599a8 100644
--- a/using-wasabi/PasswordBestPractices.html
+++ b/using-wasabi/PasswordBestPractices.html
@@ -24,12 +24,12 @@
     
     Password Best Practices | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Password best practices
       Introduction
      You shouldn't try to re-invent the wheel for something as complicated and nuanced as cryptography, and especially in regards to entropy.
      These are some of the industry best practices:
      TIP
      Don't "roll your own" crypto.
       Password basics
      1. Randomness is the single-most important requirement for a strong password, because randomness means that the password has no predictable pattern to it. This makes it impossible to crack without doing an exhaustive, "brute-force" attack.
      2. Assuming a password is constructed randomly, its length has the most impact on its strength. However, a password that is very long, but not randomly constructed, such as: thequickbrownfoxjumpedoverthelazydogsback, or a passage from literature, is certain to be on every serious hacker's guess list.
      3. "Entropy" is a term commonly used to define the strength of a random password. There is a tutorial about how to calculate and evaluate entropy in your password here.
       What not to do
      Here are a few examples that do it completely wrong. You should not generate your password like this:
      1. Do not use publicly known information like your grandma's maiden name and the birthday of your dog. Emma1992 is a really, really, really bad password, because it can easily be guessed and it is very short. Here is a list of the worst and most commonly used passwordsopen in new window in recent years. Password hackers start with lists like this.
      2. Do not use the same password that you have used in other places. Because if one password is leaked, then other ones are compromised.
      3. Do try to use a mix of uppercase and lowercase letters, numbers, and special characters (&$%@ etc.) in your password.
      4. Do not take a famous quote, or well-known passage from literature and use it for a password. It will not fool any serious hacker, even if you throw in substitutions such as: "@" instead of "a", or "$" instead of "s".
        Make a secure password!!
        It is of utmost importance to generate a secure password following best practices.
       Use Diceware
      Rolling dice is an easy and effective way to get high entropy and randomness in a password that can even be memorized.
      The Diceware method is a great strategy for your most precious passwords (e.g. the password to your computer, your backups, or your encryption key). You can even use Diceware to create secure wallets.
      To generate a password using Diceware, you just need a high-quality die, a pen, and some paper. You can find EFF's Diceware list at the Electronic Frontier Foundation websiteopen in new window. Make sure you are alone and there are no cameras nearby. For maximum protection, disconnect your computer from the internet (after you save the Diceware list) and cover your webcam.
      To start, roll the die five times. Record the number from each roll using the pen and paper. You will end up with a five-digit number. We got 52611. Now search on the Diceware list for the five digit number you just created. Write down the word the number corresponds to, in our case it is salvo. This word by itself is not a good password, it would only take about a thousandth of a second to crack. Repeat the dice rolling process at least five more times.
      After six sets of five rolls, we ended up with 52611 51631 63432 43123 21641 and 14146. This corresponds to the password salvo rhoda walton mudd croft bride.
      This six-word passphrase, even though easy to remember, is just one of 2.21 x 10^23, or 221 sextillion possible six-word combinations taken from the list of 7776 words. A computer capable of 1 trillion guesses/second would take, on average, over 3500 years to correctly guess this or any six-word combination of words from the list, if they are chosen randomly.
      A 6-word passphrase derived as just discussed has 77 bits of entropy. Best practices for being secure against any adversary currently recommendopen in new window a minimum of near 80 bits of entropy, so this example phrase barely qualifies.
       Use a dictionary
      All of the major languages have at least 100,000 words in their dictionaries. Most have over 300,000 words. You can take a dictionary in any language that you are comfortable with and create a very strong password by randomly selecting as few as 5 words from it.
      The quick, but not technically random way would be to flip open your chosen dictionary to any seemingly random page, close your eyes, and put your fingertip down on the page. Choose the word nearest your fingertip that has at least 4 letters. Repeat this process at least 4 more times.
      If you'd prefer a truly random way to select pages, and you are using either Windows or Linux, you can easily create random numbers in a selected range (such as the number of pages in your dictionary) from your terminal.
      Assuming your dictionary has, for example, 854 pages:
      Windows: Open a Powershell terminal and enter:
      [C:\User>] get-random -maximum 854
 
      Linux: Open a terminal and enter:
      [user@you:~$] echo $(( $RANDOM % 854 ))
 
      Each time you repeat this command, your operating system will return a random number somewhere in the range of available pages of your dictionary.
      Use this function to pick pages in a truly random manner, and select the needed words in the same way as before.
      Both this and the Diceware method are good ways to create a password with sufficient randomness that was generated completely off-line.
       Use an open-source password manager
      There are several well-known, cross-platform, and open-source password managers available. The main requirement besides being open-source, is a cryptographically secure random number generator, with the ability to generate significant entropy while using letters, numbers, and special characters.
      It is recommended that you use all available characters when generating a password, and the length of the password should be at least 12 characters for minimally sufficient entropy.
      It is up to the user to choose between a password manager that stores its data in the cloud, making it easy to stay in sync across various devices, or one that only stores its data locally.
      As it so often happens, more convenience means less security in this decision.
       Password entropy
      "Entropy" is a term commonly used to define password strength. It is typically used to describe the combined effect of randomness, length, and number of characters (lowercase/uppercase letters, numbers, and special characters) or words in a password or passphrase.
      Calculating entropy allows the strength of different randomly constructed passwords or phrases to be compared. It also defines the size of the search-space an attacker would need to cover to find the password by trying all possibilities.
       How to calculate entropy
      Assuming a password or passphrase is constructed randomly, its level of entropy can be calculated in this way:
      • For a password, the total number of possible outcomes given a specific length (L), and number of characters used (C), is: C raised to the power of L, or C^L.
         Example: jwodnrosqf is lowercase only (C = 26) and 10 characters long (L = 10). So, 26^10 = 141,000,000,000,000 (141 trillion).

         Including uppercase letters in the same password: jWoDNrosqF to double (C), results in 52^10 possible passwords = 145,000,000,000,000,000 (145 quadrillion).

         Including special characters in the same password: jW0DNro$qF raises (C) to 95, resulting in 95^10 possibilities = 59,900,000,000,000,000,000 (59.9 quintillion).
      • For a passphrase chosen randomly from a list of words, the total number of possible outcomes given a specific number of words (N) and wordlist size (S) is: S raised to the power of N, or S^N.
         Example: The EFF Diceware list contains 7776 words. Randomly selecting 5 words from the list results in 7776^5 possible passphrases = 28,400,000,000,000,000,000 (28.4 quintillion).
      Just knowing how to do these basic calculations allows you to compare the strength of different randomly-generated passwords or phrases.
       "Bits" of entropy
      Password entropy is often discussed and compared in a context of bits of entropy. This is, of course, because computers can only process 0's and 1's, or bits, so everything related is expressed that way. To calculate bits of entropy, use a calculator that does logarithmsopen in new window and compute log2(x), where x = the total number of possible outcomes for an event.
      For example, there are 7776 words on the EFF wordlist commonly used with dice to create passphrases. Plugging 7776 into the calculator to get log2(7776), it is shown that each word taken randomly from the list contributes 12.92 bits of entropy to the strength of the passphrase. So, a 5-word passphrase selected randomly from the EFF list will have 5 x 12.92 = 64 bits of entropy.
      Since the combination of: lowercase + uppercase letters, numbers, and special characters = 95, a password constructed using all of these will have log2(95), or 6.57 bits of entropy for each character that comprises the password.
      From that, we can now calculate that, in order to get the same level of entropy with a password instead of a 5-word passphrase, the password must be at least 10 characters in length.
       How much entropy is needed
      Entropy matters because it allows one to compare the required search-space of a potential password with the search-speed known to be available to various potential adversaries. In doing so, it is possible to then know how long it would take an adversary with known resources to attempt every mathematically possible password or passphrase for a given level of entropy.
      Edward Snowden revealed in 2013 that the NSA had the ability to guess passwords at a rate of 1 trillion guesses/second. At that speed of guessing, the password in the above example (28.4 quintillion possibilities) could be guessed in at most, 11 months.
      Since there is an equal chance of finding the password in the first half of the total number of guesses as there is in finding it in the second half of the total number, it is accurate to assume that on average, a password will be found in 1/2 of the time required to do an exhaustive search. That means just over 5 months for the example just mentioned.
      Keep in mind that Snowden's information in quite old, in a processing-power context. We have no way of knowing what is currently possible, so if a State-Level attacker is a part of your assumed threat-model, it would be wise to assume that their tools are now much more powerful.
      Even if a given threat-model does not include State-Level attackers, it is still important to consider that there are GPU-based password hacking tools publicly available that are capable of guessing well into the billions of guesses/second.
      
-    
+    
   
 
diff --git a/using-wasabi/PasswordFinder.html b/using-wasabi/PasswordFinder.html
index 6eeca9fdf0..3065b21357 100644
--- a/using-wasabi/PasswordFinder.html
+++ b/using-wasabi/PasswordFinder.html
@@ -24,10 +24,10 @@
     
     Password Finder | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Password Finder
      Wasabi Password Finder is a tool for helping those who made a mistake typing the password during the wallet creation process. This tool tries to find the password that decrypts the encrypted secret key stored in a given wallet file.
       Limitations
      Wasabi Wallet protects the encrypted secret key with the same technology used to protect paper wallets (BIP 38open in new window) and for that reason, it is computationally infeasible to brute force the password using all the possible combinations (assuming a secure password was chosen).
      WARNING
      It is important to know that the Wasabi Password Finder is not for breaking wallet passwords but for finding errors (typos) in an already known password, and that it's success rate is limited.
       Usage
      After an incorrect password is entered when opening a wallet, Forgot Password will show up.
      Wasabi Wallet Forgot Password
      First you will be asked questions, like your most likely password, which language, which characters it contains etc. After that it will search if your password can be found.
      
-    
+    
   
 
diff --git a/using-wasabi/PayJoin.html b/using-wasabi/PayJoin.html
index 26e1e0a23d..391e4b48ff 100644
--- a/using-wasabi/PayJoin.html
+++ b/using-wasabi/PayJoin.html
@@ -24,7 +24,7 @@
     
     PayJoin | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       PayJoin
       Sending PayJoin step-by-step
      1. Load a wallet and open the Send dialog.
      2. Request from the receiver a BIP21 Bitcoin URIopen in new window with the flag pj= and paste it into the To field of the Send dialog. (E.g. bitcoin:tb1q0382a3m2jzvyk5lkea5h5jcht88xa6l0jufgwx?amount=0.00010727&pj=https://payjoin.test.kukks.org/BTC/pj)
      Send Bitcoin PayJoin transaction in Wasabi Wallet
      1. Click Continue.
      2. Enter the label.
      3. At Preview Transaction, verify that the information is correct.
      PayJoinPreviewTransaction
      1. Click Confirm, and type in the password.
      The success of a PayJoin transaction is not something that depends on Wasabi.
      It may happen that the transaction is broadcast with success, but that it is not a PayJoin. This can happen for several reasons including:
      • The receiver did not have any utxos to contribute towards a PayJoin.
      • Your wallet does not use the same address format as the receiver's.
      • The PayJoin server is not available.
       The goal of PayJoin
      PayJoin is a collaborative transaction between the sender and the receiver of a payment, for example the merchant and the customer. The goal of the protocol is to break the common input ownership heuristic, while making it difficult to fingerprint that the transaction is in fact a CoinJoin. Further, it reduces the transaction fees paid by the merchant due to consolidation of coins.
       Coordination
      The coordination of this coinjoin is done with the PayToEndPoint [P2EP] concept. The receiver is reachable over the internet, either over a Tor onion service or clearnet IP address. The link is included in a BIP21 Bitcoin URI, and is provided to the sender as the payment invoice. The sender uses this onion service or IP address to connect to the server of the receiver and communicate the further protocol. The coordination is usually done within seconds, and will abort to the fallback transaction after some time if the connection breaks.
       Fallback transaction
      In the very first request to the receiving server, the sender provides a finalized signed transaction which has only the inputs of the sender, like any other Bitcoin transaction. The inputs are only from the sender. The outputs are the address of the receiver, as well as the change address of the sender. For example here, Alice pays Bob 0.2 bitcoin.
      Alice input   1 bitcoin   -->   Bob output            0.2 bitcoin
@@ -32,6 +32,6 @@
 
      Both the sender and the receiver could broadcast this transaction.
       PayJoin transaction
      The receiving server responds to this initial proposal, with a transaction that adds more inputs to the transaction. Thus, the output belonging to the receiver increases in value, above the value that the payment amount is due.
      Alice input   1 bitcoin   -->   Bob output            0.7 bitcoin
 Bob input     0.5 bitcoin -->   Alice change output   0.8 bitcoin
 
      The sender broadcasts this transaction to the Bitcoin network.
       Advantages of PayJoin
      First and foremost, the common input ownership heuristic is broken, meaning that the inputs do not belong to one single entity, but to several of them. This breaks one of the most important assumptions of transaction surveillance companies. Contrarily to other coinjoin implementations, the outputs are not of equal value, so it is not obvious that this transaction is in fact a coinjoin.
      Further, the outputs do not reflect the actual value of the transaction. In our example, the economic transfer is of 0.2 bitcoin from Alice to Bob, but the outputs are worth 0.7 bitcoin and 0.8 bitcoin. This is obfuscating the actual amount payed.
      Finally, the receiver is consolidating his coins, thus saving on future transaction fees. Without the PayJoin, the receiver would have two coins, worth 0.2 bitcoin and 0.5 bitcoin, and he would have to pay twice the transaction fee to spend these coins. But because of using PayJoin, he only has one coin, worth 0.7 bitcoin, thus reducing his future transaction costs when spending this coin.
      
-    
+    
   
 
diff --git a/using-wasabi/RPC.html b/using-wasabi/RPC.html
index b5f055d30b..893a6e7209 100644
--- a/using-wasabi/RPC.html
+++ b/using-wasabi/RPC.html
@@ -24,7 +24,7 @@
     
     RPC Interface | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Wasabi Remote Procedure Call Interface
      Wasabi Wallet provides an RPC interface to interact with the wallet programmatically. The RPC server is listening by default on port 37128.
       Limitations
      The RPC server does NOT support batch requests or TLS communications (because it is not supported on Linux and on Macopen in new window). Requests are served in order one-by-one in series (no parallel processing). It is intentionally limited to serve only one whitelisted local address and it is disabled by default.
      The more user friendly command line interface wcli can be found hereopen in new window.
       Configure RPC
      The RPC server has to be configured and enabled. This is done in the Config.json file and the relevant settings are:
      JsonRpcServerEnabled: [true | false] (default: false)
@@ -416,6 +416,6 @@
   "id": "1"
 }
 
      
-    
+    
   
 
diff --git a/using-wasabi/Receive.html b/using-wasabi/Receive.html
index b43f2ed075..b6ddfa9a2d 100644
--- a/using-wasabi/Receive.html
+++ b/using-wasabi/Receive.html
@@ -24,7 +24,7 @@
     
     Receive | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Receive bitcoin
      Receive bitcoin in Wasabi Walletopen in new window
       Generating addresses step-by-step
      1. Start Wasabi and open the wallet that you want to receive coins into.
      2. Click the Receive button in the main view's top right corner.
      3. Type in the name of the entities who know that this address is yours. If you have already used a label before, simply choose it from the suggested labels.
      Receive label in Wasabi
      1. Press Continue and the wallet will generate a new address.
      Bitcoin address in Wasabi
       Bitcoin public keys and addresses
      The Bitcoin protocol utilizes public key cryptographyopen in new window to defend and verify the property rights of the individuals holding and transacting bitcoin. A private key is a large random number that should be kept secret. With the elliptic curve digital signature algorithmopen in new window, based on the private key you can calculate a public key. If someone has only the public key, it is computationally infeasible [pretty much impossible] to calculate the private key. Whoever knows the private key can calculate a cryptography signature over a message, which proves that the private key was known by the signer, without actually revealing the secret.
      For data size efficiency, in Bitcoin, the public key is hashedopen in new window and encoded into a bech32 address. This address commits to the public key, which commits to the private key. In a Bitcoin transaction, the output creates a new unspent transaction output which is "locked up" by an address. The input of the transaction spends a UTXO by providing a valid signature of the public key that the address committed to.
      TIP
      Wasabi Wallet does not "store your money", rather it stores your public keys and an encrypted secret that requires your password to derive the private keys. It creates addresses for receiving bitcoin, and it signs transactions that spend your bitcoin.
       The problem with address reuse
      Whenever you use the same address to lock up different UTXOs, then all these coins can be spent by anyone who knows the same private key. This makes it obvious for anyone that this one entity [you] owns all these coins, which is very bad for privacy. The first rule of Bitcoin privacy is never reuse addresses!
      TIP
      This is why Wasabi removes the address from the Addresses Awaiting Payment list as soon as it has received a coin.
       The importance of labeling
      Satoshis are the base unit currency of the Bitcoin network and are truly fungible, meaning that any 100 000 000 satoshis are always equal to 1 bitcoin. Just like with gold atoms, it doesn't matter which specific gold atoms you have, as long as it's gold, it's gold. However, an unspent transaction output, a bitcoin, is a chunk of money and is not fungible, because it has a different amount of satoshis in it, a different public key locking it up, a unique transaction history, and a unique index number. This is just like a gold coin, with a unique amount of gold atoms, and either a pretty mintage or an old chipped broken coin. Because UTXOs are not fungible, it is very important to know exactly which coin is which, and that is done by carefully labeling.
      For example, if I create a new address to receive a 0.5 BTC payment from Andrew for a laptop that I sold to him then the label has to be: Andrew.
      The label is not for describing the reason for payment, but rather to list those who know that this address is yours. Understanding this difference between labeling an address and describing a transaction is very important for your privacy.
      TIP
      In Wasabi it is mandatory to give every receive address a label of those who know that this address is yours, so that later you know what to do with it, and it also helps the auto coin selection algorithm when sending.
       Clusters
      Following the previous example, if I have to send a fraction (0.1 BTC) of the previously received coin to Charlie then in the Send tab the observers should be: Charlie. In that way, the change (0.4 BTC) will be known by Andrew and Charlie because they both will be able to follow the change. That's exactly what Wasabi displays in the coins list (cluster column), Wasabi tells us who are the ones that know about each of our coins in order to allow us to decide what to do with the coins.
      Let's take a look at another example: Imagine you have three coins, one known by Alice, one known by a KYC exchange and finally one known by Charlie. Imagine you need to sell a few sats to Charlie, which coin/s should you send? The obvious selection is the one already known by Charlie because by doing that he cannot learn anything new about our wallet, moreover, neither Alice nor the KYC exchange can learn anything new! But what if the coin is not big enough and we need to use more than one coin? You can use the one known by Alice or the one known by the KYC exchange, but are you okay with Charlie knowing about your deposit/withdrawal from the exchange? Are you okay with Alice knowing about your deal with Charlie? In case none of those combinations are acceptable for you then you should CoinJoin your coins.
       Coinjoined coins
      Those inputs that participate in a Wasabi coinjoin transaction get transformed into arbitrary sized outputs with an increased anonymity score. By default, Wasabi tries to create big coinjoin transactions with many inputs and outputs, but the individual coins' privacy varies depending on the final amounts and values of the inputs and outputs of other participants. The higher the anonymity score of a coin, the harder it is for an observer to know who that coin belongs to. For that reason, coins with a high anonymity score are usually the ones preferred when making a payment transaction. When coins achieve the target anonymity score of the selected coinjoin strategy, their values will the visible under the Privacy Progress bar.
       Final words about labels and examples
      4 coins with good labels:
      Andrew
@@ -34,6 +34,6 @@
 
      2 coins with bad labels:
      Payment from Andrew for my laptop
 From my old wallet
 
      In case we take the two first coins with good labels and send them to María, look how the change cluster will be displayed: Maria, Andrew, David, Me (these people know about the coin). Now, look how this will be displayed if I use the two coins with bad labels: Maria, Payment from Andrew for my laptop, From my old wallet (Is this high-quality info about the privacy level of my coin? Not really.).
      So, think about coins, think about who knows and make sure to make decisions about privacy based on what you are going to reveal and to whom. Wasabi doesn't care about why you transact with bitcoins, it only cares about who you transact with because this is what helps you reclaim your privacy.
      
-    
+    
   
 
diff --git a/using-wasabi/RestoreElectrum.html b/using-wasabi/RestoreElectrum.html
index 3afb4c2cee..c69350aef4 100644
--- a/using-wasabi/RestoreElectrum.html
+++ b/using-wasabi/RestoreElectrum.html
@@ -24,13 +24,13 @@
     
     Restoring Wasabi Wallet in Electrum | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Restoring Wasabi Wallet in Electrum
      Potential privacy leak!
      If you do not run your own Electrum server, you will leak all your addresses to random third-party servers, losing anonymity against those entities, so you must make a judgement call by being aware of this.
      To gain some privacy by using Electrum you should set up Tor on Network preferences or by installing your own Electrum server via Electrum Personal Serveropen in new window, ElectrumXopen in new window or Electrsopen in new window.
      Electrum does currently not support Taproot
      As of Wasabi version 2.0.3open in new window, users may receive Taproot outputs from coinjoin or as a change output from a normal transaction. So when recovering a wallet from Wasabi in Electrum some funds might be missing, as the Taproot (SegWit v1) coins are not shown. An other wallet that does support Taproot should be used for recovering Taproot coins.
       Restoring Wasabi Wallet via Electrum GUI
      1. Launch Electrum.
        If you don't have a wallet created on Electrum it should automatically display an Install Wizard. If it opens your default wallet then go to File -> New/Restore.
      2. Name your new Electrum wallet.
      3. Choose Standard wallet.
      4. Choose I already have a seed.
      5. Type in your seed (recovery words).
      6. Click the Options button, then select BIP39 seed and if you created your Wasabi wallet with a password make sure to check Extend this seed with custom words and type your password in the Seed extension window.
      7. On the Script type and Derivation path window, choose native SegWit (p2wpkh) or manually insert m/84'/0'/0'.
      8. Increase the gap limit by opening Electrum's Console and execute the following commands:
        wallet.change_gap_limit(100)
 wallet.gap_limit_for_change = 100
 wallet.synchronize()
 
      
-    
+    
   
 
diff --git a/using-wasabi/Send.html b/using-wasabi/Send.html
index 2b745b4c20..2c8475447c 100644
--- a/using-wasabi/Send.html
+++ b/using-wasabi/Send.html
@@ -24,10 +24,10 @@
     
     Send | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Send
      Send in Wasabi Walletopen in new window
       How to send bitcoin step-by-step
      1. Click the Send button.
      Wasabi Wallet Send Button
      1. Enter the destination address.
      Wasabi Wallet Send To Field
      1. Specify the amount of bitcoin to send to the destination address. Optionally, you can specify the dollar amount to send instead.
      Wasabi Wallet Send Amount Field
      1. Click Continue.
      Wasabi Wallet Send
      1. Label the recipient by entering the name of the person or company who you are sending to.
      Wasabi Wallet Send Recipient Label
      1. Preview Transaction.
        • Verify the amount, recipient, and the address.
        • Review the estimated time for confirmation and the transaction fee. Optionally, you can change the transaction fee or confirmation time by clicking on the edit fee icon.
        Wasabi Wallet Send Change Fee
        • Review the suggestions to improve your privacy by clicking the shield icon in the top right corner. For example, you may want to slightly increase or decrease your payment amount to avoid change.
        Wasabi Wallet Send Privacy Suggestion
      2. Click Confirm.
      Wasabi Wallet Send Preview Transaction
      1. Type in your password, then click Continue.
      Wasabi Wallet Send Password
      1. Transaction successfully sent!
      Wasabi Wallet Payment Successful
       Coins
      A coin is an unspent transaction output (UTXO): a chunk of bitcoin that can be sent in a future transaction. Unlike fiat currencies which have fixed denominations, each UTXO contains a variable amount of bitcoin. You can get coins by first receiving them from someone else. When you want to send some bitcoin you simply enter the amount to send and the address after clicking the Send button. Wasabi Wallet does the job of automatically selecting the appropriate combination of coins to include as inputs in the transaction.
       Clusters
      Every time you receive a payment, you first must label the observers who know this address is yours. This transaction metadata is used to build a cluster of which people know about your coins. For example, if you receive a coin from Alice, then the cluster is Alice. If you now send half of this coin to Bob, then the cluster of your change coin is Alice, Bob. The goal is to know the observers who know about your coins and try to reduce their number for each coin.
       Anonymity Set
      A typical bitcoin transaction will contain one input and two outputs - one of the outputs is the coin you are sending and the other output is the change coin that goes back to your wallet. Your change coin can be linked to this one input. There is a 1 in 1 chance to find this link and no plausible deniability. Thus, Wasabi denotes this coin's anonymity set as 1.
      In a Wasabi coinjoin, many peers register coins in the input of the transaction, and in the output there are several equal value coins. For example, the output may contain 20 coins worth exactly 0.3 bitcoin. This means that when looking at one of these coinjoin outputs, there is a 1 in 20 chance to find the corresponding input: thus an anonymity set of 20. Therefore, the higher the anonymity set, the more your post-coinjoin coin is delinked from the pre-coinjoin history.
      There are three coinjoin strategies to choose from in Wasabi Wallet which effect the target anonymity score for your coins. These three strategies are Minimize Cost, Maximize Speed, and Maximize Privacy. Each of these strategies come with different trade-offs.
      Alternatively, custom coinjoin settings can be configured.
      Coinjoin Strategy
       Receiving Address
      When sending bitcoin, you need to know the destination address of the receiver. This commits to the spending condition that the receiver agrees to have for this coin. The address can be a public key hash [starting with 1], a script hash [starting with 3], a native SegWit bech32 public key hash [starting with bc1q], or a Taproot bech32m public key [starting with bc1p]. Make sure that you ask the receiver for a new address for every payment to protect your privacy and theirs. Wasabi will calculate the checksum and notify you if the provided address is wrong.
       Observers
      In Wasabi it is mandatory to provide one or more labels each time you initiate a transfer of bitcoin. These labels should be the observers of the transaction. An observer of a sending transaction is, of course, the receiver, as well as any other third party that knows that you are the sender of this transaction. For example, you should include as a label the payment processor or the bitcoin exchange if you use their services. This metadata will be used to build an accurate cluster of observers who know about your coins.
       Amount
      In the Amount text box you can specify how many bitcoins the receiving address will gain. You can also see and enter the current US Dollar value of the sending amount.
      Avoid sending rounded values
      If you specify a rounded amount, like 0.0100 0000 bitcoin, then the change output will not be rounded, like 0.0896 8413 bitcoin. This makes it easy for an observer to conclude that the spending amount was the 0.01 bitcoin, and that the other output is the change back to the sender. So in order to increase your privacy, you can set a non-rounded amount, like 0.0101 6843.
      Send Amount Field
       Mining Fee
      Every transaction must specify a fee which incentives the miner to include it in a block, it is calculated by value of inputs - value of outputs. The higher the fee per virtual byte (vByte) transaction size, the more likely miners are to confirm this transaction. Wasabi uses Bitcoin Core's smart fee algorithm to estimate the time it will take to confirm at the given fee level. You can change the fee by moving the slider, or by manually setting the transaction fee rate.
      Wasabi Wallet Fee Slider
      In some cases, there is very little demand for block space, and then Wasabi will set the minimum fee of 1 sat/vByte.
      High-priority transaction fees
      If you have a transaction that is high-priority and you really want it to be confirmed ASAP:
      1. Use a mempool monitoropen in new window (available Tor onion websiteopen in new window) to see what fees are likely to get a transaction to be confirmed in the next block.
      2. Select a fee that is well above the current highest fee (perhaps double or triple it) if it is very important to you that the transaction is confirmed soon.
      For a deeper dive into the fee estimation process, this articleopen in new window is worth reading.
       Privacy Suggestions
      Since Wasabi version 2.0.4open in new window the Preview Transaction dialog contains privacy suggestions. The privacy suggestions help the user to improve their transaction. They are displayed when hovering over the triangle or shield in the top right corner. The suggestions are based on the current coin selection for this transaction. For example, the suggestions will warn the user when the transaction contains non-private coins.
      There are warnings for:
      • Interlinking labels
      • Using non-private coins
      • Using semi-private coins
      • Creating change
      • Consolidating 10 coins or more
      • Using unconfirmed coins
      • Using coinjoining coins
      There are clickable suggestions to:
      • Manage labels (when interlinking labels)
      • Only use private coins
      • Not use non-private coins (only use private and semi-private)
      • Avoid change
      The suggestion to only use semi-private or private coins is only shown if the amount difference is less than or equal to 25%.
      TIP
      Each suggestion has a tooltip. Hover over the suggestion to see more information.
       Password
      In order to spend a coin, the transaction must be signed by the private key corresponding to that coin. Wasabi stores a secret on the computer, encrypted with the password that you specified during the wallet generation. To spend a coin you need to type in the password, which decrypts the encrypted secret, and then derive the child private key that signs the transaction. Afterwards, the password is wiped from memory.
       Broadcast
      Once the transaction is signed, Wasabi will connect to a random Bitcoin P2P node over Tor and provide this transaction, then it will immediately disconnect. This first node will gossip the transaction throughout the network, then miners can include it in a block.
      If for some reason the first broadcast fails, then if you have Wasabi connected to your own Bitcoin full node this node will broadcast the transaction to the network. If this also fails, then the transaction is sent to the backend coordinator with a new Tor identity, who then broadcasts the transaction to the network.
       Speed Up or Cancel Transaction
      Pending (unconfirmed) Bitcoin transactions can be replaced by sending a new transaction that pays a higher fee rate using the same (or some) coins/UTXOs. This can be used to speed up or cancel a transaction. The miners are incentivized to mine the transaction with the higher fee rate, as this will earn them more money. If the new higher fee rate paying transaction is confirmed, the old transaction can be considered "replaced".
      Since Wasabi version 2.0.4open in new window it is possible to easily speed up or cancel a pending transaction. Speeding up and cancelling are similar to each other, the main difference being that a Cancel Transaction will send the coins to a new address owned by the user/wallet (this is all done automatically). The transaction is then "cancelled" because the bitcoin (minus the fees) is returned to the user's wallet.
      Speeding up or cancelling a transaction costs additional fees, because a new bitcoin transaction with a higher fee rate (than the previous transaction) has to be sent.
      Wasabi first tries to utilize RBF, if that's not possible it tries to do CPFP.
      To Speed Up or Cancel a Transaction, right-click on the pending transaction in the history.
      History Right Click
      Click one of the two options and then confirm that you want to pay the additional fee for this action. After which the succesfully speed up/cancelled dialog is displayed.
      In the history, the transaction will now have a rocket (speeded up) or a cross (cancelled) icon. The transaction is still pending, but it should be confirmed sooner than the initial transaction.
      How to speed up Bitcoin transactionopen in new window
      
-    
+    
   
 
diff --git a/using-wasabi/Testnet.html b/using-wasabi/Testnet.html
index 26e542bc05..151dc99cc2 100644
--- a/using-wasabi/Testnet.html
+++ b/using-wasabi/Testnet.html
@@ -24,10 +24,10 @@
     
     Testnet | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Testnet
       Bitcoin testnet
      The Bitcoin testnet is a network that behaves almost exactly the same as the Bitcoin mainnet. The major difference is that the bitcoin on the testnet do not have any economical value, they should not be used to buy or sell goods and services. This makes the network very useful for testing software and features, because there is no risk of losing precious "real" bitcoin from the main network.
      Don't loose your bitcoin
      When testing cutting edge software like Wasabi, use testnet to ensure that your mistakes don't cost you money!
       Activating testnet in Wasabi
      First, open your Wasabi Wallet and click the Settings button in the bottom left corner.
      Settings button
      Select the Bitcoin tab, click on the Network dropdown and select TestNet.
      Settings Network Dropdown
      Restart Wasabi to activate the change. After the restart, you should see the TestNet indicator in the top right corner of the wallet.
      Bitcoin testnet network activated in Wasabi Wallet
      When Wasabi is started in testnet, it will fetch testnet BIP 158 block filtersopen in new window from the coordinator. For the first start, this may take a couple of minutes.
      After the testing, set the settings back to mainnet, and close Wasabi. It will load on mainnet the next time you start it.
      TIP
      Alternatively, you can edit the Config.json file in your Wasabi data folder. In the second line you can modify the value of "Network":, to "Main", "TestNet", or "RegTest". The changes will apply on the next launch of Wasabi.
       Loading a wallet
      Wasabi differentiates between Mainnet and TestNet wallets. Meaning that a TestNet wallet will not show up when the Main network is active, and vice versa. You have to create a new wallet when you activate TestNet for the first time.
       Receiving testnet bitcoin
      You can generate a receive address the same way as on mainnet, by labeling the known by entities in the Receive dialog. Notice that testnet SegWit addresses start with tb1q..., and not with bc1q... as mainnet addresses.
      Because testnet bitcoin don't have economical value, they are gifted by different sources. There are faucetsopen in new window like this oneopen in new window or bitcoinfaucet.uo1.netopen in new window that give a certain amount of testnet bitcoin per time period. You may also ask other developers if they have a couple of spare testnet coins available.
       Coinjoin on testnet
      CoinJoin on testnet is as easy as on mainnet. Usually there are other testers doing a coinjoin, but if you are the only one at the moment, then load two wallets and start coinjoining in both of them.
      
-    
+    
   
 
diff --git a/using-wasabi/WalletGeneration.html b/using-wasabi/WalletGeneration.html
index 88e0b99d17..23a4e3412a 100644
--- a/using-wasabi/WalletGeneration.html
+++ b/using-wasabi/WalletGeneration.html
@@ -24,7 +24,7 @@
     
     Wallet Generation | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Wallet Generation
       Introduction
      With Wasabi you can generate an unlimited number of Bitcoin wallets very quickly, without any cost, and without asking anyone for permission. Each wallet has separate private and public keys in a unique backup, and they are not at all linked to the other wallets generated on the same computer. So, with several wallets, you can conveniently manage your bitcoin for different use cases without worrying about revealing that you control them.
       Generating the wallet step-by-step
      1. Launch Wasabi Wallet. The very first time you run the software the Add Wallet dialog will be open automatically, but you can also access it by clicking on Add Wallet in the NavBar or Searchbar.
      2. Click Create a new wallet to generate a new wallet.
      Add a Bitcoin wallet with Wasabi
      1. Give the wallet a name. This name is not shared with anyone, it is only stored locally on your computer. Click Continue.
      Add Wallet Wallet Name
      1. Write down the 12 recovery words (mnemonic seed phrase) in the correct order and store them in a safe place. You have to use this seed phrase together with your password to recover your wallet (using Wasabi or another BIP 39open in new window compliant wallet).
        Back up your recovery words!
        Without the recovery words (Seed phrase) AND the password, you cannot recover your wallet. So, triple-check that you have a proper backup! Make sure the backup of your recovery words is stored separately from the password backup.
      Wasabi Wallet recovery words
      1. You must confirm the Recovery Words by clicking on the right word in the right order, as a check to make sure that your Recovery Words are backed up. So, confirm the Recovery Words, and click Continue.
      Wasabi Wallet confirm recovery words
      1. Write a long and random password (passphrase) and back it up. It encrypts your secrets, and you will need it every time you want to open the wallet, spend bitcoin from this wallet or recover your wallet.
        If you are uncertain about how to create a secure password, refer to Password Best Practices for helpful information.
        Back up your password!
        Without the password, you cannot spend your bitcoin or recover your wallet, even if you have the recovery words (Seed phrase). So, triple-check that you have a proper backup!
      2. Confirm the password and click the Continue button.
      Wasabi Wallet Add Password
      1. Select the coinjoin strategy for this wallet and click Continue.
      Add Wallet Coinjoin Strategy
      1. The wallet is succesfully added! Click Done.
      Wallet Successfully Added
       Important info about your wallet password
      Wasabi integrates BIP 38: Password-Protected Private Keyopen in new window, which means that the secrets needed to spend the bitcoin are encrypted on the computer. If someone has compromised your operating system and hardware and he only has the encrypted secrets, then no bitcoin can be spent by him. You need both the encrypted secrets and the password in order to enable the private key which can sign a spending transaction. This means that the password is your last line of defense against anyone who tries to steal your bitcoin.
       How are the secrets created
      Wasabi uses BIP 38: Password-Protected Private Keyopen in new window
                            +--------------+
@@ -69,6 +69,6 @@
                   +--------------------+
 
 
      
-    
+    
   
 
diff --git a/using-wasabi/WalletLoad.html b/using-wasabi/WalletLoad.html
index 3dab855940..b514812310 100644
--- a/using-wasabi/WalletLoad.html
+++ b/using-wasabi/WalletLoad.html
@@ -24,10 +24,10 @@
     
     Wallet Load | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       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 password. 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 password and press Open.
      Type your password to open the wallet
       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 filtersopen in new window. 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.
      Wallet is synchronizing itself with the Bitcoin network
       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.4open in new window 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.
      
-    
+    
   
 
diff --git a/using-wasabi/WalletRecovery.html b/using-wasabi/WalletRecovery.html
index 74c2c82028..08c851aa59 100644
--- a/using-wasabi/WalletRecovery.html
+++ b/using-wasabi/WalletRecovery.html
@@ -24,10 +24,10 @@
     
     Recover a Wallet | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Recover a Wallet
      There are two different ways that you can recover an already used wallet in Wasabi.
       Mnemonic Recovery Words and Password
      Wasabi uses the BIP 39open in new window mnemonic code for generating BIP 32open in new window hierarchical deterministic wallets. Both your password and the generated 12 mnemonic recovery words are the necessary secrets to recover your wallet. The recovery words are spell checked based on the official wordlistopen in new window, with the right word shown below the text box.
      To recover a wallet:
      1. Click on Add Wallet at the bottom left corner of the main view.
      Wasabi Wallet Add Wallet
      1. Click on Recover a wallet.
      Wasabi Wallet Add Wallet
      1. Give the wallet a name for future recognition of the wallet.
      Wasabi Wallet Name Wallet
      1. Type in the Recovery Words in the correct order and click Continue.
      Wasabi Wallet Recover Wallet
      1. Type in the Password.
      Add Wallet Add Password
      Now Wasabi will recover your wallet.
      With this, only the private keys are imported, but not the labels of your addresses.
      DANGER
      At recovery, Wasabi is unable to check if your password is correct or not. If you type a wrong password a completely different wallet will be recovered.
      You can also use the Advanced Recovery Options to specify the gap limit. The gap limit is about how far Wasabi will check the HD wallet structure for consecutive addresses that have no coins, in some cases, you may want to increase this limit.
      Wasabi Wallet Recovery Advanced
      TIP
      With this method, you can recover a wallet that was generated with any BIP39 compatible software, not just a Wasabi generated wallet.
       Back up Wallet File and Password
      Wasabi Wallet creates a backup of your wallet file inside WalletBackups in your Wasabi data folder. If you have done a backup of this file, then you can import it at Add Wallet, by clicking on Import a wallet.
      Alternitavely: copy the wallet file to the Wallets folder, and upon the next restart of Wasabi, it will show this wallet in the NavBar, from there you can open it as usual.
      Using this method will also backup your address labels and cluster history.
      WARNING
      Make sure to back up your password separately because it is necessary to spend your bitcoin.
      
-    
+    
   
 
diff --git a/using-wasabi/WasabiSetupVM.html b/using-wasabi/WasabiSetupVM.html
index 2aa23d7be0..f99505a129 100644
--- a/using-wasabi/WasabiSetupVM.html
+++ b/using-wasabi/WasabiSetupVM.html
@@ -24,7 +24,7 @@
     
     Wasabi Setup in Virtual Machines | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Wasabi Setup in Virtual Machines
       Benefits of Virtual Machines
      Virtualization allows you to create and run as many virtual machines (VMs) on a single computer at one time as desired. The only constraints are the amount of RAM and hard disk space available on the host computer.
      Each VM is isolated from the host machine. Therefore, such things as corrupted files, configuration errors, malware, etc., encountered during the use of a VM do not affect the host computer.
      If you are a developer, using virtual machines gives you several powerful features. You can easily:
      • Create snapshots of a VM's state at any time. These snapshots can be restored later if a problem or undesired condition arises in the current state of the VM.
      • Set up a template VM with a desired development environment or configuration, and then quickly create lightweight, disposable clones of the template for specific tests.
      • Develop and/or test applications in Windows, Linux, and macOS at the same time, on the same computer. You can link them together in a customizable internal network if desired.
      For developers, the use of virtual machines offers some of the basic version control features of git but applied to operating systems rather than files or projects.
       Qubes
      Qubesopen in new window is a free and open-source security-oriented operating system meant for single-user desktop computing. Qubes OS leverages xen-based virtualization to allow for the creation and management of isolated virtual machines (VMs) called qubes. This is valuable for users of high security software like Wasabi Wallet, and especially useful for testers of cutting edge developer branches. There is a separation of the virtual machines running Wasabi on testnet, and those running on mainnet with valuable private keys. If a reviewer compiles a malicious developer branch, then his mainnet private keys are secure in a different qube.
      This is a step-by-step guide on how to properly compile Wasabi Wallet from source in independent qubes. For tutorials on how to downloadopen in new window and installopen in new window Qubes, please see their exhaustive documentation.
       Generate Template VM
      The dependencies to compile Wasabi from source will be downloaded and installed in a new template VM, which is generated by cloning the Debian template from the dom0 terminal.
      [user@dom0 ~]$ qvm-clone template-debian-10 template-wasabi
@@ -32,7 +32,7 @@
 
      Update the template-wasabi.
      [user@template-wasabi ~]$ sudo apt update
 [user@template-wasabi ~]$ sudo apt upgrade
 [user@template-wasabi ~]$ sudo apt dist-upgrade
-
      Install .NET 7.0 SDKopen in new window for "Build apps" in template-wasabi.
      Optional for privacy
      You can disable .NET's telemetry, which is sending some usage information to Microsoft:
      [user@template-wasabi ~]$ export DOTNET_CLI_TELEMETRY_OPTOUT=1
+
      Install .NET 8.0 SDKopen in new window for "Build apps" in template-wasabi.
      Optional for privacy
      You can disable .NET's telemetry, which is sending some usage information to Microsoft:
      [user@template-wasabi ~]$ export DOTNET_CLI_TELEMETRY_OPTOUT=1
 
      If you need to update .NET, then do it in this VM. Now shut down template-wasabi.
      [user@dom0 ~]$ qvm-shutdown template-wasabi
 
       Generate App VM
      Create a new App VM source-wasabi which is based on template-wasabi. This qube will be used to download, compile and run the Wasabi source code. This way you can create multiple App VMs for different testing purposes. All these App VMs will be updated when you update template-wasabi.
      [user@dom0 ~]$ qvm-create source-wasabi --template template-wasabi --label red
 
       Compile and Run Wasabi
      Start the gnome-terminal of source-wasabi.
      [user@dom0 ~]$ qvm-run -a source-wasabi gnome-terminal
@@ -46,7 +46,7 @@
 
       Install Package in App VM
      Alternatively, you can also install the package in a new App VM, this is a stable version suitable to use on mainnet and is separated from the development App VM. There are no additional dependencies required, so the App VM can be based on template-debian-10 directly.
      [user@dom0 ~]$ qvm-create package-wasabi --template template-debian-10 --label red
 [user@dom0 ~]$ qvm-run -a package-wasabi gnome-terminal
 
      Download, verify and install the latest Wasabi-2.0.5.deb package in package-wasabi, then start Wasabi.
      [user@package-wasabi ~]$ wassabee
-
       VirtualBox
      VirtualBoxopen in new window is a lightweight, powerful free and open-source virtualization tool that allows you to run one or more independent operating systems as "virtual machines" (VMs) on your computer. The computer on which VirtualBox is installed is referred to as the "host" machine, and the VMs that are created are referred to as "guests".
      Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and supports a large number of guest operating systems including, but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x and 4.x), Solaris and OpenSolaris, OS/2, and OpenBSD.
      You can download the latest Virtualbox binary for your host OS hereopen in new window.
      Make sure that you also download the VirtualBox Extension Pack, shown just below the links for downloading the binary installation files. This package will add several useful capabilities to VirtualBox.
      Wasabi Wallet Virtualbox
      Detailed instructions for installing VirtualBox on your host computer can be found hereopen in new window.
      If you run into trouble or have special requirements, the complete User Manual can be found hereopen in new window.
       Create Your First Virtual Machine
      Detailed instructions for creating various types of virtual machines can be found hereopen in new window.
      Things to Note:
      • For each operating system version that you wish to use in a VM, you will need an .iso installation file for that particular OS.
      • During the installation process for whatever OS you have chosen for your VM, you will likely see references to your hard disk and/or Master Boot Record. Be assured that those references are pertaining to your "virtual" hard drive and/or boot records that are a part of the VM. They are NOT referring to your computer's physical drive or boot records.
      Other than the creation of a folder which holds the data for each VM that you may create, your physical hard drive and/or boot records will not be altered or harmed by the installation of an OS inside the VM.
      • Optional, but strongly recommended: Enable the built-in "Guest Additions" functions of Virtualbox. This step will give you a full-sized display, and make the usage of your mouse seamless when switching between different VMs that are running at the same time. Instruction for enabling "Guest Additions" can be found hereopen in new window.
       Generate a Template VM
      It's now time to start customizing your development templates! Make sure that you have run any needed updates for your VM.
      Next, the dependencies to compile Wasabi from source will be downloaded and installed in a new template VM, which can be based on your preferred OS.
      With VirtualBox, you can create separate templates based on Windows or any Linux distribution. Finally, you can add any other tools that you prefer, such as Visual Studio / Visual Studio Code, Atom, etc..
       Install Required Dependencies
      Start your template VM and open a terminal window.
      Install .NET 7.0 SDKopen in new window for "Build apps".
      Optional for privacy
      You can disable .NET's telemetry, which is sending some usage information to Microsoft. In your terminal window, run:
      your@vm:~$ export DOTNET_CLI_TELEMETRY_OPTOUT=1
+
       VirtualBox
      VirtualBoxopen in new window is a lightweight, powerful free and open-source virtualization tool that allows you to run one or more independent operating systems as "virtual machines" (VMs) on your computer. The computer on which VirtualBox is installed is referred to as the "host" machine, and the VMs that are created are referred to as "guests".
      Presently, VirtualBox runs on Windows, Linux, Macintosh, and Solaris hosts and supports a large number of guest operating systems including, but not limited to Windows (NT 4.0, 2000, XP, Server 2003, Vista, Windows 7, Windows 8, Windows 10), DOS/Windows 3.x, Linux (2.4, 2.6, 3.x and 4.x), Solaris and OpenSolaris, OS/2, and OpenBSD.
      You can download the latest Virtualbox binary for your host OS hereopen in new window.
      Make sure that you also download the VirtualBox Extension Pack, shown just below the links for downloading the binary installation files. This package will add several useful capabilities to VirtualBox.
      Wasabi Wallet Virtualbox
      Detailed instructions for installing VirtualBox on your host computer can be found hereopen in new window.
      If you run into trouble or have special requirements, the complete User Manual can be found hereopen in new window.
       Create Your First Virtual Machine
      Detailed instructions for creating various types of virtual machines can be found hereopen in new window.
      Things to Note:
      • For each operating system version that you wish to use in a VM, you will need an .iso installation file for that particular OS.
      • During the installation process for whatever OS you have chosen for your VM, you will likely see references to your hard disk and/or Master Boot Record. Be assured that those references are pertaining to your "virtual" hard drive and/or boot records that are a part of the VM. They are NOT referring to your computer's physical drive or boot records.
      Other than the creation of a folder which holds the data for each VM that you may create, your physical hard drive and/or boot records will not be altered or harmed by the installation of an OS inside the VM.
      • Optional, but strongly recommended: Enable the built-in "Guest Additions" functions of Virtualbox. This step will give you a full-sized display, and make the usage of your mouse seamless when switching between different VMs that are running at the same time. Instruction for enabling "Guest Additions" can be found hereopen in new window.
       Generate a Template VM
      It's now time to start customizing your development templates! Make sure that you have run any needed updates for your VM.
      Next, the dependencies to compile Wasabi from source will be downloaded and installed in a new template VM, which can be based on your preferred OS.
      With VirtualBox, you can create separate templates based on Windows or any Linux distribution. Finally, you can add any other tools that you prefer, such as Visual Studio / Visual Studio Code, Atom, etc..
       Install Required Dependencies
      Start your template VM and open a terminal window.
      Install .NET 8.0 SDKopen in new window for "Build apps".
      Optional for privacy
      You can disable .NET's telemetry, which is sending some usage information to Microsoft. In your terminal window, run:
      your@vm:~$ export DOTNET_CLI_TELEMETRY_OPTOUT=1
 
      If you need to update .NET, do it in this VM.
      Now, shut down your template VM.
       Cloning a Virtual Machine
      At this point, you should have a Template VM set up with your preferred tools and environment.
      Now the real fun begins, and you will be rewarded for all of your hard work to get to this point!
      VirtualBox will allow you to make as many lightweight, or "linked" clones from a template as you may need. "Linked" means that the vast majority of the system files are borrowed from the template VM while the clone is running, so that the clone takes up much, much less hard drive space.
      Any changes to the clone VM, constructive or destructive, do not affect the template VM. You may think of a linked clone as a "disposable" copy of your template. Perfect for experimentation, with no risk to your template or your computer!
       How to Create a Linked Clone
      Instructions on how to create linked clones in VirtualBox can be found hereopen in new window.
       Compile and Run Wasabi in Your VM
      Start your cloned VM, and open a terminal window.
      Clone & run Wasabi.
      your@vm:~$ git clone https://github.com/zkSNACKs/WalletWasabi.git
 your@vm:~$ cd WalletWasabi/WalletWasabi.Fluent.Desktop
 your@vm:~$ dotnet run
@@ -55,6 +55,6 @@
 your@vm:~$ git checkout <development branch>
 
      Pull the latest commits.
      your@vm:~$ git pull
 
      If you are comfortable with Gitopen in new window, you can now have several versions of Wasabi running for testing purposes, at the same time, on the same computer.
       Install Latest Package
      Alternatively, you can also install the package in a new VM. This is a stable version suitable to use on mainnet and is separated from the development VM. There are no additional dependencies required to run this version.
      Download, verify and install the latest Wasabi-2.0.5 package in your VM, then start Wasabi.
      Have fun, and please consider contributing to the Wasabi project!
      
-    
+    
   
 
diff --git a/using-wasabi/index.html b/using-wasabi/index.html
index a958241f62..505ee2ad9c 100644
--- a/using-wasabi/index.html
+++ b/using-wasabi/index.html
@@ -24,10 +24,10 @@
     
     Using Wasabi | Wasabi Docs
     
-    
+    
   
   
     
-    
+    
   
 
diff --git a/why-wasabi/AddressReuse.html b/why-wasabi/AddressReuse.html
index fa7b4031c1..8b17796667 100644
--- a/why-wasabi/AddressReuse.html
+++ b/why-wasabi/AddressReuse.html
@@ -24,10 +24,10 @@
     
     Address Reuse | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Address Reuse
      The first rule of Bitcoin privacy:
      Never reuse addresses!
      The second rule of Bitcoin privacy:
      NEVER reuse addresses!!
       Problem
       Easy wallet clustering
      If an address is used more than once, it means that the same private key can spend all its coins. It is very easy to find all the UTXOs of an address, and thus to find out how many bitcoin the private key holds.
      Further, in a transaction where one output has a reused address, then it is very likely that this output is the payment destination, and not the change. Most wallets automatically generate new change addresses for every transaction, but payment addresses are selected manually by the user.
      Read more about the privacy concerns of address reuse in the separate entryopen in new window and the privacy chapteropen in new window of the Bitcoin wiki.
      There are different types of address reuse:
       Publicly advertised addresses (donations)
      Here, a person publishes a single address to a public forum, like in the bio of a social media network or on a website, and anyone can send bitcoin to this address.
       Dusting
      With a forced address reuse attackopen in new window, an attacker sends a small amount of bitcoin to an already existing address. The attacker hopes that this dust coin is consolidated with another coin, thus linking the two in a cluster.
       Intentionally malicious
      Since Wasabi is libre and open-source, anyone can modify a fork of Wasabi to make sure the same two addresses are recycled in every CoinJoin registration. This is someone intentionally deanonymizing himself, and he might have quite dubious motives.
       Wasabi's Solution
       Remove used address from GUI
      Wasabi encourages the user to not reuse addresses. You always get a new Bitcoin address whenever you generate one. Previously generated addresses, which haven't received bitcoin yet, are displayed at Addresses Awaiting Payment. An address is automatically removed from the Addresses Awaiting Payment list once that address receives funds.
      To protect against forced address reuse attack (Dusting), Wasabi has a modifiable dust limit, where the wallet does not show coins below a certain threshold value.
      
-    
+    
   
 
diff --git a/why-wasabi/Coins.html b/why-wasabi/Coins.html
index 314a1a19c8..177161d58b 100644
--- a/why-wasabi/Coins.html
+++ b/why-wasabi/Coins.html
@@ -24,7 +24,7 @@
     
     Coins | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Coins
      Bitcoin has an accounting model of unspent transaction output [UTXO]open in new window. A transaction has inputs: the coins that are being spent, and outputs: the corresponding newly created coins (unspent). The input of a transaction has to be an unspent output of a previous transaction. Each UTXO is the tip of the chain of links between inputs and outputs, all the way back to a coinbase transactionopen in new window that pays the miner.
       Problem
       UTXOs are not fungible
      Each UTXO is a unique snowflake with a public transaction history. For example, when Alice sends a coin to Bob, then Bob does not just have any random UTXO, but he has specifically the coin that Alice has sent him. When Bob sends this coin to Charlie, then Charlie can check the history of the coin and see the transaction from Alice to Bob. But due to the pseudonymity of Bitcoin, he does not necessarily find out that Alice is involved.
      Further, when Alice has one non-private coin and one private coin, and she selects both of them as the inputs of a transaction, the linking of these two coins strongly suggests that the coin that was private also belongs to Alice. This means that coin consolidation can lead to an overall decrease in privacy, especially when using an automatic coin selection algorithm.
       Wasabi's Solution
       Manual coin labeling and selection
      Using Wasabi it is mandatory to label every receiving and destination address. This helps the user to know where their coins came from so that they can judge whether there are privacy concerns when sending a specific coin to a specific receiver. The default Send workflow uses the auto coin selection algorithm, which is based on the labeling system.
      Read more here.
       Change avoidance suggestion
      When sending bitcoin, the transaction might contain change (back to the sender). This can have privacy downsides as explained here. When sending in Wasabi the user will be shown with an option to avoid change by slightly increasing or decreasing the send amount in order to avoid change (if possible). There is a shield icon shown at the Preview Transaction screen at the top right corner which displays the options when hovering over with the cursor.
       Heuristics identifying change
      One prime goal of transaction surveillance companies is to identify the change coin of a Bitcoin transaction, as this is vital information for building a cluster of coins belonging to one entity. There are several heuristics, practical assumptions which are not guaranteed to be accurate or optimal, that are used to deanonymize users:
       Address reuse
      When several coins have the same address, then they are owned by the same entity. Thus if a transaction has a reused address in the output, it is very likely to be the payment amount from one entity to another. Thus the other output of this transaction is likely to be the change of the entity providing the inputs of the transaction.
      Remember
      Never reuse addresses!
       Wallet fingerprinting
      Different software wallets have different methods of creating Bitcoin transactions. So if it is known that a transaction was created by a specific wallet, then it can be checked how this wallet handles change.
      Wasabi tries to build the most common form of transaction structure, thus reducing the likelihood of identifying any given transaction as being from Wasabi. However, Wasabi CoinJoins are very easily fingerprinted, and any coin associated is clearly managed with Wasabi Wallet.
       Round numbers
      When making a payment, then often the destination address receives a round number of bitcoin. Because the input is usually a non-round number, the other output will also be a non-round number. This makes it clear that the non-round number output is the change back to the sender.
      A [0.1293 0112 btc]  -->  B [0.0500 0000 btc]
@@ -44,6 +44,6 @@
 A [1.3576 1516 btc]  -->  B [1.0135 6515 btc]
                           C [0.3440 4721 btc] (= change)
 
      
-    
+    
   
 
diff --git a/why-wasabi/LegalConcern.html b/why-wasabi/LegalConcern.html
index dc5b89f862..49e630cd00 100644
--- a/why-wasabi/LegalConcern.html
+++ b/why-wasabi/LegalConcern.html
@@ -24,10 +24,10 @@
     
     CoinJoin Legal Concern | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       CoinJoin Legal Concern
      Using Bitcoin and other cryptocurrencies in the everyday course of businesses is becoming more and more popular. Digital money has a lot of advantages, from unstoppable transactions to relatively low fees, and quick final settlement of international payments. But all come at a price: the blockchain stores sensitive information like the amount and involved addresses of a transaction, giving away too much business-related information to the public. However, this does not necessarily need to be the case.
       Overview
      A CoinJoin transaction obfuscates the history of a given coin, making it hard to trace the coin back to the originator of the funds. The implementation of Wasabi Wallet CoinJoin allows the original user to get back his funds with an obfuscated history.
      It is often assumed that the main problem with an obfuscated transaction history is that financial regulators may have concerns about money laundering. However, this is only the first impression, if we go into the details it can become more transparent why institutions should not worry about violating AML rules and why companies could have a direct competitive advantage using CoinJoin transactions.
      With a transparent financial track record, companies paying with cryptocurrencies may find themselves in a squeezing situation, where their suppliers, clients, and competitors are aware of all of their payment steps and prices. For institutional investors, each step would be scrutinized by the market causing intentional or unintentional price manipulation.
      While the Bitcoin blockchain does not store personal information about the owners of the specific Bitcoin addresses, using metadata makes it possible to link Bitcoin addresses to certain companies and individuals. If such a link can be established, all past and future transactions can be traced.
       CoinJoin transactions
       Difference between ordinary banking and blockchain
      The ordinary banking system is closed, a very non-transparent system, where the data inside this system is hidden from outside observers. “Only” the bank and the user know the transactions made inside the system. In opposition, the blockchain is transparent and open to everyone. This means not only the “bank” (custodial service provider) but also outsider 3rd party observers are capable of tracking these transactions.
       Service providers' obligations regarding privacy
      There is no question a service provider who keeps a record of personal information needs to deal with the different privacy regulations and act according to them. In the ordinary banking system personal financial information is handled as a secret thus preserving individual privacy from third parties. Whereas in the open blockchain system this information by the nature of the technology cannot be kept secret, so there is a large risk of a privacy leak of sensitive financial information. This is obviously not intentional and even though the personal information might be protected, the financial information is nevertheless leaked due to the pseudonym nature of the system. This information has similar sensitivity as name, address, gender, etc. so it should be handled with great care.
       CoinJoin as a privacy-preserving tool
      Since the Bitcoin blockchain is transparent, transactions cannot be kept secret. Currently, one prevalent solution in Bitcoin to gain privacy is to CoinJoin the different coins to obfuscate their history. By the use of this tool, a custodial service provider can at least start to protect its users' financial privacy.
       Privacy perspective from the companies' point of view
      The essence of competitive advantages is to keep and hold business secrets. Each and every successful company has developed its own mechanism to deliver the best products and services to its customers. To reach this, they usually use a secret sauce, called the business secret to deliver the results. If anything, when a financial payment becomes fully transparent this business secret is evaporating Let’s look a bit deeper into what exactly this means for companies, who would like to use Bitcoin as the payment method, where all transactions are recorded on the blockchain.
       Suppliers
      Companies use suppliers to acquire products and services they use in their own production stages. For these products and services, of course, they pay a reasonable price. However, this price is usually negotiable, especially in B2B relationships or large scale orders. What would happen if all of a sudden, the price of raw materials for a company becomes fully public? Other competitors can now demand similar discounts, forcing industries into a vicious cycle of price reduction. As each and every price discount is negotiated on a case by case basis, considering factors as creditworthiness and timing of payment, transparent supplier prices would only cause enormous pressure on suppliers to deal with negotiations.
      Beyond the price of products, the timing of payments is also fully transparent on the blockchain. However, in certain circumstances, it is also a crucial business secret to keep the information on the sequence of invoice payments indoors. Considering cash flow implications, it can happen that one invoice is paid on time, while other invoices are still pending payment. In the case of blockchain transactions however all payments are transparent, so it can be clear for each counterparty that only a selected number of invoices has been paid even if the sufficient funds are available which can cause unnecessary tension between business partners.
      Additionally, if all historical transactions of a company are known, its creditworthiness might be considered incorrectly. It can happen that the creditworthiness is considered better than it is if the incoming funds to a specific address are extraordinarily high, but these funds are needed in other parts of the business, so the overall solvency of the business can be still negative despite the large funds. On the other hand, creditworthiness can be considered worse than it actually is, if only a handful of addresses are taken into consideration for the solvency analysis, neglecting other forms of wealth, like other Bitcoin addresses, or fiat accounts.
       Clients
      From the client’s perspective, the factors listed under suppliers are all applicable. If a client knows the revenue stream of the company, they can draw an incorrect conclusion about the actual financial situation of a company and make a decision of purchasing a product based on this assumed financial situation. If for example, there are no incoming funds for a given period, clients may stay away from purchasing products and services, solely because they might consider the company dormant or insolvent. But in reality, the seasonality of incoming funds is not disclosed for all companies, so it can be a perfectly stable business situation to receive incoming funds only in a given period of a year, while still being able to deliver service throughout the year.
      Another aspect is the possible price negotiations on the client-side. If a client finds out that another client is paying less for a service or product, they can demand similar discounts which can result in downward price pressure in the industry. This can ultimately result in companies going out of businesses if they cannot adjust to the lower price levels which are below the equilibrium prices.
       Competitors
      Everyone can agree that the pricing structure of services is a very sensitive topic and is the core of the business secret which makes a company successful. If all competitors can look at the transactions of the company, it also means they can adjust their own pricing structure to follow the successful market leaders in the industry, causing turbulence in competition. Each company has its own pricing structure which should be coming from the internal processes, know-how, and resources. Although external factors should be considered in pricing, they should not be the main driving force in pricing decisions.
       Employees
      There is now a growing number of companies that are paying their employees salaries in bitcoin due to the trustless transactions with relatively low fees, especially with international transactions.
      With transparent transaction history, employees would be aware of each other’s salaries without the company disclosing this information. Although there are some theories supporting a transparent salary structure, up to now the majority of the companies prefer to keep salaries as secret and obligate employees to keep salary and wage information confidential. Obfuscated transaction history can help companies to keep salary information confidential which can keep a relaxed atmosphere among employees with no wage pressures.
       Phishing attacks
      Disclosing financial information for a company makes them more vulnerable to phishing attacks. If the exact time and amount of payment are publicly known, attackers can use this information to build trust with the company and squeeze out other crucial business information pretending to be a trusted partner.
       Privacy perspective from the institutional investor’s point of view
      The Bitcoin market is considered fairly concentratedopen in new window in the sense that out of the millions of Bitcoin addresses, less than 1% holds 87% of bitcoins.
      Bitcoin address distribution
      Institutional investors and cryptocurrency exchanges are holding large sums of bitcoin on a blockchain where transactions are completely transparent. These so-called whales sometimes need to move large amounts of coins for any reason which can often lead to unintentional price manipulation. If a large bitcoin holding is on the move, it can always raise concern in the media regarding the future of Bitcoin, causing unnecessary price fluctuations. In the case of unintentional price manipulation, it is difficult to prove there has been no insider trading on the institutional side, which can cause loss of faith from the clients.
      Using obfuscated transaction history in large bitcoin transactions can help to keep the market stable and avoid unintentional price manipulations.
       Resolving AML conflicts
      Privacy is not just for criminals. One of the major critiques against using CoinJoin is that if the transaction history is not known for a company, it may be used as a way to launder money. From the above-listed cases, we already see that currently using fiat payments, during the normal course of businesses, companies do not disclose all financial information as that would result in a loss of business secrets. Why would they need to do this if they are just using a new method of payment, called Bitcoin? Using privacy tools to obfuscate Bitcoin transactions is completely legal and in accordance with the current legal framework.
       User privacy
      In all jurisdictions, there are different laws and acts that are made to protect customers privacy. This is not limited only to personal data but also financial data. In the EU there is GDPR, in the USA there is the Privacy Act of 1974, in Canada, there is the Privacy Act of 1985, etc. These set different rules to be kept in order to preserve individual privacy both on personal and financial levels.
       KYC/AML
      By now in mainly all jurisdictions, custodial cryptocurrency service providers (wallet, exchange, payment processor, etc.) are requested to run KYC/AML checks on users and their transactions. The KYC process and inner policies should ensure personal data protection. The accounts are assigned to these individual users, who are verified by the provider. This means the provider identifies the user just like a legacy bank would do. The different AML checks are run on deposits or withdrawals. The suspicious transactions can be linked to users based on the transactions that are initiated by them personally. KYC and AML procedures now ensure that all transactions involving fiat (like buying and selling bitcoin on exchanges for fiat currency) have a detailed background in terms of who is sending what money to whom, the identification of transactions are even more strict than in the current banking world, where two companies or individuals can send even large funds without the need to verify their source.
       Using CoinJoin as a custodial service provider
      As soon as a user deposits the funds to any of these service providers, the funds are in one large cluster. From now on the funds are possessed by the service provider and the actual user balances are only kept on internal records. At this point all KYC/AML procedures are done, funds should be considered “clean”. The funds are controlled by the service provider and different policies are set for securing these funds (hot and cold storage, multisig, etc.). The record system of the provider will show the exact value of funds belonging to the different users. This is the time when a provider could preserve its users’ privacy by applying CoinJoin on these funds. In case of a withdrawal, coinjoined UTXOs could be sent to the user. Again, this user is already KYC-ed, the provider has full knowledge about the user. In case of a law enforcement request, all data can be provided, since the deposit history of the user in question is still available. The only thing CoinJoin does, in this case, is protecting the user from third-party observers, while the service provider is still enabled to provide data for law enforcement if requested.
       Conclusion
      Companies using Bitcoin as a method of payment currently do not have sufficient privacy regarding their financial information. Outsiders can get valuable business-related information by studying the public transaction history of a company, causing economic damage in the long run. Using CoinJoin transactions can help businesses to keep their privacy while still enjoying the benefits that Bitcoin transactions can provide. Concerns from the AML perspective are not valid, as the necessary data can be provided to authorities upon investigation requests.
      
-    
+    
   
 
diff --git a/why-wasabi/NetworkLevelPrivacy.html b/why-wasabi/NetworkLevelPrivacy.html
index dcb11eb579..e09e000f90 100644
--- a/why-wasabi/NetworkLevelPrivacy.html
+++ b/why-wasabi/NetworkLevelPrivacy.html
@@ -24,10 +24,10 @@
     
     Network-Level Privacy | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Network-Level Privacy - Bitcoin Core vs Wasabi Wallet
      Bitcoin is a peer-to-peer network of full nodes that define, verify, and enforce the Bitcoin consensus rules. There is a lot of communication between them and metadata can be used to de-anonymize Bitcoin users.
       Problem
       Clearnet light clients
      When the communication to the network is unencrypted over clearnet, then there is an easy correlation of the Bitcoin transactions to the IP address of the peer who sent it. The IP address can even be used to find the physical location of the user!
      A Bitcoin full node broadcasts not just the transactions of its user, but it also gossips all of the other transactions that it has received from its peers. Thus it is very difficult to find out which transactions originated from which full node. However, when a node or a wallet does not gossip all transactions, but only the transactions of its user, then it is easier to find out which node has sent those specific transactions.
      There are light wallets, which query a backend server to get information regarding specific addresses or use BIP 37open in new window bloom filtering SPV wallet protocol, which is extremely bad for privacyopen in new window. And there is Electrum, which sends your addressesopen in new window to random Electrum servers.
      DANGER
      When the user sends the extended public key or a filter of all the addresses to the central server, then the server can COMPLETELY deanonymize the users.
       Wasabi's solution
       Full node by default & block filters over Tor
      Wasabi checks if there is a local Tor instance installed, and if so, it uses this to onion-route all the traffic to and from the network. If Tor is not already installed, then it is accessed automatically from within Wasabi. This means that by default, all network communication is secured from outside snooping and the IP address is hidden.
      In order to fully verify everything, running a full node is essential. If bitcoindopen in new window is installed and run on the same computer as Wasabi, then it will automatically and by default connect to the full node. It is also possible to connect Wasabi to a remote full node on another computer by specifying the local IP address or Tor onion service in the settings. Then, Wasabi pulls the verified blocks and queries the mempool from the full node.
      Wasabi ships with Bitcoin Knots!
      Wasabi has a partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.
      However, even if no full node is installed, Wasabi has a light client mode based on BIP 158 block filtersopen in new window. The Wasabi server sends a filter of all the transactions in each block to all the users. Then, users check locally if the block contains any transactions with their addresses. If not, then the filter is stored for later reference, and no block is downloaded. However, if there is a user transaction in that block, then Wasabi connects to a random Bitcoin P2P node over Tor and asks for this entire block, not only one transaction. This block request is indistinguishable from the regular P2P gossip, and thus nobody, neither the server nor the full node, know which addresses belong to the user.
      Privacy by default!
      Wasabi has network-level privacy as good as a Bitcoin full node.
       In-depth comparison
      Furthermore, network-level privacy consists of two sub-categories.
      • Private UTXO Retrieval
      • Private Transaction Broadcasting
       Bitcoin Core
       Private UTXO retrieval
      Bitcoin Core downloads all the blocks ever created and establishes your wallet balances locally. This is as good as it gets.
       Private transaction broadcasting
      Bitcoin Core broadcasts transactions to other peers on the clearnet, unencrypted. Other peers cannot figure out which transaction originates from a specific node because Core does not only broadcast its own transactions but also propagates every other transaction that hits its mempool. However, some papers note it’s not bulletproof:
      Bitcoin transaction propagation does not hide the source of a transaction very well, especially against a “supernode” eavesdropper that forms a large number of outgoing connections to reachable nodes on the network. Dandelion: Privacy-Preserving Transaction Propagationopen in new window.
       Adversaries identified
      • Malicious Peer
      • Supernode
       Bitcoin Core + Tor
      You can use Bitcoin Core with Tor, which solves some of the above-mentioned issues. In this case, a supernode cannot track back transactions to your IP address.
      An entity that can break Tor is a universal adversary, however, most Tor attacks are not possible if exit nodes are not involved. It is reasonable to assume that this entity can break the onion routing, not Tor's encryption itself.
       Adversaries identified
      • Tor breaker
       Wasabi Wallet light node
       Private UTXO retrieval
      The backend server serves block filters to all the clients over Tor. From those filters, the clients figure out which blocks they are interested in and download them [and some false positive blocks] from peers. One block per peer, and always over a fresh Tor stream. When a block is acquired, the peer gets disconnected. Because of the end-to-end encryption of the onion network, it immediately defeats an ISP adversary and makes the already impossible job of the Sybil adversary even more impossible. The only adversary that could possibly overcome this would have to setup thousands of full nodes over Tor and also break Tor itself.
       Private transaction broadcasting
      All Wasabi traffic is tunneled through Tor. Wasabi connects only to onion nodes, so end-to-end encryption is enforced between the wallet and peers. All this without involving any exit node. Wasabi connects to each peer through a different Tor stream. A new Bitcoin peer is chosen for every transaction broadcast.
      Everything over Tor!
      Wasabi broadcast transactions to only one peer over Tor, and immediately after that the peer is disconnected.
       Adversaries identified
      • ISP
      • Tor Breaker Sybil Attacker With Thousands Of Full Nodes Over Onion
       Wasabi Wallet + full node
      TIP
      Wasabi has a partial Bitcoin Knots integration. This means that it is possible (but not mandatory) to start Bitcoin Knots during the launch of Wasabi, without having to install or configure anything manually.
       Private UTXO retrieval
      If you have a listening full node running in the background (not only Bitcoin Core, any full node) then Wasabi automatically picks it up and instead of asking peers for blocks, it asks for blocks from your own node. Using Wasabi this way results in the same privacy model as Bitcoin Core's, regarding Private UTXO Retrieval.
       Private transaction broadcasting
      Even when Wasabi is connected to your own node, it will broadcast the transaction in the above-described way: to one new peer over Tor.
       Universal Attacks
      Every time you use software that interacts with a Bitcoin network, and especially a Bitcoin node, you leave a sticky fingerprint in your traffic. It comes in the form of a small but unavoidable spike in volume every time a new block is mined and the nodes start gossiping about it. The blocks in Bitcoin are quite big, and the propagation speed is critical for consensus (greater delay means more frequent accidental forks), so such effect is predictable, and, in a sense, inherent to the Bitcoin architecture.
      Notably, the volume of block-related messages was drastically reduced since the introduction of Compact Block Relay (BIP 152open in new window. Instead of requesting whole blocks, mostly consisting of transactions already known to the node, the peer informed of a new block is only requesting the missing transactions. Yet the amount of extra communications in the seconds following a new block is still considerable. This effect may not be noticeable for a single block, but over time it gets statistically significant and may get exploited.
      As reported by Niko Kudriastev and Michael Maltsevopen in new window, it is possible to detect Bitcoin communications using nothing but traffic volume over time - a piece of information even most privacy concerned individuals are likely leaking to their law-abiding Internet Service Provider. In this case, using a VPN and running the node over Tor may not be enough to avoid being detected.
       Protection
      There are many ways to go about it, but staying completely undetected is far from trivial - traditional privacy-enhancing tools mostly focus on the packet level, which is orthogonal to the technique. Let’s break down the potential defense vectors.
      • VPN / Tor - unlikely to affect the time series shape much, and therefore for larger traffic lengths the statistical significance of block-related spikes will inevitably become overwhelming.
      • Traffic mixing - for traffic volumes that are orders of magnitude higher than Bitcoin P2P communications, mixing is likely to be very effective. That would, however, demand constant shielding of both upstream and downstream communications, and couldn't be done effectively by just running the node on a general-purpose machine - any noticeably long unshielded period may be enough for detection.
      • Being your own ISP - too spicy for most, but that should work.
      • Blockstream Satellite - the ultimate solution. Eliminates the traffic analysis threat altogether.
      Beyond active measures available now, both the privacy and the bandwidth efficiency of Bitcoin communications are actively worked on. It is entirely possible that the messaging protocol will get to the point where block propagation doesn't trigger any significant spikes in traffic volume.
      You can read more about BitSniff hereopen in new window and check the interactive demo hereopen in new window.
      Watch the videoopen in new window
      
-    
+    
   
 
diff --git a/why-wasabi/TransactionGraph.html b/why-wasabi/TransactionGraph.html
index 540904d79b..5890fc3eb8 100644
--- a/why-wasabi/TransactionGraph.html
+++ b/why-wasabi/TransactionGraph.html
@@ -24,10 +24,10 @@
     
     Transaction Graph | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Transaction Graph
       Problem
       Public transaction history
      Because of the input and output model of Bitcoin, there is a chain of digital signatures all the way from the coinbase reward to the current UTXO. This transaction history can reveal sensitive information about the spending patterns of individuals. The receiver of a coin can look back into the transaction history of the sender. And the sender can see the future spending of the receiver.
       Wasabi's Solution
       WabiSabi coinjoins
      In order to obfuscate the link between inputs and outputs, Wasabi uses the WabiSabiopen in new window coinjoin protocol. The Wasabi central coordinator cannot steal and cannot spy, it simply helps many peers to build a huge transaction, with many inputs, and many outputs. The non-private inputs can be linked to their previous transaction history. However, the coinjoin outputs with an anonymity score cannot be tied to the inputs.
      This means that when sending an anonscore coin, the receiver does not know about the transaction history before the coinjoin. And when the receiver does a coinjoin himself, then the sender cannot spy on the later spending patterns. An outside observer can only guess the correct link at a rate of 1 in the anonscore, for example, 1-in-100, or 1%.
      
-    
+    
   
 
diff --git a/why-wasabi/TransactionSurveillanceCompanies.html b/why-wasabi/TransactionSurveillanceCompanies.html
index 2d43cd83f0..0eec0463a6 100644
--- a/why-wasabi/TransactionSurveillanceCompanies.html
+++ b/why-wasabi/TransactionSurveillanceCompanies.html
@@ -24,10 +24,10 @@
     
     Transaction Surveillance Companies | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Transaction Surveillance Companies
      A transaction surveillance company is one that attempts to spy on bitcoin users. Their business model is usually to sell the data to any governments, corporations and individuals willing to pay for their services.
       Spying technology
      There are a number of techniques probably used by transaction surveillance companies:
       AML/KYC information
      Many bitcoin exchanges require users to undergo Anti-Money Laundering (AML) and Know-Your-Customer (KYC) checks, which requires users to reveal all kinds of invasive personal information such as their real name, residence, occupation, net worth and income. All this information is usually passed onto the exchange's partner transaction surveillance company, which keeps a database linking the victim's personal information with their bitcoin addresses and transactions.
       Blockchain analysis
      Bitcoin on-chain transactions are visible to all and so can be analyzed. Important techniques are the common-input-ownership heuristic and address reuse.
       Wallet synchronization analysis
      Bitcoin lightweight wallets often download their own history and balance by querying a third-party server. Transaction surveillance companies often try to exploit this to learn which addresses and transactions belong to certain wallets and IPs. The companies have been known to collect BIP 37open in new window filters from BIP37-enabled wallets. They almost-certainly also run many Electrum servers which can spy on any Electrum wallet that connects to them.
       Transaction broadcasting
      Surveillance companies have been known to sybil and eclipse attack the bitcoin network, and specific nodes, in order to try to find the source IP addresses of unconfirmed transactions.
       Criticisms
       Attempt to invade privacy
      The right to privacy is recognized as a human right, for instance in the US constitution, European Union regulations and the Constitution of India.
      Financial privacy is an essential criteria for the efficient operation of a free market: if you run a business, you cannot effectively set prices if your suppliers and customers can see all your transactions against your will. You cannot compete effectively if your competition is tracking your sales. Individually your informational leverage is lost in your private dealings if you don't have privacy over your accounts: if you pay your landlord in Bitcoin without enough privacy in place, your landlord will see when you've received a pay raise and can hit you up for more rent.
      Financial privacy is essential for personal safety: if thieves can see your income, holdings, and spending, they can use that information to target and exploit you. Without privacy, malicious parties have more ability to steal your identity, snatch your packages from your doorstep, or impersonate businesses you transact with. They also know exactly how much to try to scam you for.
      Financial privacy is essential for human dignity: no one wants the snotty barista at the coffee shop or their nosy neighbors commenting on their income or spending habits. No one wants their baby-crazy in-laws asking why they're buying contraception (or sex toys). Your employer has no business knowing what church you donate to. Only in a perfectly enlightened discrimination-free world where no one has undue authority over anyone else could we retain our dignity and make our lawful transactions freely without self-censorship if we don't have privacy.
      Most importantly, financial privacy isn't incompatible with things like law enforcement or transparency. You can always keep records, be ordered (or volunteer) to provide them to whomever, have judges hold against your interest when you can't produce records (as is the case today). None of this requires globally visible public records.
      Globally visible public records in finance are completely unheard-of. They are undesirable and arguably intolerable. The Bitcoin whitepaper made a promise of how we could get around the visibility of the ledger with pseudonymous addresses, but the ecosystem has broken that promise in a bunch of places and we ought to fix it. Bitcoin could have coded your name or IP address into every transaction. It didn't. The whitepaper even has a section on privacy. Sufficient privacy is an essential prerequisite for a viable digital currency.
       Attempt to destroy fungibility
      Privacy invasions can lead to damaging or destroying bitcoin fungibility. The aim of bitcoin is to be a decentralized digital currency, but if all users are eventually required to consult centralized blacklists before accepting bitcoin, then its decentralization will be destroyed.
      How is financial privacy an essential element to fungibility in Bitcoin?
       No mechanism for oversight or appeal
      There appears to be no recourse for someone affected by false positive identification of exchange-disapproved transaction history. This could result in them wrongly having their coins confiscated.
       Jurisdiction
      Transaction surveillance company market themselves as a tool for finding "bad guys", but it's unclear which jurisdiction that applies to. For example, could one day the government of China pressure those companies into marking certain coins as "bad" because they belong to users who disagree with Chinese government policy?
       Incentivized to oppose bitcoin updates
      During the deployment of segregated witness, certain transaction surveillance companies were believed to have spread misinformation about it, because the update enables Lightning Network. The companies saw it as a threat to their business, since it can enable transacting with bitcoin more privately.
       Oversold effectiveness
      Transaction surveillance companies rely on heuristics or assumptions when analyzing the blockchain. These heuristics are sometimes not true, for example, the common-input-ownership heuristic is broken by CoinJoin. Even if that heuristic is true, it still requires actually identifying the cluster, which is not always possible.
      Laws surrounding anti-money-laundering typically require businesses to make reasonable efforts to investigate the source of funds. Usually, the transaction surveillance company's customers simply want to legally protect themselves, regardless of whether the surveillance actually works. There is a lot of money in this space from governments and other authorities, who usually don't understand the underlying technology and are happy to throw money at several startups who claim to be able to accurately track everything. Whether the activities of transaction surveillance companies actually help against money laundering is an open question.
      image
      According to an excerpt from Chainalysis in their 2021 reportopen in new window, in 2019, criminal activity represented only 2.1% of all cryptocurrency transaction volume.
       Examples
      
-    
+    
   
 
diff --git a/why-wasabi/WhyFinancialPrivacy.html b/why-wasabi/WhyFinancialPrivacy.html
index 6943931731..f9393ac187 100644
--- a/why-wasabi/WhyFinancialPrivacy.html
+++ b/why-wasabi/WhyFinancialPrivacy.html
@@ -24,10 +24,10 @@
     
     Why Financial Privacy is Especially Important | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Why Financial Privacy is Especially Important
      The possibility to be anonymous or pseudonymous relies on you not revealing any identifying information about yourself in connection with the bitcoin addresses you use. If you post your bitcoin address on the web, then you're associating that address and any transactions with it with the name you posted under. If you posted under a handle that you haven't associated with your real identity, then you're still pseudonymous. For greater privacy, it's best to use bitcoin addresses only once.
      By Satoshi Nakamoto in How anonymous are bitcoins? - Bitcointalkopen in new window
      Gaining privacy with Wasabi Wallet for Bitcoin transactions
       Why it is important to keep your funds private
      One of the apparent contradictions of Bitcoin is the notion that your transactions can be private but have a public transaction record.
      As a financial system, Bitcoin functions completely differently from the established banking network. Bitcoin allows you to store funds yourself, without the need for a third party and therefore places the burden on you of keeping said funds secure and accessible.
      While opening an account with a traditional bank or other financial institution requires significant cost and effort, creating a Bitcoin wallet is quick and easy to do on your home computer. This speedy process makes it possible to create hundreds of separate wallets if you wish.
      Two aspects —in particular privacy and identity— function very differently with Bitcoin than in the legacy financial system.
       Pseudonyms protect your identity in Bitcoin
      A bank account, PayPal account, or credit card is always tied to a real identity, making it difficult for many people to open one. Bitcoin doesn't require any identity to be part of this network.
      Being able to use the internet anonymously or pseudonymously is the only way for many people to truly be themselves. Hundreds of millions of people around the globe are not accepted in their societies for reasons they cannot control.
      Maintaining an identity with a large following might require paid services such as blogs, logo designs, stock photos, VPNs, or translations. Without the ability to pay for these services anonymously, you would be forced to reveal your true identity in order to maintain your pseudonym situation. This clearly makes no sense and has potentially dangerous ramifications.
       How Bitcoin empowers anonymity
      Bitcoin is an important, empowering technology. Using Bitcoin protects your right to remain anonymous on the internet. It allows anonymous or pseudonymous fundraising. Groups can collectively control Bitcoin accounts and choose to either hide or reveal financial information at will.
      There are many positive reasons for a private and secure banking system like Bitcoin.
      For example, a workers' rights group could raise funds with Bitcoin. The money could be used for servers, flyers, remote helpers… and all without tying any transaction to the real identities of the volunteers.
      Likewise, a domestic abuse victim might use Bitcoin to securely stack away funds to prepare for an independent life.
       Privacy through pseudonymous accounts
      Privacy in traditional banking is guaranteed by the institutions that make up the system, such as banks, credit card companies, and governments. They (try to) ensure that your bank balance stays a secret. This puts them in a powerful position, where only they have complete oversight as to what is going on.
      In the Bitcoin ecosystem, everyone can see the history and balance of every address, but they cannot necessarily see who controls it. All addresses and transactions are recorded in Bitcoin's publicly distributed database, the blockchain. The addresses do not have names or IP addresses attached to them, so it is not always possible to know which transaction belongs to which individual.
       Threat model
      When considering privacy you need to think about exactly who you're hiding from. You must examine how a hypothetical adversary could spy on you, what kind of information is most important to you and which technology you need to use to protect your privacy. The kind of behaviour needed to protect your privacy therefore depends on your threat model.
      Newcomers to privacy often think that they can simply download some software and all their privacy concerns will be solved. This is not so. Privacy requires a change in behaviour, however slight. For example, imagine if you had a perfectly private internet where who you're communicating with and what you say are completely private. You could still use this to communicate with a social media website to write your real name, upload a selfie and talk about what you're doing right now. Anybody on the internet could view that information so your privacy would be ruined even though you were using perfectly private technology.
      For details read the talk Opsec for Hackers by grugqopen in new window. The talk is aimed mostly at political activists who need privacy from governments, but the advice generally applies to all of us.
      Most of the time plausible deniability is not good enough because lots of spying methods only need to work on a statistical level (e.g. targeted advertising).
      
-    
+    
   
 
diff --git a/why-wasabi/WhyPrivacyImportant.html b/why-wasabi/WhyPrivacyImportant.html
index 804cd7efeb..5c95f36889 100644
--- a/why-wasabi/WhyPrivacyImportant.html
+++ b/why-wasabi/WhyPrivacyImportant.html
@@ -24,10 +24,10 @@
     
     Why Privacy is Important | Wasabi Docs
     
-    
+    
   
   
     
      Wasabi Docs
       Why Privacy is Important
      It's not that I have something to hide. It's that I have nothing to share.
      Privacy is the selective revealing of your Self to your peers. You have many thoughts in your mind which you choose to never tell anyone, and many of your actions are never witnessed by another person. The ability to keep a secret is an essential part of the human experience.
      • Why do you draw the curtains at night?
      • Why do you close the door when in the shower?
      • Why do you send your love letters only to your spouse?
      Watch the videoopen in new window
      Economic trade of goods and services is based on mutual beneficial voluntary action. But when an outside authority demands that the peers reveal the details of their exchange, then they must beg for permission of every act. Yet individuals can use the tools of self-defense at their disposal to regain their sovereignty.
      Without financial privacy, there is no human dignity.
       Privacy? I don't have anything to hide
      Over the last 16 months, as I've debated this issue around the world, every single time somebody has said to me, "I don't really worry about invasions of privacy because I don't have anything to hide." I always say the same thing to them. I get out a pen, I write down my email address. I say, "Here's my email address. What I want you to do when you get home is email me the passwords to all of your email accounts, not just the nice, respectable work one in your name, but all of them, because I want to be able to just troll through what it is you're doing online, read what I want to read and publish whatever I find interesting. After all, if you're not a bad person, if you're doing nothing wrong, you should have nothing to hide." Not a single person has taken me up on that offer. - Glenn Greenwald in Why privacy matters - TED Talkopen in new window
      The primary reason for window curtains in our house, is to stop people from being able to see in. The reason we don’t want them to see in is because we consider much of what we do inside our homes to be private. Whether that be having dinner at the table, watching a movie with your kids, or even engaging in intimate or sexual acts with your partner. None of these things are illegal by any means but even knowing this, we still keep the curtains and blinds on our windows. We clearly have this strong desire for privacy when it comes to our personal life and the public. - Joshua in The Crypto Paperopen in new window
       Read also
       Quotes
      Arguing that you don't care about the right to privacy because you have nothing to hide is no different than saying you don't care about free speech because you have nothing to say. - Edward Snowden on Redditopen in new window
      The NSA has built an infrastructure that allows it to intercept almost everything. With this capability, the vast majority of human communications are automatically ingested without targeting. If I wanted to see your emails or your wife's phone, all I have to do is use intercepts. I can get your emails, passwords, phone records, credit cards. I don't want to live in a society that does these sort of things... I do not want to live in a world where everything I do and say is recorded. That is not something I am willing to support or live under. - Edward Snowden in The Guardianopen in new window
      We all need places where we can go to explore without the judgmental eyes of other people being cast upon us, only in a realm where we're not being watched can we really test the limits of who we want to be. It's really in the private realm where dissent, creativity and personal exploration lie. - Glenn Greenwald in Huffington Postopen in new window
      
-    
+    
   
 
diff --git a/why-wasabi/index.html b/why-wasabi/index.html
index 6c830bbbc0..70f012709a 100644
--- a/why-wasabi/index.html
+++ b/why-wasabi/index.html
@@ -24,10 +24,10 @@
     
     Why Wasabi | Wasabi Docs
     
-    
+    
   
   
     
-    
+