|
|
|
# Hush
|
Updating branch (#108)
* Fix
* -print
* Filter null outputs
* Rewards cc
* Fix
* Linker
* Fix
* Fix
* KOMODO_LONGESTCHAIN
* Mining_height
* Fix dropped assetoshis
* Error null CCvin
* Test
* Test
* Test
* Fix sell
* Fix order book prints
* )
* Test
* Test
* Fix order display
* Fix oops
* Fix duplicate vin
* Remove dust check
* Fix silly bug
* Test
* Test
* Fix
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Fix compiler error: call of overloaded 'Pair(const char [9], time_t)' is ambiguous
* Fix compiler error: call of overloaded 'Pair(const char [9], time_t)' is ambiguous
* Correctly parse optional top parameter to getsnapshot
* Fix token orders crash
* Add SEC to assetchains.json
* Split amounts/validation: bid, ask, swap
* Fixes
* Test
* Test
* Test
* Test
* +print
* Test
* Test
* Test
* Test
* Test
* Test
* SMALLVAL
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Properly handle multiple vins funding fills
* Test
* Test
* Test
* Test
* Fix ask fill dest
* Test
* Rewards functions
* Fix
* Test
* Params to rewardscalc
* Create funding, addfunding, lock
* Test
* +print
* tokenswapask
* Test
* Test
* Swap functions
* ac_cc under 1000 is not fungible
* Allow to cancel invalid orders
* Prevent negative numbers in assets tx
* Uint64 -> int64
* Fix oops
* Prevent bid for nonexistent assetid
* Error check bidding for assetid that is txid but not asset creation
* Fix
* Fix
* Add pause if scriptcheckqueue isn't idle
* Fix
* -> -> .
* Fix
* Test
* VOBJ
* Tokeninfo rpc
* Asset list
* Test
* strcpy(cp->normaladdr,AssetsNormaladdr);
* Fix
* Rewardslist rewardsinfo
* Fix
* Fix
* Fix
* Vent
* fix
* Int64
* Int64
* Fix createfunding
* Fix false positive error
* sbits = stringbits(planstr);
* Fix maxmoney
* Fix funding name
* Test
* Print
* CCutoxvalue
* Fix rewardslock utxo selection
* New PoW diff calc
* tst
* Test
* Oldflag for PoW calc
* Test
* Test
* tst
* Test
* Test
* Filter locked utxo
* Test
* Fix PoW recalc
* Test min seconds
* int64_t CCduration(uint256 txid)
* Test
* Test
* Test one day
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Prevent inputs of CC inputs
* Test
* tst
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* New rewards address
* Fix mask
* Test
* Test
* Test
* Test
* Test
* Test
* Teest
* Stricter vin/vout checks for assets
* Token swap ready for testing
* Fix rewards unlock
* Fix
* Test
* Validate rewards
* Test
* Trim funding input
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Test
* Activate CCduration constraint
* Parameterize KOMODO_FIRSTFUNGIBLEID to 100
* +print
* Test
* Test
* Test
* Test
* Fix c script
* Test
* Initial dice morph from rewards.cpp
* Fix
* Test
* Fix
* Test
* Diceaddfunds
* Fix
* Dice list and dice info
* dicefund
* Dice bet
* Test
* Test
* Put process block's check block call inside lock, revert mining testblockvalidity outside lock
* Don't exit fiat-cli on error
* Docs for coinsupply RPC and improved error-checking on block height
* Version to 0.3.12-beta.
* Change version to 0.3.12 for gilab CI.
* Put undefines for _cpuid back.
* Network decentralizatoin and bug fixes
* Remove unnecessary staking delay
* Staking and mining timeing improvements
* Put staking readout once per staking loop so people know it's staking
* Fail on get_chainactive before lock if checks fail
* Fix check for stake transaction after Komodo merge
* Portable dev (#105)
* Force portable code
* Switch to old MMX instructions, avoiding SSE & SSE2 instructions.
* Less agressive, leave verus code (which checks for it) using advanced instructions.
* Compiling only for windows
* Update .gitlab-ci.yml
* Try -march=native for C++ code generation.
* Tweaking machine architecture settings.
* Try native alone.
* Also get LIBCRYPTOCONDITIONS to -march=native
* Switch other lib to native as well.
* Try switching back further for CPU architecture.
* Even lower end settings.
* Turn on symbols.
* Use sse2,3 and 4 capable x64.
* Once again let verus lib use advances instructioins since it checjs via CPUID at run time.
* Modify a few more makefile entries.
* Switch to AMD model similar to our test system.
* Get snark makefile to k8 too.
* Yet another -march to modify to k8, or two of them.
* Brute force k8 settings, comment non-portable code out.
* Put the condition on cpuid back.
* Put non-portable advenced instruction code back
* Enable instructions.
* Add lib for separate settings.
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* replacing k8-sse3 specific flags to x86-84
* updating versions
* updating versions
* Get verus-cli verusd updated (#106)
* Force portable code
* Switch to old MMX instructions, avoiding SSE & SSE2 instructions.
* Less agressive, leave verus code (which checks for it) using advanced instructions.
* Compiling only for windows
* Update .gitlab-ci.yml
* Try -march=native for C++ code generation.
* Tweaking machine architecture settings.
* Try native alone.
* Also get LIBCRYPTOCONDITIONS to -march=native
* Switch other lib to native as well.
* Try switching back further for CPU architecture.
* Even lower end settings.
* Turn on symbols.
* Use sse2,3 and 4 capable x64.
* Once again let verus lib use advances instructioins since it checjs via CPUID at run time.
* Modify a few more makefile entries.
* Switch to AMD model similar to our test system.
* Get snark makefile to k8 too.
* Yet another -march to modify to k8, or two of them.
* Brute force k8 settings, comment non-portable code out.
* Put the condition on cpuid back.
* Put non-portable advenced instruction code back
* Enable instructions.
* Add lib for separate settings.
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* Update .gitlab-ci.yml
* replacing k8-sse3 specific flags to x86-84
* updating versions
* Propagate verusd changes.
6 years ago
|
|
|
|
|
|
|
## What is Hush?
|
|
|
|
|
|
|
|
![Logo](doc/hush/hush.png "Logo")
|
|
|
|
|
|
|
|
Hush implements Extreme Privacy via blockchain tech. We have our own
|
|
|
|
genesis block. We are not a chain fork (copy) of another coin. We are based on
|
|
|
|
Bitcoin code, with sophisticated zero-knowledge mathematics added for privacy.
|
|
|
|
This keeps your transaction metadata private!
|
|
|
|
|
|
|
|
## This repository
|
|
|
|
|
|
|
|
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, it will likely take a few hours at least, but
|
|
|
|
some people report full nodes syncing in less than 1.5 hours. A competing privacy
|
|
|
|
coin takes over 24 hours to sync their full nodes because of Sprout Transactions, lulz.
|
|
|
|
|
|
|
|
## BANNED BY GITHUB
|
|
|
|
|
|
|
|
In working on this release, Duke Leto was suspended from Github, which gave Hush developers
|
|
|
|
the impetus to completely leave that racist and censorship-loving platform.
|
|
|
|
|
|
|
|
Hush now has it's own <a href="https://git.hush.is/hush">git.hush.is</a> Gitea instance,
|
|
|
|
because we will not be silenced by Microsoft.
|
|
|
|
|
|
|
|
All Hush software will be released from git.hush.is and hush.is, downloads from any other
|
|
|
|
domains should be assumed to be backdoored.
|
|
|
|
|
|
|
|
**Hush is unfinished and highly experimental.** Use at your own risk! Just like Bitcoin.
|
|
|
|
|
|
|
|
## Socials
|
|
|
|
|
|
|
|
Please feel free to join us on Telegram for official support :
|
|
|
|
* Main group: https://hush.is/tg
|
|
|
|
* Support group: https://hush.is/telegram_support
|
|
|
|
* Mining group: https://hush.is/telegram_mining
|
|
|
|
|
|
|
|
Other socials:
|
|
|
|
|
|
|
|
* <a href="https://hush.is/twitter">@MyHushTeam</a> on Twitter</a>
|
|
|
|
* <a href="https://hush.is/yt">Hush</a> on YouTube</a>
|
|
|
|
* <a href="https://hush.is/reddit">Hush</a> on Reddit</a>
|
|
|
|
|
|
|
|
## Official Explorer
|
|
|
|
|
|
|
|
<a href="https://explorer.hush.is">explorer.hush.is</a>
|
|
|
|
|
|
|
|
We are looking for alternate explorers to be run on Tor, i2P and other TLDs, if you are interested
|
|
|
|
please join TG and ask questions.
|
|
|
|
|
|
|
|
## 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://git.hush.is/hush/hush3/src/master/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.
|
|
|
|
|
|
|
|
# Installing
|
|
|
|
|
|
|
|
See [INSTALL.md](https://git.hush.is/hush/hush3/src/branch/master/INSTALL.md)
|
|
|
|
|
|
|
|
# License
|
|
|
|
|
|
|
|
For license information see the file [COPYING](COPYING).
|