65da80de58
We now have our halving schedule implemented until the BR goes to zero. The data was calculated via two new scripts which are in ./contrib : $ ./contrib/hush_halvings 1,12500000000,340000 2,312500000,2020000 3,156250000,3700000 4,78125000,5380000 5,39062500,7060000 6,19531250,8740000 7,9765625,10420000 8,4882812,12100000 9,2441406,13780000 10,1220703,15460000 11,610351,17140000 12,305175,18820000 13,152587,20500000 14,76293,22180000 15,38146,23860000 16,19073,25540000 17,9536,27220000 18,4768,28900000 19,2384,30580000 20,1192,32260000 21,596,33940000 22,298,35620000 23,149,37300000 24,74,38980000 25,37,40660000 26,18,42340000 27,9,44020000 28,4,45700000 29,2,47380000 30,1,49060000 31,0,50740000 32,0,52420000 33,0,54100000 $ ./contrib/hush_block_subsidy_per_halving 0,1250000000,1125000000,125000000 1,625000000,562500000,62500000 2,312500000,281250000,31250000 3,156250000,140625000,15625000 4,78125000,70312500,7812500 5,39062500,35156250,3906250 6,19531250,17578125,1953125 7,9765625,8789062,976562 8,4882812,4394531,488281 9,2441406,2197265,244140 10,1220703,1098632,122070 11,610351,549316,61035 12,305175,274658,30517 13,152587,137329,15258 14,76293,68664,7629 15,38146,34332,3814 16,19073,17166,1907 17,9536,8583,953 18,4768,4291,476 19,2384,2145,238 20,1192,1072,119 21,596,536,59 22,298,268,29 23,149,134,14 24,74,67,7 25,37,33,3 26,18,16,1 27,9,8,0 28,4,4,0 29,2,2,0 30,1,1,0 31,0,0,0 These show that the block subsidy for miners goes to 0 at the 31st halving and that the Founders Reward AKA Dev Tax goes to 0 at the 27th halving. There is also some current KMD internals code that we inherited that prevents the FR from being less than 10000, so that code would currently set our FR to 0 at the 14th halving and lead less HUSH being mined than the planned 21M and even a bit less than the amount under 21M that normally happens, such as in BTC. We have some time to deal with the bug, since halving 14 is in about 52 years.
HUSH
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!
Discord
Please feel free to join us on Discord at https://myhush.org/discord 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: https://dexstats.info/addressconverter.php
or this command line tool: https://github.com/MyHush/hush3/blob/duke/contrib/convert_address.py
Using an old wallet.dat
Backup your old HUSH wallet.dat, and backup any current wallet.dat that is in your
~/.komodo/HUSH3/
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
~/.komodo/HUSH3/
with a command like
# DO NOT RUN THIS WITHOUT MAKING BACKUPS!
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://
- DO NOT USE FROM PUBLIC WIFI
- DO NOT USE ON A COMPUTER OTHER PEOPLE USE
- 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: https://wallet.myhush.org
The source code for the Hush web wallet is here: https://github.com/MyHush/myhushwallet
Installing
See INSTALL.md.
License
For license information see the file COPYING.