JUMBLE CASH, User Privacy Explained

JUMBLE CASH USER PRIVACY FUNCTION

Since its pivot from an exchange token to a full blockchain, as usual we definitely see countless projects on Ethereum fork over to Binance Smart Chain (BSC). Projects and engineers which chose to fork any existing code base, should do so with the intention to improve the original version. Not just to be a straight copy cat.

JUMBLE CASH WISHES TO STRENGTHEN IT'S USER PRIVACY FOR BNB TRANSACTIONS

The various rudiments for the it's user privacy is vast and clearly different since the shift from eth to bsc.
Why?

Unlike Ethereum, each validator in BSC can only see the last 5000 blocks. For the Tornado Cash clones the issue arises because when someone deposits in the pool, this transaction is logged on chain and is needed to be referenced when it comes time to withdraw. But because BSC validators can only see the last 5000 blocks, in most cases the block which logged the deposit will no longer be readily visible.

in depth meaning

Practically what this means is, a user deposits into the pool to make use of the privacy it offers. But when it comes time to withdraw it's likely that more than 5000 blocks would have passed. Especially as the number of transactions and hence blocks in BSC is growing rapidly, as seen here: https://bscscan.com/chart/tx. Meaning any direct forks of Tornado would not be able to accommodate withdraws because of the need to reference the block where the transaction occurred

The teams effort to resolve the issue;

The Jumble cash engineers have solved this issue through a BSC smart contract which directly interacts with our own dedicated node.
This allows Jumble network to build ontop of the given privacy architecture, which solutions like Tornado have established, but now also leverage the speeds and low transaction costs which BSC offers.

Jumble makes privacy cheap, fast and truly accessible. Additionally all transactions on Jumble are faster, as we are not reliant on public nodes.

User Experience has tended to plague the blockchain space, too often compromising ease of use for technical features.

To gain true user traction Jumble will empower users using a familiar user experience which has inherent privacy; our browser wallet.
From a user and usage perspective this acts like Metamask, reducing the learning curve and accelerating traction of Jumble .
Use Jumble to hde your financial data by mixing transfers with funds in Jumble pools, ensuring that all subsequent transfers remain anonymous. Each time you withdraw, Jumble ensures you use a fresh address. Delivering the following tangible user value:

1. Keeps your wealth hidden
2. Conceal the source of your assets
3. Hide your trading activities

Along with other features which we will touch on in subsequent posts, we believe that technical solution in combination with our user centric approach can truly empower user privacy for BNB.

Check out jumble cash on their social media platforms now

Website
Telegram
Medium
Twitter

Author's Bitcointalk link