@clareifi.com What now?

@clareifi.com Ha! “hard mode” 4sure. Debugging decryption failures with zero server-side visibility is a special kind of pain.

Next - Phase 3 envelope key architecture for key rotation, public profiles and selective sharing. Security audit before anything goes beyond personal use.

Thanks for following along 🔐

@clareifi.com Server never saw plaintext. Architecture held.

clareifi.xyz

#BuildInPublic #Privacy #E2EE

@clareifi.com it makes debugging harder.

What shipped:
→ Supabase auth (email + password)
→ Salt stored server-side, key derived client-side
→ New device fetches salt, derives correct key, decrypts notes
→ Tested: Chrome, Brave, Vivaldi, Samsung Internet — all working

@clareifi.com Fair point — an envelope key now is cleaner than re-wrapping everything at rotation time. It’s on the roadmap.

Phase 2 is shipping working sync. Phase 3 is where the key hierarchy gets more sophisticated. Building deliberately, not just fast.