
Introduction
Binance Smart Chain (BSC) is a blockchain network built for running smart contract-based applications, which allows users to get the best of both worlds: the high transaction capacity of BC and the smart contract functionality of BSC. What is special about Binance Smart Chain is its low fees and fast transaction speed, but what is even more special is its compatibility with EVM (Ethereum Virtual Machine). Due to EVM compatibility, DApps developed on Ethereum can be ported (imported into Binance Smart Chain as-is), and Ethereum wallets like Metamask can be used as-is. However, transactions on Binance Smart Chain are not private. For this reason, the project I want to introduce to you today is Jumble (https://jumblecash.com), a simple service that will increase privacy when making transactions through the Binance Smart Chain network.
Definition
Going into more detail, Jumble (https://jumblecash.com) is a project aimed at securing BSC transactions between addresses. The idea is that the same transactions are made but with increased privacy for users. Jumble effectively breaks the link in the chain between transaction sources and destination addresses by leveraging privacy-centric architecture and algorithms, keeping your data secure and anonymous.
How does it work?
Jumble is fully automated and operates without human assistance as when the jumble process is complete, the protocol simply deletes all related data.
A browser wallet with inherent privacy
Jumble provides a web-based wallet, like Metamask, that provides privacy to users by hiding their financial data and ensures that subsequent transfers remain completely anonymous. The idea is that for each transaction, the user uses a new address.

Privacy-focused pools
Wallet transactions leverage the power of Jumble Pools, which are pools of tokens that use a decentralized protocol that is autonomous from the private transactions of the Binance Smart Chain network, i.e. BEP20-like.
Jumble is able to do this through privacy algorithms that allow breaking the previously discussed link between transactions and destination addresses. That is, for each withdrawal a new transaction.
It is also important to know that non-Jumble users can also use the Pools directly through the web and increase the level of their privacy.

Bounty program
The project gives the opportunity to earn $JUM tokens performing some social media tasks and doing simple steps from the bounty program explained into the following Bitcointalk Thread here (https://bitcointalk.org/index.php?topic=5331970.0), where you can access the link in order to see what are the conditions to become an early Jumble contributor and start acquiring tokens.
You can also stay tuned in their official Telegram Channel (https://t.me/jumblecash). I hope you liked the post and soon I'll send you new ones.
Token details
The Jumble token will be the $JUM, which will be a native Binance Smart Chain token under the BEP20 protocol. HODLers of $JUM will be able to deposit their tokens on the platform where they will be able to receive new $JUM on a monthly basis as the platform rewards its users by distributing 80% of the fees collected under the BEP20 protocol on BNB. The remaining 20% will go towards the development and growth of the project.

Roadmap
Q1 2021
- Fungible Pool (done)
Q2 2021
- Bsc Starter
Q3 2021
- Claim for reimbursement
- Start of betting
- Additional tokens (BEP20)
Q4 2021
- Launch of the purse extension
- BEP / BEP20 Bridge
Social Media Links
Medium: https://twitter.com/jumble_cash
Twitter: https://medium.com/@jumblecash
Telegram: https://t.me/jumblecash
--------------------------------------------------------------------------------------------------------------------------------------------------
Author Details
Email: [email protected]
Bitcointalk username: adriaparcerisas
Bitcointalk profile link: https://bitcointalk.org/index.php?action=profile;u=1870482
BSC wallet: 0x91707502A8DFDC523f7a6f2c218cC9a52777d5ad
Bitcointalk Proof of Authentication link: https://bitcointalk.org/index.php?topic=5331970.msg57127253#msg57127253