Implement forward secrecy by creating E3 keys

[ryardley]

We currently save all encrypted state using a key derived from the passphrase that the node operator selects.
We are using eventsourcing now however so we should attempt to add some forward secrecy.
We should use E3 keys that are saved encrypted in a KV store but then purged once an E3 round is finalized

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• enclave#152

Related Issues

• Create an "encrypted" Repository #193
• When deleting keyshare ensure that persisted state is cleaned up #152
• Add autokey functionality for ciphernodes #353
• Secure cipher.rs #787
• Ciphernode Recover from shutdown #144

👤 Suggested Assignees

• ryardley

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!