<p></p>
<p>Hm... that is always tricky. I think with Revolut it was similar but there was some solution. I would need to dig deeper to figure it out. I think excluding it from json was the solution...It is not a critivcal field so I don't see any problem to not have that in the contract.</p>
<p>From RevolutAccountPayload:</p>
<pre><code> // For backward compatibility we need to exclude the new field for the contract json.
    // We can remove that after a while when risk that users with pre 1.3.8 version trade with updated
    // users is very low.
    @JsonExclude
    @Getter
    private String userName = "";
</code></pre>

<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/pull/5117#issuecomment-772702392">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNRCATZ7HHN3ZBKNXODS5GE4JANCNFSM4WSZ3CCQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNQ37ZJ4FYXEF3G7SIDS5GE4JA5CNFSM4WSZ3CC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFYHIBOA.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/pull/5117#issuecomment-772702392",
"url": "https://github.com/bisq-network/bisq/pull/5117#issuecomment-772702392",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>