Alternatives to depreciated requests eth_decrypt and eth_getEncryptionPublicKey

[TechnicallyWeb3]

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/

[jdbertron]

Can we please get a response for this ? What is the alternative ?