<p>I've added another verification method above.</p>
<blockquote>
<p><strong>6. Verify photo id data with app like ProofMode (buyer sends seller signed picture of their face, which seller can verify was taken within the past few minutes, has adequate likeness, and was taken at the location on the actual id)</strong></p>
<p>Basic idea here is that the user includes a photo id (driver's license, debit card, etc) with sensitive/unnecessary information blurred out (driver's license number, debit card number, etc should NOT be shown), leaving only information that's revealed in the payment method (full name, maybe address, etc).</p>
<p>This method would be easy for a scammer to exploit, in theory, as they could simply photoshop the original picture id with information they can control, but keep in mind that if a scammer decides to photoshop an id with their own face, they'd have to show their own face, which is highly unlikely. A more likely attack vector is for the scammer to hire a rightful account owner to do this for them, but again -- such a practice would be impractical for a scammer to do consistently, and easy for an honest user to do consistently.</p>
<p>As with the other methods listed here, this method would need to be used in conjunction with another method above for it to have any strength.</p>
<ul>
<li>Verifies: face, address</li>
<li>Integrity: derived from difficulty of spoofing GPS and/or facial appearance (or from the spammer's willingness to show their own face, or from the scammer making the effort to get the rightful account owner to show their face for every trade)</li>
<li>Ease: easy</li>
<li>Downside: user has to show their face</li>
<li>Privacy: with adequate blurring, photo id shouldn't show any additional information (beyond picture of face) that's not already revealed in the payment account.</li>
</ul>
</blockquote>

<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/83?email_source=notifications&email_token=AJFFTNSE67ZE27MIZCKLVO3PWVCR7A5CNFSM4HLNAEK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7A6XY#issuecomment-494800735">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUDQYAALLXJL77ZFPTPWVCR7ANCNFSM4HLNAEKQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AJFFTNQXUOXU7H4RTT22KUTPWVCR7A5CNFSM4HLNAEK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7A6XY.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/83?email_source=notifications\u0026email_token=AJFFTNSE67ZE27MIZCKLVO3PWVCR7A5CNFSM4HLNAEK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7A6XY#issuecomment-494800735",
"url": "https://github.com/bisq-network/proposals/issues/83?email_source=notifications\u0026email_token=AJFFTNSE67ZE27MIZCKLVO3PWVCR7A5CNFSM4HLNAEK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV7A6XY#issuecomment-494800735",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>