forked from onryo/hush.land
onryo
3 years ago
9 changed files with 347 additions and 26 deletions
@ -0,0 +1,78 @@ |
|||
<!doctype html> |
|||
<head> |
|||
<title>Hush vs KYCcoin | Hush - Transact and Speak Freely</title> |
|||
<link href="css/styles.css" rel="stylesheet" type="text/css" /> |
|||
<meta name="viewport" content="width=device-width, initial-scale=1"> |
|||
</head> |
|||
<body> |
|||
<h2>Hush - Speak and Transact Freely</h2> |
|||
<h3>Private Cryptocurrency and Messenger using Zero Knowledge Mathematics</h3> |
|||
<pre> |
|||
&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&& &&&&&& &&&& &&&&&& &&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& &&&&& |
|||
&&&&& &&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& |
|||
&&&&& &&&& &&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&& &&&&&& && && &&&&&& &&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& |
|||
&&&& |
|||
</pre> |
|||
<table> |
|||
<tr> |
|||
<td><a href="https://hush.land/">Home</a></td> |
|||
<td><a href="hushdex">HushDEX</a></td> |
|||
<td><a href="hushchat">HushChat</a></td> |
|||
<td><a href="https://git.hush.is/hush/">Gitea</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="better-than-monero">Hush vs Monero</a></td> |
|||
<td><a href="better-than-zcash">Hush vs Zcash</a></td> |
|||
<td><a href="better-than-pirate">Hush vs Pirate</a></td> |
|||
<td><a href="better-than-komodo">Hush vs Komodo</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="https://explorer.hush.is/">Explorer</a></td> |
|||
<td><a href="http://hushv3jigvdpymnxf4zogpkzqldyo3626mpg3od4s5jtowpnagtjqsyd.onion">Explorer on TOR</a></td> |
|||
<td><a href="faq">F.A.Q</a></td> |
|||
<td><a href="team">Team</a></td> |
|||
</tr> |
|||
</table> |
|||
<div class="block"> |
|||
<p>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.</p> |
|||
<p>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".</p> |
|||
<p>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.</p> |
|||
<p>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".</p> |
|||
<p>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.</p> |
|||
<p>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.</p> |
|||
<p>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.</p> |
|||
<p>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!</p> |
|||
<p>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.</p> |
|||
<p>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.</p> |
|||
<p>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.</p> |
|||
<p>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</p> |
|||
<p>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.</p> |
|||
<p>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!</p> |
|||
<p>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.</p> |
|||
</div> |
|||
<div class="links"> |
|||
<a href="https://app.element.io/#/room/#hush:privacytools.io"><span style="color: #262626">[</span> matrix <span style="color: #262626">]</span></a> |
|||
<a href="https://fosstodon.org/@myhushteam"><span style="color: #262626">[</span> mastodon <span style="color: #262626">]</span></a> |
|||
<a href="https://odysee.com/@hushcoin"><span style="color: #262626">[</span> peertube <span style="color: #262626">]</span></a> |
|||
<a href="https://t.me/hush_main"><span style="color: #262626">[</span> telegram <span style="color: #262626">]</span></a> |
|||
</div> |
|||
</body> |
|||
</html> |
|||
@ -0,0 +1,82 @@ |
|||
<!doctype html> |
|||
<head> |
|||
<title>Hush vs BadCaca | Hush - Transact and Speak Freely</title> |
|||
<link href="css/styles.css" rel="stylesheet" type="text/css" /> |
|||
<meta name="viewport" content="width=device-width, initial-scale=1"> |
|||
</head> |
|||
<body> |
|||
<h2>Hush - Speak and Transact Freely</h2> |
|||
<h3>Private Cryptocurrency and Messenger using Zero Knowledge Mathematics</h3> |
|||
<pre> |
|||
&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&& &&&&&& &&&& &&&&&& &&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& &&&&& |
|||
&&&&& &&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& |
|||
&&&&& &&&& &&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&& &&&&&& && && &&&&&& &&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& |
|||
&&&& |
|||
</pre> |
|||
<table> |
|||
<tr> |
|||
<td><a href="https://hush.land/">Home</a></td> |
|||
<td><a href="hushdex">HushDEX</a></td> |
|||
<td><a href="hushchat">HushChat</a></td> |
|||
<td><a href="https://git.hush.is/hush/">Gitea</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="better-than-monero">Hush vs Monero</a></td> |
|||
<td><a href="better-than-zcash">Hush vs Zcash</a></td> |
|||
<td><a href="better-than-pirate">Hush vs Pirate</a></td> |
|||
<td><a href="better-than-komodo">Hush vs Komodo</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="https://explorer.hush.is/">Explorer</a></td> |
|||
<td><a href="http://hushv3jigvdpymnxf4zogpkzqldyo3626mpg3od4s5jtowpnagtjqsyd.onion">Explorer on TOR</a></td> |
|||
<td><a href="faq">F.A.Q</a></td> |
|||
<td><a href="team">Team</a></td> |
|||
</tr> |
|||
</table> |
|||
<div class="block"> |
|||
<p>Hush believes in more cryptocoins in general and more privacy coins in particular, is a good thing, needed to fully displace corrupt institutions such as WU and VISA, that have preyed on the poor for decades. Even so, HUSH believes we are the very best privacy coin based on zero-knowledge math and we compete directly with Monero, the oldest and most-used privacy coin currently.</p> |
|||
<p>Zero-knowledge math instead of obfuscation. Let's say Alice makes an XMR transaction to Bob. They both have relatively good privacy, at first. Alice has very good operational security (opsec) and does not use that address for any other purpose. She does her part to preserve her privacy.</p> |
|||
<p>Now Bob on the otherhand, he has very poor opsec. He uses this same address on every website, exchange and shady darkweb market he uses. One (or many) of these can work together, to correlate details about Bob. They can be hacked for this information and they can be legally required to share it, or the companies can dedice to work together to reduce their fraud costs.</p> |
|||
<p>Bob's actions would hurt any privacy coin protocol, no matter how private. The point is that it hurts CryptoNote Protocol coins much more, of which Monero is one, then coins like Hush, which use zero-knowledge math instead of obfuscation.</p> |
|||
<p>By default, Monero transactions hide the actual funds you are spending with ten other, un-related coins, owned by other Monero users. These are called "mixins" and currently XMR uses 11 mixins. Previously they used only a few and had to use more to make the statistics look less bleak.</p> |
|||
<p>As time goes on, and Bob uses his bad opsec, and his friends have bad opsec, and honest users make honest mistakes, Alice's privacy goes down. And most importantly, it is reduced by the actions of others and she has no control or way to improve it. There is simply nothing Alice can do. It's a numbers game, you are hiding in a very small crowd and it gets smaller over time too.</p> |
|||
<p>Hush is based on zero-knowledge math and does not have this problem. We call it our "anonymity set" which is the number of unspent shielded outputs at a block height. For Monero, their "anonymity set" is only the number of outputs involved in the transaction, which is a tiny number. The Hush anonymity set is drastically larger and protects every transaction.</p> |
|||
<p>Encrypted data at protocol level. Every single HUSH transaction has encrypted data section, regardless of it being used. This means that every single transaction might have encrypted data. Only the sender and receiver know. Monero lacks this basic feature, which is why they cannot even create a competitor to HushChat, they lack the basic protocol-level feature to enable it.</p> |
|||
<p>Monero could, in theory, change and start doing this one day. But the problem remains, years of blockchain history did not use it, and it's trivial to tell if somebody is using this new feature. It must be enabled from the beginning, which is what HUSH has done.</p> |
|||
<p>So far Monero users suffer from being using it: monero-badcaca.net as Monero or badcaca lacks IP-level privacy fixes and hence leaks metadata to all middlemen and ISPs.</p> |
|||
<p>Hush has Sietch. One of the main function of Sietch is to make linkability analysis of fully shielded transactions drastically more expensive, for more information please read: git.hush.is/hush/sietch and git.hush.is/hush/sietch-whitepaper</p> |
|||
<p>Create your own Hush sidechain. The future is multi-chain, hence the ease of creating new independent blockchains via Hush Smart Chains, sometimes called "sidechains". Hush empowers you to "spin up" a competitor to Hush with a single command, and it can integrate with the HUSH mainnet as much or little as you desire and there are no taxes paid to Hush like on Ethereum.</p> |
|||
<p>Create your own Hush Smart chain and run all the servers, decide all the parameters such as block size/time, total supply, etc. and mine the genesis block, and create mining pools and explorers. HSC's are a scalable platform to create private HushChat communities isolated from HUSH mainnet.</p> |
|||
<p>This is a desired property for high-privacy use cases. HushChat is a federated chat system, where communities decide if users should be able to chat with each other, similar to Mastodon servers being a decentralized version of Twitter.</p> |
|||
<p>Total supply is fixed at 21 million, exactly the same as Bitcoin. There are no any real reasons to change the supply except to create a larger market capitalization in the early days of a coin, a cheap marketing trick. 21 million was good enough for Satoshi and good enough for Hush.</p> |
|||
<p>Monero has an unlimited supply, and hence, is not deflationary, like Bitcoin and Hush. Hush inherits more Store-of-Value properties from Bitcoin because of this.</p> |
|||
<p>Monero is supported by blockchain analysis companies: ciphertrace.com/ciphertrace-announces-worlds-first-monero-tracing-capabilities started tracking Monero transactions since August 31 2020.</p> |
|||
<p>Even Monero community admits that XMR is broken: monerooutreach.org/breaking-monero</p> |
|||
<p>Riccardo "fluffypony" Spagni as an ex-monero co-founder bought himself a $750.000 watch and also he says: I thought, I'm going to pump it and dump it, because I was interested and taking the ideas and implementing them in bitcoin. The bitcoin code base was far more interesting to me than monero, and I thought, I'm not going to work on this codebase, it's terrible.</p> |
|||
</div> |
|||
<div class="links"> |
|||
<a href="https://app.element.io/#/room/#hush:privacytools.io"><span style="color: #262626">[</span> matrix <span style="color: #262626">]</span></a> |
|||
<a href="https://fosstodon.org/@myhushteam"><span style="color: #262626">[</span> mastodon <span style="color: #262626">]</span></a> |
|||
<a href="https://odysee.com/@hushcoin"><span style="color: #262626">[</span> peertube <span style="color: #262626">]</span></a> |
|||
<a href="https://t.me/hush_main"><span style="color: #262626">[</span> telegram <span style="color: #262626">]</span></a> |
|||
</div> |
|||
</body> |
|||
</html> |
|||
@ -0,0 +1,76 @@ |
|||
<!doctype html> |
|||
<head> |
|||
<title>Hush vs Testcoin | Hush - Transact and Speak Freely</title> |
|||
<link href="css/styles.css" rel="stylesheet" type="text/css" /> |
|||
<meta name="viewport" content="width=device-width, initial-scale=1"> |
|||
</head> |
|||
<body> |
|||
<h2>Hush - Speak and Transact Freely</h2> |
|||
<h3>Private Cryptocurrency and Messenger using Zero Knowledge Mathematics</h3> |
|||
<pre> |
|||
&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&& &&&&&& &&&& &&&&&& &&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& &&&&& |
|||
&&&&& &&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& |
|||
&&&&& &&&& &&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&& &&&&&& && && &&&&&& &&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& |
|||
&&&& |
|||
</pre> |
|||
<table> |
|||
<tr> |
|||
<td><a href="https://hush.land/">Home</a></td> |
|||
<td><a href="hushdex">HushDEX</a></td> |
|||
<td><a href="hushchat">HushChat</a></td> |
|||
<td><a href="https://git.hush.is/hush/">Gitea</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="better-than-monero">Hush vs Monero</a></td> |
|||
<td><a href="better-than-zcash">Hush vs Zcash</a></td> |
|||
<td><a href="better-than-pirate">Hush vs Pirate</a></td> |
|||
<td><a href="better-than-komodo">Hush vs Komodo</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="https://explorer.hush.is/">Explorer</a></td> |
|||
<td><a href="http://hushv3jigvdpymnxf4zogpkzqldyo3626mpg3od4s5jtowpnagtjqsyd.onion">Explorer on TOR</a></td> |
|||
<td><a href="faq">F.A.Q</a></td> |
|||
<td><a href="team">Team</a></td> |
|||
</tr> |
|||
</table> |
|||
<div class="block"> |
|||
<p>Pirate is a testcoin with a marketing department which is part of the larger "Komodo Ecosystem" which has been involved in many many shady ICO's, like the launching of KMD, and projects which are under investigation for fraud, like K64.</p> |
|||
<p>ARRR exists for 2 years and more than 90% of the total supply have been mined already which means that a few individuals own most of the coins. Hush was created in 2016 and only 50% was mined.</p> |
|||
<p>Hush does not support KYC. Hush does not help the identity theft industry by linking personal information to blockchain data, which does not work to reduce fraud and is almost always stolen, re-sold and used for illegimate purposes: pirate.black/changelly-exchange-listing-is-live</p> |
|||
<p>Hush was the first coin ever to measure anonsets in real-time. <a href="http://attackingzcash.com/anonset/">Anonsets</a>, AKA "anonymity sets" are a measure of how much privacy a privacy coin has. Hush was the first cryptocoin ever to measure this in real-time, via the getchaintxstats RPC, which Duke Leto worked on in Bitcoin Core.</p> |
|||
<p>Bitcoin Core has code from HUSH since Duke Leto upstreamed a change from Hush's version of getchaintxstats to the version in BTC Core. Pirate attempted to pay him to add this so-called zindex feature, but he refused, and so they are unable to measure their anonset in real-time.</p> |
|||
<p>Hush has encrypted p2p layer. Pirate 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.</p> |
|||
<p>Duke Leto wrote large portions of ARRR while being a Komodo Core developer for about two years and now it's unmaintained because there is nobody left that understands it. Additionally, KMD developers consider ARRR a separate project and make decisions that hurt the privacy of ARRR users.</p> |
|||
<p>Pirate lacks Sietch. Pirate does not have the advanced privacy technology called "Sietch" attackingzcash.com which makes it much easier for blockchain analysis companies to attack.</p> |
|||
<p>Pirate disabled Duke's privacy features to KMD. Duke Leto wrote code to protect against a specific kind of attack called a linkability attack and since Pirate and KMD developers who actually maintain Pirate, who has no dedicated developers don't understand it, they commented it out.</p> |
|||
<p>Pirate has no developers. The original developers of Pirate were jl777 and Duke Leto, who gave jl777 the idea for Pirate, by asking "What could the opposite of -ac_public=1 mean"? The next day, the Pirate testcoin was born, but there no any other developers left in Piratecoin.</p> |
|||
<p>Pirate requires a 1.6GB download of junk files. To run a full node you must download gigabytes of junk required for a disabled part of the code wasting the bandwidth of all users.</p> |
|||
<p>Pirate full node takes days to sync. Their full node is so slow to sync that they have built-ing the concept of downloading bootstraps (trusting somebody else's blockchain history!) into the full node itself. They truly don't grasp basic blockchain security principles.</p> |
|||
<p>Pirate is based on Sprout, a very old version of zaddrs that have been successfully attacked and are additionally extremely slow. Pirate based their chain on this old tech which is why it's so damn slow to sync a full node. HUSH was the very first coin to bbased solely on Sapling zaddrs.</p> |
|||
</div> |
|||
<div class="links"> |
|||
<a href="https://app.element.io/#/room/#hush:privacytools.io"><span style="color: #262626">[</span> matrix <span style="color: #262626">]</span></a> |
|||
<a href="https://fosstodon.org/@myhushteam"><span style="color: #262626">[</span> mastodon <span style="color: #262626">]</span></a> |
|||
<a href="https://odysee.com/@hushcoin"><span style="color: #262626">[</span> peertube <span style="color: #262626">]</span></a> |
|||
<a href="https://t.me/hush_main"><span style="color: #262626">[</span> telegram <span style="color: #262626">]</span></a> |
|||
</div> |
|||
</body> |
|||
</html> |
|||
@ -0,0 +1,85 @@ |
|||
<!doctype html> |
|||
<head> |
|||
<title>Hush vs Tcash | Hush - Transact and Speak Freely</title> |
|||
<link href="css/styles.css" rel="stylesheet" type="text/css" /> |
|||
<meta name="viewport" content="width=device-width, initial-scale=1"> |
|||
</head> |
|||
<body> |
|||
<h2>Hush - Speak and Transact Freely</h2> |
|||
<h3>Private Cryptocurrency and Messenger using Zero Knowledge Mathematics</h3> |
|||
<pre> |
|||
&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&& &&&&&& &&&& &&&&&& &&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& &&&&& |
|||
&&&&& &&&& && &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&& |
|||
&&&&& &&&& &&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&&& &&&&& |
|||
&&&&& &&&&&& &&&&&& &&&&& |
|||
&&& &&&&&& && && &&&&&& &&& |
|||
&&&&&& &&&&&& &&&&&& |
|||
&&&& &&&&&& &&&& |
|||
&&&&&& |
|||
&&&& |
|||
</pre> |
|||
<table> |
|||
<tr> |
|||
<td><a href="https://hush.land/">Home</a></td> |
|||
<td><a href="hushdex">HushDEX</a></td> |
|||
<td><a href="hushchat">HushChat</a></td> |
|||
<td><a href="https://git.hush.is/hush/">Gitea</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="better-than-monero">Hush vs Monero</a></td> |
|||
<td><a href="better-than-zcash">Hush vs Zcash</a></td> |
|||
<td><a href="better-than-pirate">Hush vs Pirate</a></td> |
|||
<td><a href="better-than-komodo">Hush vs Komodo</a></td> |
|||
</tr> |
|||
<tr> |
|||
<td><a href="https://explorer.hush.is/">Explorer</a></td> |
|||
<td><a href="http://hushv3jigvdpymnxf4zogpkzqldyo3626mpg3od4s5jtowpnagtjqsyd.onion">Explorer on TOR</a></td> |
|||
<td><a href="faq">F.A.Q</a></td> |
|||
<td><a href="team">Team</a></td> |
|||
</tr> |
|||
</table> |
|||
<div class="block"> |
|||
<p>Hush is better than Zcash because Hush has mandatory privacy. Zcash has ignored the fact that optional privacy is no privacy at all for over four years. All major blockchain analysis companies support Zcash now, but they don't support Hush.</p> |
|||
<p>At this point, it seems that Zcash has no mandatory privacy because it's financially profitable for them to not have privacy, so they can sell services to ChainAnalysis, CipherTrace and friends.</p> |
|||
<p>Zcash works directly with the governement and blockchain analysis companies, here's a link to a video that was originally deleted: bitchute.com/video/PWXU7D4VV0lB, at 43 minute a presenter mentions that these analysis companies specified above are actively working with Zcash.</p> |
|||
<p>This is one of reason why Zcash doesn't want you to use z-addresses, so their friends can track your transactions. A recent academic study published on May 18, 2020 by CarnegieMellon University showed that only 0.1% of ZEC users are using z-addresses properly.</p> |
|||
<p>zecpages.com is supported by Zcash to increase zaddrs use at least to some degree, another marketing trick to make people believe that someone is actually using z addresses, and still 5% of zaddr use only, so users link the social media accounts to their zaddrs: zecpages.com/directory</p> |
|||
<p>Zcash reduces privacy of miners with "Shielding Rule" where newly mined coinbase funds must be sent to a zaddr first, before they can be sent to a transparent address. As a result, it infects the shielded pool with Value and Timing metadata leakage: git.hush.is/hush/sietch-whitepaper</p> |
|||
<p>Hush is not in debt to investors. Zcash raised $3.000.000 from investors, which they must pay back, at least 10-100x or maybe more to satisfy the original investors. This is why the price of ZEC in satoshis (not USD), always goes down. They are paying back initial investors by selling parts of the Founders Reward which was renamed and made it even harder to track where the money goes.</p> |
|||
<p>Recently the entire Zcash company was donated to a non-profit, that nobody has heard of! This was after changing their name legally to "Electric Coin Company", further throwing shade on their operation. Note that Zcash Company already was a Swiss-based Company with a US company subsidiary and a 501c3 non-profit called Zcash Foundation, which they constantly fought with. When does an entire for-profit VC-funded company get donated to a non-profit? Sounds quite shady indeed.</p> |
|||
<p>Hush uses Bitcoin for security. Zcash stupidly tries to compete and replace Bitcoin, Hush relies on BTC mainnet for protection from mining attacks. This is done via Delayed-Proof-of-Work, which allows blockchains with smaller hashrates to be protected by blockchains with larger hashrates.</p> |
|||
<p>Hush has Sietch. Sietch has been protecting HUSH mainnet since September 2019 and adds Monero-like protections on top of Zcash Protocol, which is why we describe Hush Protocol as an improved Zcash Protocol and most secure and private cryptocoin: eprint.iacr.org/2020/627.pdf</p> |
|||
<p>Hush has HushChat. HushChat is a decentralized Signal competitor, and HushChat Protocol implements a protocol very similar to Signal Protocol, with ratcheting, where we replace traditional metadata-nightmare phone numbers with shielded Hush addresses. No centralized servers, no companies, no phone numbers, no JavaScript, Plausible Deniability and support for emoji!</p> |
|||
<p>Hush tells the public the truth. Zcash tries to hide security problems and their various shady dealings with various organizations. For example, the Sprout CVE was kept secret for about a year by Zcash Company and then dumped on the greater community like a large turd sandwhich for lunch. Another Zcash vulnerability CVE-2019-16930 was publicly disclosed by Duke Leto.</p> |
|||
<p>Zcash Company was trying to keep it secret and this is when most Zcash people, including security officers and engineering, blocked him on Twitter, to the detriment of all Zcash users. The "Sapling Woodchipper" CVE-2019-11636 has actually gotten worse since Zcash made their transaction fees ten times less, in an effort to control fees, they made the attack ten times cheaper.</p> |
|||
<p>Hush uses the same zero-Knowledge math, for free. Zcash spent millions of dollars to develop bleeding edge new mathematics, called zk-SNARKs (zero knowledge succinct non-interactive arguments of knowledge), which Hush uses for free. Zcash Company additionally spends obscene amounts of money maintaining this code as an upstream, for free. Zcash has no "technological moat" and Hush takes all the best ideas, for free, and combines them with the best ideas from Monero. Thanks Zcash!</p> |
|||
<p>Hush is free software. We are a GPLv3 Free Software community, so Hush owns it's own patents and intellectual property. If you use our stuff in an uncool way, we will send Software Freedom Law Center to you. They love GPLv3 enforcement.</p> |
|||
<p>Zcash steals ZIP400, with cryptographic proof. Daira, author of Zcash Protocol, was stupid enough to steal the work of Duke Leto (ZIP400, twitter.com/dukeleto/status/1325043400035471361) and tried to delete all history of Duke writing the document. They failed to correctly change history and left traces that prove Duke Leto wrote ZIP400 and that Zcash Foundation stole the document, committing MIT Copyright Infringement by removing Duke Leto's name from the document.</p> |
|||
<p>Unlike most free software projects, Hush developers are open to granting MIT/Apache2 licenses to companies who want to use our code in business ventures, which we support. We just don't support writing code for free and then companies taking it, making their riches, and giving nothing back and not appropriately paying the people who maintain production. Pay before you play.</p> |
|||
<p>Hush has network-level privacy. Zcash and Bitcoin itself have no network-level privacy, it makes sense for Bitcoin as it is not a privacy coin and everything is public. Encrypting connections between Bitcoin full nodes would mostly be a waste of resources and it would prevent some very old computers from joining the network, potentially. OK Satoshi, you get a pass from Duke.</p> |
|||
<p>Now Zcash, on the otherhand, is supposed to be a privacy coin right? It would benefit from network-level privacy such as SSL/TLS (like the little green lock in your browser), but they never implemented it. Either they are stupid and lazy, or they are smart and realize that since most Zcash transactions don't use privacy, it's basically worthless to add network encryption to Zcash.</p> |
|||
<p>Hush has mandatory network-level TLS 1.3 encryption between all peers, the current best in world used by all modern web servers and browsers. All legacy ciphersuites are turned off and Hush only supports TLS 1.3, unlike almost any other software out there.</p> |
|||
<p>Hush nodes have mandatory privacy on the blockchain and on the network and these two things together combine to make Hush exponentially more private than Zcash.</p> |
|||
<p>Hush is a platform to make privacy coins. Hush gives you the ultimate freedom to make your own privacy coins, which can integrate with Hush or not. Zcash wants to be a king, where you live on their land and pay them a tax. With Hush, you can make your own kingdom (or queendom) and there are no taxes paid to Hush, as opposed to building on Ethereum. Hush Smart Chains can be completely independent of Hush, or be protected by Hush (and Bitcoin hashrate) via Delayed-Proof-of-Work.</p> |
|||
</div> |
|||
<div class="links"> |
|||
<a href="https://app.element.io/#/room/#hush:privacytools.io"><span style="color: #262626">[</span> matrix <span style="color: #262626">]</span></a> |
|||
<a href="https://fosstodon.org/@myhushteam"><span style="color: #262626">[</span> mastodon <span style="color: #262626">]</span></a> |
|||
<a href="https://odysee.com/@hushcoin"><span style="color: #262626">[</span> peertube <span style="color: #262626">]</span></a> |
|||
<a href="https://t.me/hush_main"><span style="color: #262626">[</span> telegram <span style="color: #262626">]</span></a> |
|||
</div> |
|||
</body> |
|||
</html> |
|||
Loading…
Reference in new issue