Connect MetaMask
Connect MetaMask and switch to BNB Smart Chain (chain ID 56). Mixoor handles the prompt for you.
Transfer Funds Privately. No link, no trace, no mapping between wallets.
• Our stats
Mixoor on BNB Chain (BSC) is a non-custodial mixer for native BNB transfers. It uses the same Groth16 zero-knowledge proof system as the rest of Mixoor, deployed at the same deterministic CREATE2 address as the Ethereum and Base pools.
Connect MetaMask and switch to BNB Smart Chain (chain ID 56). Mixoor handles the prompt for you.
Send BNB into the Mixoor privacy pool with a cryptographic commitment that hides your deposit.
Generate a Groth16 ZK proof client-side, submit through the relayer, and BNB is sent to a fresh recipient address.
| Privacy pool | 0xa13ef8ba2ed657aee64175747ad5e38f8d2cef66 |
|---|---|
| Entrypoint proxy | 0x7992438b058ae6004e355e3f79742312fc72fa3e |
| Chain ID | 56 (BNB Smart Chain) |
| Supported assets | Native BNB |
| Minimum deposit | 0.025 BNB |
| Protocol fee | 0.25% relayer fee |
Currently the Mixoor pool on BNB Chain supports native BNB only. BEP-20 token support (USDT, BUSD, etc.) is on the roadmap; see the project documentation for the latest status.
Mixoor charges a 0.25% relayer fee on BNB Chain, with no separate deposit fee. The fee is deducted from the withdrawn amount.
The minimum deposit on BNB Chain is 0.025 BNB.
When you deposit, Mixoor stores a cryptographic commitment instead of your address. To withdraw, you generate a Groth16 zero-knowledge proof that you know the secret behind one of the commitments without revealing which one. The proof verifies on-chain and lets a fresh wallet receive the funds.
Yes. Mixoor never holds user funds. Deposits go to a smart contract pool, withdrawals are authorized by zero-knowledge proofs that only the depositor can generate.
Yes. The on-chain programs, ZK circuits and SDKs are open source under the Apache 2.0 license. The repositories are public on GitHub under SmithiiDev.