-
Notifications
You must be signed in to change notification settings - Fork 196
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
feat(world-modules): string systemId in callWithSignature
typehash
#2700
Conversation
🦋 Changeset detectedLatest commit: dfe0a7b The changes in this PR will be included in the next version bump. This PR includes changesets to release 24 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -34,7 +37,9 @@ function getSignedMessageHash( | |||
abi.encodePacked( | |||
"\x19\x01", | |||
domainSeperator, | |||
keccak256(abi.encode(CALL_TYPEHASH, signer, systemId, keccak256(callData), nonce)) | |||
keccak256( | |||
abi.encode(CALL_TYPEHASH, signer, keccak256(abi.encode(systemId.toString())), keccak256(callData), nonce) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want to do a straight cast of systemId
here, not systemId.toString
, as toString
is more meant as the human-readable version for logging/debugging (e.g. sy:<root>:Register
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I didn't think about that! thanks
callWithSignature
typehash
changeset? |
Making signatures more legible with a
string
systemId