we could have great things but metamask depreciated eth_getEncryptionPublicKey and eth_decrypt

we have a hack-job way of using it w/ hardware wallets and such but somewhat concerned they're just gonna nuke it out of the API one day

nobody has been able to tell me why they "could not be perfectly confident in its safety" -- any ideas?

https://medium.com/metamask/metamask-api-method-deprecation-2b0564a84686

What apps are relying on this in production right now? I might be able to help here.

Building ponder.sh. EVM, TypeScript, open-source enjoyer.

we're using it still! well, we're doing quasi commit and reveal, bidder commits to a sellers specific (burner) EOA they designate, then the seller posts the private key on-chain to mass reveal all private bids at end --- but working with hardware wallets has been pain in the ass, works OK on metamask for now still tho

went down this rabbit hole last year while trying to store burner account private keys on-chain. rip the dream

This becomes a problem insofar as EOAs remain more popular than smart contract wallets. I believe this will flip as L2s have native account abstraction and L1 improves the base layer for the same.
That being said more ppl should just use the magic of the ENS Registry, it's the best KV store where you could put a pubkey

We could have user-friendly version of pgp but nooooooo