TypedData.EncodeData should not reject a Domain without a ChainId#21306
Merged
holiman merged 2 commits intoethereum:masterfrom Aug 3, 2020
curvegrid:fix-eip712-domain-no-chainid
Merged
TypedData.EncodeData should not reject a Domain without a ChainId#21306holiman merged 2 commits intoethereum:masterfrom curvegrid:fix-eip712-domain-no-chainid
holiman merged 2 commits intoethereum:masterfrom
curvegrid:fix-eip712-domain-no-chainid
Conversation
holiman
reviewed
Aug 2, 2020
| } | ||
|
|
||
| if len(domain.Name) == 0 && len(domain.Version) == 0 && len(domain.VerifyingContract) == 0 && len(domain.Salt) == 0 { | ||
| if domain.ChainId == nil && len(domain.Name) == 0 && len(domain.Version) == 0 && len(domain.VerifyingContract) == 0 && len(domain.Salt) == 0 { |
Contributor
There was a problem hiding this comment.
Could you explain why you moved domain.ChainId == nil into this clause? I don't understand
Contributor
Author
There was a problem hiding this comment.
EIP-712 says the domain has to have at least one of the fields (chain ID, name, version, verifying contract or salt) (https://github.com/ethereum/EIPs/blob/master/EIPS/eip-712.md#definition-of-domainseparator)
I supposed this check was responsibile for enforcing that condition.
holiman
approved these changes
Aug 3, 2020
Contributor
|
Thanks! |
This was referenced Feb 24, 2021
enriquefynn
pushed a commit
to enriquefynn/go-ethereum
that referenced
this pull request
Mar 10, 2021
…a ChainId (ethereum#21306) * Do not check for a non-nil ChainId * Add encoding test
MariusVanDerWijden
pushed a commit
to MariusVanDerWijden/go-ethereum
that referenced
this pull request
Feb 2, 2026
…a ChainId (ethereum#21306) * Do not check for a non-nil ChainId * Add encoding test
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
3 participants
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.
This seems to be partially fixed by #19303, however the
.validate()method ofTypedDataDomainstill errors out when there is no chain ID.According to EIP 712,
chainIdis optional.I have removed the non-nil check and changed it so that validate only rejects completely empty domains. Tests included.
This change is