-
-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to backup and restore your application directory #1279
Comments
Related issue: haveno-dex/haveno-docs#16 |
This helps a lot. Can using the share app on windows and then emailing it to yourself also save your data? Or does that only share the app itself? Thanks |
You can backup your application directory any way you like, though it's probably too big to be sent over email, since it can be 100s of mbs. Be sure to backup your application directory and not the application itself, by creating a backup from within the app or by copying your application directory manually to a location of your choice. The application directory is located at:
|
This helps a lot. One more question: if the Monero is in the security deposit, your seed phrase and date would not be able to recover it correct? |
Correct, because the funds are held in a multisig wallet, so your backup needs to contain that wallet for you to recover the funds by completing the trade. |
This issue requests documenting how to backup and restore your application directory in the docs repository, as it's a frequently asked question.
To summarize:
Go to Account > Backup > Select backup location.
This will save your entire application directory to a location of your choice.
The backup includes your main wallet and the current state of your offers or trades. You should create a new backup in order to include any new or updated offers or trades.
To restore, you can install Haveno, then copy your backup folder as your main application folder, located at:
Note: replace "Haveno" with the name of the third party network you're using, if applicable.
The text was updated successfully, but these errors were encountered: