Having privacy while doing transactions on a public-blockchain is hard ,
As in most situations you will need to be connected with to an exchange or any central point where you can be targeted by malicous actors,
Look at the coinbase situation where a blackhat had access to all your important situation via a Customer Support insider.

Tornado cash offered privacy but was sadly affiliaited for a long while to being an illegal mixer.

This is where Eden's Protocol comes in, heavily inspired by the Tornado-cash protocol it utillizes ZKP to make sure the user can deposit and withdraw on every supported EVM chain, The cross-chain messaging is facilitated by Chainlink's CCIP which makes a secure/fast experience.

Normally the Tornado Cash's users were limited with amounts/ specific chain where you deposited,las there was no way to use the same withdraw note to withdraw your tokens on another chain with Eden's Protocol it gives users the power to withdraw wherever and whatever amount they want.

The vaults of Eden will make sure to give the liquidity needed if there is no activity from others depositers, the depositers of the vault will get paid in fees that are made from the deposit/withdraw fees, which incentives Liquidity-Providers and keeps the protocol running.

The contract structure exist of:

• EdenPL.sol (Deployed on Ethereum mainnet to verify/confirm all commitments/proofs.
• EdenEVM.sol (EVM variant that sends the commitments/ proofs to the mainnet
• EdenVault.sol(Supplies liquidity if other user's deposit can't cover it.)
• verifier.sol (used to verify the proofs on-chain!)
• MerkleTreeWithHistory.sol (from Tornado-Cash)

This makes sure even in a situation where deposit are low by users, it will be supplied via LP deposited into the vaults.

With this Liquidity the private 'cross-chain-bridge' can still keep functioning when user want to bridge (deposit/withdraw) their tokens to another chain.