Hush - Speak and Transact Freely

Private Cryptocurrency and Messenger using Zero Knowledge Mathematics

                  &&&&                  
         &&&&    &&&&&&    &&&&         
        &&&&&&   &&&&&&   &&&&&&        
 &&&    &&&&&&    &&&&    &&&&&&    &&& 
&&&&&   &&&&&&            &&&&&&   &&&&&
&&&&&   &&&&&&     &&     &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&   &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&   &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&            &&&&&
&&&&&   &&&&&&    &&&&&            &&&&&
&&&&&    &&&&       &&    &&&&&&   &&&&&
&&&&&                     &&&&&&   &&&&&
&&&&&    &&&&     &&&     &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&   &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&   &&&&&&   &&&&&
&&&&&   &&&&&&   &&&&&&   &&&&&&   &&&&&
&&&&&   &&&&&&            &&&&&&   &&&&&
 &&&    &&&&&&   &&  &&   &&&&&&    &&& 
        &&&&&&   &&&&&&   &&&&&&        
         &&&&    &&&&&&    &&&&         
                 &&&&&&                 
                  &&&&                  
HUSH 602424 anonset at block 613967 0.00000335 btc 53.72% mined in 1735 days
ARRR 544883 anonset at block 1471748 42334% higher 92.47% mined in 1069 days
Home HushDEX HushChat Gitea
Hush vs Monero Hush vs Zcash Hush vs Pirate Hush vs Komodo
Explorer Explorer on TOR F.A.Q Team

Hush has cryptographic proof it was attacked by Komodo Notary Node operators: only Komodo Notary Node operators can perform this attack because it is only their 64 public keys which are embedded into the source code of Komodo and Hush, which allows deciding which notarizations are valid.

They abused and disgraced their duty to protect and actually created malicious-yet-valid notarizations, which prevented nodes from syncing. Komodo Notary Nodes have now done this twice, once to SAFE and now to HUSH, and they can do this attack to any coin they currently "protect".

But jl777 says it is not possible to make malicious notarizations? jl777 is a liar who benefits from you believing it. It's possible when you combine normal notary operations with an Eclipse Attack, which KMD Notary Nodes trivially can do, since nodes connect to notary nodes by default.

KMD Notary nodes simply use their CPU/ASICs to mine a chain fork which is 1 block different than the real chain, then they come together to notarize it, which is valid since it's a valid block. This will cause any honest node to "get stuck" at that "malicious notarized chainfork".

This attack is interesting as transactions are created at the consensus layer which then eventually attack the Peer-2-Peer (P2P) network layer, preventing the node from syncing.

Notary nodes went far back into history, created a "fork in the road", made a road 1 foot long, and told everybody to go that way, knowing it to be a dead end. Notary nodes are given way too much power in the Komodo DPoW system, something we have fixed in the newly designed Hush DPoW system.

HUSH removed all public keys from KMD and now runs its own DPoW network. Additionally, we have added features to our full nodes which allow nodes to individually respond to DPoW-related attacks: -dpow-start-height is a feature to ignore all DPoW notarizations before a certain height. This allows nodes to respond to any possible future DPoW attack without updating code.

Many, if not all, Komodo Notary Node operators came together and spent extra time and effort to attack the Hush blockchain, to create malicious notarizations and run Hush nodes even though they said they dropped support for us for no reason. It requires at least 13 of 64 notary nodes to participate, so over a dozen notary nodes conspired to attack Hush. We have quite the fanboy club!

All that time spent on attacking, and Duke Leto released "Decentralized Dominatrix" Hush 3.6.0 which completely defeats the attacks and actually drastically increases the security and privacy.

KMD can hold your blockchain hostage if you do not pay your DPoW rent. HUSH does not want to be the master of your chain, so we will teach you how to break free of your KMD cage.

How can they break free of KMD bondage? FIRO and friends must demand to own the public keys and corresponding private keys which are the "trusted 64" which can make valid notarizations. The coin being notarized must own those addresses or they are "DPoW slaves" to Komodo.

The Komodo community were performing a DDOS attack on the FreedomDecrypted show when Duke Leto called out Zcash and Komodo for being a fraud and working with government. Full show: lbry.tv/@MyHushTeam:3/Freedom-Decrypted--Komodo-Script-Kiddies-Attack---Fail-:e

Hush does not use JS. In 2019, the KMD team received a notification from npm about a vulnerability in one of the upstream libraries KMD's Agama wallet was using, shortly after 100 BTC was stolen.

Komodo started to introduce KYC elements to AtomicDex: web.archive.org/web/20201101070728/https://komodoplatform.com/community-update-on-atomicdex-kyc-aml. Also the CTO of KMD, Kadan Stadelmann is a Blockchain Analyst for the Austrian military!

Hush has encrypted p2p layer. Komodo P2P layer is plaintext and leaks metadata to the ISP and all middlemen on the internet path. Hush nodes only use encrypted TLS 1.3 connections.