<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://bisq.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=W000000t</id>
	<title>Bisq Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://bisq.wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=W000000t"/>
	<link rel="alternate" type="text/html" href="https://bisq.wiki/Special:Contributions/W000000t"/>
	<updated>2026-05-08T19:40:35Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.34.0</generator>
	<entry>
		<id>https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3186</id>
		<title>Last resort restore</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3186"/>
		<updated>2023-04-10T16:00:45Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Import raw data from backup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful.&lt;br /&gt;
The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation.&lt;br /&gt;
In practical terms, it means that if something goes wrong with this guide and your machine explodes, you were warned and are the sole responsible for the event.&lt;br /&gt;
&lt;br /&gt;
=== Test with a fresh data directory ===&lt;br /&gt;
&lt;br /&gt;
First of all, make sure you have the latest version installed, and Bisq is closed (terminate orphan existing processes if any), then rename your [https://bisq.wiki/Data_directory#Default_locations data directory] by changing &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; to, for example, &amp;lt;code&amp;gt;Bisq.old&amp;lt;/code&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
Start Bisq again: it should start into a 100% new instance, creating a brand new &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; folder (if it doesn't, try uninstalling and then reinstalling Bisq).&amp;lt;br&amp;gt;&lt;br /&gt;
Close Bisq again: we are going to use the freshly created Data Directory as a stump to populate with our old data.&lt;br /&gt;
&lt;br /&gt;
=== Import raw data from backup ===&lt;br /&gt;
&lt;br /&gt;
Open your renamed folder, get into the &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder, and sort files by &amp;quot;last modified&amp;quot; descending, you are looking for those files that were modified most recently, all of them in the same day (presumably the last day your Bisq was operational).&amp;lt;br&amp;gt;&lt;br /&gt;
The list should include:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;&amp;lt;br&amp;gt;BsqSwapTrades&amp;lt;br&amp;gt;&lt;br /&gt;
DisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
RefundDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
SequenceNumberMap&amp;lt;br&amp;gt;&lt;br /&gt;
MyVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
OpenOffers&amp;lt;br&amp;gt;&lt;br /&gt;
MyBlindVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
ClosedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MediationDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
MyProposalList&amp;lt;br&amp;gt;&lt;br /&gt;
MailboxMessageList&amp;lt;br&amp;gt;&lt;br /&gt;
AccountAgeWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
PendingTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyProofOfBurnList&amp;lt;br&amp;gt;&lt;br /&gt;
PreferencesPayload&amp;lt;br&amp;gt;&lt;br /&gt;
UserPayload&amp;lt;br&amp;gt;&lt;br /&gt;
AddressEntryList&amp;lt;br&amp;gt;&lt;br /&gt;
FailedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyReputationList&amp;lt;br&amp;gt;&lt;br /&gt;
TempProposalStore&amp;lt;br&amp;gt;&lt;br /&gt;
NavigationPath&amp;lt;br&amp;gt;&lt;br /&gt;
UnconfirmedBsqChangeOutputList&amp;lt;br&amp;gt;&lt;br /&gt;
IgnoredMailboxMap&amp;lt;br&amp;gt;&lt;br /&gt;
PeerList&amp;lt;br&amp;gt;&lt;br /&gt;
RemovedPayloadsMap&amp;lt;br&amp;gt;&lt;br /&gt;
TradeStatistics3Store&amp;lt;br&amp;gt;&lt;br /&gt;
SignedWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all the above files in the corresponding &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder of your fresh data directory, overwriting the existing ones.&lt;br /&gt;
&lt;br /&gt;
Then, delete from the fresh data directory, and replace with copies from the old directory, the following folders:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;btc_mainnet/keys&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/wallet&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/tor/hiddenservice&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored; if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3185</id>
		<title>Last resort restore</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3185"/>
		<updated>2023-04-10T15:58:24Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful.&lt;br /&gt;
The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation.&lt;br /&gt;
In practical terms, it means that if something goes wrong with this guide and your machine explodes, you were warned and are the sole responsible for the event.&lt;br /&gt;
&lt;br /&gt;
=== Test with a fresh data directory ===&lt;br /&gt;
&lt;br /&gt;
First of all, make sure you have the latest version installed, and Bisq is closed (terminate orphan existing processes if any), then rename your [https://bisq.wiki/Data_directory#Default_locations data directory] by changing &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; to, for example, &amp;lt;code&amp;gt;Bisq.old&amp;lt;/code&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
Start Bisq again: it should start into a 100% new instance, creating a brand new &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; folder (if it doesn't, try uninstalling and then reinstalling Bisq).&amp;lt;br&amp;gt;&lt;br /&gt;
Close Bisq again: we are going to use the freshly created Data Directory as a stump to populate with our old data.&lt;br /&gt;
&lt;br /&gt;
=== Import raw data from backup ===&lt;br /&gt;
&lt;br /&gt;
Open your renamed folder, get into the &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder, and sort files by &amp;quot;last modified&amp;quot; descending, you are looking for those files that were modified most recently, all of them in the same day (presumably the last day your Bisq was operational).&amp;lt;br&amp;gt;&lt;br /&gt;
The list should include:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;BsqSwapTrades&amp;lt;br&amp;gt;&lt;br /&gt;
DisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
RefundDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
SequenceNumberMap&amp;lt;br&amp;gt;&lt;br /&gt;
MyVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
OpenOffers&amp;lt;br&amp;gt;&lt;br /&gt;
MyBlindVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
ClosedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MediationDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
MyProposalList&amp;lt;br&amp;gt;&lt;br /&gt;
MailboxMessageList&amp;lt;br&amp;gt;&lt;br /&gt;
AccountAgeWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
PendingTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyProofOfBurnList&amp;lt;br&amp;gt;&lt;br /&gt;
PreferencesPayload&amp;lt;br&amp;gt;&lt;br /&gt;
UserPayload&amp;lt;br&amp;gt;&lt;br /&gt;
AddressEntryList&amp;lt;br&amp;gt;&lt;br /&gt;
FailedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyReputationList&amp;lt;br&amp;gt;&lt;br /&gt;
TempProposalStore&amp;lt;br&amp;gt;&lt;br /&gt;
NavigationPath&amp;lt;br&amp;gt;&lt;br /&gt;
UnconfirmedBsqChangeOutputList&amp;lt;br&amp;gt;&lt;br /&gt;
IgnoredMailboxMap&amp;lt;br&amp;gt;&lt;br /&gt;
PeerList&amp;lt;br&amp;gt;&lt;br /&gt;
RemovedPayloadsMap&amp;lt;br&amp;gt;&lt;br /&gt;
TradeStatistics3Store&amp;lt;br&amp;gt;&lt;br /&gt;
SignedWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all the above files in the corresponding &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder of your fresh data directory, overwriting the existing ones.&lt;br /&gt;
&lt;br /&gt;
Then, delete from the fresh data directory, and replace with copies from the old direcoty, the following folders:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;btc_mainnet/keys&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/wallet&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/tor/hiddenservice&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored;if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3184</id>
		<title>Last resort restore</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=3184"/>
		<updated>2023-04-10T15:56:08Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Import raw data from backup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful.&lt;br /&gt;
The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation.&lt;br /&gt;
&lt;br /&gt;
=== Test with a fresh data directory ===&lt;br /&gt;
&lt;br /&gt;
First of all, make sure you have the latest version installed, and Bisq is closed (terminate orphan existing processes if any), then rename your [https://bisq.wiki/Data_directory#Default_locations data directory] by changing &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; to, for example, &amp;lt;code&amp;gt;Bisq.old&amp;lt;/code&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
Start Bisq again: it should start into a 100% new instance, creating a brand new &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; folder (if it doesn't, try uninstalling and then reinstalling Bisq).&amp;lt;br&amp;gt;&lt;br /&gt;
Close Bisq again: we are going to use the freshly created Data Directory as a stump to populate with our old data.&lt;br /&gt;
&lt;br /&gt;
=== Import raw data from backup ===&lt;br /&gt;
&lt;br /&gt;
Open your renamed folder, get into the &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder, and sort files by &amp;quot;last modified&amp;quot; descending, you are looking for those files that were modified most recently, all of them in the same day (presumably the last day your Bisq was operational).&amp;lt;br&amp;gt;&lt;br /&gt;
The list should include:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;BsqSwapTrades&amp;lt;br&amp;gt;&lt;br /&gt;
DisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
RefundDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
SequenceNumberMap&amp;lt;br&amp;gt;&lt;br /&gt;
MyVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
OpenOffers&amp;lt;br&amp;gt;&lt;br /&gt;
MyBlindVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
ClosedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MediationDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
MyProposalList&amp;lt;br&amp;gt;&lt;br /&gt;
MailboxMessageList&amp;lt;br&amp;gt;&lt;br /&gt;
AccountAgeWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
PendingTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyProofOfBurnList&amp;lt;br&amp;gt;&lt;br /&gt;
PreferencesPayload&amp;lt;br&amp;gt;&lt;br /&gt;
UserPayload&amp;lt;br&amp;gt;&lt;br /&gt;
AddressEntryList&amp;lt;br&amp;gt;&lt;br /&gt;
FailedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyReputationList&amp;lt;br&amp;gt;&lt;br /&gt;
TempProposalStore&amp;lt;br&amp;gt;&lt;br /&gt;
NavigationPath&amp;lt;br&amp;gt;&lt;br /&gt;
UnconfirmedBsqChangeOutputList&amp;lt;br&amp;gt;&lt;br /&gt;
IgnoredMailboxMap&amp;lt;br&amp;gt;&lt;br /&gt;
PeerList&amp;lt;br&amp;gt;&lt;br /&gt;
RemovedPayloadsMap&amp;lt;br&amp;gt;&lt;br /&gt;
TradeStatistics3Store&amp;lt;br&amp;gt;&lt;br /&gt;
SignedWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all the above files in the corresponding &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder of your fresh data directory, overwriting the existing ones.&lt;br /&gt;
&lt;br /&gt;
Then, delete from the fresh data directory, and replace with copies from the old direcoty, the following folders:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;btc_mainnet/keys&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/wallet&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/tor/hiddenservice&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored;if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3183</id>
		<title>Connecting to your own Bitcoin node</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3183"/>
		<updated>2023-03-29T16:19:47Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* General node settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq will '''connect to your local Bitcoin node''' if it finds it upon starting up. This article contains the requirements for this to work correctly.&lt;br /&gt;
&lt;br /&gt;
You can also specify the addresses of particular Bitcoin nodes in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= General node settings =&lt;br /&gt;
&lt;br /&gt;
The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;server=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;pruned=0&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;peerbloomfilters=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which in turn:&lt;br /&gt;
* enable the block server mode&lt;br /&gt;
* disable the pruning of old blocks&lt;br /&gt;
* allow Bisq to run its SPV wallet&lt;br /&gt;
&lt;br /&gt;
Multiple reports have been received, where any declination of the Ronin node just won't work, or will work once, only to stop working after the next reboot, requiring a restore to network provided nodes. We are not able to suggest a workaround, except involving Ronin support.&lt;br /&gt;
&lt;br /&gt;
= Connecting to a local Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or &amp;lt;code&amp;gt;bitcoind&amp;lt;/code&amp;gt; running on &amp;lt;code&amp;gt;localhost&amp;lt;/code&amp;gt; on port 8333.&lt;br /&gt;
&lt;br /&gt;
Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.&lt;br /&gt;
&lt;br /&gt;
= Connecting to another Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
By default, Bisq maximizes your privacy by connecting to nodes run by trusted  Bisq contributors. &lt;br /&gt;
&lt;br /&gt;
If you'd like to connect to another node, you can specify its address in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;. Bisq will validate the address and connect to the specified node the next time it starts.&lt;br /&gt;
&lt;br /&gt;
Bisq supports connecting to Bitcoin nodes with Tor v3 addresses: this is the easiest path to take, since you only have to fill in your node's onion address in settings.&amp;lt;br&amp;gt;&lt;br /&gt;
If your node is on your local network, connecting directly to it rather than using Tor would reduce latency by a sensible degree. In order to do this:&lt;br /&gt;
* make sure the node's firewall allows incoming connections on port 8333 from the local network&lt;br /&gt;
* have Bitcoin daemon listen to &amp;lt;code&amp;gt;0.0.0.0&amp;lt;/code&amp;gt; rather than &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt; (add a line that says &amp;lt;code&amp;gt;bind 0.0.0.0&amp;lt;/code&amp;gt;)&lt;br /&gt;
* uncheck &amp;quot;Use Tor for Bitcoin network&amp;quot; under Settings&amp;gt;Network in Bisq application&lt;br /&gt;
* fill in your node's local network &amp;lt;code&amp;gt;ipaddress:8333&amp;lt;/code&amp;gt; in &amp;quot;Use custom bitcoin Core nodes&amp;quot; field&lt;br /&gt;
&lt;br /&gt;
Explaining in detail each step of the above goes past the scope of this guide, yet you can usually find more information either by searching for specific guides, or asking on discussion boards/groups.&lt;br /&gt;
&lt;br /&gt;
= Troubleshooting =&lt;br /&gt;
&lt;br /&gt;
If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows.  &lt;br /&gt;
&lt;br /&gt;
For MacOS:&lt;br /&gt;
 &amp;lt;code&amp;gt;Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
For Linux:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt; cd /opt/bisq/bin&lt;br /&gt;
&lt;br /&gt;
./Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/7c07cdb6ff60ad1186dea33acdfb688668c2aae6/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L76 here in the Bisq code]. &lt;br /&gt;
&lt;br /&gt;
[[Running_from_the_command_line|More info on running from the command line]].&lt;br /&gt;
&lt;br /&gt;
[[Command_line_options|More info on command line options]].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Trading_fees&amp;diff=3182</id>
		<title>Trading fees</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Trading_fees&amp;diff=3182"/>
		<updated>2023-03-25T23:09:06Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Current rates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Trading fees''' are paid to fund the [[DAO | Bisq DAO]] when making or taking an offer. Fees can be paid in BSQ or BTC. &lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Getting a discount ==&lt;br /&gt;
&lt;br /&gt;
Bisq encourages traders to use [[BSQ]] by offering a discount of approximately 50%. This discount fluctuates as the BSQ/BTC rate fluctuates. To maintain the 50% discount target, trading fees are [[update BSQ trading fees | updated]] every cycle as necessary.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|If you're interested in using BSQ to pay trading fees, [[Paying_trading_fees_with_BSQ#Acquire_BSQ|see this article for instructions]].}}&lt;br /&gt;
&lt;br /&gt;
== Current rates ==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;width: 250px;&amp;quot;&lt;br /&gt;
|+ Trading Fees per 1 BTC&lt;br /&gt;
|-&lt;br /&gt;
!&lt;br /&gt;
!BTC&lt;br /&gt;
!BSQ&lt;br /&gt;
|-&lt;br /&gt;
!Maker&lt;br /&gt;
|0.001&lt;br /&gt;
|14.29&lt;br /&gt;
|-&lt;br /&gt;
!Taker&lt;br /&gt;
|0.01&lt;br /&gt;
|142.94&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Combined BTC trading fee rate is 1.1% (0.1% by maker and 1% by taker). Absolute minimum fee to avoid dust is 0.00005 BTC.&lt;br /&gt;
&lt;br /&gt;
Combined BSQ trading fee rate is targeted at 0.55% (0.05% by maker and 0.5% by taker). Absolute minimum fee to avoid dust is 0.03 BSQ.&lt;br /&gt;
&lt;br /&gt;
Trading fee rates and absolute minimums are DAO parameters that [[Proposals|must be proposed]] and approved through DAO voting in order to take effect. BTC fee rates tend to stay constant, but BSQ rates are [[Updating_BSQ_trading_fees|adjusted every cycle]] to account for BSQ rate fluctuation.&lt;br /&gt;
&lt;br /&gt;
== Selecting how to pay ==&lt;br /&gt;
&lt;br /&gt;
Traders choose how they'd prefer to pay trading fees while making or taking an offer. BSQ and BTC amounts (and fiat equivalents) are shown.&lt;br /&gt;
&lt;br /&gt;
[[File:Pick-trade-fee-currency.png|600px|thumb|left|Pick how to pay trade fees on this screen while making or taking an offer.]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear: both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Features]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=3180</id>
		<title>Running Bisq on Tails</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=3180"/>
		<updated>2023-03-10T09:16:44Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Persistent Data Directory */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To '''run Bisq on the Tails OS''', a few manual steps are required.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Preparations ==&lt;br /&gt;
&lt;br /&gt;
* Configure an [https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/ administration password]&lt;br /&gt;
* Configure [https://tails.boum.org/doc/first_steps/persistence/index.en.html persistence]&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|Tails does not persist user data by default. Even with persistence enabled, '''all data in Bisq's default [[data directory]] will be erased as soon as you reboot'''. This means you will lose your Bisq keys, wallet data, and everything else.&lt;br /&gt;
&lt;br /&gt;
To avoid data loss, make sure that persistence is enabled, and that Bisq user data is stored in a persistent directory before shutting down Tails.}}&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
&lt;br /&gt;
After restarting Tails, go to https://github.com/bisq-network/bisq/releases using your Tor Browser and download the &amp;lt;code&amp;gt;Bisq-64bit-[version].deb&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; files.&lt;br /&gt;
&lt;br /&gt;
You may have to use &amp;lt;code&amp;gt;wget&amp;lt;/code&amp;gt;, because &amp;lt;code&amp;gt;curl&amp;lt;/code&amp;gt; may not use Tor and could be blocked from using the internet.&lt;br /&gt;
&lt;br /&gt;
=== Verify your download ===&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;wget &amp;lt;nowiki&amp;gt;https://bisq.network/pubkey/[keyid].asc&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; should result in a file &amp;lt;code&amp;gt;[keyid].asc&amp;lt;/code&amp;gt; in your working directory. See &amp;quot;Verification&amp;quot; section of [https://github.com/bisq-network/bisq/releases/latest release notes] for the exact key ID you should use (it's &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; as of this writing) to verify your download.&lt;br /&gt;
* Import the key to gpg by &amp;lt;code&amp;gt;gpg --import [keyid].asc&amp;lt;/code&amp;gt;&lt;br /&gt;
* Check the signature with &amp;lt;code&amp;gt;gpg --digest-algo SHA256 --verify [yourbinaryhere]{.asc*,}&amp;lt;/code&amp;gt; which should give you something like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[snip]&lt;br /&gt;
gpg: Good signature from &amp;quot;Christoph Atteneder...&lt;br /&gt;
[snip]&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
&lt;br /&gt;
Do a simple &amp;lt;code&amp;gt;sudo dpkg -i [yourbinaryhere]&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Configure ===&lt;br /&gt;
&lt;br /&gt;
* Make authcookie readable:&lt;br /&gt;
&amp;lt;code&amp;gt;sudo chmod o+r /var/run/tor/control.authcookie&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Create a file &amp;lt;code&amp;gt;/etc/onion-grater.d/bisq.yml&amp;lt;/code&amp;gt; with contents:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then restart the &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt; service with &amp;lt;code&amp;gt;sudo systemctl restart onion-grater.service&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* In &amp;lt;code&amp;gt;/usr/share/applications/Bisq.desktop&amp;lt;/code&amp;gt;, replace:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;Exec=/opt/bisq/bin/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Persistent Data Directory ==&lt;br /&gt;
&lt;br /&gt;
Tails will delete all new files when shutting down, unless they are in a persistent storage location.&lt;br /&gt;
&lt;br /&gt;
First, move the Bisq binary you downloaded to a persistent directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir /home/amnesia/Persistent/bisq/&lt;br /&gt;
&lt;br /&gt;
mv /path/to/[yourbinaryhere] /home/amnesia/Persistent/bisq/&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, link Bisq's default [[data directory]] to a persistent data directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir /home/amnesia/Persistent/bisq/Bisq/&lt;br /&gt;
&lt;br /&gt;
ln -s /home/amnesia/Persistent/bisq/Bisq /home/amnesia/.local/share/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Existing user ===&lt;br /&gt;
&lt;br /&gt;
To import user data from another Bisq installation or backup, copy it to the persistent data directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cp -r /[yourdirectoryhere]/Bisq/* /home/amnesia/Persistent/bisq/Bisq/&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
N.B. In this example, the correct path to your &amp;lt;code&amp;gt;btc_mainnet&amp;lt;/code&amp;gt; directory should be:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/home/amnesia/Persistent/bisq/Bisq/btc_mainnet&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Run Bisq ==&lt;br /&gt;
&lt;br /&gt;
Click &amp;lt;code&amp;gt;Applications&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Internet&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Or via terminal:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation Script ==&lt;br /&gt;
&lt;br /&gt;
Because Tails doesn't persist the Bisq installation [https://bisq.wiki/Running_Bisq_on_Tails#Install_Bisq] or configuration [https://bisq.wiki/Running_Bisq_on_Tails#Configure], they must be repeated after every restart. To make life easier, you can automate this in a bash script. Make sure the script is saved somewhere in the Tails persistent directory.&lt;br /&gt;
&lt;br /&gt;
* Create script file:&lt;br /&gt;
&amp;lt;code&amp;gt;touch ~/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Make script executable:&lt;br /&gt;
&amp;lt;code&amp;gt;chmod +x ~/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Edit and save file: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
dpkg -i /home/amnesia/Persistent/bisq/[yourbinaryhere]&lt;br /&gt;
echo &amp;quot;Change access rights of /var/run/tor/control.authcookie ...&amp;quot;&lt;br /&gt;
chmod o+r /var/run/tor/control.authcookie&lt;br /&gt;
echo &amp;quot;Create /etc/onion-grater.d/bisq.yml ...&amp;quot;&lt;br /&gt;
echo &amp;quot;---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&amp;quot; &amp;gt; /etc/onion-grater.d/bisq.yml&lt;br /&gt;
echo &amp;quot;Restart onion-grater service ...&amp;quot;&lt;br /&gt;
systemctl restart onion-grater.service&lt;br /&gt;
echo &amp;quot;Edit Bisq executable file ...&amp;quot;&lt;br /&gt;
sed -i 's+Exec=/opt/bisq/bin/Bisq+Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth+' /usr/share/applications/bisq-Bisq.desktop&lt;br /&gt;
ln -s /home/amnesia/Persistent/bisq/Bisq /home/amnesia/.local/share/Bisq&lt;br /&gt;
echo &amp;quot;Bisq installed successfully.&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now you can run this script to install and configure Bisq after a Tails restart:&lt;br /&gt;
&amp;lt;code&amp;gt;sudo /home/amnesia/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Guides]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=3173</id>
		<title>Running Bisq on Tails</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=3173"/>
		<updated>2023-03-01T17:21:18Z</updated>

		<summary type="html">&lt;p&gt;W000000t: uploaded changes by HeadsAndTails from bisq.community&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To '''run Bisq on the Tails OS''', a few manual steps are required.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Preparations ==&lt;br /&gt;
&lt;br /&gt;
* Configure an [https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/ administration password]&lt;br /&gt;
* Configure [https://tails.boum.org/doc/first_steps/persistence/index.en.html persistence]&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|Tails does not persist user data by default. Even with persistence enabled, '''all data in Bisq's default [[data directory]] will be erased as soon as you reboot'''. This means you will lose your Bisq keys, wallet data, and everything else.&lt;br /&gt;
&lt;br /&gt;
To avoid data loss, make sure that persistence is enabled, and that Bisq user data is stored in a persistent directory before shutting down Tails.}}&lt;br /&gt;
&lt;br /&gt;
== Download ==&lt;br /&gt;
&lt;br /&gt;
After restarting Tails, go to https://github.com/bisq-network/bisq/releases using your Tor Browser and download the &amp;lt;code&amp;gt;Bisq-64bit-[version].deb&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; files.&lt;br /&gt;
&lt;br /&gt;
You may have to use &amp;lt;code&amp;gt;wget&amp;lt;/code&amp;gt;, because &amp;lt;code&amp;gt;curl&amp;lt;/code&amp;gt; may not use Tor and could be blocked from using the internet.&lt;br /&gt;
&lt;br /&gt;
=== Verify your download ===&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;wget &amp;lt;nowiki&amp;gt;https://bisq.network/pubkey/[keyid].asc&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; should result in a file &amp;lt;code&amp;gt;[keyid].asc&amp;lt;/code&amp;gt; in your working directory. See &amp;quot;Verification&amp;quot; section of [https://github.com/bisq-network/bisq/releases/latest release notes] for the exact key ID you should use (it's &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; as of this writing) to verify your download.&lt;br /&gt;
* Import the key to gpg by &amp;lt;code&amp;gt;gpg --import [keyid].asc&amp;lt;/code&amp;gt;&lt;br /&gt;
* Check the signature with &amp;lt;code&amp;gt;gpg --digest-algo SHA256 --verify [yourbinaryhere]{.asc*,}&amp;lt;/code&amp;gt; which should give you something like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[snip]&lt;br /&gt;
gpg: Good signature from &amp;quot;Christoph Atteneder...&lt;br /&gt;
[snip]&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
&lt;br /&gt;
Do a simple &amp;lt;code&amp;gt;sudo dpkg -i [yourbinaryhere]&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Configure ===&lt;br /&gt;
&lt;br /&gt;
* Make authcookie readable:&lt;br /&gt;
&amp;lt;code&amp;gt;sudo chmod o+r /var/run/tor/control.authcookie&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Create a file &amp;lt;code&amp;gt;/etc/onion-grater.d/bisq.yml&amp;lt;/code&amp;gt; with contents:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then restart the &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt; service with &amp;lt;code&amp;gt;sudo systemctl restart onion-grater.service&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* In &amp;lt;code&amp;gt;/usr/share/applications/Bisq.desktop&amp;lt;/code&amp;gt;, replace:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;Exec=/opt/bisq/bin/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Persistent Data Directory ==&lt;br /&gt;
&lt;br /&gt;
Tails will delete all new files when shutting down, unless they are in a persistent storage location.&lt;br /&gt;
&lt;br /&gt;
First, move the Bisq binary you downloaded to a persistent directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir /home/amnesia/Persistent/bisq/&lt;br /&gt;
mv /path/to/[yourbinaryhere] /home/amnesia/Persistent/bisq/&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, link Bisq's default [[data directory]] to a persistent data directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;mkdir /home/amnesia/Persistent/bisq/Bisq/&lt;br /&gt;
ln -s /home/amnesia/Persistent/bisq/Bisq /home/amnesia/.local/share/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Existing user ===&lt;br /&gt;
&lt;br /&gt;
To import user data from another Bisq installation or backup, copy it to the persistent data directory:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;cp -r /[yourdirectoryhere]/Bisq/* /home/amnesia/Persistent/bisq/Bisq/&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
N.B. In this example, the correct path to your &amp;lt;code&amp;gt;btc_mainnet&amp;lt;/code&amp;gt; directory should be:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/home/amnesia/Persistent/bisq/Bisq/btc_mainnet&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Run Bisq ==&lt;br /&gt;
&lt;br /&gt;
Click &amp;lt;code&amp;gt;Applications&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Internet&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Or via terminal:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Installation Script ==&lt;br /&gt;
&lt;br /&gt;
Because Tails doesn't persist the Bisq installation [https://bisq.wiki/Running_Bisq_on_Tails#Install_Bisq] or configuration [https://bisq.wiki/Running_Bisq_on_Tails#Configure], they must be repeated after every restart. To make life easier, you can automate this in a bash script. Make sure the script is saved somewhere in the Tails persistent directory.&lt;br /&gt;
&lt;br /&gt;
* Create script file:&lt;br /&gt;
&amp;lt;code&amp;gt;touch ~/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Make script executable:&lt;br /&gt;
&amp;lt;code&amp;gt;chmod +x ~/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Edit and save file: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
dpkg -i /home/amnesia/Persistent/bisq/[yourbinaryhere]&lt;br /&gt;
echo &amp;quot;Change access rights of /var/run/tor/control.authcookie ...&amp;quot;&lt;br /&gt;
chmod o+r /var/run/tor/control.authcookie&lt;br /&gt;
echo &amp;quot;Create /etc/onion-grater.d/bisq.yml ...&amp;quot;&lt;br /&gt;
echo &amp;quot;---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&amp;quot; &amp;gt; /etc/onion-grater.d/bisq.yml&lt;br /&gt;
echo &amp;quot;Restart onion-grater service ...&amp;quot;&lt;br /&gt;
systemctl restart onion-grater.service&lt;br /&gt;
echo &amp;quot;Edit Bisq executable file ...&amp;quot;&lt;br /&gt;
sed -i 's+Exec=/opt/bisq/bin/Bisq+Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth+' /usr/share/applications/bisq-Bisq.desktop&lt;br /&gt;
ln -s /home/amnesia/Persistent/bisq/Bisq /home/amnesia/.local/share/Bisq&lt;br /&gt;
echo &amp;quot;Bisq installed successfully.&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now you can run this script to install and configure Bisq after a Tails restart:&lt;br /&gt;
&amp;lt;code&amp;gt;sudo /home/amnesia/Persistent/bisq/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Guides]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3161</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3161"/>
		<updated>2023-02-03T14:51:52Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Steps for accounts setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
* run Tor Browser (ignore the error about restarting Tor if there is another Tor Browser open, as they will try to bind the same ports, returning an error, and close the popup) and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time (this will run a dedicated Tor circuit builder for your Bisq activity)&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it) &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor) and from the one reported from any other Tor Browser you maybe already have on the system&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays within your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disable cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, and under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location. Even if you don't disable mic access, the microphone will still be unavailable during web calls, because of a compile-time setting of Tor Browser.&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's threat model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you maybe have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account,  registering at https://bisq.community is needed to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3160</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3160"/>
		<updated>2023-02-03T14:48:01Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Known issues and warnings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
* run Tor Browser (ignore the error about restarting Tor if there is another Tor Browser open, as they will try to bind the same ports, returning an error, and close the popup) and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time (this will run a dedicated Tor circuit builder for your Bisq activity)&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it) &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor) and from the one reported from any other Tor Browser you maybe already have on the system&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays within your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disable cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, and under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location. Even if you don't disable mic access, the microphone will still be unavailable during web calls, because of a compile-time setting of Tor Browser.&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's threat model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you maybe have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3159</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3159"/>
		<updated>2023-02-03T14:46:04Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Steps for base setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
* run Tor Browser (ignore the error about restarting Tor if there is another Tor Browser open, as they will try to bind the same ports, returning an error, and close the popup) and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time (this will run a dedicated Tor circuit builder for your Bisq activity)&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it) &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor) and from the one reported from any other Tor Browser you maybe already have on the system&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays within your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disable cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, and under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location. Even if you don't disable mic access, the microphone will still be unavailable during web calls, because of a compile-time setting of Tor Browser.&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3158</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3158"/>
		<updated>2023-02-03T14:38:18Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Steps for base setup */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
* run Tor Browser (ignore the error about restarting Tor if there is another Tor Browser open, as they will try to bind the same ports, returning an error, and close the popup) and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time (this will run a dedicated Tor circuit builder for your Bisq activity)&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it) &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor) and from the one reported from any other Tor Browser you maybe already have on the system&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays within your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3157</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3157"/>
		<updated>2023-02-03T14:37:22Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
* run Tor Browser (ignore the error about restarting Tor if there is another Tor Browser open, as they will try to bind the same ports, returning an error, and close the popup) and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time (this will run a dedicated Tor circuit builder for your Bisq activity)&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it) &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor) and from the one reported from any other Tor Browser you maybe already have on the system&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3156</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3156"/>
		<updated>2023-02-03T14:29:30Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
&lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it (right after this, it's a good time to enable the automatic connection, which means Tor Browser will build a Tor circuit right after you start it)&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Command_line_options&amp;diff=3131</id>
		<title>Command line options</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Command_line_options&amp;diff=3131"/>
		<updated>2023-01-26T21:48:02Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Dump delayed payout transactions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Specifying '''command line options''' can enable additional non-default settings when [[Running_from_the_command_line|running Bisq from the command line]].&lt;br /&gt;
&lt;br /&gt;
See a full list of available options [https://github.com/bisq-network/bisq/blob/master/common/src/main/java/bisq/common/config/Config.java#L57 in the code]. This article covers more notable ones for typical use cases.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Specify a different data directory ==&lt;br /&gt;
&lt;br /&gt;
The default data directory Bisq uses is called &amp;quot;Bisq&amp;quot;. All Bisq data is fully contained in it. The [[Data_directory#Default_locations|default path]] of this data directory varies based on your operating system. To change the default path too, [[#Specify_a_different_data_directory_path|see below]].&lt;br /&gt;
&lt;br /&gt;
You can specify a different data directory with &amp;lt;code&amp;gt;--appData=BisqTest&amp;lt;/code&amp;gt; (change &amp;quot;BisqTest&amp;quot; to whatever you want; &amp;quot;Bisq&amp;quot; is the default) and Bisq will create a brand new data directory in the [[Data_directory#Default_locations|default path]] with a new wallet, keys, onion address, etc (or use the existing data directory with that name if it's already there).&lt;br /&gt;
&lt;br /&gt;
You can use this option to run more than one instance of Bisq at once, which can be helpful to send funds from one Bisq instance to another when [[Switching_to_a_new_data_directory#Send_funds|switching to a new data directory]].&lt;br /&gt;
&lt;br /&gt;
[[#Include_command-line_options_by_default|See below]] for a suggestion on including this option automatically without having to specify it every time.&lt;br /&gt;
&lt;br /&gt;
== Specify a different data directory path ==&lt;br /&gt;
&lt;br /&gt;
If you'd like to change the default path for the data directory altogether (e.g. to store the data directory on another drive), run Bisq with &amp;lt;code&amp;gt;--appDataDir=/external/hard/drive/path&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[#Include_command-line_options_by_default|See below]] for a suggestion on including this option automatically without having to specify it every time.&lt;br /&gt;
&lt;br /&gt;
== Dump delayed payout transactions ==&lt;br /&gt;
&lt;br /&gt;
Add the &amp;lt;code&amp;gt;--dumpDelayedPayoutTxs=true&amp;lt;/code&amp;gt; option to dump delayed payout transactions in the following files in your data directory, inside the &amp;lt;code&amp;gt;db&amp;lt;/code&amp;gt; folder:&lt;br /&gt;
&lt;br /&gt;
# delayed_payout_txs_closed.json&lt;br /&gt;
# delayed_payout_txs_pending.json&lt;br /&gt;
# delayed_payout_txs_failed.json&lt;br /&gt;
&lt;br /&gt;
== Specify a Bitcoin node ==&lt;br /&gt;
&lt;br /&gt;
Sometimes Bisq cannot connect to the node specified in the interface at &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;, so starting Bisq with &amp;lt;code&amp;gt;--btcNodes=&amp;lt;node address&amp;gt;&amp;lt;/code&amp;gt; can help.&lt;br /&gt;
&lt;br /&gt;
[[#Include_command-line_options_by_default|See below]] for a suggestion on including this option automatically without having to specify it every time.&lt;br /&gt;
&lt;br /&gt;
== See all Bisq trades ==&lt;br /&gt;
&lt;br /&gt;
See all Bisq trades by running the &amp;lt;code&amp;gt;--dumpStatistics=true&amp;lt;/code&amp;gt; option. Then check out &amp;lt;code&amp;gt;btc_mainnet/db/trade_statistics.json&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
[[#Include_command-line_options_by_default|See below]] for a suggestion on including this option automatically without having to specify it every time.&lt;br /&gt;
&lt;br /&gt;
== Include command-line options by default ==&lt;br /&gt;
&lt;br /&gt;
If there are certain options you'd like to include every time you start Bisq, you can make a script that specifies them for you. &lt;br /&gt;
&lt;br /&gt;
For example, this script specifies an alternative data directory path on macOS:&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 &lt;br /&gt;
 /Applications/Bisq.app/Contents/MacOS/Bisq --appDataDir=/external/hard/drive/path&lt;br /&gt;
&lt;br /&gt;
Replace the Bisq executable path above with the [[Running_from_the_command_line|one for your operating system]] and specify the options you want to include. Then put the script somewhere in your system path so you can easily call it.&lt;br /&gt;
&lt;br /&gt;
Optionally, consider making a dummy directory in the default location to prevent Bisq from accidentally launching in its default mode. To do this, create a directory named &amp;quot;Bisq&amp;quot; in the default [[Data_directory#Default_locations|data directory path]] for your operating system without any permissions.&lt;br /&gt;
&lt;br /&gt;
For example, on macOS:&lt;br /&gt;
&lt;br /&gt;
 $ cd ~/Library/Application\ Support/&lt;br /&gt;
 $ mkdir Bisq&lt;br /&gt;
 $ chmod 000 Bisq&lt;br /&gt;
&lt;br /&gt;
In this way, since the system won't have write access in the default location, launching Bisq normally will fail, reminding you to launch Bisq with your script.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Failed_Trades_-_Reimbursement_of_Trade_Fees_and_Miner_Fees&amp;diff=3125</id>
		<title>Failed Trades - Reimbursement of Trade Fees and Miner Fees</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Failed_Trades_-_Reimbursement_of_Trade_Fees_and_Miner_Fees&amp;diff=3125"/>
		<updated>2023-01-21T19:34:33Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sometimes trades on Bisq fail because of bugs or edge situations, that lead to an invalid deposit transaction: either no deposit txid exists, or the txid is missing from the blockchain (as can be verified on a blockchain explorer).&lt;br /&gt;
&lt;br /&gt;
Usually failed trades will also have an issue with the maker and/or taker txid, caused by an out-of-sync internal Bisq wallet on the party with the failed tx.&lt;br /&gt;
* if miner and trade fees were lost for the BTC buyer and/or seller, a reimbursement can be considered if the lost fees are significant enough, e.g. above $10 of value&lt;br /&gt;
* if no fees were lost, no reimbursement is obviously needed&lt;br /&gt;
* '''no other losses will be caused by a failed trade''', as the deposit tx never happens, so no additional funds will have left your wallet in the first place&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Common reasons for trades to fail ==&lt;br /&gt;
&lt;br /&gt;
The most common reason for a trade to fail is either the maker or taker is trading with an out-of-sync bitcoin wallet.&lt;br /&gt;
&lt;br /&gt;
When the maker is trading with an out-of-sync Bisq wallet they will often be able to 'make' a trade of their choosing. Normally one of two things happen:&lt;br /&gt;
# 1. When the maker is trading with an out-of-sync Bisq wallet most often the trade will end up not being displayed on the Bisq Markets for someone to take as the software checks to make sure an offer is valid before propagating it to the peer to peer network. When a trade fails in this way the maker will not have lost any trade fees or miner fees as there was never any maker transaction ID. In this instance the fix is for the maker of the trade to do an [[Resyncing SPV file|SPV resync]]. Once this is completed they can delete the trade they made by goin to Portfolio &amp;gt; Open Offers and pressing the delete icon next to the trade.&lt;br /&gt;
# 2. Sometimes an invalid maker offer can be shown in a users Bisq instance. If this happens when the taker takes the offer they will lose both mining and trade fees as they will incur costs for the taker transaction ID even though a deposit transaction will not be created. In this case reimbursement can be considered by the taker if the lost fees are significant enough to warrant making a reimbursement request, eg above $10 of value.). In this instance the fix is for the maker of the trade to do an [[Resyncing SPV file|SPV resync]]. &lt;br /&gt;
&lt;br /&gt;
When the taker is trading with an out-of-sync Bisq wallet they will often be able to 'take' a trade of their choosing. Normally one of two things happen:&lt;br /&gt;
# 1. The trade remains in the offer book, the taker transaction and the deposit transaction fails, the trade can be seen on both the buyer's and seller's Bisq instance. The deposit transaction confirmation will show as N/A. This is because the deposit transaction could not be created because the taker transaction failed. In this instance neither the maker or taker will have lost any trade or miner fees. The offer will still be able to be taken in the offer book, and the taker transaction did not confirm so no fees were spent from the takers wallet. In this instance the fix is for the taker of the trade to do an [[Resyncing SPV file|SPV resync]]. &lt;br /&gt;
# 2. The trade is removed from the offer book, the taker transaction and the deposit transaction fails, the trade can be seen on both the buyer's and seller's Bisq instance. The deposit transaction confirmation will show as being present but a check on a blockchain explorer will show it as an invalid transaction. This is because the deposit transaction could not be created because the taker transaction failed. In this instance the maker will have lost trade and miner fees, but the taker will not have lost any fees. In this case reimbursement can be considered by the maker if the lost fees are significant enough to warrant making a reimbursement request, eg above $10 of value.). In this instance the fix is for the taker of the trade to do an [[Resyncing SPV file|SPV resync]]. &lt;br /&gt;
&lt;br /&gt;
== Less common reasons for trades to fail ==&lt;br /&gt;
&lt;br /&gt;
Less common reasons for trades to fail are:&lt;br /&gt;
&lt;br /&gt;
* Bugs in the software&lt;br /&gt;
* Tor network issues&lt;br /&gt;
* A user trading with an out of space hard drive, corrupted wallet, or poor connection to the Bisq network&lt;br /&gt;
&lt;br /&gt;
In these cases the maker and taker can check their respective transaction IDs.&lt;br /&gt;
&lt;br /&gt;
* If the maker or taker ID failed then the respective user will not have lost any miner or trade fees.&lt;br /&gt;
* If the maker transition ID was successful on the blockchain then the maker will not have lost any trade or miner fees IF the deposit transaction shows as N/A&lt;br /&gt;
* If the maker transition ID was successful on the blockchain then the maker will have lost trade and mine fees IF the deposit transaction shows as being present but is invalid  when checked on the blockchain.&lt;br /&gt;
* If the taker transition ID was successful on the blockchain then the taker will have lost trade and miner fees if the trade failed.&lt;br /&gt;
&lt;br /&gt;
In instances like the above ideally the trade would end up in mediation and the mediator will request your logs to understand what the issue was that caused the trade to fail and make recommendations for what, if anything, you need to do to avoid future instances of failed trades.&lt;br /&gt;
&lt;br /&gt;
== What failed trades are eligible for reimbursement? ==&lt;br /&gt;
&lt;br /&gt;
Any user that has lost trade and miner fees is eligible for reimbursement.&lt;br /&gt;
&lt;br /&gt;
Trades are also only eligible for reimbursement if submitted within 3 months from the date of the trade.&lt;br /&gt;
&lt;br /&gt;
== When to consider reimbursement? ==&lt;br /&gt;
&lt;br /&gt;
It is important to remember no trade or deposit funds are lost with failed trades. Most of the time if you see your Bisq wallet is missing funds from a failed trade it means your wallet it out-of-sync, which is why the trade failed!  Do an [[Resyncing SPV file|SPV resync]] to fix the issue and your wallet will show the correct balance.&lt;br /&gt;
&lt;br /&gt;
Reimbursement of a filed trade requires some work to do in gathering the information and posting it online, it also have some privacy implications as you are having to post maker, taker, and deposit transaction IDs. As a result of this it is often not making reimbursement requests for MOST failed trades as miner and trade fees are usually small (less than a few dollars, local currency equivalent, of value). Therefore, it is recommended traders ONLY request reimbursement for trades where they feel their trade fee and miner fee losses are significant enough to warrant the time to do so. Most of the time this will be for takers with lost trade fees where the trade that failed was a large amount of BTC. For example the maximum trade fee loss on a 2 BTC trade would be 0.0088 BTC. This would be worth requesting reimbursement for.&lt;br /&gt;
&lt;br /&gt;
== What should I do before requesting reimbursement request for lost miner and trade fees? ==&lt;br /&gt;
&lt;br /&gt;
Before requesting reimbursement for a filed trade you should make sure you are eligible for reimbursement ie you have lost both trade fees and miner fees.&lt;br /&gt;
&lt;br /&gt;
You should also be aware of what miner fees and reimbursement fees you have lost on the trade. This is important as it means traders are aware of what fees they are claiming before they make a reimbursement request and prevents any misunderstanding of users with failed trades assuming they have lost the trade or deposit amounts when that is not the case, and in most cases can be quickly solved with an [[Resyncing_SPV_file|SPV Resync]].&lt;br /&gt;
&lt;br /&gt;
==== How do I know what my miner fees were? ====&lt;br /&gt;
&lt;br /&gt;
Please also make sure you know how much miner fees you lost for a trade. This can be checked on blockchain explorer. &lt;br /&gt;
&lt;br /&gt;
[[File:Miner fees.png|thumb|center|This shows where you can find your miner fees on a blockchain explorer such as mempool.space]]&lt;br /&gt;
&lt;br /&gt;
==== How do I know what my trader fees were? ====&lt;br /&gt;
&lt;br /&gt;
Please also make sure you know how much trade fees you lost for a trade. This will be a percentage of the trade amount and differs depending on whether you were the maker or taker or chose BTC or BSQ to pay the trade fees.&lt;br /&gt;
&lt;br /&gt;
* BTC trade fees are 0.12% of the trade amount for the maker and 0.88% of the trade amount for the taker.&lt;br /&gt;
* BSQ trade fees are 0.06% of the trade amount for the  maker and 0.44% of the trade amount for the taker.&lt;br /&gt;
&lt;br /&gt;
You can check the latest trading fees [[Trading_fees|here]].&lt;br /&gt;
&lt;br /&gt;
You can verify your BTC fees on any blockchain explorer.&lt;br /&gt;
&lt;br /&gt;
You can verify your BSQ fees on a BSQ explorer such as https://bisq.markets/ or https://bisq.mempool.emzy.de/&lt;br /&gt;
&lt;br /&gt;
== How to make reimbursement request for lost miner and trade fees from a failed trade? ==&lt;br /&gt;
&lt;br /&gt;
You can make a reimbursement request for lost miner and trade fees from a failed trade by creating a new issue on the [https://github.com/bisq-network/support/issues Bisq GitHub Support repository].&lt;br /&gt;
&lt;br /&gt;
You will need a GitHub account, to maintain privacy feel free to create on just for the purpose of the reimbursement. There is a [https://github.com/bisq-network/support/issues/new?assignees=&amp;amp;labels=&amp;amp;template=reimbursement-template.md&amp;amp;title=Fee+reimbursement+for+trade+XXXXX template here]* that you should follow to create your reimbursement request.&lt;br /&gt;
&lt;br /&gt;
*This link will only work when you are logged into a GitHub account.&lt;br /&gt;
&lt;br /&gt;
Once your issue is posted a support agent might ask you some more questions if they need any extra info to what you have provided.&lt;br /&gt;
&lt;br /&gt;
If your request is a valid one for reimbursement then the [https://bisq.wiki/Fee_Reimbursement_Agent Fee Reimbursement Agent] will add you to their list of reimbursement cases to payout. They usually process reimbursements every 4-8 weeks in batches so please be prepared to wait a little time before reimbursement. You can follow the process on the issue you created to see the status of your reimbursement.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3096</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3096"/>
		<updated>2023-01-14T16:53:19Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Tips */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
&lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose every personalization (pinned tabs and history mainly), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3095</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3095"/>
		<updated>2023-01-14T16:50:23Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; in other words, we will use Tor Browser in a way that it is NOT intended to be used. An adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
&lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose everything (passwords, history, pinned tabs, and everything else will be discarded), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3094</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3094"/>
		<updated>2023-01-14T16:48:46Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Tips */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; an adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
&lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
* sometimes the Tor connection will degrade to a point where it's not useable, and you need to create a new Tor circuit; do NOT, EVER click &amp;quot;New Identity&amp;quot; to do this, or you will lose everything (passwords, history, pinned tabs, and everything else will be discarded), rather close Tor Browser and restart it&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3093</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3093"/>
		<updated>2023-01-14T16:46:11Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* If you don't already have Tor Browser installed: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; an adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
&lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3068</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=3068"/>
		<updated>2022-12-27T22:22:00Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
This is not an advanced privacy/anonymity guide, but is rather tailored to Bisq contributors and their selective need for pseudonymity, which should not impact too much on convenience unless they cover very sensitive roles (in which case they are already prepared on the matter of personal security, and do not really need this guide anyway).&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as key elements for Bisq's well being, might be among targeted individuals, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
The aim of this guide is containerization, which means that a ''contributor'' will appear to an ''adversary'' (someone trying to understand who you really are, to do bad things to you) as a specific individual, traceable online as ''contributor'', but hopefully (if you do things well enough) not linkable to their real identity, nor to other possible nyms ''contributor'' uses while participating in other projects.&lt;br /&gt;
In other words, ''adversary'' will be able to tell if something on the internet has been said by ''contributor'', but it should not make them any wiser about who ''contributor'' really is, where they live, or which other works they have done for other initiatives.&lt;br /&gt;
We will be making Tor Browser work as a much more convenient, much less privacy hardened browser, that will still force you to connect through Tor to do whatever you need; an adversary will be able to fingerprint you as a nym, but they won't find details to locate your real identity if you are careful; the previous statement will not be liked by enthusiasts of online privacy, but a mild yet consistent plan, is still much better than a very strong plan that is not adhered to 100% of the time because it is very unconvenient.&lt;br /&gt;
&lt;br /&gt;
Let's clear up some definitions:&lt;br /&gt;
* privacy is when someone knows who you are, but not what you do&lt;br /&gt;
* anonymity is when someone knows what you do, but not who you are&lt;br /&gt;
* pseudonymity is when someone knows &amp;quot;who&amp;quot; you are and what you do, but the &amp;quot;who&amp;quot; is an imaginary identity that exists only in its own reality, without any ties to your real or alternative identities&lt;br /&gt;
&lt;br /&gt;
For more info:&lt;br /&gt;
* https://github.com/BlockchainCommons/pseudonymity-guide&lt;br /&gt;
* https://anonymousplanet.org/guide.html&lt;br /&gt;
&lt;br /&gt;
= Tenets =&lt;br /&gt;
&lt;br /&gt;
* I will have a Bisq nym, that will be the only one used for everything related to Bisq&lt;br /&gt;
* My Bisq nym will be its own person, it will not be similar to, know about the existence of, or participate in the same chats/groups/forums/activities as my real or alternative identities&lt;br /&gt;
* I will only use Tor for everything the Bisq nym does&lt;br /&gt;
* I will endure the slowness of Tor, and will NOT use my real connection nor my faster VPN to do Bisq stuff&lt;br /&gt;
&lt;br /&gt;
= Steps for base setup =&lt;br /&gt;
 &lt;br /&gt;
== If you don't already have Tor Browser installed: ==&lt;br /&gt;
 &lt;br /&gt;
* download Tor Browser for your OS&lt;br /&gt;
* have Tor Browser &amp;quot;installed&amp;quot; (actually it is just uncompressed in a folder with no ties to registry or system config) in a path that's unique to your Bisq nym&lt;br /&gt;
  &lt;br /&gt;
== If you have another Tor Browser already installed ==&lt;br /&gt;
  &lt;br /&gt;
* make a copy of your installed Tor Browser directory. (For example copy to &amp;lt;code&amp;gt;Tor Browser Bisq&amp;lt;/code&amp;gt;)&lt;br /&gt;
* run the copy, ignore the error about restarting Tor if the other Tor Browser is open (they will try to bind the same ports, returning an error), close the popup and open &amp;lt;code&amp;gt;about:config&amp;lt;/code&amp;gt; in the URL bar, say that you really want to access the options, then search for &amp;lt;code&amp;gt;_port&amp;lt;/code&amp;gt;&lt;br /&gt;
* you want to edit &amp;lt;code&amp;gt;network.proxy.socks_port&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;extensions.torlauncher.control_port&amp;lt;/code&amp;gt;, the standard values here are respectively 9150 and 9151 (standalone tor daemon is 9050 and 9051), so you can change them to 9250 and 9251, or increase them to 9350 and 9351 if you want several Tor Browser instances running at the same time&lt;br /&gt;
* still in about:config, search for &amp;quot;privacy.resistFingerprinting.letterboxing&amp;quot; and set it to false (allows maximizing pages to fill the whole screen)&lt;br /&gt;
* close Tor Browser and restart it&lt;br /&gt;
* start the other Tor Browser in your system&lt;br /&gt;
 &lt;br /&gt;
== Common steps ==&lt;br /&gt;
 &lt;br /&gt;
* go to geolocation.com in Tor Browser, verify the IP and location is different from your real ones (it will necessarily be, this is just to show you where you appear to be coming from, when using Tor)&lt;br /&gt;
* make sure the shield icon in top right is empty (clicking on it says &amp;quot;standard&amp;quot;); this will enable scripts, which are not &amp;quot;safe&amp;quot; for anonymity, but you want a bit of convenience to be able to use Matrix and other websites that require javascript, as long as all activity in this browser stays withing your Bisq nym&lt;br /&gt;
* go to settings &amp;gt; privacy, and under &amp;quot;history&amp;quot; disable &amp;quot;always use private browsing&amp;quot;, this will restart Tor Browser; after restart, return to same settings, disabled cookie deletion after Tor Browser closes (so you can log back in to websites automatically), enable all logins&amp;amp;passwords saving, in under history enable what suits you (enable both &amp;quot;remember&amp;quot; for maximum convenience), then under Permissions, block requests to access camera and location (maybe you need to enable mic for calls).&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* if for some reason you don't like the IP/location you are coming from out of Tor, or the connection has become unbearably slow for you, you can click on top right tool button and choose &amp;quot;New Identity&amp;quot;, Tor Browser will restart and find another circuit&lt;br /&gt;
* sometimes Tor will become slow, really, unbearably torturing slow; stay strong, don't go clearnet; if all else fails, blame Tor with your correspondents, it will immediately excuse you for your unresponsiveness, and at the same time show you are very privacy-oriented and make you look really cool&lt;br /&gt;
* the usual tip to leave the tor browser window at default size is not really needed here, as we are okay with &amp;quot;fingerprinting&amp;quot; the nym&lt;br /&gt;
&lt;br /&gt;
= Known issues and warnings =&lt;br /&gt;
&lt;br /&gt;
* real anonymity does not exist, even if you could &amp;quot;plug&amp;quot; into the internet like rebels plugged into the Matrix, someone could still be able to trace the source of your &amp;quot;signal&amp;quot;; proper personal protection can be achieved based on one's dedication and skills, and always relative to one's thread model (a Bisq contributor shouldn't get the same attention that a whistleblower does, for example)&lt;br /&gt;
* it only takes one mistake, where you let a hint to your real identity slip through your pseudonym, and your whole nym is compromised, plus all of their past activity will be linked to you&lt;br /&gt;
* assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
* in the above configuration, Tor Browser loses most of its specific privacy strengths, yet it's still very useful to have a portable, containerized browser that will only work through Tor, and builds its own Tor connection, distinct from any other Tor daemon you might have on your system (versus, for example, using several chromium instances tied to the same Tor proxy, which will all use the same entry and exit node, and which will be at risk of going on clearnet if for any reason the plugin you use to proxy through Tor doesn't do its job)&lt;br /&gt;
* this guide is only aimed at online protection, offering nothing in the compartment of offline security: anyone physically accessing your PC will be able to tell that you are, in fact, ''contributor'', plus any other identity you might have used online, unless you also hardened your system with additional layers that will not be covered in this guide, at least for now (see Tails, Qubes, Whonix, or any other renowned tool for PC protection)&lt;br /&gt;
&lt;br /&gt;
= Steps for accounts setup =&lt;br /&gt;
As a Bisq contributor, you will need at minimum a GitHub account, to be able to publish Compensation Requests. A GitHub account requires an email address, so you will need that one as well.&lt;br /&gt;
Protonmail is one email provider that will let you register -as of now- without any KYC elements (no other email addresses nor phone numbers needed); riseup.net also offers no-kyc email, but you need an invite by another user; in case you know of similar services, please notify us and we will gladly add them in this guide.&lt;br /&gt;
An account on matrix is also advised to access Bisq's space, you will register from https://bisq.chat and use the same email to associate to that account, you might want to also register at https://bisq.community to interact with the forum.&lt;br /&gt;
An interesting customization can be to obtain an AI generated face to associate with your account, there are many services that let you get such a picture for free.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3067</id>
		<title>Connecting to your own Bitcoin node</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3067"/>
		<updated>2022-12-13T22:06:10Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Connecting to another Bitcoin node */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq will '''connect to your local Bitcoin node''' if it finds it upon starting up. This article contains the requirements for this to work correctly.&lt;br /&gt;
&lt;br /&gt;
You can also specify the addresses of particular Bitcoin nodes in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= General node settings =&lt;br /&gt;
&lt;br /&gt;
The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;server=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;pruned=0&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;peerbloomfilters=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which in turn:&lt;br /&gt;
* enable the block server mode&lt;br /&gt;
* disable the pruning of old blocks&lt;br /&gt;
* allow Bisq to run its SPV wallet&lt;br /&gt;
&lt;br /&gt;
= Connecting to a local Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or &amp;lt;code&amp;gt;bitcoind&amp;lt;/code&amp;gt; running on &amp;lt;code&amp;gt;localhost&amp;lt;/code&amp;gt; on port 8333.&lt;br /&gt;
&lt;br /&gt;
Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.&lt;br /&gt;
&lt;br /&gt;
= Connecting to another Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
By default, Bisq maximizes your privacy by connecting to nodes run by trusted  Bisq contributors. &lt;br /&gt;
&lt;br /&gt;
If you'd like to connect to another node, you can specify its address in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;. Bisq will validate the address and connect to the specified node the next time it starts.&lt;br /&gt;
&lt;br /&gt;
Bisq supports connecting to Bitcoin nodes with Tor v3 addresses: this is the easiest path to take, since you only have to fill in your node's onion address in settings.&amp;lt;br&amp;gt;&lt;br /&gt;
If your node is on your local network, connecting directly to it rather than using Tor would reduce latency by a sensible degree. In order to do this:&lt;br /&gt;
* make sure the node's firewall allows incoming connections on port 8333 from the local network&lt;br /&gt;
* have Bitcoin daemon listen to &amp;lt;code&amp;gt;0.0.0.0&amp;lt;/code&amp;gt; rather than &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt; (add a line that says &amp;lt;code&amp;gt;bind 0.0.0.0&amp;lt;/code&amp;gt;)&lt;br /&gt;
* uncheck &amp;quot;Use Tor for Bitcoin network&amp;quot; under Settings&amp;gt;Network in Bisq application&lt;br /&gt;
* fill in your node's local network &amp;lt;code&amp;gt;ipaddress:8333&amp;lt;/code&amp;gt; in &amp;quot;Use custom bitcoin Core nodes&amp;quot; field&lt;br /&gt;
&lt;br /&gt;
Explaining in detail each step of the above goes past the scope of this guide, yet you can usually find more information either by searching for specific guides, or asking on discussion boards/groups.&lt;br /&gt;
&lt;br /&gt;
= Troubleshooting =&lt;br /&gt;
&lt;br /&gt;
If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows.  &lt;br /&gt;
&lt;br /&gt;
For MacOS:&lt;br /&gt;
 &amp;lt;code&amp;gt;Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
For Linux:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt; cd /opt/bisq/bin&lt;br /&gt;
&lt;br /&gt;
./Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/7c07cdb6ff60ad1186dea33acdfb688668c2aae6/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L76 here in the Bisq code]. &lt;br /&gt;
&lt;br /&gt;
[[Running_from_the_command_line|More info on running from the command line]].&lt;br /&gt;
&lt;br /&gt;
[[Command_line_options|More info on command line options]].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Table_of_penalties&amp;diff=3030</id>
		<title>Table of penalties</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Table_of_penalties&amp;diff=3030"/>
		<updated>2022-10-26T16:27:45Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Penalties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Penalties ==  &lt;br /&gt;
Bisq has [[Trading_rules|Rules]] in place to make the trading process as safe and convenient as possible for all parties involved, and it is important those rules are followed by users.&lt;br /&gt;
&lt;br /&gt;
Penalties are a percentage of the trade amount, deducted from the offending peer's security deposit (and when needed, also from trade amount itself) and offered as a compensation to the other peer during the [[Dispute_resolution#Level_2:_Mediation|Dispute resolution process]]&lt;br /&gt;
The actual penalty will be '''up to''' the values detailed below, depending on security deposit % and mediator's discretion, ''except'' for 100% penalties, that refer to serious violations and will always imply losing the whole amount (trade + deposit).&lt;br /&gt;
&lt;br /&gt;
Alternatively, if good communication is established, peers can use trader chat to agree on a penalty amount to relay to their mediator.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' BTC Buyer or Seller issues:''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Buyer or Seller &lt;br /&gt;
|-&lt;br /&gt;
| 100% || Fraud attempt: debiting of peer's account, code tampering &lt;br /&gt;
|-&lt;br /&gt;
| 50% || Attempting to get a peer to communicate outside of Bisq by displaying your contact info in the 'additional information' field on a cash by mail or face to face offer.&lt;br /&gt;
|-&lt;br /&gt;
| 25% || Not responding to a mediator within 48h&lt;br /&gt;
|-&lt;br /&gt;
| 25% || Bitcoin-related payment references (e; BTC, Bisq, Bitcoin...) &lt;br /&gt;
|-&lt;br /&gt;
| 20% || Cancelling a trade &lt;br /&gt;
|-&lt;br /&gt;
| 20% || Requesting that payment be made from/to a different account name, without mediator's acknowledgement&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Requiring personal data: ID, home address, etc. (Bisq should incentivize accounts that do not ask for any more info than necessary) &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' BTC Buyer:''' &lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Buyer&lt;br /&gt;
|-&lt;br /&gt;
| 100% || Payment chargeback&lt;br /&gt;
|-&lt;br /&gt;
| 25% || Paying from an account with different name (as in &amp;quot;different person&amp;quot;, while little variations, where it's clear payment comes for the correct person, are not penalized), seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 20% || Payment is 72+ hours late&lt;br /&gt;
|-&lt;br /&gt;
| 15% || Payment is 48-72 hours late &lt;br /&gt;
|-&lt;br /&gt;
| 15% || Paying from an account with same name but different account number, seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Payment is 24-48 hours late&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Similar, but wrong, payment method (eg. SWIFT instead of SEPA, SEPA instant instead of Wise...)&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Wrong payment amount: buyer has the option to correct the amount within the trade window, seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Using unagreed payment reference. Any unagreed payment reference (also the trade ID) shares the same penalty. &amp;quot;Flowers&amp;quot; could be as bad as &amp;quot;services rendered&amp;quot; depending on every single case&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Late payment because of low fee for altcoin tx; penalty can be reduced during mediation if buyer uses RBF or similar&lt;br /&gt;
|-&lt;br /&gt;
| 5% || Payment is up to 24 hours late&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
''' BTC Seller:'''&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Seller&lt;br /&gt;
|-&lt;br /&gt;
| 15% || BTC is released outside of trade window&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
- Release times can't be enforced, because at mediation, the last trader to accept the suggestion is the one who decides when the payout is submitted.&lt;br /&gt;
- Cannot accept SEPA instant is replaced by buyer or seller's penalty &amp;quot;Suggest different payment method - account without mediator's acknowledgement.&amp;quot;. This way, an instant SEPA trade could continue as normal SEPA&lt;br /&gt;
- All reasons to  cancel a trade are merged, because traders will tend to give the reason that penalizes them less&lt;br /&gt;
- I keep the explanation because penalizing a user because their bank asks for info is a controversial matter. I might agree with note 3 but this has been working so far.&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Mobile_notifications&amp;diff=3028</id>
		<title>Mobile notifications</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Mobile_notifications&amp;diff=3028"/>
		<updated>2022-09-29T06:33:43Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A full Bisq mobile app doesn't exist yet, but you can get '''mobile notifications''' from Bisq while it runs on your computer.&lt;br /&gt;
&lt;br /&gt;
The mobile notifications app currently works on iOS and Android devices with Google Play Services; only for Android platform, the latest APK can also be downloaded from the [https://github.com/bisq-network/bisqremote_Android/releases github repository].&lt;br /&gt;
&lt;br /&gt;
'''Foreword about current state of mobile app'''ː currently, the mobile app will be able to pair with desktop (only through token), but it won't show a feedback about the pairing being successful; the app will also show an event in notification area, when one of the trigger events selected on desktop will happen, but the details of such event won't be visible on mobile, and clicking the event in notification area will bring back to the pairing screen; it is needed to open the desktop app to verify what event triggered the notification.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Get the app ==&lt;br /&gt;
&lt;br /&gt;
Mobile app links:&lt;br /&gt;
* [https://play.google.com/store/apps/details?id=com.joachimneumann.bisq Google Play Store] (Android) ([https://github.com/bisq-network/bisqremote_Android Source])&lt;br /&gt;
* [https://apps.apple.com/us/app/bisq-mobile/id1424420411 Apple App Store] (iOS) ([https://github.com/bisq-network/bisqremote_iOS Source])&lt;br /&gt;
&lt;br /&gt;
== Pair the mobile app with desktop Bisq ==&lt;br /&gt;
&lt;br /&gt;
You will need to send the pairing token generated by the mobile app to desktop Bisq. To do this, you can either use your computer's webcam to scan a QR code shown on your phone, or send the pairing token text manually from the mobile app to your desktop and paste it into Bisq yourself.&lt;br /&gt;
&lt;br /&gt;
To generate the pairing token, click &amp;lt;code&amp;gt;Pair&amp;lt;/code&amp;gt; in the mobile app.&lt;br /&gt;
&lt;br /&gt;
If you'd like to use your desktop computer's webcam, go to &amp;lt;code&amp;gt;Account&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Notifications&amp;lt;/code&amp;gt;, click &amp;lt;code&amp;gt;Scan QR Code&amp;lt;/code&amp;gt;, and scan the QR code shown in the mobile app.&lt;br /&gt;
&lt;br /&gt;
If not, securely send the text of the pairing token to yourself and click &amp;lt;code&amp;gt;I don't have a webcam&amp;lt;/code&amp;gt; in desktop Bisq. The apps may mention something about email, but you can send the pairing key using any method you prefer.&lt;br /&gt;
&lt;br /&gt;
When pairing completes, you’ll see a success message in Bisq desktop.&lt;br /&gt;
&lt;br /&gt;
== Configure notifications ==&lt;br /&gt;
&lt;br /&gt;
There are three types of notifications you can get: trade alerts, offer alerts, and price alerts. You can also enable and disable notification sounds.&lt;br /&gt;
&lt;br /&gt;
=== Trade alerts ===&lt;br /&gt;
&lt;br /&gt;
These alerts will notify you whenever:&lt;br /&gt;
* your action is needed on any open trades&lt;br /&gt;
* one of your offers is taken&lt;br /&gt;
* you've received a new dispute message&lt;br /&gt;
&lt;br /&gt;
To enable trade alerts, simply check the &amp;lt;code&amp;gt;Receive trade messages&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
'''Note that dispute alerts do not include any message content'''—they merely let you know a new dispute message has been received on your desktop Bisq app.&lt;br /&gt;
&lt;br /&gt;
Here’s how trade alerts can be useful:&lt;br /&gt;
&lt;br /&gt;
Example 1: you’re buying BTC, just sent your deposit, and are waiting for the transaction to hit 1 blockchain confirmation so you can send payment. That can take approximately 10 minutes. Instead of waiting at your screen, you can go have a coffee and let your phone alert you when it’s time to send the fiat currency or altcoin payment.&lt;br /&gt;
&lt;br /&gt;
Example 2: you’re selling BTC, and you’re waiting for your trading partner to send you fiat currency or altcoin payment. It might take them minutes or hours. Instead of repeatedly checking your desktop Bisq app for updates, your mobile device will simply push an alert as soon as your trading partner marks their payment as sent, so you can then check for the payment and promptly complete the trade.&lt;br /&gt;
&lt;br /&gt;
=== Offer alerts  ===&lt;br /&gt;
&lt;br /&gt;
These alerts will notify you whenever there’s a new offer that fits your criteria.&lt;br /&gt;
&lt;br /&gt;
To set your criteria:&lt;br /&gt;
&lt;br /&gt;
# Select your preferred payment account.&lt;br /&gt;
# Select which offers you want to receive alerts for: buy or sell. If you want to buy bitcoin, you’ll want to know when someone’s made a good sell offer (and vice-versa if you want to sell bitcoin).&lt;br /&gt;
# Determine the % distance from the market price for which you want to get a notification. With a price distance set, you will only receive an alert when an offer that meets (or exceeds) your requirements is published. Example: you want to sell BTC, but you will only sell at a 2% premium to the current market price. Setting this field to 2% will ensure you only receive alerts for offers with prices that are 2% (or more) above the current market price.&lt;br /&gt;
# Hit &amp;lt;code&amp;gt;Add offer alert&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Clicking &amp;lt;code&amp;gt;Manage offer alerts&amp;lt;/code&amp;gt; shows you a screen with all configured alerts. There, you can remove offer alerts you no longer need.&lt;br /&gt;
&lt;br /&gt;
=== Price alerts ===&lt;br /&gt;
&lt;br /&gt;
These alerts will notify you whenever bitcoin hits the specified price in the specified currency.&lt;br /&gt;
&lt;br /&gt;
First, select your currency. Then, choose the upper and lower price thresholds. You’ll get an alert when the bitcoin price goes above your upper threshold, or when it goes below your lower threshold.&lt;br /&gt;
&lt;br /&gt;
Example: an alert set with an upper threshold of 6000 EUR and lower threshold of 5500 EUR will send you a notification when the market price goes over 6000 or when it goes below 5500 EUR.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Once a price alert is triggered, it’s automatically deleted so you don’t get repeated notifications as the price fluctuates.}}&lt;br /&gt;
&lt;br /&gt;
== Technical details &amp;amp; privacy ==&lt;br /&gt;
&lt;br /&gt;
[[File:Mobile-notifications-architecture.png|600px|thumb|left|Bisq mobile notification architecture.]]&lt;br /&gt;
&amp;lt;div style=&amp;quot;clear: both;&amp;quot;&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Notifications are sent from the Bisq desktop app to the Bisq relay node which acts as proxy to the Apple/Google push notification services.&lt;br /&gt;
&lt;br /&gt;
=== Pairing ===&lt;br /&gt;
&lt;br /&gt;
Before allowing the mobile app to start the pairing to the Bisq desktop app, the mobile App registers with the Apple or Google notification service and receives a notification token. This happens in the background without any user interaction. Next, a byte cryptographic key for symmetric encryption is generated in the phone and the pairing token is assembled.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|We use the 128 bit AES/CBC/PKCS5Padding symmetric encryption algorithm. A fresh 16-character Initialization Vector is created and attached to each notification.}}&lt;br /&gt;
&lt;br /&gt;
The pairing token consists of four parts which are separated by the &amp;quot;|&amp;quot; character:&lt;br /&gt;
&lt;br /&gt;
* A Magic, currently either iOS, iOSDev or android.&lt;br /&gt;
* A Phone descriptor, e.g., iPhone6.&lt;br /&gt;
* A 32-byte cryptographic key for symmetric encryption. This key is generated by the phone and used in the Bisq desktop app to encrypt the content of the notification.&lt;br /&gt;
* A device token, either from Apple or from Google.&lt;br /&gt;
&lt;br /&gt;
The pairing token is then transferred from the phone to Bisq desktop by QR code (using the desktop computers' webcam) or manually by the user (e.g., sending the string through a secure messaging app, email, etc).&lt;br /&gt;
&lt;br /&gt;
=== Sending a notification ===&lt;br /&gt;
&lt;br /&gt;
The Bisq desktop app knows the device token (from Apple or Google) and it has the encryption key from the phone. The notification itself is a json string containing the type of notification and its content. After encrypting the notification the desktop app sends it along with the device token to a Bisq relay node over Tor. Because of Tor, the relay node does not know the IP address of the computer on which you run your Bisq desktop app. The relay node forwards the notification to an Apple/Google push notification server (over https), which then pushes a notification to your mobile device using the provided device token.&lt;br /&gt;
&lt;br /&gt;
=== Privacy ===&lt;br /&gt;
&lt;br /&gt;
Ultimately, Apple/Google know that a device with your device token is receiving Bisq notifications. Note that they already knew you are likely to be a Bisq user when you download the Bisq mobile app. However, neither Google nor Apple can see the content of the notification. This is also the reason why OS pop-ups that notify you cannot contain any notification specific content.&lt;br /&gt;
&lt;br /&gt;
Currently, the relay node does not store any data (notifications, device tokens, etc).&lt;br /&gt;
&lt;br /&gt;
We feel that Push notifications can’t be implemented in a more private way. If there is any aspect of this mobile notifications mechanism, feel free to contact us. Of course, the notification mechanism is optional and does in no way limit the functionality of the Bisq desktop app.&lt;br /&gt;
&lt;br /&gt;
== More information ==&lt;br /&gt;
&lt;br /&gt;
See the [https://github.com/bisq-network/bisqremote/wiki/Specification wiki on GitHub] for more details.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Template:Run_with_Java_options&amp;diff=3001</id>
		<title>Template:Run with Java options</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Template:Run_with_Java_options&amp;diff=3001"/>
		<updated>2022-07-23T23:21:58Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* GUI fix */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Command-line fix ==&lt;br /&gt;
&lt;br /&gt;
{{{2}}}:&lt;br /&gt;
&lt;br /&gt;
 JAVA_TOOL_OPTIONS=&amp;quot;{{{1}}}&amp;quot; /opt/bisq/bin/Bisq&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq&amp;lt;/code&amp;gt; is the default application directory on Linux. If you run another operating system, you'll need to replace that path with [[Running_from_the_command_line|the one for your OS]].&lt;br /&gt;
&lt;br /&gt;
You can adjust the scaling factor as you wish, of course, and add any [[Command_line_options|runtime options for Bisq]] as well.&lt;br /&gt;
&lt;br /&gt;
== GUI fix ==&lt;br /&gt;
&lt;br /&gt;
To be able to launch the fix by double clicking an icon, rather than running a command in CLI, you can edit the launcher file to run, instead of the Bisq app directly, a shell script which injects said fix.&lt;br /&gt;
&lt;br /&gt;
1. Create a text file (for example &amp;lt;code&amp;gt;/opt/bisq/Bisq-runner.sh&amp;lt;/code&amp;gt;) containing the following code:&lt;br /&gt;
&lt;br /&gt;
 #!/bin/bash&lt;br /&gt;
 JAVA_TOOL_OPTIONS=&amp;quot;{{{1}}}&amp;quot; /opt/bisq/bin/Bisq&lt;br /&gt;
&lt;br /&gt;
2. Make it executable:&lt;br /&gt;
&lt;br /&gt;
 chmod +x /opt/bisq/Bisq-runner.sh&lt;br /&gt;
&lt;br /&gt;
3. Edit the launcher file (&amp;lt;code&amp;gt;/opt/bisq/Bisq.desktop&amp;lt;/code&amp;gt; and/or &amp;lt;code&amp;gt;/usr/share/applications/Bisq.desktop&amp;lt;/code&amp;gt;) by opening it in a text editor and modifying the &amp;lt;code&amp;gt;Exec&amp;lt;/code&amp;gt; line like follows:&lt;br /&gt;
&lt;br /&gt;
 Exec=/opt/bisq/Bisq-runner.sh&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3000</id>
		<title>Connecting to your own Bitcoin node</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=3000"/>
		<updated>2022-07-23T23:10:57Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Connecting to another Bitcoin node */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq will '''connect to your local Bitcoin node''' if it finds it upon starting up. This article contains the requirements for this to work correctly.&lt;br /&gt;
&lt;br /&gt;
You can also specify the addresses of particular Bitcoin nodes in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= General node settings =&lt;br /&gt;
&lt;br /&gt;
The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;server=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;pruned=0&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;peerbloomfilters=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which in turn:&lt;br /&gt;
* enable the block server mode&lt;br /&gt;
* disable the pruning of old blocks&lt;br /&gt;
* allow Bisq to run its SPV wallet&lt;br /&gt;
&lt;br /&gt;
= Connecting to a local Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or &amp;lt;code&amp;gt;bitcoind&amp;lt;/code&amp;gt; running on &amp;lt;code&amp;gt;localhost&amp;lt;/code&amp;gt; on port 8333.&lt;br /&gt;
&lt;br /&gt;
Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.&lt;br /&gt;
&lt;br /&gt;
= Connecting to another Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
By default, Bisq maximizes your privacy by connecting to nodes run by trusted  Bisq contributors. &lt;br /&gt;
&lt;br /&gt;
If you'd like to connect to another node, you can specify its address in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;. Bisq will validate the address and connect to the specified node the next time it starts.&lt;br /&gt;
&lt;br /&gt;
Bisq supports connecting to Bitcoin nodes with Tor v3 addresses: this is the easiest path to take, since you only have to fill in your node's onion address in settings.&amp;lt;br&amp;gt;&lt;br /&gt;
If your node is on your local network, connecting directly to it rather than using Tor would reduce latency by a sensible degree. In order to do this:&lt;br /&gt;
* make sure the node's firewall allows incoming connections on port 8333 from the local network&lt;br /&gt;
* have Bitcoin daemon listen to &amp;lt;code&amp;gt;0.0.0.0&amp;lt;/code&amp;gt; rather than &amp;lt;code&amp;gt;127.0.0.1&amp;lt;/code&amp;gt;&lt;br /&gt;
* uncheck &amp;quot;Use Tor for Bitcoin network&amp;quot; under Settings&amp;gt;Network in Bisq application&lt;br /&gt;
* fill in your node's local network &amp;lt;code&amp;gt;ipaddress:8333&amp;lt;/code&amp;gt; in &amp;quot;Use custom bitcoin Core nodes&amp;quot; field&lt;br /&gt;
&lt;br /&gt;
Explaining in detail each step of the above goes past the scope of this guide, yet you can usually find more information either by searching for specific guides, or asking on discussion boards/groups.&lt;br /&gt;
&lt;br /&gt;
= Troubleshooting =&lt;br /&gt;
&lt;br /&gt;
If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows.  &lt;br /&gt;
&lt;br /&gt;
For MacOS:&lt;br /&gt;
 &amp;lt;code&amp;gt;Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
For Linux:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt; cd /opt/bisq/bin&lt;br /&gt;
&lt;br /&gt;
./Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/7c07cdb6ff60ad1186dea33acdfb688668c2aae6/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L76 here in the Bisq code]. &lt;br /&gt;
&lt;br /&gt;
[[Running_from_the_command_line|More info on running from the command line]].&lt;br /&gt;
&lt;br /&gt;
[[Command_line_options|More info on command line options]].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=2999</id>
		<title>Connecting to your own Bitcoin node</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Connecting_to_your_own_Bitcoin_node&amp;diff=2999"/>
		<updated>2022-07-23T22:54:47Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* General node settings */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq will '''connect to your local Bitcoin node''' if it finds it upon starting up. This article contains the requirements for this to work correctly.&lt;br /&gt;
&lt;br /&gt;
You can also specify the addresses of particular Bitcoin nodes in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= General node settings =&lt;br /&gt;
&lt;br /&gt;
The bitcoin.conf file needs to contain the following settings (either by adding them or editing the existing ones):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;server=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;pruned=0&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;peerbloomfilters=1&amp;lt;/code&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
which in turn:&lt;br /&gt;
* enable the block server mode&lt;br /&gt;
* disable the pruning of old blocks&lt;br /&gt;
* allow Bisq to run its SPV wallet&lt;br /&gt;
&lt;br /&gt;
= Connecting to a local Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or &amp;lt;code&amp;gt;bitcoind&amp;lt;/code&amp;gt; running on &amp;lt;code&amp;gt;localhost&amp;lt;/code&amp;gt; on port 8333.&lt;br /&gt;
&lt;br /&gt;
Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.&lt;br /&gt;
&lt;br /&gt;
= Connecting to another Bitcoin node =&lt;br /&gt;
&lt;br /&gt;
By default, Bisq maximizes your privacy by connecting to nodes run by trusted  Bisq contributors. &lt;br /&gt;
&lt;br /&gt;
If you'd like to connect to another node, you can specify its address in &amp;lt;code&amp;gt;Settings&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Network Info&amp;lt;/code&amp;gt;. Bisq will validate the address and connect to the specified node the next time it starts.&lt;br /&gt;
&lt;br /&gt;
Bisq v1.7.4 and later releases support connecting to Bitcoin nodes with Tor v3 addresses. &lt;br /&gt;
&lt;br /&gt;
= Troubleshooting =&lt;br /&gt;
&lt;br /&gt;
If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows.  &lt;br /&gt;
&lt;br /&gt;
For MacOS:&lt;br /&gt;
 &amp;lt;code&amp;gt;Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
For Linux:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt; cd /opt/bisq/bin&lt;br /&gt;
&lt;br /&gt;
./Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true &amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Contributor nodes can be seen [https://github.com/bisq-network/bisq/blob/7c07cdb6ff60ad1186dea33acdfb688668c2aae6/core/src/main/java/bisq/core/btc/nodes/BtcNodes.java#L51-L76 here in the Bisq code]. &lt;br /&gt;
&lt;br /&gt;
[[Running_from_the_command_line|More info on running from the command line]].&lt;br /&gt;
&lt;br /&gt;
[[Command_line_options|More info on command line options]].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Troubleshooting_network_issues&amp;diff=2997</id>
		<title>Troubleshooting network issues</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Troubleshooting_network_issues&amp;diff=2997"/>
		<updated>2022-06-29T17:54:16Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* 3/4 connection problem */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;You may be experiencing '''network issues''' if you're stuck on Bisq's initial loading screen for a while. Often this results in a screen mentioning outdated Tor files and other Tor settings. This could occur for a number of reasons.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Weak internet connection ==&lt;br /&gt;
&lt;br /&gt;
Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to cause issues.&lt;br /&gt;
&lt;br /&gt;
== 3/4 connection problem ==&lt;br /&gt;
&lt;br /&gt;
If Bisq stalls at step 3/4 of the startup sequence for more than 5 minutes it means the initial data download from seednodes has failed, or is taking too long.&lt;br /&gt;
This can happen on weak or slow internet connections, or if Tor is having issues relaying the large data download to your node.&lt;br /&gt;
Proposed mitigation is to clear the Tor cachefiles. (Close Bisq first). All files except &amp;lt;code&amp;gt;hiddenservice&amp;lt;/code&amp;gt; can be deleted from &amp;lt;code&amp;gt;btc_mainnet/tor&amp;lt;/code&amp;gt; beneath the [[https://bisq.wiki/Data_directory#Default_locations data directory]], they will be re-created as necessary at startup.  &amp;lt;code&amp;gt;hiddenservice&amp;lt;/code&amp;gt; should be kept as it defines your onion address.&lt;br /&gt;
&lt;br /&gt;
See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843&lt;br /&gt;
&lt;br /&gt;
For a geekier approach, you can also try [[Manually_select_seednodes|manually choosing seednodes to connect to]]&lt;br /&gt;
&lt;br /&gt;
== Windows antivirus software ==&lt;br /&gt;
&lt;br /&gt;
Antivirus software is known to cause connection issues. Try turning it off to see if it helps Bisq to connect, and if it does, consider switching antivirus software or running Bisq on another operating system on which you don't need to run antivirus.&lt;br /&gt;
&lt;br /&gt;
== Being temporarily banned by the Tor network ==&lt;br /&gt;
&lt;br /&gt;
Trying to open Bisq too many times in a short timeframe can result in failing to connect to the Tor network. Simple wait 30-60 minutes and then try opening Bisq again.&lt;br /&gt;
&lt;br /&gt;
== Tor censorship ==&lt;br /&gt;
&lt;br /&gt;
In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.&lt;br /&gt;
&lt;br /&gt;
Tor is tries to fight such obstacles by providing ''bridges''. Bridges help you connect to the Tor network through a less well-known node. If you know someone who runs a bridge, you can ask to use their bridge, or you can go to https://bridges.torproject.org/bridges to pick a bridge listed by the Tor Project.&lt;br /&gt;
&lt;br /&gt;
If you're in China, [[在中国运行Bisq_(Running_Bisq_in_China)|this method using SStap]] has worked to get around the Great Firewall.&lt;br /&gt;
&lt;br /&gt;
==Tor bridges that don't work ==&lt;br /&gt;
&lt;br /&gt;
Some network administrators try really hard to block all Tor activity on their network (universities are infamous for this) and will even sometimes block specific types of SSL traffic and handshakes.&lt;br /&gt;
&lt;br /&gt;
In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.&lt;br /&gt;
&lt;br /&gt;
== Altcoin nodes running on the same computer ==&lt;br /&gt;
&lt;br /&gt;
Some forks of the Bitcoin repository (e.g., Litecoin, Dogecoin, etc) are known to cause issues with Bisq starting up. Bisq can sometimes recognize altcoin nodes as Bitcoin nodes, causing Bisq to try connecting to them and then failing when it finds no Bitcoin blocks.&lt;br /&gt;
&lt;br /&gt;
To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2996</id>
		<title>Manually select seednodes</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2996"/>
		<updated>2022-06-29T17:51:36Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one workaround that will increase your probability of correctly running Bisq.&lt;br /&gt;
&lt;br /&gt;
We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue'' in case your browser complains about the security of the page, they are just showing a large HTML table):&lt;br /&gt;
 - http://46.101.179.224:8080/&lt;br /&gt;
 - http://135.181.92.87:8080/&lt;br /&gt;
&lt;br /&gt;
What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).&lt;br /&gt;
&lt;br /&gt;
During high network instability, only a handful of seednodes will satisfy such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.&lt;br /&gt;
&lt;br /&gt;
Once you have copied those &amp;lt;code&amp;gt;address.onion:port&amp;lt;/code&amp;gt; strings, place them in a command line to start Bisq, appending them as a comma-separated list to the &amp;lt;code&amp;gt;-seednodes=&amp;lt;/code&amp;gt; option, like so for example (for Linux):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2995</id>
		<title>Manually select seednodes</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2995"/>
		<updated>2022-06-29T17:51:13Z</updated>

		<summary type="html">&lt;p&gt;W000000t: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one workaround that will increase your probability of correctly running Bisq.&lt;br /&gt;
&lt;br /&gt;
We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue'' in case your browser complains about the security of the page, they are just showing a large HTML table):&lt;br /&gt;
 - http://46.101.179.224:8080/&lt;br /&gt;
 - http://135.181.92.87:8080/&lt;br /&gt;
&lt;br /&gt;
What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large integer near ''Number of BSQ blocks'' (''171131'' at the time of writing).&lt;br /&gt;
&lt;br /&gt;
During high network instability, only a handful of seednodes will show such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.&lt;br /&gt;
&lt;br /&gt;
Once you have copied those &amp;lt;code&amp;gt;address.onion:port&amp;lt;/code&amp;gt; strings, place them in a command line to start Bisq, appending them as a comma-separated list to the &amp;lt;code&amp;gt;-seednodes=&amp;lt;/code&amp;gt; option, like so for example (for Linux):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2994</id>
		<title>Manually select seednodes</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Manually_select_seednodes&amp;diff=2994"/>
		<updated>2022-06-29T17:24:39Z</updated>

		<summary type="html">&lt;p&gt;W000000t: Created page with &amp;quot;If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one w...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If Tor network is experiencing issues, and seednodes are only partially operational, leading to frequent inability to connect to the p2p network, the following method is one workaround that will increase your probability of correctly running Bisq.&lt;br /&gt;
&lt;br /&gt;
We want to manually connect to seednodes that appear to be working, rather than having Bisq randomly choose them; reach the network monitors available at the following addresses (click ''Continue'' in case your browser complains about the security of the page, they are just showing a large HTML table):&lt;br /&gt;
 - http://46.101.179.224:8080/&lt;br /&gt;
 - http://135.181.92.87:8080/&lt;br /&gt;
&lt;br /&gt;
What you are looking for is in the '''Data inventory''' and '''DAO data''' columns, where you need to make sure that the former reports ''Number of Mediator: 2'' (do not mind skull and warning icons), and the latter shows a large number near ''Number of BSQ blocks'' (''171131'' at the time of writing).&lt;br /&gt;
&lt;br /&gt;
During high network instability, only a handful of seednodes will show such requirements, and the data will also change both with time, and between the two monitor URLs, so your job is to identify those (at least a couple, the more the merrier) that show most consistently stable over time on all monitors, and note down their ''Node address:'' under the '''Seed node info''' column.&lt;br /&gt;
&lt;br /&gt;
Once you have copied those &amp;lt;code&amp;gt;address.onion:port&amp;lt;/code&amp;gt; strings, place them in a command line to start Bisq, appending them as a comma-separated list to the &amp;lt;code&amp;gt;-seednodes=&amp;lt;/code&amp;gt; option, like so for example (for Linux):&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=2993</id>
		<title>Last resort restore</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Last_resort_restore&amp;diff=2993"/>
		<updated>2022-06-09T09:39:15Z</updated>

		<summary type="html">&lt;p&gt;W000000t: Created page with &amp;quot;Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful. The following is t...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Sometimes it will happen that your Bisq instance won't start, and you don't have backups, or your backups do not start as well, or are too old to be useful.&lt;br /&gt;
The following is to be intended as a hacky-workaround-last-resort-attempt to have Bisq start while retaining as much data as possible from the previous installation.&lt;br /&gt;
&lt;br /&gt;
=== Test with a fresh data directory ===&lt;br /&gt;
&lt;br /&gt;
First of all, make sure you have the latest version installed, and Bisq is closed (terminate orphan existing processes if any), then rename your [https://bisq.wiki/Data_directory#Default_locations data directory] by changing &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; to, for example, &amp;lt;code&amp;gt;Bisq.old&amp;lt;/code&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
Start Bisq again: it should start into a 100% new instance, creating a brand new &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt; folder (if it doesn't, try uninstalling and then reinstalling Bisq).&amp;lt;br&amp;gt;&lt;br /&gt;
Close Bisq again: we are going to use the freshly created Data Directory as a stump to populate with our old data.&lt;br /&gt;
&lt;br /&gt;
=== Import raw data from backup ===&lt;br /&gt;
&lt;br /&gt;
Open your renamed folder, get into the &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder, and sort files by &amp;quot;last modified&amp;quot; descending, you are looking for a series of file that were modified last, all of them in the same day (presumably the last day your Bisq was operational).&amp;lt;br&amp;gt;&lt;br /&gt;
The list should include:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;BsqSwapTrades&amp;lt;br&amp;gt;&lt;br /&gt;
DisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
RefundDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
SequenceNumberMap&amp;lt;br&amp;gt;&lt;br /&gt;
MyVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
OpenOffers&amp;lt;br&amp;gt;&lt;br /&gt;
MyBlindVoteList&amp;lt;br&amp;gt;&lt;br /&gt;
ClosedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MediationDisputeList&amp;lt;br&amp;gt;&lt;br /&gt;
MyProposalList&amp;lt;br&amp;gt;&lt;br /&gt;
MailboxMessageList&amp;lt;br&amp;gt;&lt;br /&gt;
AccountAgeWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
PendingTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyProofOfBurnList&amp;lt;br&amp;gt;&lt;br /&gt;
PreferencesPayload&amp;lt;br&amp;gt;&lt;br /&gt;
UserPayload&amp;lt;br&amp;gt;&lt;br /&gt;
AddressEntryList&amp;lt;br&amp;gt;&lt;br /&gt;
FailedTrades&amp;lt;br&amp;gt;&lt;br /&gt;
MyReputationList&amp;lt;br&amp;gt;&lt;br /&gt;
TempProposalStore&amp;lt;br&amp;gt;&lt;br /&gt;
NavigationPath&amp;lt;br&amp;gt;&lt;br /&gt;
UnconfirmedBsqChangeOutputList&amp;lt;br&amp;gt;&lt;br /&gt;
IgnoredMailboxMap&amp;lt;br&amp;gt;&lt;br /&gt;
PeerList&amp;lt;br&amp;gt;&lt;br /&gt;
RemovedPayloadsMap&amp;lt;br&amp;gt;&lt;br /&gt;
TradeStatistics3Store&amp;lt;br&amp;gt;&lt;br /&gt;
SignedWitnessStore&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Copy all the above files in the corresponding &amp;lt;code&amp;gt;btc_mainnet/db&amp;lt;/code&amp;gt; folder of your fresh data directory, overwriting the existing ones.&lt;br /&gt;
&lt;br /&gt;
Then, delete from the fresh data directory, and replace with copies from the old direcoty, the following folders:&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;btc_mainnet/keys&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/wallet&amp;lt;br&amp;gt;&lt;br /&gt;
btc_mainnet/tor/hiddenservice&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cross your fingers, and start Bisq again hoping that everything, including the state of trades and disputes, has been restored;if not, this is a reversible step as you can simply restore the existing old folder after deleting the fresh one you created.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2989</id>
		<title>Face-to-face (payment method)</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2989"/>
		<updated>2022-05-23T15:04:04Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Setting up a F2F account in Bisq */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq can help users arrange '''face-to-face''' (F2F) trades to buy and sell bitcoin. &lt;br /&gt;
&lt;br /&gt;
Done correctly, this may be the only payment method that can be both private ''and'' anonymous. But there are a number of things you should consider when doing a F2F trade on Bisq. &lt;br /&gt;
&lt;br /&gt;
F2F trades are ''technically'' very similar to online trades. In fact, to carry out a F2F trade, you follow the exact same process within the Bisq software as you would for any other trade. The difference is in how the buyer pays the seller: instead of paying through a financial intermediary (like a bank or other money transfer service), the buyer meets the seller in real life and pays with cash.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Setting up a F2F account in Bisq =&lt;br /&gt;
&lt;br /&gt;
When setting up a F2F payment account in Bisq, you will be asked to enter the following information:&lt;br /&gt;
&lt;br /&gt;
* Country&lt;br /&gt;
* Currency &lt;br /&gt;
* City (this will be displayed with the offer)&lt;br /&gt;
* Additional information  (for example where you would like to complete the trade, do NOT place direct contact information here!)&lt;br /&gt;
&lt;br /&gt;
You can only select one currency for a single F2F account. If you would like to trade with more than one currency, please create separate accounts for each currency.&lt;br /&gt;
&lt;br /&gt;
Define any special terms, conditions, or details you would like to be displayed with your offers in the 'Additional Information' field. '''Users can see this field ''before'' taking the offer by clicking the info icon of the offer.''' &lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Consider setting up separate F2F accounts for buying and selling so you can specify special instructions for each.}}&lt;br /&gt;
&lt;br /&gt;
= Making a F2F offer =&lt;br /&gt;
&lt;br /&gt;
Make sure to state any special terms or conditions in the 'Additional Information' field of the payment account before making an offer. The person taking the offer will be accepting these terms and conditions by taking the offer. For example you could include that you are looking to complete the trade in a Starbucks within the city center.&lt;br /&gt;
&lt;br /&gt;
Please note it is against Bisq rules to use the 'Additional Information' field to include advertising offers with a way to contact you prior to the trade (e.g. website, phone, email, or Matrix/Keybase/Telegram user name). Doing this can result in a penalty, should someone take your offer and request for you to be penalized.&lt;br /&gt;
&lt;br /&gt;
= Taking a F2F offer =&lt;br /&gt;
&lt;br /&gt;
'''Make sure to check the offer maker's terms and conditions before taking a F2F offer.''' If you cannot fulfill the terms, do not take the the offer. If you have specific terms you would prefer, consider making your own offer instead.&lt;br /&gt;
&lt;br /&gt;
== Meeting your trading partner ==&lt;br /&gt;
&lt;br /&gt;
Doing a transaction face-to-face means you’ll be coming within close proximity of a stranger to exchange relatively substantial value.&lt;br /&gt;
&lt;br /&gt;
=== Be safe ===&lt;br /&gt;
&lt;br /&gt;
People do local, in-person commerce all the time, all over the world. Incidents are rare, but they do happen. You should be cognizant of risks and do your part to minimize potential harm.&lt;br /&gt;
&lt;br /&gt;
'''Guard your data.''' When you set up a face-to-face payment account in Bisq, you’ll need to provide contact information so you can arrange a meeting with your trading partner. Make sure this information isn’t traceable back to your property or identity.&lt;br /&gt;
&lt;br /&gt;
'''Meet in a neutral public place.''' Meeting your trading partner in a place with witnesses and security cameras significantly reduces the chance of an incident.&lt;br /&gt;
&lt;br /&gt;
'''Don’t bring more than you need.''' Even in a public place, incidents can still happen, but you can limit the chance even further by limiting valuables on your person that would interest a thief in the first place.&lt;br /&gt;
&lt;br /&gt;
'''Bring backup.''' Consider bringing a friend with you. Also, depending on the laws in your area &amp;amp; your own comfort, consider carrying a concealed tool for self-defense. Even pepper-spray can hobble a criminal just enough to get you out of immediate danger.&lt;br /&gt;
&lt;br /&gt;
=== Validate payment ===&lt;br /&gt;
&lt;br /&gt;
Face-to-face trades are usually settled with cash. Cash is wonderfully anonymous, but it can be counterfeited. Be sure you know the basics of detecting counterfeit currency. For example, there are several characteristics of US dollar bills one can examine to quickly determine fakes with high accuracy.&lt;br /&gt;
&lt;br /&gt;
You could look for tools like counterfeit pens to do the work for you, but make sure you do thorough research before picking one. Counterfeit pens, for example, are often not reliable.&lt;br /&gt;
&lt;br /&gt;
If you’d rather not take the chance of carrying or accepting cash, consider meeting at a bank where you can validate a buyer’s payment on the spot.&lt;br /&gt;
&lt;br /&gt;
=== Ensure you follow Bisq protocol ===&lt;br /&gt;
&lt;br /&gt;
Ultimately, the deal will be completed in Bisq. Buyers must mark payment as sent before sellers can release assets.&lt;br /&gt;
&lt;br /&gt;
'''Buyers''' should bring a laptop with them so they can mark the payment as sent. Otherwise, the buyer will end up paying the seller and have to walk away without the bitcoin they paid for (since the seller won’t be able to acknowledge receipt of payment before the buyer acknowledges they sent payment).&lt;br /&gt;
&lt;br /&gt;
'''Sellers''' should bring a laptop with their Bisq client running no matter what. Once they receive a legitimate payment, they’ll need to mark the payment as received so the assets are released to the buyer. No buyer will want to walk away after paying without proof of a complete deal.&lt;br /&gt;
&lt;br /&gt;
== Disputes ==&lt;br /&gt;
&lt;br /&gt;
The lack of verifiable actions makes handling face-to-face disputes much harder.&lt;br /&gt;
&lt;br /&gt;
This is why we highly recommend that both parties bring laptops and acknowledge their ends of the deal on the spot.&lt;br /&gt;
&lt;br /&gt;
Otherwise, the same dispute process is in place for F2F trades, but be advised that mediators and arbitrators often won’t have a way to settle disputes. In such cases, aggrieved traders can send deposit funds to the donation address and [[Making_a_reimbursement_request|make an appeal to the Bisq DAO]].&lt;br /&gt;
&lt;br /&gt;
Having said that, mediators and arbitrators may attempt different tactics to get a handle on the situation. For example, they may ask a potential scammer for ID verification, which is a request a real scammer probably wouldn’t comply with.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2988</id>
		<title>Face-to-face (payment method)</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2988"/>
		<updated>2022-05-23T15:01:12Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Setting up a F2F account in Bisq */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq can help users arrange '''face-to-face''' (F2F) trades to buy and sell bitcoin. &lt;br /&gt;
&lt;br /&gt;
Done correctly, this may be the only payment method that can be both private ''and'' anonymous. But there are a number of things you should consider when doing a F2F trade on Bisq. &lt;br /&gt;
&lt;br /&gt;
F2F trades are ''technically'' very similar to online trades. In fact, to carry out a F2F trade, you follow the exact same process within the Bisq software as you would for any other trade. The difference is in how the buyer pays the seller: instead of paying through a financial intermediary (like a bank or other money transfer service), the buyer meets the seller in real life and pays with cash.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Setting up a F2F account in Bisq =&lt;br /&gt;
&lt;br /&gt;
When setting up a F2F payment account in Bisq, you will be asked to enter the following information:&lt;br /&gt;
&lt;br /&gt;
* Country&lt;br /&gt;
* Currency &lt;br /&gt;
* City (this will be displayed with the offer)&lt;br /&gt;
* Additional information  (for example where you would like to complete the trade.)&lt;br /&gt;
&lt;br /&gt;
You can only select one currency for a single F2F account. If you would like to trade with more than one currency, please create separate accounts for each currency.&lt;br /&gt;
&lt;br /&gt;
Define any special terms, conditions, or details you would like to be displayed with your offers in the 'Additional Information' field. '''Users can see this field ''before'' taking the offer by clicking the info icon of the offer.''' &lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Consider setting up separate F2F accounts for buying and selling so you can specify special instructions for each.}}&lt;br /&gt;
&lt;br /&gt;
= Making a F2F offer =&lt;br /&gt;
&lt;br /&gt;
Make sure to state any special terms or conditions in the 'Additional Information' field of the payment account before making an offer. The person taking the offer will be accepting these terms and conditions by taking the offer. For example you could include that you are looking to complete the trade in a Starbucks within the city center.&lt;br /&gt;
&lt;br /&gt;
Please note it is against Bisq rules to use the 'Additional Information' field to include advertising offers with a way to contact you prior to the trade (e.g. website, phone, email, or Matrix/Keybase/Telegram user name). Doing this can result in a penalty, should someone take your offer and request for you to be penalized.&lt;br /&gt;
&lt;br /&gt;
= Taking a F2F offer =&lt;br /&gt;
&lt;br /&gt;
'''Make sure to check the offer maker's terms and conditions before taking a F2F offer.''' If you cannot fulfill the terms, do not take the the offer. If you have specific terms you would prefer, consider making your own offer instead.&lt;br /&gt;
&lt;br /&gt;
== Meeting your trading partner ==&lt;br /&gt;
&lt;br /&gt;
Doing a transaction face-to-face means you’ll be coming within close proximity of a stranger to exchange relatively substantial value.&lt;br /&gt;
&lt;br /&gt;
=== Be safe ===&lt;br /&gt;
&lt;br /&gt;
People do local, in-person commerce all the time, all over the world. Incidents are rare, but they do happen. You should be cognizant of risks and do your part to minimize potential harm.&lt;br /&gt;
&lt;br /&gt;
'''Guard your data.''' When you set up a face-to-face payment account in Bisq, you’ll need to provide contact information so you can arrange a meeting with your trading partner. Make sure this information isn’t traceable back to your property or identity.&lt;br /&gt;
&lt;br /&gt;
'''Meet in a neutral public place.''' Meeting your trading partner in a place with witnesses and security cameras significantly reduces the chance of an incident.&lt;br /&gt;
&lt;br /&gt;
'''Don’t bring more than you need.''' Even in a public place, incidents can still happen, but you can limit the chance even further by limiting valuables on your person that would interest a thief in the first place.&lt;br /&gt;
&lt;br /&gt;
'''Bring backup.''' Consider bringing a friend with you. Also, depending on the laws in your area &amp;amp; your own comfort, consider carrying a concealed tool for self-defense. Even pepper-spray can hobble a criminal just enough to get you out of immediate danger.&lt;br /&gt;
&lt;br /&gt;
=== Validate payment ===&lt;br /&gt;
&lt;br /&gt;
Face-to-face trades are usually settled with cash. Cash is wonderfully anonymous, but it can be counterfeited. Be sure you know the basics of detecting counterfeit currency. For example, there are several characteristics of US dollar bills one can examine to quickly determine fakes with high accuracy.&lt;br /&gt;
&lt;br /&gt;
You could look for tools like counterfeit pens to do the work for you, but make sure you do thorough research before picking one. Counterfeit pens, for example, are often not reliable.&lt;br /&gt;
&lt;br /&gt;
If you’d rather not take the chance of carrying or accepting cash, consider meeting at a bank where you can validate a buyer’s payment on the spot.&lt;br /&gt;
&lt;br /&gt;
=== Ensure you follow Bisq protocol ===&lt;br /&gt;
&lt;br /&gt;
Ultimately, the deal will be completed in Bisq. Buyers must mark payment as sent before sellers can release assets.&lt;br /&gt;
&lt;br /&gt;
'''Buyers''' should bring a laptop with them so they can mark the payment as sent. Otherwise, the buyer will end up paying the seller and have to walk away without the bitcoin they paid for (since the seller won’t be able to acknowledge receipt of payment before the buyer acknowledges they sent payment).&lt;br /&gt;
&lt;br /&gt;
'''Sellers''' should bring a laptop with their Bisq client running no matter what. Once they receive a legitimate payment, they’ll need to mark the payment as received so the assets are released to the buyer. No buyer will want to walk away after paying without proof of a complete deal.&lt;br /&gt;
&lt;br /&gt;
== Disputes ==&lt;br /&gt;
&lt;br /&gt;
The lack of verifiable actions makes handling face-to-face disputes much harder.&lt;br /&gt;
&lt;br /&gt;
This is why we highly recommend that both parties bring laptops and acknowledge their ends of the deal on the spot.&lt;br /&gt;
&lt;br /&gt;
Otherwise, the same dispute process is in place for F2F trades, but be advised that mediators and arbitrators often won’t have a way to settle disputes. In such cases, aggrieved traders can send deposit funds to the donation address and [[Making_a_reimbursement_request|make an appeal to the Bisq DAO]].&lt;br /&gt;
&lt;br /&gt;
Having said that, mediators and arbitrators may attempt different tactics to get a handle on the situation. For example, they may ask a potential scammer for ID verification, which is a request a real scammer probably wouldn’t comply with.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2982</id>
		<title>Frequently asked questions</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2982"/>
		<updated>2022-04-28T20:21:37Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project. &lt;br /&gt;
&lt;br /&gt;
Feel free to ask further questions on any of Bisq's many outreach channels. &lt;br /&gt;
&lt;br /&gt;
== About ==&lt;br /&gt;
&lt;br /&gt;
==== How is Bisq different from other decentralized exchanges? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is a peer-to-peer trading network, not a website or &amp;quot;app&amp;quot; or other centralized service. It's software you run on your own hardware, which connects to other people running the Bisq software to facilitate trades. It's open-source and community-driven.&lt;br /&gt;
&lt;br /&gt;
And you can trade bitcoin for fiat currencies with it!&lt;br /&gt;
&lt;br /&gt;
The difference between Bisq and other so-called decentralized exchanges is as stark as the difference between owning your own home and renting someone else's—in the former case you have full control over the property, and in the latter you're always subject to the landlord's whims and demands (no matter how nice the landlord may seem to be).&lt;br /&gt;
&lt;br /&gt;
With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.&lt;br /&gt;
&lt;br /&gt;
* Bisq does not hold any bitcoin. All bitcoin used for trading is held in '''2-of-2 multisignature addresses''' controlled solely by the trading peers themselves.&lt;br /&gt;
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.&lt;br /&gt;
* All Bisq data is transferred over its own secure peer-to-peer network, which is built on top of the Tor network—no central servers. This means '''there are no data honeypots''', rendering large-scale hacks of customer information databases impossible.&lt;br /&gt;
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.&lt;br /&gt;
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.&lt;br /&gt;
* Bisq is code, not a company. It is an open-source project organized as a [[Decentralized_autonomous_organization|decentralized autonomous organization (DAO)]] built on top of Bitcoin.&lt;br /&gt;
&lt;br /&gt;
See more in the [[Introduction]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq open-source software? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License. &lt;br /&gt;
&lt;br /&gt;
Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq safe? ====&lt;br /&gt;
&lt;br /&gt;
Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.&lt;br /&gt;
&lt;br /&gt;
Bisq employs three primary mechanisms to achieve security:&lt;br /&gt;
&lt;br /&gt;
* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.&lt;br /&gt;
* Both traders are required to pay security deposits, which are refunded after trades are completed.&lt;br /&gt;
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.&lt;br /&gt;
&lt;br /&gt;
To mitigate this risk, Bisq:&lt;br /&gt;
&lt;br /&gt;
* only supports payment methods which are known to make chargebacks difficult—this is why Bisq does not support PayPal and credit cards, for example. See more on chargeback risks.&lt;br /&gt;
* employs an [[Account_limits#Account_signing account|signing mechanism]] that forces 0.01 BTC buy limits until a buyer's integrity (not identity!) is verified.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====&lt;br /&gt;
&lt;br /&gt;
Some people find Bisq's interface intuitive, but many people don't. Check out [https://www.youtube.com/watch?v=HDkzUl9wibc this tour video] to help you make sense of the interface, and then check out the [https://www.youtube.com/watch?v=QjmpAq9RUXM Bird's Eye View of a Bisq Trade] video for a high-level overview of how Bisq trading works.&lt;br /&gt;
&lt;br /&gt;
Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.&lt;br /&gt;
&lt;br /&gt;
As of April 2021, Bisq contributors have designed a whole new beautiful interface that should make Bisq significantly more intuitive, and are also in touch with a talented UI developer to turn the design into code. You can follow progress on this initiative [https://github.com/bisq-network/projects/issues/49 here].&lt;br /&gt;
&lt;br /&gt;
==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
While Bisq can technically support any market, only a handful of markets are consistently active on Bisq—mainly because they offer good payment methods and had strong on-the-ground support to bootstrap them in the beginning.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Note that a weak offer book in a particular market doesn't ''necessarily'' mean trades don't take place in that market. It could be that there are people lurking there that will happily take an offer if you take the initiative to make one (this is often the case in markets like CAD, AUD, and GBP, for example).&lt;br /&gt;
&lt;br /&gt;
You can check trade history for your market by going to &amp;lt;code&amp;gt;Market&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Trades&amp;lt;/code&amp;gt; and picking your currency from the dropdown.}}&lt;br /&gt;
&lt;br /&gt;
If your market has no recent trades, a little more work will need to be done to get it going. At a minimum, payment methods common in your market should be added ([https://github.com/bisq-network/growth/issues/new/choose suggest them here]), and some form of marketing should be done to get users and market-makers to bootstrap a market.&lt;br /&gt;
&lt;br /&gt;
Bisq contributors are more than happy to help if you can help with guidance, connections to people who can help, and/or events and translations and other vehicles for reaching your target demographics.&lt;br /&gt;
&lt;br /&gt;
==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
Yes, the chicken-and-egg problem with Bisq is real. &lt;br /&gt;
&lt;br /&gt;
Here are some ways to get just enough bitcoin to do your first trade on Bisq:&lt;br /&gt;
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]&lt;br /&gt;
* hop onto the &amp;lt;code&amp;gt;Get your first BTC&amp;lt;/code&amp;gt; room on [https://bisq.chat Matrix] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])&lt;br /&gt;
&lt;br /&gt;
== Trading ==&lt;br /&gt;
&lt;br /&gt;
==== What are trading fees? ====&lt;br /&gt;
&lt;br /&gt;
[[Trading fees]] are calculated as a percentage of trade size: 0.1% for makers and 0.7% for takers if paid in BTC and about half of that if paid in BSQ.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that you'll also need to pay [[mining fees]] for the on-chain transactions, as well as a deposit to lock into the multisig escrow. You'll get the deposit back in full after the trade completes successfully.&lt;br /&gt;
&lt;br /&gt;
==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.&lt;br /&gt;
&lt;br /&gt;
Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.&lt;br /&gt;
&lt;br /&gt;
Other things you can do: &lt;br /&gt;
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)&lt;br /&gt;
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)&lt;br /&gt;
&lt;br /&gt;
==== Why does Bisq require a security deposit in BTC? ====&lt;br /&gt;
&lt;br /&gt;
[[Security deposit | Security deposits]] create strong incentives for buyers and sellers to follow the [[Trading rules|rules of Bisq's trading protocol]]. Deposits are locked into multisig escrow along with the bitcoin being traded, and are returned to each user when the trade is complete.&lt;br /&gt;
&lt;br /&gt;
If a trade is disputed through a mediator or arbitrator, some or all of the offending party's security deposit may be awarded to the counterparty. Examples of protocol violations include a buyer failing to pay a seller, paying with a different account or with a different name, or a seller failing to acknowledge receipt of a buyer's payment.&lt;br /&gt;
&lt;br /&gt;
Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.&lt;br /&gt;
&lt;br /&gt;
See full [[trading rules]].&lt;br /&gt;
&lt;br /&gt;
==== What are trading limits? How much bitcoin can I buy/sell at once? ====&lt;br /&gt;
&lt;br /&gt;
Trading limits vary based on payment method, since some payment methods are more secure than others.&lt;br /&gt;
&lt;br /&gt;
Relatively safe payment methods such as Japan's Furikomi and Australia's PayID are set to allow trades of up to 1 BTC, but other payment methods such as Zelle and SEPA have a cap of 0.25 BTC. See the [[Payment_methods|full list of payment methods and limits]].&lt;br /&gt;
&lt;br /&gt;
Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.&lt;br /&gt;
&lt;br /&gt;
==== Which payment methods are available? ====&lt;br /&gt;
&lt;br /&gt;
See [[payment methods]].&lt;br /&gt;
&lt;br /&gt;
If you'd like to suggest a payment method to be added, please [https://github.com/bisq-network/growth/issues/new/choose submit a new issue].&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq handle fiat like dollars and euros? Where does it go? ====&lt;br /&gt;
&lt;br /&gt;
Bisq doesn't handle fiat at all -- it only handles BTC. Trades are settled outside of Bisq, meaning fiat payments are sent outside Bisq via traditional banking services.&lt;br /&gt;
&lt;br /&gt;
Bisq merely matches peers and sets incentives (e.g. locking a BTC security deposit from both peers, as a sort of escrow) to encourage both trading peers to act in good faith. This is also why you need bitcoin to begin trading on Bisq.&lt;br /&gt;
&lt;br /&gt;
==== How long does a trade take? ====&lt;br /&gt;
&lt;br /&gt;
There is no automatic order matching on Bisq, and trades are settled manually by humans. As a result, trades are not completed as quickly as they would be on centralized exchanges, but can still be fairly quick. &lt;br /&gt;
&lt;br /&gt;
Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).&lt;br /&gt;
&lt;br /&gt;
As far as Bisq is concerned, the deposit transaction needs to be confirmed once before the buyer can send payment. Bitcoin transactions take about 10 minutes to confirm, so with quick traders and quick payment method, a Bisq trade can be completed in a matter of minutes.&lt;br /&gt;
&lt;br /&gt;
Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).&lt;br /&gt;
&lt;br /&gt;
See the list of [[payment methods]] for complete details.&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq protect my privacy? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is standalone, open-source software that you can inspect before running on your machine, and as a result, you don't have to trust that any server is logging your personal details (as you would in the case of a website).&lt;br /&gt;
&lt;br /&gt;
As for the trading process, your payment information is stored locally on your machine, and only your trading partner (and your mediator or arbitrator, in case of a dispute) can ever see it. All data exchanged between users is encrypted and signed.&lt;br /&gt;
&lt;br /&gt;
To transmit data from one user to another, Bisq uses a P2P network built on top of Tor, which provides a high degree of anonymity. The user doesn't need to do any additional work for all of this to work—it is all integrated in the application.&lt;br /&gt;
&lt;br /&gt;
==== Do I need to keep Bisq online for my offers to remain online? ====&lt;br /&gt;
&lt;br /&gt;
Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.&lt;br /&gt;
&lt;br /&gt;
If you have published an offer, your Bisq application needs to stay online so it can react when another trader wants to take your offer (the multisig deposit transaction is created in the take-offer process). Be sure you have deactivated your computer's standby mode so your Bisq application can stay online (monitor standby is not a problem).&lt;br /&gt;
&lt;br /&gt;
If your Bisq application does go offline, your offer will get removed from the distributed offerbook. It will be re-published the next time you start your Bisq application.&lt;br /&gt;
&lt;br /&gt;
After an offer has been taken and the trade process has started, neither trader needs to be online continuously, but each trader will need to be online periodically to check if any action is needed on their side (e.g. sending fiat/altcoin, confirming payment receipt, etc).&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq wallet? ====&lt;br /&gt;
&lt;br /&gt;
No, but you may find it convenient to keep a small amount of trading capital there.&lt;br /&gt;
&lt;br /&gt;
When entering a new trade on Bisq, you will get the option to transfer funds from your Bisq wallet ''or'' send funds from an external wallet.&lt;br /&gt;
&lt;br /&gt;
Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq token? ====&lt;br /&gt;
&lt;br /&gt;
No, using BSQ is totally optional. However, using it gets you a ~50% discount on [[trading fees]] while helping to [[Introduction_to_the_DAO#Earn_and_distribute_revenue|compensate Bisq contributors]] at the same time.&lt;br /&gt;
&lt;br /&gt;
==== Will my bank know I'm trading bitcoin? ====&lt;br /&gt;
&lt;br /&gt;
Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.&lt;br /&gt;
&lt;br /&gt;
But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the &amp;quot;reason for payment&amp;quot; field always be left BLANK when making a payment (if the payment method offers such a field).&lt;br /&gt;
&lt;br /&gt;
If a reason is required, it should be something trivial like a &amp;quot;-&amp;quot; or &amp;quot;payment&amp;quot;. If you want to use something else, please agree on an alternative with your peer using trader chat.&lt;br /&gt;
See full [[trading rules]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Common Technical Niggles ==&lt;br /&gt;
&lt;br /&gt;
==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ==== &lt;br /&gt;
&lt;br /&gt;
If Bisq won't open, try right-clicking the app and clicking &amp;lt;code&amp;gt;Open&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If you get the prompt asking to record your keystrokes, rest assured it's a [https://github.com/bisq-network/bisq/issues/3373 bug] (Bisq is absolutely not recording your keystrokes). This bug should be fixed with a [[https://github.com/bisq-network/projects/issues/44|Java LTS version update]] coming soon.&lt;br /&gt;
&lt;br /&gt;
==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has had memory usage and CPU usage issue on certain operating systems in the past, but these issues should be resolved now. You can manually set the max RAM usage by following [[Reducing_memory_usage|these instructions]].&lt;br /&gt;
&lt;br /&gt;
Chances are Bisq is probably just trying to sync blockchain data. New releases of Bisq include data stores updated at release time to reduce this syncing time, but as a release gets older (i.e., beyond 3-4 weeks old), the data stores get older, and syncing takes longer. Just let it finish and your computer resources should go back down to normal again.&lt;br /&gt;
&lt;br /&gt;
If the issue doesn't go away on its own, please reach out for help in the &amp;lt;code&amp;gt;Support&amp;lt;/code&amp;gt; room [https://bisq.chat on Matrix] or open an issue [https://github.com/bisq-network/bisq on GitHub].&lt;br /&gt;
&lt;br /&gt;
==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====&lt;br /&gt;
&lt;br /&gt;
See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.&lt;br /&gt;
&lt;br /&gt;
==== Bisq says &amp;quot;this offer cannot be taken due to counterparty trade restrictions&amp;quot;. What does that mean? ====&lt;br /&gt;
&lt;br /&gt;
This happens in rare circumstances.  Bisq checks information about an account such as its age to determine if it is allowed to trade over certain limits.  The information is stored in the P2P network, and it may not yet have propagated to your node.  Try again after restarting Bisq.  The offer maker may need to restart Bisq in order for the information to propagate.&lt;br /&gt;
&lt;br /&gt;
==== My SPV resync is taking all day and it keeps freezing.  What can I do to make it go faster? ====&lt;br /&gt;
&lt;br /&gt;
Unfortunately this can happen sometimes if your wallet is over a year old and/or has a lot of transactions.  If the resync stalls, close and restart Bisq to continue the resync.  It will go faster if you [[Connecting_to_your_own_Bitcoin_node|connect to a local Bitcoin node]].&lt;br /&gt;
After your SPV resync is completed, it would be best to switch to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====&lt;br /&gt;
&lt;br /&gt;
The procedure involves setting aside the existing wallet directory (by renaming) in order to get a fresh wallet.  The wallet directory is at &amp;lt;code&amp;gt;btc_mainnet/wallet&amp;lt;/code&amp;gt; from the [[Data_directory|main data directory location]].  You'll then be able to activate either the old or new wallet by renaming the directory before starting Bisq.  Be sure that Bisq is never running when you rename a directory.&lt;br /&gt;
# You have some BSQ and also some BTC balance existing in your wallet.  (You need BTC to pay mining fees for sending BSQ).  &lt;br /&gt;
# Close Bisq then rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; directory to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt;. &lt;br /&gt;
# Start Bisq and it will create a fresh wallet.  Note down your BSQ receiving address and also your BTC receiving address.  Write down your recovery seed phrase (Under Account / Wallet Seed menu) and store it in a safe place (not online).  &lt;br /&gt;
# Close Bisq and rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; dir to &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt;, rename your old wallet dir to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;, then restart Bisq.  &lt;br /&gt;
# Send BSQ to your new receiving address you saved in the earlier step.  Then send BTC the same way.  Close Bisq.  &lt;br /&gt;
# Rename &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;.  Then restart Bisq.&lt;br /&gt;
&lt;br /&gt;
Done!  Your BSQ and BTC balances have been moved to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;heightOfLastBlock must match chainHeight&amp;quot; error on starting Bisq ====&lt;br /&gt;
&lt;br /&gt;
The following procedure should fix itː&lt;br /&gt;
* make a backup of your data folder&lt;br /&gt;
* close Bisq&lt;br /&gt;
* from inside data folder, delete DaoStateStore and BsqBlocks&lt;br /&gt;
* restart Bisq&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; ====&lt;br /&gt;
&lt;br /&gt;
This is a known issue, stemming from how the application will err on the side of caution when P2P network conditions are less than favorable.&lt;br /&gt;
It most often happens when the peer is offline, so usually when a seller taker accepts an open offer with a non-instant payment method, like SEPA, and then goes offline, since the payment will take at least a day to be credited and they do not need to stay connected while the buyer maker's payment arrives.&lt;br /&gt;
Here are some things that might work&lt;br /&gt;
* Send a message in trader chat&lt;br /&gt;
* Insist on pressing the button tens of times&lt;br /&gt;
* Restart Bisq&lt;br /&gt;
* Follow menus '''Settings''' -&amp;gt; '''Network Info''' -&amp;gt; '''Open Tor Settings''' -&amp;gt; '''Delete Outdated Tor Files And Shutdown''', then restart Bisq&lt;br /&gt;
* Do nothing and stay online, as the button will sometimes finally &amp;quot;register&amp;quot; by itself with a random delay&lt;br /&gt;
* When everything else fails, and the trade period is almost at its end, communicate your intentions to the peer in trader chat and open mediation by pressing Ctrl-O in trade window, explaining what happened to the mediator, even better by attaching a screenshot of the issue; a support ticket will be opened and both peers will have the opportunity to accept the original payout&lt;br /&gt;
&lt;br /&gt;
==== I want to install Bisq on a VPS or on an otherwise headless system ====&lt;br /&gt;
&lt;br /&gt;
Bisq needs a graphical desktop environment to be ran, but in order to keep offers online without the need to have your PC always on, some users reported good results by using https://www.xpra.org as a graphical endpoint which you can forward to a client.&lt;br /&gt;
&lt;br /&gt;
== Dispute resolution ==&lt;br /&gt;
&lt;br /&gt;
==== How does dispute resolution work? ====&lt;br /&gt;
&lt;br /&gt;
Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
Trader chat enables traders to resolve small issues themselves privately over end-to-end encrypted chat right in Bisq. If this doesn't work, traders can engage a mediator to examine the situation and suggest a payout. In rare circumstances that mediation fails, a trader can choose to engage an arbitrator to re-examine the situation and make a payout.&lt;br /&gt;
&lt;br /&gt;
Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.&lt;br /&gt;
&lt;br /&gt;
See [[trading rules]] and [[dispute resolution]] for more.&lt;br /&gt;
&lt;br /&gt;
==== How is collusion between mediators, arbitrators, and traders prevented? ====&lt;br /&gt;
&lt;br /&gt;
With the launch of the new trading protocol in v1.2, multisig escrows went from 2-of-3 to 2-of-2 arrangements, so that only the two trading peers have control of trading funds (instead of the 2 trading peers and an arbitrator). With no keys in the multisig escrow, it is no longer possible for a mediator or arbitrator to collude with another trader to release funds maliciously.&lt;br /&gt;
&lt;br /&gt;
Mediators and arbitrators are still bonded roles, however, because even though they cannot sign a payout transaction to resolve a dispute, they can ''advise'' how to resolve a dispute, and it's important that they be responsive, responsible, and fair when doing so.&lt;br /&gt;
&lt;br /&gt;
==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====&lt;br /&gt;
&lt;br /&gt;
Bisq only supports payment methods for which chargebacks are not easy (e.g., this is why PayPal and credit cards are not supported). But there is still a little chargeback risk with banks. If a bank executes a chargeback after the BTC has been released, there is nothing a mediator or arbitrator can do.&lt;br /&gt;
&lt;br /&gt;
Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:&lt;br /&gt;
&lt;br /&gt;
# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.&lt;br /&gt;
# [[Account_limits#Account_signing|Account signing]] requires higher-risk payment methods to be signed upon verifying the integrity of a trader before account aging kicks in. Until such accounts are signed, buy limits are set to 0.01 BTC.&lt;br /&gt;
# National currency payment methods which are found to be used for chargebacks are quickly removed.&lt;br /&gt;
&lt;br /&gt;
==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====&lt;br /&gt;
&lt;br /&gt;
Pure reputation without additional dispute resolution measures is a weak protection system, as you can never avoid [https://en.wikipedia.org/wiki/Sybil_attack sybil] or [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks.&lt;br /&gt;
&lt;br /&gt;
Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.&lt;br /&gt;
&lt;br /&gt;
==== How can I contact my trading peer? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has a built-in end-to-end encrypted [[Dispute_resolution#Level_1:_Trader_chat|chat mechanism]] that you can use to talk to your trading peer while the trade is in progress.&lt;br /&gt;
&lt;br /&gt;
== DAO ==&lt;br /&gt;
&lt;br /&gt;
==== What is the Bisq DAO? ====&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO (decentralized autonomous organization) is a decentralized governance mechanism for the Bisq software, built on Bitcoin. It takes the place of a company. How good can decentralized software possibly be if it's still controlled by a single entity, like a company?&lt;br /&gt;
&lt;br /&gt;
Decentralized software is no good without decentralized governance.&lt;br /&gt;
&lt;br /&gt;
That's why Bisq is not a company or legal entity of any kind—instead, it's organized as a DAO. The DAO handles the software's funding and strategy-making to enable the Bisq network to thrive, and at the same time, harden it against attacks on the infrastructure that powers its leadership and operation.&lt;br /&gt;
&lt;br /&gt;
In a nutshell, the Bisq DAO enables Bisq to become even more censorship-resistant, a core [[Introduction|principle of the project]] from the very beginning.&lt;br /&gt;
&lt;br /&gt;
Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].&lt;br /&gt;
&lt;br /&gt;
==== How does the Bisq DAO work? ====&lt;br /&gt;
&lt;br /&gt;
The primary purposes of the Bisq DAO are financing the project and determining strategy.&lt;br /&gt;
&lt;br /&gt;
# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.&lt;br /&gt;
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.&lt;br /&gt;
&lt;br /&gt;
Learn more about how this actually works in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this series of short 3-5 minute videos].&lt;br /&gt;
&lt;br /&gt;
See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.&lt;br /&gt;
&lt;br /&gt;
==== What do I need to know about the DAO, as a trader? ====&lt;br /&gt;
&lt;br /&gt;
First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.&lt;br /&gt;
&lt;br /&gt;
But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.&lt;br /&gt;
&lt;br /&gt;
But why have the BSQ token at all? Because it enables Bisq contributors to be paid for their work without any central wallets or points of control. When you buy BSQ, you're directly paying a Bisq contributor for their work, and in the process, helping to sustain the whole project. The dynamic this token enables is not possible with plain bitcoin.&lt;br /&gt;
&lt;br /&gt;
When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.&lt;br /&gt;
&lt;br /&gt;
[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====&lt;br /&gt;
&lt;br /&gt;
Bisq already earns revenue from trading fees. It's not launching this DAO and BSQ token for ''earning'' revenue—it's doing it to ''distribute'' the revenue it already earns to more people without any central points of control.&lt;br /&gt;
&lt;br /&gt;
BSQ tokens are issued every time a contributor's compensation request is approved through voting, and the tokens are destroyed every time a trader uses BSQ to pay trading fees.&lt;br /&gt;
&lt;br /&gt;
BSQ issuance is not a 1-time event, and its purpose is not to raise capital. You can see a walk-through of the BSQ issuance process in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this video series].&lt;br /&gt;
&lt;br /&gt;
==== Can I use Bisq without BSQ and without this DAO? ====&lt;br /&gt;
&lt;br /&gt;
You could. All you'd have to do is pay your trading fees with BTC instead of BSQ. But we hope you don't, because doing so would render the project unsustainable.&lt;br /&gt;
&lt;br /&gt;
Before the Bisq DAO, trading fees went to just a couple of wallets owned by specific Bisq contributors (arbitrators). All other contributors were not paid. Bisq needs its contributors to be paid in regular, predictable ways to ensure continual (and reliable) development, service, and growth; the Bisq DAO enables this to happen by distributing trading fees to all contributors in a totally decentralized way.&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO and BSQ token enable a funding and governance mechanism that is [[https://bisq.network/blog/bisq-dao-for-bitcoin-maximalists/ not possible with plain bitcoin]]. We highly recommend you check [[Decentralized_autonomous_organization|out the documentation]] and [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e video series]] to learn more.&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
==== This project is cool! How can I help out? ====&lt;br /&gt;
&lt;br /&gt;
Check out the [[contributor checklist]]. We'd love to hear from you!&lt;br /&gt;
&lt;br /&gt;
==== I have a question that isn’t covered here...? ====&lt;br /&gt;
&lt;br /&gt;
Feel free to reach out on [https://bisq.chat Matrix] or [https://bisq.network/#community any other channel].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2981</id>
		<title>Frequently asked questions</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2981"/>
		<updated>2022-04-24T15:29:38Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Common Technical Niggles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project. &lt;br /&gt;
&lt;br /&gt;
Feel free to ask further questions on any of Bisq's many outreach channels. &lt;br /&gt;
&lt;br /&gt;
== About ==&lt;br /&gt;
&lt;br /&gt;
==== How is Bisq different from other decentralized exchanges? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is a peer-to-peer trading network, not a website or &amp;quot;app&amp;quot; or other centralized service. It's software you run on your own hardware, which connects to other people running the Bisq software to facilitate trades. It's open-source and community-driven.&lt;br /&gt;
&lt;br /&gt;
And you can trade bitcoin for fiat currencies with it!&lt;br /&gt;
&lt;br /&gt;
The difference between Bisq and other so-called decentralized exchanges is as stark as the difference between owning your own home and renting someone else's—in the former case you have full control over the property, and in the latter you're always subject to the landlord's whims and demands (no matter how nice the landlord may seem to be).&lt;br /&gt;
&lt;br /&gt;
With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.&lt;br /&gt;
&lt;br /&gt;
* Bisq does not hold any bitcoin. All bitcoin used for trading is held in '''2-of-2 multisignature addresses''' controlled solely by the trading peers themselves.&lt;br /&gt;
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.&lt;br /&gt;
* All Bisq data is transferred over its own secure peer-to-peer network, which is built on top of the Tor network—no central servers. This means '''there are no data honeypots''', rendering large-scale hacks of customer information databases impossible.&lt;br /&gt;
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.&lt;br /&gt;
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.&lt;br /&gt;
* Bisq is code, not a company. It is an open-source project organized as a [[Decentralized_autonomous_organization|decentralized autonomous organization (DAO)]] built on top of Bitcoin.&lt;br /&gt;
&lt;br /&gt;
See more in the [[Introduction]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq open-source software? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License. &lt;br /&gt;
&lt;br /&gt;
Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq safe? ====&lt;br /&gt;
&lt;br /&gt;
Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.&lt;br /&gt;
&lt;br /&gt;
Bisq employs three primary mechanisms to achieve security:&lt;br /&gt;
&lt;br /&gt;
* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.&lt;br /&gt;
* Both traders are required to pay security deposits, which are refunded after trades are completed.&lt;br /&gt;
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.&lt;br /&gt;
&lt;br /&gt;
To mitigate this risk, Bisq:&lt;br /&gt;
&lt;br /&gt;
* only supports payment methods which are known to make chargebacks difficult—this is why Bisq does not support PayPal and credit cards, for example. See more on chargeback risks.&lt;br /&gt;
* employs an [[Account_limits#Account_signing account|signing mechanism]] that forces 0.01 BTC buy limits until a buyer's integrity (not identity!) is verified.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====&lt;br /&gt;
&lt;br /&gt;
Some people find Bisq's interface intuitive, but many people don't. Check out [https://www.youtube.com/watch?v=HDkzUl9wibc this tour video] to help you make sense of the interface, and then check out the [https://www.youtube.com/watch?v=QjmpAq9RUXM Bird's Eye View of a Bisq Trade] video for a high-level overview of how Bisq trading works.&lt;br /&gt;
&lt;br /&gt;
Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.&lt;br /&gt;
&lt;br /&gt;
As of April 2021, Bisq contributors have designed a whole new beautiful interface that should make Bisq significantly more intuitive, and are also in touch with a talented UI developer to turn the design into code. You can follow progress on this initiative [https://github.com/bisq-network/projects/issues/49 here].&lt;br /&gt;
&lt;br /&gt;
==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
While Bisq can technically support any market, only a handful of markets are consistently active on Bisq—mainly because they offer good payment methods and had strong on-the-ground support to bootstrap them in the beginning.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Note that a weak offer book in a particular market doesn't ''necessarily'' mean trades don't take place in that market. It could be that there are people lurking there that will happily take an offer if you take the initiative to make one (this is often the case in markets like CAD, AUD, and GBP, for example).&lt;br /&gt;
&lt;br /&gt;
You can check trade history for your market by going to &amp;lt;code&amp;gt;Market&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Trades&amp;lt;/code&amp;gt; and picking your currency from the dropdown.}}&lt;br /&gt;
&lt;br /&gt;
If your market has no recent trades, a little more work will need to be done to get it going. At a minimum, payment methods common in your market should be added ([https://github.com/bisq-network/growth/issues/new/choose suggest them here]), and some form of marketing should be done to get users and market-makers to bootstrap a market.&lt;br /&gt;
&lt;br /&gt;
Bisq contributors are more than happy to help if you can help with guidance, connections to people who can help, and/or events and translations and other vehicles for reaching your target demographics.&lt;br /&gt;
&lt;br /&gt;
==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
Yes, the chicken-and-egg problem with Bisq is real. &lt;br /&gt;
&lt;br /&gt;
Here are some ways to get just enough bitcoin to do your first trade on Bisq:&lt;br /&gt;
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]&lt;br /&gt;
* hop onto the &amp;lt;code&amp;gt;Get your first BTC&amp;lt;/code&amp;gt; room on [https://bisq.chat Matrix] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])&lt;br /&gt;
&lt;br /&gt;
== Trading ==&lt;br /&gt;
&lt;br /&gt;
==== What are trading fees? ====&lt;br /&gt;
&lt;br /&gt;
[[Trading fees]] are calculated as a percentage of trade size: 0.1% for makers and 0.7% for takers if paid in BTC and about half of that if paid in BSQ.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that you'll also need to pay [[mining fees]] for the on-chain transactions, as well as a deposit to lock into the multisig escrow. You'll get the deposit back in full after the trade completes successfully.&lt;br /&gt;
&lt;br /&gt;
==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.&lt;br /&gt;
&lt;br /&gt;
Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.&lt;br /&gt;
&lt;br /&gt;
Other things you can do: &lt;br /&gt;
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)&lt;br /&gt;
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)&lt;br /&gt;
&lt;br /&gt;
==== Why does Bisq require a security deposit in BTC? ====&lt;br /&gt;
&lt;br /&gt;
[[Security deposit | Security deposits]] create strong incentives for buyers and sellers to follow the [[Trading rules|rules of Bisq's trading protocol]]. Deposits are locked into multisig escrow along with the bitcoin being traded, and are returned to each user when the trade is complete.&lt;br /&gt;
&lt;br /&gt;
If a trade is disputed through a mediator or arbitrator, some or all of the offending party's security deposit may be awarded to the counterparty. Examples of protocol violations include a buyer failing to pay a seller, paying with a different account or with a different name, or a seller failing to acknowledge receipt of a buyer's payment.&lt;br /&gt;
&lt;br /&gt;
Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.&lt;br /&gt;
&lt;br /&gt;
See full [[trading rules]].&lt;br /&gt;
&lt;br /&gt;
==== What are trading limits? How much bitcoin can I buy/sell at once? ====&lt;br /&gt;
&lt;br /&gt;
Trading limits vary based on payment method, since some payment methods are more secure than others.&lt;br /&gt;
&lt;br /&gt;
Relatively safe payment methods such as Japan's Furikomi and Australia's PayID are set to allow trades of up to 1 BTC, but other payment methods such as Zelle and SEPA have a cap of 0.25 BTC. See the [[Payment_methods|full list of payment methods and limits]].&lt;br /&gt;
&lt;br /&gt;
Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.&lt;br /&gt;
&lt;br /&gt;
==== Which payment methods are available? ====&lt;br /&gt;
&lt;br /&gt;
See [[payment methods]].&lt;br /&gt;
&lt;br /&gt;
If you'd like to suggest a payment method to be added, please [https://github.com/bisq-network/growth/issues/new/choose submit a new issue].&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq handle fiat like dollars and euros? Where does it go? ====&lt;br /&gt;
&lt;br /&gt;
Bisq doesn't handle fiat at all -- it only handles BTC. Trades are settled outside of Bisq, meaning fiat payments are sent outside Bisq via traditional banking services.&lt;br /&gt;
&lt;br /&gt;
Bisq merely matches peers and sets incentives (e.g. locking a BTC security deposit from both peers, as a sort of escrow) to encourage both trading peers to act in good faith. This is also why you need bitcoin to begin trading on Bisq.&lt;br /&gt;
&lt;br /&gt;
==== How long does a trade take? ====&lt;br /&gt;
&lt;br /&gt;
There is no automatic order matching on Bisq, and trades are settled manually by humans. As a result, trades are not completed as quickly as they would be on centralized exchanges, but can still be fairly quick. &lt;br /&gt;
&lt;br /&gt;
Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).&lt;br /&gt;
&lt;br /&gt;
As far as Bisq is concerned, the deposit transaction needs to be confirmed once before the buyer can send payment. Bitcoin transactions take about 10 minutes to confirm, so with quick traders and quick payment method, a Bisq trade can be completed in a matter of minutes.&lt;br /&gt;
&lt;br /&gt;
Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).&lt;br /&gt;
&lt;br /&gt;
See the list of [[payment methods]] for complete details.&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq protect my privacy? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is standalone, open-source software that you can inspect before running on your machine, and as a result, you don't have to trust that any server is logging your personal details (as you would in the case of a website).&lt;br /&gt;
&lt;br /&gt;
As for the trading process, your payment information is stored locally on your machine, and only your trading partner (and your mediator or arbitrator, in case of a dispute) can ever see it. All data exchanged between users is encrypted and signed.&lt;br /&gt;
&lt;br /&gt;
To transmit data from one user to another, Bisq uses a P2P network built on top of Tor, which provides a high degree of anonymity. The user doesn't need to do any additional work for all of this to work—it is all integrated in the application.&lt;br /&gt;
&lt;br /&gt;
==== Do I need to keep Bisq online for my offers to remain online? ====&lt;br /&gt;
&lt;br /&gt;
Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.&lt;br /&gt;
&lt;br /&gt;
If you have published an offer, your Bisq application needs to stay online so it can react when another trader wants to take your offer (the multisig deposit transaction is created in the take-offer process). Be sure you have deactivated your computer's standby mode so your Bisq application can stay online (monitor standby is not a problem).&lt;br /&gt;
&lt;br /&gt;
If your Bisq application does go offline, your offer will get removed from the distributed offerbook. It will be re-published the next time you start your Bisq application.&lt;br /&gt;
&lt;br /&gt;
After an offer has been taken and the trade process has started, neither trader needs to be online continuously, but each trader will need to be online periodically to check if any action is needed on their side (e.g. sending fiat/altcoin, confirming payment receipt, etc).&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq wallet? ====&lt;br /&gt;
&lt;br /&gt;
No, but you may find it convenient to keep a small amount of trading capital there.&lt;br /&gt;
&lt;br /&gt;
When entering a new trade on Bisq, you will get the option to transfer funds from your Bisq wallet ''or'' send funds from an external wallet.&lt;br /&gt;
&lt;br /&gt;
Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq token? ====&lt;br /&gt;
&lt;br /&gt;
No, using BSQ is totally optional. However, using it gets you a ~50% discount on [[trading fees]] while helping to [[Introduction_to_the_DAO#Earn_and_distribute_revenue|compensate Bisq contributors]] at the same time.&lt;br /&gt;
&lt;br /&gt;
==== Will my bank know I'm trading bitcoin? ====&lt;br /&gt;
&lt;br /&gt;
Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.&lt;br /&gt;
&lt;br /&gt;
But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the &amp;quot;reason for payment&amp;quot; field always be left BLANK when making a payment (if the payment method offers such a field).&lt;br /&gt;
&lt;br /&gt;
If a reason is required, it should be something trivial like a &amp;quot;-&amp;quot; or &amp;quot;payment&amp;quot;. If you want to use something else, please agree on an alternative with your peer using trader chat.&lt;br /&gt;
See full [[trading rules]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Common Technical Niggles ==&lt;br /&gt;
&lt;br /&gt;
==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ==== &lt;br /&gt;
&lt;br /&gt;
If Bisq won't open, try right-clicking the app and clicking &amp;lt;code&amp;gt;Open&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If you get the prompt asking to record your keystrokes, rest assured it's a [https://github.com/bisq-network/bisq/issues/3373 bug] (Bisq is absolutely not recording your keystrokes). This bug should be fixed with a [[https://github.com/bisq-network/projects/issues/44|Java LTS version update]] coming soon.&lt;br /&gt;
&lt;br /&gt;
==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has had memory usage and CPU usage issue on certain operating systems in the past, but these issues should be resolved now. You can manually set the max RAM usage by following [[Reducing_memory_usage|these instructions]].&lt;br /&gt;
&lt;br /&gt;
Chances are Bisq is probably just trying to sync blockchain data. New releases of Bisq include data stores updated at release time to reduce this syncing time, but as a release gets older (i.e., beyond 3-4 weeks old), the data stores get older, and syncing takes longer. Just let it finish and your computer resources should go back down to normal again.&lt;br /&gt;
&lt;br /&gt;
If the issue doesn't go away on its own, please reach out for help in the &amp;lt;code&amp;gt;Support&amp;lt;/code&amp;gt; room [https://bisq.chat on Matrix] or open an issue [https://github.com/bisq-network/bisq on GitHub].&lt;br /&gt;
&lt;br /&gt;
==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====&lt;br /&gt;
&lt;br /&gt;
See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.&lt;br /&gt;
&lt;br /&gt;
==== Bisq says &amp;quot;this offer cannot be taken due to counterparty trade restrictions&amp;quot;. What does that mean? ====&lt;br /&gt;
&lt;br /&gt;
This happens in rare circumstances.  Bisq checks information about an account such as its age to determine if it is allowed to trade over certain limits.  The information is stored in the P2P network, and it may not yet have propagated to your node.  Try again after restarting Bisq.  The offer maker may need to restart Bisq in order for the information to propagate.&lt;br /&gt;
&lt;br /&gt;
==== My SPV resync is taking all day and it keeps freezing.  What can I do to make it go faster? ====&lt;br /&gt;
&lt;br /&gt;
Unfortunately this can happen sometimes if your wallet is over a year old and/or has a lot of transactions.  If the resync stalls, close and restart Bisq to continue the resync.  It will go faster if you [[Connecting_to_your_own_Bitcoin_node|connect to a local Bitcoin node]].&lt;br /&gt;
After your SPV resync is completed, it would be best to switch to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====&lt;br /&gt;
&lt;br /&gt;
The procedure involves setting aside the existing wallet directory (by renaming) in order to get a fresh wallet.  The wallet directory is at &amp;lt;code&amp;gt;btc_mainnet/wallet&amp;lt;/code&amp;gt; from the [[Data_directory|main data directory location]].  You'll then be able to activate either the old or new wallet by renaming the directory before starting Bisq.  Be sure that Bisq is never running when you rename a directory.&lt;br /&gt;
# You have some BSQ and also some BTC balance existing in your wallet.  (You need BTC to pay mining fees for sending BSQ).  &lt;br /&gt;
# Close Bisq then rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; directory to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt;. &lt;br /&gt;
# Start Bisq and it will create a fresh wallet.  Note down your BSQ receiving address and also your BTC receiving address.  Write down your recovery seed phrase (Under Account / Wallet Seed menu) and store it in a safe place (not online).  &lt;br /&gt;
# Close Bisq and rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; dir to &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt;, rename your old wallet dir to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;, then restart Bisq.  &lt;br /&gt;
# Send BSQ to your new receiving address you saved in the earlier step.  Then send BTC the same way.  Close Bisq.  &lt;br /&gt;
# Rename &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;.  Then restart Bisq.&lt;br /&gt;
&lt;br /&gt;
Done!  Your BSQ and BTC balances have been moved to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;heightOfLastBlock must match chainHeight&amp;quot; error on starting Bisq ====&lt;br /&gt;
&lt;br /&gt;
The following procedure should fix itː&lt;br /&gt;
* make a backup of your data folder&lt;br /&gt;
* close Bisq&lt;br /&gt;
* from inside data folder, delete DaoStateStore and BsqBlocks&lt;br /&gt;
* restart Bisq&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; ====&lt;br /&gt;
&lt;br /&gt;
This is a known issue, and it's because the application will err on the side of caution when P2P network conditions are less than favourable.&lt;br /&gt;
It most often happens when the peer is offline, so usually when a seller taker accepts an open offer with a non-instant payment method, like SEPA, and then goes offline, since the payment will take at least a day to be credited and they do not need to stay connected while the buyer maker's payment arrives.&lt;br /&gt;
Here are some things that might work&lt;br /&gt;
* Send a message in trader chat&lt;br /&gt;
* Insist on pressing the button tens of times&lt;br /&gt;
* Restart Bisq&lt;br /&gt;
* Follow menus '''Settings''' -&amp;gt; '''Network Info''' -&amp;gt; '''Open Tor Settings''' -&amp;gt; '''Delete Outdated Tor Files And Shutdown''', then restart Bisq&lt;br /&gt;
* Do nothing and stay online, as the button will sometimes finally &amp;quot;register&amp;quot; by itself with a random delay&lt;br /&gt;
* When everything else fails, and the trade period is almost at its end, communicate your intentions to the peer in trader chat and open mediation by pressing Ctrl-O in trade window, explaining what happened to the mediator, even better by attaching a screenshot of the issue; a support ticket will be opened and both peers will have the opportunity to accept the original payout&lt;br /&gt;
&lt;br /&gt;
==== I want to install Bisq on a VPS or on an otherwise headless system ====&lt;br /&gt;
&lt;br /&gt;
Bisq needs a graphical desktop environment to be ran, but in order to keep offers online without the need to have your PC always on, some users reported good results by using https://www.xpra.org as a graphical endpoint which you can forward to a client.&lt;br /&gt;
&lt;br /&gt;
== Dispute resolution ==&lt;br /&gt;
&lt;br /&gt;
==== How does dispute resolution work? ====&lt;br /&gt;
&lt;br /&gt;
Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
Trader chat enables traders to resolve small issues themselves privately over end-to-end encrypted chat right in Bisq. If this doesn't work, traders can engage a mediator to examine the situation and suggest a payout. In rare circumstances that mediation fails, a trader can choose to engage an arbitrator to re-examine the situation and make a payout.&lt;br /&gt;
&lt;br /&gt;
Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.&lt;br /&gt;
&lt;br /&gt;
See [[trading rules]] and [[dispute resolution]] for more.&lt;br /&gt;
&lt;br /&gt;
==== How is collusion between mediators, arbitrators, and traders prevented? ====&lt;br /&gt;
&lt;br /&gt;
With the launch of the new trading protocol in v1.2, multisig escrows went from 2-of-3 to 2-of-2 arrangements, so that only the two trading peers have control of trading funds (instead of the 2 trading peers and an arbitrator). With no keys in the multisig escrow, it is no longer possible for a mediator or arbitrator to collude with another trader to release funds maliciously.&lt;br /&gt;
&lt;br /&gt;
Mediators and arbitrators are still bonded roles, however, because even though they cannot sign a payout transaction to resolve a dispute, they can ''advise'' how to resolve a dispute, and it's important that they be responsive, responsible, and fair when doing so.&lt;br /&gt;
&lt;br /&gt;
==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====&lt;br /&gt;
&lt;br /&gt;
Bisq only supports payment methods for which chargebacks are not easy (e.g., this is why PayPal and credit cards are not supported). But there is still a little chargeback risk with banks. If a bank executes a chargeback after the BTC has been released, there is nothing a mediator or arbitrator can do.&lt;br /&gt;
&lt;br /&gt;
Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:&lt;br /&gt;
&lt;br /&gt;
# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.&lt;br /&gt;
# [[Account_limits#Account_signing|Account signing]] requires higher-risk payment methods to be signed upon verifying the integrity of a trader before account aging kicks in. Until such accounts are signed, buy limits are set to 0.01 BTC.&lt;br /&gt;
# National currency payment methods which are found to be used for chargebacks are quickly removed.&lt;br /&gt;
&lt;br /&gt;
==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====&lt;br /&gt;
&lt;br /&gt;
Pure reputation without additional dispute resolution measures is a weak protection system, as you can never avoid [https://en.wikipedia.org/wiki/Sybil_attack sybil] or [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks.&lt;br /&gt;
&lt;br /&gt;
Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.&lt;br /&gt;
&lt;br /&gt;
==== How can I contact my trading peer? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has a built-in end-to-end encrypted [[Dispute_resolution#Level_1:_Trader_chat|chat mechanism]] that you can use to talk to your trading peer while the trade is in progress.&lt;br /&gt;
&lt;br /&gt;
== DAO ==&lt;br /&gt;
&lt;br /&gt;
==== What is the Bisq DAO? ====&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO (decentralized autonomous organization) is a decentralized governance mechanism for the Bisq software, built on Bitcoin. It takes the place of a company. How good can decentralized software possibly be if it's still controlled by a single entity, like a company?&lt;br /&gt;
&lt;br /&gt;
Decentralized software is no good without decentralized governance.&lt;br /&gt;
&lt;br /&gt;
That's why Bisq is not a company or legal entity of any kind—instead, it's organized as a DAO. The DAO handles the software's funding and strategy-making to enable the Bisq network to thrive, and at the same time, harden it against attacks on the infrastructure that powers its leadership and operation.&lt;br /&gt;
&lt;br /&gt;
In a nutshell, the Bisq DAO enables Bisq to become even more censorship-resistant, a core [[Introduction|principle of the project]] from the very beginning.&lt;br /&gt;
&lt;br /&gt;
Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].&lt;br /&gt;
&lt;br /&gt;
==== How does the Bisq DAO work? ====&lt;br /&gt;
&lt;br /&gt;
The primary purposes of the Bisq DAO are financing the project and determining strategy.&lt;br /&gt;
&lt;br /&gt;
# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.&lt;br /&gt;
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.&lt;br /&gt;
&lt;br /&gt;
Learn more about how this actually works in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this series of short 3-5 minute videos].&lt;br /&gt;
&lt;br /&gt;
See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.&lt;br /&gt;
&lt;br /&gt;
==== What do I need to know about the DAO, as a trader? ====&lt;br /&gt;
&lt;br /&gt;
First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.&lt;br /&gt;
&lt;br /&gt;
But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.&lt;br /&gt;
&lt;br /&gt;
But why have the BSQ token at all? Because it enables Bisq contributors to be paid for their work without any central wallets or points of control. When you buy BSQ, you're directly paying a Bisq contributor for their work, and in the process, helping to sustain the whole project. The dynamic this token enables is not possible with plain bitcoin.&lt;br /&gt;
&lt;br /&gt;
When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.&lt;br /&gt;
&lt;br /&gt;
[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====&lt;br /&gt;
&lt;br /&gt;
Bisq already earns revenue from trading fees. It's not launching this DAO and BSQ token for ''earning'' revenue—it's doing it to ''distribute'' the revenue it already earns to more people without any central points of control.&lt;br /&gt;
&lt;br /&gt;
BSQ tokens are issued every time a contributor's compensation request is approved through voting, and the tokens are destroyed every time a trader uses BSQ to pay trading fees.&lt;br /&gt;
&lt;br /&gt;
BSQ issuance is not a 1-time event, and its purpose is not to raise capital. You can see a walk-through of the BSQ issuance process in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this video series].&lt;br /&gt;
&lt;br /&gt;
==== Can I use Bisq without BSQ and without this DAO? ====&lt;br /&gt;
&lt;br /&gt;
You could. All you'd have to do is pay your trading fees with BTC instead of BSQ. But we hope you don't, because doing so would render the project unsustainable.&lt;br /&gt;
&lt;br /&gt;
Before the Bisq DAO, trading fees went to just a couple of wallets owned by specific Bisq contributors (arbitrators). All other contributors were not paid. Bisq needs its contributors to be paid in regular, predictable ways to ensure continual (and reliable) development, service, and growth; the Bisq DAO enables this to happen by distributing trading fees to all contributors in a totally decentralized way.&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO and BSQ token enable a funding and governance mechanism that is [[https://bisq.network/blog/bisq-dao-for-bitcoin-maximalists/ not possible with plain bitcoin]]. We highly recommend you check [[Decentralized_autonomous_organization|out the documentation]] and [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e video series]] to learn more.&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
==== This project is cool! How can I help out? ====&lt;br /&gt;
&lt;br /&gt;
Check out the [[contributor checklist]]. We'd love to hear from you!&lt;br /&gt;
&lt;br /&gt;
==== I have a question that isn’t covered here...? ====&lt;br /&gt;
&lt;br /&gt;
Feel free to reach out on [https://bisq.chat Matrix] or [https://bisq.network/#community any other channel].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2980</id>
		<title>Frequently asked questions</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2980"/>
		<updated>2022-04-21T22:09:53Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project. &lt;br /&gt;
&lt;br /&gt;
Feel free to ask further questions on any of Bisq's many outreach channels. &lt;br /&gt;
&lt;br /&gt;
== About ==&lt;br /&gt;
&lt;br /&gt;
==== How is Bisq different from other decentralized exchanges? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is a peer-to-peer trading network, not a website or &amp;quot;app&amp;quot; or other centralized service. It's software you run on your own hardware, which connects to other people running the Bisq software to facilitate trades. It's open-source and community-driven.&lt;br /&gt;
&lt;br /&gt;
And you can trade bitcoin for fiat currencies with it!&lt;br /&gt;
&lt;br /&gt;
The difference between Bisq and other so-called decentralized exchanges is as stark as the difference between owning your own home and renting someone else's—in the former case you have full control over the property, and in the latter you're always subject to the landlord's whims and demands (no matter how nice the landlord may seem to be).&lt;br /&gt;
&lt;br /&gt;
With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.&lt;br /&gt;
&lt;br /&gt;
* Bisq does not hold any bitcoin. All bitcoin used for trading is held in '''2-of-2 multisignature addresses''' controlled solely by the trading peers themselves.&lt;br /&gt;
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.&lt;br /&gt;
* All Bisq data is transferred over its own secure peer-to-peer network, which is built on top of the Tor network—no central servers. This means '''there are no data honeypots''', rendering large-scale hacks of customer information databases impossible.&lt;br /&gt;
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.&lt;br /&gt;
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.&lt;br /&gt;
* Bisq is code, not a company. It is an open-source project organized as a [[Decentralized_autonomous_organization|decentralized autonomous organization (DAO)]] built on top of Bitcoin.&lt;br /&gt;
&lt;br /&gt;
See more in the [[Introduction]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq open-source software? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License. &lt;br /&gt;
&lt;br /&gt;
Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq safe? ====&lt;br /&gt;
&lt;br /&gt;
Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.&lt;br /&gt;
&lt;br /&gt;
Bisq employs three primary mechanisms to achieve security:&lt;br /&gt;
&lt;br /&gt;
* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.&lt;br /&gt;
* Both traders are required to pay security deposits, which are refunded after trades are completed.&lt;br /&gt;
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.&lt;br /&gt;
&lt;br /&gt;
To mitigate this risk, Bisq:&lt;br /&gt;
&lt;br /&gt;
* only supports payment methods which are known to make chargebacks difficult—this is why Bisq does not support PayPal and credit cards, for example. See more on chargeback risks.&lt;br /&gt;
* employs an [[Account_limits#Account_signing account|signing mechanism]] that forces 0.01 BTC buy limits until a buyer's integrity (not identity!) is verified.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====&lt;br /&gt;
&lt;br /&gt;
Some people find Bisq's interface intuitive, but many people don't. Check out [https://www.youtube.com/watch?v=HDkzUl9wibc this tour video] to help you make sense of the interface, and then check out the [https://www.youtube.com/watch?v=QjmpAq9RUXM Bird's Eye View of a Bisq Trade] video for a high-level overview of how Bisq trading works.&lt;br /&gt;
&lt;br /&gt;
Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.&lt;br /&gt;
&lt;br /&gt;
As of April 2021, Bisq contributors have designed a whole new beautiful interface that should make Bisq significantly more intuitive, and are also in touch with a talented UI developer to turn the design into code. You can follow progress on this initiative [https://github.com/bisq-network/projects/issues/49 here].&lt;br /&gt;
&lt;br /&gt;
==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
While Bisq can technically support any market, only a handful of markets are consistently active on Bisq—mainly because they offer good payment methods and had strong on-the-ground support to bootstrap them in the beginning.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Note that a weak offer book in a particular market doesn't ''necessarily'' mean trades don't take place in that market. It could be that there are people lurking there that will happily take an offer if you take the initiative to make one (this is often the case in markets like CAD, AUD, and GBP, for example).&lt;br /&gt;
&lt;br /&gt;
You can check trade history for your market by going to &amp;lt;code&amp;gt;Market&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Trades&amp;lt;/code&amp;gt; and picking your currency from the dropdown.}}&lt;br /&gt;
&lt;br /&gt;
If your market has no recent trades, a little more work will need to be done to get it going. At a minimum, payment methods common in your market should be added ([https://github.com/bisq-network/growth/issues/new/choose suggest them here]), and some form of marketing should be done to get users and market-makers to bootstrap a market.&lt;br /&gt;
&lt;br /&gt;
Bisq contributors are more than happy to help if you can help with guidance, connections to people who can help, and/or events and translations and other vehicles for reaching your target demographics.&lt;br /&gt;
&lt;br /&gt;
==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
Yes, the chicken-and-egg problem with Bisq is real. &lt;br /&gt;
&lt;br /&gt;
Here are some ways to get just enough bitcoin to do your first trade on Bisq:&lt;br /&gt;
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]&lt;br /&gt;
* hop onto the &amp;lt;code&amp;gt;Get your first BTC&amp;lt;/code&amp;gt; room on [https://bisq.chat Matrix] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])&lt;br /&gt;
&lt;br /&gt;
== Trading ==&lt;br /&gt;
&lt;br /&gt;
==== What are trading fees? ====&lt;br /&gt;
&lt;br /&gt;
[[Trading fees]] are calculated as a percentage of trade size: 0.1% for makers and 0.7% for takers if paid in BTC and about half of that if paid in BSQ.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that you'll also need to pay [[mining fees]] for the on-chain transactions, as well as a deposit to lock into the multisig escrow. You'll get the deposit back in full after the trade completes successfully.&lt;br /&gt;
&lt;br /&gt;
==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.&lt;br /&gt;
&lt;br /&gt;
Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.&lt;br /&gt;
&lt;br /&gt;
Other things you can do: &lt;br /&gt;
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)&lt;br /&gt;
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)&lt;br /&gt;
&lt;br /&gt;
==== Why does Bisq require a security deposit in BTC? ====&lt;br /&gt;
&lt;br /&gt;
[[Security deposit | Security deposits]] create strong incentives for buyers and sellers to follow the [[Trading rules|rules of Bisq's trading protocol]]. Deposits are locked into multisig escrow along with the bitcoin being traded, and are returned to each user when the trade is complete.&lt;br /&gt;
&lt;br /&gt;
If a trade is disputed through a mediator or arbitrator, some or all of the offending party's security deposit may be awarded to the counterparty. Examples of protocol violations include a buyer failing to pay a seller, paying with a different account or with a different name, or a seller failing to acknowledge receipt of a buyer's payment.&lt;br /&gt;
&lt;br /&gt;
Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.&lt;br /&gt;
&lt;br /&gt;
See full [[trading rules]].&lt;br /&gt;
&lt;br /&gt;
==== What are trading limits? How much bitcoin can I buy/sell at once? ====&lt;br /&gt;
&lt;br /&gt;
Trading limits vary based on payment method, since some payment methods are more secure than others.&lt;br /&gt;
&lt;br /&gt;
Relatively safe payment methods such as Japan's Furikomi and Australia's PayID are set to allow trades of up to 1 BTC, but other payment methods such as Zelle and SEPA have a cap of 0.25 BTC. See the [[Payment_methods|full list of payment methods and limits]].&lt;br /&gt;
&lt;br /&gt;
Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.&lt;br /&gt;
&lt;br /&gt;
==== Which payment methods are available? ====&lt;br /&gt;
&lt;br /&gt;
See [[payment methods]].&lt;br /&gt;
&lt;br /&gt;
If you'd like to suggest a payment method to be added, please [https://github.com/bisq-network/growth/issues/new/choose submit a new issue].&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq handle fiat like dollars and euros? Where does it go? ====&lt;br /&gt;
&lt;br /&gt;
Bisq doesn't handle fiat at all -- it only handles BTC. Trades are settled outside of Bisq, meaning fiat payments are sent outside Bisq via traditional banking services.&lt;br /&gt;
&lt;br /&gt;
Bisq merely matches peers and sets incentives (e.g. locking a BTC security deposit from both peers, as a sort of escrow) to encourage both trading peers to act in good faith. This is also why you need bitcoin to begin trading on Bisq.&lt;br /&gt;
&lt;br /&gt;
==== How long does a trade take? ====&lt;br /&gt;
&lt;br /&gt;
There is no automatic order matching on Bisq, and trades are settled manually by humans. As a result, trades are not completed as quickly as they would be on centralized exchanges, but can still be fairly quick. &lt;br /&gt;
&lt;br /&gt;
Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).&lt;br /&gt;
&lt;br /&gt;
As far as Bisq is concerned, the deposit transaction needs to be confirmed once before the buyer can send payment. Bitcoin transactions take about 10 minutes to confirm, so with quick traders and quick payment method, a Bisq trade can be completed in a matter of minutes.&lt;br /&gt;
&lt;br /&gt;
Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).&lt;br /&gt;
&lt;br /&gt;
See the list of [[payment methods]] for complete details.&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq protect my privacy? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is standalone, open-source software that you can inspect before running on your machine, and as a result, you don't have to trust that any server is logging your personal details (as you would in the case of a website).&lt;br /&gt;
&lt;br /&gt;
As for the trading process, your payment information is stored locally on your machine, and only your trading partner (and your mediator or arbitrator, in case of a dispute) can ever see it. All data exchanged between users is encrypted and signed.&lt;br /&gt;
&lt;br /&gt;
To transmit data from one user to another, Bisq uses a P2P network built on top of Tor, which provides a high degree of anonymity. The user doesn't need to do any additional work for all of this to work—it is all integrated in the application.&lt;br /&gt;
&lt;br /&gt;
==== Do I need to keep Bisq online for my offers to remain online? ====&lt;br /&gt;
&lt;br /&gt;
Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.&lt;br /&gt;
&lt;br /&gt;
If you have published an offer, your Bisq application needs to stay online so it can react when another trader wants to take your offer (the multisig deposit transaction is created in the take-offer process). Be sure you have deactivated your computer's standby mode so your Bisq application can stay online (monitor standby is not a problem).&lt;br /&gt;
&lt;br /&gt;
If your Bisq application does go offline, your offer will get removed from the distributed offerbook. It will be re-published the next time you start your Bisq application.&lt;br /&gt;
&lt;br /&gt;
After an offer has been taken and the trade process has started, neither trader needs to be online continuously, but each trader will need to be online periodically to check if any action is needed on their side (e.g. sending fiat/altcoin, confirming payment receipt, etc).&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq wallet? ====&lt;br /&gt;
&lt;br /&gt;
No, but you may find it convenient to keep a small amount of trading capital there.&lt;br /&gt;
&lt;br /&gt;
When entering a new trade on Bisq, you will get the option to transfer funds from your Bisq wallet ''or'' send funds from an external wallet.&lt;br /&gt;
&lt;br /&gt;
Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq token? ====&lt;br /&gt;
&lt;br /&gt;
No, using BSQ is totally optional. However, using it gets you a ~50% discount on [[trading fees]] while helping to [[Introduction_to_the_DAO#Earn_and_distribute_revenue|compensate Bisq contributors]] at the same time.&lt;br /&gt;
&lt;br /&gt;
==== Will my bank know I'm trading bitcoin? ====&lt;br /&gt;
&lt;br /&gt;
Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.&lt;br /&gt;
&lt;br /&gt;
But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the &amp;quot;reason for payment&amp;quot; field always be left BLANK when making a payment (if the payment method offers such a field).&lt;br /&gt;
&lt;br /&gt;
If a reason is required, it should be something trivial like a &amp;quot;-&amp;quot; or &amp;quot;payment&amp;quot;. If you want to use something else, please agree on an alternative with your peer using trader chat.&lt;br /&gt;
See full [[trading rules]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Common Technical Niggles ==&lt;br /&gt;
&lt;br /&gt;
==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ==== &lt;br /&gt;
&lt;br /&gt;
If Bisq won't open, try right-clicking the app and clicking &amp;lt;code&amp;gt;Open&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If you get the prompt asking to record your keystrokes, rest assured it's a [https://github.com/bisq-network/bisq/issues/3373 bug] (Bisq is absolutely not recording your keystrokes). This bug should be fixed with a [[https://github.com/bisq-network/projects/issues/44|Java LTS version update]] coming soon.&lt;br /&gt;
&lt;br /&gt;
==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has had memory usage and CPU usage issue on certain operating systems in the past, but these issues should be resolved now. You can manually set the max RAM usage by following [[Reducing_memory_usage|these instructions]].&lt;br /&gt;
&lt;br /&gt;
Chances are Bisq is probably just trying to sync blockchain data. New releases of Bisq include data stores updated at release time to reduce this syncing time, but as a release gets older (i.e., beyond 3-4 weeks old), the data stores get older, and syncing takes longer. Just let it finish and your computer resources should go back down to normal again.&lt;br /&gt;
&lt;br /&gt;
If the issue doesn't go away on its own, please reach out for help in the &amp;lt;code&amp;gt;Support&amp;lt;/code&amp;gt; room [https://bisq.chat on Matrix] or open an issue [https://github.com/bisq-network/bisq on GitHub].&lt;br /&gt;
&lt;br /&gt;
==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====&lt;br /&gt;
&lt;br /&gt;
See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.&lt;br /&gt;
&lt;br /&gt;
==== Bisq says &amp;quot;this offer cannot be taken due to counterparty trade restrictions&amp;quot;. What does that mean? ====&lt;br /&gt;
&lt;br /&gt;
This happens in rare circumstances.  Bisq checks information about an account such as its age to determine if it is allowed to trade over certain limits.  The information is stored in the P2P network, and it may not yet have propagated to your node.  Try again after restarting Bisq.  The offer maker may need to restart Bisq in order for the information to propagate.&lt;br /&gt;
&lt;br /&gt;
==== My SPV resync is taking all day and it keeps freezing.  What can I do to make it go faster? ====&lt;br /&gt;
&lt;br /&gt;
Unfortunately this can happen sometimes if your wallet is over a year old and/or has a lot of transactions.  If the resync stalls, close and restart Bisq to continue the resync.  It will go faster if you [[Connecting_to_your_own_Bitcoin_node|connect to a local Bitcoin node]].&lt;br /&gt;
After your SPV resync is completed, it would be best to switch to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====&lt;br /&gt;
&lt;br /&gt;
The procedure involves setting aside the existing wallet directory (by renaming) in order to get a fresh wallet.  The wallet directory is at &amp;lt;code&amp;gt;btc_mainnet/wallet&amp;lt;/code&amp;gt; from the [[Data_directory|main data directory location]].  You'll then be able to activate either the old or new wallet by renaming the directory before starting Bisq.  Be sure that Bisq is never running when you rename a directory.&lt;br /&gt;
# You have some BSQ and also some BTC balance existing in your wallet.  (You need BTC to pay mining fees for sending BSQ).  &lt;br /&gt;
# Close Bisq then rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; directory to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt;. &lt;br /&gt;
# Start Bisq and it will create a fresh wallet.  Note down your BSQ receiving address and also your BTC receiving address.  Write down your recovery seed phrase (Under Account / Wallet Seed menu) and store it in a safe place (not online).  &lt;br /&gt;
# Close Bisq and rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; dir to &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt;, rename your old wallet dir to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;, then restart Bisq.  &lt;br /&gt;
# Send BSQ to your new receiving address you saved in the earlier step.  Then send BTC the same way.  Close Bisq.  &lt;br /&gt;
# Rename &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;.  Then restart Bisq.&lt;br /&gt;
&lt;br /&gt;
Done!  Your BSQ and BTC balances have been moved to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;heightOfLastBlock must match chainHeight&amp;quot; error on starting Bisq ====&lt;br /&gt;
&lt;br /&gt;
The following procedure should fix itː&lt;br /&gt;
* make a backup of your data folder&lt;br /&gt;
* close Bisq&lt;br /&gt;
* from inside data folder, delete DaoStateStore and BsqBlocks&lt;br /&gt;
* restart Bisq&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; ====&lt;br /&gt;
&lt;br /&gt;
This is a known issue, and it's because the application will err on the side of caution when P2P network conditions are less than favourable.&lt;br /&gt;
It most often happens when the peer is offline, so usually when a seller taker accepts an open offer with a non-instant payment method, like SEPA, and then goes offline, since the payment will take at least a day to be credited and they do not need to stay connected while the buyer maker's payment arrives.&lt;br /&gt;
Here are some things that might work&lt;br /&gt;
* Send a message in trader chat&lt;br /&gt;
* Insist on pressing the button tens of times&lt;br /&gt;
* Restart Bisq&lt;br /&gt;
* Follow menus '''Settings''' -&amp;gt; '''Network Info''' -&amp;gt; '''Open Tor Settings''' -&amp;gt; '''Delete Outdated Tor Files And Shutdown''', then restart Bisq&lt;br /&gt;
* Do nothing and stay online, as the button will sometimes finally &amp;quot;register&amp;quot; by itself with a random delay&lt;br /&gt;
* When everything else fails, and the trade period is almost at its end, communicate your intentions to the peer in trader chat and open mediation by pressing Ctrl-O in trade window, explaining what happened to the mediator, even better by attaching a screenshot of the issue; a support ticket will be opened and both peers will have the opportunity to accept the original payout&lt;br /&gt;
&lt;br /&gt;
== Dispute resolution ==&lt;br /&gt;
&lt;br /&gt;
==== How does dispute resolution work? ====&lt;br /&gt;
&lt;br /&gt;
Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
Trader chat enables traders to resolve small issues themselves privately over end-to-end encrypted chat right in Bisq. If this doesn't work, traders can engage a mediator to examine the situation and suggest a payout. In rare circumstances that mediation fails, a trader can choose to engage an arbitrator to re-examine the situation and make a payout.&lt;br /&gt;
&lt;br /&gt;
Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.&lt;br /&gt;
&lt;br /&gt;
See [[trading rules]] and [[dispute resolution]] for more.&lt;br /&gt;
&lt;br /&gt;
==== How is collusion between mediators, arbitrators, and traders prevented? ====&lt;br /&gt;
&lt;br /&gt;
With the launch of the new trading protocol in v1.2, multisig escrows went from 2-of-3 to 2-of-2 arrangements, so that only the two trading peers have control of trading funds (instead of the 2 trading peers and an arbitrator). With no keys in the multisig escrow, it is no longer possible for a mediator or arbitrator to collude with another trader to release funds maliciously.&lt;br /&gt;
&lt;br /&gt;
Mediators and arbitrators are still bonded roles, however, because even though they cannot sign a payout transaction to resolve a dispute, they can ''advise'' how to resolve a dispute, and it's important that they be responsive, responsible, and fair when doing so.&lt;br /&gt;
&lt;br /&gt;
==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====&lt;br /&gt;
&lt;br /&gt;
Bisq only supports payment methods for which chargebacks are not easy (e.g., this is why PayPal and credit cards are not supported). But there is still a little chargeback risk with banks. If a bank executes a chargeback after the BTC has been released, there is nothing a mediator or arbitrator can do.&lt;br /&gt;
&lt;br /&gt;
Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:&lt;br /&gt;
&lt;br /&gt;
# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.&lt;br /&gt;
# [[Account_limits#Account_signing|Account signing]] requires higher-risk payment methods to be signed upon verifying the integrity of a trader before account aging kicks in. Until such accounts are signed, buy limits are set to 0.01 BTC.&lt;br /&gt;
# National currency payment methods which are found to be used for chargebacks are quickly removed.&lt;br /&gt;
&lt;br /&gt;
==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====&lt;br /&gt;
&lt;br /&gt;
Pure reputation without additional dispute resolution measures is a weak protection system, as you can never avoid [https://en.wikipedia.org/wiki/Sybil_attack sybil] or [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks.&lt;br /&gt;
&lt;br /&gt;
Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.&lt;br /&gt;
&lt;br /&gt;
==== How can I contact my trading peer? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has a built-in end-to-end encrypted [[Dispute_resolution#Level_1:_Trader_chat|chat mechanism]] that you can use to talk to your trading peer while the trade is in progress.&lt;br /&gt;
&lt;br /&gt;
== DAO ==&lt;br /&gt;
&lt;br /&gt;
==== What is the Bisq DAO? ====&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO (decentralized autonomous organization) is a decentralized governance mechanism for the Bisq software, built on Bitcoin. It takes the place of a company. How good can decentralized software possibly be if it's still controlled by a single entity, like a company?&lt;br /&gt;
&lt;br /&gt;
Decentralized software is no good without decentralized governance.&lt;br /&gt;
&lt;br /&gt;
That's why Bisq is not a company or legal entity of any kind—instead, it's organized as a DAO. The DAO handles the software's funding and strategy-making to enable the Bisq network to thrive, and at the same time, harden it against attacks on the infrastructure that powers its leadership and operation.&lt;br /&gt;
&lt;br /&gt;
In a nutshell, the Bisq DAO enables Bisq to become even more censorship-resistant, a core [[Introduction|principle of the project]] from the very beginning.&lt;br /&gt;
&lt;br /&gt;
Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].&lt;br /&gt;
&lt;br /&gt;
==== How does the Bisq DAO work? ====&lt;br /&gt;
&lt;br /&gt;
The primary purposes of the Bisq DAO are financing the project and determining strategy.&lt;br /&gt;
&lt;br /&gt;
# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.&lt;br /&gt;
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.&lt;br /&gt;
&lt;br /&gt;
Learn more about how this actually works in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this series of short 3-5 minute videos].&lt;br /&gt;
&lt;br /&gt;
See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.&lt;br /&gt;
&lt;br /&gt;
==== What do I need to know about the DAO, as a trader? ====&lt;br /&gt;
&lt;br /&gt;
First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.&lt;br /&gt;
&lt;br /&gt;
But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.&lt;br /&gt;
&lt;br /&gt;
But why have the BSQ token at all? Because it enables Bisq contributors to be paid for their work without any central wallets or points of control. When you buy BSQ, you're directly paying a Bisq contributor for their work, and in the process, helping to sustain the whole project. The dynamic this token enables is not possible with plain bitcoin.&lt;br /&gt;
&lt;br /&gt;
When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.&lt;br /&gt;
&lt;br /&gt;
[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====&lt;br /&gt;
&lt;br /&gt;
Bisq already earns revenue from trading fees. It's not launching this DAO and BSQ token for ''earning'' revenue—it's doing it to ''distribute'' the revenue it already earns to more people without any central points of control.&lt;br /&gt;
&lt;br /&gt;
BSQ tokens are issued every time a contributor's compensation request is approved through voting, and the tokens are destroyed every time a trader uses BSQ to pay trading fees.&lt;br /&gt;
&lt;br /&gt;
BSQ issuance is not a 1-time event, and its purpose is not to raise capital. You can see a walk-through of the BSQ issuance process in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this video series].&lt;br /&gt;
&lt;br /&gt;
==== Can I use Bisq without BSQ and without this DAO? ====&lt;br /&gt;
&lt;br /&gt;
You could. All you'd have to do is pay your trading fees with BTC instead of BSQ. But we hope you don't, because doing so would render the project unsustainable.&lt;br /&gt;
&lt;br /&gt;
Before the Bisq DAO, trading fees went to just a couple of wallets owned by specific Bisq contributors (arbitrators). All other contributors were not paid. Bisq needs its contributors to be paid in regular, predictable ways to ensure continual (and reliable) development, service, and growth; the Bisq DAO enables this to happen by distributing trading fees to all contributors in a totally decentralized way.&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO and BSQ token enable a funding and governance mechanism that is [[https://bisq.network/blog/bisq-dao-for-bitcoin-maximalists/ not possible with plain bitcoin]]. We highly recommend you check [[Decentralized_autonomous_organization|out the documentation]] and [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e video series]] to learn more.&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
==== This project is cool! How can I help out? ====&lt;br /&gt;
&lt;br /&gt;
Check out the [[contributor checklist]]. We'd love to hear from you!&lt;br /&gt;
&lt;br /&gt;
==== I have a question that isn’t covered here...? ====&lt;br /&gt;
&lt;br /&gt;
Feel free to reach out on [https://bisq.chat Matrix] or [https://bisq.network/#community any other channel].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2979</id>
		<title>Frequently asked questions</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Frequently_asked_questions&amp;diff=2979"/>
		<updated>2022-04-20T05:15:44Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Common Technical Niggles */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project. &lt;br /&gt;
&lt;br /&gt;
Feel free to ask further questions on any of Bisq's many outreach channels. &lt;br /&gt;
&lt;br /&gt;
== About ==&lt;br /&gt;
&lt;br /&gt;
==== How is Bisq different from other decentralized exchanges? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is a peer-to-peer trading network, not a website or &amp;quot;app&amp;quot; or other centralized service. It's software you run on your own hardware, which connects to other people running the Bisq software to facilitate trades. It's open-source and community-driven.&lt;br /&gt;
&lt;br /&gt;
And you can trade bitcoin for fiat currencies with it!&lt;br /&gt;
&lt;br /&gt;
The difference between Bisq and other so-called decentralized exchanges is as stark as the difference between owning your own home and renting someone else's—in the former case you have full control over the property, and in the latter you're always subject to the landlord's whims and demands (no matter how nice the landlord may seem to be).&lt;br /&gt;
&lt;br /&gt;
With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.&lt;br /&gt;
&lt;br /&gt;
* Bisq does not hold any bitcoin. All bitcoin used for trading is held in '''2-of-2 multisignature addresses''' controlled solely by the trading peers themselves.&lt;br /&gt;
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.&lt;br /&gt;
* All Bisq data is transferred over its own secure peer-to-peer network, which is built on top of the Tor network—no central servers. This means '''there are no data honeypots''', rendering large-scale hacks of customer information databases impossible.&lt;br /&gt;
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.&lt;br /&gt;
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.&lt;br /&gt;
* Bisq is code, not a company. It is an open-source project organized as a [[Decentralized_autonomous_organization|decentralized autonomous organization (DAO)]] built on top of Bitcoin.&lt;br /&gt;
&lt;br /&gt;
See more in the [[Introduction]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq open-source software? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License. &lt;br /&gt;
&lt;br /&gt;
Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq safe? ====&lt;br /&gt;
&lt;br /&gt;
Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.&lt;br /&gt;
&lt;br /&gt;
Bisq employs three primary mechanisms to achieve security:&lt;br /&gt;
&lt;br /&gt;
* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.&lt;br /&gt;
* Both traders are required to pay security deposits, which are refunded after trades are completed.&lt;br /&gt;
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.&lt;br /&gt;
&lt;br /&gt;
To mitigate this risk, Bisq:&lt;br /&gt;
&lt;br /&gt;
* only supports payment methods which are known to make chargebacks difficult—this is why Bisq does not support PayPal and credit cards, for example. See more on chargeback risks.&lt;br /&gt;
* employs an [[Account_limits#Account_signing account|signing mechanism]] that forces 0.01 BTC buy limits until a buyer's integrity (not identity!) is verified.&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
&lt;br /&gt;
==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====&lt;br /&gt;
&lt;br /&gt;
Some people find Bisq's interface intuitive, but many people don't. Check out [https://www.youtube.com/watch?v=HDkzUl9wibc this tour video] to help you make sense of the interface, and then check out the [https://www.youtube.com/watch?v=QjmpAq9RUXM Bird's Eye View of a Bisq Trade] video for a high-level overview of how Bisq trading works.&lt;br /&gt;
&lt;br /&gt;
Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.&lt;br /&gt;
&lt;br /&gt;
As of April 2021, Bisq contributors have designed a whole new beautiful interface that should make Bisq significantly more intuitive, and are also in touch with a talented UI developer to turn the design into code. You can follow progress on this initiative [https://github.com/bisq-network/projects/issues/49 here].&lt;br /&gt;
&lt;br /&gt;
==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
While Bisq can technically support any market, only a handful of markets are consistently active on Bisq—mainly because they offer good payment methods and had strong on-the-ground support to bootstrap them in the beginning.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Note that a weak offer book in a particular market doesn't ''necessarily'' mean trades don't take place in that market. It could be that there are people lurking there that will happily take an offer if you take the initiative to make one (this is often the case in markets like CAD, AUD, and GBP, for example).&lt;br /&gt;
&lt;br /&gt;
You can check trade history for your market by going to &amp;lt;code&amp;gt;Market&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Trades&amp;lt;/code&amp;gt; and picking your currency from the dropdown.}}&lt;br /&gt;
&lt;br /&gt;
If your market has no recent trades, a little more work will need to be done to get it going. At a minimum, payment methods common in your market should be added ([https://github.com/bisq-network/growth/issues/new/choose suggest them here]), and some form of marketing should be done to get users and market-makers to bootstrap a market.&lt;br /&gt;
&lt;br /&gt;
Bisq contributors are more than happy to help if you can help with guidance, connections to people who can help, and/or events and translations and other vehicles for reaching your target demographics.&lt;br /&gt;
&lt;br /&gt;
==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====&lt;br /&gt;
&lt;br /&gt;
Yes, the chicken-and-egg problem with Bisq is real. &lt;br /&gt;
&lt;br /&gt;
Here are some ways to get just enough bitcoin to do your first trade on Bisq:&lt;br /&gt;
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]&lt;br /&gt;
* hop onto the &amp;lt;code&amp;gt;Get your first BTC&amp;lt;/code&amp;gt; room on [https://bisq.chat Matrix] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])&lt;br /&gt;
&lt;br /&gt;
== Trading ==&lt;br /&gt;
&lt;br /&gt;
==== What are trading fees? ====&lt;br /&gt;
&lt;br /&gt;
[[Trading fees]] are calculated as a percentage of trade size: 0.1% for makers and 0.7% for takers if paid in BTC and about half of that if paid in BSQ.&lt;br /&gt;
&lt;br /&gt;
Keep in mind that you'll also need to pay [[mining fees]] for the on-chain transactions, as well as a deposit to lock into the multisig escrow. You'll get the deposit back in full after the trade completes successfully.&lt;br /&gt;
&lt;br /&gt;
==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====&lt;br /&gt;
&lt;br /&gt;
Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.&lt;br /&gt;
&lt;br /&gt;
Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.&lt;br /&gt;
&lt;br /&gt;
Other things you can do: &lt;br /&gt;
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)&lt;br /&gt;
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)&lt;br /&gt;
&lt;br /&gt;
==== Why does Bisq require a security deposit in BTC? ====&lt;br /&gt;
&lt;br /&gt;
[[Security deposit | Security deposits]] create strong incentives for buyers and sellers to follow the [[Trading rules|rules of Bisq's trading protocol]]. Deposits are locked into multisig escrow along with the bitcoin being traded, and are returned to each user when the trade is complete.&lt;br /&gt;
&lt;br /&gt;
If a trade is disputed through a mediator or arbitrator, some or all of the offending party's security deposit may be awarded to the counterparty. Examples of protocol violations include a buyer failing to pay a seller, paying with a different account or with a different name, or a seller failing to acknowledge receipt of a buyer's payment.&lt;br /&gt;
&lt;br /&gt;
Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.&lt;br /&gt;
&lt;br /&gt;
See full [[trading rules]].&lt;br /&gt;
&lt;br /&gt;
==== What are trading limits? How much bitcoin can I buy/sell at once? ====&lt;br /&gt;
&lt;br /&gt;
Trading limits vary based on payment method, since some payment methods are more secure than others.&lt;br /&gt;
&lt;br /&gt;
Relatively safe payment methods such as Japan's Furikomi and Australia's PayID are set to allow trades of up to 1 BTC, but other payment methods such as Zelle and SEPA have a cap of 0.25 BTC. See the [[Payment_methods|full list of payment methods and limits]].&lt;br /&gt;
&lt;br /&gt;
Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.&lt;br /&gt;
&lt;br /&gt;
==== Which payment methods are available? ====&lt;br /&gt;
&lt;br /&gt;
See [[payment methods]].&lt;br /&gt;
&lt;br /&gt;
If you'd like to suggest a payment method to be added, please [https://github.com/bisq-network/growth/issues/new/choose submit a new issue].&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq handle fiat like dollars and euros? Where does it go? ====&lt;br /&gt;
&lt;br /&gt;
Bisq doesn't handle fiat at all -- it only handles BTC. Trades are settled outside of Bisq, meaning fiat payments are sent outside Bisq via traditional banking services.&lt;br /&gt;
&lt;br /&gt;
Bisq merely matches peers and sets incentives (e.g. locking a BTC security deposit from both peers, as a sort of escrow) to encourage both trading peers to act in good faith. This is also why you need bitcoin to begin trading on Bisq.&lt;br /&gt;
&lt;br /&gt;
==== How long does a trade take? ====&lt;br /&gt;
&lt;br /&gt;
There is no automatic order matching on Bisq, and trades are settled manually by humans. As a result, trades are not completed as quickly as they would be on centralized exchanges, but can still be fairly quick. &lt;br /&gt;
&lt;br /&gt;
Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).&lt;br /&gt;
&lt;br /&gt;
As far as Bisq is concerned, the deposit transaction needs to be confirmed once before the buyer can send payment. Bitcoin transactions take about 10 minutes to confirm, so with quick traders and quick payment method, a Bisq trade can be completed in a matter of minutes.&lt;br /&gt;
&lt;br /&gt;
Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).&lt;br /&gt;
&lt;br /&gt;
See the list of [[payment methods]] for complete details.&lt;br /&gt;
&lt;br /&gt;
==== How does Bisq protect my privacy? ====&lt;br /&gt;
&lt;br /&gt;
Bisq is standalone, open-source software that you can inspect before running on your machine, and as a result, you don't have to trust that any server is logging your personal details (as you would in the case of a website).&lt;br /&gt;
&lt;br /&gt;
As for the trading process, your payment information is stored locally on your machine, and only your trading partner (and your mediator or arbitrator, in case of a dispute) can ever see it. All data exchanged between users is encrypted and signed.&lt;br /&gt;
&lt;br /&gt;
To transmit data from one user to another, Bisq uses a P2P network built on top of Tor, which provides a high degree of anonymity. The user doesn't need to do any additional work for all of this to work—it is all integrated in the application.&lt;br /&gt;
&lt;br /&gt;
==== Do I need to keep Bisq online for my offers to remain online? ====&lt;br /&gt;
&lt;br /&gt;
Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.&lt;br /&gt;
&lt;br /&gt;
If you have published an offer, your Bisq application needs to stay online so it can react when another trader wants to take your offer (the multisig deposit transaction is created in the take-offer process). Be sure you have deactivated your computer's standby mode so your Bisq application can stay online (monitor standby is not a problem).&lt;br /&gt;
&lt;br /&gt;
If your Bisq application does go offline, your offer will get removed from the distributed offerbook. It will be re-published the next time you start your Bisq application.&lt;br /&gt;
&lt;br /&gt;
After an offer has been taken and the trade process has started, neither trader needs to be online continuously, but each trader will need to be online periodically to check if any action is needed on their side (e.g. sending fiat/altcoin, confirming payment receipt, etc).&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq wallet? ====&lt;br /&gt;
&lt;br /&gt;
No, but you may find it convenient to keep a small amount of trading capital there.&lt;br /&gt;
&lt;br /&gt;
When entering a new trade on Bisq, you will get the option to transfer funds from your Bisq wallet ''or'' send funds from an external wallet.&lt;br /&gt;
&lt;br /&gt;
Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.&lt;br /&gt;
&lt;br /&gt;
==== Do I have to use the Bisq token? ====&lt;br /&gt;
&lt;br /&gt;
No, using BSQ is totally optional. However, using it gets you a ~50% discount on [[trading fees]] while helping to [[Introduction_to_the_DAO#Earn_and_distribute_revenue|compensate Bisq contributors]] at the same time.&lt;br /&gt;
&lt;br /&gt;
==== Will my bank know I'm trading bitcoin? ====&lt;br /&gt;
&lt;br /&gt;
Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.&lt;br /&gt;
&lt;br /&gt;
But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the &amp;quot;reason for payment&amp;quot; field always be left BLANK when making a payment (if the payment method offers such a field).&lt;br /&gt;
&lt;br /&gt;
If a reason is required, it should be something trivial like a &amp;quot;-&amp;quot; or &amp;quot;payment&amp;quot;. If you want to use something else, please agree on an alternative with your peer using trader chat.&lt;br /&gt;
See full [[trading rules]] for more information.&lt;br /&gt;
&lt;br /&gt;
== Common Technical Niggles ==&lt;br /&gt;
&lt;br /&gt;
==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ==== &lt;br /&gt;
&lt;br /&gt;
If Bisq won't open, try right-clicking the app and clicking &amp;lt;code&amp;gt;Open&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
If you get the prompt asking to record your keystrokes, rest assured it's a [https://github.com/bisq-network/bisq/issues/3373 bug] (Bisq is absolutely not recording your keystrokes). This bug should be fixed with a [[https://github.com/bisq-network/projects/issues/44|Java LTS version update]] coming soon.&lt;br /&gt;
&lt;br /&gt;
==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has had memory usage and CPU usage issue on certain operating systems in the past, but these issues should be resolved now. You can manually set the max RAM usage by following [[Reducing_memory_usage|these instructions]].&lt;br /&gt;
&lt;br /&gt;
Chances are Bisq is probably just trying to sync blockchain data. New releases of Bisq include data stores updated at release time to reduce this syncing time, but as a release gets older (i.e., beyond 3-4 weeks old), the data stores get older, and syncing takes longer. Just let it finish and your computer resources should go back down to normal again.&lt;br /&gt;
&lt;br /&gt;
If the issue doesn't go away on its own, please reach out for help in the &amp;lt;code&amp;gt;Support&amp;lt;/code&amp;gt; room [https://bisq.chat on Matrix] or open an issue [https://github.com/bisq-network/bisq on GitHub].&lt;br /&gt;
&lt;br /&gt;
==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====&lt;br /&gt;
&lt;br /&gt;
See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.&lt;br /&gt;
&lt;br /&gt;
==== Bisq says &amp;quot;this offer cannot be taken due to counterparty trade restrictions&amp;quot;. What does that mean? ====&lt;br /&gt;
&lt;br /&gt;
This happens in rare circumstances.  Bisq checks information about an account such as its age to determine if it is allowed to trade over certain limits.  The information is stored in the P2P network, and it may not yet have propagated to your node.  Try again after restarting Bisq.  The offer maker may need to restart Bisq in order for the information to propagate.&lt;br /&gt;
&lt;br /&gt;
==== My SPV resync is taking all day and it keeps freezing.  What can I do to make it go faster? ====&lt;br /&gt;
&lt;br /&gt;
Unfortunately this can happen sometimes if your wallet is over a year old and/or has a lot of transactions.  If the resync stalls, close and restart Bisq to continue the resync.  It will go faster if you [[Connecting_to_your_own_Bitcoin_node|connect to a local Bitcoin node]].&lt;br /&gt;
After your SPV resync is completed, it would be best to switch to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====&lt;br /&gt;
&lt;br /&gt;
The procedure involves setting aside the existing wallet directory (by renaming) in order to get a fresh wallet.  The wallet directory is at &amp;lt;code&amp;gt;btc_mainnet/wallet&amp;lt;/code&amp;gt; from the [[Data_directory|main data directory location]].  You'll then be able to activate either the old or new wallet by renaming the directory before starting Bisq.  Be sure that Bisq is never running when you rename a directory.&lt;br /&gt;
# You have some BSQ and also some BTC balance existing in your wallet.  (You need BTC to pay mining fees for sending BSQ).  &lt;br /&gt;
# Close Bisq then rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; directory to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt;. &lt;br /&gt;
# Start Bisq and it will create a fresh wallet.  Note down your BSQ receiving address and also your BTC receiving address.  Write down your recovery seed phrase (Under Account / Wallet Seed menu) and store it in a safe place (not online).  &lt;br /&gt;
# Close Bisq and rename your &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; dir to &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt;, rename your old wallet dir to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;, then restart Bisq.  &lt;br /&gt;
# Send BSQ to your new receiving address you saved in the earlier step.  Then send BTC the same way.  Close Bisq.  &lt;br /&gt;
# Rename &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;oldWallet&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;newWallet&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;wallet&amp;lt;/code&amp;gt;.  Then restart Bisq.&lt;br /&gt;
&lt;br /&gt;
Done!  Your BSQ and BTC balances have been moved to a fresh wallet.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;heightOfLastBlock must match chainHeight&amp;quot; error on starting Bisq ====&lt;br /&gt;
&lt;br /&gt;
The following procedure should fix itː&lt;br /&gt;
* make a backup of your data folder&lt;br /&gt;
* close Bisq&lt;br /&gt;
* from inside data folder, delete DaoStateStore and BsqBlocks&lt;br /&gt;
* restart Bisq&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Payment started&amp;quot; button will not stick, always says &amp;quot;Please send confirmation again&amp;quot; ====&lt;br /&gt;
&lt;br /&gt;
This is a known issue, and it's because the application will err on the side of caution when P2P network conditions are less than favourable.&lt;br /&gt;
It most often happens when the peer is offline, so usually when a seller taker accepts an open offer with a non-instant payment method, like SEPA, and then goes offline, since the payment will take at least a day to be credited and they do not need to stay connected while the buyer maker's payment arrives.&lt;br /&gt;
Here are some things that might work&lt;br /&gt;
* Send a message in trader chat&lt;br /&gt;
* Insist on pressing the button tens of times&lt;br /&gt;
* Restart Bisq&lt;br /&gt;
* Do nothing and stay online, as the button will sometimes finally &amp;quot;register&amp;quot; by itself with a random delay&lt;br /&gt;
* When everything else fails, and the trade period is almost at its end, communicate your intentions to the peer in trader chat and open mediation by pressing Ctrl-O in trade window, explaining what happened to the mediator, even better by attaching a screenshot of the issue; a support ticket will be opened and both peers will have the opportunity to accept the original payout&lt;br /&gt;
&lt;br /&gt;
== Dispute resolution ==&lt;br /&gt;
&lt;br /&gt;
==== How does dispute resolution work? ====&lt;br /&gt;
&lt;br /&gt;
Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.&lt;br /&gt;
&lt;br /&gt;
Trader chat enables traders to resolve small issues themselves privately over end-to-end encrypted chat right in Bisq. If this doesn't work, traders can engage a mediator to examine the situation and suggest a payout. In rare circumstances that mediation fails, a trader can choose to engage an arbitrator to re-examine the situation and make a payout.&lt;br /&gt;
&lt;br /&gt;
Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.&lt;br /&gt;
&lt;br /&gt;
See [[trading rules]] and [[dispute resolution]] for more.&lt;br /&gt;
&lt;br /&gt;
==== How is collusion between mediators, arbitrators, and traders prevented? ====&lt;br /&gt;
&lt;br /&gt;
With the launch of the new trading protocol in v1.2, multisig escrows went from 2-of-3 to 2-of-2 arrangements, so that only the two trading peers have control of trading funds (instead of the 2 trading peers and an arbitrator). With no keys in the multisig escrow, it is no longer possible for a mediator or arbitrator to collude with another trader to release funds maliciously.&lt;br /&gt;
&lt;br /&gt;
Mediators and arbitrators are still bonded roles, however, because even though they cannot sign a payout transaction to resolve a dispute, they can ''advise'' how to resolve a dispute, and it's important that they be responsive, responsible, and fair when doing so.&lt;br /&gt;
&lt;br /&gt;
==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====&lt;br /&gt;
&lt;br /&gt;
Bisq only supports payment methods for which chargebacks are not easy (e.g., this is why PayPal and credit cards are not supported). But there is still a little chargeback risk with banks. If a bank executes a chargeback after the BTC has been released, there is nothing a mediator or arbitrator can do.&lt;br /&gt;
&lt;br /&gt;
Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:&lt;br /&gt;
&lt;br /&gt;
# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.&lt;br /&gt;
# [[Account_limits#Account_signing|Account signing]] requires higher-risk payment methods to be signed upon verifying the integrity of a trader before account aging kicks in. Until such accounts are signed, buy limits are set to 0.01 BTC.&lt;br /&gt;
# National currency payment methods which are found to be used for chargebacks are quickly removed.&lt;br /&gt;
&lt;br /&gt;
==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====&lt;br /&gt;
&lt;br /&gt;
Pure reputation without additional dispute resolution measures is a weak protection system, as you can never avoid [https://en.wikipedia.org/wiki/Sybil_attack sybil] or [https://en.wikipedia.org/wiki/Confidence_trick long con] attacks.&lt;br /&gt;
&lt;br /&gt;
Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.&lt;br /&gt;
&lt;br /&gt;
==== How can I contact my trading peer? ====&lt;br /&gt;
&lt;br /&gt;
Bisq has a built-in end-to-end encrypted [[Dispute_resolution#Level_1:_Trader_chat|chat mechanism]] that you can use to talk to your trading peer while the trade is in progress.&lt;br /&gt;
&lt;br /&gt;
== DAO ==&lt;br /&gt;
&lt;br /&gt;
==== What is the Bisq DAO? ====&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO (decentralized autonomous organization) is a decentralized governance mechanism for the Bisq software, built on Bitcoin. It takes the place of a company. How good can decentralized software possibly be if it's still controlled by a single entity, like a company?&lt;br /&gt;
&lt;br /&gt;
Decentralized software is no good without decentralized governance.&lt;br /&gt;
&lt;br /&gt;
That's why Bisq is not a company or legal entity of any kind—instead, it's organized as a DAO. The DAO handles the software's funding and strategy-making to enable the Bisq network to thrive, and at the same time, harden it against attacks on the infrastructure that powers its leadership and operation.&lt;br /&gt;
&lt;br /&gt;
In a nutshell, the Bisq DAO enables Bisq to become even more censorship-resistant, a core [[Introduction|principle of the project]] from the very beginning.&lt;br /&gt;
&lt;br /&gt;
Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].&lt;br /&gt;
&lt;br /&gt;
==== How does the Bisq DAO work? ====&lt;br /&gt;
&lt;br /&gt;
The primary purposes of the Bisq DAO are financing the project and determining strategy.&lt;br /&gt;
&lt;br /&gt;
# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.&lt;br /&gt;
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.&lt;br /&gt;
&lt;br /&gt;
Learn more about how this actually works in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this series of short 3-5 minute videos].&lt;br /&gt;
&lt;br /&gt;
See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.&lt;br /&gt;
&lt;br /&gt;
==== What do I need to know about the DAO, as a trader? ====&lt;br /&gt;
&lt;br /&gt;
First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.&lt;br /&gt;
&lt;br /&gt;
But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.&lt;br /&gt;
&lt;br /&gt;
But why have the BSQ token at all? Because it enables Bisq contributors to be paid for their work without any central wallets or points of control. When you buy BSQ, you're directly paying a Bisq contributor for their work, and in the process, helping to sustain the whole project. The dynamic this token enables is not possible with plain bitcoin.&lt;br /&gt;
&lt;br /&gt;
When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.&lt;br /&gt;
&lt;br /&gt;
[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].&lt;br /&gt;
&lt;br /&gt;
==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====&lt;br /&gt;
&lt;br /&gt;
Bisq already earns revenue from trading fees. It's not launching this DAO and BSQ token for ''earning'' revenue—it's doing it to ''distribute'' the revenue it already earns to more people without any central points of control.&lt;br /&gt;
&lt;br /&gt;
BSQ tokens are issued every time a contributor's compensation request is approved through voting, and the tokens are destroyed every time a trader uses BSQ to pay trading fees.&lt;br /&gt;
&lt;br /&gt;
BSQ issuance is not a 1-time event, and its purpose is not to raise capital. You can see a walk-through of the BSQ issuance process in [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e this video series].&lt;br /&gt;
&lt;br /&gt;
==== Can I use Bisq without BSQ and without this DAO? ====&lt;br /&gt;
&lt;br /&gt;
You could. All you'd have to do is pay your trading fees with BTC instead of BSQ. But we hope you don't, because doing so would render the project unsustainable.&lt;br /&gt;
&lt;br /&gt;
Before the Bisq DAO, trading fees went to just a couple of wallets owned by specific Bisq contributors (arbitrators). All other contributors were not paid. Bisq needs its contributors to be paid in regular, predictable ways to ensure continual (and reliable) development, service, and growth; the Bisq DAO enables this to happen by distributing trading fees to all contributors in a totally decentralized way.&lt;br /&gt;
&lt;br /&gt;
The Bisq DAO and BSQ token enable a funding and governance mechanism that is [[https://bisq.network/blog/bisq-dao-for-bitcoin-maximalists/ not possible with plain bitcoin]]. We highly recommend you check [[Decentralized_autonomous_organization|out the documentation]] and [https://www.youtube.com/playlist?list=PLFH5SztL5cYPAXWFz-IMB4dBZ0MEZEG_e video series]] to learn more.&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
==== This project is cool! How can I help out? ====&lt;br /&gt;
&lt;br /&gt;
Check out the [[contributor checklist]]. We'd love to hear from you!&lt;br /&gt;
&lt;br /&gt;
==== I have a question that isn’t covered here...? ====&lt;br /&gt;
&lt;br /&gt;
Feel free to reach out on [https://bisq.chat Matrix] or [https://bisq.network/#community any other channel].&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Trading_rules&amp;diff=2973</id>
		<title>Trading rules</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Trading_rules&amp;diff=2973"/>
		<updated>2022-04-09T20:54:14Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Do not communicate with buyers away from Bisq */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Both Bisq traders must follow these '''trading rules''' to ensure smooth and successful trades.&lt;br /&gt;
&lt;br /&gt;
To trade on Bisq, you assume one of two roles, no matter what national currency or cryptocurrency you’re trading: you either ''buy bitcoin'' or ''sell bitcoin''.&lt;br /&gt;
&lt;br /&gt;
The rules below are '''default''' rules for every transaction. Offer makers sometimes specify their own additional terms for handling payments. For example, a seller using cash deposits might require a picture of a receipt torn in half with &amp;quot;NO REFUND&amp;quot; written on it. Face-to-face traders often specify terms about where and how to meet. &lt;br /&gt;
&lt;br /&gt;
Make sure you’re okay with an offer-maker’s terms '''before''' you accept an offer!&lt;br /&gt;
&lt;br /&gt;
Trade rules also help with the following:&lt;br /&gt;
&lt;br /&gt;
* Promoting good behavior from traders&lt;br /&gt;
* Penalizing bad behavior from traders&lt;br /&gt;
* Promoting good payment accounts of traders&lt;br /&gt;
* Penalizing bad payment accounts of traders&lt;br /&gt;
* Put the 'wrong doer' in a worse position and the person 'not at fault' in a better position&lt;br /&gt;
&lt;br /&gt;
= Rules for bitcoin sellers =&lt;br /&gt;
&lt;br /&gt;
Whether making or taking an offer, bitcoin sellers put all the bitcoin they’re selling in the multisig escrow, so there’s less for them to do and fewer rules they need to follow.&lt;br /&gt;
&lt;br /&gt;
=== Click &amp;lt;code&amp;gt;Confirm payment&amp;lt;/code&amp;gt; after receiving payment ===&lt;br /&gt;
&lt;br /&gt;
Sellers have until the end of the maximum trade period to do so.&lt;br /&gt;
&lt;br /&gt;
[[Account_limits#Account_signing|Account signing]], introduced in Bisq v1.2, enables a seller with a signed payment account to sign a buyer’s payment account when they successfully receive a payment. For such trades, it is recommended that the seller take as long as possible (i.e., wait until close to the end of the trade period) to confirm receipt of payment to reduce the chance of a chargeback.&lt;br /&gt;
&lt;br /&gt;
=== Collaborate with mediators and arbitrators ===&lt;br /&gt;
&lt;br /&gt;
In case of a dispute, users must respond to inquiries within 48 hours and providing materials as requested to determine an outcome.&lt;br /&gt;
&lt;br /&gt;
Mediators may take up to 48 hours to respond to messages, and arbitrators may take up to 5 days to respond to messages.&lt;br /&gt;
&lt;br /&gt;
=== Do not change payment details once trade is in progress ===&lt;br /&gt;
&lt;br /&gt;
Once the deposit transaction is published, the trade is in progress, and its terms cannot be changed. The seller had agreed to be paid as specified in the trade contract.&lt;br /&gt;
&lt;br /&gt;
In the event of an unexpected circumstance (e.g., hitting a bank-imposed transfer limit), seller can propose alternatives through trader chat or mediation, but buyer is not required to comply. It is the seller to ensure that the payment account in their offer will work before an offer is taken.&lt;br /&gt;
&lt;br /&gt;
=== Do not confirm payments with mismatching details ===&lt;br /&gt;
&lt;br /&gt;
Payer name, payment method, institution, and other details of a payment should ''exactly'' match the details in the trade contract. '''If not, the payment should not be accepted.'''&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|This is especially relevant for trades in which a signed seller trades with an unsigned buyer, because confirmation of payment receipt signs the buyer’s payment account. In case of such an issue, a dispute should be opened.}}&lt;br /&gt;
&lt;br /&gt;
=== Do not communicate with buyers away from Bisq ===&lt;br /&gt;
&lt;br /&gt;
Using email addresses, phone numbers, and other means to contact traders is strongly discouraged. The trader chat feature built into Bisq should be used instead: not only is it more private, but the chat record can more easily be made available to mediators and arbitrators (useful in case a trader’s chat messages indicate they broke a rule). This includes advertising offers to sell BTC with a way to contact you, for example a website, Telegram user name, or email.&lt;br /&gt;
&lt;br /&gt;
At this point, the software itself does not provide a way to relay the message record between 2 traders to a mediator or arbitrator, so other means of sharing the chat record will be used if needed.&lt;br /&gt;
&lt;br /&gt;
= Rules for bitcoin buyers =&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|To avoid unexpected issues, make sure you can actually carry out a payment with the payment method you’ve set up in Bisq. Examples: Wells Fargo doesn’t allow cash deposits into bank accounts not owned by the depositor, and Zelle has weekly and monthly transfer maximums that are easy to overlook. The software will warn you about known issues, but cannot possibly keep up with all the newest banking and money transfer rules.}}&lt;br /&gt;
&lt;br /&gt;
=== Make payment reasonably early within trade period ===&lt;br /&gt;
&lt;br /&gt;
Buyer should complete at a time such that the seller has enough time to acknowledge receipt of the payment before the trade period is over. Waiting until the very end of the trade period to make a payment is not advised, as then the seller cannot reasonably act in time to acknowledge receipt (also, it’s annoying). The lengths of trade periods vary based on [[Payment methods|payment method]].&lt;br /&gt;
&lt;br /&gt;
This is especially important for buyers with unsigned payment accounts trading with sellers with signed payment accounts. A seller will not want to confirm receipt of a payment made at the last minute from an untrusted account, so if you’re a buyer looking to get your payment account signed, you should make the payment ''as soon as possible''.&lt;br /&gt;
&lt;br /&gt;
=== Use same payment account in trade contract === &lt;br /&gt;
&lt;br /&gt;
Intermediary banks or other payment methods from the same bank are not acceptable. Account information (e.g., name, account number, etc) of the account used to make the payment must '''exactly''' match the information in the Bisq payment account details.&lt;br /&gt;
&lt;br /&gt;
If such a payment cannot be made, please communicate the issue through trader chat, or you’ll need to make your case to a mediator or arbitrator.&lt;br /&gt;
&lt;br /&gt;
=== Click Payment started after sending payment ===&lt;br /&gt;
&lt;br /&gt;
Seller cannot mark payment as received until buyer confirms that they have sent it. &lt;br /&gt;
&lt;br /&gt;
Don’t forget to do this!&lt;br /&gt;
&lt;br /&gt;
=== Leave the &amp;quot;reason for payment&amp;quot; field empty ===&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|Before 1.5.5, it was required to put the trade ID in the 'reason for payment' field of a payment. As of 1.5.5, reason for payment should be left BLANK.}}&lt;br /&gt;
&lt;br /&gt;
Some payments offer a way to specify a reason for payment (some payment methods call it &amp;quot;Message&amp;quot; or &amp;quot;Information for recipient&amp;quot; or similar). '''Leave this field BLANK.''' Do not put the trade ID, any mentions of &amp;quot;Bisq&amp;quot; or &amp;quot;Bitcoin&amp;quot; or &amp;quot;crypto&amp;quot;, or any other text whatsoever.&lt;br /&gt;
&lt;br /&gt;
If you are required to fill in a reason, use your account name eg &amp;quot;Joe Bloggs&amp;quot; alternatively enter something non-descriptive like a dash &amp;quot;-&amp;quot;. If you would prefer to use other text please agree this with your peer in trader chat. Please remember your peer is not obligated to agree anything and may not want to agree to anything other than leaving the description blank, your name or a dash. &lt;br /&gt;
&lt;br /&gt;
Violating this rule will likely result in a [[Table of penalties|trade penalty]]. &lt;br /&gt;
&lt;br /&gt;
Many banks don’t like anything related to Bitcoin, and may take draconian measures if they sense such a transaction.&lt;br /&gt;
&lt;br /&gt;
Many users trade from personal accounts and may object to using anything that looks like it could be a commercial transaction.&lt;br /&gt;
&lt;br /&gt;
=== Pay any transaction fees ===&lt;br /&gt;
&lt;br /&gt;
Any fees incurred to make the payment via the agreed payment method (e.g., bank fees for bank transfer, money-order fees for money orders, etc) are the buyer’s responsibility to pay.&lt;br /&gt;
&lt;br /&gt;
The seller should receive the exact amount of the trade. The only exception to this rule is if the receiving institution imposes a fee on incoming payments—these fees are borne by the seller.&lt;br /&gt;
&lt;br /&gt;
=== Collaborate with mediators and arbitrators ===&lt;br /&gt;
&lt;br /&gt;
In case of a dispute, users must respond to inquiries within 48 hours and providing materials as requested to determine an outcome.&lt;br /&gt;
&lt;br /&gt;
Mediators may take up to 48 hours to respond to messages, and arbitrators may take up to 5 days to respond to messages.&lt;br /&gt;
&lt;br /&gt;
=== Do not communicate with sellers away from Bisq ===&lt;br /&gt;
&lt;br /&gt;
Using email addresses, phone numbers, and other means to contact traders is strongly discouraged. The trader chat feature built into Bisq should be used instead: not only is it more private, but the chat record can more easily be made available to mediators and arbitrators (useful in case a trader’s chat messages indicate they broke a rule). This includes advertising offers to buy BTC with a way to contact you for example; a website, Telegram user name, or email.&lt;br /&gt;
&lt;br /&gt;
At this point, the software itself does not provide a way to relay the message record between 2 traders to a mediator or arbitrator, so other means of sharing the chat record will be used if needed.&lt;br /&gt;
&lt;br /&gt;
= What happens when things go wrong? =&lt;br /&gt;
&lt;br /&gt;
Sometimes trades do not go to plan for whatever reason. &lt;br /&gt;
&lt;br /&gt;
It is prudent for all traders to know when entering into the trade what will happen when things go wrong. Traders would be wise to make themselves aware of the [[dispute resolution]] process to ensure there are no surprises.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Cash_by_mail&amp;diff=2972</id>
		<title>Cash by mail</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Cash_by_mail&amp;diff=2972"/>
		<updated>2022-04-09T20:53:06Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Making a CBM offer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Cash by mail''' (CBM) is one of the most private payment methods on Bisq. &lt;br /&gt;
&lt;br /&gt;
This payment method has special requirements you should be aware of, so please read this article carefully before doing any cash by mail trades.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
= Setting up a CBM account in Bisq =&lt;br /&gt;
&lt;br /&gt;
When setting up cash-by-mail payment account in Bisq, you will be asked to enter the following information:&lt;br /&gt;
&lt;br /&gt;
* Name or nym the package should be addressed to&lt;br /&gt;
* Postal address &lt;br /&gt;
* Currency &lt;br /&gt;
* Additional information &lt;br /&gt;
&lt;br /&gt;
If selling BTC, the name/nym and address fields should be the name you would like to buyer to address the package to. If buying BTC, the name/nym and address fields should be the name the seller or postal service to return the package to in case of any issues.&lt;br /&gt;
&lt;br /&gt;
You can only select one currency for a single cash-by-mail account. If you would like to trade with more than one currency, please create separate accounts for each currency.&lt;br /&gt;
&lt;br /&gt;
Define any special terms, conditions, or details you would like to be displayed with your offers in the 'Additional Information' field. '''Users can see this field ''before'' taking the offer by clicking the info icon of the offer.''' &lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Consider setting up separate cash-by-mail accounts for buying and selling so you can specify special instructions for each.}}&lt;br /&gt;
&lt;br /&gt;
= Making a CBM offer =&lt;br /&gt;
&lt;br /&gt;
Make sure to state any special terms or conditions in the 'Additional Information' field of the payment account before making an offer. The person taking the offer will be accepting these terms and conditions by taking the offer.&lt;br /&gt;
&lt;br /&gt;
Please note it is against Bisq rules to use the 'Additional Information' field to include advertising offers with a way to contact you prior to the trade (e.g. website, phone, email, or Matrix/Keybase/Telegram user name). Doing this can result in a penalty, should someone take your offer and request for you to be penalized.&lt;br /&gt;
&lt;br /&gt;
= Taking a CBM offer =&lt;br /&gt;
&lt;br /&gt;
'''Make sure to check the offer maker's terms and conditions before taking a CBM offer.''' If you cannot fulfill the terms, do not take the the offer. If you have specific terms you would prefer, consider making your own offer instead.&lt;br /&gt;
&lt;br /&gt;
= Sending cash in the mail =&lt;br /&gt;
&lt;br /&gt;
Please see the Bisq trade protocol for [[Trading_rules|general trading rules]].&lt;br /&gt;
&lt;br /&gt;
In addition, buyers should:&lt;br /&gt;
&lt;br /&gt;
* Package cash in a tamper-evident cash bag. You can get one at [https://shop.fulmo.org/product/tamper-proof-courier-bags/ the FULMO shop] (the Bisq project gains nothing for providing this link. Fulmo is a friendly member of the Bisq community).&lt;br /&gt;
* Place tamper-evident cash bag inside another package.&lt;br /&gt;
* Address the package to the name and address in the seller's cash-by-mail payment account.&lt;br /&gt;
* Follow any special requirements and conditions set by the seller.&lt;br /&gt;
* Film or take high-resolution photos of the cash packaging process with the address and tracking number already affixed to packaging.&lt;br /&gt;
* Send the cash package to the BTC seller with a courier service that requires receipt of delivery to be confirmed by the seller.&lt;br /&gt;
* Consider using a courier service that has appropriate insurance in place for any issues with delivery.&lt;br /&gt;
* Communicate with courier service as required.&lt;br /&gt;
&lt;br /&gt;
'''Please make sure you have all the necessary items arranged ''before'' taking an offer (tamper-evident cash bags, other packaging, courier and insurance picked out, etc).'''&lt;br /&gt;
&lt;br /&gt;
= Receiving cash in the mail =&lt;br /&gt;
&lt;br /&gt;
When receiving cash in the mail, you should:&lt;br /&gt;
&lt;br /&gt;
* Film the opening of the package, making sure that the tracking number provided by the sender is visible in the video.&lt;br /&gt;
* Follow any special requirements and conditions set by the buyer.&lt;br /&gt;
* Communicate with buyer's courier service as required.&lt;br /&gt;
&lt;br /&gt;
= Dispute resolution =&lt;br /&gt;
&lt;br /&gt;
Cash-by-mail trades are less verifiable than other fiat trades. This makes handling disputes much harder, so the onus to act honestly is squarely on both peers.&lt;br /&gt;
&lt;br /&gt;
It is highly recommended for peers to make use of Bisq's trader chat to communicate directly with one another. This is the most promising way to resolve any issues that may arise during the trade.&lt;br /&gt;
&lt;br /&gt;
Regarding dispute resolution, please note:&lt;br /&gt;
&lt;br /&gt;
* Mediators can consider your case and make a suggestion, but they are NOT guaranteed to help.&lt;br /&gt;
* If a mediator is engaged, and if either peer rejects the mediator's suggestion, both peers' funds will be sent to a [https://bisq.wiki/Arbitration#Time-Locked_Payout_Transaction Bisq 'donation' address], and the trade will effectively be completed.&lt;br /&gt;
* If a trader rejects a mediation suggestion and opens arbitration, it could lead to lose both trading and deposit funds.&lt;br /&gt;
* Arbitrators will make a decision based on the evidence provided to them. Therefore, please follow and document the above processes to have evidence in case of dispute. For cash-by-mail trades, arbitrator decisions are final, meaning reimbursement requests to the Bisq DAO for any funds lost in cash-by-mail trades will NOT be considered.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2971</id>
		<title>Face-to-face (payment method)</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Face-to-face_(payment_method)&amp;diff=2971"/>
		<updated>2022-04-09T20:52:10Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Making a F2F offer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bisq can help users arrange '''face-to-face''' (F2F) trades to buy and sell bitcoin. &lt;br /&gt;
&lt;br /&gt;
Done correctly, this may be the only payment method that can be both private ''and'' anonymous. But there are a number of things you should consider when doing a F2F trade on Bisq. &lt;br /&gt;
&lt;br /&gt;
F2F trades are ''technically'' very similar to online trades. In fact, to carry out a F2F trade, you follow the exact same process within the Bisq software as you would for any other trade. The difference is in how the buyer pays the seller: instead of paying through a financial intermediary (like a bank or other money transfer service), the buyer meets the seller in real life and pays with cash.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Setting up a F2F account in Bisq =&lt;br /&gt;
&lt;br /&gt;
When setting up a F2F payment account in Bisq, you will be asked to enter the following information:&lt;br /&gt;
&lt;br /&gt;
* Country&lt;br /&gt;
* Currency &lt;br /&gt;
* City (this will be displayed with the offer)&lt;br /&gt;
* How would you like to be contacted by the trading peer (Please. state the method of contact you would be happy with eg; Telegram, Matrix, Email, Phone. Please do not list your actual contact details)&lt;br /&gt;
* Additional information  (for example where you would like to complete the trade.)&lt;br /&gt;
&lt;br /&gt;
You can only select one currency for a single cash-by-mail account. If you would like to trade with more than one currency, please create separate accounts for each currency.&lt;br /&gt;
&lt;br /&gt;
Define any special terms, conditions, or details you would like to be displayed with your offers in the 'Additional Information' field. '''Users can see this field ''before'' taking the offer by clicking the info icon of the offer.''' &lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|Consider setting up separate F2F accounts for buying and selling so you can specify special instructions for each.}}&lt;br /&gt;
&lt;br /&gt;
= Making a F2F offer =&lt;br /&gt;
&lt;br /&gt;
Make sure to state any special terms or conditions in the 'Additional Information' field of the payment account before making an offer. The person taking the offer will be accepting these terms and conditions by taking the offer. For example you could include that you are looking to complete the trade in a Starbucks within the city center.&lt;br /&gt;
&lt;br /&gt;
Please note it is against Bisq rules to use the 'Additional Information' field to include advertising offers with a way to contact you prior to the trade (e.g. website, phone, email, or Matrix/Keybase/Telegram user name). Doing this can result in a penalty, should someone take your offer and request for you to be penalized.&lt;br /&gt;
&lt;br /&gt;
= Taking a F2F offer =&lt;br /&gt;
&lt;br /&gt;
'''Make sure to check the offer maker's terms and conditions before taking a F2F offer.''' If you cannot fulfill the terms, do not take the the offer. If you have specific terms you would prefer, consider making your own offer instead.&lt;br /&gt;
&lt;br /&gt;
== Meeting your trading partner ==&lt;br /&gt;
&lt;br /&gt;
Doing a transaction face-to-face means you’ll be coming within close proximity of a stranger to exchange relatively substantial value.&lt;br /&gt;
&lt;br /&gt;
=== Be safe ===&lt;br /&gt;
&lt;br /&gt;
People do local, in-person commerce all the time, all over the world. Incidents are rare, but they do happen. You should be cognizant of risks and do your part to minimize potential harm.&lt;br /&gt;
&lt;br /&gt;
'''Guard your data.''' When you set up a face-to-face payment account in Bisq, you’ll need to provide contact information so you can arrange a meeting with your trading partner. Make sure this information isn’t traceable back to your property or identity.&lt;br /&gt;
&lt;br /&gt;
'''Meet in a neutral public place.''' Meeting your trading partner in a place with witnesses and security cameras significantly reduces the chance of an incident.&lt;br /&gt;
&lt;br /&gt;
'''Don’t bring more than you need.''' Even in a public place, incidents can still happen, but you can limit the chance even further by limiting valuables on your person that would interest a thief in the first place.&lt;br /&gt;
&lt;br /&gt;
'''Bring backup.''' Consider bringing a friend with you. Also, depending on the laws in your area &amp;amp; your own comfort, consider carrying a concealed tool for self-defense. Even pepper-spray can hobble a criminal just enough to get you out of immediate danger.&lt;br /&gt;
&lt;br /&gt;
=== Validate payment ===&lt;br /&gt;
&lt;br /&gt;
Face-to-face trades are usually settled with cash. Cash is wonderfully anonymous, but it can be counterfeited. Be sure you know the basics of detecting counterfeit currency. For example, there are several characteristics of US dollar bills one can examine to quickly determine fakes with high accuracy.&lt;br /&gt;
&lt;br /&gt;
You could look for tools like counterfeit pens to do the work for you, but make sure you do thorough research before picking one. Counterfeit pens, for example, are often not reliable.&lt;br /&gt;
&lt;br /&gt;
If you’d rather not take the chance of carrying or accepting cash, consider meeting at a bank where you can validate a buyer’s payment on the spot.&lt;br /&gt;
&lt;br /&gt;
=== Ensure you follow Bisq protocol ===&lt;br /&gt;
&lt;br /&gt;
Ultimately, the deal will be completed in Bisq. Buyers must mark payment as sent before sellers can release assets.&lt;br /&gt;
&lt;br /&gt;
'''Buyers''' should bring a laptop with them so they can mark the payment as sent. Otherwise, the buyer will end up paying the seller and have to walk away without the bitcoin they paid for (since the seller won’t be able to acknowledge receipt of payment before the buyer acknowledges they sent payment).&lt;br /&gt;
&lt;br /&gt;
'''Sellers''' should bring a laptop with their Bisq client running no matter what. Once they receive a legitimate payment, they’ll need to mark the payment as received so the assets are released to the buyer. No buyer will want to walk away after paying without proof of a complete deal.&lt;br /&gt;
&lt;br /&gt;
== Disputes ==&lt;br /&gt;
&lt;br /&gt;
The lack of verifiable actions makes handling face-to-face disputes much harder.&lt;br /&gt;
&lt;br /&gt;
This is why we highly recommend that both parties bring laptops and acknowledge their ends of the deal on the spot.&lt;br /&gt;
&lt;br /&gt;
Otherwise, the same dispute process is in place for F2F trades, but be advised that mediators and arbitrators often won’t have a way to settle disputes. In such cases, aggrieved traders can send deposit funds to the donation address and [[Making_a_reimbursement_request|make an appeal to the Bisq DAO]].&lt;br /&gt;
&lt;br /&gt;
Having said that, mediators and arbitrators may attempt different tactics to get a handle on the situation. For example, they may ask a potential scammer for ID verification, which is a request a real scammer probably wouldn’t comply with.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2964</id>
		<title>Downloading and installing</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2964"/>
		<updated>2022-03-23T17:35:48Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* macOS and Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.&lt;br /&gt;
&lt;br /&gt;
Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.&lt;br /&gt;
&lt;br /&gt;
Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.&lt;br /&gt;
&lt;br /&gt;
All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.&lt;br /&gt;
&lt;br /&gt;
== Download Bisq ==&lt;br /&gt;
&lt;br /&gt;
The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].&lt;br /&gt;
&lt;br /&gt;
There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}&lt;br /&gt;
&lt;br /&gt;
You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.&lt;br /&gt;
&lt;br /&gt;
'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''&lt;br /&gt;
&lt;br /&gt;
== Verify installer file ==&lt;br /&gt;
&lt;br /&gt;
Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.&lt;br /&gt;
&lt;br /&gt;
This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.&lt;br /&gt;
&lt;br /&gt;
Bisq installer files are currently built and signed by Christoph Atteneder (ripcurlx). His public key ID is &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; and fingerprint is &amp;lt;code&amp;gt;CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B&amp;lt;/code&amp;gt;, which you can verify through [https://github.com/bisq-network/bisq/commits?author=ripcurlx commits on GitHub] and [https://keybase.io/ripcurlx on Keybase].&lt;br /&gt;
&lt;br /&gt;
The full public key is available [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
=== Obtain signature files for installer files ===&lt;br /&gt;
&lt;br /&gt;
To verify your installer file is intact and as the developer intended, you will need the PGP signature file corresponding to the installer file you downloaded.&lt;br /&gt;
&lt;br /&gt;
On the [https://bisq.network/downloads/ Bisq website's download page], download the PGP signature file for the installer file you downloaded before.&lt;br /&gt;
&lt;br /&gt;
If you prefer to download from GitHub, you will see the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file for your installer in the assets section [https://github.com/bisq-network/bisq/releases/latest of the release] along with the installer file itself.&lt;br /&gt;
&lt;br /&gt;
In either case, the filename for the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; you download should be identical to the filename for the installer file, just with &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; appended (e.g., signature file for &amp;lt;code&amp;gt;Bisq-1.2.7.dmg&amp;lt;/code&amp;gt; would be &amp;lt;code&amp;gt;Bisq-1.2.7.dmg.asc&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
Once you've got the installer file and its corresponding signature file, proceed to the directions for your operating system below.&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
&lt;br /&gt;
Once you have downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Download ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Download ripcurlx's public key [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
'''Download and install Gpg4win'''&lt;br /&gt;
&lt;br /&gt;
Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq's installer files.&lt;br /&gt;
&lt;br /&gt;
You can get Gpg4win [https://www.gpg4win.org/ here].&lt;br /&gt;
&lt;br /&gt;
Double-click the installer file and proceed to install with all default settings.&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
In Kleopatra, import ripcurlx's public key file &amp;lt;code&amp;gt;29CDFD3B.asc&amp;lt;/code&amp;gt;. Select ''No'' if asked to mark the certificate as valid.&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
With the &amp;lt;code&amp;gt;install-file.exe&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;signature-file.exe.asc&amp;lt;/code&amp;gt; in the same directory, double-click on the &amp;lt;code&amp;gt;.exe.asc&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
You should see a Kleopatra window pop up with a green progress bar that says &amp;quot;Verified .exe with .exe.asc&amp;quot;. The program will continue to say &amp;quot;The data could not be verified&amp;quot; in bold but you can disregard that message.&lt;br /&gt;
&lt;br /&gt;
This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the &amp;lt;code&amp;gt;.exe&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
=== macOS and Linux ===&lt;br /&gt;
&lt;br /&gt;
Once you've downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You might see an ominous sounding warning along the lines of &amp;quot;This key is not certified with a trusted signature&amp;quot;. This basically means that none of the public keys on your machine have signed the key you just imported. It also means that you have not explicitly indicated you trust this key yourself. This is not necessarily a bad thing, but please see more about what this means [https://serverfault.com/a/569923 here]. In short, you can verify the integrity of this key by [[ #Verify installer file | cross-referencing ripcurlx's Bisq commit signatures and Keybase profile]].&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with GPG (a free open source version of PGP) you probably need to install GPG command line tools first.&lt;br /&gt;
Following instructions are taken from https://blog.ghostinthemachines.com/2015/03/01/how-to-use-gpg-command-line.&lt;br /&gt;
&lt;br /&gt;
The easiest way to install the GPG command line tools on your Mac is to first install Homebrew, a package management system that makes thousands of software packages available for install on your Mac.&lt;br /&gt;
&lt;br /&gt;
Open a Terminal window (Applications &amp;gt; Utilities menu), then enter the following command.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;ruby -e &amp;quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&amp;quot; &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When that’s complete, install the GPG software package with the following command.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;brew install gnupg &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With the installer file and installer signature file in the same directory, run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;gpg --digest-algo SHA256 --verify SIGNATURE-FILE.asc &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; is the filename of the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file you just downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Common errors'''&lt;br /&gt;
&lt;br /&gt;
 gpg: directory '/Users/bisq/.gnupg' created&lt;br /&gt;
 gpg: keybox '/Users/bisq/.gnupg/pubring.kbx' created&lt;br /&gt;
 gpg: can't open 'SIGNATURE-FILE.asc': No such file or directory&lt;br /&gt;
 gpg: verify signatures failed: No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you haven't replaced &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; with the actual signature file you want to use e.g. &amp;lt;code&amp;gt;Bisq-1.6.4.dmg.asc&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 gpg: can't open 'Bisq-1.6.4.dmg.asc': No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you either haven't downloaded the signature file already or you are not in the correct directory. You can run &amp;lt;code&amp;gt;pwd&amp;lt;/code&amp;gt; to see the path you are in.&lt;br /&gt;
If you want to switch to the directory, where the downloaded files are you can use the [https://www.git-tower.com/learn/git/ebook/en/command-line/appendix/command-line-101/#:~:text=It%20will%20return%20the%20path,%24%20cd%20.. `cd` command] and switch to the correct directory by typing e.g. &amp;lt;code&amp;gt;cd ~/Downloads&amp;lt;/code&amp;gt;(switching to the download directory on macOS). To list all files in the current directory you can enter &amp;lt;code&amp;gt;ls -la&amp;lt;/code&amp;gt; in your console. &lt;br /&gt;
&lt;br /&gt;
 gpg: assuming signed data in 'Bisq-1.6.4.dmg'&lt;br /&gt;
 gpg: Signature made Thu May  6 13:32:43 2021 EDT&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer &amp;quot;christoph.atteneder@gmail.com&amp;quot;&lt;br /&gt;
 gpg: Can't check signature: No public key&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, you have not imported the public key successfully. Please follow the guide above on how to import the public key for verification.&lt;br /&gt;
&lt;br /&gt;
'''Successful verification'''&lt;br /&gt;
&lt;br /&gt;
You should see output that looks something like:&lt;br /&gt;
&lt;br /&gt;
 gpg: Signature made Thu 13 Feb 2020 01:38:03 PM EST&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer ...&lt;br /&gt;
 gpg: Good signature from &amp;quot;Christoph Atteneder ...&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Great, this means the installer file we downloaded is intact and as intended.&lt;br /&gt;
&lt;br /&gt;
'''Verify jar file after installation'''&lt;br /&gt;
&lt;br /&gt;
As one last check, you can verify the hash of the jar file after installing Bisq.&lt;br /&gt;
&lt;br /&gt;
On macOS, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
 /Applications/Bisq.app/Contents/Java/&lt;br /&gt;
&lt;br /&gt;
On Linux, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
 /opt/bisq/bin/Bisq&lt;br /&gt;
&lt;br /&gt;
or also&lt;br /&gt;
&lt;br /&gt;
 /opt/bisq/lib/app/&lt;br /&gt;
&lt;br /&gt;
If you cannot find the jar file in the locations above in Linux, you can try finding it by running&lt;br /&gt;
&lt;br /&gt;
 find / -name &amp;quot;desktop*.jar&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Get the hash of the jar file with:&lt;br /&gt;
&lt;br /&gt;
 shasum -a256 /path/to/jar/file/jar-name.jar&lt;br /&gt;
&lt;br /&gt;
The hash you get should match the hash in the &amp;lt;code&amp;gt;.jar.txt&amp;lt;/code&amp;gt; file in the [https://github.com/bisq-network/bisq/releases/latest release assets].&lt;br /&gt;
&lt;br /&gt;
== Build from source ==&lt;br /&gt;
&lt;br /&gt;
[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine. &lt;br /&gt;
&lt;br /&gt;
Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]&lt;br /&gt;
&lt;br /&gt;
== OS-specific install notes ==&lt;br /&gt;
&lt;br /&gt;
=== Linux (General) ===&lt;br /&gt;
&lt;br /&gt;
Bisq works with a number of Linux distros, but not all desktop environments are supported. &lt;br /&gt;
&lt;br /&gt;
These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.&lt;br /&gt;
&lt;br /&gt;
* GNOME&lt;br /&gt;
* Mate&lt;br /&gt;
* Xfce&lt;br /&gt;
* KDE Plasma&lt;br /&gt;
* Cinnamon&lt;br /&gt;
&lt;br /&gt;
Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.&lt;br /&gt;
&lt;br /&gt;
Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.&lt;br /&gt;
&lt;br /&gt;
=== Arch Linux ===&lt;br /&gt;
&lt;br /&gt;
The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].&lt;br /&gt;
&lt;br /&gt;
# From the command line, clone the repository from AUR. &lt;br /&gt;
# Then from the cloned directory, run &amp;lt;code&amp;gt;makepkg -si&amp;lt;/code&amp;gt;. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.&lt;br /&gt;
&lt;br /&gt;
If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].&lt;br /&gt;
&lt;br /&gt;
Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.&lt;br /&gt;
&lt;br /&gt;
=== Gentoo ===&lt;br /&gt;
&lt;br /&gt;
Use &amp;lt;code&amp;gt;eselect repository enable booboo&amp;lt;/code&amp;gt; to use the 'booboo' overlay which carries the binaries, and then emerge &amp;lt;code&amp;gt;bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tails ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.&lt;br /&gt;
&lt;br /&gt;
=== Qubes ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.&lt;br /&gt;
&lt;br /&gt;
== Update Bisq ==&lt;br /&gt;
&lt;br /&gt;
Installing a new Bisq version will update Bisq. More details at [[Updating Bisq]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Use Cases]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Bisq_Price_Indices&amp;diff=2962</id>
		<title>Bisq Price Indices</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Bisq_Price_Indices&amp;diff=2962"/>
		<updated>2022-03-21T07:10:11Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Altcoins: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''Bisq Price Indices''' are the weighted average asset prices calculated by each of the [[Bisq pricenode |Bisq Pricenodes]].  It was implemented in Bisq v1.3.8 as part of [https://github.com/bisq-network/projects/issues/35 Project 35] in order to gain independence from Bitcoin Average as a price oracle, decentralizing data sources from 35+ different data providers around the world.&lt;br /&gt;
&lt;br /&gt;
Bisq Pricenodes fetch the latest price data, once per minute, from various providers for each asset. The price indices are equally weighted, so for example if there's a single provider for a given asset, the weight will be 100%. If there's 2 data providers for an asset, the weights will 50% each, if there are 4, 25% each, etc.&lt;br /&gt;
&lt;br /&gt;
Providers are selected considering for each asset reliability of the data and trading volume. The following tables display which data providers are used to calculate prices for each actively traded asset on Bisq.&lt;br /&gt;
&lt;br /&gt;
In the case of nodes diverging more than 1% for a given asset, the prices will be outside the price tolerance protection, and Bisq will display an error to user preventing them from taking an offer.&lt;br /&gt;
&lt;br /&gt;
= Asset Table =&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bitpay || Coingecko || Binance || Coinpaprika || Kraken || Quoine || BTCmarkets || Independent&amp;lt;/BR&amp;gt;Reserve || Mercado&amp;lt;/BR&amp;gt;Bitcoin&lt;br /&gt;
|-&lt;br /&gt;
| '''AED''' || 50% || 50% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-  style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''AFN''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''ALL''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''AMD''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''ANG''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''AOA''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''ARS''' || 33% || 33% ||  || 33% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''AUD''' || 14% || 14% ||  || 14% || 14% || 14% || 14% || 14% || &lt;br /&gt;
|-&lt;br /&gt;
| '''AWG''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''AZN''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BAM''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BBD''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BDT''' || 50% || 50% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BGN''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BHD''' || 50% || 50% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BIF''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BMD''' || 50% || 50% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BND''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BOB''' || 50% ||  ||  || 50% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BRL''' || 25% || 25% ||  || 25% ||  ||  ||  ||  || 25%&lt;br /&gt;
|-&lt;br /&gt;
| '''BSD''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BTN''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BWP''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''BYN''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''BZD''' || 100% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''CAD''' || 25% || 25% ||  || 25% || 25% ||  ||  ||  || &lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- table 2 --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bittpay || Coingecko || Binance || Coinpaprika || Kraken || Bitstamp || Exmo || Bitfinex || Quoine || Coinmate || Bitbay&lt;br /&gt;
|-&lt;br /&gt;
| '''CDF''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''CHF''' || 25% || 25% ||  || 25% || 25% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''CLP''' || 33% || 33% ||  ||  || 33% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''CNY''' || 33% || 33% ||  || 33% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''COP''' || 50% || 50% ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''CRC''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''CUP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''CVE''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''CZK''' || 25% || 25% ||  || 25% ||  ||  ||  ||  ||  || 25% || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''DJF''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''DKK''' || 33% || 33% ||  || 33% ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''DOP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''DZD''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''EGP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''ETB''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''EUR''' || 9% || 9% || 9% || 9% || 9% || 9% || 9% || 9% || 9% || 9% || 9%&lt;br /&gt;
|-&lt;br /&gt;
| '''FJD''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''FKP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''GBP''' || 12% || 12% || 12% || 12% || 12% || 12% ||  || 12% ||  ||  || 12%&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''GEL''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''GHS''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''GIP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''GMD''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''GNF''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''GTQ''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bitpay || Coingecko || Coinpaprika || Bitfinex || Quoine || Bitflyer || Coinone&lt;br /&gt;
|-&lt;br /&gt;
| '''GYD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''HKD''' || 25% || 25% || 25% ||  || 25% ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''HNL''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''HRK''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''HTG''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''HUF''' || 33% || 33% || 33% ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''IDR''' || 25% || 25% || 25% ||  || 25% ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''ILS''' || 33% || 33% || 33% ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''INR''' || 33% || 33% || 33% ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''IQD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''IRR''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''ISK''' || 50% ||  || 50% ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''JMD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''JOD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''JPY''' || 14% || 14% || 14% || 14% || 14% || 14% || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''KES''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''KGS''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''KHR''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''KMF''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''KPW''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''KRW''' || 25% || 25% || 25% ||  ||  ||  || 25%&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''KWD''' || 50% || 50% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''KYD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''KZT''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''LAK''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- table 4--&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bitpay || Cingecko || Binance || Coinpaprika || Independent&amp;lt;/br&amp;gt;Reserve || Luno&lt;br /&gt;
|-&lt;br /&gt;
| '''LBP''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''LKR''' || 50% || 50% ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''LRD''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''LSL''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''LYD''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MAD''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MDL''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MGA''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MKD''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MMK''' || 50% || 50% ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MNT''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MOP''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MRU''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MUR''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MVR''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MWK''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''MXN''' || 33% || 33% ||  || 33% ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''MYR''' || 25% || 25% ||  || 25% ||  || 25%&lt;br /&gt;
|-&lt;br /&gt;
| '''MZN''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''NAD''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''NGN''' || 25% || 25% ||  || 25% ||  || 25%&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''NIO''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''NOK''' || 33% || 33% ||  || 33% ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''NPR''' || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''NZD''' || 25% || 25% ||  || 25% || 25% || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bitpay || Coingecko || Binance || Coinpaprika || Exmo || Quoine || Bitbay&lt;br /&gt;
|-&lt;br /&gt;
| '''OMR''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''PAB''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''PEN''' || 50% ||  ||  || 50% ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''PGK''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''PHP''' || 33% || 33% ||  || 33% ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''PKR''' || 33% || 33% ||  || 33% ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''PLN''' || 20% || 20% ||  || 20% || 20% ||  || 20%&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''PYG''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''QAR''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''RON''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''RSD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''RUB''' || 25% || 25% || 25 || 25% || 25% ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''RWF''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SAR''' || 50% || 50% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SBD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SCR''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SDG''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SEK''' || 33% || 33% ||  || 33% ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SGD''' || 25% || 25% ||  || 25% ||  || 25% || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SHP''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SLL''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SOS''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SRD''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''STN''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''SVC''' || 100% ||  ||  ||  ||  ||  || &lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- table 6 --&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Currency || Bitpay || Coingecko || Binance || Coinpaprika || Kraken || Bitstamp || Exmo || Bitfinex || Independent&amp;lt;/br&amp;gt;Reserve || Bitbay || Luno || Paribu || Hit&lt;br /&gt;
|-&lt;br /&gt;
| '''SYP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''SZL''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''THB''' || 33% || 33% ||  || 33% ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''TJS''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''TMT''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''TND''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''TOP''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''TRY''' || 20% || 2% || 20% || 20% ||  ||  ||  ||  ||  ||  ||  || 20% || &lt;br /&gt;
|-&lt;br /&gt;
| TTD || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''TWD''' || 33% || 33% ||  || 33% ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''TZS''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''UAH''' || 20% || 20% || 20% || 20% ||  ||  || 20% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''UGX''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''USD''' || 10% || 10% ||  || 10% || 10% || 10% || 10% || 10% || 10% || 10% ||  ||  || 10%&lt;br /&gt;
|-&lt;br /&gt;
| '''UYU''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''UZS''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''VES''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''VND''' || 33% || 33% ||  || 33% ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''VUV''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''WST''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| XAF || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''XCD''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''XOF''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''XPF''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''YER''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''ZAR''' || 20% || 20% || 20% || 20% ||  ||  ||  ||  ||  ||  || 20% ||  || &lt;br /&gt;
|-&lt;br /&gt;
| '''ZMW''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| '''ZWL''' || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Altcoins: ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;small&amp;gt;A:Binance B:Huobi C:Kraken D:Poloniex E:Exmo F:Bitstamp G:Bitfinex H:Bitpay I:BTCmarkets J:Coingecko K:Bitbay LːBitflyer M:Quobi&amp;lt;/small&amp;gt;&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|  || A || B || C || D || E || F || G || H || I || J || K || L || M&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| BEAM || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| BTM ||  || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| DAI || 50% ||  ||  ||  ||  ||  || 50% ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| DASH || 14% || 14% || 14% || 14% || 14% ||  ||  || 14% || 14% ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| DCR || 33% || 33% ||  || 33 ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| DOGE || 20 % || 20 % || 20 % || 20 % || 20 % ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| ETC ||  ||  || 20% || 20% || 20% || 20% ||  || 20% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| ETH || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7% || 7%&lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| FAIR ||  || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| LTC || 10% || 10% || 10% || 10% || 10% || 10% || 10% ||  || 10% || 10% || 10% ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| NAV || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| PIVX || 100% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| USDC ||  ||  ||  ||  ||  ||  ||  || 100% ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| XMR || 16% || 16% || 16% || 16% || 16% ||  || 16% ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| XZC || 50% || 50% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
| ZEC || 20% || 20% || 20% || 20% || 20% ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|- style=&amp;quot;background-color: #ECECF0&amp;quot;&lt;br /&gt;
| ZEN || 50% || 50% ||  ||  ||  ||  ||  ||  ||  ||  ||  ||  || &lt;br /&gt;
|-&lt;br /&gt;
|  || A || B || C || D || E || F || G || H || I || J || K || L || M&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;small&amp;gt;A:Binance B:Huobi C:Kraken D:Poloniex E:Exmo F:Bitstamp G:Bitfinex H:Bitpay I:BTCmarkets J:Coingecko K:Bitbay LːBitflyer M:Quobi&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=2961</id>
		<title>Running Bisq on Tails</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Running_Bisq_on_Tails&amp;diff=2961"/>
		<updated>2022-03-19T19:33:52Z</updated>

		<summary type="html">&lt;p&gt;W000000t: add persistent storage instructions by https://github.com/amosgroth&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To '''run Bisq on the Tails OS''', a few manual steps are required.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Preparations ==&lt;br /&gt;
&lt;br /&gt;
* Configure a [https://tails.boum.org/doc/first_steps/welcome_screen/administration_password/ administration password] when installing Bisq&lt;br /&gt;
* Configure persistence [https://tails.boum.org/doc/first_steps/persistence/index.en.html]&lt;br /&gt;
* Configure dotfiles [https://tails.boum.org/doc/first_steps/persistence/index.en.html#index13h2]&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Warn|Tails does not persist data by default, so while following these directions will allow you to run Bisq on Tails, '''all data will be erased as soon as you reboot'''. This means you will lose your Bisq keys, wallet data, and everything else in the [[data directory]]. &lt;br /&gt;
&lt;br /&gt;
Make sure to set up persistent storage and dotfiles to have your Bisq data persisted across sessions.}}&lt;br /&gt;
&lt;br /&gt;
== Install ==&lt;br /&gt;
&lt;br /&gt;
After restarting Tails, go to https://github.com/bisq-network/bisq/releases using your Tor Browser and download the &amp;lt;code&amp;gt;Bisq-64bit-[version].deb&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; files.&lt;br /&gt;
&lt;br /&gt;
You may have to use &amp;lt;code&amp;gt;wget&amp;lt;/code&amp;gt;, because &amp;lt;code&amp;gt;curl&amp;lt;/code&amp;gt; may not use Tor and could be blocked from using the internet.&lt;br /&gt;
&lt;br /&gt;
=== Verify your download ===&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;wget &amp;lt;nowiki&amp;gt;https://bisq.network/pubkey/[keyid].asc&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; should result in a file &amp;lt;code&amp;gt;[keyid].asc&amp;lt;/code&amp;gt; in your working directory. See &amp;quot;Verification&amp;quot; section of [https://github.com/bisq-network/bisq/releases/latest release notes] for the exact key ID you should use (it's &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; as of this writing) to verify your download.&lt;br /&gt;
* Import the key to gpg by &amp;lt;code&amp;gt;gpg --import [keyid].asc&amp;lt;/code&amp;gt;&lt;br /&gt;
* Check the signature with &amp;lt;code&amp;gt;gpg --digest-algo SHA256 --verify [yourbinaryhere]{.asc*,}&amp;lt;/code&amp;gt; which should give you something like this&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
[snip]&lt;br /&gt;
gpg: Good signature from &amp;quot;Christoph Atteneder...&lt;br /&gt;
[snip]&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Install Bisq ===&lt;br /&gt;
&lt;br /&gt;
Do a simple &amp;lt;code&amp;gt;sudo dpkg -i [yourbinaryhere]&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
== Configure ==&lt;br /&gt;
&lt;br /&gt;
* Make authcookie readable:&lt;br /&gt;
&amp;lt;pre&amp;gt;sudo chmod o+r /var/run/tor/control.authcookie&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Configure &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Create a file &amp;lt;code&amp;gt;/etc/onion-grater.d/bisq.yml&amp;lt;/code&amp;gt; with contents:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then restart the &amp;lt;code&amp;gt;onion-grater&amp;lt;/code&amp;gt; service with &amp;lt;code&amp;gt;service onion-grater restart&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
* In &amp;lt;code&amp;gt;/usr/share/applications/bisq-Bisq.desktop&amp;lt;/code&amp;gt;, replace:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;Exec=/opt/bisq/bin/Bisq&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
with:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Run Bisq ==&lt;br /&gt;
&lt;br /&gt;
Click &amp;lt;code&amp;gt;Applications&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Other&amp;lt;/code&amp;gt; &amp;gt; &amp;lt;code&amp;gt;Bisq&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Or via terminal:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Persistent Data Directory ==&lt;br /&gt;
&lt;br /&gt;
Either you want a fresh install or you had Bisq installed somewhere else and would like to keep your Bisq user identity and data. In both cases, you need to make sure that the Bisq [[data directory]] doesn't get lost after restarting Tails.&lt;br /&gt;
&lt;br /&gt;
After the first start, Bisq has automatically created its [[data directory]] in the &amp;lt;code&amp;gt;~/.local/share/Bisq&amp;lt;/code&amp;gt; directory and from there it gets deleted after a Tails restart.&lt;br /&gt;
&lt;br /&gt;
=== New User ===&lt;br /&gt;
&lt;br /&gt;
* Quit Bisq after the first start, once synchronisation and setup are completed&lt;br /&gt;
* Move the [[data directory]] to the dotfiles [https://tails.boum.org/doc/first_steps/persistence/index.en.html#index13h2]&lt;br /&gt;
&amp;lt;code&amp;gt;mv ~/.local/share/Bisq/* /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
* Restart Tails&lt;br /&gt;
&lt;br /&gt;
=== Existing User ===&lt;br /&gt;
&lt;br /&gt;
* Copy your backup of the Bisq [[data directory]] to the dotfiles [https://tails.boum.org/doc/first_steps/persistence/index.en.html#index13h2]&lt;br /&gt;
&amp;lt;code&amp;gt;cp -r /[yourdirectoryhere]/Bisq /live/persistence/TailsData_unlocked/dotfiles/.local/share/Bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
* Restart Tails&lt;br /&gt;
&lt;br /&gt;
== Installation Script ==&lt;br /&gt;
&lt;br /&gt;
Because Tails doesn't persist the Bisq for the next session, you have to repeat the installation [https://bisq.wiki/Running_Bisq_on_Tails#Install_Bisq] and configuration [https://bisq.wiki/Running_Bisq_on_Tails#Configure] after every restart. To make life easier, you can automate this in a bash script. Make sure this script is saved somewhere in the Tails persistent directory.&lt;br /&gt;
&lt;br /&gt;
* Create script file:&lt;br /&gt;
&amp;lt;code&amp;gt;touch ~/Persistent/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Make script executable:&lt;br /&gt;
&amp;lt;code&amp;gt;chmod +x ~/Persistent/install-bisq.sh&amp;lt;/code&amp;gt;&lt;br /&gt;
* Edit and save file: &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/bash&lt;br /&gt;
&lt;br /&gt;
dpkg -i [yourbinaryhere]&lt;br /&gt;
echo &amp;quot;Change access rights of /var/run/tor/control.authcookie ...&amp;quot;&lt;br /&gt;
chmod o+r /var/run/tor/control.authcookie&lt;br /&gt;
echo &amp;quot;Create /etc/onion-grater.d/bisq.yml ...&amp;quot;&lt;br /&gt;
echo &amp;quot;---&lt;br /&gt;
- apparmor-profiles:&lt;br /&gt;
    - '/opt/bisq/bin/Bisq'&lt;br /&gt;
  users:&lt;br /&gt;
    - 'amnesia'&lt;br /&gt;
  commands:&lt;br /&gt;
    AUTHCHALLENGE:&lt;br /&gt;
      - 'SAFECOOKIE .*'&lt;br /&gt;
    SETEVENTS:&lt;br /&gt;
      - 'CIRC WARN ERR'&lt;br /&gt;
      - 'CIRC ORCONN INFO NOTICE WARN ERR HS_DESC HS_DESC_CONTENT'&lt;br /&gt;
    GETINFO:&lt;br /&gt;
      - 'net/listeners/socks'&lt;br /&gt;
    ADD_ONION:&lt;br /&gt;
      - pattern:     'NEW:(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: 'NEW:{} Port=9999,{client-address}:{}'&lt;br /&gt;
      - pattern:     '(\S+):(\S+) Port=9999,(\S+)'&lt;br /&gt;
        replacement: '{}:{} Port=9999,{client-address}:{}'&lt;br /&gt;
    DEL_ONION:&lt;br /&gt;
      - '.+'&lt;br /&gt;
    HSFETCH:&lt;br /&gt;
      - '.+'&lt;br /&gt;
  events:&lt;br /&gt;
    CIRC:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ORCONN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    INFO:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    NOTICE:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    WARN:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    ERR:&lt;br /&gt;
      suppress: true&lt;br /&gt;
    HS_DESC:&lt;br /&gt;
      response:&lt;br /&gt;
        - pattern:     '650 HS_DESC CREATED (\S+) (\S+) (\S+) \S+ (.+)'&lt;br /&gt;
          replacement: '650 HS_DESC CREATED {} {} {} redacted {}'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOAD (\S+) (\S+) .*'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOAD {} {} redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC UPLOADED (\S+) (\S+) .+'&lt;br /&gt;
          replacement: '650 HS_DESC UPLOADED {} {} redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH'&lt;br /&gt;
        - pattern:     '650 HS_DESC REQUESTED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC REQUESTED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '650 HS_DESC RECEIVED (\S+) NO_AUTH \S+ \S+'&lt;br /&gt;
          replacement: '650 HS_DESC RECEIVED {} NO_AUTH redacted redacted'&lt;br /&gt;
        - pattern:     '.*'&lt;br /&gt;
          replacement: ''&lt;br /&gt;
    HS_DESC_CONTENT:&lt;br /&gt;
      suppress: true&amp;quot; &amp;gt; /etc/onion-grater.d/bisq.yml&lt;br /&gt;
echo &amp;quot;Restart onion-grater service ...&amp;quot;&lt;br /&gt;
service onion-grater restart&lt;br /&gt;
echo &amp;quot;Edit Bisq executable file ...&amp;quot;&lt;br /&gt;
sed -i 's+Exec=/opt/bisq/bin/Bisq+Exec=/opt/bisq/bin/Bisq --torControlPort 9051 --torControlCookieFile=/var/run/tor/control.authcookie --torControlUseSafeCookieAuth+' /usr/share/applications/bisq-Bisq.desktop&lt;br /&gt;
echo &amp;quot;Bisq installed successfully.&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now you might run this script everytime you want to install and run Bisq after a Tails restart:&lt;br /&gt;
&amp;lt;code&amp;gt;sudo ./install-bisq.sh&amp;lt;?code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Guides]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=How_do_I_send_fiat_to_Bisq&amp;diff=2948</id>
		<title>How do I send fiat to Bisq</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=How_do_I_send_fiat_to_Bisq&amp;diff=2948"/>
		<updated>2022-03-11T17:26:08Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* You don't. */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== So, how do I send fiat to Bisq, or how do I use my credit card to buy bitcoin? ==&lt;br /&gt;
= You don't. =&lt;br /&gt;
&lt;br /&gt;
This guide was made as an attempt to garner attention from such query terms that regularly appear on some of our support venues.&lt;br /&gt;
&lt;br /&gt;
Bisq is a DEX (decentralized exchange), it doesn't directly deal with fiat, so it doesn't have builtin fiat accounts, nor credit card payment endpoints; it only manages a BTC wallet (and a special [[BSQ]] wallet).&lt;br /&gt;
&lt;br /&gt;
To trade, you need to find another user who agrees with you (selling BTC while you want to buy, or buying BTC while you want to sell, using same currency and same [[Payment_methods|payment method]]); Bisq will manage the Bitcoin side of the transaction with its battle-tested escrow, and trading peers will manage the fiat/altcoin side on their end, by dealing directly between themselves.&lt;br /&gt;
&lt;br /&gt;
=== There might be a way to buy BTC with credit card on Bisq though ===&lt;br /&gt;
&lt;br /&gt;
Technically, you could say you can buy BTC with your credit card on Bisq, even if that's a little more convoluted than what you normally see on e-commerce websites: you would need to setup a payment method that supports receiving deposits from cards, like [[Revolut]], [[TransferWise|Wise]] (ex TransferWise), [[Amazon_eGift_card|Amazon eGift card]] to say a few, send money from your credit card to those accounts, and then make, or take, an offer that uses one of those methods.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=How_do_I_send_fiat_to_Bisq&amp;diff=2946</id>
		<title>How do I send fiat to Bisq</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=How_do_I_send_fiat_to_Bisq&amp;diff=2946"/>
		<updated>2022-03-11T09:57:23Z</updated>

		<summary type="html">&lt;p&gt;W000000t: Created page with &amp;quot;== So, how do I send fiat to Bisq, or how do I use my credit card to buy bitcoin? == = You don't. =  This guide was made as an attempt to garner attention from such questions...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== So, how do I send fiat to Bisq, or how do I use my credit card to buy bitcoin? ==&lt;br /&gt;
= You don't. =&lt;br /&gt;
&lt;br /&gt;
This guide was made as an attempt to garner attention from such questions that get regularly asked on some of our support venues.&lt;br /&gt;
&lt;br /&gt;
Bisq is a DEX (decentralized exchange), it doesn't directly deal with fiat, so it doesn't have builtin fiat accounts, nor credit card payment endpoints; it only manages a BTC wallet (and a special [[BSQ]] wallet).&lt;br /&gt;
&lt;br /&gt;
To trade, you need to find another user who agrees with you (selling BTC while you want to buy, or buying BTC while you want to sell, using same currency and same [[Payment_methods|payment method]]); Bisq will manage the Bitcoin side of the transaction with its battle-tested escrow, and trading peers will manage the fiat/altcoin side on their end, by dealing directly between themselves.&lt;br /&gt;
&lt;br /&gt;
=== There might be a way to buy BTC with credit card on Bisq though ===&lt;br /&gt;
&lt;br /&gt;
Technically, you could say you can buy BTC with your credit card on Bisq, even if that's a little more convoluted than what you normally see on e-commerce websites: you would need to setup a payment method that supports receiving deposits from cards, like [[Revolut]], [[TransferWise|Wise]] (ex TransferWise), [[Amazon_eGift_card|Amazon eGift card]] to say a few, send money from your credit card to those accounts, and then make, or take, an offer that uses one of those methods.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2945</id>
		<title>Downloading and installing</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2945"/>
		<updated>2022-03-08T22:10:19Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Gentoo */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.&lt;br /&gt;
&lt;br /&gt;
Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.&lt;br /&gt;
&lt;br /&gt;
Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.&lt;br /&gt;
&lt;br /&gt;
All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.&lt;br /&gt;
&lt;br /&gt;
== Download Bisq ==&lt;br /&gt;
&lt;br /&gt;
The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].&lt;br /&gt;
&lt;br /&gt;
There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}&lt;br /&gt;
&lt;br /&gt;
You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.&lt;br /&gt;
&lt;br /&gt;
'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''&lt;br /&gt;
&lt;br /&gt;
== Verify installer file ==&lt;br /&gt;
&lt;br /&gt;
Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.&lt;br /&gt;
&lt;br /&gt;
This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.&lt;br /&gt;
&lt;br /&gt;
Bisq installer files are currently built and signed by Christoph Atteneder (ripcurlx). His public key ID is &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; and fingerprint is &amp;lt;code&amp;gt;CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B&amp;lt;/code&amp;gt;, which you can verify through [https://github.com/bisq-network/bisq/commits?author=ripcurlx commits on GitHub] and [https://keybase.io/ripcurlx on Keybase].&lt;br /&gt;
&lt;br /&gt;
The full public key is available [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
=== Obtain signature files for installer files ===&lt;br /&gt;
&lt;br /&gt;
To verify your installer file is intact and as the developer intended, you will need the PGP signature file corresponding to the installer file you downloaded.&lt;br /&gt;
&lt;br /&gt;
On the [https://bisq.network/downloads/ Bisq website's download page], download the PGP signature file for the installer file you downloaded before.&lt;br /&gt;
&lt;br /&gt;
If you prefer to download from GitHub, you will see the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file for your installer in the assets section [https://github.com/bisq-network/bisq/releases/latest of the release] along with the installer file itself.&lt;br /&gt;
&lt;br /&gt;
In either case, the filename for the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; you download should be identical to the filename for the installer file, just with &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; appended (e.g., signature file for &amp;lt;code&amp;gt;Bisq-1.2.7.dmg&amp;lt;/code&amp;gt; would be &amp;lt;code&amp;gt;Bisq-1.2.7.dmg.asc&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
Once you've got the installer file and its corresponding signature file, proceed to the directions for your operating system below.&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
&lt;br /&gt;
Once you have downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Download ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Download ripcurlx's public key [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
'''Download and install Gpg4win'''&lt;br /&gt;
&lt;br /&gt;
Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq's installer files.&lt;br /&gt;
&lt;br /&gt;
You can get Gpg4win [https://www.gpg4win.org/ here].&lt;br /&gt;
&lt;br /&gt;
Double-click the installer file and proceed to install with all default settings.&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
In Kleopatra, import ripcurlx's public key file &amp;lt;code&amp;gt;29CDFD3B.asc&amp;lt;/code&amp;gt;. Select ''No'' if asked to mark the certificate as valid.&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
With the &amp;lt;code&amp;gt;install-file.exe&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;signature-file.exe.asc&amp;lt;/code&amp;gt; in the same directory, double-click on the &amp;lt;code&amp;gt;.exe.asc&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
You should see a Kleopatra window pop up with a green progress bar that says &amp;quot;Verified .exe with .exe.asc&amp;quot;. The program will continue to say &amp;quot;The data could not be verified&amp;quot; in bold but you can disregard that message.&lt;br /&gt;
&lt;br /&gt;
This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the &amp;lt;code&amp;gt;.exe&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
=== macOS and Linux ===&lt;br /&gt;
&lt;br /&gt;
Once you've downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You might see an ominous sounding warning along the lines of &amp;quot;This key is not certified with a trusted signature&amp;quot;. This basically means that none of the public keys on your machine have signed the key you just imported. It also means that you have not explicitly indicated you trust this key yourself. This is not necessarily a bad thing, but please see more about what this means [https://serverfault.com/a/569923 here]. In short, you can verify the integrity of this key by [[ #Verify installer file | cross-referencing ripcurlx's Bisq commit signatures and Keybase profile]].&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with GPG (a free open source version of PGP) you probably need to install GPG command line tools first.&lt;br /&gt;
Following instructions are taken from https://blog.ghostinthemachines.com/2015/03/01/how-to-use-gpg-command-line.&lt;br /&gt;
&lt;br /&gt;
The easiest way to install the GPG command line tools on your Mac is to first install Homebrew, a package management system that makes thousands of software packages available for install on your Mac.&lt;br /&gt;
&lt;br /&gt;
Open a Terminal window (Applications &amp;gt; Utilities menu), then enter the following command.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;ruby -e &amp;quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&amp;quot; &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When that’s complete, install the GPG software package with the following command.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;brew install gnupg &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With the installer file and installer signature file in the same directory, run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;gpg --digest-algo SHA256 --verify SIGNATURE-FILE.asc &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; is the filename of the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file you just downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Common errors'''&lt;br /&gt;
&lt;br /&gt;
 gpg: directory '/Users/bisq/.gnupg' created&lt;br /&gt;
 gpg: keybox '/Users/bisq/.gnupg/pubring.kbx' created&lt;br /&gt;
 gpg: can't open 'SIGNATURE-FILE.asc': No such file or directory&lt;br /&gt;
 gpg: verify signatures failed: No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you haven't replaced &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; with the actual signature file you want to use e.g. &amp;lt;code&amp;gt;Bisq-1.6.4.dmg.asc&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 gpg: can't open 'Bisq-1.6.4.dmg.asc': No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you either haven't downloaded the signature file already or you are not in the correct directory. You can run &amp;lt;code&amp;gt;pwd&amp;lt;/code&amp;gt; to see the path you are in.&lt;br /&gt;
If you want to switch to the directory, where the downloaded files are you can use the [https://www.git-tower.com/learn/git/ebook/en/command-line/appendix/command-line-101/#:~:text=It%20will%20return%20the%20path,%24%20cd%20.. `cd` command] and switch to the correct directory by typing e.g. &amp;lt;code&amp;gt;cd ~/Downloads&amp;lt;/code&amp;gt;(switching to the download directory on macOS). To list all files in the current directory you can enter &amp;lt;code&amp;gt;ls -la&amp;lt;/code&amp;gt; in your console. &lt;br /&gt;
&lt;br /&gt;
 gpg: assuming signed data in 'Bisq-1.6.4.dmg'&lt;br /&gt;
 gpg: Signature made Thu May  6 13:32:43 2021 EDT&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer &amp;quot;christoph.atteneder@gmail.com&amp;quot;&lt;br /&gt;
 gpg: Can't check signature: No public key&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, you have not imported the public key successfully. Please follow the guide above on how to import the public key for verification.&lt;br /&gt;
&lt;br /&gt;
'''Successful verification'''&lt;br /&gt;
&lt;br /&gt;
You should see output that looks something like:&lt;br /&gt;
&lt;br /&gt;
 gpg: Signature made Thu 13 Feb 2020 01:38:03 PM EST&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer ...&lt;br /&gt;
 gpg: Good signature from &amp;quot;Christoph Atteneder ...&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Great, this means the installer file we downloaded is intact and as intended.&lt;br /&gt;
&lt;br /&gt;
'''Verify jar file after installation'''&lt;br /&gt;
&lt;br /&gt;
As one last check, you can verify the hash of the jar file after installing Bisq.&lt;br /&gt;
&lt;br /&gt;
On macOS, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
 /Applications/Bisq.app/Contents/Java/&lt;br /&gt;
&lt;br /&gt;
On Linux, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
/opt/bisq/bin/Bisq&lt;br /&gt;
&lt;br /&gt;
Get the hash of the jar file with:&lt;br /&gt;
&lt;br /&gt;
 shasum -a256 /path/to/jar/file/jar-name.jar&lt;br /&gt;
&lt;br /&gt;
The hash you get should match the hash in the &amp;lt;code&amp;gt;.jar.txt&amp;lt;/code&amp;gt; file in the [https://github.com/bisq-network/bisq/releases/latest release assets].&lt;br /&gt;
&lt;br /&gt;
== Build from source ==&lt;br /&gt;
&lt;br /&gt;
[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine. &lt;br /&gt;
&lt;br /&gt;
Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]&lt;br /&gt;
&lt;br /&gt;
== OS-specific install notes ==&lt;br /&gt;
&lt;br /&gt;
=== Linux (General) ===&lt;br /&gt;
&lt;br /&gt;
Bisq works with a number of Linux distros, but not all desktop environments are supported. &lt;br /&gt;
&lt;br /&gt;
These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.&lt;br /&gt;
&lt;br /&gt;
* GNOME&lt;br /&gt;
* Mate&lt;br /&gt;
* Xfce&lt;br /&gt;
* KDE Plasma&lt;br /&gt;
* Cinnamon&lt;br /&gt;
&lt;br /&gt;
Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.&lt;br /&gt;
&lt;br /&gt;
Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.&lt;br /&gt;
&lt;br /&gt;
=== Arch Linux ===&lt;br /&gt;
&lt;br /&gt;
The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].&lt;br /&gt;
&lt;br /&gt;
# From the command line, clone the repository from AUR. &lt;br /&gt;
# Then from the cloned directory, run &amp;lt;code&amp;gt;makepkg -si&amp;lt;/code&amp;gt;. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.&lt;br /&gt;
&lt;br /&gt;
If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].&lt;br /&gt;
&lt;br /&gt;
Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.&lt;br /&gt;
&lt;br /&gt;
=== Gentoo ===&lt;br /&gt;
&lt;br /&gt;
Use &amp;lt;code&amp;gt;eselect repository enable booboo&amp;lt;/code&amp;gt; to use the 'booboo' overlay which carries the binaries, and then emerge &amp;lt;code&amp;gt;bisq&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Tails ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.&lt;br /&gt;
&lt;br /&gt;
=== Qubes ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Use Cases]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2944</id>
		<title>Downloading and installing</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Downloading_and_installing&amp;diff=2944"/>
		<updated>2022-03-08T22:08:49Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* OS-specific install notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.&lt;br /&gt;
&lt;br /&gt;
Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.&lt;br /&gt;
&lt;br /&gt;
Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.&lt;br /&gt;
&lt;br /&gt;
All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.&lt;br /&gt;
&lt;br /&gt;
== Download Bisq ==&lt;br /&gt;
&lt;br /&gt;
The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].&lt;br /&gt;
&lt;br /&gt;
There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.&lt;br /&gt;
&lt;br /&gt;
{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}&lt;br /&gt;
&lt;br /&gt;
You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.&lt;br /&gt;
&lt;br /&gt;
'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''&lt;br /&gt;
&lt;br /&gt;
== Verify installer file ==&lt;br /&gt;
&lt;br /&gt;
Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.&lt;br /&gt;
&lt;br /&gt;
This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.&lt;br /&gt;
&lt;br /&gt;
Bisq installer files are currently built and signed by Christoph Atteneder (ripcurlx). His public key ID is &amp;lt;code&amp;gt;29CDFD3B&amp;lt;/code&amp;gt; and fingerprint is &amp;lt;code&amp;gt;CB36 D7D2 EBB2 E35D 9B75 500B CD5D C1C5 29CD FD3B&amp;lt;/code&amp;gt;, which you can verify through [https://github.com/bisq-network/bisq/commits?author=ripcurlx commits on GitHub] and [https://keybase.io/ripcurlx on Keybase].&lt;br /&gt;
&lt;br /&gt;
The full public key is available [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
=== Obtain signature files for installer files ===&lt;br /&gt;
&lt;br /&gt;
To verify your installer file is intact and as the developer intended, you will need the PGP signature file corresponding to the installer file you downloaded.&lt;br /&gt;
&lt;br /&gt;
On the [https://bisq.network/downloads/ Bisq website's download page], download the PGP signature file for the installer file you downloaded before.&lt;br /&gt;
&lt;br /&gt;
If you prefer to download from GitHub, you will see the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file for your installer in the assets section [https://github.com/bisq-network/bisq/releases/latest of the release] along with the installer file itself.&lt;br /&gt;
&lt;br /&gt;
In either case, the filename for the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; you download should be identical to the filename for the installer file, just with &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; appended (e.g., signature file for &amp;lt;code&amp;gt;Bisq-1.2.7.dmg&amp;lt;/code&amp;gt; would be &amp;lt;code&amp;gt;Bisq-1.2.7.dmg.asc&amp;lt;/code&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
Once you've got the installer file and its corresponding signature file, proceed to the directions for your operating system below.&lt;br /&gt;
&lt;br /&gt;
=== Windows ===&lt;br /&gt;
&lt;br /&gt;
Once you have downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Download ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Download ripcurlx's public key [https://bisq.network/pubkey/29CDFD3B.asc here on the Bisq website].&lt;br /&gt;
&lt;br /&gt;
'''Download and install Gpg4win'''&lt;br /&gt;
&lt;br /&gt;
Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq's installer files.&lt;br /&gt;
&lt;br /&gt;
You can get Gpg4win [https://www.gpg4win.org/ here].&lt;br /&gt;
&lt;br /&gt;
Double-click the installer file and proceed to install with all default settings.&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
In Kleopatra, import ripcurlx's public key file &amp;lt;code&amp;gt;29CDFD3B.asc&amp;lt;/code&amp;gt;. Select ''No'' if asked to mark the certificate as valid.&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
With the &amp;lt;code&amp;gt;install-file.exe&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;signature-file.exe.asc&amp;lt;/code&amp;gt; in the same directory, double-click on the &amp;lt;code&amp;gt;.exe.asc&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
You should see a Kleopatra window pop up with a green progress bar that says &amp;quot;Verified .exe with .exe.asc&amp;quot;. The program will continue to say &amp;quot;The data could not be verified&amp;quot; in bold but you can disregard that message.&lt;br /&gt;
&lt;br /&gt;
This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the &amp;lt;code&amp;gt;.exe&amp;lt;/code&amp;gt; file.&lt;br /&gt;
&lt;br /&gt;
=== macOS and Linux ===&lt;br /&gt;
&lt;br /&gt;
Once you've downloaded the installer file and corresponding signature file:&lt;br /&gt;
&lt;br /&gt;
'''Import ripcurlx's public key'''&lt;br /&gt;
&lt;br /&gt;
Run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You might see an ominous sounding warning along the lines of &amp;quot;This key is not certified with a trusted signature&amp;quot;. This basically means that none of the public keys on your machine have signed the key you just imported. It also means that you have not explicitly indicated you trust this key yourself. This is not necessarily a bad thing, but please see more about what this means [https://serverfault.com/a/569923 here]. In short, you can verify the integrity of this key by [[ #Verify installer file | cross-referencing ripcurlx's Bisq commit signatures and Keybase profile]].&lt;br /&gt;
&lt;br /&gt;
'''Verify the signature of the binary you downloaded'''&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with GPG (a free open source version of PGP) you probably need to install GPG command line tools first.&lt;br /&gt;
Following instructions are taken from https://blog.ghostinthemachines.com/2015/03/01/how-to-use-gpg-command-line.&lt;br /&gt;
&lt;br /&gt;
The easiest way to install the GPG command line tools on your Mac is to first install Homebrew, a package management system that makes thousands of software packages available for install on your Mac.&lt;br /&gt;
&lt;br /&gt;
Open a Terminal window (Applications &amp;gt; Utilities menu), then enter the following command.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;ruby -e &amp;quot;$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)&amp;quot; &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When that’s complete, install the GPG software package with the following command.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;brew install gnupg &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
With the installer file and installer signature file in the same directory, run:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;gpg --digest-algo SHA256 --verify SIGNATURE-FILE.asc &amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; is the filename of the &amp;lt;code&amp;gt;.asc&amp;lt;/code&amp;gt; file you just downloaded.&lt;br /&gt;
&lt;br /&gt;
'''Common errors'''&lt;br /&gt;
&lt;br /&gt;
 gpg: directory '/Users/bisq/.gnupg' created&lt;br /&gt;
 gpg: keybox '/Users/bisq/.gnupg/pubring.kbx' created&lt;br /&gt;
 gpg: can't open 'SIGNATURE-FILE.asc': No such file or directory&lt;br /&gt;
 gpg: verify signatures failed: No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you haven't replaced &amp;lt;code&amp;gt;SIGNATURE-FILE.asc&amp;lt;/code&amp;gt; with the actual signature file you want to use e.g. &amp;lt;code&amp;gt;Bisq-1.6.4.dmg.asc&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 gpg: can't open 'Bisq-1.6.4.dmg.asc': No such file or directory&lt;br /&gt;
&lt;br /&gt;
In this case, you either haven't downloaded the signature file already or you are not in the correct directory. You can run &amp;lt;code&amp;gt;pwd&amp;lt;/code&amp;gt; to see the path you are in.&lt;br /&gt;
If you want to switch to the directory, where the downloaded files are you can use the [https://www.git-tower.com/learn/git/ebook/en/command-line/appendix/command-line-101/#:~:text=It%20will%20return%20the%20path,%24%20cd%20.. `cd` command] and switch to the correct directory by typing e.g. &amp;lt;code&amp;gt;cd ~/Downloads&amp;lt;/code&amp;gt;(switching to the download directory on macOS). To list all files in the current directory you can enter &amp;lt;code&amp;gt;ls -la&amp;lt;/code&amp;gt; in your console. &lt;br /&gt;
&lt;br /&gt;
 gpg: assuming signed data in 'Bisq-1.6.4.dmg'&lt;br /&gt;
 gpg: Signature made Thu May  6 13:32:43 2021 EDT&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer &amp;quot;christoph.atteneder@gmail.com&amp;quot;&lt;br /&gt;
 gpg: Can't check signature: No public key&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this case, you have not imported the public key successfully. Please follow the guide above on how to import the public key for verification.&lt;br /&gt;
&lt;br /&gt;
'''Successful verification'''&lt;br /&gt;
&lt;br /&gt;
You should see output that looks something like:&lt;br /&gt;
&lt;br /&gt;
 gpg: Signature made Thu 13 Feb 2020 01:38:03 PM EST&lt;br /&gt;
 gpg:                using RSA key CB36D7D2EBB2E35D9B75500BCD5DC1C529CDFD3B&lt;br /&gt;
 gpg:                issuer ...&lt;br /&gt;
 gpg: Good signature from &amp;quot;Christoph Atteneder ...&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Great, this means the installer file we downloaded is intact and as intended.&lt;br /&gt;
&lt;br /&gt;
'''Verify jar file after installation'''&lt;br /&gt;
&lt;br /&gt;
As one last check, you can verify the hash of the jar file after installing Bisq.&lt;br /&gt;
&lt;br /&gt;
On macOS, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
 /Applications/Bisq.app/Contents/Java/&lt;br /&gt;
&lt;br /&gt;
On Linux, the default location of the jar file is:&lt;br /&gt;
&lt;br /&gt;
/opt/bisq/bin/Bisq&lt;br /&gt;
&lt;br /&gt;
Get the hash of the jar file with:&lt;br /&gt;
&lt;br /&gt;
 shasum -a256 /path/to/jar/file/jar-name.jar&lt;br /&gt;
&lt;br /&gt;
The hash you get should match the hash in the &amp;lt;code&amp;gt;.jar.txt&amp;lt;/code&amp;gt; file in the [https://github.com/bisq-network/bisq/releases/latest release assets].&lt;br /&gt;
&lt;br /&gt;
== Build from source ==&lt;br /&gt;
&lt;br /&gt;
[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine. &lt;br /&gt;
&lt;br /&gt;
Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]&lt;br /&gt;
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]&lt;br /&gt;
&lt;br /&gt;
== OS-specific install notes ==&lt;br /&gt;
&lt;br /&gt;
=== Linux (General) ===&lt;br /&gt;
&lt;br /&gt;
Bisq works with a number of Linux distros, but not all desktop environments are supported. &lt;br /&gt;
&lt;br /&gt;
These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.&lt;br /&gt;
&lt;br /&gt;
* GNOME&lt;br /&gt;
* Mate&lt;br /&gt;
* Xfce&lt;br /&gt;
* KDE Plasma&lt;br /&gt;
* Cinnamon&lt;br /&gt;
&lt;br /&gt;
Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.&lt;br /&gt;
&lt;br /&gt;
Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.&lt;br /&gt;
&lt;br /&gt;
=== Arch Linux ===&lt;br /&gt;
&lt;br /&gt;
The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].&lt;br /&gt;
&lt;br /&gt;
# From the command line, clone the repository from AUR. &lt;br /&gt;
# Then from the cloned directory, run &amp;lt;code&amp;gt;makepkg -si&amp;lt;/code&amp;gt;. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.&lt;br /&gt;
&lt;br /&gt;
If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].&lt;br /&gt;
&lt;br /&gt;
Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.&lt;br /&gt;
&lt;br /&gt;
=== Gentoo ===&lt;br /&gt;
&lt;br /&gt;
Use `eselect repository enable booboo` to use the `booboo` overlay which carries the binaries, and then emerge `bisq`&lt;br /&gt;
&lt;br /&gt;
=== Tails ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.&lt;br /&gt;
&lt;br /&gt;
=== Qubes ===&lt;br /&gt;
&lt;br /&gt;
Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Use Cases]]&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Table_of_penalties&amp;diff=2939</id>
		<title>Table of penalties</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Table_of_penalties&amp;diff=2939"/>
		<updated>2022-03-06T21:19:58Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Penalties */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Penalties ==  &lt;br /&gt;
Bisq has [[Trading_rules|Rules]] in place to make the trading process as safe and convenient as possible for all parties involved, and it is important those rules are followed by users.&lt;br /&gt;
&lt;br /&gt;
Penalties are a percentage of the trade amount, deducted from the offending peer's security deposit and offered as a compensation to the other peer during the [[Dispute_resolution#Level_2:_Mediation|Dispute resolution process]]&lt;br /&gt;
The actual penalty will be '''up to''' the values detailed below, depending on security deposit % and mediator's discretion, ''except'' for 100% penalties, that refer to serious violations and will always imply losing the whole amount (trade + deposit).&lt;br /&gt;
&lt;br /&gt;
Alternatively, if good communication is established, peers can use trader chat to agree on a penalty amount to relay to their mediator.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' BTC Buyer or Seller issues:''' &lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Buyer or Seller &lt;br /&gt;
|-&lt;br /&gt;
| 100% || Fraud attempt: debiting of peer's account, code tampering &lt;br /&gt;
|-&lt;br /&gt;
| 25% || Not responding to a mediator within 48h&lt;br /&gt;
|-&lt;br /&gt;
| 25% || Bitcoin-related payment references (e; BTC, Bisq, Bitcoin...) &lt;br /&gt;
|-&lt;br /&gt;
| 20% || Cancelling a trade &lt;br /&gt;
|-&lt;br /&gt;
| 20% || Requesting that payment be made from/to a different account name, without mediator's acknowledgement&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Requiring personal data: ID, home address, etc. (Bisq should incentivize accounts that do not ask for any more info than necessary) &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' BTC Buyer:''' &lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Buyer&lt;br /&gt;
|-&lt;br /&gt;
| 100% || Payment chargeback&lt;br /&gt;
|-&lt;br /&gt;
| 25% || Paying from an account with different name (as in &amp;quot;different person&amp;quot;, while little variations, where it's clear payment comes for the correct person, are not penalized), seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 20% || Payment is 72+ hours late&lt;br /&gt;
|-&lt;br /&gt;
| 15% || Payment is 48-72 hours late &lt;br /&gt;
|-&lt;br /&gt;
| 15% || Paying from an account with same name but different account number, seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Payment is 24-48 hours late&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Similar, but wrong, payment method (eg. SWIFT instead of SEPA, SEPA instant instead of Wise...)&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Wrong payment amount: buyer has the option to correct the amount within the trade window, seller is allowed to cancel the trade with no penalty&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Using unagreed payment reference. Any unagreed payment reference (also the trade ID) shares the same penalty. &amp;quot;Flowers&amp;quot; could be as bad as &amp;quot;services rendered&amp;quot; depending on every single case&lt;br /&gt;
|-&lt;br /&gt;
| 10% || Late payment because of low fee for altcoin tx; penalty can be reduced during mediation if buyer uses RBF or similar&lt;br /&gt;
|-&lt;br /&gt;
| 5% || Payment is up to 24 hours late&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
''' BTC Seller:'''&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
!  !! Seller&lt;br /&gt;
|-&lt;br /&gt;
| 15% || BTC is released outside of trade window&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
- Release times can't be enforced, because at mediation, the last trader to accept the suggestion is the one who decides when the payout is submitted.&lt;br /&gt;
- Cannot accept SEPA instant is replaced by buyer or seller's penalty &amp;quot;Suggest different payment method - account without mediator's acknowledgement.&amp;quot;. This way, an instant SEPA trade could continue as normal SEPA&lt;br /&gt;
- All reasons to  cancel a trade are merged, because traders will tend to give the reason that penalizes them less&lt;br /&gt;
- I keep the explanation because penalizing a user because their bank asks for info is a controversial matter. I might agree with note 3 but this has been working so far.&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_checklist&amp;diff=2934</id>
		<title>Contributor checklist</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_checklist&amp;diff=2934"/>
		<updated>2022-03-02T22:07:42Z</updated>

		<summary type="html">&lt;p&gt;W000000t: add link to contributor opsec short guide&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;If you're interested in contributing to Bisq, ​welcome! This '''contributor checklist''' will get you plugged in and productive as quickly as possible.&lt;br /&gt;
&lt;br /&gt;
Bisq is free and open source software, but contributing is not just about writing code. A contributor is any individual who works to improve and add value to the Bisq network and its users.&lt;br /&gt;
&lt;br /&gt;
This can mean anything from fixing typos in documentation, to providing support, to testing out new growth strategies, to implementing new Bisq features and everything in between. All such contributions are eligible for [[compensation]] from the Bisq DAO.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
== Basics ==&lt;br /&gt;
&lt;br /&gt;
Suggestions below are in no particular order. Disregard developer-oriented items if you're not looking to contribute code.&lt;br /&gt;
&lt;br /&gt;
# Join the [https://bisq.chat Matrix space].&lt;br /&gt;
# Introduce yourself in the &amp;lt;code&amp;gt;general&amp;lt;/code&amp;gt; room. Say a bit about your skills and interests. This will help others point you in the right direction.&lt;br /&gt;
# Explore the other rooms on Matrix, and join the ones that are of interest to you. For a start, consider joining &amp;lt;code&amp;gt;dev&amp;lt;/code&amp;gt; (if you’re a developer) and &amp;lt;code&amp;gt;growth&amp;lt;/code&amp;gt;.&lt;br /&gt;
# Watch the following repositories on GitHub: [https://github.com/bisq-network/bisq core software], [https://github.com/bisq-network/bisq/discussions discussions], [https://github.com/bisq-network/proposals proposals], [https://github.com/bisq-network/growth growth], [https://github.com/bisq-network/roles roles] and [https://github.com/bisq-network/compensation compensation].&lt;br /&gt;
# Read the [https://github.com/bisq-network/bisq/blob/master/docs/README.md developer docs] to set up a Bisq development environment.&lt;br /&gt;
# Read [https://chris.beams.io/posts/git-commit How to Write a Git Commit Message] and follow its [https://chris.beams.io/posts/git-commit/#7-rules 7 rules] when contributing to Bisq projects.&lt;br /&gt;
# Get set up to [https://help.github.com/articles/signing-commits-using-gpg/ Sign your Git Commits] with GPG. Any commits to any Bisq repository must be signed.&lt;br /&gt;
&lt;br /&gt;
== Learn how we work ==&lt;br /&gt;
&lt;br /&gt;
# Read about [[Project_management|Bisq’s project management process]].&lt;br /&gt;
# Familiarize yourself with [https://ossec-docs.readthedocs.io/en/latest/docs/development/oRFC/orfc-1.html C4: The Collective Code Construction Contract]. It’s a simple set of collaboration rules based on GitHub’s fork+pull request model, and a foundational part of how we work together.&lt;br /&gt;
# For more context on C4 and the principles behind it, read author Pieter Hintjens' short book, [https://www.gitbook.com/?utm_source=legacy&amp;amp;utm_medium=redirect&amp;amp;utm_campaign=close_legacy Social Architecture].&lt;br /&gt;
# To understand the fundamentals of Bisq's mission and motivations, read the introductory wiki articles on [[Introduction|Bisq]] and the [[Introduction_to_the_DAO|Bisq DAO]].&lt;br /&gt;
# To understand Bisq’s commitment to radical transparency and radical honesty, read Part III of [https://www.amazon.com/Principles-Life-Work-Ray-Dalio/dp/1501124021/ Ray Dalio’s Principles].&lt;br /&gt;
# To get inspired about what building software in a non-hierarchical organization can be like (and what it requires of everyone involved), read the [https://steamcdn-a.akamaihd.net/apps/valve/Valve_NewEmployeeHandbook.pdf Valve Employee Handbook].&lt;br /&gt;
# Finally, a few words on [[Contributor_privacy_and_opsec|safeguarding your privacy]]&lt;br /&gt;
&lt;br /&gt;
== Get connected ==&lt;br /&gt;
&lt;br /&gt;
# Browse and subscribe to the [https://www.youtube.com/c/bisq-network Bisq YouTube channel] to catch up on meetings we hold, tutorials we publish, technical sessions, and more.&lt;br /&gt;
# Follow [https://twitter.com/bisq_network @bisq_network] on Twitter, or on any of the other channels listed [https://bisq.network/#community on the bottom of the website]: forum, Telegram, Matrix, Mastodon, etc.&lt;br /&gt;
# Subscribe to the [https://lists.bisq.network/listinfo/bisq-contrib bisq-contrib] mailing list for low-frequency, high-priority contributor communications.&lt;br /&gt;
&lt;br /&gt;
If you decide to proceed and start contributing, you'll want to join Bisq's GitHub organization so you can be assigned to issues:&lt;br /&gt;
&lt;br /&gt;
# Request an invite to the [https://github.com/bisq-network @bisq-network GitHub organization] on Matrix. An admin will get you set up. Doing this makes it possible to add you to the [https://github.com/orgs/bisq-network/teams @bisq-network/contributors] team and to assign you to GitHub issues.&lt;br /&gt;
# After accepting your GitHub invitation, consider changing your [https://github.com/orgs/bisq-network/people membership visibility] from &amp;lt;code&amp;gt;private&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;public&amp;lt;/code&amp;gt;. This helps others know at a glance roughly how many contributors are involved with Bisq.&lt;br /&gt;
&lt;br /&gt;
== Do valuable work and get compensated ==&lt;br /&gt;
&lt;br /&gt;
After browsing GitHub repositories and Matrix discussions, you will start to develop a sense for what's happening, what's needed, and where you can help:&lt;br /&gt;
&lt;br /&gt;
# '''Find a problem somewhere in Bisq-land''' that (a) needs fixing and (b) is a match for your skills and interests. Browse critical bugs, open bounties, follow chats on Matrix and the forums, and ask around about what other contributors think needs fixing. &lt;br /&gt;
# '''Get assigned to an issue''' or have your initiative acknowledged in some other way. While you don’t strictly need anybody’s permission to do anything for Bisq, you’ll want to make sure there's buy-in from other contributors so your work is received well. Otherwise, there are no guarantees that your work will be merged, reviewed, or eligible for compensation.&lt;br /&gt;
# '''Do work to fix that problem'''. Submit your fix for review with a pull request (for code and documentation changes) or with a GitHub issue (for everything else).&lt;br /&gt;
# '''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.&lt;br /&gt;
# '''Incorporate review feedback''' you get until your fix gets merged or is otherwise accepted.&lt;br /&gt;
# '''Repeat''' steps 1–5.&lt;br /&gt;
# [[compensation|Submit a compensation request]] toward the end of the cycle.&lt;br /&gt;
&lt;br /&gt;
{{Admonition Note|As you'll see from browsing the various repositories on GitHub, changes to Bisq are almost always discussed publicly. This helps maintain Bisq's commitment to transparency, invites feedback to improve the quality of contributions, and it helps keep compensation honest. '''Always try to make sure your work is documented somewhere so others can follow its progress and offer feedback.'''}}&lt;br /&gt;
&lt;br /&gt;
Ultimately, please remember that all Bisq contributors participate on a voluntary basis, and the more energy and quality you bring to the table, the more existing contributors will be encouraged to pay you attention.&lt;br /&gt;
&lt;br /&gt;
Regarding development, keep in mind that reviewing other contributors' work can be highly valuable as well (both to the project, and also to yourself as a way to learn how Bisq works). Quality code reviews are eligible for compensation just like any other contribution.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
	<entry>
		<id>https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=2933</id>
		<title>Contributor privacy and opsec</title>
		<link rel="alternate" type="text/html" href="https://bisq.wiki/index.php?title=Contributor_privacy_and_opsec&amp;diff=2933"/>
		<updated>2022-03-02T22:04:46Z</updated>

		<summary type="html">&lt;p&gt;W000000t: /* Preserving your privacy while contributing to Bisq */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;First of all: Bitcoin is good for you and the rest of the world, and dealing with Bitcoin is, in itself, perfectly fine and natural. This means that when you privately trade on Bisq, you are most probably doing nothing wrong, on the contrary you are furthering the ideals Bitcoin was created for, even if someone might try to convince you otherwise.&lt;br /&gt;
&lt;br /&gt;
There are parties though that would rather have Bitcoin either disappear, or be turned into the ultimate mass-control tool (the latter being a very realistic scenario, given the peculiarities of the blockchain and its workings). This might, in turn, lead these parties to act in such a way that Bitcoin itself doesn't prosper, or projects around it disappear completely.&lt;br /&gt;
&lt;br /&gt;
Bisq contributors, as &amp;quot;key&amp;quot; elements for Bisq's well being, might be among the targeted elements for the above reason, and for this, other than for best practices regarding privacy on the internet, it is advisable they act accordingly, first and foremost for their own safety, and then for Bisq's.&lt;br /&gt;
&lt;br /&gt;
This article will not be a duplicate of existing, well written resources about privacy on the internet, like this one: https://github.com/BlockchainCommons/Pseudonymity-Guide&lt;br /&gt;
&lt;br /&gt;
Rather, this will be a short heads up to aspiring contributors, but really, anyone, to follow some simple principles.&lt;br /&gt;
&lt;br /&gt;
* Assume any online service will keep all the information about you that you allow it to obtain (browser/PC information via javascript, OS preferred language, obviously your IP, cookies...) and store them for the long term even after you think you deleted them&lt;br /&gt;
* Assume that anything you do, say, or write, will be used against you, even if it was innocent and apparently inconsequential at the time&lt;br /&gt;
&lt;br /&gt;
An &amp;quot;affordable&amp;quot; way to being able to do and say almost anything you would want to, is to remove the ties between your real ID and your internet ID:&lt;br /&gt;
# Use Tor&lt;br /&gt;
# Create a whole new virtual identity, with emails and usernames that you don't use for other personal things&lt;br /&gt;
# Keep that identity in check with itself, and never mix things you do and say with that, with those you do and say with either your real ID, or other IDs you might have created&lt;br /&gt;
&lt;br /&gt;
These are just the basics: do your own research, privacy is not easy to obtain as everything which is free, is usually at the cost of it; privacy is also inconvenient, as everything which is convenient and free also comes at the cost of your privacy. So start with small steps, learn to develop a routine, and then progressively document yourself, for example on guides like the one linked above.&lt;br /&gt;
&lt;br /&gt;
For starters, avoid linking your real ID, or even an existing alternate ID, with what you do on Bisq, but rather prefer building a whole new identity.&lt;/div&gt;</summary>
		<author><name>W000000t</name></author>
		
	</entry>
</feed>