Skip to content
HUSH fork of KMD
Branch: master
Clone or download
Pull request Compare This branch is 161 commits ahead, 2 commits behind jl777:master.
Latest commit cc56d67 Jul 11, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Update Github issue template Aug 6, 2018
build-aux/m4 Merge branch 'beta' into mergemaster Apr 16, 2018
contrib Add airdrop txids Apr 20, 2019
depends Avoid downloading the 700MB sprout-groth16 file we do not need Jul 5, 2019
doc Update versions, copyrights and man pages Jun 25, 2019
qa Update May 29, 2019
share Merge branch 'beta' into mergemaster Apr 16, 2018
src Merge remote-tracking branch 'origin/nogroth16' into duke Jul 11, 2019
zcutil Avoid downloading the 700MB sprout-groth16 file we do not need Jul 5, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Merge branch 'master' into beta May 23, 2019
.gitlab-ci.yml add wget and fetch-params Jun 10, 2019
.gitmodules Merge branch 'beta' into mergemaster Apr 16, 2018
.travis.yml test Aug 10, 2018
AUTH_KEY.json.enc fixing broken auth May 28, 2018
Brewfile Removing unnecessary slashes Aug 18, 2018 fix typo Jun 9, 2019
COPYING Update copyright to 2019 Jan 1, 2019
Dockerfile Merge branch 'beta' into mergemaster Apr 16, 2018 Port from old repo Jun 12, 2019 All latest updates, smart contracts, including oracle from KMD/jl777 Sep 13, 2018 Updating branch (jl777#108) Aug 11, 2018 Fix link in readme to install instructions May 29, 2019 add security info Jun 7, 2019 Bugfix: Replace bashisms with standard sh to fix build on non-BASH sy… Oct 3, 2014 added patch files Jan 3, 2017 Update code of conduct info May 1, 2019 Update versions, copyrights and man pages Jun 25, 2019 added patch files Jan 3, 2017 Updating branch (jl777#108) Aug 11, 2018 Updating branch (jl777#108) Aug 11, 2018
equihash.cpp.patch added patch files Jan 3, 2017 Removing unnecessary slashes Aug 18, 2018 fix Nov 25, 2018 shell script to document migrate process Sep 6, 2018 added patch files Jan 3, 2017
patches added patch files Jan 3, 2017 notarization check for asset chains Sep 17, 2018 fix OSX May 31, 2019
user-config.jam darwin 333 Oct 22, 2017


What is HUSH?


HUSH (originally Zdash) is a code fork of ZCash which has it's own genesis block. It is not a fork of another network. Based on Bitcoin's code, it intends to offer a far higher standard of privacy through a sophisticated zero-knowledge proving scheme that preserves confidentiality of transaction metadata.

This software is the HUSH node and command-line client. It downloads and stores the entire history of HUSH transactions; depending on the speed of your computer and network connection, the synchronization process could take a day or more once the blockchain has reached a significant size.

HUSH is unfinished and highly experimental. Use at your own risk!


Please feel free to join us on Discord at There are many channels, some you might enjoy are #general, #support and #mining.

Claiming Funds From Old Hush Wallets

Hush migrated to a new mainnet after Block 500,000 on the old Hush blockchain. Funds in addresses as of Block 500,000 were transported to our new chain. About 31,000 addresses with at least 0.00000001 HUSH were transported to the new Hush mainnet.

To claim funds on the new chain, there are few options.

Funds on exchanges

Firstly, no bueno! Not your keys, not your coins. It's best not to store coins on exchanges. But in this case, you lucked out! There is nothing to do to claim new coins if you have coins on an exchange that supports the new Hush chain. The exchange will follow the instructions from the next section and you will magically have funds on the new chain. Note that old Hush addresses started with t1 and now they begin with R.

To see what an old HUSH v2 address looks like on the new chain, this online tool can be used:

or this command line tool:

Using an old wallet.dat

Backup your old HUSH wallet.dat, and backup any current wallet.dat that is in your


directory. There is no way to lose funds, as long as you have backups!!! Make sure to make backups. Do not skip this step.

Make sure any/all GUI wallets are stopped! Also make sure your old Hush node and new Hush3 node are stopped:

    cd hush3
    ./src/hush-cli stop

Do not copy wallets or move wallets while your full node is running! This could corrupt your wallet!

Now copy your old Hush wallet.dat to


with a command like

    cp ~/.hush/wallet.dat ~/.komodo/HUSH3/

The reason this works is that both old HUSH and new HUSH are still Bitcoin Protocol coins, which both use secp256k1 public keys. Now start your HUSH3 node again, with this special CLI argument that will clear out transactions from your wallet:

    cd hush3
    ./src/hushd -zapwallettxes

This will cause a full history rescan, which will take some time. Once it's complete, you can see your funds with this command:

    ./src/hush-cli getwalletinfo

NOTE: Do not use this wallet except to send funds to a new wallet!

Private Keys

You can also transport funds one address at a time via private keys.

Agama Desktop Wallet WIF-to-WIF Tool can convert between old HUSH and new HUSH3 private keys.

Web Wallet Seed Phrase

Nothing needs to be done, and if you use the Hush web wallet with a seed phrase, you can unlock your new funds on the new Hush mainnet with the same seedphrase.

This web wallet is hosted on a best-effort basis to give newcomers an easy way to make addresses for mining and other uses. Please heed this advice to keep your funds safe:

  • DO NOT USE FOR LARGE AMOUNTS, use a full node or light wallet
  • ALWAYS ACCESS VIA https://
  • BACK UP YOUR SEED PHRASE (multiple paper copies)

Even if you follow all those rules, due to web wallets relying on DNS and IP addresss, there are still potential attacks. You have been warned:

The source code for the Hush web wallet is here:




For license information see the file COPYING.

You can’t perform that action at this time.