Bisq Wiki - User contributions [en]

Trading rules

2026-04-15T12:30:19Z

SuddenWhipVapor: /* Do not confirm payments with mismatching details */ requirement to open mediation when payment details don't match

Both Bisq traders must follow these '''trading rules''' to ensure smooth and successful trades.

To trade on Bisq, you assume one of two roles, no matter what national currency or cryptocurrency you’re trading: you either ''buy bitcoin'' or ''sell bitcoin''.

The rules below are '''default''' rules for every transaction. Offer makers sometimes specify their own additional terms for handling payments. For example, a seller using cash deposits might require a picture of a receipt torn in half with "NO REFUND" written on it. Face-to-face traders often specify terms about where and how to meet.

Make sure you’re okay with an offer-maker’s terms '''before''' you accept an offer!

Trade rules also help with the following:

* Promoting good behavior from traders
* Penalizing bad behavior from traders
* Promoting good payment accounts of traders
* Penalizing bad payment accounts of traders
* Put the 'wrong doer' in a worse position and the person 'not at fault' in a better position

= Common rules =

=== Match Bisq account details with real data ===

The data you enter during fiat account creation in Bisq must match with the real data associated to the fiat account (for example, but not limited to, filling in your full account holder name instead of placing just your initials).

=== No requirement to reply in trader chat ===

While using the available trade chat can be helpful to resolve issues directly among traders without the overhead of mediation, and being communicative is a good way to ease the process for new traders, there is no obligation to reply to a peer's messages.

=== Do not communicate with your peer away from Bisq ===

Using email addresses, phone numbers, and other means to contact traders is strongly discouraged. The trader chat feature built into Bisq should be used instead: not only is it more private, but the chat record can more easily be made available to mediators and arbitrators (useful in case a trader’s chat messages indicate they broke a rule). This includes advertising offers to sell BTC with a way to contact you, for example a website, Telegram user name, or email.

In any case, it is forbidden to contact the peer using contacts obtained from their payment details, without their prior consent, or missing a compelling reason to do so.

=== Be responsive during a dispute ===

Traders are expected to reply within 48hrs to either mediators or arbitrators, and could lose the dispute based on unresponsiveness.

Mediators may take up to 48 hours to respond to messages, and arbitrators may take up to 5 days to respond to messages.

=== Do not change payment details once trade is in progress ===

Once the deposit transaction is published, the trade is in progress, and its terms cannot be changed. Traders agreed to use the payment details specified in the trade contract.

In the event of an unexpected circumstance (e.g. hitting a bank-imposed transfer limit, or a payment institution interfering with the transaction), traders can propose alternatives through trader chat or mediation, but the peer is not required to comply. It is each trader's responsibility to ensure that the payment account in their offer will work before an offer is taken.

= Rules for bitcoin sellers =

Whether making or taking an offer, bitcoin sellers put all the bitcoin they’re selling in the multisig escrow, so there’s less for them to do and fewer rules they need to follow.

=== Click <code>Confirm payment</code> after receiving payment ===

Sellers have until the end of the maximum trade period to do so.

[[Account_limits#Account_signing|Account signing]], introduced in Bisq v1.2, enables a seller with a signed payment account to sign a buyer’s payment account when they successfully receive a payment. For such trades, it is recommended that the seller take as long as possible (i.e., wait until close to the end of the trade period) to confirm receipt of payment to reduce the chance of a chargeback.

=== Do not confirm payments with mismatching details ===

Payer name, account numbers, payment method, institution, and other details of a payment should match the details in the trade contract. If there are any concerns that buyer's payment details do not match (e.g. wrong name, account number etc) mediation should be opened immediately, using the key combination <code>Ctrl-O</code> while on the trade panel.'''

{{Admonition_Warn|This is especially relevant for trades in which a signed seller trades with an unsigned buyer, because confirmation of payment receipt signs the buyer’s payment account. In case of such an issue, a dispute should be opened.}}

= Rules for bitcoin buyers =

{{Admonition_Warn|To avoid unexpected issues, make sure you can actually carry out a payment with the payment method you’ve set up in Bisq. Examples: Wells Fargo doesn’t allow cash deposits into bank accounts not owned by the depositor, and Zelle has weekly and monthly transfer maximums that are easy to overlook. The software will warn you about known issues, but cannot possibly keep up with all the newest banking and money transfer rules.}}

=== Make payment reasonably early within trade period ===

Buyer should complete at a time such that the seller has enough time to acknowledge receipt of the payment before the trade period is over. Waiting until the very end of the trade period to make a payment is not advised, as then the seller cannot reasonably act in time to acknowledge receipt (also, it’s annoying). The lengths of trade periods vary based on [[Payment methods|payment method]].

This is especially important for buyers with unsigned payment accounts trading with sellers with signed payment accounts. A seller will not want to confirm receipt of a payment made at the last minute from an untrusted account, so if you’re a buyer looking to get your payment account signed, you should make the payment ''as soon as possible''.

Some payment methods include an option to cancel a payment after you have sent it eg Revolut and Interac e-Transfer. If you cancel payment without agreement with the seller or mediator you might end up being penalized for cancelling the trade.

=== Click Payment started after sending payment ===

Seller cannot mark payment as received until buyer confirms that they have sent it.

Don’t forget to do this!

=== Leave the "reason for payment" field empty ===

{{Admonition_Warn|Before 1.5.5, it was required to put the trade ID in the 'reason for payment' field of a payment. As of 1.5.5, reason for payment should be left BLANK.}}

Some payments offer a way to specify a reason for payment (some payment methods call it "Message" or "Information for recipient" or similar). '''Leave this field BLANK.''' Do not put the trade ID, any mentions of "Bisq" or "Bitcoin" or "crypto", or any other text whatsoever.

If you are required to fill in a reason, use your account name eg "Joe Bloggs" alternatively enter something non-descriptive like a dash "-". If you would prefer to use other text please agree this with your peer in trader chat. Please remember your peer is not obligated to agree anything and may not want to agree to anything other than leaving the description blank, your name or a dash.

Violating this rule will likely result in a [[Table of penalties|trade penalty]].

Many banks don’t like anything related to Bitcoin, and may take draconian measures if they sense such a transaction.

Many users trade from personal accounts and may object to using anything that looks like it could be a commercial transaction.

=== Pay any transaction fees ===

Any fees incurred to make the payment via the agreed payment method (e.g., bank fees for bank transfer, money-order fees for money orders, etc) are the buyer’s responsibility to pay.

The seller should receive the exact amount of the trade. The only exception to this rule is if the receiving institution imposes a fee on incoming payments—these fees are borne by the seller.

= What happens when things go wrong? =

Sometimes trades do not go to plan for whatever reason.

It is prudent for all traders to know when entering into the trade what will happen when things go wrong. Traders would be wise to make themselves aware of the [[dispute resolution]] process to ensure there are no surprises.

Bisq 2 mobile applications

2026-04-11T16:53:26Z

SuddenWhipVapor: SuddenWhipVapor moved page Bisq 2 mobile to Bisq 2 mobile applications: more appropriate and descriptive

The mobile ecosystem of Bisq 2 allows access to the [[Bisq Easy]] protocol from a smartphone, via two applications:

* Bisq Easy Mobile (Android only)
* Bisq Connect (Android and iOS)

== Bisq Easy Mobile ==

Bisq Easy Mobile is a full Bisq Easy node running on your Android device. It features the complete p2p network stack and connects with its own onion address.

It provides the same privacy and security as the Bisq 2 desktop application.

It is primarily suited for buyers who:
* want to buy their first sats
* prefer not to use a desktop computer

Pros:
* Runs a full Bisq Easy node
* Does not require a separate device

Cons:
* Available for Android only
* Higher battery, bandwidth, and resource usage
* App may lose connectivity when moved to background, and reconnection can take time
* No synchronization or interoperability with a desktop instance
* Users must manually manage backups

== Bisq Connect ==

Bisq Connect is a lightweight companion app that allows you to remotely access and control a Bisq 2 node running elsewhere.

It is available for both Android and iOS (via TestFlight).

Instead of running a node locally, the app connects to a backend node, which can be:

* your own Bisq 2 desktop application
* a Bisq 2 node running on a headless machine or VPS
* a node operated by a trusted third party

The mobile app acts as a remote interface, allowing you to monitor and manage your node from your phone.

Features:
* Pairing via QR code
* Real-time market data
* Push notifications
* Private P2P messaging
* Built-in Tor support
* Open-source and auditable

Pros:
* Available on both Android and iOS
* Low resource and battery usage
* Seamless access to the same data across devices when self-hosted
* No need for mobile backups (data is stored on the backend node)
* Mobile app can be closed without affecting node operation

Cons:
* Requires a running backend node
* Using a third-party node requires trust in the operator, as all data is hosted on that node

== Notes ==

On iOS, Bisq Connect is currently distributed via Apple TestFlight and requires iOS 16.0 or higher.

TestFlight builds expire after 90 days, but updates are released regularly.

== Future Development ==

Bisq Easy Mobile will not support the upcoming MuSig protocol.

Bisq Connect is the likely platform for supporting new protocols, depending on development priorities and user demand.

Bisq 2 mobile

2026-04-11T16:53:26Z

SuddenWhipVapor: SuddenWhipVapor moved page Bisq 2 mobile to Bisq 2 mobile applications: more appropriate and descriptive

#REDIRECT [[Bisq 2 mobile applications]]

Bisq 2 mobile applications

2026-04-11T16:52:04Z

SuddenWhipVapor: Rework

MuSig-tradelimits

2026-04-09T07:58:00Z

SuddenWhipVapor: Include limit simulator reference

== Why are trade limits necessary? ==

Most fiat payment methods carry a risk of bank chargebacks.
To reduce this risk, Bisq applies both trade amount limits and trade rate limits to Bitcoin buyers, since buyers are the ones who could initiate a chargeback.

=== Fiat trades – Bitcoin buyers ===

Trade limits depend on:

* The chargeback risk of the selected payment method
* Whether the buyer has imported a signed account age witness from Bisq 1
* The age of the payment account

=== Fiat trades – Bitcoin sellers ===

For sellers, trade limits depend only on the selected payment method.

=== Cryptocurrency trades ===

A maximum trade amount limit equivalent to 10,000 USD applies.

== How are trade limits applied? ==

Trade limits are calculated based on these rules:

* Each fiat payment method has a chargeback risk level. Depending on that level, the maximum trade amount of 10,000 USD can be reduced by up to 50%.
* If a user imports a previously signed Bisq 1 account, all limits are removed.
* If a payment account is older than 90 days, limits are removed. For newer accounts, limits increase gradually until reaching that age.

=== Trade rate limit ===

The trade rate limit (number of trades allowed per day) is based on the trade amount limit:

* It is calculated as: trade amount limit ÷ 1,000
* The minimum value is 1 trade per day
* Once the maximum trade amount limit is reached, the trade rate limit no longer applies

You can import accounts from Bisq 1 and keep their account age.

== Trade limit calculator ==

Use the simulator to see which limits apply to you based on:

* Your selected payment method
* The age of your payment account
* Whether you have imported a signed Bisq 1 account

MuSig-tradelimits

2026-04-09T07:52:31Z

SuddenWhipVapor: Substasntial stub

MuSig-tradelimits

2026-04-08T08:17:09Z

SuddenWhipVapor: First stub

== WIP ==

Setting a higher limit for trade amounts is an effective way to reduce security risk when dealing with new users.

Bisq Easy

2026-03-19T20:38:36Z

SuddenWhipVapor: /* Trade Rules */ updated payment reason rule

Bisq Easy is a trade protocol for Bisq 2, designed to facilitate the acquisition of bitcoin with zero trade fees and without the requirement of a security deposit. Bisq Easy is a social trade protocol intended for novice bitcoin buyers seeking a non-KYC option and aiming to be efficiently onboarded by experienced and knowledgeable sellers that are familiar with the Bisq platform.

Bisq Easy is currently the only trade protocol for [[Bisq 2]]. More [[Trade_Protocols|trade protocols]] are planned for the future.

== Bisq Easy Trade Protocol Specifics ==

=== Trade fees ===

There are no trade fees for buyers or sellers for trading on Bisq Easy.

=== Mining fees ===

Buyers will not have to pay any mining fees when they trade on Bisq Easy.

Sellers will need to pay any fees required to send the bitcoin to the buyer after receiving their payment. For on chain transactions the seller is responsible for paying mining fees needed to send the bitcoin to the buyer's waller. For lighting transactions the seller is responsible for paying any routing fees needed to pay the buyer's ln invoice.

=== Security mechanisms ===

The security of the trade is proportional to the reputation of the seller.

As Bisq Easy is [[reputation based]], and reputation provides a fairly low security model, it means traders on Bisq Easy are suited only to rather small amounts of bitcoin.

By default buyers can only exchange messages with sellers that have a certain level of reputation, however, buyers can opt-out from that protection.

Trading with sellers without reputation, or very low reputation, carries significant risks and should be only done if the risks are well understood and managed.

=== Currencies / Payment Methods ===

Bisq Easy buyers and sellers can trade bitcoin for any type of fiat.

Fiat buyers and sellers can choose whatever type of payment method they agree upon for fiat transfer.

=== Dispute mechanisms ===

Buyers and sellers trading on Bisq Easy can access mediation support should anything go wrong with their trade.

Mediators will be able to:

* Help facilitate the successful completion of the trade
* Confirm fiat / altcoin and bitcoin payments
* Help cancel trade if needed
* Report a trader who severely violated the trade rules to the moderator who can ban the user.

Depending on the form of reputation used, a fraudulent seller can get their bonded BSQ confiscated by the DAO or their Bisq 1 onion address banned. As all reputation is linked to the user profile, a banned user profile disables their reputation.

=== Security deposit requirements ===

Bisq Easy trades do not require any security deposits from either the buyer or seller.

=== Privacy benefits / trade-offs ===

As no security deposits are required buyers and sellers using fiat will be revealing their bank account details to users that might end up backing out of the trade. If a user backs out of a trade there is less possibility to penalize them than if they had to trade using a security deposit. The seller can report a buyer who cancelled the trade after the payment account data has been transmitted to the moderator, who can ban the buyer.

== Identity ==

Buyers and sellers on Bisq Easy can create multiple identities.

Find out more about managing your [[Identity]] on Bisq 2.

== Reputation ==

The security mechanism of Bisq Easy is based on the reputation of the seller. Buyers on Bisq Easy do not need to have a reputation as they will always send the payment first.

Find out more about [[Reputation]] for Bisq Easy.

== Using Bisq Easy to buy bitcoin ==

Users of Bisq Easy can buy bitcoin using fiat or altcoins with no fees and no security deposits.

== Using Bisq Easy to sell bitcoin ==

Users of Bisq Easy can sell bitcoin for fiat or altcoins with no fees and no security deposits.

Sellers of Bisq Easy will however have to build up their [[reputation]] in order to get buyers.

== How to buy bitcoin on Bisq Easy ==

Buying Bitcoin with Bisq Easy is recommended for small fiat amounts, or as a starting point if you still have no Bitcoin that you can use for the security deposits of other trade protocols.

You can opt for two ways to find a trading partner to get some Bitcoin: taking an existing offer or creating one.

=== Creating an offer ===
Creating an offer is a great way to establish your own terms and simply wait for someone to match what you are after. It is also the right option if you don't find any offers with the right premium or payment methods in the market you want to trade in. Follow along to learn how to navigate to your preferred market and create a new offer in it:

Begin by opening up Bisq 2. Once the application has started, you should select ''Bisq Easy'' on the left panel, and ''Offerbook'' on the top tab.

[[File:Create buy offers screenshot 1.png|frameless]]

Each different national currency has its own market. You can click on the displayed pair to open a selector where you can choose the currency you would like to trade in. In this example, we are interested in buying some Bitcoin by paying with Euros, so we will select the ''BTC/EUR'' pair, but you should select whatever currency you are using. Afterward, click on the ''Create offer'' button on the right-hand side.

[[File:Create buy offers screenshot 2.png|frameless]]

You will now enter the offer creation wizard. The first step will be to choose between buying or selling Bitcoin. Select ''Buy Bitcoin'' and click on ''Next''.

[[File:Create buy offers screenshot 3.png|frameless]]

On the following screen, you will be asked for confirmation on which currency you want to pay your Bitcoin with. The selected currency will be the one you selected in the previous ''Offerbook'' screen. You can change your mind here if needed. Since for this example we want to move forward with Euros, we don't need to change anything on this screen, and we can simply click ''Next''.

[[File:Create buy offers screenshot 4.png|frameless]]

On the next screen, you will have to select which Payment Methods are you willing to use. You should select at least one, but you can also select multiple of them. The more Payment Methods you add, the more chances you will have of finding a willing trade peer. In this example, we initially select ''SEPA'' and ''Revolut''.

[[File:Create buy offers screenshot 5.png|frameless]]

Besides the presented Payment Methods, you can also add customized Payment Methods to your offer. For instance, for this offer, I would be happy to make a cash deposit at a Rabobank physical branch. I can use the bottom input to add this method to my offer.

[[File:Create buy offers screenshot 6.png|frameless]]

Once you are done selecting Payment Methods, you can move on by clicking ''Next''.

On the next screen, you will have to set how much Bitcoin you want to buy or, putting it the other way around, how much fiat currency you want to sell. The minimum trade amount on Bisq easy is the equivalent of 6 USD and the maximum amount is {{MaxBisqEasyTrade}}. You can write the fiat amount, the BTC amount, or simply move the slider around.

[[File:Create buy offers screenshot 9.png|frameless]]

You also have the option of defining a range instead of a fixed value for the trade amount. By doing that, you set a minimum and maximum amount, and you signal to the market that you are willing to trade any amount between those two numbers. For this example, we will create an offer with a range between 100€ and 200€. Once you have set your fixed value or a range, click ''Next'' to move on.

[[File:Create buy offers screenshot 10.png|frameless]]

With this, you will reach the final step of the offer creation wizard. The final screen shows a summary of all the details you have defined. Now is the time for you to review whether everything is fine. This is important because, once you click on ''Create offer'', the offer will be available for anyone to take and, once that happens, it will be binding. So, make sure you are happy with the details you see. Once you are sure, click on ''Create offer'' and your offer will be added to the market.

[[File:Create buy offers screenshot 11.png|frameless]]

Your order is finally ready. Now, you will have to wait until another peer takes it. If your offer remains unpicked for longer than you would like to, consider modifying it to add additional payment methods or adding a more flexible range of values that could attract different users.

[[File:Create buy offers screenshot 12.png|frameless]]

Once a peer takes your offer, you will receive a notification and be able to see the started trade in the ''Open Trades'' panel of Bisq Easy. Also, keep in mind that offers remain open until you close them. If you only want to transact once, you should close it after it gets taken, or more peers could keep taking it!

=== Taking an offer ===

Taking an existing offer is the fastest and simplest way to find a partner and start trading. Follow along to learn how to navigate to your preferred market and pick an existing offer in it.

Begin by opening up Bisq 2. Once the application has started, you should select ''Bisq Easy'' on the left panel, and ''Getting started'' on the top tab.

[[File:Taking offer to buy 1.png|frameless]]

On this page, click on the ''Start trade wizard''. This is the easiest way to get started. A small note: once you become more experienced, you might prefer to use the ''Offerbook'' page to do your trades. But for the first trades, we advise using the trade wizard.

[[File:Taking offer to buy 2.png|frameless]]

With this, you will enter the trade wizard, which will guide you step by step through the process of taking an existing offer to buy some Bitcoin. In the first screen, select ''Buy Bitcoin'' and click on ''Next''.

[[File:Taking offer to buy 3.png|frameless]]

In the following screen, you need to indicate which national currency you want to use to pay your trading partner. Since we want to use Euros for this trade, we select that currency in the list. Once you have selected your currency, click on ''Next'' to move on.

[[File:Taking offer to buy 4.png|frameless]]

On the next screen, you will have to select which Payment Methods you are willing to use. You should select at least one, but you can also select multiple of them. The more Payment Methods you add, the more chances you will have of finding a willing trade peer. In this example, we initially select ''SEPA'' and ''Revolut''.

[[File:Create buy offers screenshot 5.png|frameless]]

Once you are done selecting Payment Methods, you can move on by clicking ''Next''.

On the next screen, you will have to set how much Bitcoin you want to buy or, putting it the other way around, how much fiat currency you want to sell. The minimum trade amount on Bisq Easy is the equivalent of 6 USD and the maximum amount is {{MaxBisqEasyTrade}}. You can write the fiat amount, the BTC amount, or simply move the slider around.

[[File:Taking offer to buy 5.png|frameless]]

For this example, let's imagine we would like to buy 150€ worth of Bitcoin. We set the value and click on ''Next'' to move on.

In the following screen, you will be presented a list of offers that match your needs. You can select any of the offers presented, but we advise taking the first offer. By default, offers will be presented by decreasing reputation, so the most trusted trades will be on the top of the list. You can check other offers that might have more interesting prices, but be aware that the lower the reputation of the trader, the higher the risk you will face. If you want to keep things safe and simple, simply pick the first offer that you see. Once you have settled for an offer, click on ''Next'' to move on.

[[File:Taking offer to buy 6.png|frameless]]

The final screen will allow you to review all the details. Make sure you are happy with all the details of the trade, since once you move on, you will effectively commit to doing the trade. If there's anything you want to change, you can always navigate back and modify any of the trade details. Once you are ready, click on ''Confirm trade''.

[[File:Taking offer to buy 7.png|frameless]]

Once you have done this, the offer is taken and you can begin the trade process. You can read more about the trade process here: [[Bisq_Easy#Trade_Process|Trade Process]].

Remember that when you take an offer, you commit to follow through. Be aware that, once you take it, you can't simply back down without consequences.

Note that there is also a chance that no offers are found matching your needs. If this is the case, you will see a screen like the one below. You can wait some time and try again later, or you can instead create your own offer. You can read more about creating an offer here [[Bisq_Easy#Bisq_Easy#Creating_an_offer|Creating a buy offer]].

[[File:Taking offer to buy 8.png|frameless]]

== How to sell bitcoin on Bisq Easy ==

Users of Bisq Easy can both make an offer to sell bitcoin, or take an offer from a user looking to buy bitcoin.

Seller's on Bisq Easy will usually be experienced Bisq users. It is expected they will be helpful and supportive to buyers who are new to Bitcoin and/or Bisq. Bisq Easy seller's should be passionate about helping new Bisq users smoothly acquire no KYC bitcoin in a peer to peer manner.

As building reputation incurs costs for the bitcoin sellers. It is expected that they will sell bitcoin at a premium of about 10-15%. The premium reflects the additional costs and compensates sellers for the on-boarding service they provide.

== Trade Process ==

Trade process for Bisq Easy is as follows:

* The offer maker defines the trade terms, if this was not already defined in the maker's user profile.
* Once the traders have agreed on the trade terms (e.g. payment method and trade price) the trade starts.
* The seller transmits the payment account details to the buyer (e.g. bank account number). The buyer sends the BTC address to the seller.
* The buyer starts the Fiat payment to the seller's account and sends the seller a message that the payment is in transit.
* Once the seller has received the Fiat payment they send the Bitcoin to the buyer's address.
* After the buyer receives the Bitcoin the trade is completed.

== Trade Rules ==

Bisq Easy trading rules are as follows:

* Before the payment details are exchanged the trade can be canceled by any party without justification.
* After the payment details are exchanged, not fulfilling the trade obligations is considered a breach of the trade contract and can lead to getting banned from the network.
* When sending the Fiat, the buyer MUST leave the payment reason field blank, or, if that is not possible, fill it with their own name, and MUST NOT use any term related to 'Bitcoin', 'Bisq' or 'Trade'.
* If the trade cannot be completed instantly because the Fiat transfer takes longer, both traders have to be online at least once a day to follow up the trade process.
* If there are any open questions or problems the traders can use the support chat, invite a mediator into their trade chat or get in touch with Bisq support team on the [[Matrix_bisq.chat|Matrix channel]].

== Chat Rules ==

Bisq Easy has the following chat rules it expects traders to follow:

* Be respectful: Always treat others with kindness and respect. Avoid offensive language, personal attacks, and harassment. Remember that behind every screen is a real person with feelings.
* No spamming: Please refrain from flooding the chat with repetitive or irrelevant messages. Keeping the conversation meaningful and on-topic helps everyone engage in a more constructive manner.
* No advertising: We kindly ask you to avoid promoting products, services, or posting external links. This ensures that the focus remains on meaningful discussions rather than promotional content.
* No hate speech: We have zero tolerance for content that promotes discrimination, hate speech, or violence against any individual or group. Let's foster an inclusive and supportive community.
* No trolling: Disruptive behavior, trolling, or intentionally provoking others disrupts the positive atmosphere we aim to maintain. Let's all strive for respectful and constructive interactions.
* Keep it safe: Protect your privacy and that of others by not sharing personal information such as phone numbers, addresses or any other sensitive data in the chat. Safety first!
* Respect privacy: Do not share private conversations or screenshots without consent. Respecting each other's privacy is a cornerstone of trust.
* Report misconduct: If you witness any violations of these rules or encounter inappropriate behavior, please report it to the moderator. Your vigilance helps maintain a friendly and safe community.
* Follow moderator's Instructions: Our moderators are here to ensure a positive environment. Please comply with any instructions or guidelines they provide to maintain order and respect.
* Enjoy the chat: Above all, we encourage you to engage in meaningful discussions, make friends, and have fun in a positive and inclusive environment. Let's create a community we can all be proud to be a part of.

Remember, by participating in the chat, you agree to abide by these rules. Failure to comply may result in warnings, temporary mute, or ban from the Bisq network.

== How to stay safe on Bisq Easy ==

Here are some tips for keeping safe when trading on Bisq Easy and avoiding any scams.

=== Tips for bitcoin buyers ===

Bitcoin buyers send the fiat payment before sending any bitcoin. For this reason they should take steps to ensure their trades are successful.

# Start with a small amount as a test trade
# Start chatting with the seller before sending the fiat payment to check that they are still active
# Choose a seller with a high reputation. The higher the reputation of the seller the better. Sellers need a minimum reputation score of 30,000, ideally you should be choosing to trade with someone higher than this. Look at the star system for guidance. It will be safer to trade with a 5 star rated seller than a 1 star rated seller.
# Send payment as soon as possible once you have the seller's account details.
# Only send payment to the account details provided by the Seller in the trade chat window. If the seller is trying to change the account they want you to send payment to, it would be better to cancel the trade and open a new trade with another seller.
# Place the trade ID from Bisq Easy in the payment reason.
# Send the payment from the same account you share the information with in trader chat. For example if you are having problems with the payment do not send payment from your partners, business, friends etc account. Instead try and resolve the issue so you can send payment from the correct account and failing that open mediation to get additional support.
# Keep the trade chat limited to using Bisq 2. Do not communicate with the seller via WhatsApp, Matrix etc as it will make mediation much harder if there is an issue.
# Avoid trading off platform with any Bisq sellers.

=== Tips for bitcoin sellers ===

Although bitcoin buyers send the fiat payment before bitcoin sellers send them any bitcoin, sellers should still be aware of buyers attempting any charge-back scams. There is almost no cost for a bitcoin buyer to create an account and start making trades, therefore, there is little for a buyer to lose by attempting a scam. Almost all buyers on Bisq Easy will be honest but it is still good to be cautious.

For this reason they should take steps to ensure their trades are successful.

# Be careful when dealing with buyers with brand new accounts (the buyer's account age is shown in their profile).
# Avoid payment methods that have a high possibility of charge-backs eg; PayPal, Venmo
# Make sure the payment you receive matches the buyers account details. Avoid sending bitcoin to buyer's with mis-matching account details. It would be better to refund the payment to the account you received the payment from and cancel the trade.
# Keep the trade chat limited to using Bisq 2. Do not communicate with the buyer via WhatsApp, Matrix etc as it will make mediation much harder if there is an issue.
# Avoid trading off platform with any Bisq sellers.
# If you have any concerns about a trade open mediation.

Cash by mail

2026-03-06T11:03:31Z

SuddenWhipVapor: additional measures

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

{{Admonition_Note|You might want to use a PO Box and a name which is not your real one, instead of registering an account to your own house under your real identity.}}

= 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:

* follow any special requirements and conditions set by the seller
* package cash in a tamper-evident cash bag
* place tamper-evident cash bag inside a parcel. AVOID using an envelope where a postal worker would be able to feel a wad of cash as this can lead to stolen cash
* 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 packaging addressed the same in case the outer one gets ripped open or damaged by water
* seal all packages well, with tape
* 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
* if it's available, consider using a courier service that has appropriate insurance in place for any issues with delivery (i.e. USPS Registered Mail, insuring packages up to $50,000)

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

Additional measures to ensure safer trades:

* to help prove package integrity before and after shipping, both parties should ideally also take high-definition photos, or preferably a video, when handing the package to or collecting it from the postal office, this helps verify whether the package remains in the same condition as during preparation
* packaging should be as inconspicuous as possible, a flat envelope can reveal likely contents and invite theft, while using a hollowed paperback book or another ordinary object can better conceal the cash

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

Verse

2026-02-17T11:23:59Z

SuddenWhipVapor: notice about Verse having been discontinued.

{{Admonition_Note|'''Verse has been DISCONTINUED as a service. This article has been kept for historical purposes, but the link from [[Payment methods]] has been removed.'''}}

'''Verse''' is a payment method added in Bisq v1.7.5.

Verse is a mobile payment app based in Europe owned by Square. Users can pay and request money from your friends. Payments are immediate and free. It is easy to use.

Verse is multi currency, easy to use and payments are instant and free.

Verse is designed for small payments between friends and family members. Fiat money you receive is stored in your Verse balance. From there you can send it to your friends’ digital wallets. When you want that money to be in your real world wallet, all you have to do is transfer it to your bank account. Withdrawals from Verse (sending to own account) take anywhere from a few seconds to two business days.

Verse allows users to:

* Send money to their contacts listed in the contacts list on their mobile device.
* Request money from their contacts listed in the contacts list on their mobile device.
* Receive and withdraw payments made by other Users that have your mobile phone number saved in their contacts list.
* Payments via Verse card (if they have one)
* Withdraw cash using Verse card via ATM network (if they have one)

Money can be added by debit / credit card. Verse accepts VISA and MasterCard. Withdrawals are made to your linked debit / credit card.

Why
Verse is like the European Cash App. It is multi currency, easy to use and payments are instant and free.

== Where can I find out more about Verse? ==

Here is a list of Verse resources:

* [https://verse.me/ Verse website]
* [https://twitter.com/joinverse/ Verse Twitter]
* [https://verse.me/en/terms Verse T&Cs]
* [https://verse.me/en/faq/ Verse FAQs]

== What countries are available for Verse? ==

Verse operates in the following countries: Austria, Belgium, Denmark, Finland, France, Germany, Greece, Ireland, Italy, Poland, Portugal, Slovakia, Spain, Sweden, and The Netherlands.

== What currencies are available for Verse? ==

Verse supports the following currencies; EUR, SEK, HUF, DKK, PLN

You can change between currencies in the your Verse account. Your default currency is decided by your phone number's country code. You can switch currencies every time you make a payment (the currency menu is right above the amount you are paying) and the change will be made immediately.

There are no commissions when changing of currency, the current exchange rate (Visa mid-market) will be applied.

== What is the maximum trading duration for Verse? ==

The maximum trade time is 1 day. Generally Verse transfers will be completed instantly.

Users making withdrawals from Verse (sending funds to their bank account) should expect to wait anywhere from a few seconds to two business days (it depends on their bank).

== What is the maximum BTC limit for an Verse trade? ==

{{MaxTradeSizeBisq1}}.

== Is Verse a payment method that can be signed? ==

No, Verse accounts do not require signing.

== How do I set up a Verse account? ==

Get the app from https://verse.me

== How do I add Verse as a payment method in Bisq? ==

It is easy to add your Verse account to Bisq.

# Go to the top menu in Bisq and select Account.
# Then select National Currency Accounts.
# Click add new account
# Select Verse
# Complete the details
# Choose to use a custom account name this helps makes it easier for you to manage multiple payment methods in Bisq (this will be visible only to you, for example: Verse - Jan Janssen)
# Click save new account

To send payment to someone you need there verse user name (similar to [[Revolut]], it is created for you based on first and last name, some users have the option to change their username).

If you have more than one Verse account you wish to add to Bisq you can create different accounts for each.

Make sure all the details are correct when you add.

{{Admonition_Warn|Verse is a multiple currency payment method that can send and receive payment in EUR, SEK, HUF, DKK, PLN.

When setting up your Verse account in Bisq please make sure to include the username that matches your username in your Verse account. This will ensure that when you send funds they show from the correct account and when you receive funds they will be credited to your account.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== How do I buy BTC with my Verse account? ==

You can buy BTC with Verse on Bisq in 2 waysː

# Make an offer to buy BTC on the EUR, SEK, HUF, DKK, or PLN market.
# Take an offer to buy BTC on the EUR, SEK, HUF, DKK, or PLN market.

When the offer is confirmed Bisq will provide you with the BTC Sellers Verse details for you to complete the payment. You should send payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC Seller receives your payment they will confirm in Bisq and your security deposit and your purchased trade amount will be available in your wallet.

{{Admonition_Warn|Please send payment only to the username provided by the BTC Seller in their Bisq account. Please leave the payment description blank.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== How do I sell BTC with my Verse account? ==

You can sell BTC with Verse on Bisq in 2 waysː

# Make an offer to sell BTC on the EUR, SEK, HUF, DKK, or PLN market.
# Take an offer to sell BTC on the EUR, SEK, HUF, DKK, or PLN market.

When the offer is confirmed Bisq will provide with the BTC Buyer with your Verse details for you to complete the payment. They should send payment at their first opportunity and confirm they have done so in Bisq by clicking 'payment started'.

Once you receive payment from the BTC Buyer you should confirm payment has been received in Bisq. One you have done this the BTC Buyer will receive their funds and you will receive your security deposit back.

{{Admonition_Warn|BTC Sellers should expect to receive payment from the username shown in the BTC Buyer's Bisq account.

Verse users are limited to sending or receiving €10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. This can be increased by Verse on request.}}

== Are there any limits for me to be aware of when using my Verse account? ==

€10,000 per year (or equivalent foreign currency amount) for accumulated payments made from or received into their payment account. Can be increased on request.

== Are there any fees for me to be aware of when using my Verse account? ==

Free. For payment operations that involve currency conversion and currency exchange services, the exchange rate will be calculated based on the currency sale or purchase rates, as applicable, by Visa International

== How does dispute resolution when trading with Verse? ==

If a dispute occurs the mediator may ask the buyer to send them information showing that they made the payment of the correct amount to the BTC Seller within the correct time frame.

The mediator may ask the seller to send them information to prove their account details are correct, or in the case of the BTC Buyer making a payment late, or of the wrong amount.

For more information see [[dispute resolution]].

Payment methods

2026-02-17T11:21:01Z

SuddenWhipVapor: /* Fiat payment methods */ removed Verse, as it is discontinued

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

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding trade limits and account signing, primarily apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

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 have limitations that require Bisq [[Bisq 1|v1]] to employ special measures like lower per-trade limits and [[Account_limits#Account_signing|account signing]] to encourage fair trades.

__TOC__

== Fiat payment methods ==

Fiat payment methods vary significantly in characteristics like chargeback risk, regional availability, transaction limits, fees, privacy, and verification speed. The primary consideration for supporting a method on Bisq is '''chargeback risk'''. Methods with easy chargebacks (like PayPal, Venmo, Cash App) are generally not supported.

Suggestions for new payment methods, especially those enabling new markets, are welcome. See the criteria and process for adding methods [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here on GitHub], or discuss them on [https://bisq.chat Matrix] in the #payment-methods channel.

Below is a list of fiat payment methods currently supported in Bisq v1.

'''Note on Signing Requirement:''' Methods marked with an asterisk (*) '''do not''' require [[Account_limits#Account_signing|account signing]] to lift the initial low buying limit. All other listed fiat methods generally require signing.

'''Note on Trade Limits:''' The maximum trade sizes listed below may not be available immediately for new payment accounts. Please refer to [[Account_limits]] for details on account aging and signing required to enable larger trade sizes.

{| class="wikitable sortable"
|+ Supported Fiat Payment Methods (Bisq v1)
|-
! Payment Method [* = Signing Not Required] !! Region !! Trading Period !! Per-Trade Limit (BTC) !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.0625 ||
|-
| Advanced Cash* || Global (BRL, EUR, GBP, KZT, RUB, UAH, USD) || 1 day || 0.5 || Not available in the USA.
|-
| Alipay* || China || 1 day || 0.25 ||
|-
| [[Amazon_eGift_card|Amazon eGift Card]]* || Global (AUD, CAD, EUR, GBP, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.0625 || Check supported markets in [[Amazon_eGift_card|article]].
|-
| Australian PayID* || Australia || 1 day || 0.25 ||
|-
| [[Bizum]]* || Spain|| 1 day || 0.02 || Bizum limits: ~1000 EUR/trade, ~2000 EUR/day.
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.0625 ||
|-
| [[Cash by Mail]]* || Global || 8 days || 0.0625 || Follow [[Cash_by_Mail|instructions carefully]].
|-
| Cash Deposit* || Global || 4 days || 0.0625 || Check if payee bank allows 3rd party deposits.
|-
| [[CelPay]]* || Global (AUD, CAD, GBP, HKD, USD) || 1 day || 0.0625 || CelPay limit: ~$2,500/day.
|-
| Domestic Wire Transfer* || USA || 3 days || 0.0625 ||
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 0.25 || See [[Face-to-face_(payment_method)|F2F article]] for guidance.
|-
| [[Faster Payments]]* || UK || 1 day || 0.0625 || See [[Faster_Payments|article]] for usage notes.
|-
| [[Faster_Payments_System_SBP|Faster Payments System (SBP)]]* || Russia || 1 day || 0.05 ||
|-
| HalCash* || Spain || 1 day || 0.25 ||
|-
| [[IMPS]]* || India || 1 day || 0.0625 || IMPS limit: ~1,000,000 INR/day.
|-
| Interac-e-Transfer || Canada || 1 day || 0.0625 || Interac Autodeposit is '''not''' supported.
|-
| Japan Zengin Furikomi* || Japan || 1 day || 0.25 ||
|-
| MercadoPago || Argentina || 1 day || 0.0625 ||
|-
| [[Monese]]* || Europe (GBP, EUR, RON) || 1 day || 0.0625 ||
|-
| MoneyBeam (N26) || Europe || 1 day || 0.0625 ||
|-
| MoneyGram* || Global || 4 days || 0.125 ||
|-
| National Bank Transfer || Global || 4 days || 0.0625 ||
|-
| [[Nequi]]*|| Colombia || 1 day || 0.0625 || Nequi limit: ~7,000,000 COP/month.
|-
| [[NEFT]]* || India || 1 day || 0.10 || NEFT limit: ~50,000 INR/transaction.
|-
| [[Paxum]]* || Global || 1 day || 0.0625 ||
|-
| [[Paysera]]* || Global || 1 day || 0.0625 ||
|-
| [[PayTM]]* || India || 1 day || 0.0250 || PayTM limit: ~100,000 INR/transaction.
|-
| Perfect Money* || Global || 1 day || 0.25 ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.0625 ||
|-
| Popmoney || USA || 1 day || 0.0625 ||
|-
| PromptPay* || Thailand || 1 day || 0.25 ||
|-
| [[Revolut]] || Global || 1 day || 0.0625 || See [[Revolut|article]] for usage notes.
|-
| [[RTGS]]* || India || 1 day || 0.10 || RTGS limits: Min 200,000 INR, Max 1,000,000 INR/transaction.
|-
| [[Satispay]]* || Italy || 1 day || 0.0625 ||
|-
| [[SEPA]] || Europe || 6 days || 0.0625 ||
|-
| [[SEPA Instant]] || Europe || 1 day || 0.0625 ||
|-
| [[Strike]]* || USA || 1 day || 0.0625 || Non-KYC Strike users have lower limits.
|-
| [[SWIFT]]* || Global || 7 days || 0.125 ||
|-
| Swish* || Sweden || 1 day || 0.25 ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || 0.0250 || Tikkie limit: ~2500 EUR/24 hours.
|-
| Transfer with Same Bank || Global || 2 days || 0.0625 ||
|-
| Transfer from Specific Banks || Global || 4 days || 0.0625 ||
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.0625 || USPS limits: Max 1000 USD/order, check daily limits.
|-
| Uphold || Global || 1 day || 0.0625 ||
|-
| [[UPI]]* || India || 1 day || 0.0250 || UPI limit: ~100,000 INR/transaction.
|-
| WeChat Pay* || China || 1 day || 0.25 ||
|-
| Western Union || Global || 4 days || 0.125 ||
|-
| [[Wise]]* || Global ('''non-USD''' trades) || 4 days || 0.0625 ||
|-
| [[Wise-USD]]* || Global ('''USD''' trades) || 4 days || 0.0625 ||
|-
| [[Zelle]] || USA || 4 days || 0.0625 || Check your bank's Zelle support & limits.
|}
=== Payment method guides ===

<gallery mode="packed" heights="150px">
File:Payment-methods-advice-eur.png|EUR payment methods overview.
File:Payment-methods-advice-usd.png|USD payment methods overview.
</gallery>

== Altcoin payment methods ==

Bisq also supports trading Bitcoin against various cryptocurrencies, like XMR, ETH, ZEC, L-BTC or LTC. A full list is available on the [https://bisq.network/markets/ Bisq Network Markets page].

Because cryptocurrency transfers are generally irreversible and fast, altcoin trades usually have higher limits (up to 0.5 BTC) available immediately, without the need for account aging or signing required for many fiat methods.

{| class="wikitable"
|+ Supported Altcoin Payment Methods (Bisq v1)
|-
! Payment Method !! Trading Period !! Per-Trade Limit (BTC)
|-
| [[Altcoins]] || 1 day || 0.5
|-
| [[Altcoins Instant]] || 1 hour || 0.5
|}

'''Warning for Instant Trades:''' Altcoins Instant trades require quick confirmation (within 1 hour). Remember to disable any open Instant offers (via `Portfolio` > `My Open Offers`) if you might be unavailable to complete the trade promptly.

See the general Account setup process within Bisq for adding altcoin accounts.

[[Category:Features]]
</translate>

Account limits

2026-02-12T12:24:13Z

SuddenWhipVapor: /* With your own signed account */

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.5 BTC right away, but all fiat payment account types have limits lower than 0.5 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.5 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

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

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

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

==== With your own signed account ====

Once you have a signed and fully matured payment account, any new payment account you create after it, that requires signing, will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Backup

2025-12-14T18:22:15Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Built-in automatic backup ==

Bisq2 extends the existing manual backup, and also provides a feature to create versioned backups: [[automatic backup]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:21:44Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Built-in automatic backup ==

Bisq2 extends the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:21:06Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner.

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:20:32Z

SuddenWhipVapor:

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]

Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Backup

2025-12-14T18:20:01Z

SuddenWhipVapor: stump

= Backup strategies=

== Manual backup ==

Bisq1 has a manually triggered backup feature that saves a copy of the whole contents of the data directory to a selected location: [[backing up application data]]
Bisq2 has a very similar feature that can be reached under Support > Resources > Backup, and works in a similar manner

== Builtin automatic backup ==

Bisq2 builds on top of the existing manual backup, and also provides a feature to create versioned backups: [[automatic backups]]

== Custom automatic backup scripts ==

A standalone script is also available to create versioned backups on Windows, MacOS and Linux, of the essential database files of both Bisq1 and Bisq2: [[automatic backup script]]

Automatic backup

2025-12-14T18:07:41Z

SuddenWhipVapor: add screenshot

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.
[[File:Resources automatic backup.png|thumb]]

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

File:Resources automatic backup.png

2025-12-14T18:06:46Z

SuddenWhipVapor:

automatic backup & retention system page

Automatic backup

2025-12-14T18:04:02Z

SuddenWhipVapor: fix title format

=== Bisq2 automatic backup & retention system ===

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute\n\
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

Automatic backup

2025-12-14T18:03:15Z

SuddenWhipVapor: Stump created

= Bisq2 automatic backup & retention system =

The Bisq application automatically creates a backup whenever a data storage file is updated. Recent backups are retained more densely, while older ones are gradually thinned out. This approach maintains a good balance between storage usage and ensuring that sufficiently recent backups are available when needed.

Backup snapshots are created on every write (the backup filename is the store filename plus the timestamp format <code>yyyy-MM-dd_HHmm</code>) and are grouped by the store’s parent filename.

The system keeps backup snapshots based on the following rules and the <code>MaxBackupSize</code> (default 100MB):

*Last hour: a snapshot every minute\n\
*Past hour → 24 hours: the most recent snapshot from each hour is kept
*Past day → 7 days: the most recent snapshot from each day is kept
*Past week → 28 days: the most recent snapshot from each week is kept
*Past month → 1 year: the most recent snapshot from each month is kept
*Older than a year: the most recent snapshot from each year is kept

Finding your arbitrator

2025-11-11T09:15:59Z

SuddenWhipVapor: /* Matrix and onion addresses */ updated RA2 matrix handle

Here is a list of current Bisq arbitrators and their onion addresses, as well as how you can find the arbitrator for a specific Bisq trade.

If you need to find your mediator see [[Finding your mediator|here]].

__TOC__

= Get in touch with your arbitrator =

For open trades, you should be able to get in touch with your arbitrator through Bisq arbitration chat itself.

If you cannot get in touch with your arbitrator on Bisq for 72 hours (sometimes Bisq message system fails), or the issue needs urgent attention, you can get in touch with them on the [[Matrix bisq.chat]] group. Their Matrix handles and onion addresses are displayed in the headline for the #support channel as well.

= How to find the arbitrator for a trade =

== In Bisq 1 ==

=== System message ===

Go to 'Support > Arbitration' tab since arbitration begins.

=== View contract in JSON ===

Alternatively, you can look for your arbitrator since the trade starts:

# Go to <code>Portfolio > Open Trades</code>, <code>Portfolio > History</code>, or <code>Portfolio > Failed Trades</code> (depending on the status of your trade)
# Click the <code>i</code> icon next to the trade ID of the trade in question (it's on the very left in the first column)
# In the pop-up that appears, toward the bottom, click <code>View Contract in JSON Format</code>.
# Scroll down and you'll find <code>"refundAgentNodeAddress"</code> it is just below <code>"lockTime"</code> after the refundAgentNodeAddress you will see your arbitrators's onion address.

This is the onion address of the arbitrator for your trade.

= Matrix and onion addresses =

{| class="wikitable"
! Arbitrator
! TorV3 Address
! GitHub Handle
! Matrix Handle
|-
| refundagent2
| 3z5jnirlccgxzoxc6zwkcgwj66bugvqplzf6z2iyd5oxifiaorhnanqd.onion:9999
| [https://github.com/refund-agent2 refund-agent2]
| [[Matrix bisq.chat | @refund-agent2:envs.net]]
|-
| refundagent3
| yjlcxr6rho6zkpecwdp3vlpduzcl7i6cbgaquvxqmvsbw3dnheus6qad.onion:9999
| [https://github.com/refundagent3 refundagent3]
| [[Matrix bisq.chat | @refundagent3:imagisphe.re]]
|}

[[Category:Use Cases]]

Account limits

2025-11-07T12:57:30Z

SuddenWhipVapor: /* How to get an account signed */ better wording

Elevated '''account limits''' apply to fiat payment accounts in order to limit damage a malicious user can do while allowing honest users to start trading immediately with no KYC and utmost privacy.

Altcoin accounts can trade 0.5 BTC right away, but all fiat payment account types have limits lower than 0.5 BTC to match their particular risk profiles (see [[Payment_methods#Fiat_payment_methods|this table]] for details). Some payment methods with chargeback risk implement a mechanism called ''account signing'' that restricts trading activity until a trader proves their integrity to further secure against foul play.

To reduce the size of trades entering arbitration Bisq also sets new users trade limits to be 0.1 BTC. This is an additional limit to account limits but users can opt out of this limit at any time.

__TOC__

== Which payment accounts are affected ==

Only fiat payment methods are affected by elevated account limits. Altcoin accounts are only affected by the new user limits which can be opted out if necessary for allow every altcoin account to trade up to 0.5 BTC right away upon creating a payment account in Bisq.

All fiat payment methods in all markets limit total trade size depending on the payment method's risk profile (see [[Payment_methods#Fiat_payment_methods|this table]] for details).

Despite these limitations, chargebacks can still be possible for certain payment methods. Bisq reduces this risk with a mechanism called '''account signing'''.

Account signing only applies to payment accounts that meet ''both'' of the following conditions:
* used in the following markets: USD, EUR, CAD, GBP, AUD, or BRL
* is subject to chargeback risk: SEPA, SEPA Instant, Interac e-Transfer, Zelle, Revolut, Chase QuickPay, Popmoney, MoneyBeam, Uphold, and any kind of bank transfer

This means that all payment accounts that deal in currencies not listed above do ''not'' require account signing, even if they are subject to chargeback risk.

== Account aging ==

[[File:See-account-age.png|400px|thumb|See account age in the offer book.]]

Account age is no longer used to determine trade size limits for most payment methods. It is still measured, however, and you can see a payment account's age in the offer book before taking an offer, but we caution against using it as a measure of integrity. Older accounts are not ''necessarily'' safer.

'''Practically, this means that all payment methods on Bisq have full selling capability from the moment they are created.''' Selling limits no longer phase in over time.

Some payment methods implement a variation of account aging called account signing whereby limits are increased in stages over a period of 60 days after signing. More about this below.

If you're interested, details on the <code>AccountAgeWitness</code> object that enables this aging mechanism are [https://docs.bisq.network/payment-account-age-witness.html here].

== Account signing ==

[[File:Account-signing-overview.png|thumb|right|A graphical overview of account signing.]]

Account signing limits ''buying'' limits of risky fiat payment methods to {{MaxTradeSizeUnsigned}} until the trader has bought bitcoin from a seller with a signed payment account, and then gradually phases in full buying limits. Selling limits are unaffected.

In a nutshell, this is how it works:
* Payment account is created in Bisq for risky payment method
** Buying is limited to {{MaxTradeSizeUnsigned}} BTC per trade until account is signed (see how [[#How_to_get_an_account_signed|below]])
* 30 days after signing, buying limits are increased to 50% of maximum
* 60 days after signing, maximum trade size is allowed

Let's see how this works in practice by looking at an example. SEPA has a maximum trade size of 0.0624 BTC, and it requires account signing in order for to enable full trade limits.

First let's observe what happens if a new SEPA account is never signed. Notice how buying limits never increase beyond {{MaxTradeSizeUnsigned}}, but selling 0.0624 BTC is allowed from day 0.

{| class="wikitable"
! Time Since Creating SEPA Payment Account (Never Signed)
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 90
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|}

If that SEPA account manages to get signed on the same day it's created, it will see its {{MaxTradeSizeUnsigned}} limit increased on Day 30. Selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30
| 0.03125 BTC
| 0.0624 BTC
|-
| Day 60
| 0.0624 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

But if that SEPA account isn't signed until Day 30, it won't see its limits lifted until Day 60. Again, selling limits are unaffected.

{| class="wikitable"
! Time Since Creating SEPA Payment Account
! Maximum Trade Size (Buy)
! Maximum Trade Size (Sell)
|-
| Day 0
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 30 - Account Signed
| {{MaxTradeSizeUnsigned}}
| 0.0624 BTC
|-
| Day 60
| 0.0325 BTC
| 0.0624 BTC
|-
| Day 90
| 0.0624 BTC
| 0.0624 BTC
|}

=== How to get an account signed ===

Payment accounts that require signing cannot buy more than {{MaxTradeSizeUnsigned}} until 30 days ''after'' they are signed. Accounts can be signed with the following two methods.

==== Buying BTC ====
To sign your account you have to buy BTC following these requirements:
* trade amount is greater than or equal to {{MinTradeSizeToBeSigned}} BTC and lesser than or equal to {{MaxTradeSizeUnsigned}}
* offer must be in a market that requires signing (USD, EUR, CAD, GBP, AUD, BRL)
* seller's account must have been signed for over 30 days at the time of the signing trade

Through taking an offer you can make sure that the offer fulfills the requirements to sign your account. Making an offer could not sign your account, because taker could be unable to sign your account (signed since less than 30 days, or unsigned).

The Bisq interface makes it easy to determine if an offer can help you get signed: simply '''look for buy offers with a check mark badge''':

[[File:Good-bad-signing-asks.png|600px|thumb|left|Top offer won't get you signed. Bottom offer will get you signed.]]

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

In the image above, the offer on top does not have a check mark, but the offer on the bottom does. And it's a valid size (i.e., between {{MinTradeSizeToBeSigned}} BTC and {{MaxTradeSizeUnsigned}}), so taking that offer and successfully completing the trade will result in a signed account.

You can see your payment account's limits and signing status at <code>Accounts</code> > <code>National Currency Accounts</code>. Pick an account and look toward the bottom:

[[File:Payment-account-signing-status.png|600px|thumb|left|Where to see your payment account's limits and signing status.]]

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

==== With your own signed account ====

Once you have 1 signed payment account, any new payment account you create that requires signing will be self-signed as long as it uses the '''exact same name''' as your previously signed account. The payment account can be of a different type (e.g. a signed SEPA account can self-sign a SEPA Instant account), but a payment account created with a name that is even slightly different will not be self-signed.

Payment account types that don't require your full name cannot be self-signed (e.g. Revolut, which only requires an email address) and they cannot self-sign other payment accounts.

Self-signed accounts are immediately signed, but limits are not immediately lifted. This is because they have an age of 0 days, so 30 days must pass for the {{MaxTradeSizeUnsigned}} limit to be lifted, and another 30 days must pass for full trading ability to take effect (see tables above).

== Backing up and restoring payment accounts ==

Once your payment accounts have accrued age and been signed, you won't want to give them up. With [[Backing_up_application_data|proper backups]], you won't have to—payment accounts can be restored if you ever have to remove/reinstall Bisq, move to another machine, etc.

== User opt-out limits ==

To reduce trades into arbitration for new users unfamiliar with Bisq, new users have a 0.1 BTC limit by default that can be opt-out of at any time.

To access this limit go to Settings > Preferences

[[File:Trade limits.png|frameless|left|Trade limit setting in Bisq that can opted out of or changed at any time]]

Shown above is the trade limit setting in Bisq that can opted out of or edited higher or lower at any time.

If you opt of of this limit you will be given a pop up message informing you...

{{Admonition_Warn|Trading limits are set to reduce risk of costly disputes and losing funds for new users. Raise trading limits at your own risk. Every trader has their own pace, but it's recommended to complete at least 5 trades before raising trade limits.

By raising trading limits you acknowledge to be familiar with the basic use of Bisq, like [[Backing_up_application_data|backing up your data]], [[rading_rules|trading rules]], [[Dispute_resolution|dispute resolution]], [[Table_of_penalties|penalties]] and [[User_support|where to find support]].}}

Account signing limits are still applied to buy BTC with most National Account payment methods to reduce chargeback risk.

Payment methods

2025-10-31T16:15:45Z

SuddenWhipVapor: remove interac e-transfer link

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

{{Admonition_Note|'''Version Context:''' The details on this page, particularly regarding trade limits and account signing, primarily apply to trading on '''[[Bisq 1|Bisq v1]]'''.}}

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 have limitations that require Bisq [[Bisq 1|v1]] to employ special measures like lower per-trade limits and [[Account_limits#Account_signing|account signing]] to encourage fair trades.

__TOC__

== Fiat payment methods ==

Fiat payment methods vary significantly in characteristics like chargeback risk, regional availability, transaction limits, fees, privacy, and verification speed. The primary consideration for supporting a method on Bisq is '''chargeback risk'''. Methods with easy chargebacks (like PayPal, Venmo, Cash App) are generally not supported.

Suggestions for new payment methods, especially those enabling new markets, are welcome. See the criteria and process for adding methods [https://github.com/bisq-network/growth/issues/new?assignees=&labels=re%3Apayment-method&template=add_payment_method.md&title= here on GitHub], or discuss them on [https://bisq.chat Matrix] in the #payment-methods channel.

Below is a list of fiat payment methods currently supported in Bisq v1.

'''Note on Signing Requirement:''' Methods marked with an asterisk (*) '''do not''' require [[Account_limits#Account_signing|account signing]] to lift the initial low buying limit. All other listed fiat methods generally require signing.

'''Note on Trade Limits:''' The maximum trade sizes listed below may not be available immediately for new payment accounts. Please refer to [[Account_limits]] for details on account aging and signing required to enable larger trade sizes.

{| class="wikitable sortable"
|+ Supported Fiat Payment Methods (Bisq v1)
|-
! Payment Method [* = Signing Not Required] !! Region !! Trading Period !! Per-Trade Limit (BTC) !! Notes
|-
| [[ACH]]* || USA || 5 days || 0.0625 ||
|-
| Advanced Cash* || Global (BRL, EUR, GBP, KZT, RUB, UAH, USD) || 1 day || 0.5 || Not available in the USA.
|-
| Alipay* || China || 1 day || 0.25 ||
|-
| [[Amazon_eGift_card|Amazon eGift Card]]* || Global (AUD, CAD, EUR, GBP, INR, JPY, SAR, SEK, SGD, TRY, USD) || 1 day || 0.0625 || Check supported markets in [[Amazon_eGift_card|article]].
|-
| Australian PayID* || Australia || 1 day || 0.25 ||
|-
| [[Bizum]]* || Spain|| 1 day || 0.02 || Bizum limits: ~1000 EUR/trade, ~2000 EUR/day.
|-
| [[Capitual]]* || Global (BRL, EUR, GBP, USD) || 1 day || 0.0625 ||
|-
| [[Cash by Mail]]* || Global || 8 days || 0.0625 || Follow [[Cash_by_Mail|instructions carefully]].
|-
| Cash Deposit* || Global || 4 days || 0.0625 || Check if payee bank allows 3rd party deposits.
|-
| [[CelPay]]* || Global (AUD, CAD, GBP, HKD, USD) || 1 day || 0.0625 || CelPay limit: ~$2,500/day.
|-
| Domestic Wire Transfer* || USA || 3 days || 0.0625 ||
|-
| [[Face-to-face_(payment_method)|Face-to-Face (F2F)]]* || Global || 4 days || 0.25 || See [[Face-to-face_(payment_method)|F2F article]] for guidance.
|-
| [[Faster Payments]]* || UK || 1 day || 0.0625 || See [[Faster_Payments|article]] for usage notes.
|-
| [[Faster_Payments_System_SBP|Faster Payments System (SBP)]]* || Russia || 1 day || 0.05 ||
|-
| HalCash* || Spain || 1 day || 0.25 ||
|-
| [[IMPS]]* || India || 1 day || 0.0625 || IMPS limit: ~1,000,000 INR/day.
|-
| Interac-e-Transfer || Canada || 1 day || 0.0625 || Interac Autodeposit is '''not''' supported.
|-
| Japan Zengin Furikomi* || Japan || 1 day || 0.25 ||
|-
| MercadoPago || Argentina || 1 day || 0.0625 ||
|-
| [[Monese]]* || Europe (GBP, EUR, RON) || 1 day || 0.0625 ||
|-
| MoneyBeam (N26) || Europe || 1 day || 0.0625 ||
|-
| MoneyGram* || Global || 4 days || 0.125 ||
|-
| National Bank Transfer || Global || 4 days || 0.0625 ||
|-
| [[Nequi]]*|| Colombia || 1 day || 0.0625 || Nequi limit: ~7,000,000 COP/month.
|-
| [[NEFT]]* || India || 1 day || 0.10 || NEFT limit: ~50,000 INR/transaction.
|-
| [[Paxum]]* || Global || 1 day || 0.0625 ||
|-
| [[Paysera]]* || Global || 1 day || 0.0625 ||
|-
| [[PayTM]]* || India || 1 day || 0.0250 || PayTM limit: ~100,000 INR/transaction.
|-
| Perfect Money* || Global || 1 day || 0.25 ||
|-
| [[Pix]]*|| Brazil || 1 day || 0.0625 ||
|-
| Popmoney || USA || 1 day || 0.0625 ||
|-
| PromptPay* || Thailand || 1 day || 0.25 ||
|-
| [[Revolut]] || Global || 1 day || 0.0625 || See [[Revolut|article]] for usage notes.
|-
| [[RTGS]]* || India || 1 day || 0.10 || RTGS limits: Min 200,000 INR, Max 1,000,000 INR/transaction.
|-
| [[Satispay]]* || Italy || 1 day || 0.0625 ||
|-
| [[SEPA]] || Europe || 6 days || 0.0625 ||
|-
| [[SEPA Instant]] || Europe || 1 day || 0.0625 ||
|-
| [[Strike]]* || USA || 1 day || 0.0625 || Non-KYC Strike users have lower limits.
|-
| [[SWIFT]]* || Global || 7 days || 0.125 ||
|-
| Swish* || Sweden || 1 day || 0.25 ||
|-
| [[Tikkie]]* || The Netherlands || 1 day || 0.0250 || Tikkie limit: ~2500 EUR/24 hours.
|-
| Transfer with Same Bank || Global || 2 days || 0.0625 ||
|-
| Transfer from Specific Banks || Global || 4 days || 0.0625 ||
|-
| [[US Postal Money Order]]* || USA || 8 days || 0.0625 || USPS limits: Max 1000 USD/order, check daily limits.
|-
| Uphold || Global || 1 day || 0.0625 ||
|-
| [[UPI]]* || India || 1 day || 0.0250 || UPI limit: ~100,000 INR/transaction.
|-
| [[Verse]]* || Europe (EUR, SEK, HUF, DKK, PLN) || 1 day || 0.0625 || Verse limit: ~10,000 EUR/year.
|-
| WeChat Pay* || China || 1 day || 0.25 ||
|-
| Western Union || Global || 4 days || 0.125 ||
|-
| [[Wise]]* || Global ('''non-USD''' trades) || 4 days || 0.0625 ||
|-
| [[Wise-USD]]* || Global ('''USD''' trades) || 4 days || 0.0625 ||
|-
| [[Zelle]] || USA || 4 days || 0.0625 || Check your bank's Zelle support & limits.
|}
=== Payment method guides ===

<gallery mode="packed" heights="150px">
File:Payment-methods-advice-eur.png|EUR payment methods overview.
File:Payment-methods-advice-usd.png|USD payment methods overview.
</gallery>

== Altcoin payment methods ==

Bisq also supports trading Bitcoin against various cryptocurrencies, like XMR, ETH, ZEC, L-BTC or LTC. A full list is available on the [https://bisq.network/markets/ Bisq Network Markets page].

Because cryptocurrency transfers are generally irreversible and fast, altcoin trades usually have higher limits (up to 0.5 BTC) available immediately, without the need for account aging or signing required for many fiat methods.

{| class="wikitable"
|+ Supported Altcoin Payment Methods (Bisq v1)
|-
! Payment Method !! Trading Period !! Per-Trade Limit (BTC)
|-
| [[Altcoins]] || 1 day || 0.5
|-
| [[Altcoins Instant]] || 1 hour || 0.5
|}

'''Warning for Instant Trades:''' Altcoins Instant trades require quick confirmation (within 1 hour). Remember to disable any open Instant offers (via `Portfolio` > `My Open Offers`) if you might be unavailable to complete the trade promptly.

See the general Account setup process within Bisq for adding altcoin accounts.

[[Category:Features]]
</translate>

Howto

2025-10-31T16:15:13Z

SuddenWhipVapor: remove interac e-transfer reference

List of short how-to guides for new Bisq users:

1. Getting started

*[[How to back up your Bisq wallet seed]]
*[[Set up a Revolut payment account]]
*[[Set up a SEPA payment account]] (EUR)
*[[Set up a Zelle payment account]] (USD)
*[[Set up a UK Faster Payments account]] (GBP)
*[[Set up a National bank transfer account]] (BRL)
*How to back up your payment accounts on Bisq

2. Trade

*[[How to buy BSQ on Bisq]]
*[[How to buy BTC on Bisq with EUR]]
*[[How to buy BTC on Bisq with CAD]]
*How to buy BTC on Bisq with USD
*[[How to buy ETH on Bisq]]
*[[How to buy USDT on Bisq]]
*[[How to buy XMR on Bisq]]
*[[How to buy BTC on Bisq with CNY]]
*[[How to buy BTC on Bisq with NGN]]
*[[How to buy BTC on Bisq with INR]]
*[[How to buy BTC on Bisq with ARS]]
*[[How to sell BSQ on Bisq]]
*[[How to sell BTC on Bisq with EUR]]
*How to sell BTC on Bisq with USD
*[[How to sell USDT on Bisq]]
*[[How to sell XMR on Bisq]]
*[[How to create an offer to buy BTC with EUR]]
*[[How to create an offer to sell BTC with EUR]]

3. Contribute
*[[How to be a market maker on Bisq]]
*[[How to do arbitrage on Bisq]]
*[[How to do remittance on Bisq]]
*Educational resources
*Marketing
*How to be a developer on Bisq
*How to make a compensation request on Bisq

4. DAO
*How to vote on the Bisq DAO
*How to make a proposal on the Bisq DAO

==Bitcoin Wisdom==
*DON'T TRUST. VERIFY.
*Trusted Third Parties are security holes.
*Not your keys, not your coins.
*Vires in numeris.

How to buy BTC on Bisq with CAD

2025-10-31T16:13:36Z

SuddenWhipVapor: remove interac e-transfer reference

First download, install Bisq and create a backup (copy seed words - see [[How to back up your Bisq wallet seed]]).

Make sure you have a fiat payment account set up.

1. On '''Market''' tab select CAD - Canadian Dollar

2. Click on '''BUY BTC'''.

3. Select an offer and click on '''TAKE OFFER'''.

4. Review offer details including amount, price. Then click on '''NEXT STEP'''.

5. Fund your trade (from Bisq wallet or external wallet).

6. Click on '''CONFIRM TAKE OFFER'''.

7. After 1 blockchain confirmation (~10 minutes) you will be prompted to initiate payment. Make a transfer to the seller using your fiat payment method, then click on '''PAYMENT STARTED'''.

8. When the seller confirms payment received the trade is complete and you can '''withdraw your BTC'''.

*For more short guides see [[Howto]]. You can also find support on '''[https://bisq.chat Matrix]'''.

Automatic backup script

2025-10-13T09:11:03Z

SuddenWhipVapor:

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The provided code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/.local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/.local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup\private`"" "`"$FolderToBackup\settings`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>

Bisq 2 mobile applications

2025-10-11T17:37:54Z

SuddenWhipVapor: typo fix

The mobile version of Bisq 2 allows you to access the [[Bisq Easy]] protocol from a smartphone, and it comes in two versions:

* Bisq Easy full node
* Bisq 2 remote

== Bisq Easy full node ==

This is the full experience of Bisq Easy on mobile: the application acts as an autonomous node on the Bisq 2 p2p network, getting its own onion address and hosting all the features of the Bisq Easy trading protocol in your pocket.
It is tailored mostly for buyers, who:
* are completely new to Bitcoin and want to get their first satoshis, so they can use them to cover for the security deposit on [[Bisq 1]], in order to access a more advanced trading protocol, with larger liquidity and better prices
* do not own a desktop computer, or share it with other people, and prefer not to expose their trading

Cons:
* it will use more of your battery, because it has to manage the full p2p stack to be online
* you phone might kill the process after a while to free up resources, so you will need to start it again

== Bisq 2 remote ==

It works in a similar way to what a remote desktop does, since you need a running Bisq 2 instance on your desktop computer at home, or a headless instance on a VPS, or even some trusted third party who runs Bisq 2 and allows you to piggyback on his desktop connection.
It is the preferred option for sellers, or frequent buyers:
* lightweight if compared to the Bisq Easy full node version
* all the profile information and offer book activity is managed in a single place (your desktop computer) so access to trades can be transparently available on two different devices
* even if your phone kills its process, the current state will be preserved on the desktop application
* this will be the version where access to new protocols could be added in the future, for example the MuSig upgrade of the existing Bisq1 multisig protocol

Cons:
* you need a desktop instance running somewhere (this is the only downside, really)

Bisq 2 mobile applications

2025-10-11T16:49:25Z

SuddenWhipVapor: updated on henrik's input

The mobile version of Bisq 2 allows you to access the [[Bisq Easy]] protocol from a smartphone, and it comes in two versions:

* Bisq Easy full node
* Bisq 2 remote

== Bisq Easy full node ==

This is the full experience of Bisq Easy on mobile: the application acts as an autonomous node on the Bisq 2 p2p network, getting its own onion address and hosting all the features of the Bisq Easy trading protocol in your pocket.
It is tailored mostly for buyers, who:
* are completely new to Bitcoin and want to get their first satoshis, so they can use them to cover for the security deposit on [[Bisq 1]], in order to access a more advanced trading protocol, with larger liquidity and better prices
* do not own a desktop computer, or share it with other people, and prefer not to expose their trading

Cons:
* it will use more of your battery, because it has to manage the full p2p stack to be online
* you phone might kill the process after a while to free up resources, so you will need to start it again

== Bisq 2 remote ==

It works in a similar way to what a remote desktop does, since you need a running Bisq 2 instance on your desktop computer at home, or a headless instance on a VPN, or even some trusted third party who runs Bisq 2 and allows you to piggyback on his desktop connection.
It is the preferred option for sellers, or frequent buyers:
* lightweight if compared to the Bisq Easy full node version
* all the profile information and offer book activity is managed in a single place (your desktop computer) so access to trades can be transparently available on two different devices
* even if your phone kills its process, the current state will be preserved on the desktop application
* this will be the version where access to new protocols could be added in the future, for example the MuSig upgrade of the existing Bisq1 multisig protocol

Cons:
* you need a desktop instance running somewhere (this is the only downside, really)

Bisq 2 mobile applications

2025-10-11T15:22:48Z

SuddenWhipVapor: fixes and tweaks

The mobile version of Bisq 2 allows you to access the [[Bisq Easy]] protocol from a smartphone, and it comes in two versions:

* Bisq Easy full node
* Bisq 2 remote

== Bisq Easy full node ==

This is the full experience of Bisq Easy on mobile: the application acts as an autonomous node on the Bisq 2 p2p network, getting its own onion address and hosting all the features of the Bisq Easy trading protocol in your pocket.
It is tailored mostly for buyers, who:
* are completely new to Bitcoin and want to get their first satoshis, so they can use them to cover for the security deposit on [[Bisq 1]], in order to access a more advanced trading protocol, with larger liquidity and better prices
* do not own a desktop computer, or share it with other people, and prefer not to expose their trading

Cons:
* it will use more of your battery, because it has to manage the full p2p stack to be online
* your phone will probably kill the process after a while to free up resources, so you will lose the current state

== Bisq 2 remote ==

It works in a similar way to what a remote desktop does, since you need a running Bisq 2 instance on your desktop computer at home, which will have to be turned on and connected, and will accept an incoming connection from the mobile remote app to make its features accessible.
It is the preferred option for sellers, or frequent buyers:
* lightweight if compared to the Bisq Easy full node version
* all the profile information and offer book activity is managed in a single place (your desktop computer) so access to trades can be transparently available on two different devices
* even if your phone kills its process, the current state will be preserved on the desktop application
* this will be the version where access to new protocols could be added in the future, for example the MuSig upgrade of the existing Bisq1 multisig protocol

Cons:
* you need a desktop computer always running and connected to the internet in order to use it (this is the only downside, really)

Bisq 2

2025-10-11T15:18:44Z

SuddenWhipVapor: add link to bisq 2 mobile

Bisq 2 is the successor to the original Bisq ([[Bisq 1|Bisq v1]]). It has been developed from the ground up to allow for multiple trade protocols to be accessed via a single decentralized exchange platform, and it also sports a proper mobile version, [[Bisq 2 mobile]].

At the initial launch of Bisq 2 will support only one trading protocol '[[Bisq Easy]]'. Over time more trading protocols will be added.

Once the Bisq Multisig protocol is implemented in Bisq 2, the old version of Bisq can fade out. [[Bisq 1]] will still find its usage as Bisq DAO management tool and for BSQ-BTC trading.

Similar to Bisq v1, Bisq 2 will be a decentralized bitcoin exchange that allows anyone to buy and sell bitcoin in exchange for national currencies or other cryptocurrencies.

* Bisq 2 is a desktop application that works across platforms.
* Bisq 2 allows users to choose between multiple trading protocols to find the best fit for their preference. Aspects like privacy and security, convenience, costs and trade duration will differ and the user can make the choice.
* Bisq 2 is a peer-to-peer network that enables users to find people to trade with, make and take offers to buy and sell bitcoin, communicate with their trading peers and when necessary access support.
* Bisq 2 is privacy focused, no verified accounts or KYC will be required and run over the Tor network (as well as I2P in future).
* Bisq 2 is self custodial. Your keys are always under your control.
* Bisq 2 is open source (AGPL) and built and maintained by contributors who form the Bisq DAO.

== Why Bisq 2? ==

Bisq v1 is a powerful tool for bitcoiners that want to be able to buy and sell bitcoin peer to peer whilst maintaining their privacy, not having to undergo arduous KYC processes, and keeping control of their bitcoin.

Bisq v1 was launched on mainnet in April 2016 and whilst there has been constant improvements to the trade protocol and user interface over the years it was designed from the outset to support only one trade protocol. As bitcoin has developed and Bisq user base has grown there has been an obvious need for Bisq to expand its offerings to offer more options to its users for example trades over lightning and access via mobile devices. Bisq 2 is the first step to develop something that is built from the ground up to be more accessible to users and provide access to multiple trading protocols that can expand over time.

The core benefits of Bisq 2 are:

=== Multiple Trade Protocols ===

Bisq 2 will offer a variety of [[trade protocols]] for users. Each trade protocol will come with its own benefits and tradeoffs. Having multiple protocols allows users to choose what trade protocols are best for them based on; convenience, security, miner costs, trade fees, privacy, available support etc. All trade protocols can be accessed independently and users can switch between protocols for different trades.

The follow trade protocols are on the roadmap:

* [[Bisq_Easy|Bisq Easy]]: Reputation based trading with no security deposit requirements (included in the initial launch)
* Bisq Multisig: Similar to the current trade protocol used by Bisq 1 but with some improvements

* Submarine Swaps: Atomic swap of LN BTC <-> mainnet BTC

* Liquid Submarine Swaps: Atomic swap of LN BTC <-> Liquid BTC

* Liquid Multisig: Bisq Multisig ported to Liquid network with faster confirmation, lower fees and better privacy (confidential transactions)

* Bisq Lightning: LN BTC <-> Fiat (chain of multiple protocols: Liquid Submarine Swaps, Liquid Multisig)
* Liquid Swaps: Atomic swap of Liquid BTC <-> Liquid assets like L-USDT

* BSQ Swaps: Atomic swap of BSQ <-> BTC
* Monero Swaps: Cross chain atomic swap of BTC <-> XMR

Find out more about the [[Trade_Protocols|trade protocols]] Bisq 2 will use.

=== Multiple privacy networks ===
Bisq 2 will support multiple privacy networks. Initially it will only support Tor but I2P support is already implemented but in an experimental state. Upcoming privacy networks like Nym could be added in future if they fit the requirements.

Having multiple networks adds resilience in case one network has availability issues (as it happened multiple times with Tor when DoS attacks decreased the Tor network stability and with that Bisq's availability and stability).

The P2P network has also a built in DoS protection using Proof of Work and comes with many improvements compared to the Bisq 1 P2P network.

===Multiple Identities ===

Bisq 1 used a single onion address and key pair which represent the user's identity. Bisq 2 will allow users to create multiple identities, giving the user more control and better privacy. The user can choose between the highest level of convenience and use just one global identity for all interactions (like Bisq 1) or at the other extreme use a separate identity for any type of interaction (e.g. use a different identity for each trade as well as for each chat room). And anything in between (separating fiat and altcoin trades,...).

Find out more about how Bisq 2 manages [[Identity|identities]].

=== Multiple applications ===

The reference implementation will be the Bisq 2 JavaFx desktop application.

But there is also ongoing work on a HTML interface with a headless application to be used on personal Node projects like Start9, Umbrel, MyNode,...

Beside that there will be a REST API (useful for trading bots,...).

Bisq Easy can be implemented as a mobile app (at least for Android there are no conceptual or technical hurdles).

=== Multiple wallets ===

At launch time Bisq 2 will not include a wallet, but work is underway to support multiple wallet options.

Bitcoin core as a full wallet is already implemented (but not exposed in the UI). For users who do not want to run a full Bitcoin node, there will be a light wallet option. Currently Electrum is implemented but we might change to another solution.

For the different trade protocols there will be the specific wallets required. E.g. for Liquid the Elements wallet is already integrated. For Monero Swaps we need to provide an interface for using the Monero wallet. Find out more about the [[Bisq_2_Wallet|Bisq 2 wallet]].

=== Bonded Roles ===

The contributors providing the resources and infrastructure for Bisq 2 will require their roles to be bonded. This concept was also used in Bisq 1 but as it was not strictly enforced by the system, not all roles are secured by bonds as it was envisioned. In Bisq 2 having set up a BSQ bond is mandatory for most roles and node operators and enforced by the system.

Find out more about the [[Bisq_2_Roles|Bisq 2 roles]].

== Bisq 1 vs Bisq 2 ==

When Bisq 2 is launched it will initially only use the one trade protocol '[[Bisq Easy]]' therefore the differences are based on a 2-of-2 multisig protocol (Bisq 1) vs a reputation based trade protocol (Bisq Easy).

== Bisq Easy ==

Bisq Easy was designed for new Bitcoin users who have not yet purchased Bitcoin and therefore cannot use Bisq 1 due the requirements of the security deposit. A lot of effort was put into making it as simple to use as possible.

Bisq Easy tries to replicate the experience of a novice Bitcoiner visiting a Bitcoin meetup and getting a gentle and friendly introduction into the Bitcoin world as well as the opportunity to purchase their first Bitcoin from a helpful peer. This is inspired by the famous Satoshi Squares (early days informal Bitcoin meetups), which was also the initial name inspiration for Bitsquare - the previous brand name of Bisq.

The seller is expected to be an experienced Bitcoin and Bisq user and to have built up a reputation. The seller should be helpful and serve as guide through the newbie's first Bitcoin trade.

Bisq Easy tries to be a much more social experience as it is the case on Bisq 2. It also provides a "learn" section where newbies can learn about important topics like wallets, privacy and security. The various sections for chat rooms should also boost the social and communicative aspect of Bisq Easy.

=== Main differences for BTC buyers ===

Initially when Bisq 2 is launched the difference between versions will be that Bisq 2 will allow for users to buy bitcoin with no security deposit, no trade fees and no miner fees. Whereas, Bisq 1 will allow users to buy bitcoin with a security deposit and incur trade fees and miner costs.

The tradeoff for Bisq 2 is that the security of the trade will be based on seller reputation as opposed to Bisq 1 where the security of the trade is based on bitcoin collateral secured in the multisig.

Therefore, Bisq 2 will be cheaper and more convenient to trade for bitcoin buyers but at the cost of less robust security than Bisq 1. This is opposed to Bisq 1 that will be more secure but also more expensive, in terms of trade and miner fees, and less convenient for bitcoin buyers.

Bisq 2 will initially be more suitable for users wanting to complete trades for small amounts of bitcoin, whereas, Bisq 1 will continue to be suitable for users wanting to complete trades for larger amounts of bitcoin.

=== Main differences for BTC sellers ===

Initially when Bisq 2 is launched the difference between versions will be that Bisq 2 will allow users to sell bitcoin with no security deposit, no trade fees and no security deposit. Whereas, Bisq 1 will allow users to sell bitcoin with a security deposit and incur trade fees and miner costs.

Sellers on Bisq 2 will be expected to build their reputation. This can be done in multiple ways but to achieve a high reputation they will need to either burn BSQ and / or create a BSQ bond that locks in a specific amount of BSQ for a specified length of time.

The first iteration of Bisq 2 will have more buyers than sellers. That means a small number of sellers will be servicing the buyers. Bitcoin sellers on Bisq 2 will be required to make a judgement on how best to achieve their reputation and what the cost of doing so will involve. Bitcoin seller's using Bisq 2 will also need to account for the fact that bitcoin buyers are not putting down a security deposit for their trades so there will likely be a higher trade abandonment than in Bisq 1.

It is expected that some bitcoin sellers currently active on Bisq 1 may choose to experiment with Bisq 2, and the number of buyers and sellers on Bisq 2 will grow over time.

As in Bisq 1 seller's will be able to choose the price above or below market they wish to sell their bitcoin for.

Due to the requirements on bonds and the potential higher effort on communication with a newbie Bitcoiner, the price premium can be expected to be much higher than in Bisq 1 (maybe 10-15% above market). The Seller is the one who sets the price.

== How Bisq 2 keeps data private ==

Bisq 2 achieves data privacy for users in the same way as Bisq 1:

* Using Bisq requires no registration or centralized identity verification
* Every Bisq application connects to the Bisq network with a Tor hidden service (as well as I2P in future)
* Bisq has no central servers or databases to record data
* Data is encrypted such that trade details are readable only by counter-parties

== How Bisq 2 resists censorship ==

Bisq 2 achieves censorship resistance in the same way as Bisq 1:

* Bisq’s network is a fully distributed P2P network, and thus difficult to shut down
* Bisq’s network is built on top of Tor (I2P), and thus inherits Tor’s own censorship resistance
* Bisq is an open source project and a DAO, not a company; it is not incorporated, and thus cannot be dis-incorporated

== Advanced configurations for Bisq 2 ==

For users that want to tinker with the default config setting. Bisq 2 supports users to add a config file in the data directory which overrides the default config.

This can be useful instead of dealing with command line options. Command-line options override values set in the configuration file.

For more info see the GitHub pull request [https://github.com/bisq-network/bisq2/pull/2201 here].

== Installation ==

=== Download and verify ===

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.

To import the key in Linux and MacOS:

<code>curl https://bisq.network/pubkey/E222AA02.asc | gpg --import </code>

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:

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

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

=== Known issues with installation ===

'''MacOS'''

Notarization was removed from the build pipeline because of the risk of Apple certification revocation ([https://github.com/bisq-network/bisq/discussions/6341 GitHub issue]). Unfortunately this will require extra steps when installing Bisq on macOS.

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 using macOS Ventura (13.0+) you need to execute the following in your terminal to be able to start Bisq 2:

<code>sudo xattr -rd com.apple.quarantine /Applications/Bisq2.app</code>

You will be prompted to enter your password to execute the command as super user, and this should allow you to start Bisq 2 normally.

'''Windows'''

The developer code signing was removed for the same reason as above. You can ignore the warning after having verified the installer.

There are known issues with antivirus software: Bisq or Tor processes could be prevented from running, files could get deleted in the data directory [2] or the application directory [1]), or startup could be delayed to the point that Tor is terminated, and a lockfile is left behind preventing Bisq from being started again (this requires you to restart Windows in order to remove the lockfile). These issues are currently being evaluated and addressed.

Windows suffers from a much wider attack surface compared to Linux or OSX, please consider using a different operating system when dealing with cryptocurrencies.

[1] Application directory (contains application installation files): C:\Users<username>\AppData\Local\Bisq2

[2] Data directory (contains all Bisq data): C:\Users<username>\AppData\Roaming\Bisq2

'''Linux'''

Debian users: if you have issues starting Bisq, run <code>/opt/bisq2/bin/Bisq2</code>

If your Linux distribution does not support .deb files please follow these instructions:

<code>
cd ~/Downloads

mkdir tmp

cd tmp

ar x ../Bisq-64bit-2.1.2.deb

sudo tar Jxvf data.tar.xz

sudo cp -rp opt/Bisq2 /opt/
</code>

The above is not tested in all distributions, if you encounter issues please report them [https://github.com/bisq-network/bisq2/issues here].

Bisq 2 mobile applications

2025-10-11T15:17:18Z

SuddenWhipVapor: second stump

The mobile version of Bisq 2 allows to access the [[Bisq Easy]] protocol from a smartphone, and it comes in two versions:

* Bisq Easy full node
* Bisq 2 remote

== Bisq Easy full node ==

This is the full experience of Bisq Easy on mobile: the application acts as an autonomous node on the Bisq 2 p2p network, getting its own onion address and hosting the feature of the Bisq Easy trading protocol in your pocket.
It is tailored mostly for buyers, who:
* are completely new to Bitcoin and want to get their first satoshis, so they can use them to cover for the security deposit on [[Bisq 1]], in order to access a stronger trading protocol, with larger liquidity and better prices
* do not own a desktop computer, or share it with other people, and prefer not to expose their trading

Cons:
* it will use more of your battery, because it has to manage the full p2p stack to be online
* your phone will probably kill the process after a while to free up resources, so you will lose the current state

== Bisq 2 remote ==

It works in a similar way to what a remote desktop does, since you need a running Bisq 2 instance on your home desktop computer, which will have to be turned on and connected, and will accept an incoming connection from the mobile remote app to make its features accessible.
It is the preferred option for sellers, or frequent buyers:
* lightweight if compared to the Bisq Easy full node version
* all the profile information and offerbook activity is managed in a single place (your desktop computer) so access to trades can be transparenly available on two different devices
* this will be the version where access to new protocols could be added in the future, for example the MuSig improvement of the existing Bisq1 multisig protocol

Cons:
* you need a desktop computer always running and connected to the internet in order to use it (this is the only downside, really)

Bisq 2 mobile applications

2025-10-11T15:11:41Z

SuddenWhipVapor: First stump

SEPA

2025-09-04T11:44:30Z

SuddenWhipVapor: /* How do I sell BTC with my SEPA account? */ fixed BTC/BIC typo

'''SEPA''' is a payment method used in Bisq for buying and selling BTC for Euros (EUR). SEPA is the most common way people in the EU send and receive payments to each other via their banks.

SEPA payments usually take a couple of working days to complete, but can take up to 6 days depending on weekends and public holidays.

== Where can I find out more about SEPA? ==

Here's a list of SEPA resources:

* [https://en.wikipedia.org/wiki/Single_Euro_Payments_Area SEPA Wikipedia Page]
* [https://www.europeanpaymentscouncil.eu/ SEPA regulator]

== What countries are available for SEPA? ==

SEPA payments are available to most people in Europe. All EU users and some additional European countries can benefit from this service.

== What currencies are available for SEPA? ==

SEPA allows peer to peer payments of:

* Euros (EUR)

== What is the maximum trading duration for SEPA? ==

The maximum trade time is 6 days. Generally, SEPA payments will be completed within 2 working days. SEPA payments are usually not processed on weekends or bank holidays.

== What is the maximum BTC limit for a SEPA trade? ==

{{MaxTradeSizeBisq1}}.

== Is SEPA a payment method that can be signed? ==

Yes, SEPA payment accounts on Bisq require [[Account_limits|signing]] to lift limits to above {{MaxTradeSizeUnsigned}}.

== How do I set up a SEPA account? ==

SEPA is supported by all EU-based banks, some EU-based payment providers, as well as some non-EU European banks and payment providers.

== How do I add a SEPA account as a payment method in Bisq? ==

It is easy to add your SEPA account to Bisq.

# Go to the top menu in SEPA and select Account.
# Then select National Currency Accounts.
# Click add new account
# Select SEPA
# Complete the details
# Choose to use a custom account name this helps makes it easier for you to manage multiple payment methods in Bisq (this will be visible only to you, for example: SEPA - EUR - Jan Franco
# Click save new account

Make sure all the details are correct when you add.

Make sure to include both your Name as shown by the bank when you send payment (eg Jan Franco, or Franco. Jan), your IBAN and BIC number.

{{Admonition_Warn|Revolut SEPA accounts are not allowed on Bisq due to poor acceptance by other banks}}

== How do I buy BTC with my SEPA account? ==

You can buy BTC with SEPA on Bisq in 2 ways:

# Make an offer to buy BTC on the EUR market.
# Take an offer to buy BTC on the EUR market.

When the offer is confirmed, Bisq will provide you with the BTC seller's SEPA details for you to complete the payment. You should send the payment immediately and confirm you have done so in Bisq by clicking 'payment started'.

If you have the option to include a payment reference, please leave it blank. If your bank requires one, please just use your name that matches your bank account.

Once the BTC seller receives your payment, they will confirm in Bisq, and your security deposit and your purchased trade amount will be available in your wallet.

{{Admonition_Warn|Please send payment only to the details provided by the BTC Seller in their Bisq account. Please leave the payment description blank.}}

== How do I sell BTC with my SEPA account? ==

You can sell BTC using SEPA on Bisq in two ways:

# Make an offer to sell BTC on the EUR market.
# Take an offer to sell BTC on the EUR market.

Once your offer is confirmed, Bisq will provide the BTC buyer with your SEPA details for completing the payment. The buyer should send the payment promptly and confirm in Bisq by clicking 'payment started'.

Upon receiving the payment, confirm it in Bisq. After you've done this, the BTC buyer will receive their funds, and you will get your security deposit back.

{{Admonition_Warn|BTC Sellers should expect to receive payment from the name shown in the BTC Buyer's Bisq account. Not all banks will show the IBAN and BIC number the payment came from but the name must match.}}

== Are there any limits for me to be aware of when using my SEPA account? ==

Limits are set by your bank. Check with your bank what the limits allowed are. Most limits are about €50,000 per day. There is no minimum limit.

== Are there any fees for me to be aware of when using my SEPA account? ==

It is free to send and receive SEPA payments (as in the SEPA network itself do not charge fees to the operators). However, some banks might add changes to send or receive SEPA payments. If your bank has SEPA charges consider looking to open a new bank with fee free banking.

== How does dispute resolution when trading with SEPA? ==

If a dispute arises, the mediator may request the buyer to submit information proving they made the payment of the correct amount to the BTC Seller within the specified time frame.

The mediator may also ask the seller to provide information verifying their account details are accurate. In cases where the BTC Buyer makes a payment late or of the wrong amount, the seller should be prepared to provide this information as well.

For more information see [[dispute resolution]].

Table of penalties

2025-08-29T09:48:30Z

SuddenWhipVapor: /* Trade Penalties */ clarify seller's liability in correctly setting up his account

'''Penalties''' help enforce the [[Trading_rules|Bisq Trading Rules]], ensuring the process is as safe and fair as possible. The penalties detailed on this page apply specifically to trading protocols that utilize '''[[Security deposit|security deposits]]''' as their primary security mechanism. Protocols that do not use security deposits, like [[Bisq 2|Bisq Easy]] which relies on [[Reputation]], will have different consequences or mechanisms for handling rule violations.

Penalties are calculated as a percentage of the trade amount and are deducted '''primarily''' from the offending peer's [[Security deposit|security deposit]]. During the [[Dispute_Resolution_in_Bisq_1|dispute resolution process]], this amount may be offered as compensation to the counterparty. ''(Note: See below regarding 100% penalties potentially affecting the trade amount as well).''

'''Important Notes:'''
* The actual penalty applied is '''up to''' the maximum percentage listed below, considering the [[Security deposit|security deposit]] size and the [[Mediator]]'s discretion.
* 100% penalties represent serious violations and usually mean losing the entire [[Security deposit|security deposit]] '''and potentially the trade amount itself'''.
* Penalties are '''not cumulative'''; if multiple violations occur, the single highest applicable penalty percentage is typically used.
* Peers experiencing issues are encouraged to communicate via [[Dispute_Resolution_in_Bisq_1|trader chat]]. If mutually agreed, they can suggest a specific penalty amount to the [[Mediator]].
* To incentivize resolution via mediation, any penalty proposal will generally leave the penalized peer with at least 5% of the trade amount (deducted from the deposit), encouraging acceptance over costly [[Arbitration|arbitration]].

__TOC__

== Trade Penalties ==

=== Penalties Applicable to Either Trader ===
These penalties can apply to either the BTC Buyer or the BTC Seller, depending on who commits the violation in a protocol using security deposits.
{| class="wikitable" style="width: 100%;"
|-
! style="width: 15%;" | Max Penalty (%) !! style="width: 85%;" | Violation Description
|-
| style="text-align:center;" | 100 || Fraud attempt (e.g., unauthorized debiting of peer's account, malicious code tampering).
|-
| style="text-align:center;" | 50 || Attempting to solicit off-platform communication by including contact information in offer details (e.g., in 'additional information' field for [[Cash by mail|Cash by Mail]] or [[Face-to-face (payment method)|Face-to-Face]] offers).
|-
| style="text-align:center;" | 25 || Not responding to [[Mediator]] inquiries within 48 hours during an active dispute resolution process.
|-
| style="text-align:center;" | 25 || Contacting trading peer outside of Bisq [[Dispute_Resolution_in_Bisq_1|trader chat]] without prior consent or a clear, necessary reason related to completing the payment.
|-
| style="text-align:center;" | 20 || Cancelling an accepted trade without a valid reason according to [[Trading_rules|Trading Rules]].
|-
| style="text-align:center;" | 20 || Requesting payment be sent to, or insisting on paying from, a different account/name than agreed in the trade details, without [[Mediator]] approval.
|-
| style="text-align:center;" | 10 || Requiring excessive personal data from the counterparty beyond what is strictly necessary for the chosen payment method (e.g., demanding ID copies, proof of address unless intrinsic to the method like [[Cash by mail|Cash by Mail]]).
|-
| style="text-align:center;" | 10 || Abusive or disrespectful behavior towards the trading peer, [[Mediator]], or [[Arbitration|Arbitrator]] during the dispute process.
|}

=== Penalties Applicable Specifically to the BTC Buyer ===
These penalties apply only to the trader buying BTC (sending fiat or altcoins) in a protocol using security deposits.
{| class="wikitable" style="width: 100%;"
|-
! style="width: 15%;" | Max Penalty (%) !! style="width: 85%;" | Violation Description
|-
| style="text-align:center;" | 100 || Payment chargeback after trade completion.
|-
| style="text-align:center;" | 25 || Using Bitcoin-related terms (e.g., "BTC", "Bisq", "Bitcoin") in payment references/notes.
|-
| style="text-align:center;" | 25 || Paying from an account with a significantly different name (indicating a likely third party). ''Note: Seller may cancel trade without penalty.''
|-
| style="text-align:center;" | 20 || Payment sent is 72+ hours late (beyond the trade period).
|-
| style="text-align:center;" | 15 || Payment sent is 48-72 hours late.
|-
| style="text-align:center;" | 15 || Paying from an account with the correct name but different account details (e.g., wrong bank/account number) than specified for the payment method. ''Note: Seller may cancel trade without penalty.''
|-
| style="text-align:center;" | 10 || Payment sent is 24-48 hours late.
|-
| style="text-align:center;" | 10 || Using a similar but incorrect payment method that causes issues (e.g., sending via standard SWIFT when SEPA was agreed).
|-
| style="text-align:center;" | 10 || Paying the wrong fiat amount. ''Note: Buyer usually has the option to correct the amount within the trade window. Seller may cancel trade without penalty if not corrected promptly.''
|-
| style="text-align:center;" | 10 || Using an unagreed payment reference/memo, including potentially problematic neutral terms or the Trade ID itself.
|-
| style="text-align:center;" | 10 || Delayed altcoin payment due to Buyer choosing an extremely low network fee. ''Note: Penalty may be reduced if Buyer uses transaction acceleration techniques (RBF, CPFP).''
|-
| style="text-align:center;" | 5 || Payment sent is up to 24 hours late.
|}

=== Penalties Applicable Specifically to the BTC Seller ===
These penalties apply only to the trader selling BTC (receiving fiat or altcoins) in a protocol using security deposits.
{| class="wikitable" style="width: 100%;"
|-
! style="width: 15%;" | Max Penalty (%) !! style="width: 85%;" | Violation Description
|-
| style="text-align:center;" | 25 || Incorrect data in fiat account setup, used as-is by the buyer, causes buyer's bank to intervene (penalty amount depends on the nature of the bank's intervention)
|-
| style="text-align:center;" | 15 || BTC is released significantly outside the expected timeframe after payment confirmation, without valid reason.
|}

Trading rules

2025-08-29T09:42:40Z

SuddenWhipVapor: /* Common rules */ clarify rule to use real data in account creation

Both Bisq traders must follow these '''trading rules''' to ensure smooth and successful trades.

To trade on Bisq, you assume one of two roles, no matter what national currency or cryptocurrency you’re trading: you either ''buy bitcoin'' or ''sell bitcoin''.

The rules below are '''default''' rules for every transaction. Offer makers sometimes specify their own additional terms for handling payments. For example, a seller using cash deposits might require a picture of a receipt torn in half with "NO REFUND" written on it. Face-to-face traders often specify terms about where and how to meet.

Make sure you’re okay with an offer-maker’s terms '''before''' you accept an offer!

Trade rules also help with the following:

* Promoting good behavior from traders
* Penalizing bad behavior from traders
* Promoting good payment accounts of traders
* Penalizing bad payment accounts of traders
* Put the 'wrong doer' in a worse position and the person 'not at fault' in a better position

= Common rules =

=== Match Bisq account details with real data ===

The data you enter during fiat account creation in Bisq must match with the real data associated to the fiat account (for example, but not limited to, filling in your full account holder name instead of placing just your initials).

=== No requirement to reply in trader chat ===

While using the available trade chat can be helpful to resolve issues directly among traders without the overhead of mediation, and being communicative is a good way to ease the process for new traders, there is no obligation to reply to a peer's messages.

=== Do not communicate with your peer away from Bisq ===

Using email addresses, phone numbers, and other means to contact traders is strongly discouraged. The trader chat feature built into Bisq should be used instead: not only is it more private, but the chat record can more easily be made available to mediators and arbitrators (useful in case a trader’s chat messages indicate they broke a rule). This includes advertising offers to sell BTC with a way to contact you, for example a website, Telegram user name, or email.

In any case, it is forbidden to contact the peer using contacts obtained from their payment details, without their prior consent, or missing a compelling reason to do so.

=== Be responsive during a dispute ===

Traders are expected to reply within 48hrs to either mediators or arbitrators, and could lose the dispute based on unresponsiveness.

Mediators may take up to 48 hours to respond to messages, and arbitrators may take up to 5 days to respond to messages.

=== Do not change payment details once trade is in progress ===

Once the deposit transaction is published, the trade is in progress, and its terms cannot be changed. Traders agreed to use the payment details specified in the trade contract.

In the event of an unexpected circumstance (e.g. hitting a bank-imposed transfer limit, or a payment institution interfering with the transaction), traders can propose alternatives through trader chat or mediation, but the peer is not required to comply. It is each trader's responsibility to ensure that the payment account in their offer will work before an offer is taken.

= Rules for bitcoin sellers =

Whether making or taking an offer, bitcoin sellers put all the bitcoin they’re selling in the multisig escrow, so there’s less for them to do and fewer rules they need to follow.

=== Click <code>Confirm payment</code> after receiving payment ===

Sellers have until the end of the maximum trade period to do so.

[[Account_limits#Account_signing|Account signing]], introduced in Bisq v1.2, enables a seller with a signed payment account to sign a buyer’s payment account when they successfully receive a payment. For such trades, it is recommended that the seller take as long as possible (i.e., wait until close to the end of the trade period) to confirm receipt of payment to reduce the chance of a chargeback.

=== Do not confirm payments with mismatching details ===

Payer name, account numbers, payment method, institution, and other details of a payment should match the details in the trade contract. If there are any concerns that buyer's payment details do not match (e.g. wrong name, account number etc) payment should not be accepted.'''

{{Admonition_Warn|This is especially relevant for trades in which a signed seller trades with an unsigned buyer, because confirmation of payment receipt signs the buyer’s payment account. In case of such an issue, a dispute should be opened.}}

= Rules for bitcoin buyers =

{{Admonition_Warn|To avoid unexpected issues, make sure you can actually carry out a payment with the payment method you’ve set up in Bisq. Examples: Wells Fargo doesn’t allow cash deposits into bank accounts not owned by the depositor, and Zelle has weekly and monthly transfer maximums that are easy to overlook. The software will warn you about known issues, but cannot possibly keep up with all the newest banking and money transfer rules.}}

=== Make payment reasonably early within trade period ===

Buyer should complete at a time such that the seller has enough time to acknowledge receipt of the payment before the trade period is over. Waiting until the very end of the trade period to make a payment is not advised, as then the seller cannot reasonably act in time to acknowledge receipt (also, it’s annoying). The lengths of trade periods vary based on [[Payment methods|payment method]].

This is especially important for buyers with unsigned payment accounts trading with sellers with signed payment accounts. A seller will not want to confirm receipt of a payment made at the last minute from an untrusted account, so if you’re a buyer looking to get your payment account signed, you should make the payment ''as soon as possible''.

Some payment methods include an option to cancel a payment after you have sent it eg Revolut and Interac e-Transfer. If you cancel payment without agreement with the seller or mediator you might end up being penalized for cancelling the trade.

=== Click Payment started after sending payment ===

Seller cannot mark payment as received until buyer confirms that they have sent it.

Don’t forget to do this!

=== Leave the "reason for payment" field empty ===

{{Admonition_Warn|Before 1.5.5, it was required to put the trade ID in the 'reason for payment' field of a payment. As of 1.5.5, reason for payment should be left BLANK.}}

Some payments offer a way to specify a reason for payment (some payment methods call it "Message" or "Information for recipient" or similar). '''Leave this field BLANK.''' Do not put the trade ID, any mentions of "Bisq" or "Bitcoin" or "crypto", or any other text whatsoever.

If you are required to fill in a reason, use your account name eg "Joe Bloggs" alternatively enter something non-descriptive like a dash "-". If you would prefer to use other text please agree this with your peer in trader chat. Please remember your peer is not obligated to agree anything and may not want to agree to anything other than leaving the description blank, your name or a dash.

Violating this rule will likely result in a [[Table of penalties|trade penalty]].

Many banks don’t like anything related to Bitcoin, and may take draconian measures if they sense such a transaction.

Many users trade from personal accounts and may object to using anything that looks like it could be a commercial transaction.

=== Pay any transaction fees ===

Any fees incurred to make the payment via the agreed payment method (e.g., bank fees for bank transfer, money-order fees for money orders, etc) are the buyer’s responsibility to pay.

The seller should receive the exact amount of the trade. The only exception to this rule is if the receiving institution imposes a fee on incoming payments—these fees are borne by the seller.

= What happens when things go wrong? =

Sometimes trades do not go to plan for whatever reason.

It is prudent for all traders to know when entering into the trade what will happen when things go wrong. Traders would be wise to make themselves aware of the [[dispute resolution]] process to ensure there are no surprises.

Automatic backup script

2025-08-12T22:14:53Z

SuddenWhipVapor:

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The provided code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup\private`"" "`"$FolderToBackup\settings`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>

Backing up application data

2025-08-03T17:21:21Z

SuddenWhipVapor: add reference to automatic backup script guide

'''Backing up''' your Bisq data is crucial to ensure you can retain control over trades, disputes, payment accounts, and funds in case of issues with your machine (e.g., drive failure) or Bisq itself (e.g., critical bugs).

All Bisq data is stored right on your computer—it's never stored (or even sent) to a central server, so backing it up is your job.

To see how to ''restore'' data to Bisq, see [[Restoring application data]].

__TOC__

= Back up the entire Bisq data directory =

The safest, quickest, easiest, and most comprehensive thing you can do to safeguard your data is to back up the whole data directory at regular intervals. See the various elements of the data directory detailed [[Data_directory#Data_Directory_Structure|here]].

In addition, to make restoring payment accounts easier, you may want to back up an [[#Back_up_payment_accounts|export of your payment accounts]].

== While Bisq is running ==

Go to <code>Account</code> > <code>Backup</code> and put in a location for your backup to be exported to (note that this section is titled "Backup wallet" in the software but it actually exports the entire data directory).

[[File:Backup-while-running.png|600px|thumb|left|Data directory backup screen.]]

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

== While Bisq is closed ==

When Bisq is closed, you can simply copy the entire data directory and paste it somewhere safe. Find the location of your data directory by clicking on the <code>Open Directory</code> button (see screenshot above) or see [[Data_directory#Default_Locations|data directory locations here]].

== Encrypt your backup ==

'''Backup files are not encrypted.''' If you’ve set a wallet password, your wallet files will be encrypted, but all your other data will ''not'' be encrypted.

We recommend encrypting the whole backup folder with something like gpg, 7-Zip, Cryptomator, etc.

= Back up payment accounts =

If you just want to back up your payment accounts, export them from <code>Account</code> > <code>National Currency Accounts</code>.

Be advised: exporting your accounts this way only exports metadata. '''Aging and signing status are not included'''. To include [[Account_limits|account aging and signing status]], you also need to save the <code>btc_mainnet/keys/sig.key</code> file from your [[Data_directory|data directory]].

Because of the way [[Restoring_application_data#Restore_payment_accounts|restoring payment accounts]] works, it's best for most users to back up the whole data directory ''and'' back up a payment account export.

[[File:Export-payment-accounts.png|600px|thumb|left|Export fiat payment accounts here. You can export altcoin accounts from the Altcoin Accounts tab.]]

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

= Back up your wallet seed =

Please be sure to [[Backing_up_your_wallet_seed|properly back up your wallet seed]].

= Export Tor state =

If you want to carry over a particular onion address (and keep your local reputation), you can replace the <code>btc_mainnet/tor/hiddenservice</code> folder in your data directory with the one from your backup.

= Export trade history =

In <code>Portfolio</code> > <code>History</code> you'll find an <code>Export to CSV</code> button to export your trade history.

There's no way to import this data back into Bisq, but it can be useful to have a copy of this data for yourself for record-keeping, analysis, etc.

= Export transaction history =

In <code>Funds</code> > <code>Transactions</code> you'll find an <code>Export to CSV</code> button to export your trade history.

There's no way to import this data back into Bisq, but it can be useful to have a copy of this data for yourself for record-keeping, analysis, etc.

= Automatic backup with cyclic redundancy =

Bisq doesn't directly implement a scheduled backup feature, but you can set up an [[Automatic_backup_script|automatic backup routine]] to store a versioned history of your data directory in a compact way.

Automatic backup script

2025-07-23T14:38:36Z

SuddenWhipVapor: /* macOS */

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup\private`"" "`"$FolderToBackup\settings`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>

Automatic backup script

2025-07-21T09:33:51Z

SuddenWhipVapor: only include `private` and `settings` folders for Bisq2

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup\private`"" "`"$FolderToBackup\settings`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== macOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}/private" "${FOLDER_TO_BACKUP}/settings"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>

Automatic backup script

2025-07-21T08:42:57Z

SuddenWhipVapor: /* MacOS */ Add Bisq2 + MacOS

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

# Adjust 7z.exe path if needed
& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== macOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/Users/YOURUSERNAME/Library/Application Support/Bisq2/db"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${ARCHIVE_PATH}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using:

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq2backup.log 2>&1</code>

Automatic backup script

2025-07-21T08:40:19Z

SuddenWhipVapor: /* Windows */ Add Bisq2 + Windows

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named scripts.
* Inside this folder, create a new file named bisq2backup.ps1.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$FolderToBackup = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq2\db"
$TargetFolder = "D:\BACKUPS\BISQ2"
$BackupCount = 4
# ============================

$ArchiveRoot = "bisq2_backup_"
$Timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$ArchiveName = "$ArchiveRoot$Timestamp.7z"
$TempArchive = Join-Path $env:TEMP $ArchiveName
$FinalArchive = Join-Path $TargetFolder $ArchiveName

# Adjust 7z.exe path if needed
& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "`"$TempArchive`"" "`"$FolderToBackup`""

Move-Item -Path $TempArchive -Destination $FinalArchive -Force

$Archives = Get-ChildItem -Path $TargetFolder -Filter "$ArchiveRoot*.7z" | Sort-Object LastWriteTime -Descending

if ($Archives.Count -gt $BackupCount) {
Write-Output "Found $($Archives.Count) backups, removing oldest one(s)"
$Archives | Select-Object -Skip $BackupCount | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq2backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq2backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

MacOS

Automatic backup script

2025-07-21T08:31:02Z

SuddenWhipVapor: /* Linux */ make cosmetic changes

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

windows

== MacOS ==

MacOS

Automatic backup script

2025-07-21T08:29:38Z

SuddenWhipVapor: /* Linux */ make cosmetic changes

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with
<code>crontab -e</code>
and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# EDIT THE FOLLOWING
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ##

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with <code>crontab -e</code> (in Debian derivatives), and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

windows

== MacOS ==

MacOS

Automatic backup script

2025-07-21T08:28:40Z

SuddenWhipVapor: /* MacOS */ add MacOs instructions

The biggest issues for users happen when data files are lost or corrupted, leading to missing or borked trades, or unrecoverable Delayed Payout Transactions.

Having an automated backup solution helps covering that risk, by removing the need to manually run a backup after every application state change (mainly "offer created", "trade started", "trade completed").

Issues could still happen when a critical event occurs right after a state change was saved to disk, and before an automated backup was taken, but there are strategies to mitigate that possibility, which will be discussed.

__TOC__

= Common requirements and backup strategy =

All scripts require 7z compression (7-zip on Windows, p7zip-full on Linux, p7zip on MacOS).

The code will backup all functional files in the data directory, leaving out non-unique files that the Bisq application will fetch/re-create autonomously, and compress them into a 7zip archive, keeping the number of last backups that you define, while deleting the oldest one(s) if the existing number of backups is higher.

It is advised that you direct the backups to either an external drive, or a NAS, or an encrypted cloud storage.

Depending on how bulletproof of a backup schedule you want, you can increase the number of backups to keep on disk to 10 or more (the size of each depends on the history of your instance, but it usually resides in a few tens of MB, often less) and the frequency the script runs with, for example every 1 or 2 hours.

= Bisq1 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/home/YOURUSERNAME/local/share/Bisq/btc_mainnet"
TARGET_FOLDER="/mnt/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="$SOURCE_DIR/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "$SUBFOLDER_DB_PATH/$file" ]; then
echo "$SUBFOLDER_DB_PATH/$file" >> "$FILE_LIST"
fi
done

for subfolder in "$FOLDER_KEYS" "$FOLDER_WALLET"; do
find "$SOURCE_DIR/$subfolder" -maxdepth 1 -type f >> "$FILE_LIST"
done

FOLDER_TOR_PATH="$SOURCE_DIR/$FOLDER_TOR"
if [ -d "$FOLDER_TOR_PATH" ]; then
find "$FOLDER_TOR_PATH" -type f >> "$FILE_LIST"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "$ARCHIVE_PATH" @"$FILE_LIST"

rm "$FILE_LIST"

echo "Backup completed: $BACKUP_FILE"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with <code>crontab -e</code> (in Debian derivatives), and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log</code>

== Windows ==

Create a scripts solder and a PowerShell script:

* Open File Explorer and navigate to your user directory (e.g. C:\Users\YOURUSERNAME).
* Create a folder named <code>scripts</code>.
* Inside this folder, create a new file named <code>bisq1backup.ps1</code>.

Right-click the script file and open it in Notepad, then paste and edit the following code.

<pre>
# ==== EDIT THE FOLLOWING ====
$SOURCE_DIR = "C:\Users\YOURUSERNAME\AppData\Roaming\Bisq\btc_mainnet"
$TARGET_FOLDER = "D:\BACKUPS\BISQ1"
$BACKUP_COUNT = 4
# ============================

$ARCHIVE_ROOT = "bisq1_backup_"
$timestamp = Get-Date -Format "yyyyMMdd_HHmmss"
$BACKUP_FILE = "$ARCHIVE_ROOT$timestamp.7z"
$ARCHIVE_PATH = Join-Path $TARGET_FOLDER $BACKUP_FILE

$SELECTED_FILES = @(
"BsqSwapTrades",
"BallotList",
"DisputeList",
"RefundDisputeList",
"SequenceNumberMap",
"MyVoteList",
"OpenOffers",
"MyBlindVoteList",
"ClosedTrades",
"MediationDisputeList",
"MyProposalList",
"MailboxMessageList",
"AccountAgeWitnessStore",
"PendingTrades",
"MyProofOfBurnList",
"PreferencesPayload",
"UserPayload",
"AddressEntryList",
"FailedTrades",
"MyReputationList",
"TempProposalStore",
"NavigationPath",
"UnconfirmedBsqChangeOutputList",
"IgnoredMailboxMap",
"PeerList",
"RemovedPayloadsMap",
"TradeStatistics3Store",
"SignedWitnessStore"
)

$FOLDER_KEYS = "keys"
$FOLDER_WALLET = "wallet"
$FOLDER_TOR = "tor\hiddenservice"

$FILE_LIST = [System.IO.Path]::GetTempFileName()

$SUBFOLDER_DB_PATH = Join-Path $SOURCE_DIR "db"
foreach ($file in $SELECTED_FILES) {
$path = Join-Path $SUBFOLDER_DB_PATH $file
if (Test-Path $path -PathType Leaf) {
Add-Content -Path $FILE_LIST -Value $path
}
}

foreach ($subfolder in @($FOLDER_KEYS, $FOLDER_WALLET)) {
$dir = Join-Path $SOURCE_DIR $subfolder
if (Test-Path $dir) {
Get-ChildItem -Path $dir -File | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}
}

$FOLDER_TOR_PATH = Join-Path $SOURCE_DIR $FOLDER_TOR
if (Test-Path $FOLDER_TOR_PATH -PathType Container) {
Get-ChildItem -Path $FOLDER_TOR_PATH -File -Recurse | ForEach-Object {
Add-Content -Path $FILE_LIST -Value $_.FullName
}
}

& "C:\Program Files\7-Zip\7z.exe" a -t7z -mx=9 -m0=lzma2 -mmt=on -spf $ARCHIVE_PATH @"$FILE_LIST"

Remove-Item $FILE_LIST

Write-Output "Backup completed: $BACKUP_FILE"

$backupFiles = Get-ChildItem -Path $TARGET_FOLDER -Filter "$ARCHIVE_ROOT*.7z" | Sort-Object LastWriteTime -Descending
if ($backupFiles.Count -gt $BACKUP_COUNT) {
Write-Output "Found $($backupFiles.Count) backups, removing oldest one(s)"
$backupFiles | Select-Object -Skip $BACKUP_COUNT | ForEach-Object {
Remove-Item $_.FullName -Force
}
}
</pre>

To run the script every 8 hours:
* Open Task Scheduler.
* Create a new task and give it a name (for example, "bisq1backup").
* In the Triggers tab, set a new trigger to begin the task on a schedule, repeating every 8 hours.
* In the Actions tab, add a new action:
** Program/script: powershell.exe
** Add arguments: -ExecutionPolicy Bypass -File "C:\Users\YOURUSERNAME\scripts\bisq1backup.ps1"
* Adjust settings as needed and save the task.

== MacOS ==

Open the Terminal and run:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq1backup
chmod +x bisq1backup
nano bisq1backup
</pre>

Paste the following code and edit where needed:

<pre>
#!/bin/bash

# ==== EDIT THE FOLLOWING ====
SOURCE_DIR="/Users/YOURUSERNAME/Library/Application\ Support/Bisq/btc_mainnet"
TARGET_FOLDER="/Volumes/BACKUPS/BISQ1"
BACKUP_COUNT=4
# ============================

ARCHIVE_ROOT="bisq1_backup_"
BACKUP_FILE="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${BACKUP_FILE}"
SELECTED_FILES=(
"BsqSwapTrades"
"BallotList"
"DisputeList"
"RefundDisputeList"
"SequenceNumberMap"
"MyVoteList"
"OpenOffers"
"MyBlindVoteList"
"ClosedTrades"
"MediationDisputeList"
"MyProposalList"
"MailboxMessageList"
"AccountAgeWitnessStore"
"PendingTrades"
"MyProofOfBurnList"
"PreferencesPayload"
"UserPayload"
"AddressEntryList"
"FailedTrades"
"MyReputationList"
"TempProposalStore"
"NavigationPath"
"UnconfirmedBsqChangeOutputList"
"IgnoredMailboxMap"
"PeerList"
"RemovedPayloadsMap"
"TradeStatistics3Store"
"SignedWitnessStore"
)

FOLDER_KEYS="keys"
FOLDER_WALLET="wallet"
FOLDER_TOR="tor/hiddenservice"

FILE_LIST=$(mktemp)

SUBFOLDER_DB_PATH="${SOURCE_DIR}/db"
for file in "${SELECTED_FILES[@]}"; do
if [ -f "${SUBFOLDER_DB_PATH}/$file" ]; then
echo "${SUBFOLDER_DB_PATH}/$file" >> "${FILE_LIST}"
fi
done

for subfolder in "${FOLDER_KEYS}" "${FOLDER_WALLET}"; do
find "${SOURCE_DIR}/${subfolder}" -maxdepth 1 -type f >> "${FILE_LIST}"
done

FOLDER_TOR_PATH="${SOURCE_DIR}/${FOLDER_TOR}"
if [ -d "${FOLDER_TOR_PATH}" ]; then
find "${FOLDER_TOR_PATH}" -type f >> "${FILE_LIST}"
fi

7z a -t7z -mx=9 -m0=lzma2 -mmt=on -spf "${ARCHIVE_PATH}" @"${FILE_LIST}"

rm "${FILE_LIST}"

echo "Backup completed: ${BACKUP_FILE}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "Found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

To run the backup every 8 hours, edit your crontab using

<code>crontab -e</code>

Then add the following line:

<code>0 */8 * * * /Users/YOURUSERNAME/scripts/bisq1backup > /tmp/bisq1backup.log 2>&1</code>

= Bisq2 =

== Linux ==

Create a <code>scripts</code> folder in your <code>home</code> directory, prepare an executable file and open it with an editor:

<pre>
cd ~
mkdir -p scripts
cd scripts
touch bisq2backup
chmod +x bisq2backup
nano bisq2backup
</pre>

paste the following code in the file, and edit where needed:

<pre>
#!/bin/bash

# EDIT THE FOLLOWING
FOLDER_TO_BACKUP="/home/YOURUSERNAME/local/share/Bisq2/db"
TARGET_FOLDER="/mnt/BACKUPS/BISQ2"
BACKUP_COUNT=4
# ##

ARCHIVE_ROOT="bisq2_backup_"
ARCHIVE_NAME="${ARCHIVE_ROOT}$(date +%Y%m%d_%H%M%S).7z"
ARCHIVE_PATH="${TARGET_FOLDER}/${ARCHIVE_NAME}"

7z a -t7z -mx=9 -mfb=64 -md=32m -ms=on -mmt=on "/tmp/${ARCHIVE_NAME}" "${FOLDER_TO_BACKUP}"
mv "/tmp/${ARCHIVE_NAME}" "${TARGET_FOLDER}"

ARCHIVE_COUNT=$(find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | wc -l)

if [ "${ARCHIVE_COUNT}" -gt "${BACKUP_COUNT}" ]; then
echo "found ${ARCHIVE_COUNT} backups, removing oldest one(s)"
find "${TARGET_FOLDER}" -maxdepth 1 -type f -name "${ARCHIVE_ROOT}*.7z" | sort -r | tail -n +"${BACKUP_COUNT}" | xargs -I {} rm -f {}
fi
</pre>

Lastly, edit the system <code>crontab</code> with <code>crontab -e</code> (in Debian derivatives), and add the following line to have a backup taken every 8 hours:

<code>0 */8 * * * /home/YOURUSERNAME/scripts/bisq2backup > /tmp/bisq1backup.log</code>

== Windows ==

windows

== MacOS ==

MacOS

Automatic backup script

2025-07-21T08:24:01Z

SuddenWhipVapor: /* Linux */

Automatic backup script

2025-07-21T08:23:30Z

SuddenWhipVapor: /* Windows */

Automatic backup script

2025-07-21T08:15:23Z

SuddenWhipVapor: Add Windows and MacOS stubs to make editing easier

Automatic backup script

2025-07-21T08:08:47Z

SuddenWhipVapor: Consolidated most common text, added Bisq2 on linux

Automatic backup script

2025-07-21T07:44:57Z

SuddenWhipVapor: /* Linux */