<p></p>
<p>Fair points indeed.  Using the venmo dictionary (or any other similar dictionary) is not good strategy.  However, I don't think the current approach is good enough and the situation could be improved quite a bit by:</p>
<p>a) trade IDs generated using a few different encodings/formats so that no single regular expression matches them.  Even 4-5 different encoding formats would go a long way in making the IDs "blend" better.</p>
<p>b) Users could use improvised payment descriptions that contain the ID, i.e. instead of "123123ABCD" one could include "Payment for #123123ABCD" or "Order #123123ACDB" - this way both parties would be able to recognize the transfer from the code (and the amount) yet the bank transfer can be virtually unrecognizable to third parties just by looking at the description.  The beauty of this approach is that it works right now, pretty much without an explicit agreement and protocol between the parties - people have been doing this for quite some time actually.</p>
<p>In order to facilitate b) I think a couple sentences describing this, near where the Trade ID is displayed, would suffice.</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/2869#issuecomment-626359912">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNTMZKE4H6IPSE7LJWDRQ3ONLANCNFSM4HS7RAMQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNRIFDIBN4SFUN5NRE3RQ3ONLA5CNFSM4HS7RAM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEVKX42A.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/2869#issuecomment-626359912",
"url": "https://github.com/bisq-network/bisq/issues/2869#issuecomment-626359912",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>