Does the Ceramic team still recommend storing encrypted data as described in this article? How to store signed and encrypted data on IPFS
This way of storing data relies on EIP-2844, but as far as I can tell there has been no progress on that EIP for quite some time (over a year), and according to the EIP itself it is not recommended to be used. I could be incorrect, but I believe that there are many wallets that wouldn’t be able to support this…
@jthor could you take a look at this?
EIP-2844 is not something that we are actively pursuing anymore. It’s still being used inside of various js-did libraries for legacy reasons, but we are likely to remove support in the future.
The main reason is that it’s really hard to get wallets to adopt a standard like this. We found the approach of using did:pkh and CACAO to create sessions much more powerful.
I used the tutorial above to learn how to use a DID (but not a wallet) in order to store signed and encrypted data. This is the only way I really know how to safely store private data on IPFS. Since EIP-2844 will be discarded, will this whole tutorial no longer be valid?
Should i learn how to store my private data on IPFS using did:pkh and CACAO? Kind of seems like those are for a different use-case, but im not quite sure.
did:pkh (and DID Sessions) does seem powerful to me, but it’s not 100% clear how it is used to encrypt data. Maybe updating the tutorial is necessary? I haven’t had time to do a deep dive on it yet, so maybe this is answered somewhere already
Yep, good point. The tutorial needs to be updated. One suggestion is to use the approach used here:
