MetaMask / MetaMask/metamask-extension
Eth_decrypt is not supported anymore?
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
Hi i asked for support regarding this function and was directed to ask for help here instead,
https://github.com/ethers-io/ethers.js/discussions/4889
eth_decrypt used to work but now its throwing this rejected error even after signing the tx
```
Error: user rejected action (action="unknown", reason="rejected", info={ "error": { "code": -32603, "data": { "originalError": { } }, "message": "MetaMask DecryptMessage: User denied message decryption." }, "payload": { "id": 9, "jsonrpc": "2.0", "method": "eth_decrypt", "params": [ "cynO2IeYe/weLFuV3/Ec2hhpxFFg5OU=", "
```
referenced the following PR and verified my implementation coherent with x25519-xsalsa20-poly1305
https://github.com/ethers-io/ethers.js/issues/4139
i even tried on the docs and its throwing the same error
https://docs.metamask.io/wallet/reference/json-rpc-methods/eth_decrypt/
is eth_decrypt finally deprecated and no longer supported? is there a suggested workaround to decrypt cipherTexts?
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [X] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
https://github.com/ethers-io/ethers.js/discussions/4889
https://docs.metamask.io/wallet/reference/json-rpc-methods/eth_decrypt/
Contributor guide
Research direction
Review the linked discussion, issue 4139, and MetaMask eth_decrypt documentation, then reproduce the reported rejection with the JSON-RPC method. Establish whether the method remains supported and document a confirmed workaround or the required product change; the issue currently names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, cryptography, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100