Add legacy EIP-1271 support (i.e. 'isValidSignature(bytes,bytes)') #29
Conversation
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
sidnym-ladrut
changed the title
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.
Early versions of EIP-1271 called for a validation function with signature
isValidSignature(bytes,bytes) => (bytes4). Notably, this is the only version of the signature standard supported by by SAFE v1.*.*.In order to enable support for SAFE v1.*.* contracts (and any other legacy EIP-1271 targets), these changes add the
isValidSignature(bytes,bytes) => (bytes4)signature as an overloaded alternative to the modernisValidSignature(bytes32,bytes) => (bytes4)signature.