From 381077255aed3ee492f10940a02ca77ce9842795 Mon Sep 17 00:00:00 2001 From: Duke Leto Date: Sun, 5 Jun 2022 04:10:59 +0000 Subject: [PATCH] Update 'README.md' --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 4943c80..be1a0f5 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,9 @@ consolidation=1 * If a certain zaddr has more than 30 zutxos (items in the array output of `z_listunspent`) it's likely they are mining to the exchange, or sending many small deposits * You can then manually inspect these user accounts or send them a message to not mine to the exchange * The `rescan` RPC in Hush 3.9.1 can be used to rescan from any block height, which minimizes downtime. - * Example usage: `hush-cli rescan 123456` + * Example usage: `hush-cli rescan 123456` + * Another important way to minimize downtime is the use the `-keepnotewitnesscache` option to hushd, for instance: + * `hushd -keepnotewitnesscache -rescanheight 123456` will greatly speed up rescanning by only updating the Sapling zaddr witness cache instead of calculating it from scratch * It's best to only send payouts a few times per day (such as 2 or 3) instead of when they are above a threshold. * This will make pool wallets smaller and faster, miner wallets smaller and faster, and exchange wallets smaller and faster (because miners often mine directly to pools) * For exchanges, you can limit how many withdrawals a user can do per day, such as 3, and show them how many they have left. This will help keep wallets small and fast.