Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix verifyingContract to be a valid evm hex address (using cosmos as hex address) #9

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

randy75828
Copy link
Collaborator

image

MetaMask (currently only the extension) has added a new validation that requires the verifyingContract field in the EIP-712 JSON to be a valid EVM address. This change is causing issues because our verifyingContract is set to 'cosmos', preventing users from submitting transactions on Carbon via MetaMask.

To resolve this, we need to update verifyingContract to any valid hex address, but this will require a backend upgrade.

below is an issue created by another team which is facing the same issue:

MetaMask/metamask-extension#26980

this is prob the quickest fix cos not sure when metamask team will update

the hex address can be anything, just need to follow the spec.

relevant portion of the code in metamask extension source code:

image

Edit: We have decided to go ahead with the hex representation of 'comsos' as the hex address

@yan-soon yan-soon merged commit 1877433 into sdk-v0.50.5 Sep 9, 2024
10 of 16 checks passed
@yan-soon yan-soon deleted the fix/metamask-signing branch September 9, 2024 09:37
@yan-soon yan-soon restored the fix/metamask-signing branch September 13, 2024 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants