Different behavior of 'eth_sign' between MetaMask and ETH Rpc api
Open
- Dominant language
- TypeScript
- Stars
- 268
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
refs to https://github.com/ChainSafe/web3.js/issues/4780#issuecomment-1049094336
Now we can only sign 32 bytes hash in [metamask](https://docs.metamask.io/guide/signing-data.html#a-brief-history).
But there's no limit in [ETH RPC Api](https://eth.wiki/json-rpc/API#eth_sign)
Is there a reason why metamask give the limit?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked web3.js issue comment and the MetaMask signing-data and ETH JSON-RPC API references cited in the report. Compare the documented eth_sign input limits and behavior, then record the reason for the difference and the expected compatibility decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100