Encrypted recovery

Backup & Restore

Create an encrypted backup, test recovery readiness, and review local or optional decentralized mirror status.

🔐 Backup & Restore

Your vault lives on this device. Export regularly so you can recover your identity, API keys, subscriptions, attachments, and earned rewards on any device.

💾 Export Vault

Choose a strong passphrase — you will need it to restore. The export includes app-owned localStorage state and is always encrypted for launch safety.

Encryption passphrase (required) Use at least 12 characters. This passphrase is required for restore and cannot be recovered by EONAPP.

📂 Restore Vault

Choose your vault backup file and enter the passphrase used when you exported it.

Vault backup file (.json or .eon)

🔑 Recovery Phrase

Generate a 12-word recovery phrase to back up your vault identity. Write it down and store it safely — it is shown once and never saved on this device.

⚠️ Write these words down now. This is the only time they will be shown.

Recommended backup locations

Google Drive ↗ iCloud ↗ OneDrive ↗ Dropbox ↗ or email it to yourself — any safe, private location works.

🛟 Account Survival Drill

CEO rule: users must not lose NFTs, receipts, API-key status, rewards, identity, or local settings during Cloudflare updates. This drill proves the local-first recovery path before paid traffic.

01Local-first source of truthNo traditional account database is required to keep user-owned app data alive.

02Encrypted exportAES-GCM backup with passphrase, payload hash, and update-survival manifest.

03Restore drillImport replaces only app-owned state, then runs restore/update-survival receipts.

04Optional mirror choiceUsers may store encrypted copies on cloud, USB, email, IPFS, Arweave, or other private storage.

Review identity Review API-key status

Run the survival check to see backup readiness, restore attempt budget, local key count, recovery phrase status, and update-survival proof.

Central database decision: keep the consumer Vault local-first. Use Cloudflare Workers only for signed entitlement/status proofs and optional encrypted snapshots — never as the only copy of user NFTs, receipts, API-key status, or identity.

Security + storage posture

Encrypted vault export remains the hard backup layer. The site stays local-first, while signed Worker snapshots are used only for mutable claim and entitlement data.

P2P Network Status

Decentralized relay health — Nostr relays for challenge discovery and referral proof broadcasting.

Checking relay connections…