Feature: Encrypted Vault Backup & Restore (Offline Archive)

Open
  • Is something wrong?
#13 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
data, security

Research direction

Start by locating how the encrypted vault stores notes, vector memories, and action history, then read the existing key derivation and encryption paths. Define a versioned .yaanvault format that can export and restore those records offline, with password-based encryption and integrity verification. Done means an export can be restored on another device and corrupted or invalid-password archives are rejected.

Written by the indexing model from the issue text.

Description

enhancement
Summary

Enable users to export their encrypted notes, vector memories, and action history into an encrypted export file (.yaanvault) that can be restored on another device without relying on a network sync relay.

Scope
  • Password-derived key (PBKDF2/Argon2 + AES-GCM).
  • Export payload includes schema versioning.
  • Verification checksum / HMAC to prevent corrupted restores.
Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
25m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentwithyash/yaan

All issues in developmentwithyash/yaan

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.