<p></p>

<h3>Description</h3>

<p>At present, in the rare cases Mediators need to create manual payout transactions to release the funds from the multisig, they need to request the private keys of both traders and sign the transaction for them. This is a terrible violation of one of the core Bitcoin principles.</p>
<h3>Expected behaviour</h3>

<p>Once a trader opens mediation the mediator gets access to the trade's contract with all the necessary information to create the transaction. They should do so and share the unsigned transaction to the traders so they can sign and broadcast it.</p>
<h3>Actual behaviour</h3>

<p>The mediator creates. signs the transaction for both traders and broadcasts it.</p>
<h3>Screenshots</h3>

<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/44140017/76680743-19059800-65e3-11ea-8a86-626bebbd565a.png"><img src="https://user-images.githubusercontent.com/44140017/76680743-19059800-65e3-11ea-8a86-626bebbd565a.png" alt="emergencyMultisigPayoutTool" style="max-width:100%;"></a></p>
<h4>Additional info</h4>

<p>I've created a guide for an <a href="https://bisq.wiki/Manual_payout" rel="nofollow">alternative method using tools outside of Bisq</a>. It'd be great if we could add the following functions to the Bisq software:</p>
<ol>
<li>verify and sign message with a specific address</li>
<li>verify and sign a transaction</li>
<li>encrypt and decrypt message with a specific address</li>
</ol>
<p>It's imperative that the sign, encrypt and decrypt functions are done inside the Bisq software due to the need of private key. Electrum and Coinbin's UI may be worth copying.</p>
<p>Related<br>
<a href="https://docs.bisq.network/manual-dispute-payout.html" rel="nofollow">Legacy Manual payout process</a><br>
Update to new protocol - <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="528902442" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/3694" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq/pull/3694/hovercard" href="https://github.com/bisq-network/bisq/pull/3694">#3694</a></p>
<p>ping <a class="team-mention js-team-mention" data-error-text="Failed to load team members" data-id="3440888" data-permission-text="Team members are private" data-url="/orgs/bisq-network/teams/mediators/members" data-hovercard-type="team" data-hovercard-url="/orgs/bisq-network/teams/mediators/hovercard" href="https://github.com/orgs/bisq-network/teams/mediators">@bisq-network/mediators</a> <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/wiz/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/wiz">@wiz</a> <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/Bisq-knight/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/Bisq-knight">@Bisq-knight</a></p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/issues/4061">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNWBJ2TDU6K477ZVARTRHNRIHANCNFSM4LI3OOTA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNS2UGTWFIVGEBYILDLRHNRIHA5CNFSM4LI3OOTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IVDZWQA.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/issues/4061",
"url": "https://github.com/bisq-network/bisq/issues/4061",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>