MetaMask / MetaMask/eth-sig-util
Verifying Contract in eth_signTypedData
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 583
- Forks
- 228
- Avg merge
- 11h 22m
- Merged PRs (30d)
- 7
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100