Thinking about approaches to simplify e2e encryption, this is one of the ideas that came to mind.

The seed then could further be used to encrypt the PDAs data.

Sharing the passphrase between the parties that should have access to the data would make this probably something one would call a symmetric cryptographic approach.

A sub-question to this would be whether the contents of a PDA seed are somehow publicly accessible (intentionally or accidentally, e.g., while browsing Solana Explorer).

I'm super new to cryptographic concepts, therefore some kindness and reasons whilst picking apart and destroying these thoughts would be superb.

1 Answer 1


I don't think it's a good idea to have any function to the passphrase other than to encrypt the data.

The program bytecode is public, and the raw transaction input is public. If that passphrase is ever included in a transaction, that will hint at or simply expose that passphrase, and if the data is also encrypted with the seed from that passphrase it will also decrypt the data.

That's a security self-sabotage you don't want to do when the simplest way to encrypt data end-to-end is to, well, to simply encrypt the data end-to-end.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.