fix(api): remove strict 130-char signature length regex to support EIP-1271 smart account signatures (#8008) - #8049
Open
TanmayDagur wants to merge 1 commit into
Conversation
…P-1271 smart account signatures (Uniswap#8008)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📝 Overview & Problem
This PR resolves Issue #8008, where users leveraging Smart Contract Wallets (e.g., Safe, Ambire, Argent, Biconomy) encounter client-side and OpenAPI schema validation errors when signing transaction steps or placing Limit Orders/UniswapX trades:
{ "detail": "\"signature\" with value \"0xf0640...\" fails to match the required pattern: /^0x[0-9,a-z,A-Z]{130}$/", "errorCode": "VALIDATION_ERROR" }