Difference between revisions of "Manual payout"

From Bisq Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
== Warning ==
+
== Overview ==
  
−
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.
+
Funds for a Bisq trade are locked in a 2-of-2 multisig that is controlled only by the two parties involved.
 +
Bisq normally does all the work to sign and publish the payout at trade completion.
 +
However sometimes a trade can fail due to unforseen circumstances, leaving the funds stranded in the 2-of-2 multisig.
 +
When this happens, a Manual Payout may be necessary.
  
−
== 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.
+
== Using Bisq's Manual Payout tool ==
 +
The emergency payout tool is in Bisq, if you do a CTRL-G it will open.   
  
−
== What you need ==
+
The purpose of the tool is to allow owners of a 2of2 multisig to issue a transaction which pays out the funds to their addresses.  The tool is designed to be used in collaboration with mediators but
 +
it could conceivably be used by the multisig key holders alone.
  
−
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.
+
The tool operates in 4 steps:  
−
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>.
 
  
 +
# Fill input information;
 +
# Import/export details to trade participants;
 +
# Sign using each holder's private key;
 +
# Build and broadcast the payout.
  
−
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.
 
−
 
−
== Using Bisq's Manual Payout tool ==
 
−
Please press Ctrl+J and check the include private keys, clickl COPY TO CLIPBOARD and paste on a notepad. Search on that file for your public key. In the same line there's also a priv HEX=.
 
−
BuyerMultiSigPubKeyHex: ...
 
−
SellerMultiSigPubKeyHex: ...
 
  
−
The BTC seller encountered a bug and lost access to its information. I'll need you to use the Emergy multisig payout tool (Ctrl+g) to release the funds.
 
−
1. Open the tool with Ctrl+G.
 
−
2. Click import and paste the following text in the first field and click IMPORT FROM STRING. It should populate the view with the info about the payout transaction.
 
  
−
<unsigend transaction string>
+
=== Fill in inputs ===
  
−
3. Go to SIGN and paste your private key for this trade (priv HEX=) and click GENERATE SIGNATURE.
+
Input information can be either filled in manually using information from the Bisq trade's Json contract, or for ease of use the same information can be imported from the Mediation ticket.
−
4. Copy the signature hex that you get and share it with me.
 
  
−
Tools you need:
+
* If filling in manually, all fields on the "Inputs" tab must be entered.
−
* Bisq software
+
* If importing from Mediation, choose the Import menu option then pick your mediation ticket from the drop down list and press "Import from mediation ticket".
−
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]
 
−
* [https://coinb.in/ Coinbin web wallet]
 
−
* [https://www.torproject.org/ Tor browser]
 
  
−
== Get multisig public keys ==
+
One important thing which the tool prompts you for is the "amountInMultisig" field.  This value is not known in Bisq, so the user (or Mediator) has to look it up on a Blockchain explorer and enter it completely accurately into the tool.  If it is incorrect in any way the resultant transaction will fail.  (Reason for this is that Segwit includes the amount as part of the signature inputs).
  
−
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 ==
+
=== Import/Export to trade participants ===
  
−
To access your Bisq wallet private key
+
Once accurate input information has been entered, the same information needs to be passed to both owners of the multisig keys (the two traders). This is what the "Export" menu item is for. It translates the input field data into a code which can be DM'd or emailed to the participants, which they can enter via the "Import" menu (& "Import from String" option).
−
# 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.''
+
The important thing is that each participant have EXACTLY the same information entered into the Inputs section of the tool.  If there is any discrepancy between the inputs that each participant signs, then the transaction will be invalid.
  
−
== Get payout addresses ==
+
Note that if the two traders have access to the mediation ticket they can Import from the ticket themselves.  But it is generally best for Mediator to Export their filled in fields to both traders (via DM).
  
−
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 ==
+
=== Sign ===
  
−
For all the web interactions use the Tor browser.
+
Both participants have to sign the inputs. This is done from the Sign menu, for convenience there is a "Locate key in wallet" button which will scan the user's wallet for a key which matches the inputs. "Generate signature" will sign the inputs using the key at the top of the screen. Users could alternatively choose to locate the key themselves, and paste it into the "privateKeyHex" field before doing "Generate signature".
−
# 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 ==
+
Once the signature has been generated each participant should send it to the person who will build and broadcast the transaction (usually the Mediator).
−
# 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.
+
=== Build & Broadcast ===
  
−
== Sign transaction ==
+
Once both signatures have been provided, they can be pasted into the Build screen at which time the "Build" button at the bottom of that screen should be pressed.  It will generate the TxID and transaction hex into the text area. The transaction hex can be verified using your own tools* or simply broadcast to the network using the "Broadcast" button (or alternatively send it yourself using your Bitcoin node).  
−
# 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==
+
* NB: "https://bitaps.com/broadcast" has a "Preview" feature that tests if the transaction is acceptable to the mempool before actually sending it. Any errors in the transaction will be listed, or if it is good it will say "Test mempool transaction accepted" and give the option to broadcast it at that point.
−
# 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.
 

Latest revision as of 22:04, 11 November 2023

Overview

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


Using Bisq's Manual Payout tool

The emergency payout tool is in Bisq, if you do a CTRL-G it will open.

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

The tool operates in 4 steps:

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


Fill in inputs

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

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

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


Import/Export to trade participants

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

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

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


Sign

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

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


Build & Broadcast

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


  • NB: "https://bitaps.com/broadcast" has a "Preview" feature that tests if the transaction is acceptable to the mempool before actually sending it. Any errors in the transaction will be listed, or if it is good it will say "Test mempool transaction accepted" and give the option to broadcast it at that point.
Retrieved from "https://bisq.wiki/index.php?title=Manual_payout&oldid=3358"