gnunet-handbook

commit 05a479d3319f0048588a9ba3707dd9b9e29180ac
parent 65481c379b33bbc7f660fa84ba59a323aab24f53
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Mon, 24 Oct 2022 21:55:50 +0900

update new namestore API

Diffstat:
M
users/gns.rst
 | 
38
++++++++++++++++++++++++++++++++++++++

1 file changed, 38 insertions(+), 0 deletions(-)
diff --git a/users/gns.rst b/users/gns.rst
@@ -159,6 +159,44 @@ If you ever need to reset your zone database, you can use ``gnunet-namestore-dbt
 with the ``--reset`` option.
 **DANGER: This command will delete ALL of your records in all zones!**
 
+Orphaning
+"""""""""
+
+It can happen that you accidentally or semi-accidentally delete your ego, e.g.
+using ``gnunet-identity --delete=myzone``.
+In this case the records stored in the zone are still in the database but the
+missing ego causes them to be *orphaned*.
+
+Orphaned records are still published in the DHT but access to them is limited.
+For example, managing records through the NAMESTORE API is not longer possible.
+
+You can check for orphaned records using:
+
+::
+
+  $ gnunet-namestore --list-orphans
+
+This will output any orphaned records in the format
+
+.. code-block:: text
+
+  <$LABEL>.<$PRIVATE_KEY>:
+  $RECORD_DATA
+
+In order to recover (and un-orphan) the records, you can re-add the ego by
+executing
+
+::
+
+  $ gnunet-identity --create=<myzone> --privkey=$PRIVATE_KEY
+
+If instead you should decide that you want to **purge** all orphaned records,
+you can execute
+
+::
+
+  $ gnunet-namestore --purge-orphans
+
 Records
 """""""