Bisq Wiki - User contributions [en]

Pricenode Operator

2024-03-11T13:22:37Z

Jmacxx: BitcoinAverage no longer required. Updated comp.

A '''Pricenode Operator''' runs one or more [[pricenode]] instance and keeps them updated.

__TOC__

== Issue ==
https://github.com/bisq-network/roles/issues/14

== Team ==
[https://github.com/orgs/bisq-network/teams/pricenode-operators/members @bisq-network/pricenode-operators]

== Duties ==
* Setup and maintain a suitable hosting environment for the pricenode
* Operate your pricenode using the [https://github.com/bisq-network/bisq/tree/master/pricenode#how-to-deploy-for-production current pricenode documentation]
* Run collectd with the [https://github.com/bisq-network/bisq/tree/master/pricenode#Monitoring current monitoring documentation] from bisq-monitoring operator
* Maintain your Tor onion hostname in the [https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/provider/ProvidersRepository.java#L38 Bisq pricenode provider repository]

== Rights ==
* Claim 130 USD compensation each cycle

== Bonding ==
Required. See https://github.com/bisq-network/bisq/blob/42a037e/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L59

[[Category:Stubs]]
[[Category:Roles]]
[[Category:Operator]]

Manually select seednodes

2023-11-27T15:36:56Z

Jmacxx:

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.

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):
- http://5.189.155.112:8080/

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).

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.

Once you have copied those <code>address.onion:port</code> strings, place them in a command line to start Bisq, appending them as a comma-separated list to the <code>-seednodes=</code> option, like so for example (for Linux):

<code>/opt/bisq/bin/Bisq -seedNodes=address1.onion:8000,address2.onion:8000,address3.onion:8000</code>

Press Enter, cross your fingers, and watch the magic happen (maybe), otherwise go back to square one and retry with different seednodes.

Amazon eGift card

2023-11-10T03:18:21Z

Jmacxx: /* Step 2. Customize eGift card */

'''Amazon eGift Cards''' are one of the more private payment methods on Bisq. They tend to be quick and convenient, but funds must be spent on Amazon.

{| class="wikitable"
|-
| '''Chargeback risk''' || Low
|-
| '''Privacy protection''' || Very high
|-
| '''Trade period''' || 24 hours (payment is immediate, as fast as an email)
|-
| '''Regions''' || Countries listed below
|-
| '''Amazon fees''' || No fees
|-
| '''Verifiability''' || High
|-
| '''Fraud risk''' || Low
|-
| '''Number of worldwide Amazon users''' || ~300 million
|}

__TOC__

== Disambiguation ==

Amazon eGift cards are bought on the Amazon website using your account, and sent electronically to the recipient, '''not''' the paper vouchers that contain a visible code, and that you can buy at shops for cash. We understand the latter are more private because there is no name attached to the payment, but they also come with risks, namely:
* no payment proof: the seller can claim the code was already spent on receipt, and neither the buyer nor the mediator have any means to ascertain either way
* illicit origin: code vouchers could be obtained through scams, and the recipient account could get the balance erased as a result, and his Amazon account banned
For these reasons, Bisq only allows for eGift cards.

== Regional Availability ==

Amazon eGift Cards are available in the following regions:

{| class="wikitable"
|-
! Country !! Currency !! Website
|-
| Australia || AUS || https://www.amazon.com.au
|-
| Canada || CAD || https://www.amazon.ca
|-
| Europe || EUR || Multiple websites (.fr, .de, etc)
|-
| United Kingdom || GBP || https://www.amazon.co.uk
|-
| India || INR || https://www.amazon.in
|-
| Japan || JPY || https://www.amazon.co.jp
|-
| Saudi Arabia || SAR || https://www.amazon.sa
|-
| Sweden || SEK || https://www.amazon.se
|-
| Singapore || SGD || https://www.amazon.sg
|-
| Turkey || TRY || https://www.amazon.com.tr
|-
| United States || USD|| https://www.amazon.com
|}

== Adding as Payment Account in Bisq ==

To add Amazon eGift Cards as a payment method in Bisq, go to <code>Account</code> > <code>National Currency Accounts</code> > <code>Add New Account</code>, and then select 'Amazon eGift Card' in the drop-down.

{{Admonition_Note | You can trade across currencies by creating Amazon eGift Card payment accounts in Bisq for each currency you wish to trade in, and then purchasing gift cards from the website corresponding to the region for that currency to settle trades.

'''Amazon eGift Cards can only be redeemed on the website they were purchased from.''' For example, to redeem a gift card on Amazon.jp, it must have been purchased on Amazon.jp. See more details on [https://www.amazon.com/Amazon-1_US_Email-eGift-Card/dp/B004LLIKVU Amazon's product page].}}

You can fill in an email address or a phone number:

# Which one you pick (email address or phone number) only affects how the bitcoin seller will receive the eGift Card (i.e., via email or text message)
# The phone number or email address provided here does not need to be linked to your Amazon account. Once the bitcoin seller has received the eGift Card, they can add it to any Amazon account.

[[File:Amazon eGift Card - Adding to Bisq.png|800px|thumb|left|Creating an Amazon eGift card payment account in Bisq.]]

<br clear=all>

== Buying bitcoin with an Amazon eGift Card ==

=== Step 1. Log in to Amazon ===

First, log in to the Amazon website you'll be buying the eGift card on. '''If trading a currency used on multiple Amazon sites (e.g. EUR currency has amazon.de, amazon.it, amazon.es, etc), please confirm with your peer (through trader chat) which site should be used to purchase the gift card.''' You should be able to use your existing Amazon account to log in to any Amazon site (e.g. you can sign in to amazon.de using an account created on amazon.com).

=== Step 2. Customize eGift card ===

It's recommended to customize the eGift Card to reduce the chances the gift card is seen as suspicious. Feel free to customize the card design, message, etc. Just remember not to include anything about Bisq or bitcoin anywhere.

* '''Amount''': Choose the amount of fiat to send that matches your trade amount. It is recommended to do multiple gift cards of 100 USD or less, as Amazon can consider gift cards of higher amounts to be fraudulent.
* '''Delivery''': Email address or phone number of the seller
* '''To''': eGift recipient information as prompted in the Bisq trade.
* '''Message''': This should be left blank. If you would like to use anything other than a blank message make sure to use trader chat to confirm it with your trading peer. If not a message has been confirmed please leave blank.'''

[[File:Amazon.png|800px|thumb|left|Customize your gift card.]]

<br clear=all>

=== Step 3. Make Payment ===

After your card is ready go, you just have to pay for it! Amazon accepts debit and credit cards, but you cannot pay for an eGift card with another eGift card (or any other Amazon credit balance).

Note: your payment details will NOT be shared with the Seller. The only information they will see is the information you entered to customize the gift card in step 2.

After paying, you'll receive an email receipt from Amazon—make sure you keep this email in case of any issues!

Then make sure you mark your payment as sent in Bisq.

=== Step 4. Seller Gets Notification ===

Once the buyer sends the gift card, the seller will receive an email or SMS message letting them know about their gift card.

{{Admonition_Note|If the seller didn't receive a notification, you can have Amazon send another notification (email or SMS) from the Recent Orders section on Amazon.}}

Upon checking the payment (making sure it's the right amount etc), the seller must confirm the payment in Bisq to complete the trade.

Optionally, the seller can also acknowledge the gift card through Amazon, which would send the buyer an email letting them know the seller has received their gift card.

== See also ==
* [[Payment methods]]

[[Category:Features]]

Cash by mail

2022-09-12T13:20:43Z

Jmacxx: /* Sending cash in the mail */

'''Cash by mail''' (CBM) is one of the most private payment methods on Bisq.

This payment method has special requirements you should be aware of, so please read this article carefully before doing any cash by mail trades.

__TOC__

= Setting up a CBM account in Bisq =

When setting up cash-by-mail payment account in Bisq, you will be asked to enter the following information:

* Name or nym the package should be addressed to
* Postal address
* Currency
* Additional information

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.

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.

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.'''

{{Admonition_Note|Consider setting up separate cash-by-mail accounts for buying and selling so you can specify special instructions for each.}}

= Making a CBM offer =

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.

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.

= Taking a CBM offer =

'''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.

= Sending cash in the mail =

Please see the Bisq trade protocol for [[Trading_rules|general trading rules]].

In addition, buyers should:

* 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).
* Place tamper-evident cash bag inside another package.
* Address the package to the name and address in the seller's cash-by-mail payment account.
* Put a return address in case the package cannot be delivered.
* Use inner and outer envelopes/packaging addressed the same in case the outer one gets ripped open or damaged by water.
* Seal all packages well, with tape.
* Follow any special requirements and conditions set by the seller.
* Film or take high-resolution photos of the cash packaging process with the address and tracking number already affixed to packaging.
* Send the cash package to the BTC seller with a courier service that requires receipt of delivery to be confirmed by the seller.
* Consider using a courier service that has appropriate insurance in place for any issues with delivery.
* Communicate with courier service as required.

'''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).'''

= Receiving cash in the mail =

When receiving cash in the mail, you should:

* Film the opening of the package, making sure that the tracking number provided by the sender is visible in the video.
* Follow any special requirements and conditions set by the buyer.
* Communicate with buyer's courier service as required.

= Dispute resolution =

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.

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.

Regarding dispute resolution, please note:

* Mediators can consider your case and make a suggestion, but they are NOT guaranteed to help.
* 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.
* If a trader rejects a mediation suggestion and opens arbitration, it could lead to lose both trading and deposit funds.
* 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.

Network status indicator

2022-08-23T21:19:27Z

Jmacxx:

There is an icon in the bottom right footer bar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a popup description of the state.

'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state. To resolve the issue, see [[Troubleshooting_network_issues|Troubleshooting network issues]]

'''Yellow''' - there are outbound but no inbound connections. Bisq can operate in this state, but it is sub-optimal.
This is a normal state at application startup, until peers discover and connect to your node.
However if it persists for several hours it could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
If this condition persists for more than a few hours, clear the Tor cache and restart Bisq after clicking on: Settings -> Network Info -> Open Tor Settings -> <code>[Delete outdated Tor files and shut down]</code>.

'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.

This indicator has been created because some Bisq nodes get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than an hour, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. The yellow status indicator will start blinking to attract your attention if the issue does not get resolved.

Troubleshooting network issues

2022-08-17T21:47:22Z

Jmacxx: moved Network_status_indicator to top level page

Network status indicator

2022-08-17T21:44:28Z

Jmacxx: Created page with " [''feature, TBD, in development''] There is an icon in the bottom right footer bar to indicate the the status of the P2P network connection. It will be either red, yellow o..."

[''feature, TBD, in development'']

There is an icon in the bottom right footer bar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a popup description of the state.

'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state. To resolve the issue, see [[Troubleshooting_network_issues|Troubleshooting network issues]]

'''Yellow''' - there are outbound but no inbound connections. Bisq can operate in this state, but it is sub-optimal.
This is a normal state at application startup, until peers discover and connect to your node.
However if it persists for several hours it could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
If this condition persists for more than a few hours, clear the Tor cache and restart Bisq after clicking on: Settings -> Network Info -> Open Tor Settings -> <code>[Delete outdated Tor files and shut down]</code>.

'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.

This indicator has been created because some Bisq nodes get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than an hour, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. The yellow status indicator will start blinking to attract your attention if the issue does not get resolved.

Troubleshooting network issues

2022-08-17T02:21:52Z

Jmacxx: /* Network status indicator */

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.

__TOC__

== Weak internet connection ==

Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to cause issues.

== 3/4 connection problem ==

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.
This can happen on weak or slow internet connections, or if Tor is having issues relaying the large data download to your node.
Proposed mitigation is to clear the Tor cachefiles. (Close Bisq first). All files except <code>hiddenservice</code> can be deleted from <code>btc_mainnet/tor</code> beneath the [[https://bisq.wiki/Data_directory#Default_locations data directory]], they will be re-created as necessary at startup. <code>hiddenservice</code> should be kept as it defines your onion address.

See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843

For a geekier approach, you can also try [[Manually_select_seednodes|manually choosing seednodes to connect to]]

== Windows antivirus software ==

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.

== Being temporarily banned by the Tor network ==

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.

== Tor censorship ==

In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.

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.

If you're in China, [[在中国运行Bisq_(Running_Bisq_in_China)|this method using SStap]] has worked to get around the Great Firewall.

==Tor bridges that don't work ==

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.

In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.

== Altcoin nodes running on the same computer ==

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.

To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.

== Network status indicator ==

[''feature, TBD, in development'']

There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state. This indicator has been added because some Bisq nodes get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. If this test fails, a popup will appear describing the problem.

'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state.

'''Yellow''' - there are outbound but no inbound connections. This could be normal if there has not been enough uptime for peers to discover and connect to your node.
Bisq can operate in this state, but it is sub-optimal. It could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
If this condition persists for more than a few hours, clear the Tor cache and restart Bisq by clicking on: Settings -> Network Info -> Open Tor Settings -> [Delete outdated Tor files and shut down].

'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.

Troubleshooting network issues

2022-08-17T02:07:58Z

Jmacxx: Add section for Network status indicator

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.

__TOC__

== Weak internet connection ==

Bisq generally needs a strong, fast connection to work properly. Tethering on mobile connections can work but is known to cause issues.

== 3/4 connection problem ==

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.
This can happen on weak or slow internet connections, or if Tor is having issues relaying the large data download to your node.
Proposed mitigation is to clear the Tor cachefiles. (Close Bisq first). All files except <code>hiddenservice</code> can be deleted from <code>btc_mainnet/tor</code> beneath the [[https://bisq.wiki/Data_directory#Default_locations data directory]], they will be re-created as necessary at startup. <code>hiddenservice</code> should be kept as it defines your onion address.

See https://github.com/bisq-network/bisq/issues/2547#issuecomment-1016787843

For a geekier approach, you can also try [[Manually_select_seednodes|manually choosing seednodes to connect to]]

== Windows antivirus software ==

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.

== Being temporarily banned by the Tor network ==

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.

== Tor censorship ==

In certain situations, Bisq may fail to start because your ISP or network provider is actively blocking Tor.

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.

If you're in China, [[在中国运行Bisq_(Running_Bisq_in_China)|this method using SStap]] has worked to get around the Great Firewall.

==Tor bridges that don't work ==

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.

In these scenarios, consider using a VPN and then running Bisq from within the VPN tunnel.

== Altcoin nodes running on the same computer ==

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.

To solve this, switch altcoin nodes off, turn Bisq on and let it load completely. Then, turn the altcoin nodes back on.

== Network status indicator ==

[''feature, TBD, in development'']

There is an icon in the bottom right footerbar to indicate the the status of the P2P network connection. It will be either red, yellow or green depending on the count and type of connections your node has. Hover over it with the mouse to see the connections detail, or click on it to get a description of the error state. This indicator has been added because some users get unknowingly stuck in a state of not accepting inbound connections, and therefore never getting any takers for their offers. If the status remains yellow for more than 30 minutes, the Bisq node will do a self-ping test over Tor in order to check incoming connectivity. If this test fails, a popup will appear describing the problem.

'''Red''' - An error situation- there are no P2P network connections. This would usually indicate that your internet connection has broken. Check other network applications such as a web browser. Bisq cannot function properly in this state.

'''Yellow''' - there are outbound but no inbound connections. This could be normal if there has not been enough uptime for peers to discover and connect to your node.
Bisq can operate in this state, but it is sub-optimal. It could mean that inbound connections are blocked, the result being your offers would not be reachable. (Peers would be frustrated with the response "Maker_Offline" as a result of trying to take your offer).
If this condition persists for more than a few hours, clear the Tor cache and restart Bisq by clicking on: Settings -> Network Info -> Open Tor Settings -> [Delete outdated Tor files and shut down].

'''Green''' - the P2P connection is healthy, as you have a mix of outbound and inbound connections.

Troubleshooting network issues

2022-05-29T20:44:16Z

Jmacxx: Added section on 3/4 connection problem

Manual payout

2022-05-15T17:00:28Z

Jmacxx: Re-formatted to show the Bisq Manual Payout tool instructions before the coinbin instructions.

== Overview ==

Funds for a Bisq trade are locked in a 2-of-2 multisig that is controlled only by the two parties involved.
Bisq normally does all the work to sign and publish the payout at trade completion.
However sometimes a trade can fail due to unforseen circumstances, leaving the funds stranded in the 2-of-2 multisig.
When this happens, a Manual Payout may be necessary.

== Using Bisq's Manual Payout tool ==
The emergency payout tool is in Bisq, if you do a CTRL-G it will open.

The purpose of the tool is to allow owners of a 2of2 multisig to issue a transaction which pays out the funds to their addresses. The tool is designed to be used in collaboration with mediators but
it could conceivably be used by the multisig key holders alone.

It is similar in operation to the tool "coinbin".

The tool operates in 4 steps:

# Fill input information;
# Import/export details to trade participants;
# Sign using each holder's private key;
# Build and broadcast the payout.

=== Fill in inputs ===

Input information can be either filled in manually using information from the Bisq trade's Json contract, or for ease of use the same information can be imported from the Mediation ticket.

* If filling in manually, all fields on the "Inputs" tab must be entered.
* If importing from Mediation, choose the Import menu option then pick your mediation ticket from the drop down list and press "Import from mediation ticket".

One important thing which the tool prompts you for is the "amountInMultisig" field. This value is not known in Bisq, so the user (or Mediator) has to look it up on a Blockchain explorer and enter it completely accurately into the tool. If it is incorrect in any way the resultant transaction will fail. (Reason for this is that Segwit includes the amount as part of the signature inputs).

=== Import/Export to trade participants ===

Once accurate input information has been entered, the same information needs to be passed to both owners of the multisig keys (the two traders). This is what the "Export" menu item is for. It translates the input field data into a code which can be DM'd or emailed to the participants, which they can enter via the "Import" menu (& "Import from String" option).

The important thing is that each participant have EXACTLY the same information entered into the Inputs section of the tool. If there is any discrepancy between the inputs that each participant signs, then the transaction will be invalid.

Note that if the two traders have access to the mediation ticket they can Import from the ticket themselves. But it is generally best for Mediator to Export their filled in fields to both traders (via DM).

=== Sign ===

Both participants have to sign the inputs. This is done from the Sign menu, for convenience there is a "Locate key in wallet" button which will scan the user's wallet for a key which matches the inputs. "Generate signature" will sign the inputs using the key at the top of the screen. Users could alternatively choose to locate the key themselves, and paste it into the "privateKeyHex" field before doing "Generate signature".

Once the signature has been generated each participant should send it to the person who will build and broadcast the transaction (usually the Mediator).

=== Build & Broadcast ===

Once both signatures have been provided, they can be pasted into the Build screen at which time the "Build" button at the bottom of that screen should be pressed. It will generate the TxID and transaction hex into the text area. The transaction hex can be verified using your own tools* or simply broadcast to the network using the "Broadcast" button (or alternatively send it yourself using your Bitcoin node).

* NB: "https://bitaps.com/broadcast" has a "Preview" feature that tests if the transaction is acceptable to the mempool before actually sending it. Any errors in the transaction will be listed, or if it is good it will say "Test mempool transaction accepted" and give the option to broadcast it at that point.

== Alternate method using coinbin ==

In this process you copy and paste your private keys from the Bisq software into a web browser. As a precaution it is advised you remove all of your funds from this wallet before starting this procedure.

=== Precautions ===

This method is only necessary in extreme occasions where one of the traders may not be available. Therefore it is important to make sure that the person who constructs the transaction does not defraud the other signers.

=== What you need ===

This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.
To spend out of a multisig, two things are needed:
* A redeem script.
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.

Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.

Tools you need:
* Bisq software
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]
* [https://coinb.in/ Coinbin web wallet]
* [https://www.torproject.org/ Tor browser]

=== Get multisig public keys ===

Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract.
# Find your trade under <code>PORTFOLIO</code>.
# Click the <code>i</code> icon next to the trade ID, and at the bottom click <code>VIEW CONTRACT IN JSON FORMAT</code>. At the end, you see the Buyer and Seller public keys:
<nowiki>
BuyerMultiSigPubKeyHex: <hex value>
SellerMultiSigPubKeyHex: <hex value></nowiki>

=== Get private keys ===

To access your Bisq wallet private key
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.
# In the text editor, search for the public key value. You are looking for an entry that reads <code>DeterministicKey{pub HEX=<hex value></code> where <hex value> is the public key.
# When you've found this entry, select and copy the <code>priv WIF=<hex value></code> value that immediately follows the pub HEX value. This value is the private key.
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.

''Note: If your wallet uses a password, you will need to remove the password to view the private keys in wallet data.''

=== Get payout addresses ===

At the end of the JSON contract file you can also find the intended payout address for each trader:
<nowiki>
makerPayoutAddressString: <address value>
takerPayoutAddressString: <address value></nowiki>

=== Recreating Redeem script ===

For all the web interactions use the Tor browser.
# Go to the [https://coinb.in/ Coinbin web wallet]:
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code>
# Paste the three public keys in the following order 1) SellerMultiSigPubKeyHex, 2) BuyerMultiSigPubKeyHex
# Click <code>submit</code> to see an address and a Redeem Script. Make sure the address matches the multisig address for the trade. If not, try to change the order of the public keys.
# Copy and save the Redeem Script.

=== Creating transaction ===

# Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.
# Paste the Redeem Script in the text field at the top and click <code>Load</code>. It should take a few seconds and then return the value locked in the multisig.
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.
# Add a new output by clicking the <code>+</code> sign next to the <code>amount</code> field. For this second output paste the address that belongs to <code>takerPayoutAddressString</code> and the respective trade amount.
# Copy and save the transaction.
# Click <code>submit</code> to obtain an encoded transaction string.

=== Verify transaction ===

Click <code>Verify</code> at the top and paste the encoded string obtained from the step 5.e. Verify it all is correct before moving to the next step.

=== Sign transaction ===

# Click <code>Sign</code> at the top of the page and paste your WIF private key in the <code>Private key</code> text field and the encoded transaction in the text field below.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

=== Second signature and broadcast ===

# The second signer clicks <code>Verify</code> at the top of the Coinbin website and pastes the encoded string the previous signer shared with you. If you are ok with it, click <code>Sign</code> at the top of the page and paste your WIF private key text field and the encoded transaction shared with you in the text field below.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it.

=== Verify transaction before broadcasting===

# Confirm everything is correct and click <code>Broadcast</code> at the top of the page.
# After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.
# When complete, delete the <code>bisqWallet.txt</code> file created in step 1.

Data Privacy

2022-03-11T16:25:58Z

Jmacxx:

As Bisq is a peer to peer trading system, there is no central server for storing account information. Only the two people involved in a P2P trade know the details of that trade. If mediation or arbitration is opened, the mediator or arbitrator are provided with the trade details too.

The trade parameters are stored on those participants' computers. That is much better than having the data stored in centralized servers, but still is not ideal. Bisq users may trade with lots of people over time and those details can accumulate. If their computer were lost stolen or seized, unwelcome individuals might gain access to that information, which in the case of more popular trading methods would be account names and numbers.

To mitigate that risk, Bisq has introduced a feature to clear account related information from closed trades after a certain grace period has passed. As always, you are in charge of your own Bisq instance and so this grace period can be configured to best suit your preference. It is configured by the field "Clear sensitive data after (days)" in the Settings screen. Once a trade has finished, it is unlikely that you ever need to see your trading peer's payment account information, as it was only required to make and/or verify that payment. So a good rule of thumb would probably be the default setting of 60 days, or lower. After a closed trade has passed the grace period, Bisq clears maker/taker payment account payloads from the trade, as well as trader chats. The same applies to any Mediation/Arbitration dispute linked to the trade. (Note that the grace period is measured from the trade date, so for example if you did a trade on 1st January, and it completed on the 5th of January the account information would be cleared on the 1st March based on the default setting of 60 days.)

That's all there is to it, a privacy preserving effort we can all take part in to keep Bisq useful and safe for all, especially for your past trade peers whose details you might have the liability to protect.

Payment methods

2022-03-08T01:26:04Z

Jmacxx:

<languages/>
<translate>
Bisq offers several '''payment methods''' to buy and sell bitcoin for fiat currencies or other cryptocurrencies.


Every offer on Bisq designates a payment method for traders to settle payments. The Bisq software does not actually integrate with any payment methods—'''all non-bitcoin fund transfers are made outside of Bisq software'''.


Unlike cryptocurrency transfers, many fiat payment transfers are riddled with flaws and limitations that require Bisq to employ special measures to encourage fair and honest trades. One of these measures is lower per-trade limits, which are covered below. Another key measure is [[Account_limits#Account_signing|account signing]].


__TOC__

== Fiat payment methods == 


The payment methods vary in chargeback risk, regional availability, transaction size, fees, privacy, verifiability, and other characteristics.
The top consideration for maintaining payment methods is chargeback risk. PayPal, Venmo, and Cash App are not supported on Bisq because chargebacks for payments made with those services are relatively easy.


We welcome suggestions for new payment methods on Bisq, especially for those that enable new markets. Documentation on the criteria and process for adding new payment methods is found [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here]. Please also feel free to make suggestions by reaching out on [https://bisq.chat Matrix] in the #payment-methods channel.


Below is a list of fiat payment methods Bisq currently supports.


''Note: The maximum trade sizes listed below are not available for most newly-created payment accounts. Please refer to [https://bisq.wiki/Account_signing Account signing] for details on how to enable larger trade sizes for your payment accounts. ''


{| class="wikitable sortable"
|-
! Payment Method !! Region !! Trading Period !! Per-Trade Limit !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.25 BTC || coming soon v1.8.0!
|-
| Advanced Cash* || Global || 1 day || 2.00 BTC || Not available in the USA.
|-
| Alipay* || China || 1 day || 1.00 BTC ||
|-
| [[Amazon_eGift_card|Amazon eGift Card*]] || Global (AUS, CAD, EUR, GBP, INR, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.25 BTC || Supported in USD, EUR, CAD, and a [[Amazon_eGift_card|handful of other markets]].
|-
| Australian PayID* || Australia || 1 day || 1.00 BTC ||
|-
| [[Bizum]]* || Spain|| 1 day || €2,000 Euros per day || NEW
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.25 BTC || NEW
|-
| [[Cash by Mail]]* || Global || 8 days || 0.25 BTC || Please check [[Cash_by_Mail|the article]] and follow the instructions to avoid disputes.
|-
| Cash Deposit* || N/A || 4 days || 0.25 BTC || Ensure to follow Cash by Mail trade rules.
|-
| [[CelPay]]* || Global || 1 days || $2,500 limit per day || NEW
|-
| [[Domestic Wire Transfer]]* || USA || 3 days || 0.25 BTC || coming soon v1.8.0!
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 1.00 BTC || [[Face-to-face_(payment_method)|See article]] for special guidance on F2F transactions.
|-
| [[Faster Payments]]* || UK || 1 day || 0.25 BTC || [[Faster_Payments|See article]] for recent changes to avoid issues.
|-
| HalCash* || Spain || 1 day || 1.00 BTC ||
|-
| [[IMPS]]* || India || 1 day || Rs. 1,000,000 per day || NEW
|-
| Interac e-Transfer || Canada || 1 day || 0.25 BTC ||
|-
| Japan Zengin Furikomi* || Japan || 1 day || 1.00 BTC ||
|-
| [[Monese]]* || Europe (GBP, EUR and RON) || 1 day || 0.25 BTC || NEW
|-
| MoneyBeam (N26) || Europe || 1 day || 0.25 BTC ||
|-
| MoneyGram* || Global || 4 days || 0.50 BTC ||
|-
| National Bank Transfer || N/A || 4 days || 0.25 BTC ||
|-
| [[Nequi]]*|| Colombia || 1 day || COP 7,000,000 per month || NEW
|-
| [[NEFT]]* || India || 1 day || Rs. 50,000 per transaction || NEW
|-
| [[Paxum]]* || Global || 1 day || 0.25 BTC || NEW
|-
| [[Paysera]]* || Global || 1 day || 0.25 BTC || NEW
|-
| [[PayTM]]* || India || 1 day || Rs. 100,000 per transaction || NEW
|-
| Perfect Money* || Europe and USA || 1 day || 1.00 BTC ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.25 BTC || NEW
|-
| Popmoney || USA || 1 day || 0.25 BTC ||
|-
| PromptPay* || Thailand || 1 day || 1.00 BTC ||
|-
| [[Revolut]] || Global || 1 day || 0.25 BTC || [[Revolut|See article]] for recent changes to avoid issues.
|-
| [[RTGS]]* || India || 1 day || Minimum of Rs.200,000, Maximum of Rs.1,000,000 per transaction || NEW
|-
| [[Satispay]]* || Italy || 1 day || 0.25 BTC || NEW
|-
| SEPA || Europe || 6 days || 0.25 BTC ||
|-
| SEPA Instant || Europe || 1 day || 0.25 BTC ||
|-
| Skrill* || Global || Varies || 0.25 BTC || Coming soon!
|-
| [[Strike]]* || USA || 1 day || $1,000 maximum per transaction || NEW
|-
| [[SWIFT]]* || Worldwide || 7 days || 0.5 BTC ||
|-
| Swish* || Sweden || 1 day || 1.00 BTC ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || €2,500 maximum per transaction || Coming soon v1.8.0!
|-
| Transfer with Same Bank || N/A || 2 days || 0.25 BTC ||
|-
| Transfer from Specific Banks || N/A || 4 days || 0.25 BTC ||
|-
| [[TransferWise]]* || Global except USD trades || 4 days || 1.00 BTC ||
|-
| [[TransferWise-USD]]* || Global for USD trades || 4 days || 1.00 BTC || Coming soon v1.8.0!
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.25 BTC || Within USA, $1000 limit per transaction, up to $3000 per day without ID.
|-
| Uphold || Global || 1 day || 0.25 BTC ||
|-
| [[UPI]]* || India || 1 day || Rs. 100,000 per transaction || NEW
|-
| [[Verse]]* || Europe (EUR, SEK, HUF, DKK, PLN) || 1 day || €10,000 per year || NEW
|-
| WeChat Pay* || China || 1 day || 1.00 BTC ||
|-
| Western Union || Global || 4 days || 0.50 BTC ||
|-
| Zelle || USA || 4 days || 0.25 BTC || See [https://www.zellepay.com/get-started this page] to see if/how your bank works with Zelle (including sending limits).
|}


<nowiki>*</nowiki> These payment methods '''do not''' need to be signed to lift the 0.01 BTC buying limit (see [[Account_limits#Account_signing|account signing]] for more details).

=== Payment method guides === 


<div style="margin-top: 1.5em;">
<li style="display: inline-block;"> [[File:Payment-methods-advice-eur.png|thumb|none|300px|EUR payment methods overview.]] </li>
<li style="display: inline-block;"> [[File:Payment-methods-advice-usd.png|thumb|none|300px|USD payment methods overview.]] </li>
</div>


<div style="clear: both;"></div>

== Altcoin payment methods == 


Bisq also supports a [https://bisq.network/markets/ variety] of cryptocurrencies for buying and selling bitcoin, like [[XMR]], [[ETH]], [[ZEC]], [[L-BTC]] or [[LTC]].


Because altcoin transfers are irreversible and relatively quick, altcoin trades can be up to 2 BTC in size right away (no need to wait for account aging or account signing).


{| class="wikitable"
|-
! Payment Method !! Trading Period !! Per-Trade Limit
|-
| [[Altcoins]] || 1 day || 2.00 BTC
|-
| [[Altcoins Instant]] || 1 hour || 2.00 BTC
|}


Altcoins Instant trades go by fast! Please remember to disable Instant offers in <code>Portfolio</code> > <code>My Open Offers</code> if you might not be around to settle an Instant trade.


See more details about creating altcoin accounts [[Creating_a_payment_account#Creating_an_altcoin_account | here]].


[[Category:Features]]
</translate>

Data Privacy

2022-03-04T15:19:52Z

Jmacxx: Jmacxx moved page Draft:Data Privacy to Data Privacy: moved out of draft status

As Bisq is a peer to peer trading system, there is no central server for storing account information. Only the two people involved in a P2P trade know the details of that trade. If mediation or arbitration is opened, the mediator or arbitrator are provided with the trade details too.

The trade parameters are stored on those participants' computers. That is much better than having the data stored in centralized servers, but still is not ideal. Bisq users may trade with lots of people over time and those details can accumulate. If their computer were lost stolen or seized, unwelcome individuals might gain access to that information, which in the case of more popular trading methods would be account names and numbers.

To mitigate that risk, Bisq has introduced a feature to clear account related information from closed trades after a certain grace period has passed. As always, you are in charge of your own Bisq instance and so this grace period can be configured to best suit your preference. It is configured by the field "Clear sensitive data after (days)" in the Settings screen. Once a trade has finished, it is unlikely that you ever need to see your trading peer's payment account information, as it was only required to make and/or verify that payment. So a good rule of thumb would probably be the default setting of 20 days. After a closed trade has passed the grace period, Bisq clears maker/taker payment account payloads from the trade, as well as trader chats. The same applies to any Mediation/Arbitration dispute linked to the trade. (Note that the grace period is measured from the trade date, so for example if you did a trade on 1st January, and it completed on the 5th of January the account information would be cleared on the 21st January based on the default setting of 20 days.)

That's all there is to it, a privacy preserving effort we can all take part in to keep Bisq useful and safe for all, especially for your past trade peers whose details you might have the liability to protect.

Draft:Data Privacy

2022-03-04T15:19:52Z

Jmacxx: Jmacxx moved page Draft:Data Privacy to Data Privacy: moved out of draft status

#REDIRECT [[Data Privacy]]

Data Privacy

2022-01-30T02:49:20Z

Jmacxx: Describes a feature to clear sensitive peer account data from the Bisq app

As Bisq is a peer to peer trading system, there is no central server for storing account information. Only the two people involved in a P2P trade know the details of that trade. If mediation or arbitration is opened, the mediator or arbitrator are provided with the trade details too.

The trade parameters are stored on those participants' computers. That is much better than having the data stored in centralized servers, but still is not ideal. A market maker on Bisq may trade with a lot of people over time and those details can accumulate. If their computer were lost stolen or siezed, unwelcome individuals might gain access to that information, which in the case of more popular trading methods would be account names and numbers.

To mitigate that risk, Bisq has introduced a feature to clear account related information from closed trades after a certain grace period has passed. As always, you are in charge of your own Bisq instance and so this grace period can be configured to best suit your preference. It is configured by the field "Clear sensitive data after (days)" in the Settings screen. Once a trade has finished, it is unlikely that you ever need to see your trading peer's payment account information, as it was only required to make and/or verify that payment. So a good rule of thumb would probably be the default setting of 20 days. After a closed trade has passed the grace period, Bisq clears maker/taker payment account payloads from the trade, as well as trader chats. The same applies to any Mediation/Arbitration dispute linked to the trade. (Note that the grace period is measured from the trade date, so for example if you did a trade on 1st January, and it completed on the 5th of January the account information would be cleared on the 21st January based on the default setting of 20 days.)

That's all there is to it, a privacy preserving effort we can all take part in to keep Bisq useful and safe for all.

Frequently asked questions

2022-01-19T18:08:59Z

Jmacxx: /* Common Technical Niggles */

Below is a compilation of '''frequently-asked questions (FAQ)''' about Bisq, how to use it, and how to help the project.

Feel free to ask further questions on any of Bisq's many outreach channels.

== About ==

==== How is Bisq different from other decentralized exchanges? ====

Bisq is a peer-to-peer trading network, not a website or "app" 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.

And you can trade bitcoin for fiat currencies with it!

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).

With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.

* 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.
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.
* 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.
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.
* 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.

See more in the [[Introduction]].

==== Is Bisq open-source software? ====

Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License.

Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].

==== Is Bisq safe? ====

Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.

Bisq employs three primary mechanisms to achieve security:

* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.
* Both traders are required to pay security deposits, which are refunded after trades are completed.
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.

When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.

To mitigate this risk, Bisq:

* 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.
* 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.

== Getting started ==

==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====

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.

Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.

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].

==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====

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.

{{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).

You can check trade history for your market by going to <code>Market</code> > <code>Trades</code> and picking your currency from the dropdown.}}

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.

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.

==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====

Yes, the chicken-and-egg problem with Bisq is real.

Here are some ways to get just enough bitcoin to do your first trade on Bisq:
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]
* hop onto the <code>#buy-bitcoin</code> channel on [https://keybase.io/team/bisq Keybase] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])

== Trading ==

==== What are trading fees? ====

[[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.

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.

==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====

Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.

Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.

Other things you can do:
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)

==== Why does Bisq require a security deposit in BTC? ====

[[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.

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.

Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.

See full [[trading rules]].

==== What are trading limits? How much bitcoin can I buy/sell at once? ====

Trading limits vary based on payment method, since some payment methods are more secure than others.

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]].

Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.

==== Which payment methods are available? ====

See [[payment methods]].

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].

==== How does Bisq handle fiat like dollars and euros? Where does it go? ====

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.

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.

==== How long does a trade take? ====

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.

Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).

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.

Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).

See the list of [[payment methods]] for complete details.

==== How does Bisq protect my privacy? ====

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).

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.

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.

==== Do I need to keep Bisq online for my offers to remain online? ====

Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.

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).

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.

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).

==== Do I have to use the Bisq wallet? ====

No, but you may find it convenient to keep a small amount of trading capital there.

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.

Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.

==== Do I have to use the Bisq token? ====

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.

==== Will my bank know I'm trading bitcoin? ====

Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.

But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the "reason for payment" field always be left BLANK when making a payment (if the payment method offers such a field).

If a reason is required, it should be something trivial like a "-" or "payment". If you want to use something else, please agree on an alternative with your peer using trader chat.
See full [[trading rules]] for more information.

== Common Technical Niggles ==

==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ====

If Bisq won't open, try right-clicking the app and clicking <code>Open</code>.

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.

==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====

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]].

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.

If the issue doesn't go away on its own, please reach out for help in the <code>#support</code> channel [https://keybase.io/team/bisq on Keybase] or open an issue [https://github.com/bisq-network/bisq on GitHub].

==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====

See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.

==== Bisq says "this offer cannot be taken due to counterparty trade restrictions". What does that mean? ====

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.

==== My SPV resync is taking all day and it keeps freezing. What can I do to make it go faster? ====

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]].
After your SPV resync is completed, it would be best to switch to a fresh wallet.

==== How can I get a fresh Bisq wallet and transfer my BSQ balance to it? ====

The procedure involves setting aside the existing wallet directory (by renaming) in order to get a fresh wallet. The wallet directory is at <code>btc_mainnet/wallet</code> 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.
# You have some BSQ and also some BTC balance existing in your wallet. (You need BTC to pay mining fees for sending BSQ).
# Close Bisq then rename your <code>wallet</code> directory to <code>oldWallet</code>.
# 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).
# Close Bisq and rename your <code>wallet</code> dir to <code>newWallet</code>, rename your old wallet dir to <code>wallet</code>, then restart Bisq.
# Send BSQ to your new receiving address you saved in the earlier step. Then send BTC the same way. Close Bisq.
# Rename <code>wallet</code> to <code>oldWallet</code> and <code>newWallet</code> to <code>wallet</code>. Then restart Bisq.

Done! Your BSQ and BTC balances have been moved to a fresh wallet.

== Dispute resolution ==

==== How does dispute resolution work? ====

Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.

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.

Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.

See [[trading rules]] and [[dispute resolution]] for more.

==== How is collusion between mediators, arbitrators, and traders prevented? ====

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.

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.

==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====

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.

Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:

# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.
# [[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.
# National currency payment methods which are found to be used for chargebacks are quickly removed.

==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====

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.

Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.

==== How can I contact my trading peer? ====

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.

== DAO ==

==== What is the Bisq DAO? ====

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?

Decentralized software is no good without decentralized governance.

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.

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.

Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].

==== How does the Bisq DAO work? ====

The primary purposes of the Bisq DAO are financing the project and determining strategy.

# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.

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].

See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.

==== What do I need to know about the DAO, as a trader? ====

First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.

But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.

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.

When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.

[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].

==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====

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.

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.

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].

==== Can I use Bisq without BSQ and without this DAO? ====

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.

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.

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.

== Other ==

==== This project is cool! How can I help out? ====

Check out the [[contributor checklist]]. We'd love to hear from you!

==== I have a question that isn’t covered here...? ====

Feel free to reach out [https://keybase.io/team/bisq on Keybase] or [https://bisq.network/#community any other channel].

Frequently asked questions

2022-01-14T21:22:57Z

Jmacxx: /* Common Technical Niggles */

Below is a compilation of '''frequently-asked questions''' about Bisq, how to use it, and how to help the project.

Feel free to ask further questions on any of Bisq's many outreach channels.

== About ==

==== How is Bisq different from other decentralized exchanges? ====

Bisq is a peer-to-peer trading network, not a website or "app" 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.

And you can trade bitcoin for fiat currencies with it!

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).

With Bisq you're always the owner—not just owner of your bitcoin, but also owner of your data.

* 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.
* Bisq does not hold any national currency. National currency is transferred directly from one trader to the other using traditional banking and payment services.
* 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.
* Bisq does not know anything about traders who use its network, and no data is stored on who trades with whom.
* Bisq does not require registration, so your privacy is protected, and you can '''begin trading instantly'''.
* 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.

See more in the [[Introduction]].

==== Is Bisq open-source software? ====

Bisq's software is free/libre open-source licensed under Version 3 of the GNU Affero General Public License.

Here's the [https://github.com/bisq-network/bisq source code] and [https://github.com/bisq-network/bisq/blob/master/LICENSE license].

==== Is Bisq safe? ====

Thanks to strong incentives encouraging traders to play fairly, the vast majority of trades on Bisq go smoothly and quickly.

Bisq employs three primary mechanisms to achieve security:

* All bitcoin traded with Bisq is secured in a 2-of-2 multisignature address.
* Both traders are required to pay security deposits, which are refunded after trades are completed.
* Trade disputes are handled through a [[Dispute_resolution|3-tier mechanism]] that includes end-to-end encrypted trader chat, mediation, and arbitration.

When trading fiat currency for bitcoin, there is always some chargeback risk, as fiat transactions can often be reversed.

To mitigate this risk, Bisq:

* 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.
* 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.

== Getting started ==

==== I find Bisq very confusing. I've tried using it but just end up getting lost! ====

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.

Then check out the [https://bisq.network/getting-started getting-started guide] to see how to get up and running quickly.

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].

==== I can't use Bisq to trade because there are hardly ever any offers in my currency. What can I do? ====

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.

{{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).

You can check trade history for your market by going to <code>Market</code> > <code>Trades</code> and picking your currency from the dropdown.}}

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.

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.

==== I heard I need bitcoin in order to buy bitcoin on Bisq...but I don't have any bitcoin. What can I do? ====

Yes, the chicken-and-egg problem with Bisq is real.

Here are some ways to get just enough bitcoin to do your first trade on Bisq:
* try to obtain some yourself using [https://bisq.wiki/Funding_your_wallet#How_to_Obtain_Your_First_Bitcoin these suggestions]
* hop onto the <code>#buy-bitcoin</code> channel on [https://keybase.io/team/bisq Keybase] and make a deal ([[Informal_Market_for_Small_BTC_Trades|see more here]])

== Trading ==

==== What are trading fees? ====

[[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.

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.

==== Mining fees are too high. How can I trade on Bisq cost-effectively? ====

Bisq's current trade protocol requires 4 on-chain transactions. Takers pay for 3 of these transactions and makers pay for 1 of them.

Therefore, to make trading on Bisq as cost-effective as possible, consider '''making your own offers''' at times '''when mining fees are lower'''.

Other things you can do:
* make offers to trade '''larger amounts of BTC''' (bigger offers tend to get better pricing)
* '''pay trade fees with BSQ''' (BSQ trade fees tend to be about half of BTC trading fees)

==== Why does Bisq require a security deposit in BTC? ====

[[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.

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.

Most Bisq trades complete without any problem thanks in part to the incentives that security deposits create.

See full [[trading rules]].

==== What are trading limits? How much bitcoin can I buy/sell at once? ====

Trading limits vary based on payment method, since some payment methods are more secure than others.

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]].

Altoins are not possible to charge back, so all altcoin trades have a limit of 2 BTC.

==== Which payment methods are available? ====

See [[payment methods]].

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].

==== How does Bisq handle fiat like dollars and euros? Where does it go? ====

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.

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.

==== How long does a trade take? ====

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.

Some payment methods are instant (e.g., Faster Payment) while others can take a few days (e.g., SEPA).

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.

Altcoin trade periods are always 1 day (or 1 hour for Altcoins Instant trades).

See the list of [[payment methods]] for complete details.

==== How does Bisq protect my privacy? ====

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).

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.

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.

==== Do I need to keep Bisq online for my offers to remain online? ====

Yes. There are no central servers on the Bisq network—so all peers are responsible for keeping their offers online.

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).

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.

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).

==== Do I have to use the Bisq wallet? ====

No, but you may find it convenient to keep a small amount of trading capital there.

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.

Likewise, when concluding a trade on Bisq, you can withdraw your funds to the Bisq wallet or to an external wallet.

==== Do I have to use the Bisq token? ====

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.

==== Will my bank know I'm trading bitcoin? ====

Generally speaking, Bisq doesn't deal with banks at all. All fiat transfers take place directly between users.

But there have been reports of banks closing accounts upon suspecting bitcoin activity. As a result, Bisq requires that the "reason for payment" field always be left BLANK when making a payment (if the payment method offers such a field).

If a reason is required, it should be something trivial like a "-" or "payment". If you want to use something else, please agree on an alternative with your peer using trader chat.
See full [[trading rules]] for more information.

== Common Technical Niggles ==

==== Bisq on macOS won't open, or it's asking for permission to record my keystrokes! ====

If Bisq won't open, try right-clicking the app and clicking <code>Open</code>.

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.

==== Bisq seems to bog down my computer. When I open it, CPU and memory usage spike. Can this be prevented? ====

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]].

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.

If the issue doesn't go away on its own, please reach out for help in the <code>#support</code> channel [https://keybase.io/team/bisq on Keybase] or open an issue [https://github.com/bisq-network/bisq on GitHub].

==== I'm on a high-resolution monitor on Linux and everything is way too small. Help? ====

See [[Running_on_HiDPI_screen|this article]] for a tip on fixing this issue.

==== Bisq says "this offer cannot be taken due to counterparty trade restrictions". What does that mean? ====

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.

== Dispute resolution ==

==== How does dispute resolution work? ====

Bisq provides a 3-layer mechanism for resolving disputes: trader chat, mediation, and arbitration.

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.

Veteran users: please note that the arbitrator role changed significantly with the launch of the new trade protocol on v1.2.

See [[trading rules]] and [[dispute resolution]] for more.

==== How is collusion between mediators, arbitrators, and traders prevented? ====

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.

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.

==== What happens if the person buying bitcoin does a chargeback after the bitcoin has been released from the multisig address? ====

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.

Bisq's goal is to make this scenario as unattractive as possible, using three primary mechanisms:

# [[Account limits|Account aging]] requires newly-created fiat payment accounts on Bisq to have lower trade limits, and those limits are increased over time.
# [[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.
# National currency payment methods which are found to be used for chargebacks are quickly removed.

==== Wouldn't a pure reputation system among traders make mediators and arbitrators unnecessary? ====

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.

Such mechanisms are also problematic for protecting privacy and for keeping the service decentralized.

==== How can I contact my trading peer? ====

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.

== DAO ==

==== What is the Bisq DAO? ====

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?

Decentralized software is no good without decentralized governance.

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.

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.

Read more about the Bisq DAO in [[Introduction_to_the_DAO|this introductory article]].

==== How does the Bisq DAO work? ====

The primary purposes of the Bisq DAO are financing the project and determining strategy.

# Trading fees are distributed directly from traders to contributors with a token (colored bitcoin) called BSQ.
# Strategy is determined collectively through voting done in the Bisq software and recorded on the Bitcoin network.

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].

See [[Decentralized_autonomous_organization|this article]] for a full list of resources to learn more.

==== What do I need to know about the DAO, as a trader? ====

First of all, you are NOT required to use the BSQ token or Bisq DAO to use Bisq.

But there are benefits to doing so: you'll pay lower trading fees by using BSQ instead of BTC.

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.

When you use BSQ to pay trading fees, it's destroyed and 'burned' out of existence.

[[Introduction_to_the_DAO#Overview|See more on this dynamic here]].

==== Is Bisq using a token because it needs money? What's the issuance schedule for the token? ====

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.

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.

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].

==== Can I use Bisq without BSQ and without this DAO? ====

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.

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.

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.

== Other ==

==== This project is cool! How can I help out? ====

Check out the [[contributor checklist]]. We'd love to hear from you!

==== I have a question that isn’t covered here...? ====

Feel free to reach out [https://keybase.io/team/bisq on Keybase] or [https://bisq.network/#community any other channel].

Trading GRIN

2021-11-10T13:50:51Z

Jmacxx: Add clarifications suggested by GRIN contributor marekyggdrasil

'''[https://github.com/mimblewimble/grin/blob/master/doc/grin4bitcoiners.md GRIN]''' is a minimalistic, lightweight cryptocurrency, implementing the Mimblewimble protocol for a unique balance of privacy and scalability.

== Buying GRIN ==

Buying GRIN is like buying any other [[altcoin]]. It requires a [[Creating_a_payment_account#Creating_an_altcoin_account|GRIN payment account]] in Bisq. The GRIN slatepack address to be used is issued by your grin wallet.

When buying, you should keep your GRIN wallet open to receive the payment. If that is not feasible you can also receive GRIN by exchanging slatepack messages with the seller in trader chat. More information about GRIN transactions can be found [https://docs.grin.mw/about-grin/transactions here].

Once you have recieved the GRIN you should confirm the Bisq trade to release BTC funds and escrow to the counterparty and yourself.

== Selling GRIN ==

The trader ''selling'' GRIN (BTC buyer) will send GRIN to the counterparty's slatepack address using their wallet of choice once the Bisq trade deposit is confirmed.

The amount and recipient address is displayed on-screen when you are prompted to do the transfer.

Example of sending using grin-wallet:
<pre>./grin-wallet -r "https://grinnode.live:3413" send -d grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5 10.123456789</pre>

The GRIN ''buyer'' will confirm the trade in Bisq once they are satisfied that they received the correct amount of GRIN.

You must be able to generate [https://docs.grin.mw/getting-started/wallet-handbook/#proof proof of payment] in case of a dispute. Otherwise, Confidential Transactions make it impossible for a third party to verify if a payment was made —
so GRIN sellers must be able to generate a transaction's proof for mediators or arbitrators in case of disputes.

{{Admonition_Warn|At this moment the only wallet capable of generating and verifying payment proofs is the [https://github.com/mimblewimble/grin-wallet/releases CLI wallet] developed by the GRIN core team.}}

{{Admonition_Warn|Failing to provide the proof to a dispute agent will likely result in losing the dispute case.}}

See below for instructions to generate payment proof.

== FAQ ==

'''How is the price of GRIN determined?'''

The price of GRIN is determined by the marketplace within Bisq.

Trade price is chosen by offer maker (which can be the buyer or seller). Offers are by default arranged in the marketplace with the best prices shown at the top of the list.

The last traded price is shown in at the top right of the screen as "Price of latest Bisq trade".

== Generate payment proof ==

The person sending the GRIN funds can create payment proof.

First, list your transactions using <code>txs</code>, look for the one you want to issue proof on.

The command <code>export_proof</code> will generate a file containing information to prove the details to the recipient or a mediator.

For the purpose of these examples a public node provided by https://grinnode.live is used. If you have access to your own node running locally you can remove the -r option completely or change it to a different http endpoint.

Example:

<pre>
./grin-wallet -r "https://grinnode.live:3413" txs

./grin-wallet -r "https://grinnode.live:3413" export_proof -i 2 proof2.txt
</pre>

Contents of proof2.txt:

{
"amount": "10123456789",
"excess": "0924ca1b69531aa9abcf85ff7a2bf0d494bc1d85440339332fb62374aabaddf1d6",
"recipient_address": "grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5",
"recipient_sig": "710d58fe9e728077dad9494c0d0e15ba5e883e863477aa471c753282a838d9c45966bc57d21f078c226576b6189b293eed3534b755674284a90bb99a128a7d02",
"sender_address": "grin1ephxt0u33rz9zpl7exer2awfr9s9ae28qsx7908q2zq03uv3sj7suqdule",
"sender_sig": "f054a71d5791532364b3267d44601531cdd6730e1eb487142ae798aa3de6e3551c4f756caec09d17901c5e6e08946f04d9d03d04af525567b6df14e25158160c"
}

The proof file is to be sent to a mediator in case of a dispute over payment not received or incorrect amount.

== Guidance for dispute agents ==

There are two steps for verifying the correct payment was made.

1) Check that the proof file supplied by the GRIN seller matches the details you have for the Bisq trade.

This is just basic fact checking, did the sender proof show the correct recipient address and amount?

Note that amounts are shown without a decimal place and there are 9 digits after the decimal

e.g. <code>"amount": "10123456789"</code> means 10.123456789 GRIN

2) Run the <code>verify_proof</code> command to check that the transaction is recorded on the blockchain.

{{Admonition_Warn|There's no reason to verify a proof if the amount or recipient is wrong.}}

=== Running the verify_proof wallet tool ===

In order to verify GRIN trades, you'll need grin-wallet installed on your PC. Install the grin wallet software from https://github.com/mimblewimble/grin-wallet/releases, and then:

<pre>
./grin-wallet -r "https://grinnode.live:3413" init
</pre>

The wallet is just used as a tool to verify transactions. You do not need a node, Tor or a seedphrase for this.
To verify, use the command <code>verify_proof</code> with the details provided by the GRIN seller, e.g.

<pre>
./grin-wallet -r "https://grinnode.live:3413" verify_proof ./proof2.txt
</pre>

Output:

<pre>
Payment proof's signatures are valid.
Neither the proof's sender nor recipient address belongs to this wallet.
Command 'verify_proof' completed successfully
</pre>

This proves that the amount was sent to recipient address shown in the proof and recorded in the GRIN ledger.

Trading GRIN

2021-11-10T00:16:35Z

Jmacxx:

'''[https://github.com/mimblewimble/grin/blob/master/doc/grin4bitcoiners.md GRIN]''' is a minimalistic, lightweight cryptocurrency, implementing the Mimblewimble protocol for a unique balance of privacy and scalability.

== Buying GRIN ==

Buying GRIN is like buying any other [[altcoin]]. It requires a [[Creating_a_payment_account#Creating_an_altcoin_account|GRIN payment account]] in Bisq. The GRIN slatepack address to be used is issued by your grin wallet.

When buying, you should keep your GRIN wallet open to receive the payment. More information about GRIN transactions can be found [https://docs.grin.mw/about-grin/transactions here].

Once you have recieved the GRIN you should confirm the Bisq trade to release BTC funds and escrow to the counterparty and yourself.

== Selling GRIN ==

The trader ''selling'' GRIN (BTC buyer) will send GRIN to the counterparty's slatepack address using their wallet of choice once the Bisq trade deposit is confirmed.

The amount and recipient address is displayed on-screen when you are prompted to do the transfer.

Example of sending using grin-wallet:
<pre>./grin-wallet -r "https://grinnode.live:3413" send -d grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5 10.123456789</pre>

The GRIN ''buyer'' will confirm the trade in Bisq once they are satisfied that they received the correct amount of GRIN.

You must be able to generate [https://docs.grin.mw/getting-started/wallet-handbook/#proof proof of payment] in case of a dispute. Otherwise, Confidential Transactions make it impossible for a third party to verify if a payment was made —
so GRIN sellers must be able to generate a transaction's proof for mediators or arbitrators in case of disputes.

{{Admonition_Warn|Failing to provide the proof to a dispute agent will likely result in losing the dispute case.}}

See below for instructions to generate payment proof.

== FAQ ==

'''How is the price of GRIN determined?'''

The price of GRIN is determined by the marketplace within Bisq.

Trade price is chosen by offer maker (which can be the buyer or seller). Offers are by default arranged in the marketplace with the best prices shown at the top of the list.

The last traded price is shown in at the top right of the screen as "Price of latest Bisq trade".

== Generate payment proof ==

The person sending the GRIN funds can create payment proof.

First, list your transactions using <code>txs</code>, look for the one you want to issue proof on.

The command <code>export_proof</code> will generate a file containing information to prove the details to the recipient or a mediator.

Example:

<pre>
./grin-wallet -r "https://grinnode.live:3413" txs

./grin-wallet -r "https://grinnode.live:3413" export_proof -i 2 proof2.txt
</pre>

Contents of proof2.txt:

{
"amount": "10123456789",
"excess": "0924ca1b69531aa9abcf85ff7a2bf0d494bc1d85440339332fb62374aabaddf1d6",
"recipient_address": "grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5",
"recipient_sig": "710d58fe9e728077dad9494c0d0e15ba5e883e863477aa471c753282a838d9c45966bc57d21f078c226576b6189b293eed3534b755674284a90bb99a128a7d02",
"sender_address": "grin1ephxt0u33rz9zpl7exer2awfr9s9ae28qsx7908q2zq03uv3sj7suqdule",
"sender_sig": "f054a71d5791532364b3267d44601531cdd6730e1eb487142ae798aa3de6e3551c4f756caec09d17901c5e6e08946f04d9d03d04af525567b6df14e25158160c"
}

The proof file is to be sent to a mediator in case of a dispute over payment not received or incorrect amount.

== Guidance for dispute agents ==

There are two steps for verifying the correct payment was made.

1) Check that the proof file supplied by the GRIN seller matches the details you have for the Bisq trade.

This is just basic fact checking, did the sender proof show the correct recipient address and amount?

Note that amounts are shown without a decimal place and there are 9 digits after the decimal

e.g. <code>"amount": "10123456789"</code> means 10.123456789 GRIN

2) Run the <code>verify_proof</code> command to check that the transaction is recorded on the blockchain.

{{Admonition_Warn|There's no reason to verify a proof if the amount or recipient is wrong.}}

=== Running the verify_proof wallet tool ===

In order to verify GRIN trades, you'll need grin-wallet installed on your PC. Install the grin wallet software from https://github.com/mimblewimble/grin-wallet/releases, and then:

<pre>
./grin-wallet -r "https://grinnode.live:3413" init
</pre>

The wallet is just used as a tool to verify transactions. You do not need a node, Tor or a seedphrase for this.
To verify, use the command <code>verify_proof</code> with the details provided by the GRIN seller, e.g.

<pre>
./grin-wallet -r "https://grinnode.live:3413" verify_proof ./proof2.txt
</pre>

Output:

<pre>
Payment proof's signatures are valid.
Neither the proof's sender nor recipient address belongs to this wallet.
Command 'verify_proof' completed successfully
</pre>

This proves that the amount was sent to recipient address shown in the proof and recorded in the GRIN ledger.

Trading GRIN

2021-11-09T23:28:03Z

Jmacxx: Created page with "'''[https://github.com/mimblewimble/grin/blob/master/doc/grin4bitcoiners.md GRIN]''' is a minimalistic, lightweight cryptocurrency, implementing the Mimblewimble protocol for..."

'''[https://github.com/mimblewimble/grin/blob/master/doc/grin4bitcoiners.md GRIN]''' is a minimalistic, lightweight cryptocurrency, implementing the Mimblewimble protocol for a unique balance of privacy and scalability.

== Buying GRIN ==

Buying GRIN is like buying any other [[altcoin]]. It requires a [[Creating_a_payment_account#Creating_an_altcoin_account|GRIN payment account]] in Bisq. The GRIN slatepack address to be used is issued by your grin wallet.

When buying, you should keep your GRIN wallet open to receive the payment. More information about GRIN transactions can be found [https://docs.grin.mw/about-grin/transactions here].

Once you have recieved the GRIN you should confirm the Bisq trade to release BTC funds and escrow to both parties.

== Selling GRIN ==

The trader ''selling'' GRIN (BTC buyer) will send GRIN to the counterparty's slatepack address using their wallet of choice once the Bisq trade deposit is confirmed.

The amount and recipient address is displayed on-screen when you are prompted to do the transfer.

Example of sending using grin-wallet:
<pre>./grin-wallet -r "https://grinnode.live:3413" send -d grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5 10.123456789</pre>

The GRIN ''buyer'' will confirm the trade in Bisq once they are satisfied that they received the correct amount of GRIN.

You must be able to generate [https://docs.grin.mw/getting-started/wallet-handbook/#proof proof of payment] in case of a dispute. Otherwise, Confidential Transactions make it impossible for a third party to verify if a payment was made —
so GRIN sellers must be able to generate a transaction's proof for mediators or arbitrators in case of disputes.

{{Admonition_Warn|Failing to provide the proof to a dispute agent will likely result in losing the dispute case.}}

See below for instructions to generate payment proof.

== FAQ ==

'''How is the price of GRIN determined?'''

The price of GRIN is determined by the marketplace within Bisq.

Trade price is chosen by offer maker (which can be the buyer or seller). Offers are by default arranged in the marketplace with the most attractive ones shown at the top of the list.

The last traded price is shown in at the top right of the screen as "Price of latest Bisq trade".

== Generate payment proof ==

The person sending the GRIN funds can create payment proof.

First, list your transactions using <code>txs</code>, look for the one you want to issue proof on.

The command <code>export_proof</code> will generate a file containing information to prove the details to the recipient or a mediator.

Example:

<pre>
./grin-wallet -r "https://grinnode.live:3413" txs

./grin-wallet -r "https://grinnode.live:3413" export_proof -i 2 proof2.txt
</pre>

Contents of proof2.txt:

{
"amount": "10123456789",
"excess": "0924ca1b69531aa9abcf85ff7a2bf0d494bc1d85440339332fb62374aabaddf1d6",
"recipient_address": "grin1dxnzk3gfnqz69va64ut7jafs7u72dtyswpzxekdgmlurkng9ctfqf9yqu5",
"recipient_sig": "710d58fe9e728077dad9494c0d0e15ba5e883e863477aa471c753282a838d9c45966bc57d21f078c226576b6189b293eed3534b755674284a90bb99a128a7d02",
"sender_address": "grin1ephxt0u33rz9zpl7exer2awfr9s9ae28qsx7908q2zq03uv3sj7suqdule",
"sender_sig": "f054a71d5791532364b3267d44601531cdd6730e1eb487142ae798aa3de6e3551c4f756caec09d17901c5e6e08946f04d9d03d04af525567b6df14e25158160c"
}

The proof file is to be sent to a mediator in case of a dispute over payment not received or incorrect amount.

== Guidance for dispute agents ==

There are two steps for verifying the correct payment was made.

1) Check that the proof file supplied by the GRIN seller matches the details you have for the Bisq trade.

This is just basic fact checking, did the sender proof show the correct recipient address and amount?

Note that amounts are shown without a decimal place and there are 9 digits after the decimal

e.g. <code>"amount": "10123456789" means 10.123456789 GRIN</code>

2) Run the <code>verify_proof</code> command to check that the transaction is recorded on the blockchain.

{{Admonition_Warn|There's no reason to verify a proof if the amount or recipient is wrong.}}

=== Running the verify_proof wallet tool ===

In order to verify GRIN trades, you'll need grin-wallet installed on your PC. Install the grin wallet software from https://github.com/mimblewimble/grin-wallet/releases, and then:

<pre>
./grin-wallet -r "https://grinnode.live:3413" init
</pre>

The wallet is just used as a tool to verify transactions. You do not need a node, Tor or a seedphrase for this.
To verify, use the command <code>verify_proof</code> with the details provided by the GRIN seller, e.g.

<pre>
./grin-wallet -r "https://grinnode.live:3413" verify_proof ./proof2.txt
</pre>

<pre>
Payment proof's signatures are valid.
Neither the proof's sender nor recipient address belongs to this wallet.
Command 'verify_proof' completed successfully
</pre>

This proves that the amount was sent to recipient address shown in the proof and recorded in the GRIN ledger.

Connecting to your own Bitcoin node

2021-10-14T03:35:32Z

Jmacxx:

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.

You can also specify the addresses of particular Bitcoin nodes in <code>Settings</code> > <code>Network Info</code>.

__TOC__

= General node settings =

Make sure the node you're looking to connect to, whether local or remote, meets the following requirements:
* Specify <code>peerbloomfilters=1</code> in <code>bitcoin.conf</code> file if running 0.19.0.1 or later
* Make sure node is ''not'' running in pruned mode (<code>pruned=N</code> in config means node is pruning blocks)

= Connecting to a local Bitcoin node =

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 <code>bitcoind</code> running on <code>localhost</code> on port 8333.

Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.

= Connecting to another Bitcoin node =

By default, Bisq maximizes your privacy by connecting to nodes run by trusted Bisq contributors.

If you'd like to connect to another node, you can specify its address in <code>Settings</code> > <code>Network Info</code>. Bisq will validate the address and connect to the specified node the next time it starts.

Bisq v1.7.4 and later releases support connecting to Bitcoin nodes with Tor v3 addresses.

= Troubleshooting =

If you get into a state where Bisq is unable to connect, you can revert to a provided node as follows.

Bisq -btcNodes=emzybtc3ewh7zihpkdvuwlgxrhzcxy2p5fvjggp7ngjbxcytxvt4rjid.onion:8333 -useTorForBtc=true

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].

[[Running_from_the_command_line|More info on running from the command line]].

[[Command_line_options|More info on command line options]].