Alternatives to depreciated requests eth_decrypt and eth_getEncryptionPublicKey

### What is this about?

I’m building an encrypted messaging service using MetaMask. I saw that eth_decrypt and eth_getEncryptionPublicKey are deprecated, but I rely on these methods to send and read encrypted messages.

How will I be able to take an encrypted message and decrypt it once these methods are completely deprecated? Is there a timeframe until they disappear completely?

If there is no plan to replace these methods I’m here to plead you to reconsider. I was hoping to build a suite of dapps around these encryption methods.

### 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

- [ ] 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://docs.metamask.io/wallet/reference/eth_getencryptionpublickey/?Address=0x7b9a421575f72D17331CA7433aeA46eC5d5B2739

https://docs.metamask.io/wallet/reference/eth_decrypt/

Start by reviewing the linked eth_getEncryptionPublicKey and eth_decrypt documentation and the existing issue discussion. The issue names no implementation files, tests, replacement design, or acceptance criteria; progress would require defining a supported alternative and documenting its deprecation timeline.

Written by the indexing model from the issue text.