Bisq Wiki - User contributions [en]

Restoring application data

2021-01-28T16:15:56Z

Huey735: Add Restore trade history section

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

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

__TOC__

= Restore an entire data directory =

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

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

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

= Restore payment accounts =

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

== Restore payment account metadata ==

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

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

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

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

SEPA
Alice Liddell
DE89370400440532013000
DEUTDE5X*
SKzH
salt
@56655c3738ea9dea3b20f482fff048985a2757e57dff206fbd9e8c4f267f7781

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

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

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

== Restore payment account aging and signing status ==

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

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

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

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

= Restore onion address =

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

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

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

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

= Restore trade history =

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

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

= Restore wallet =

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

Restoring application data

2021-01-28T16:11:13Z

Huey735: /* Restore onion address */ Correct the effect of restoring the hiddenservice data

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

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

__TOC__

= Restore an entire data directory =

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

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

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

= Restore payment accounts =

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

== Restore payment account metadata ==

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

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

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

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

SEPA
Alice Liddell
DE89370400440532013000
DEUTDE5X*
SKzH
salt
@56655c3738ea9dea3b20f482fff048985a2757e57dff206fbd9e8c4f267f7781

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

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

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

== Restore payment account aging and signing status ==

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

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

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

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

= Restore onion address =

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

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

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

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

= Restore wallet =

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

Emergency Multisig payout tool

2021-01-20T07:11:12Z

Huey735: /* Warning */ Add link to guide to switch to a new data directory

== Summary ==
This tool allows for a Mediator to create an unsigned transaction releasing the funds in the 2-of-2 multisig controlled by the traders and send it to each of them, have them sign it and return the signatures and have the the Mediator combine the three pieces (unsigned transaction and both signatures from the traders) to broadcast the transaction.

== Warning ==
In this process traders copy and paste their private keys from the Bisq software into a notepad. As a precaution it is advised they remove all of their funds from this wallet before starting this procedure and consider [[Switching to a new data directory|switching to a new data directory]] to get a new wallet.

== Precautions ==
The traders need to make sure the transaction details match the correct resolution before signing.

== What you need ==
As Mediator

{| class="wikitable"
|-
! fields !! description
|-
| depositTxId || ID for the transaction that sent both trader’s funds into the 2-of-2 multisig
|-
| amountInMultisig || Amount locked in the 2-of-2 multisig
|-
| buyerPayoutAmount || Amount to be released to the BTC buyer
|-
| sellerPayoutAmount || Amount to be released to the BTC seller
|-
| buyerPayoutAddress || Address onto which the BTC buyer should be paid
|-
| sellerPayoutAddress || Address onto which the BTC seller should be paid
|-
| buyerPubKeyAsHex || BTC buyer’s public key
|-
| sellerPubKeyAsHex || BTC seller’s public key
|}

As a trader (each one only needs their own private key)

{| class="wikitable"
|-
! fields !! description
|-
| privatekeyHex || your private key for this trade
|}

Open a text editor where you can gather all this information.

== Get multisig public keys ==
Each trader involved can get their public keys and the other trader's in their trade JSON contract.
# Find your trade under PORTFOLIO.
# Click the i icon next to the trade ID, and at the bottom click VIEW CONTRACT IN JSON FORMAT. At the end, you see the Buyer and Seller public keys:

<nowiki>
BuyerMultiSigPubKeyHex: <hex value>
SellerMultiSigPubKeyHex: <hex value></nowiki>

== Get private keys ==
To access your Bisq wallet private key
# Press ctrl + j, alt +j or cmd + j.
# Check Include private keys and click COPY TO CLIPBOARD and paste it to a text editor.
# In the text editor, search for the public key value. You are looking for an entry that reads DeterministicKey{pub HEX=<hex value> where <hex value> is the public key.
# When you've found this entry, select and copy the priv HEX=<hex value>. This value is the private key.
# Copy, paste and save that information in a bisqWallet.txt file.
Note: If your wallet uses a password, you will need to remove the password to view the private keys in wallet data.

== Get payout addresses ==
Open the trade details and click on VIEW CONTRACT IN JSON FORMAT. At the end of the JSON contract file you can also find the intended payout address for each trader:
<nowiki>
makerPayoutAddressString: <address value>
takerPayoutAddressString: <address value> </nowiki>

== Create Transaction ==
# Press ctrl+g. Click INPUTS and fill in the fields.
# Once finished click EXPORT and copy the string you get, save it and share it with each trader. This is the unsigned transaction

== Sign Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the information about the payout transaction.
# Go to SIGN and paste your private key for this trade (priv HEX=) and click GENERATE SIGNATURE.
# Copy the signature hex that you get and share it with the mediator

== Broadcast The Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the info about the payout transaction.
# Click BUILD (to the let). Paste the Buyer's signature on the first field and the Seller's on the second field.
# Click the BUILD button bellow the field where you pasted the signatures and it should populate with the signed transaction. Save the resulting text just to be safe.
# Click BROADCAST.
# Verify on a block explorer that the transaction was indeed broadcast.

Emergency Multisig payout tool

2021-01-20T07:08:38Z

Huey735: /* What you need */ Correct the field name for the trader's private key

== Summary ==
This tool allows for a Mediator to create an unsigned transaction releasing the funds in the 2-of-2 multisig controlled by the traders and send it to each of them, have them sign it and return the signatures and have the the Mediator combine the three pieces (unsigned transaction and both signatures from the traders) to broadcast the transaction.

== Warning ==
In this process traders copy and paste their private keys from the Bisq software into a notepad. As a precaution it is advised they remove all of their funds from this wallet before starting this procedure and move on to a new wallet – directory change reference

== Precautions ==
The traders need to make sure the transaction details match the correct resolution before signing.

== What you need ==
As Mediator

{| class="wikitable"
|-
! fields !! description
|-
| depositTxId || ID for the transaction that sent both trader’s funds into the 2-of-2 multisig
|-
| amountInMultisig || Amount locked in the 2-of-2 multisig
|-
| buyerPayoutAmount || Amount to be released to the BTC buyer
|-
| sellerPayoutAmount || Amount to be released to the BTC seller
|-
| buyerPayoutAddress || Address onto which the BTC buyer should be paid
|-
| sellerPayoutAddress || Address onto which the BTC seller should be paid
|-
| buyerPubKeyAsHex || BTC buyer’s public key
|-
| sellerPubKeyAsHex || BTC seller’s public key
|}

As a trader (each one only needs their own private key)

{| class="wikitable"
|-
! fields !! description
|-
| privatekeyHex || your private key for this trade
|}

Open a text editor where you can gather all this information.

== Get multisig public keys ==
Each trader involved can get their public keys and the other trader's in their trade JSON contract.
# Find your trade under PORTFOLIO.
# Click the i icon next to the trade ID, and at the bottom click VIEW CONTRACT IN JSON FORMAT. At the end, you see the Buyer and Seller public keys:

<nowiki>
BuyerMultiSigPubKeyHex: <hex value>
SellerMultiSigPubKeyHex: <hex value></nowiki>

== Get private keys ==
To access your Bisq wallet private key
# Press ctrl + j, alt +j or cmd + j.
# Check Include private keys and click COPY TO CLIPBOARD and paste it to a text editor.
# In the text editor, search for the public key value. You are looking for an entry that reads DeterministicKey{pub HEX=<hex value> where <hex value> is the public key.
# When you've found this entry, select and copy the priv HEX=<hex value>. This value is the private key.
# Copy, paste and save that information in a bisqWallet.txt file.
Note: If your wallet uses a password, you will need to remove the password to view the private keys in wallet data.

== Get payout addresses ==
Open the trade details and click on VIEW CONTRACT IN JSON FORMAT. At the end of the JSON contract file you can also find the intended payout address for each trader:
<nowiki>
makerPayoutAddressString: <address value>
takerPayoutAddressString: <address value> </nowiki>

== Create Transaction ==
# Press ctrl+g. Click INPUTS and fill in the fields.
# Once finished click EXPORT and copy the string you get, save it and share it with each trader. This is the unsigned transaction

== Sign Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the information about the payout transaction.
# Go to SIGN and paste your private key for this trade (priv HEX=) and click GENERATE SIGNATURE.
# Copy the signature hex that you get and share it with the mediator

== Broadcast The Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the info about the payout transaction.
# Click BUILD (to the let). Paste the Buyer's signature on the first field and the Seller's on the second field.
# Click the BUILD button bellow the field where you pasted the signatures and it should populate with the signed transaction. Save the resulting text just to be safe.
# Click BROADCAST.
# Verify on a block explorer that the transaction was indeed broadcast.

Emergency Multisig payout tool

2021-01-20T06:49:48Z

Huey735: Create a guide on how to use the Emergency Multisig payout tool

== Summary ==
This tool allows for a Mediator to create an unsigned transaction releasing the funds in the 2-of-2 multisig controlled by the traders and send it to each of them, have them sign it and return the signatures and have the the Mediator combine the three pieces (unsigned transaction and both signatures from the traders) to broadcast the transaction.

== Warning ==
In this process traders copy and paste their private keys from the Bisq software into a notepad. As a precaution it is advised they remove all of their funds from this wallet before starting this procedure and move on to a new wallet – directory change reference

== Precautions ==
The traders need to make sure the transaction details match the correct resolution before signing.

== What you need ==
As Mediator

{| class="wikitable"
|-
! fields !! description
|-
| depositTxId || ID for the transaction that sent both trader’s funds into the 2-of-2 multisig
|-
| amountInMultisig || Amount locked in the 2-of-2 multisig
|-
| buyerPayoutAmount || Amount to be released to the BTC buyer
|-
| sellerPayoutAmount || Amount to be released to the BTC seller
|-
| buyerPayoutAddress || Address onto which the BTC buyer should be paid
|-
| sellerPayoutAddress || Address onto which the BTC seller should be paid
|-
| buyerPubKeyAsHex || BTC buyer’s public key
|-
| sellerPubKeyAsHex || BTC seller’s public key
|}

As a trader (each one only needs their own private key)

{| class="wikitable"
|-
! fields !! description
|-
| buyerPrivKeyAsHex || BTC buyer’s private key
|-
| sellerPrivKeyAsHex || BTC seller’s private key
|}

Open a text editor where you can gather all this information.

== Get multisig public keys ==
Each trader involved can get their public keys and the other trader's in their trade JSON contract.
# Find your trade under PORTFOLIO.
# Click the i icon next to the trade ID, and at the bottom click VIEW CONTRACT IN JSON FORMAT. At the end, you see the Buyer and Seller public keys:

<nowiki>
BuyerMultiSigPubKeyHex: <hex value>
SellerMultiSigPubKeyHex: <hex value></nowiki>

== Get private keys ==
To access your Bisq wallet private key
# Press ctrl + j, alt +j or cmd + j.
# Check Include private keys and click COPY TO CLIPBOARD and paste it to a text editor.
# In the text editor, search for the public key value. You are looking for an entry that reads DeterministicKey{pub HEX=<hex value> where <hex value> is the public key.
# When you've found this entry, select and copy the priv HEX=<hex value>. This value is the private key.
# Copy, paste and save that information in a bisqWallet.txt file.
Note: If your wallet uses a password, you will need to remove the password to view the private keys in wallet data.

== Get payout addresses ==
Open the trade details and click on VIEW CONTRACT IN JSON FORMAT. At the end of the JSON contract file you can also find the intended payout address for each trader:
<nowiki>
makerPayoutAddressString: <address value>
takerPayoutAddressString: <address value> </nowiki>

== Create Transaction ==
# Press ctrl+g. Click INPUTS and fill in the fields.
# Once finished click EXPORT and copy the string you get, save it and share it with each trader. This is the unsigned transaction

== Sign Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the information about the payout transaction.
# Go to SIGN and paste your private key for this trade (priv HEX=) and click GENERATE SIGNATURE.
# Copy the signature hex that you get and share it with the mediator

== Broadcast The Transaction ==
# Press ctrl+g and click IMPORT. Copy the string you got on step 2, paste it in the first field and press IMPORT FROM STRING. It should populate the view with the info about the payout transaction.
# Click BUILD (to the let). Paste the Buyer's signature on the first field and the Seller's on the second field.
# Click the BUILD button bellow the field where you pasted the signatures and it should populate with the signed transaction. Save the resulting text just to be safe.
# Click BROADCAST.
# Verify on a block explorer that the transaction was indeed broadcast.

Manual payout

2020-11-20T14:07:47Z

Huey735:

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== Get multisig public keys ==

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

== Get private keys ==

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

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

== Get payout addresses ==

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

== Recreating Redeem script ==

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

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

== Verify transaction ==

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

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

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

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

Manual payout

2020-11-20T14:01:34Z

Huey735: /* Get multisig public keys */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== Get private keys ==

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

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

== Get multisig public keys ==

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

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Manual payout

2020-11-20T14:00:57Z

Huey735: /* Get private keys */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== Get private keys ==

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

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

== 2. Get multisig public keys ==

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

'''About the legacy protocol'''

If resolving a trade with the old (legacy) protocol that involved a 2-of-3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own <code>bisqWallet.txt</code> file for it. They can find it by looking for the public key for their Arbitrator address. It is the one in the line with <code>context=ARBITRATOR</code>.

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in BTC.

By tracking the BTC trading fee you can find the cluster of other trades that arbitrator was involved in. Then you need to find to Payout transactions - spending from a 2-of-3 multisig. In these transactions will be able to find three revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Manual payout

2020-11-20T14:00:30Z

Huey735: /* 1. Get private keys */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== 1. Get private keys ==

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

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

== 2. Get multisig public keys ==

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

'''About the legacy protocol'''

If resolving a trade with the old (legacy) protocol that involved a 2-of-3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own <code>bisqWallet.txt</code> file for it. They can find it by looking for the public key for their Arbitrator address. It is the one in the line with <code>context=ARBITRATOR</code>.

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in BTC.

By tracking the BTC trading fee you can find the cluster of other trades that arbitrator was involved in. Then you need to find to Payout transactions - spending from a 2-of-3 multisig. In these transactions will be able to find three revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Manual payout

2020-11-10T10:57:25Z

Huey735: /* 1. Get private keys */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== 1. Get private keys ==

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

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

== 2. Get multisig public keys ==

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

'''About the legacy protocol'''

If resolving a trade with the old (legacy) protocol that involved a 2-of-3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own <code>bisqWallet.txt</code> file for it. They can find it by looking for the public key for their Arbitrator address. It is the one in the line with <code>context=ARBITRATOR</code>.

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in BTC.

By tracking the BTC trading fee you can find the cluster of other trades that arbitrator was involved in. Then you need to find to Payout transactions - spending from a 2-of-3 multisig. In these transactions will be able to find three revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Finding your mediator

2020-10-06T19:34:53Z

Huey735: /* Current mediators and their onion addresses */

Below we detail current Bisq mediators and their onion addresses, as well as how you can find the mediator for a specific Bisq trade.

__TOC__

== How to find the mediator for a trade ==

To find a trade's mediator:

# 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>.
# Ignore the <code>"mediatorNodeAddresses"</code> field, as this is the list of all active mediators when the trade started.
# Scroll down and you'll find <code>"mediatorNodeAddress"</code> field with a single <code>"hostName"</code> for the onion address.

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

== Current mediators and their onion addresses ==

{| class="wikitable"
! Mediator
! TorV3 Address
! TorV2 Address
! GitHub Handle
|-
| leo816
|
| sjlho4zwp3gecspf.onion
| leo816
|-
| wiz
| wizbisqzd7ku25di7p2ztsajioabihlnyp5lq5av66tmu7do2dke2tid.onion
| wizrsmceorm4bisq.onion
| wiz
|-
| bisq_knight
|
| apbp7ubuyezav4hy.onion
| bisq-knight
|-
| huey735
| a56olqlmmpxrn5q34itq5g5tb5d3fg7vxekpbceq7xqvfl3cieocgsyd.onion:9999
|
| huey735
|}

== Get in touch with your mediator ==

'''For open trades, you should be able to get in touch with your mediator through Bisq itself.'''

If you cannot get in touch with your mediator on Bisq, you can get in touch with them on the [https://keybase.io/team/bisq Bisq Keybase group]. Their Keybase handles and addresses are displayed in the headline for the #support channel as well.

[[Category:Use Cases]]

Manual payout

2020-09-01T12:20:05Z

Huey735: /* What you need */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== 1. Get private keys ==

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

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

== 2. Get multisig public keys ==

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

'''About the legacy protocol'''

If resolving a trade with the old (legacy) protocol that involved a 2-of-3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own <code>bisqWallet.txt</code> file for it. They can find it by looking for the public key for their Arbitrator address. It is the one in the line with <code>context=ARBITRATOR</code>.

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in BTC.

By tracking the BTC trading fee you can find the cluster of other trades that arbitrator was involved in. Then you need to find to Payout transactions - spending from a 2-of-3 multisig. In these transactions will be able to find three revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Manual payout

2020-09-01T12:19:41Z

Huey735: /* 4. Recreating Redeem script */

== Warning ==

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

== Precautions ==

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

== What you need ==

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

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

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

== 1. Get private keys ==

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

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

== 2. Get multisig public keys ==

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

'''About the legacy protocol'''

If resolving a trade with the old (legacy) protocol that involved a 2-of-3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own <code>bisqWallet.txt</code> file for it. They can find it by looking for the public key for their Arbitrator address. It is the one in the line with <code>context=ARBITRATOR</code>.

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in BTC.

By tracking the BTC trading fee you can find the cluster of other trades that arbitrator was involved in. Then you need to find to Payout transactions - spending from a 2-of-3 multisig. In these transactions will be able to find three revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get payout addresses ==

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

== 4. Recreating Redeem script ==

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

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

== 6. Verify transaction ==

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

== 7. Sign transaction ==
# Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1.b in the <code>Private key</code> text field and the encoded transaction in the text field below. To find the private key, search your <code>bisqWallet.txt</code> file for the value of the <code>BuyerMultiSigPubKeyHex</code> (or <code>SellerMultiSigPubKeyHex</code> if you are the seller), obtained in step 2. The private key beginning with <code>priv WIF=</code> is written after the search result. Ensure that the pasted private key is only the part after the <code>priv WIF=</code>.
# Click <code>Submit</code> to get a new encoded transaction string.
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

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

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

Manual payout

2020-03-14T10:19:33Z

Huey735: Created page with "== Warnings == In this process you'll be copying and pasting your private keys from the Bisq software into a web browser. So it may be worth it to move all of your funds from..."

== Warnings ==

In this process you'll be copying and pasting your private keys from the Bisq software into a web browser. So it may be worth it to move all of your funds from this wallet before starting.

== Precautions ==

This method will only be necessary in extreme occasions where one of the traders may not be available. It's therefore important to make sure that who constructs the transaction doesn't defraud the other signers.

== What we'll need ==

In this document we will using open source tools (aside from Bisq) to create, sign and broadcast transactions of funds locked in multisigs.
In order to spend out of a multisig two things are needed:
* redeem script
* enough private keys to meet the minimum multisig threshold. We'll be using the string in "priv WIF=" instead of "priv HEX=".

Bisq doesn't provide the Redeem Script for the multisig but we can recreate it with all the public keys involved in the multisig.

Tools we're going to use:
* Bisq software
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]
* [http://torproject.org Tor browser]

== 1. Get the private keys ==

You can get access to your Bisq wallet's private key by pressing "Ctrl + j" or "alt +j" or "cmd + j".

Tick “Include private keys” and click COPY TO CLIPBOARD. Copy, paste and save that information in a bisqWallet.txt file.
== 2. Get the multisg public keys ==

Each trader involved can get their and the other trader's public key in their trade JSON contract. Find your trade under PORTFOLIO. Click the little 'i' icon next to the trade ID and at the bottom click on VIEW CONTRACT IN JSON FORMAT. At the end of it you'll find the following:
<nowiki>
BuyerMultiSigPubKeyHex:
SellerMultiSigPubKeyHex:
</nowiki>

These are your and the other trader's public keys involved in the multisig.

'''Legacy protocol'''

If resolving a trade with the old protocol that involved a 2 out of 3 multisig, a third public key belonging to the arbitrator is necessary. The arbitrator can get this public key by following the steps above and search in their own bisqWallet.txt file for it. They can find it by looking for the public key for their Arbitrator address. It's the one in the line with "context=ARBITRATOR".

An alternative way to get the arbitrator's public key is to look for it in the blockchain. This can be done if at least one of the traders paid the trading fees in btc.

By tracking the btc trading fee we can find the cluster of other trades that arbitrator was involved in. Then we need to find to Payout transactions - spending from a 2 out of 3 multisig. In these transactions will be able to find 3 revealed public keys for each trade. The one that is present in both trades is the arbitrator's.

== 3. Get the payout addresses ==

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

== 4. Recreate the Redeem script ==

For all the web interaction will be using the Tor browser. Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:
* at the top click “New” and from the dropdown menu choose “MultiSig Address”
* paste in the three public keys in the following order
** Arbitrator
** BuyerMultiSigPubKeyHex
** SellerMultiSigPubKeyHex
* click submit and you should see an address and a Redeem Script. Make sure the address matches the multisig address for the trade. If not try to change the order of the public keys.
* Copy and save the Redeem Script.

== 5. Create the transaction ==

Next click, once again, “New” at the top, but this time choose “Transaction” from the dropdown menu.
* Paste the Redeem Script in the text field at the top and click “Load”. It should take a few seconds and then return the value locked in the multisig.
* For the first input fill in an address from **makerPayoutAddressString** and the respective trade amount
* add a new output by clicking the “+” sign next to the amount field. For this second output paste the address that belongs to takerPayoutAddressString and the respective trade amount
* click submit. You should now have an encoded transaction string. Copy and save it.

== 6. Verify the transactions ==

Click “Verify” at the top and paste the encoded string you got from the previous step. Verify all is correct before moving to the next step.

== 7. Sign the transaction ==

Next click “Sign” at the top of the page and paste your WIF private key you got on step 1 on the “Private key” text field and the encoded transaction in the text field bellow. Then click “Submit”.
You should get a new encoded transaction string. Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.

== 8. Second signature and broadcast ==

The second signer should click “Verify” at the top of the Coinbin website and paste the encoded string the previous signer shared with you. If you're ok with it, click “Sign” at the top of the page and paste your WIF private key you got on step 1 on the “Private key” text field and the encoded transaction shared with you in the text field bellow. Then click “Submit”. You should get a new encoded transaction string. Copy and save it.

You can verify the transaction once again before broadcasting.

If everything is correct, click “Broadcast” at the top of the page, paste the encoded transaction string you got after you signed the transaction and click “Submit”.