<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=170962" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ripcurlx">@ripcurlx</a> fantastic work! Some thoughts:</p>
<ol>
<li>
<p>I think having the "Account signing unlocked" modal appear at startup is a good idea.</p>
</li>
<li>
<p>Should we add some kind short text about liability in the modal where the seller confirms payment? Something to the effect of "it's important that you're honest here, for the health of the network, but it's not a personal endorsement that you'll be personally liable for if something goes wrong down the line". I'm anticipating people might be concerned that clicking that button might make them culpable down the line if the other person turns out to be a scammer.</p>
</li>
<li>
<p>Icons are tricky. Personally I don't immediately understand the distinction between a plain dollar sign and a dollar sign with a cloud around it. I suggest we use the same icon and differentiate with colors instead. Perhaps we use yellow for unsigned (concern, caution) and green for signed. Red would convey danger, which wouldn't be appropriate.</p>
</li>
</ol>
<p>Since it seems this icon will only indicate time since signing, how about we use a clock?</p>
<p><a target="_blank" rel="noopener noreferrer" href="https://user-images.githubusercontent.com/735155/61467961-86750200-a94a-11e9-9e17-b93a94a82b7b.png"><img src="https://user-images.githubusercontent.com/735155/61467961-86750200-a94a-11e9-9e17-b93a94a82b7b.png" alt="Screenshot from 2019-07-18 10-53-31" style="max-width:100%;"></a></p>
<p>Yellow clock for unsigned, and green clock for signed. Then (if you agree with the thought below), the user could check the peer info box for more details on the signing.</p>
<blockquote>
<p>if we are going to show other verification methods in the UI.</p>
</blockquote>
<p>I'd like to see that, if only to give users a hint of the software's future direction.</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/proposals/issues/93?email_source=notifications&email_token=AJFFTNREANZLED6466KPAQ3QACASFA5CNFSM4HOMXIY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IYM3I#issuecomment-512853613">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNSCP2JJ7ZNW7DZSMXLQACASFANCNFSM4HOMXIYQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNSD4QMMBKLDV6FWFKTQACASFA5CNFSM4HOMXIY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IYM3I.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/proposals/issues/93?email_source=notifications\u0026email_token=AJFFTNREANZLED6466KPAQ3QACASFA5CNFSM4HOMXIY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IYM3I#issuecomment-512853613",
"url": "https://github.com/bisq-network/proposals/issues/93?email_source=notifications\u0026email_token=AJFFTNREANZLED6466KPAQ3QACASFA5CNFSM4HOMXIY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2IYM3I#issuecomment-512853613",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>