Verifying Contract in eth_signTypedData

Open
  • Is something wrong?
#328 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
blockchain, documentation

Research direction

The issue names eth_signTypedData, DOMAIN_SEPARATOR, and the verifying contract but does not identify a documentation file or test. Start by locating the project’s existing signing and verification documentation, then clarify the explanation of replay protection and where it should be added; done means the role of the verifying contract is documented accurately.

Written by the indexing model from the issue text.

Description

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?

Dominant language
TypeScript
Stars
586
Forks
231
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MetaMask/eth-sig-util

All issues in MetaMask/eth-sig-util

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.