From b919012b1ec08dc591f2b83975567f460c032091 Mon Sep 17 00:00:00 2001 From: Deirdre Connolly Date: Wed, 12 Aug 2020 12:33:01 -0400 Subject: [PATCH] Monospace 'wallet.dat' --- zip-0400.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/zip-0400.rst b/zip-0400.rst index da62eb2d..e57e2fa1 100644 --- a/zip-0400.rst +++ b/zip-0400.rst @@ -18,7 +18,7 @@ RFC 2119. [#RFC2119]_ Abstract ======== -This proposal defines the current zcash format for wallet persistence storage commonly known as wallet.dat. +This proposal defines the current zcash format for wallet persistence storage commonly known as ``wallet.dat``. Motivation ========== @@ -28,7 +28,7 @@ The process of saving wallet data into disk is currently unspecified. The key-va Specification ============= -Zcash stores wallet information in a Berkeley database(BDB) [#BDB]_ commonly known as wallet.dat. +Zcash stores wallet information in a Berkeley database (BDB) [#BDB]_ commonly known as ``wallet.dat``. The main purpose of this is the persistence of public and private keys the user created and the ability to recover the wallet state after a node restart. This file also allows the migration of user information from one node to another by moving the database to the corresponding new datadir assuming both zcashd instances are running the same or similar version. The current database is a key-value store where keys and values can have multiple data types in binary format. The first data found in a database key is always the property name, the rest of the key is generally used to identify a record, for example::