-
Notifications
You must be signed in to change notification settings - Fork 71
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
Map domainHash
/messageHash
to MULTISIG
transactions and messages
#2180
Open
iamacook
wants to merge
8
commits into
main
Choose a base branch
from
domain-message-hashes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
iamacook
changed the title
Add
Map Dec 9, 2024
domainHash
/messageHash
to detailedExecutionInfo
of MULTISIG
transactionsdomainHash
/messageHash
to MULTISIG
transactions and messages
iamacook
commented
Dec 9, 2024
Comment on lines
+625
to
+631
it('these tests should cover up to the current version', () => { | ||
const deployment = getSafeL2SingletonDeployment(); | ||
|
||
expect(DOMAIN_TYPEHASH_NEW_VERSIONS.at(-1)).toBe(deployment?.version); | ||
expect(SAFE_TX_TYPEHASH_NEW_VERSIONS.at(-1)).toBe(deployment?.version); | ||
expect(SAFE_MESSAGE_TYPEHASH_VERSIONS.at(-1)).toBe(deployment?.version); | ||
}); |
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 added this to ensure we check new hashes match, should the typehashes be altered.
3 tasks
…G` transactions
iamacook
force-pushed
the
domain-message-hashes
branch
from
December 18, 2024 06:57
bb07f81
to
1a9c559
Compare
PooyaRaki
approved these changes
Jan 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
The hashes of an EIP-712 domain/message can be used to verify the legitimacy of a transaction. On the Web interface, these two values are calculated dynamically for each transaction/message.
This calculates/maps a new
typedData
, containingdomainHash
andmessageHash
to thedetailedExecutionInfo
ofMULTISIG
transactions and messages, allowing the client to render it directly.Note: messages can only be initially proposed with a signature so we need take into consideration whether it influences the viability of this.
Changes
TypedDataMapper
for dynamically calculatingtypedData
hashes.typedData
properties toMessage
andMultisigExecutionDetails
entities.