Bisq Wiki - User contributions [en]

Fees

2026-01-13T16:20:01Z

MwithM: Redirected page to Trading costs

#REDIRECT[[Trading_costs]]

Trading fees

2025-09-06T11:23:13Z

MwithM: /* Current rates */ Cycle 73 adjustment #477

'''Trading fees''' are paid to fund the [[DAO | Bisq DAO]] when making or taking an offer. Fees can be paid in BSQ or BTC.

__TOC__

== Getting a discount ==

Bisq encourages traders to use [[BSQ]] by offering a discount of approximately 50%. This discount fluctuates as the BSQ/BTC rate fluctuates. To maintain the 50% discount target, trading fees are [[update BSQ trading fees | updated]] every cycle as necessary.

{{Admonition_Note|If you're interested in using BSQ to pay trading fees, [[Paying_trading_fees_with_BSQ#Acquire_BSQ|see this article for instructions]].}}

== Current rates ==

{| class="wikitable" style="width: 250px;"
|+ Trading Fees per 1 BTC
|-
!
!BTC
!BSQ
|-
!Maker
|0.0015
|35.79
|-
!Taker
|0.0115
|274.4
|}

Combined BTC trading fee rate is 1.3% (0.15% by maker and 1.15% by taker). Absolute minimum fee to avoid dust is 0.00005 BTC.

Combined BSQ trading fee rate is targeted at 0.65% (0.075% by maker and 0.575% by taker). Absolute minimum fee to avoid dust is 0.03 BSQ.

Trading fee rates and absolute minimums are DAO parameters that [[Proposals|must be proposed]] and approved through DAO voting in order to take effect. BTC fee rates tend to stay constant, but BSQ rates are [[Updating_BSQ_trading_fees|adjusted every cycle]] to account for BSQ rate fluctuation.

== Selecting how to pay ==

Traders choose how they'd prefer to pay trading fees while making or taking an offer. BSQ and BTC amounts (and fiat equivalents) are shown.

[[File:Pick-trade-fee-currency.png|600px|thumb|left|Pick how to pay trade fees on this screen while making or taking an offer.]]
<div style="clear: both;"></div>

[[Category:Features]]

Updating BSQ trading fees

2025-08-26T08:33:28Z

MwithM: /* Determine new BSQ fees */ substitute google for cryptpad spreadsheet

'''Updating BSQ fees''' takes place every cycle to keep the BSQ [[trading fees]] at a 50% discount to BTC trading fees.

The [[Compensation Maintainer]] takes the following steps to update BSQ trading fees.

__TOC__

== Determine new BSQ fees ==

Three days before the end of proposal phase, the [[Compensation Maintainer]] shall:

* Calculate BSQ trading fee discount [https://cryptpad.fr/sheet/#/2/sheet/view/khBDMTPxN9GkLPNYaLtyWFDmdXTnDygFeYZ--qngS1o/ on this spreadsheet] using the 30-day weighted average USD/BSQ price and live USD/BTC price at the time.
** If existing BSQ discount is under 40% or over 60%, calculate new BSQ trading fees to restore a 50% discount.
** Update spreadsheet with new proposed fees. If there is no need for an update, leave the "New Fees" section blank.

== Submit DAO parameter proposals ==

Upon calculating the new BSQ fees, the [[Compensation Maintainer]] shall:

* Create a new post on [https://github.com/bisq-network/proposals/ github proposals] with the title <code>BSQ trading fee update for Cycle X</code> indicating the new proposed trading fees and close the old post (or indicate in a comment at the already opened post if there will be no changes).
* Submit DAO change parameter proposals for new BSQ trading fees and comment the corresponding TXIDs (if necessary).

== Communicate changes ==

Once DAO results are available, the [[Compensation Maintainer]] shall:

* Update the [[trading fees]] page with new BSQ trading fees.

== Reference ==

Proposals [https://github.com/bisq-network/proposals/issues/173 #173] and [https://github.com/bisq-network/proposals/issues/365 #365] led to the development of this procedure.

[[Category:Processes]]

Downloading and installing

2025-06-28T06:28:31Z

MwithM: /* macOS */ xattr -d

To use Bisq, you must first '''[https://bisq.network/downloads/ download and install]''' it. Most exchanges are centralized exchanges running on servers controlled by the exchange. Bisq is decentralized, running only on the desktops of Bisq users.

Bisq manages offers to trade using a peer-to-peer network. This is a global network made of users who are also running Bisq on their own computers.

Centralized services are easy to monitor, block, and shut down, while peer-to-peer networks like BitTorrent, Bitcoin and Bisq are difficult to surveil, censor, shut down or hack.

All of this means that if you want to use the Bisq network, you must download and run the software on your own machine.

== Download Bisq ==

The most convenient way to install Bisq on your machine is from a pre-built install file from the [https://bisq.network/downloads/ Bisq website] or [https://github.com/bisq-network/bisq/releases/latest latest GitHub release].

There's also a community-maintained [https://snapcraft.io/bisq-desktop Snap package] for various Linux distributions.

{{Admonition_Note|See [[#OS-specific_install_notes|install notes for various Linux distributions below]].}}

You can download the installer for your operating system and install Bisq right away, but we strongly recommend that you [[ #Verify installer file | verify the integrity ]] of your installer file first.

'''If you have issues, please check the ''Known issues with installation'' section in [https://github.com/bisq-network/bisq/releases/latest release notes].'''

== Verify installer file ==

=== Bisq2 specific instructions ===

Bisq2 can be downloaded [https://bisq.network/downloads/ here]. Before installing software that manages your funds, you should always verify the installer has not been tampered with, to avoid the risk of losing funds due to a compromised download.

Usually, installation binaries are signed by Alejandro García (key ID: E222AA02, primary release manager). However, since this key has expired — and the expired key was included in previous versions of the Bisq2 app — the in-app verification process would fail when attempting to download version 2.1.2. To prevent this issue, the secondary release manager assumed responsibility for signing that release. The signingkey.asc file specifies the key used for signing the binaries.

HenrikJannsen's signing key can be downloaded [https://bisq.network/pubkey/387C8307.asc here] (full fingerprint: B8A5 D214 ADFA A387 A14C 8BCF 02AA 2BAE 387C 8307).

To import the key in Linux and MacOS:

<nowiki>curl https://bisq.network/pubkey/387C8307.asc | gpg --import </nowiki>

GPG will return "This key is not certified with a trusted signature!", this is normal (see https://serverfault.com/questions/569911/how-to-verify-an-imported-gpg-key for background information what it means)

To verify the installer against the signature:

<nowiki>gpg --digest-algo SHA256 --verify BINARY{.asc*,}</nowiki>

Replace BINARY with the name of the file you downloaded.

In Windows. you can import the key, and subsequently verify the installer, by using [https://www.gpg4win.org/download.html Kleopatra].

Any software that manages funds, signs transactions, and deals with highly sensitive data is a prime target for malware. Bisq does all three. Therefore, it is highly recommended that you verify the integrity of the installer file you use to install Bisq.

This verification is something that you should do for the initial Bisq install. After the initial install, you will be prompted to install updates through Bisq's interface. The Bisq software will verify the integrity of updates for you.

Bisq installer files are currently built and signed by Alejandro Garcia (alejandrogarcia83). His public key ID is <code>E222AA02</code> and fingerprint is <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code>, which you can verify through [https://github.com/bisq-network/bisq/commits?author=alejandrogarcia83 commits on GitHub].

The full public key is available [https://bisq.network/pubkey/E222AA02.asc here on the Bisq website].

<span id="bisq-1-obtain-signature-files-for-installer-files"></span>
= Bisq 1: Obtain signature files for installer files =

All Bisq releases are cryptographically signed by its maintainer. Users can ensure that nobody tampered with the release by verifying its signatures. It’s recommended to download the GPG key from an independent keyserver (such as [https://keys.openpgp.org/ keys.openpgp.org] or [https://keyserver.ubuntu.com/ keyserver.ubuntu.com] to ensure that no adversary replaced the GPG keys and signatures on the release server.

Bisq 1 releases are signed either by Alejandro García (alejandrogarcia83) or Gabriel Bernard (gabernard). Here are the public key ids and fingerprints of both keys:

Alejandro García (public key id <code>0xF806F422E222AA02</code>): <code>B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</code> Gabriel Bernard (public key id <code>0x6C8D14D84A133008</code>): <code>1655 3BA9 2694 95EE 53BB A33A 6C8D 14D8 4A13 3008</code>

<span id="windows"></span>
== Windows ==

<span id="download-and-install-gpg4win"></span>
=== Download and install Gpg4win ===

Windows does not come with GPG software installed by default, so you will need to install it in order to verify Bisq’s installer files. You can get Gpg4win [https://www.gpg4win.org/ here]. Double-click the installer file and proceed to install with all default settings.

<span id="import-alejandro-garcías-key"></span>
=== Import Alejandro García’s key ===

Open Kleopatra (part of Gpg4win) and click on “Lookup on Server”.

[[File:Image_1.cleaned.png]]

Next type into the search field <code>alejandro.garcia@disroot.org</code> and press on search. You’ll see the following output:

[[File:Image 2.cleaned.png]]

Press on “Details…” to see the key’s fingerprint and confirm that it is correct.

[[File:Image 3.cleaned.png]]

After verifying that the fingerprint is correct, press on “Close” and press on “Import” to import the key.

<span id="verify-the-signature-of-the-binary-you-downloaded"></span>
=== Verify the signature of the binary you downloaded ===

With the <code>install-file.exe</code> and <code>signature-file.exe.asc</code> in the same directory, double-click on the <code>.exe.asc</code> file.

You should see a Kleopatra window pop up with a green progress bar that says “Verified .exe with .exe.asc”. The program will continue to say “The data could not be verified” in bold but you can disregard that message.

This means the installer file we downloaded is intact and as intended. You can proceed to install Bisq by double-clicking the .exe file.

<span id="mac-and-linux"></span>
== Mac and Linux ==

<span id="import-alejandro-garcías-key-1"></span>
=== Import Alejandro García’s key ===

To import Alejandro García’s open a terminal and run:

<pre>gpg --receive-keys 0xF806F422E222AA02</pre>
Next you need to verify key’s fingerprint and tell GPG to trust the key. First run:

<pre>gpg --edit-key 0xF806F422E222AA02</pre>
Then type:

<pre>fpr</pre>
Now ensure that you see the same output as here:

<pre>gpg> fpr
pub rsa4096/0xF806F422E222AA02 2022-09-28 Alejandro García <alejandro.garcia@disroot.org>
Primary key fingerprint: B493 3191 06CC 3D1F 252E 19CB F806 F422 E222 AA02</pre>
If the fingerprint matches you can trust the key. To trust the key type:

<pre>trust</pre>
Now you’ll see following output:

<pre>gpg> trust
pub rsa4096/0xF806F422E222AA02
created: 2022-09-28 expires: 2026-10-03 usage: SC
trust: unknown validity: unknown
sub rsa4096/0xE7F08D07C72561D0
created: 2022-09-28 expires: 2026-10-03 usage: E
[ unknown] (1). Alejandro García <alejandro.garcia@disroot.org>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu

Your decision?</pre>
Type <code>5</code> to trust to the key and you’ll see following output:

<pre>Do you really want to set this key to ultimate trust? (y/N) </pre>
Now type <code>y</code> to confirm. Now you can quit by typing <code>quit</code>.

<span id="verify-the-signature-of-the-binary-you-downloaded-1"></span>
=== Verify the signature of the binary you downloaded ===

With the installer file and installer signature file in the same directory, run:

<pre>gpg --verify INSTALLER.asc INSTALLER</pre>
Where <code>INSTALLER.asc</code> is the filename of the <code>.asc</code> file you just downloaded.

You should see an output similar to this:

<pre>gpg: Signature made Fri 22 Nov 2024 07:42:50 PM UTC
gpg: using RSA key B493319106CC3D1F252E19CBF806F422E222AA02
gpg: checking the trustdb
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2026-10-03
gpg: Good signature from "Alejandro García <alejandro.garcia@disroot.org>" [ultimate]</pre>

== Build from source ==

[https://github.com/bisq-network/bisq/blob/master/docs/build.md Building Bisq from source] requires only a single command once you have the correct JDK installed on your machine.

Finding and installing the correct JDK can sometimes be frustrating, so Bisq's developers have written scripts to make it easier:
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.sh For Linux and macOS]
* [https://github.com/bisq-network/bisq/blob/master/scripts/install_java.bat For Windows]

== OS-specific install notes ==

=== macOS ===

Starting with version v1.9.6, we remove notarization from our build pipeline because of of the risk of Apple certification revocation (see https://github.com/bisq-network/bisq/discussions/6341). Unfortunately this will require extra steps when installing Bisq on macOS.

You will receive an error popup saying that Bisq ''is damaged and can't be opened. You should move it to the Trash''.

Please follow the guide at https://support.apple.com/en-us/HT202491 in the section ''If you want to open an app that hasn’t been notarized or is from an unidentified developer''

If you are running already macOS Ventura (13.0+) you need to do following to be able to start Bisq:
* enter following command in Apple Terminal <code>sudo xattr -d com.apple.quarantine /Applications/Bisq.app</code>
* hit enter and you will be prompted to enter your password to be able to execute the command as super user

After running this successfully you should be able to start Bisq as always.

If this procedure still does not allow you to install Bisq, a last resort workaround is to install Bisq in a Linux Virtual Machine running on your system.

=== Windows ===

Starting with version v1.9.6, we remove the developer code signing because of the same reason as with Apple.

For Windows you just have to ignore the warning after you have verified the installation file yourself and proceed with the installation.

=== Linux (General) ===

Bisq works with a number of Linux distros, but not all desktop environments are supported.

These are all known compatible desktop environments. This is a growing list. If you find another compatible desktop, please inform us so it can be added.

* GNOME
* Mate
* Xfce
* KDE Plasma
* Cinnamon

Bisq might not work properly if you switch from the original desktop environment of your Linux distribution to a different one.

Note: users with discrete GPUs may encounter issues launching Bisq in some desktop environments.

=== Arch Linux ===

The Bisq [https://bisq.network/downloads/ downloads page] includes a link to the Arch User Repository (AUR) page for the [https://aur.archlinux.org/packages/bisq/ bisq package].

# From the command line, clone the repository from AUR.
# Then from the cloned directory, run <code>makepkg -si</code>. This will read the PKGBUILD file to download, verify, build, and install the various tools necessary to install Bisq.

If the version found on AUR is not up to date, you can read [[Fix_Arch_release]].

Please be advised: when you're using AUR, you're responsible for your own safety. Be sure to verify the PKGBUILD file.

=== Gentoo ===

Use <code>eselect repository enable booboo</code> to use the 'booboo' overlay which carries the binaries, and then emerge <code>bisq</code>

=== Tails ===

Please see [[Running Bisq on Tails]] for details on downloading, installing, and configuring Bisq on Tails.

=== Qubes ===

Please see [[Running Bisq on Qubes]] for a detailed Qubes setup guide.

== Update Bisq ==

Installing a new Bisq version will update Bisq. More details at [[Updating Bisq]].

[[Category:Use Cases]]

Trading fees

2025-06-01T16:30:18Z

MwithM: /* Current rates */ #475

'''Trading fees''' are paid to fund the [[DAO | Bisq DAO]] when making or taking an offer. Fees can be paid in BSQ or BTC.

__TOC__

== Getting a discount ==

Bisq encourages traders to use [[BSQ]] by offering a discount of approximately 50%. This discount fluctuates as the BSQ/BTC rate fluctuates. To maintain the 50% discount target, trading fees are [[update BSQ trading fees | updated]] every cycle as necessary.

{{Admonition_Note|If you're interested in using BSQ to pay trading fees, [[Paying_trading_fees_with_BSQ#Acquire_BSQ|see this article for instructions]].}}

== Current rates ==

{| class="wikitable" style="width: 250px;"
|+ Trading Fees per 1 BTC
|-
!
!BTC
!BSQ
|-
!Maker
|0.0015
|43.32
|-
!Taker
|0.0115
|332.12
|}

Combined BTC trading fee rate is 1.3% (0.15% by maker and 1.15% by taker). Absolute minimum fee to avoid dust is 0.00005 BTC.

Combined BSQ trading fee rate is targeted at 0.65% (0.075% by maker and 0.575% by taker). Absolute minimum fee to avoid dust is 0.03 BSQ.

Trading fee rates and absolute minimums are DAO parameters that [[Proposals|must be proposed]] and approved through DAO voting in order to take effect. BTC fee rates tend to stay constant, but BSQ rates are [[Updating_BSQ_trading_fees|adjusted every cycle]] to account for BSQ rate fluctuation.

== Selecting how to pay ==

Traders choose how they'd prefer to pay trading fees while making or taking an offer. BSQ and BTC amounts (and fiat equivalents) are shown.

[[File:Pick-trade-fee-currency.png|600px|thumb|left|Pick how to pay trade fees on this screen while making or taking an offer.]]
<div style="clear: both;"></div>

[[Category:Features]]

Making a compensation request

2025-04-27T06:03:04Z

MwithM: /* 3. Submit your GitHub issue and address feedback */

Once you've done some work on the Bisq project, you may want to '''make a compensation request''' for BSQ.

__TOC__

== Preliminary considerations ==

=== Conventions ===

Compensation requests are generally made for work done in the current DAO cycle—work delivered after the last proposal phase and before the end of the current one—but you can make a request for work done any time in the past as long as you have records of it.

Keep in mind that compensation requests will need to garner a simple majority approval in DAO voting, and before that, team leads will do an initial review of your request. For this to go well, you won't want your compensation request to be the first interaction you have with other Bisq contributors.

Ideally, you will have already had conversations with team leads and other contributors to:
* make them aware of what you want to do
* get others' feedback on your plans
* get an idea of how valuable your contribution is to the project(so your compensation request is reasonable to you ''and'' to stakeholders)
** don't hesitate to suggest a ballpark cost before getting started, if one is not already suggested by other contributors; this helps avoid surprises and hurt feelings at compensation request time

It would be even better to have public threads (issues, pull requests, other discussion threads) tracking your work, progress, and outcomes to help stakeholders put your compensation request into perspective. This is somewhat intuitive for development-related tasks, but non-development contributors should strongly consider making issues in the appropriate repositories or forums too.

For more guidance on how you can get started contributing to Bisq, check out the [[contributor checklist]].

{{Admonition_Warn|Please try not to nickel-and-dime in your compensation request. Charging top dollar for fly-by-night code reviews and minor text corrections are usually seen as red flags, and will probably not be received very well by reviewers and voters.}}

=== Eligible work ===

Compensation requests can only be made for '''delivered work''': work that has been available to users at the time compensation for it is being requested (see [https://github.com/bisq-network/proposals/issues/19 a more elaborate explanation of this notion here]). Work that’s planned or in-progress is not eligible for compensation.

Generally, work merged to the master branch of a repository can be considered delivered (if applicable).

Reporting bugs and/or opening issues generally does not qualify as delivered work since, strictly speaking, opening an issue does not usually ''deliver'' anything. With that said, there are occasional exceptions to this, so as suggested above, please keep other contributors informed about what you're up to in order to minimize misunderstandings.

== Create your compensation request ==

Making a compensation request requires 2 steps:
# opening an issue on GitHub
# submitting the compensation request to the Bisq DAO

Issuance and voting takes place on Bisq, but metadata (e.g. compensation request details) is stored on GitHub to decrease the data storage burden on the Bisq and Bitcoin networks.

If you wish to request compensation for the current cycle, please make a compensation request issue no later than one week prior to the end of the current cycle's proposal phase. This allows time for team leads to do an initial review and offer feedback. Reminders about this deadline are sent in the [[https://github.com/bisq-network/bisq/discussions|discussions area on GitHub]] and on [[https://bisq.chat|Matrix]] in the #compensation channel.

=== 1. Open a new issue ===

[[File:Github-create-cr.png|400px|thumb|left|Opening a new compensation request issue on GitHub.]]

The issue should go in the [https://github.com/bisq-network/compensation/issues bisq-network/compensation repository], and it should be titled in the following format:

<code>For Cycle N</code>, where N is the number of the current cycle

You must stick to this convention in order for the compensation request parsing bot to properly parse your request.

{{Admonition_Note|Compensation requests are assumed to be ready for review as soon as they're created. If you would prefer to delay review of your request, preface your issue's title with <code>[WIP]</code> so that people (and bots) know to ignore it. Then, when your request is ready for review, just remove <code>[WIP]</code> from the issue title.}}

=== 2. List your work in the issue ===

Compensation requests must be made in a very particular format in order for them to be valid. This is because a bot is used to parse requests to automatically aggregate work done for reporting and budgeting.

The placeholder text of the issue you just opened tells you everything you need to know.
* In the "Summary" section, fill out all the numbers in brackets ('''required''')
* In the "Contributions Delivered" section, list your contributions as rows in the table ('''required''')
* In the "Contributions in Progress" section, list contributions you're expecting to deliver in future cycles

==== Tips on making a convincing request ====

The onus is on '''you''' to convince Bisq stakeholders what you did, how much it’s worth, and why it’s valuable. Voters will be evaluating what you put in this GitHub issue to determine whether or not you should be issued the BSQ you're asking for.

In order to make your case as strong as possible, make sure to:
* Include as many links to issues, pull requests, and other "evidence" for any work you want to be compensated for
* Comments that help explain what the work is, why it is valuable, etc.
* Links to role reports, if you hold any roles in the Bisq network

As mentioned above, this is a big reason that it’s important that everything you do for Bisq be as public, documented, and verifiable as possible, and that everything you do has positive consensus with multiple stakeholders so you know you’re not wasting your time.

Even then, not all stakeholders will be familiar with your work, so it’s important to be as thorough as you can when making a compensation request so there’s enough context for those unfamiliar with your work to make an informed vote.

Feel free to check out [https://github.com/bisq-network/compensation/issues?q=is%3Aissue+is%3Aclosed old compensation requests] if you're unsure about anything.

==== Tips on valuing your work ====

Valuing work is a judgment call. There's no precise way to go about valuing your work, but here are some pointers:
* work should be valued based on the value of the contribution you made, not on the raw time you spent on it
* if you are unsure about the value of your contribution, consider what you would charge for your work if you did it as a freelancer

Ideally, especially if you're a new contributor, consider discussing compensation for particular tasks you're working on with another contributor who's been around longer to see if your expectations align with theirs. You can also browse older requests for examples of what people in the past were paid for similar work.

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

== 3. Submit your GitHub issue and address feedback ==

Upon submitting your compensation request issue (or removing <code>[WIP]</code> from the title), a bot will parse it to evaluate formatting. If it's not valid, the bot will add a <code>parsed:invalid</code> label to the issue and leave a comment with a reason. Please edit your issue until the bot adds a <code>parsed:valid</code> label. If the bot does not work and it does not produce any label, continue normally.

You may receive feedback from other contributors that needs to be addressed. After waiting for a prudential time, you can submit your request to the Bisq DAO.

== 4. Submit your request as a DAO proposal ==

Once a team lead has given you the go-ahead, it's time to submit your request to the DAO.

In Bisq, go to <code>DAO</code> > <code>Governance</code> > <code>Make Proposal</code>.

[[File:Dao-cr.png|600px|thumb|left|Submitting a compensation request to the DAO.]]

# Select "Compensation request" in the dropdown menu
# Specify your GitHub handle, exactly like it is on GitHub
# Replace the <code>#</code> with the number of your GitHub issue (for example, if your compensation request’s GitHub URL is https://github.com/bisq-network/compensation/issues/999, the URL in your DAO compensation request should be https://bisq.network/dao-compensation/999. Don’t copy the GitHub link directly—it won’t work!)
# Specify the amount of BSQ you're requesting

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

{{Admonition_Note|Bisq may not use GitHub forever. But the Bitcoin blockchain is forever, and proposal URLs cannot be changed—the Bitcoin transaction corresponding to a Bisq DAO proposal includes a hash of the proposal’s data object, which includes the proposal URL. This is why Bisq proposals require a URL with a domain name that Bisq controls: if proposal data ever needs to be migrated, the links can remain the same.}}

When you’re ready, click <code>Make proposal</code> to confirm your proposal for voting in the current cycle. '''Proposal data cannot be edited, so make sure everything is correct.'''

== 5. Add a comment to your GitHub compensation request with your BSQ transaction ID ==

To ensure that someone else is not claiming for your contributions we ask that you post your BSQ transaction ID as a comment on the GitHub issue.

You can access your BSQ transaction ID for the compensation request in the Bisq application by visiting DAO > BSQ Wallet > Transactions

Please copy your transaction ID and paste it as comment on your GitHub issue thus linking Bisq compensation request with the GitHub issue.

=== Fees and other costs ===

A compensation request is a type of proposal, and proposals cost a fee to make in the Bisq DAO. Currently that fee is 2 BSQ. Since a compensation request is intended to issue new BSQ, you’ll also need to include a small amount of bitcoin to be colored into BSQ if your proposal is accepted—100 satoshis × [requested BSQ amount]. See more details in the [[DAO_user_reference#Proposal_Phase|User Reference]].

Also remember that Bisq DAO proposals are Bitcoin transactions, so it costs mining fees and takes time for them to be confirmed. Consider watching mining fees to broadcast your proposal at a reasonable cost. Waiting until late in the proposal phase to submit may cause it to not be confirmed in time.

{{Admonition_Note|If you need to make a change, you can delete the proposal and make a new one while the proposal phase is still active, but you’ll need to pay the proposal fee again. Once the proposal phase is over, proposals cannot be added or removed until the next proposal phase.}}

The BSQ and BTC is automatically added to your proposal transaction by Bisq, but the BTC needs to be in your Bisq BTC wallet at the time you submit your proposal. Keep in mind that you’ll also need some BSQ and BTC for the other phases (vote & vote reveal).

When you successfully submit your proposal in the DAO, it’ll propagate across the Bisq peer-to-peer network and be ready for stakeholders to vote on in the voting phase. If your request is approved, you will see the BSQ you requested in your wallet after the voting phase is over.

Making a compensation request

2025-04-27T06:02:27Z

MwithM: /* 3. Submit your GitHub issue and address feedback */ bot not working, team lead review

Once you've done some work on the Bisq project, you may want to '''make a compensation request''' for BSQ.

__TOC__

== Preliminary considerations ==

=== Conventions ===

Compensation requests are generally made for work done in the current DAO cycle—work delivered after the last proposal phase and before the end of the current one—but you can make a request for work done any time in the past as long as you have records of it.

Keep in mind that compensation requests will need to garner a simple majority approval in DAO voting, and before that, team leads will do an initial review of your request. For this to go well, you won't want your compensation request to be the first interaction you have with other Bisq contributors.

Ideally, you will have already had conversations with team leads and other contributors to:
* make them aware of what you want to do
* get others' feedback on your plans
* get an idea of how valuable your contribution is to the project(so your compensation request is reasonable to you ''and'' to stakeholders)
** don't hesitate to suggest a ballpark cost before getting started, if one is not already suggested by other contributors; this helps avoid surprises and hurt feelings at compensation request time

It would be even better to have public threads (issues, pull requests, other discussion threads) tracking your work, progress, and outcomes to help stakeholders put your compensation request into perspective. This is somewhat intuitive for development-related tasks, but non-development contributors should strongly consider making issues in the appropriate repositories or forums too.

For more guidance on how you can get started contributing to Bisq, check out the [[contributor checklist]].

{{Admonition_Warn|Please try not to nickel-and-dime in your compensation request. Charging top dollar for fly-by-night code reviews and minor text corrections are usually seen as red flags, and will probably not be received very well by reviewers and voters.}}

=== Eligible work ===

Compensation requests can only be made for '''delivered work''': work that has been available to users at the time compensation for it is being requested (see [https://github.com/bisq-network/proposals/issues/19 a more elaborate explanation of this notion here]). Work that’s planned or in-progress is not eligible for compensation.

Generally, work merged to the master branch of a repository can be considered delivered (if applicable).

Reporting bugs and/or opening issues generally does not qualify as delivered work since, strictly speaking, opening an issue does not usually ''deliver'' anything. With that said, there are occasional exceptions to this, so as suggested above, please keep other contributors informed about what you're up to in order to minimize misunderstandings.

== Create your compensation request ==

Making a compensation request requires 2 steps:
# opening an issue on GitHub
# submitting the compensation request to the Bisq DAO

Issuance and voting takes place on Bisq, but metadata (e.g. compensation request details) is stored on GitHub to decrease the data storage burden on the Bisq and Bitcoin networks.

If you wish to request compensation for the current cycle, please make a compensation request issue no later than one week prior to the end of the current cycle's proposal phase. This allows time for team leads to do an initial review and offer feedback. Reminders about this deadline are sent in the [[https://github.com/bisq-network/bisq/discussions|discussions area on GitHub]] and on [[https://bisq.chat|Matrix]] in the #compensation channel.

=== 1. Open a new issue ===

[[File:Github-create-cr.png|400px|thumb|left|Opening a new compensation request issue on GitHub.]]

The issue should go in the [https://github.com/bisq-network/compensation/issues bisq-network/compensation repository], and it should be titled in the following format:

<code>For Cycle N</code>, where N is the number of the current cycle

You must stick to this convention in order for the compensation request parsing bot to properly parse your request.

{{Admonition_Note|Compensation requests are assumed to be ready for review as soon as they're created. If you would prefer to delay review of your request, preface your issue's title with <code>[WIP]</code> so that people (and bots) know to ignore it. Then, when your request is ready for review, just remove <code>[WIP]</code> from the issue title.}}

=== 2. List your work in the issue ===

Compensation requests must be made in a very particular format in order for them to be valid. This is because a bot is used to parse requests to automatically aggregate work done for reporting and budgeting.

The placeholder text of the issue you just opened tells you everything you need to know.
* In the "Summary" section, fill out all the numbers in brackets ('''required''')
* In the "Contributions Delivered" section, list your contributions as rows in the table ('''required''')
* In the "Contributions in Progress" section, list contributions you're expecting to deliver in future cycles

==== Tips on making a convincing request ====

The onus is on '''you''' to convince Bisq stakeholders what you did, how much it’s worth, and why it’s valuable. Voters will be evaluating what you put in this GitHub issue to determine whether or not you should be issued the BSQ you're asking for.

In order to make your case as strong as possible, make sure to:
* Include as many links to issues, pull requests, and other "evidence" for any work you want to be compensated for
* Comments that help explain what the work is, why it is valuable, etc.
* Links to role reports, if you hold any roles in the Bisq network

As mentioned above, this is a big reason that it’s important that everything you do for Bisq be as public, documented, and verifiable as possible, and that everything you do has positive consensus with multiple stakeholders so you know you’re not wasting your time.

Even then, not all stakeholders will be familiar with your work, so it’s important to be as thorough as you can when making a compensation request so there’s enough context for those unfamiliar with your work to make an informed vote.

Feel free to check out [https://github.com/bisq-network/compensation/issues?q=is%3Aissue+is%3Aclosed old compensation requests] if you're unsure about anything.

==== Tips on valuing your work ====

Valuing work is a judgment call. There's no precise way to go about valuing your work, but here are some pointers:
* work should be valued based on the value of the contribution you made, not on the raw time you spent on it
* if you are unsure about the value of your contribution, consider what you would charge for your work if you did it as a freelancer

Ideally, especially if you're a new contributor, consider discussing compensation for particular tasks you're working on with another contributor who's been around longer to see if your expectations align with theirs. You can also browse older requests for examples of what people in the past were paid for similar work.

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

== 3. Submit your GitHub issue and address feedback ==

Upon submitting your compensation request issue (or removing <code>[WIP]</code> from the title), a bot will parse it to evaluate formatting. If it's not valid, the bot will add a <code>parsed:invalid</code> label to the issue and leave a comment with a reason. Please edit your issue until the bot adds a <code>parsed:valid</code> label. If the bot does not work, continue normally.

You may receive feedback from other contributors that needs to be addressed. After waiting for a prudential time, you can submit your request to the Bisq DAO.

== 4. Submit your request as a DAO proposal ==

Once a team lead has given you the go-ahead, it's time to submit your request to the DAO.

In Bisq, go to <code>DAO</code> > <code>Governance</code> > <code>Make Proposal</code>.

[[File:Dao-cr.png|600px|thumb|left|Submitting a compensation request to the DAO.]]

# Select "Compensation request" in the dropdown menu
# Specify your GitHub handle, exactly like it is on GitHub
# Replace the <code>#</code> with the number of your GitHub issue (for example, if your compensation request’s GitHub URL is https://github.com/bisq-network/compensation/issues/999, the URL in your DAO compensation request should be https://bisq.network/dao-compensation/999. Don’t copy the GitHub link directly—it won’t work!)
# Specify the amount of BSQ you're requesting

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

{{Admonition_Note|Bisq may not use GitHub forever. But the Bitcoin blockchain is forever, and proposal URLs cannot be changed—the Bitcoin transaction corresponding to a Bisq DAO proposal includes a hash of the proposal’s data object, which includes the proposal URL. This is why Bisq proposals require a URL with a domain name that Bisq controls: if proposal data ever needs to be migrated, the links can remain the same.}}

When you’re ready, click <code>Make proposal</code> to confirm your proposal for voting in the current cycle. '''Proposal data cannot be edited, so make sure everything is correct.'''

== 5. Add a comment to your GitHub compensation request with your BSQ transaction ID ==

To ensure that someone else is not claiming for your contributions we ask that you post your BSQ transaction ID as a comment on the GitHub issue.

You can access your BSQ transaction ID for the compensation request in the Bisq application by visiting DAO > BSQ Wallet > Transactions

Please copy your transaction ID and paste it as comment on your GitHub issue thus linking Bisq compensation request with the GitHub issue.

=== Fees and other costs ===

A compensation request is a type of proposal, and proposals cost a fee to make in the Bisq DAO. Currently that fee is 2 BSQ. Since a compensation request is intended to issue new BSQ, you’ll also need to include a small amount of bitcoin to be colored into BSQ if your proposal is accepted—100 satoshis × [requested BSQ amount]. See more details in the [[DAO_user_reference#Proposal_Phase|User Reference]].

Also remember that Bisq DAO proposals are Bitcoin transactions, so it costs mining fees and takes time for them to be confirmed. Consider watching mining fees to broadcast your proposal at a reasonable cost. Waiting until late in the proposal phase to submit may cause it to not be confirmed in time.

{{Admonition_Note|If you need to make a change, you can delete the proposal and make a new one while the proposal phase is still active, but you’ll need to pay the proposal fee again. Once the proposal phase is over, proposals cannot be added or removed until the next proposal phase.}}

The BSQ and BTC is automatically added to your proposal transaction by Bisq, but the BTC needs to be in your Bisq BTC wallet at the time you submit your proposal. Keep in mind that you’ll also need some BSQ and BTC for the other phases (vote & vote reveal).

When you successfully submit your proposal in the DAO, it’ll propagate across the Bisq peer-to-peer network and be ready for stakeholders to vote on in the voting phase. If your request is approved, you will see the BSQ you requested in your wallet after the voting phase is over.

Restoring application data

2025-04-10T06:42:38Z

MwithM: /* Restore wallet */ Link to Create_a_new_wallet_for_your_data_directory

'''Restoring application data''' can be useful to bring back payment accounts, onion addresses, and other items from a [[Backing_up_application_data|backup]]—or to move your Bisq instance to an entirely new machine.

You can restore an entire data directory at once, or just the parts you want.

__TOC__

= Restore an entire data directory =

First make sure Bisq is closed. Then copy the entire <code>Bisq</code> directory from your backup and paste it in your machine's [[Data_directory#Default_Locations|default data directory location]]. If there already is a directory called <code>Bisq</code> there, remove it (or rename it) and replace it with your backup.

Data directories work across operating systems, so you can copy a data directory created on a Mac to the appropriate location on Linux or Windows, and it will work.

Please '''do not''' run the same data directory on 2 machines at the same time, even if you don't run both instances at the same time, as data may get corrupted in strange ways.

= Restore payment accounts =

A [[Backing_up_application_data#Back_up_payment_accounts|payment account export]] only contains metadata (name, bank information, etc). For fiat accounts, this means that restoring payment accounts is a 2-step process.

== Restore payment account metadata ==

If you have a payment accounts export file, import it in <code>Account</code> > <code>National Currency Accounts</code>.

If you don't have an export file, but you do have a full backup, you can salvage your payment account metadata from <code>btc_mainnet/db/UserPayload</code> by running the <code>strings</code> utility on the <code>UserPayload</code> file (e.g., run <code>strings /path/to/backup/btc_mainnet/db/UserPayload</code> in a terminal window). The command will output a simplified version of the <code>UserPayload</code> file to your terminal. Scroll up a bit and you should see your payment account information.

Use the output to copy and paste the details into new payment accounts in Bisq, paying special attention to make sure each field is copied over with 100% accuracy (including the salt): even a 1 character difference in any field will cause the hash of the payment account to be different, which means aging and signing status will not be restored in the following step.

There are quirks. Here's an example of output from a <code>strings</code> command:

SEPA
Alice Liddell
DE89370400440532013000
DEUTDE5X*
SKzH
salt
@56655c3738ea9dea3b20f482fff048985a2757e57dff206fbd9e8c4f267f7781

From the output above:
* Be wary of extra characters at the beginning or end of a line. In the example above, the <code>*</code> character is not part of the BIC "DEUTDE5X".
* Salts are alphanumeric, so the <code>@</code> is not part of the salt "56655c3738ea9dea3b20f482fff048985a2757e57dff206fbd9e8c4f267f7781".

If you're on Windows, or cannot use the <code>strings</code> utility for some other reason, you can just open <code>UserPayload</code> directly in a text editor, but there will be more cruft to sift through since the file isn't meant to be human-readable.

It may be tempting to just replace the entire <code>UserPayload</code> file from a backup, but this is '''not recommended''', as it may contain other data that could result in data corruption in your new instance.

== Restore payment account aging and signing status ==

Once you've restored your payment account metadata, you'll see the accounts in Bisq, but they'll have no aging or signing status.

You can get aging and signing status back by replacing <code>btc_mainnet/keys/sig.key</code> from your backup.
# Make sure you have no active offers, trades or disputes; once you change <code>sig.key</code>, you will become unreachable.
# Close Bisq. Also make sure you've made a [[Backing_up_application_data|backup of your data directory]] (just in case).
# Replace <code>/path/to/data/directory/btc_mainnet/keys/sig.key</code> with the <code>sig.key</code> from your backup.

Upon opening Bisq, you should see account aging and signing status restored for your fiat payment accounts.

If you don't, double-check:
* You copied account metadata and salt correctly [[#Restore_payment_account_metadata|in the previous step]].
* The <code>sig.key</code> you copied is the correct one (i.e., the one you were using when your accounts accrued aging and/or got signed)

= Restore onion address =

Your onion address determines your [[local reputation]], so depending on your preferences, you may want to reset it or restore it over time.

If you want to restore it:
* Close Bisq. Also make sure you've made a [[Backing_up_application_data|backup of your data directory]] (just in case).
* Replace the <code>/path/to/data/directory/btc_mainnet/tor/hiddenservices/</code> folder with the <code>btc_mainnet/tor/hiddenservices/</code> folder from your backup.

When you open Bisq, your onion address will be restored.

This means that the peers that have traded with you will see [[Local_reputation|bubbles with trade counts]] in their offer books for ''your'' offers.

= Restore trade history =

You may want to keep your trade history despite changing wallets. You can do so by:
* Closing Bisq.
* Replacing the <code>/path/to/data/directory/btc_mainnet/db/ClosedTrades</code> file on your new directory with the file from backup with the same name.

You will see [[Local_reputation|bubbles with trade counts]] in the offer books for any any peers you traded with.

= Restore wallet =

It's good to start with a [[Create_a_new_wallet_for_your_data_directory|clean wallet]] every so often, because Bisq wallets use the bitcoinj library, which causes wallet files to get increasingly larger with every transaction. Wallet corruption becomes increasingly likely and performance suffers (e.g. long startup times). If starting a new data directory, it's generally best to just send funds from one Bisq instance to another with an on-chain transaction.

Trading fees

2025-02-25T23:06:45Z

MwithM: /* Current rates */ Update as per proposal #472

'''Trading fees''' are paid to fund the [[DAO | Bisq DAO]] when making or taking an offer. Fees can be paid in BSQ or BTC.

__TOC__

== Getting a discount ==

Bisq encourages traders to use [[BSQ]] by offering a discount of approximately 50%. This discount fluctuates as the BSQ/BTC rate fluctuates. To maintain the 50% discount target, trading fees are [[update BSQ trading fees | updated]] every cycle as necessary.

{{Admonition_Note|If you're interested in using BSQ to pay trading fees, [[Paying_trading_fees_with_BSQ#Acquire_BSQ|see this article for instructions]].}}

== Current rates ==

{| class="wikitable" style="width: 250px;"
|+ Trading Fees per 1 BTC
|-
!
!BTC
!BSQ
|-
!Maker
|0.0015
|33.94
|-
!Taker
|0.0115
|260.17
|}

Combined BTC trading fee rate is 1.3% (0.15% by maker and 1.15% by taker). Absolute minimum fee to avoid dust is 0.00005 BTC.

Combined BSQ trading fee rate is targeted at 0.65% (0.075% by maker and 0.575% by taker). Absolute minimum fee to avoid dust is 0.03 BSQ.

Trading fee rates and absolute minimums are DAO parameters that [[Proposals|must be proposed]] and approved through DAO voting in order to take effect. BTC fee rates tend to stay constant, but BSQ rates are [[Updating_BSQ_trading_fees|adjusted every cycle]] to account for BSQ rate fluctuation.

== Selecting how to pay ==

Traders choose how they'd prefer to pay trading fees while making or taking an offer. BSQ and BTC amounts (and fiat equivalents) are shown.

[[File:Pick-trade-fee-currency.png|600px|thumb|left|Pick how to pay trade fees on this screen while making or taking an offer.]]
<div style="clear: both;"></div>

[[Category:Features]]

File:Payment-account-signing-status.png

2025-02-18T16:58:31Z

MwithM: MwithM reverted File:Payment-account-signing-status.png to an old version