How to Restore a Guarda Wallet Using a Backup File on a New Computer?

Understanding Guarda Wallet Backup Structure

1. Guarda Wallet generates a locally stored encrypted backup file named guarda-backup.json when users manually trigger the backup process inside the desktop or browser extension interface.

2. This file contains an encrypted version of the wallet’s seed phrase, public addresses, transaction history metadata, and associated encryption keys—none of which are transmitted to Guarda servers.

3. The backup file is password-protected using a user-defined recovery password; without this exact password, decryption fails regardless of file integrity.

4. Backup files do not include real-time balance updates—on restoration, the wallet must resync with blockchain nodes to fetch current UTXO states and token balances.

5. Guarda does not store or validate backup files on its infrastructure; users bear full responsibility for secure local storage and version control.

Step-by-Step Restoration Workflow

1. Install the official Guarda Desktop application from guarda.com/download—verify SHA256 checksum against values published on Guarda’s GitHub repository.

2. Launch the application and select “Restore Wallet” instead of “Create New Wallet” on the welcome screen.

3. Choose “Restore from Backup File”, then navigate to the location where guarda-backup.json was previously saved.

4. Enter the exact recovery password used during backup creation—case sensitivity and special character placement are enforced at runtime.

5. After successful decryption, Guarda initiates automatic blockchain synchronization; restoration completes only after confirmed block headers reach the latest network height.

Common Failure Scenarios and Diagnostics

1. If the app displays “Invalid backup format”, the file may have been edited in a text editor, corrupted during transfer, or generated by an outdated Guarda client version older than v4.12.0.

2. A “Password mismatch” error persists even with correct input when Unicode normalization differences exist—users should avoid copying passwords from rich-text sources like email clients or messaging apps.

3. When restoration halts at 98% sync, it indicates incomplete node response—switching to a different RPC endpoint under Settings > Network often resolves stalled synchronization.

4. If imported addresses show zero balances despite confirmed on-chain transactions, verify that the backup file was created after all relevant receiving addresses were generated and used—not before first deposit.

5. No recovery is possible if the backup file was overwritten by a subsequent backup containing fewer wallets or different derivation paths.

Security Validation Post-Restoration

1. Cross-check the first five characters of each restored wallet’s public address against known prior addresses displayed in the original wallet’s asset list.

2. Initiate a test transaction of minimal value to a trusted external address and confirm receipt within three network confirmations.

3. Export the newly restored wallet’s public key details and compare cryptographic fingerprints (e.g., SHA3-256 hash of concatenated xpubs) with archived records.

4. Audit active staking positions or DeFi contract allowances through Etherscan or Solscan using restored addresses—unexpected approvals indicate compromise.

5. Disable auto-sync features in Guarda settings until manual verification of all imported assets is complete.

Frequently Asked Questions

Q: Can I restore a Guarda backup file created on Windows to a macOS installation?A: Yes—Guarda backup files are cross-platform compatible as long as both installations use v4.10.0 or later and share identical encryption protocol versions.

Q: Does restoring overwrite existing wallets in the current Guarda instance?A: No—restoration adds imported wallets as new entries; pre-existing wallets remain untouched unless explicitly deleted by the user.

Q: What happens if I enter the wrong password ten times consecutively?A: Guarda enforces no lockout policy—the application permits unlimited attempts but logs failed entries locally for forensic review.

Q: Is it safe to store guarda-backup.json in cloud services like OneDrive or Google Drive?A: Only if the file remains encrypted at rest and access permissions are strictly limited—Guarda itself does not encrypt backups beyond the initial password-derived key.