@ -32,9 +32,9 @@ We have a document that explains a lot of terminology [here](https://git.hush.is
The default location on Linux for the HUSH config file is `~/.hush/HUSH3/HUSH3.conf` . This file will have a username and password for RPC
access, so don't show the contents to untrusted people. The legacy location used to be `~/.komodo/HUSH3/HUSH3.conf` . You can move the old legacy directory to the new location and it will be found and used.
An advanced feature we suggest exchanges & pools use is called `consolidation=1` which keeps wallets small and hence fast.
An advanced feature exchanges & pools can use is called `consolidation=1` which keeps wallets small and hence fast.
This feature will always make small transactions in the background, "consolidating" funds into very efficient amounts. This
makes future transactions fast by spending small amounts of time consolidating funds in the background.
makes future transactions fast by spending small amounts of time consolidating funds in the background. We note that turning on consolidation for an already very large wallet will have performance issues.
Here is an example config file for HUSH which is recommended for exchanges and mining pools:
@ -57,6 +57,9 @@ consolidation=1
* Shielded transactions do not show the sender address, receiver address or amounts on the public explorer. You will need to use local RPC methods such as `z_viewtransaction` to see those details
* Shielded transactions are larger than transparent transactions, because more data is stored
* RPCs which work with zaddrs usually begin with `z_` such as `z_listunspent`. The very common `sendmany` RPC is called `z_sendmany` for zaddrs
* To generate a new zaddr use `z_getnewaddress`
* To see the balances of all zaddrs use `z_getbalances`
* Do not use `z_getbalance` for each zaddr in the wallet, that will be drastically slower
