From f6dcf0fe786dc66235a3992205446244e754c707 Mon Sep 17 00:00:00 2001 From: Deirdre Connolly Date: Wed, 12 Aug 2020 13:03:14 -0400 Subject: [PATCH] Clarify RPC call to z_getnewaddress Co-authored-by: Daira Hopwood --- zip-0400.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/zip-0400.rst b/zip-0400.rst index a6ffc710..23b661c1 100644 --- a/zip-0400.rst +++ b/zip-0400.rst @@ -103,7 +103,7 @@ The following flow will happen when a node with wallet support is started for th * If the wallet is created with HD support, it will have additional properties ``hdseed`` and ``hdchain`` that will be saved. * ``version``, ``minversion``, ``witnesscachesize`` and ``bestblock`` properties are added. These are settings and state information: the ``bestblock`` property is a good example of the database being populated that is happening without any user interaction, but it will just update as the best block of the current chain changes. -At any time after the database is created new properties can be added as the wallet users do actions. For example, if the user creates a new sapling address with the rpc command ``getznewaddress()`` then new records with properties `sapzkey` and `sapzkeymeta` will be added to the database. +At any time after the database is created, new properties can be added as the wallet users perform actions. For example, if the user creates a new Sapling address with the RPC command ``z_getnewaddress`` then new records with properties `sapzkey` and `sapzkeymeta` will be added to the database. In zcashd, database changes do not happen immediately but they are flushed in its own thread by ``ThreadFlushWalletDB()`` function periodically to avoid overhead. The internal counter ``nWalletDBUpdated`` is increased each time a new write operation to the database is done, this is compared with the last flush in order to commit new stuff.