How Anonymity is achieved.

The goal of a mixer is to break the on-chain link between one wallet and another, and doing so is what achieves Anonymity.

HUSH behaves similar to Tornado in the sense that you are limited on how much per transaction can be 'cleaned' as opposed to our competitors who allow custom inputs. Using increments of currency helps to ensure there are less unique transactions - unique transactions are an obvious giveaway as to the link between sender and receiver. Below is a scenario common with custom input mixers (regardless of usage activity):

Mixer that allows custom input: User1 wishes to "clean" 4.69ETH. They input the
amount, enter the reciever (User2) then they confirm the transaction. 

User2 Recieves 4.69ETH. 

Had the ethereum blockchain not been so transparent (with blockchain explorers),
the on-chain link would be broken... but because it is, by looking into the contract
sending User2 the funds, you can uncover the entire in and outgoings of the mixer.

From there it is as simple as seeing (on etherscan), who sent 4.69, then who recieved
that unique amount. Higher the usage of the mixer, may add a slight challenge, but
there will only be so many 4.69ETH tx's.

By having pre-defined amounts of commonly held figures, we add a significant layer of difficulty in tracing links.

We also achieve Anonymity by being selective with the selectable ERC-20 tokens to 'clean'. On launch we will support Ethereum as it has the highest on-chain activity, perfect to mask it's own transactions. Additional tokens will be supported after launch.

Disallowing custom inputs on microcaps, unlike our competitors, adds another layer of anonymity. Microcaps are already plagued with low volume - allowing users to send custom inputs of one to another address, although may show as anonymity being achieved, but it is as simple as checking the new holders of a token, then comparing the unique receiving figure to that of the sending amount or simply checking the transactions of a token.

Last updated