The only official place to get Hush source code and binaries is git.hush.is, which is the Hush Gitea instance, which replaces Github.
Glad you asked! We would like to support as many as we can, but currently our Officially Supported OS's are:
First you must decide if you will compile Hush yourself, or use binaries. Most will use binaries, but if you are able, you should compile, since it means you don't need to trust all your funds with a binary created by a 3rd party, which could be backdoored.
Next, if you think you can copy+paste a few commands on the command-line of Linux, you are highly encouraged to try to compile yourself! It's a fun game, and the prize is a bigger slice of financial freedom.
There are various ways to stop hushd safely. The best and easiest method is hush-cli stop
The kill or killall command should not be used, it can corrupt your wallet.dat! The funds won't be completely lost, but they will be very hard to recover and require using advanced command-line tools to fix, which is as good as lost for many people. The kill command may have worked for you in the past, but it's a dangerous risk. If you are unlucky and the wallet.dat is being updated when you type the command, it can cause corruption. So it may have worked for you in the past, possibly many times, but it's still very risky.
In some rare cases it's possible that hush-cli stop will not work, because the Hush RPC interface is not responding. Hush has a special disk-based solution for this case. Run the following command on Linux: touch ~/.hush/plz_stop . This will create an empty file and hushd will notice it withing 120 seconds and stop correctly without risking a corrupt wallet.dat . On other Operating Systems, find the directory with your wallet.dat file and create a file called plz_stop in the same directory. The contents of the file do not matter.
Nodes can be out of sync for seemingly infinite reasons. We suggest reporting the details of your system, such as Operating System version and hushd version to our Telegram Support. Make sure to include details such as if you are using hushd directly or SilentDragon and any relevant version numbers.
This can happen for a few reasons. Your node may be out of sync, and still finding new blocks which contain payments to your address. You may not have imported all the private keys you thought you did. Use the validation function to check if an address is in your current wallet.
If your wallet is rescanning, it will show the balance as of the block height it is processing. You will see the balance "jump" higher when it finds a new transaction which pays one of your addresses. Your full balance will be shown when you have processed the latest block and regain "syncedness".
We have two main types of addresses, transparent and shielded. Transparent addresses start with
Originally HUSH addresses looked the same as Zcash addresses, so either t1... or z.. . When Hush changed our upstream from ZEC to KMD, that changed to be R... and zs1..., which is the prefix for Sapling Shielded Addresses.
If your address starts with zc instead of zs1, it is a Sprout address and it's not valid on the current HUSH mainnet.
For the above reasons, KMD, VRSC and SAFE addresses are all compatible, with the exact same public key generating the same exact address on KMD, VRSC, SAFE and HUSH and all the side chains (smart chains) of these respective platforms. If you own a taddr or zaddr on any one of these blockchains, you own the exact same address on all the blockchains.