https://bisq.wiki/api.php?action=feedcontributions&user=Kemccall&feedformat=atomBisq Wiki - User contributions [en]2024-03-29T06:04:06ZUser contributionsMediaWiki 1.34.0https://bisq.wiki/index.php?title=Wiki_style_guidelines&diff=857Wiki style guidelines2020-04-14T05:59:32Z<p>Kemccall: </p>
<hr />
<div>__TOC__<br />
<br />
== General guidelines ==<br />
There are three general types of information that almost every form of information can be segregated into:<br />
* Concepts<br />
* Tasks (procedures) <br />
* References<br />
<br />
For clarity it is best that these three types of information not be intermingled. For example, you do not want to step through a lengthy task to find a file name, nor would you want to search for a file name in a description of a feature. <br />
<br />
An example of a good procedure is [https://bisq.wiki/Backing_up_your_wallet Backing up your wallet]. It has a title with a gerund (Back'''ing'''), and a brief conceptual introduction followed by a step-by-step task.<br />
<br />
==Style guide references==<br />
The Bisq wiki adheres to the Wikipedia Manual of Style whenever possible. There are some styles that Wikipedia does not cover. They are documented in '''Exceptions from Wikipedia''' below. <br />
<br />
* [https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style <big>Wikipedia Manual of Style</big>]<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Images <big>Wikipedia Images</big>]<br />
* [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet <big>Wikipedia editing Cheatsheet</big>]<br />
<br />
== Exceptions from Wikipedia ==<br />
<br />
=== Procedures ===<br />
The Bisq wiki contains many procedures. The Wikipedia Manual of Styles does not include styles for technical tasks and procedures therefore the Microsoft style guide has excellent guidance for [https://docs.microsoft.com/en-us/style-guide/procedures-instructions/writing-step-by-step-instructions Writing step-by-step instructions].<br />
<br />
====Procedure titles====<br />
Use gerunds (. . . ing) for procedural titles. For example, "Back up your wallet" should be "Back'''ing''' up your wallet". Using a gerund implies you will be performing a process.<br />
<br />
=== Tabs, buttons and UI elements ===<br />
User interface (UI) elements such as tabs and buttons are indicated in '''bold''' text. <br />
<br />
===Describing UI elements===<br />
When referring to a user action, simply state "click '''Start'''", it is not necessary to state "click the '''Start''' button".</div>Kemccallhttps://bisq.wiki/index.php?title=Reducing_memory_usage&diff=855Reducing memory usage2020-04-12T05:29:49Z<p>Kemccall: </p>
<hr />
<div>== Default MaxRAM Setting ==<br />
<br />
One of the settings java virtual machines (JVMs) use to calibrate how much physical memory to reserve at startup is '''MaxRAM''', and there is a good chance your JVM's default MaxRAM configuration is too large. &nbsp;&nbsp; To check the default MaxRAM setting, run this java <code>version</code> command: <br />
<br />
java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version | grep MaxRAM<br />
<br />
Look for the MaxRAM value (bytes) in the output; this machine says<br />
<br />
367: uint64_t MaxRAM = 137438953472 <br />
<br />
This means the OpenJDK 11 JVM's MaxRAM setting is 128 GB, on a machine with only 16 GB RAM.<br />
<br />
<br />
Experiments have shown running Bisq with a 4g (GB) MaxRAM setting reduces resident memory consumption by more than 50% (when starting a clean Bisq installation with an empty data directory).<br />
&nbsp;&nbsp; Setting MaxRAM to 2g reduces resident memory usage even more, but setting it any lower (1536m) will result in an OutOfMemoryError and crash the app.<br />
<br />
<br />
As of version 1.2.7, Bisq is started with a MaxRAM setting of 4g (GB). &nbsp;&nbsp; If you are using Bisq v1.2 [.TODO] or older, consider upgrading to the [https://bisq.network/downloads latest version] to benefit from this change.</div>Kemccallhttps://bisq.wiki/index.php?title=User:Kemccall&diff=846User:Kemccall2020-04-09T05:38:48Z<p>Kemccall: </p>
<hr />
<div><br />
* https://bisq.wiki/Wiki_Editor<br />
<br />
* https://en.bitcoin.it/wiki/Main_Page<br />
* https://meta.wikimedia.org/wiki/Help:Help<br />
* https://meta.wikimedia.org/wiki/Help:Starting_a_new_page<br />
* https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style<br />
* https://en.wikipedia.org/wiki/Help:Wikitext<br />
* https://www.mediawiki.org/wiki/Help:Formatting<br />
* https://www.mediawiki.org/wiki/Help:Categories<br />
* https://www.mediawiki.org/wiki/Manual%3aTable_of_contents<br />
* https://www.mediawiki.org/wiki/Manual:Skins <br />
* https://docs.bisq.network/</div>Kemccallhttps://bisq.wiki/index.php?title=User:Kemccall&diff=845User:Kemccall2020-04-09T05:38:21Z<p>Kemccall: </p>
<hr />
<div><br />
* https://bisq.wiki/Wiki_Editor (br><br />
<br />
* https://en.bitcoin.it/wiki/Main_Page<br />
* https://meta.wikimedia.org/wiki/Help:Help<br />
* https://meta.wikimedia.org/wiki/Help:Starting_a_new_page<br />
* https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style<br />
* https://en.wikipedia.org/wiki/Help:Wikitext<br />
* https://www.mediawiki.org/wiki/Help:Formatting<br />
* https://www.mediawiki.org/wiki/Help:Categories<br />
* https://www.mediawiki.org/wiki/Manual%3aTable_of_contents<br />
* https://www.mediawiki.org/wiki/Manual:Skins<br><br />
*https://docs.bisq.network/</div>Kemccallhttps://bisq.wiki/index.php?title=User:Kemccall&diff=844User:Kemccall2020-04-09T05:36:30Z<p>Kemccall: </p>
<hr />
<div>* https://bisq.wiki/Wiki_Editor<br />
<br />
* https://en.bitcoin.it/wiki/Main_Page<br />
* https://meta.wikimedia.org/wiki/Help:Help<br />
* https://meta.wikimedia.org/wiki/Help:Starting_a_new_page<br />
* https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style<br />
* https://en.wikipedia.org/wiki/Help:Wikitext<br />
* https://www.mediawiki.org/wiki/Help:Formatting<br />
* https://www.mediawiki.org/wiki/Help:Categories<br />
* https://www.mediawiki.org/wiki/Manual%3aTable_of_contents<br />
* https://www.mediawiki.org/wiki/Manual:Skins</div>Kemccallhttps://bisq.wiki/index.php?title=User:Kemccall&diff=843User:Kemccall2020-04-09T05:35:17Z<p>Kemccall: Created page with " * https://en.bitcoin.it/wiki/Main_Page * https://meta.wikimedia.org/wiki/Help:Help * https://meta.wikimedia.org/wiki/Help:Starting_a_new_page * https://en.wikipedia.org/wiki..."</p>
<hr />
<div><br />
<br />
* https://en.bitcoin.it/wiki/Main_Page<br />
* https://meta.wikimedia.org/wiki/Help:Help<br />
* https://meta.wikimedia.org/wiki/Help:Starting_a_new_page<br />
* https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style<br />
* https://en.wikipedia.org/wiki/Help:Wikitext<br />
* https://www.mediawiki.org/wiki/Help:Formatting<br />
* https://www.mediawiki.org/wiki/Help:Categories<br />
* https://www.mediawiki.org/wiki/Manual%3aTable_of_contents<br />
* https://www.mediawiki.org/wiki/Manual:Skins</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=842Manual payout2020-04-09T05:25:40Z<p>Kemccall: /* 9. Verify transaction before broadcasting */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order, 1) Arbitrator, 2) BuyerMultiSigPubKeyHex, 3) SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
# Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Copy and save the transaction.<br />
# Click <code>submit</code> to obtain an encoded transaction string.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
# 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.<br>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>.<br />
# Click <code>Submit</code> to get a new encoded transaction string. <br />
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
# 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.<br />
# Click <code>Submit</code> to get a new encoded transaction string.<br />
# Copy and save it.<br />
<br />
==9. Verify transaction before broadcasting==<br />
# Confirm everything is correct and click <code>Broadcast</code> at the top of the page.<br />
# After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.<br />
# When complete, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=841Manual payout2020-04-09T05:24:33Z<p>Kemccall: /* 8. Second signature and broadcast */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order, 1) Arbitrator, 2) BuyerMultiSigPubKeyHex, 3) SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
# Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Copy and save the transaction.<br />
# Click <code>submit</code> to obtain an encoded transaction string.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
# 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.<br>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>.<br />
# Click <code>Submit</code> to get a new encoded transaction string. <br />
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
# 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.<br />
# Click <code>Submit</code> to get a new encoded transaction string.<br />
# Copy and save it.<br />
<br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=840Manual payout2020-04-09T05:23:18Z<p>Kemccall: /* 7. Sign transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order, 1) Arbitrator, 2) BuyerMultiSigPubKeyHex, 3) SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
# Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Copy and save the transaction.<br />
# Click <code>submit</code> to obtain an encoded transaction string.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
# 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.<br>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>.<br />
# Click <code>Submit</code> to get a new encoded transaction string. <br />
# Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=839Manual payout2020-04-09T05:21:23Z<p>Kemccall: /* 5. Creating transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order, 1) Arbitrator, 2) BuyerMultiSigPubKeyHex, 3) SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
# Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Copy and save the transaction.<br />
# Click <code>submit</code> to obtain an encoded transaction string.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=838Manual payout2020-04-09T05:19:44Z<p>Kemccall: /* 4. Recreating Redeem script */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order, 1) Arbitrator, 2) BuyerMultiSigPubKeyHex, 3) SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=837Manual payout2020-04-09T05:10:34Z<p>Kemccall: /* 2. Get multisig public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
# Find your trade under <code>PORTFOLIO</code>.<br />
# 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=831Manual payout2020-04-08T02:21:18Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txtfile.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=830Manual payout2020-04-08T02:17:45Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
To access your Bisq wallet private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txtfile.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=829Manual payout2020-04-08T02:16:41Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
To access your Bisq wallet's private key<br />
# Press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txtfile.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=828Manual payout2020-04-08T02:09:37Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
# To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check Include private keys and click <code>COPY TO CLIPBOARD</code>.<br />
# Copy, paste and save that information in a <code>bisqWallet.txtfile.<br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=825Manual payout2020-04-07T06:01:56Z<p>Kemccall: </p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisig public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex: <hex value><br />
SellerMultiSigPubKeyHex: <hex value></nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString: <address value><br />
takerPayoutAddressString: <address value></nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=822Manual payout2020-04-06T06:40:11Z<p>Kemccall: /* Warning */</p>
<hr />
<div>__NOTOC__== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=821Manual payout2020-04-06T06:26:17Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=820Manual payout2020-04-06T06:25:22Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
If resolving a trade with the old 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>.<br />
<br />
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.<br />
<br />
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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=819Manual payout2020-04-06T06:24:26Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
If resolving a trade with the old 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>.<br />
<br />
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.<br />
<br />
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 3 revealed public keys for each trade. The one that is present in both trades is the arbitrator's.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=818Manual payout2020-04-06T06:10:02Z<p>Kemccall: /* 9. Verify the transaction before broadcasting */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify transaction before broadcasting==<br />
<ol type="a"><br />
<li>Confirm everything is correct and click <code>Broadcast</code> at the top of the page.</li><br />
<li> After you have signed the transaction paste the encoded transaction string and click <code>Submit</code>.</li><br />
<li> When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</li><br />
</ol></div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=817Manual payout2020-04-06T06:06:45Z<p>Kemccall: /* Verify the transaction before broadcasting */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==9. Verify the transaction before broadcasting==<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=816Manual payout2020-04-06T06:06:28Z<p>Kemccall: /* You can verify the transaction before broadcasting */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==Verify the transaction before broadcasting==<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=815Manual payout2020-04-06T06:05:49Z<p>Kemccall: </p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
==You can verify the transaction before broadcasting==<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=814Manual payout2020-04-06T06:01:37Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''About the legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
===You can verify the transaction before broadcasting===<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=813Manual payout2020-04-06T06:00:56Z<p>Kemccall: /* 8. Second signature and broadcast */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<ol type="a"><br />
<li>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.</li><br />
<li></li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string.</li><br />
<li>Copy and save it.</li><br />
</ol><br />
===You can verify the transaction before broadcasting===<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
When complete, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=812Manual payout2020-04-06T05:57:07Z<p>Kemccall: /* 8. Second signature and broadcast */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.c.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=811Manual payout2020-04-06T05:56:26Z<p>Kemccall: /* 7. Sign transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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.b. 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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=810Manual payout2020-04-06T05:55:21Z<p>Kemccall: /* 7. Sign transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>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.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=809Manual payout2020-04-06T05:54:32Z<p>Kemccall: /* 6. Verify transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=808Manual payout2020-04-06T05:54:02Z<p>Kemccall: /* 6. Verify transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the step 6.e. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=807Manual payout2020-04-06T05:52:36Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
<ol type="a"><br />
<li>Find your trade under <code>PORTFOLIO</code>.</li><br />
<li>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:</li><br />
</ol><br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=806Manual payout2020-04-06T05:49:58Z<p>Kemccall: </p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
</ol><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
</ol><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
</ol><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=805Manual payout2020-04-06T05:48:37Z<p>Kemccall: </p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
</ol><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=804Manual payout2020-04-06T05:38:23Z<p>Kemccall: /* 7. Sign transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<ol type="a"><br />
<li>Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.</li><br />
<li>Click <code>Submit</code> to get a new encoded transaction string. </li><br />
<li>Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.</li><br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=803Manual payout2020-04-06T05:36:18Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<ol type="a"><br />
<li>To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.</li><br />
<li>Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>.</li><br />
<li>Copy, paste and save that information in a <code>bisqWallet.txt</code> file.</li><br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=802Manual payout2020-04-06T05:34:52Z<p>Kemccall: /* 5. Creating transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
# To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. <br />
#Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
<br />
== 5. Creating transaction ==<br />
<ol type="a"><br />
<li>Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.</li><br />
<li>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.</li><br />
<li>For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.</li><br />
<li>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.</li><br />
<li>Click <code>submit</code> to obtain an encoded transaction string.</li><br />
<li>Copy and save the transaction.</li><br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=801Manual payout2020-04-06T05:31:46Z<p>Kemccall: /* 4. Recreating Redeem script */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
# To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. <br />
#Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
<ol type="a"><br />
<li>Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:</li><br />
<li>At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code></li><br />
<li>Paste the three public keys in the following order:</li><br />
*Arbitrator<br />
*BuyerMultiSigPubKeyHex<br />
*SellerMultiSigPubKeyHex<br />
<li>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.</li><br />
<li>Copy and save the Redeem Script.</li><br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code> to obtain an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=800Manual payout2020-04-06T05:21:27Z<p>Kemccall: /* 2. Get multisg public keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
# To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. <br />
#Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
Each trader involved can get their public keys and the other trader's public keys in their trade JSON contract. <br />
* Find your trade under <code>PORTFOLIO</code>. <br />
* 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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code> to obtain an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=799Manual payout2020-04-06T05:18:15Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
# To access your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
# Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. <br />
#Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code> to obtain an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=798Manual payout2020-04-06T05:16:08Z<p>Kemccall: /* 1. Get private keys */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code>, <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code> to obtain an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=797Manual payout2020-04-06T05:13:58Z<p>Kemccall: /* 5. Creating transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code> to obtain an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=796Manual payout2020-04-06T05:13:15Z<p>Kemccall: /* 4. Recreating Redeem script */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=795Manual payout2020-04-06T05:07:20Z<p>Kemccall: /* 8. Second signature and broadcast */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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. Then, click <code>Submit</code> to get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
If everything is correct, click <code>Broadcast</code> at the top of the page, paste the encoded transaction string obtained after you signed the transaction and click <code>Submit</code>.<br />
<br />
After all is done, delete the <code>bisqWallet.txt</code> file created in step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=794Manual payout2020-04-06T05:03:29Z<p>Kemccall: /* 7. Sign transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
#Click <code>Sign</code> at the top of the page and paste your WIF private key obtained in step 1 in the <code>Private key</code> text field and the encoded transaction in the text field below.<br>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>.<br />
#Click <code>Submit</code> to get a new encoded transaction string. <br />
#Copy and save it and share it with the other parties of the multisig so they can sign and broadcast it.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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 from step 1 on the “Private key” text field and the encoded transaction shared with you in the text field below. Then, click “Submit”. You should get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
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”.<br />
<br />
After all is done, delete the bisqWallet.txt file you created on step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=793Manual payout2020-04-06T04:38:19Z<p>Kemccall: /* 6. Verify transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
Click <code>Verify</code> at the top and paste the encoded string obtained from the previous step. Verify it all is correct before moving to the next step.<br />
<br />
== 7. Sign transaction ==<br />
<br />
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.<br />
<br />
To find the private key, search your bisqWallet.txt file for the value of the BuyerMultiSigPubKeyHex (or SellerMultiSigPubKeyHex if you're the seller), which you got on step 2. The private key beginning with "priv WIF=" is written just after the search result. Ensure that the pasted private key is just the part after the "priv WIF=".<br />
<br />
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.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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 from step 1 on the “Private key” text field and the encoded transaction shared with you in the text field below. Then, click “Submit”. You should get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
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”.<br />
<br />
After all is done, delete the bisqWallet.txt file you created on step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=792Manual payout2020-04-06T04:37:29Z<p>Kemccall: /* 5. Creating transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from <code>makerPayoutAddressString</code> and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<br />
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.<br />
<br />
To find the private key, search your bisqWallet.txt file for the value of the BuyerMultiSigPubKeyHex (or SellerMultiSigPubKeyHex if you're the seller), which you got on step 2. The private key beginning with "priv WIF=" is written just after the search result. Ensure that the pasted private key is just the part after the "priv WIF=".<br />
<br />
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.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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 from step 1 on the “Private key” text field and the encoded transaction shared with you in the text field below. Then, click “Submit”. You should get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
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”.<br />
<br />
After all is done, delete the bisqWallet.txt file you created on step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=791Manual payout2020-04-06T04:36:34Z<p>Kemccall: /* What you need */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script.<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from **makerPayoutAddressString** and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<br />
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.<br />
<br />
To find the private key, search your bisqWallet.txt file for the value of the BuyerMultiSigPubKeyHex (or SellerMultiSigPubKeyHex if you're the seller), which you got on step 2. The private key beginning with "priv WIF=" is written just after the search result. Ensure that the pasted private key is just the part after the "priv WIF=".<br />
<br />
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.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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 from step 1 on the “Private key” text field and the encoded transaction shared with you in the text field below. Then, click “Submit”. You should get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
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”.<br />
<br />
After all is done, delete the bisqWallet.txt file you created on step 1.</div>Kemccallhttps://bisq.wiki/index.php?title=Manual_payout&diff=790Manual payout2020-04-06T04:36:12Z<p>Kemccall: /* 5. Creating transaction */</p>
<hr />
<div>== Warning ==<br />
<br />
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.<br />
<br />
== Precautions ==<br />
<br />
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.<br />
<br />
== What you need ==<br />
<br />
This document uses open source tools (other than Bisq) to create, sign and broadcast transactions of funds locked in multisig transactions.<br />
To spend out of a multisig, two things are needed:<br />
* A redeem script<br />
* Enough private keys to meet the minimum multisig threshold. Use the string in <code>priv WIF=</code> instead of <code>priv HEX=</code>.<br />
<br />
<br />
Bisq does not provide the Redeem Script for the multisig, but we can recreate it with all the public keys involved in the multisig.<br />
<br />
Tools you need:<br />
* Bisq software<br />
* [http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion Blockstream's block explorer]<br />
* [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]<br />
* [https://www.torproject.org/ Tor browser]<br />
<br />
== 1. Get private keys ==<br />
<br />
To get access to your Bisq wallet's private key press <code>Ctrl + j</code> or <code>alt +j</code> or <code>cmd + j</code>.<br />
<br />
Check <code>Include private keys</code> and click <code>COPY TO CLIPBOARD</code>. Copy, paste and save that information in a <code>bisqWallet.txt</code> file.<br />
<br />
== 2. Get multisg public keys ==<br />
<br />
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:<br />
<nowiki><br />
BuyerMultiSigPubKeyHex:<br />
SellerMultiSigPubKeyHex:<br />
</nowiki><br />
<br />
<br />
'''Legacy protocol'''<br />
<br />
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 <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>.<br />
<br />
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.<br />
<br />
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 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.<br />
<br />
== 3. Get payout addresses ==<br />
<br />
At the end of the JSON contract file you can also find the intended payout address for each trader:<br />
<nowiki><br />
makerPayoutAddressString:<br />
takerPayoutAddressString:</nowiki><br />
<br />
== 4. Recreating Redeem script ==<br />
<br />
For all the web interactions use the Tor browser. <br />
# Go to the [http://4zpinp6gdkjfplhk.onion Coinbin web wallet]:<br />
# At the top click <code>New</code> and from the dropdown menu choose <code>MultiSig Address</code><br />
# Paste the three public keys in the following order<br />
## Arbitrator<br />
## BuyerMultiSigPubKeyHex<br />
## SellerMultiSigPubKeyHex<br />
# Click submit 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.<br />
# Copy and save the Redeem Script.<br />
<br />
== 5. Creating transaction ==<br />
<br />
Again, click <code>New</code> at the top, but this time choose <code>Transaction</code> from the dropdown menu.<br />
# 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.<br />
# For the first input fill in an address from **makerPayoutAddressString** and the respective trade amount.<br />
# 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.<br />
# Click <code>submit</code>. You should now have an encoded transaction string. <br />
# Copy and save the transaction.<br />
<br />
== 6. Verify transaction ==<br />
<br />
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.<br />
<br />
== 7. Sign transaction ==<br />
<br />
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.<br />
<br />
To find the private key, search your bisqWallet.txt file for the value of the BuyerMultiSigPubKeyHex (or SellerMultiSigPubKeyHex if you're the seller), which you got on step 2. The private key beginning with "priv WIF=" is written just after the search result. Ensure that the pasted private key is just the part after the "priv WIF=".<br />
<br />
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.<br />
<br />
== 8. Second signature and broadcast ==<br />
<br />
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 from step 1 on the “Private key” text field and the encoded transaction shared with you in the text field below. Then, click “Submit”. You should get a new encoded transaction string. Copy and save it.<br />
<br />
You can verify the transaction before broadcasting.<br />
<br />
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”.<br />
<br />
After all is done, delete the bisqWallet.txt file you created on step 1.</div>Kemccall