From b4d5a1f6a0eb77a5e84adcb9a8f9068ebea90729 Mon Sep 17 00:00:00 2001 From: Oliver Gugger Date: Thu, 12 Oct 2023 19:12:59 +0200 Subject: [PATCH] Update docs/safety.md Co-authored-by: dstadulis <15150758+dstadulis@users.noreply.github.com> --- docs/safety.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/safety.md b/docs/safety.md index 1451f26bd..ad2e402f5 100644 --- a/docs/safety.md +++ b/docs/safety.md @@ -16,9 +16,11 @@ using only the `lnd` seed. If `tapd`'s database is lost or corrupted, access to all assets minted or received by that `tapd` **is lost**. Additionally, custody the BTC, used to carry/anchor the assets would also be lost. -**To avoid loss of funds, make sure you back up your `/home//.tapd` folder -regularly.** If you are using a Postgres database as the database backend, it -is enough to make backups of that database. +**To avoid loss of funds: +1) make sure the `/home//.tapd` directory is backed up regularly.** If `tapd` is configured to use Postgres as the database backend, backups this database is +sufficient to preserve access to funds. +2)`lnd`'s seed phrase has been securely backed up, as all `tapd` assets private +keys are derived from it. And of course, you also need `lnd`'s seed phrase which is what all private keys for all assets in a `tapd` instance are derived from.