Skip to content

Verifying Contract in eth_signTypedData #328

@sajadmeisami

Description

@sajadmeisami

I appreciate it if you could explain to me how a verifying contract can prevent a replay attack.
Based on my research, a verifying contract is simply a string inside the DOMAIN_SEPARATOR, and every other contract can copy it when they know its value. Please explain how it exactly plays a role in Reply protection?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions