fix: disable EIP-2612 permits for tokens with non-ASCII names #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which Jira task is linked to this PR?
LF-16416
Why was it implemented this way?
This PR disables permit usage for tokens whose contract name includes the ₮ character (specifically USD₮0) in the SDK.
Ledger devices currently freeze and crash when signing EIP-712 typed-data permits for this token due to the non-ASCII character in the name field. Since the domain name must match the on-chain token name exactly, we cannot safely normalize or replace the character client-side without breaking signature validation.
Temporary fix:
Fallback to standard approval flow for USD₮0 in the SDK to avoid hardware wallet signing failures.
Impact:
No functional change for non-affected tokens.
Users holding USD₮0 on supported chains will complete approvals via the standard approve transaction instead of permit.
We’ll re-enable permits once Ledger resolves Unicode support in typed-data signing.
Checklist before requesting a review