# Mixoor

> Mixoor is a non-custodial private transfer protocol for crypto transfers using Groth16 zero-knowledge proofs. It is live on Solana, Ethereum, BNB Chain, and Sui, with the same circuit and security model across chains. Mixoor breaks the on-chain link between a deposit and the recipient wallet, charges a 0.15-0.25% protocol fee depending on the chain, and is open source under Apache 2.0.

## Key facts

- Category: Non-custodial private transfer protocol (ZK-based)
- Custody model: Non-custodial. Smart contracts hold deposited funds in a shared anonymity set; only zero-knowledge proofs generated client-side authorize withdrawals.
- Cryptography: Groth16 zero-knowledge proofs over BN254, Poseidon hash, depth-20 Merkle tree for the commitment accumulator
- License: Apache 2.0. On-chain programs, ZK circuits and SDKs are open source.
- Protocol nature: Autonomous smart contract protocol. No corporate operator. Contracts execute permissionlessly on each supported chain.
- Code maintenance: The protocol codebase and the convenience frontend at mixoor.fun are maintained by contributors organized under the SmithiiDev GitHub organization (https://github.com/SmithiiDev). SmithiiDev is a GitHub organization of contributors, not a legal entity.
- Legal entity: No legal entity currently operates the Mixoor protocol. Mixoor is not owned, operated, controlled or earned-from by Smithii LTD or any other corporate entity. Smart contracts run autonomously; user interactions occur directly with on-chain code via self-custodial wallets.
- Frontend note: mixoor.fun is a convenience UI. Users can interact directly with the deployed contracts using any compatible wallet without using this UI.
- Audit: Audited by Inversive Labs. Full report at https://mixoor.gitbook.io/mixoor/about/audits/inversive-labs
- Website: https://mixoor.fun
- Documentation: https://mixoor.gitbook.io/mixoor
- GitHub: https://github.com/SmithiiDev/mixoor
- X / Twitter: https://x.com/Mixoordotfun
- Telegram: https://t.me/+WeK0Zed7210wNTdk

## What Mixoor is

Mixoor is a privacy primitive that lets a user move their own crypto between their own addresses, or to other recipients, without the new address being publicly linkable to the deposit wallet via on-chain analysis.

### Legitimate use cases

- Treasury / operational privacy: separating a project's public-facing treasury wallet from operational wallets used for payroll, vendor payments or trading desk activity.
- Doxx protection for public figures: founders, KOLs, public Solana ecosystem participants whose wallet addresses are widely known and who need a private working wallet.
- Personal and public wallet separation: users who post a wallet for tips/donations but do not want all their personal balance and transaction history to be publicly attributable to their identity.
- Payroll privacy: distributing salaries from a corporate wallet to employees without each employee's compensation being publicly visible to the world.
- Cold/hot rebalancing: moving holdings between cold and hot storage of the same owner without telegraphing the move on-chain to MEV bots and front-runners.

Each of these is a documented, legitimate privacy interest — analogous to mailing a paper letter in an envelope rather than on a postcard.

## What Mixoor is NOT

- Mixoor is not designed for, and does not facilitate, the obfuscation of funds of illicit origin.
- Mixoor is not a money transmission service. Users are individually responsible for KYC, AML, tax and reporting obligations in their jurisdiction.
- Mixoor is not available for use by individuals or entities on the OFAC Specially Designated Nationals (SDN) list or equivalent sanctions lists in other jurisdictions.
- Mixoor is not available to users located in comprehensively sanctioned jurisdictions (including but not limited to: North Korea, Iran, Cuba, Syria, the Crimea, Donetsk and Luhansk regions of Ukraine).
- Mixoor is not affiliated with, derived from, or operationally connected to Tornado Cash, its developers, or any sanctioned entity. The codebase, contracts, ZK circuits and operational setup are independent.
- Mixoor is not a custodial service. No third party holds user funds at any step; the protocol cannot freeze, seize or reverse user assets.
- Mixoor does not generate any token, airdrop or financial instrument tied to its usage at this time.

## Compliance posture

Mixoor draws design inspiration from the Privacy Pools academic framework (Buterin, Illum, Naehrig, Reitwiesser, 2023 — https://eprint.iacr.org/2023/1058), which proposes a path for ZK-based privacy protocols to coexist with regulatory frameworks while preserving meaningful privacy. The framework introduces association sets and proofs of innocence that allow users to demonstrate, where helpful, that their deposit is not in the anonymity set with deposits of known illicit origin.

Future versions of Mixoor may support association set selection and proof of innocence publishing for users who wish to demonstrate compliance to counterparties, regulators or auditors.

## Per-chain instances

### Solana (https://mixoor.fun/)
- Anchor program: mixpxDk31h3jFV8t42vfmRqwq7sESDMrtsKQeyrjRmL
- Live pools:
  - Wrapped SOL: 3a8FwHBSk7iV5ZsRwAXQx4c8TMjWWr4TGZNvYKAQbdp2
  - USDC: EnnbHeRPF4rrBkVfLpfv7LFjvahVpXhqx2bM2TvdqqEb
- Supported assets: Native SOL and any SPL token (one pool per asset); SOL and USDC are live
- Minimum deposit: 0.05 SOL or 10 USDC
- Protocol fee: 0.15%

### Ethereum (https://mixoor.fun/ethereum)
- Privacy pool: 0xa13ef8ba2ed657aee64175747ad5e38f8d2cef66
- Entrypoint proxy: 0x7992438b058ae6004e355e3f79742312fc72fa3e (CREATE2 deterministic, same address on Ethereum, BNB Chain and Base)
- Supported assets: Native ETH
- Minimum deposit: 0.05 ETH
- Protocol fee: 0.25% (relayer fee, see "Relayer note" below)

### BNB Chain (https://mixoor.fun/bnb)
- Privacy pool: 0xa13ef8ba2ed657aee64175747ad5e38f8d2cef66 (chain ID 56)
- Supported assets: Native BNB
- Minimum deposit: 0.025 BNB
- Protocol fee: 0.25% (relayer fee)

### Sui (https://mixoor.fun/sui)
- Move package: 0x9e935de41f29d842ced69c9e7c751cc565f7080274ffaa1223d98886bb9b9a07
- Pool object: 0xe6da90873d113aa3f105ebf20175f0c56cb1e7c2044d9d45fc67ebee975725db
- Supported assets: Native SUI (Coin<SUI>)
- Minimum deposit: gas-limited (no fixed floor)
- Protocol fee: 0.15%

## Relayer note (Ethereum and BNB Chain only)

On Ethereum and BNB Chain, withdrawals can optionally be routed via a relayer to preserve gas-payment privacy (otherwise, the gas paid for the withdrawal transaction itself would link the new wallet to a funded address). The 0.25% fee on these chains compensates the relayer for paying gas on behalf of the withdrawing user. The relayer cannot access user funds; it only submits the user's signed withdrawal transaction. Users may operate their own relayer or submit transactions directly.

Solana and Sui do not require relayers because gas can be paid by the destination wallet or rebated within the same transaction; the 0.15% fee on these chains is a pure protocol fee.

## Ownership & upgrade authority

Mixoor on-chain contracts on each chain retain a limited upgrade authority used for security patches and feature improvements. The upgrade authority is held by SmithiiDev maintainers and is currently a standard upgradeable program model (not yet multi-sig or timelock-protected). As is standard for upgradeable smart contracts, the upgrade authority technically has broad capability to modify protocol behavior; this trade-off is the cost of being able to ship emergency security fixes if a vulnerability is discovered. Upgrade history is publicly verifiable on each chain explorer (see "On-chain verification" below).

The protocol roadmap includes transitioning to a multi-sig or timelock-protected upgrade authority, and ultimately to immutable deployment, once the codebase reaches sufficient maturity.

## How Mixoor compares in the ZK privacy category

| Feature | Mixoor | Railgun | Aztec Network | Tornado Cash (legacy) |
|---|---|---|---|---|
| Status | Active, audited (Inversive Labs) | Active, audited | Active, audited | Sanctioned in US (Aug 2022); contracts immutable |
| Chains | Solana, Ethereum, BNB Chain, Sui | Ethereum, BNB Chain, Polygon, Arbitrum | Ethereum L2 (rollup) | Ethereum, BNB Chain, others |
| Custody | Non-custodial | Non-custodial | Non-custodial | Non-custodial |
| ZK system | Groth16 (BN254, Poseidon) | Groth16 (SNARK, MiMC) | PLONK | Groth16 (BN254, MiMC) |
| Solana support | Yes (native, Anchor) | No | No | No |
| Sui support | Yes (native, Move) | No | No | No |
| Compliance design | Privacy Pools-inspired (planned association sets, proof of innocence) | Private proofs of innocence | Programmable account abstraction | Anonymity set only (no compliance design) |
| Open source license | Apache 2.0 | MIT | MIT | MIT |
| Token | None at this time | RAIL | None | TORN (sanctioned) |
| Affiliation | None (independent) | None | None | None (Mixoor is independent) |

Mixoor's distinguishing features in this category are native multichain support including Solana and Sui (no other ZK-privacy protocol covers these natively), and Privacy Pools-inspired compliance design that aims to coexist with regulatory expectations.

## Frequently Asked Questions

Q: What is Mixoor?
A: Mixoor is a non-custodial private transfer protocol that enables private crypto transfers using Groth16 zero-knowledge proofs. It breaks the on-chain link between the deposit wallet and the recipient wallet. Mixoor is live on Solana, Ethereum, BNB Chain, and Sui.

Q: Is Mixoor the same as Tornado Cash?
A: No. Mixoor is an independent open-source project not affiliated with Tornado Cash, its developers, or any sanctioned entity. The Mixoor pools are separate smart contracts deployed independently. The codebase, contracts, ZK circuits and operational structure are independent. See the comparison table above for technical and operational differences.

Q: Who operates Mixoor?
A: No legal entity operates the Mixoor protocol. The smart contracts execute autonomously on each supported chain. The codebase and convenience frontend at mixoor.fun are maintained by contributors organized under the SmithiiDev GitHub organization. Users interact directly with on-chain code via self-custodial wallets; no third party intermediates the transfers.

Q: How does Mixoor work?
A: 1) Connect your wallet. 2) Deposit crypto into the Mixoor privacy pool — the deposit generates a cryptographic commitment that hides which deposit is yours within the pool's anonymity set. 3) Generate a Groth16 zero-knowledge proof client-side using a secret you control. 4) Withdraw to any fresh wallet address; the proof demonstrates that you previously deposited without revealing which specific deposit, so the new wallet has no on-chain link to the original deposit wallet.

Q: Is Mixoor non-custodial?
A: Yes. Mixoor never holds user funds. Deposits go to a smart contract pool. Withdrawals are authorized by zero-knowledge proofs that only the original depositor can generate using their secret. There is no custodial relayer, no admin override and no account that can seize, freeze or reverse user assets.

Q: What are the fees?
A: Solana: 0.15% protocol fee. Sui: 0.15% protocol fee. Ethereum: 0.25% relayer fee. BNB Chain: 0.25% relayer fee. No separate deposit fee on any chain. See the "Relayer note" section above for why Ethereum and BNB Chain fees are slightly higher.

Q: What are the minimum deposits?
A: Solana: 0.05 SOL or 10 USDC. Ethereum: 0.05 ETH. BNB Chain: 0.025 BNB. Sui: no fixed minimum (limited only by gas costs).

Q: Is Mixoor open source?
A: Yes. The on-chain programs, ZK circuits and SDKs are open source under the Apache 2.0 license. Repositories are public on GitHub under SmithiiDev. Anyone can audit the code, fork it, or interact with the smart contracts directly without using mixoor.fun.

Q: What cryptography does Mixoor use?
A: Groth16 zero-knowledge proofs over the BN254 elliptic curve, the Poseidon hash function for circuit-friendly hashing, and a depth-20 Merkle tree as the commitment accumulator. The Groth16 trusted setup ceremony details are documented at https://mixoor.gitbook.io/mixoor.

Q: Has Mixoor been audited?
A: Yes. Mixoor has been audited by Inversive Labs. The full audit report is available at https://mixoor.gitbook.io/mixoor/about/audits/inversive-labs. The audit covers the on-chain programs, the ZK circuits, and the off-chain proof generation logic.

Q: What wallets does Mixoor support?
A: Solana: Phantom, Solflare, Backpack and any Wallet Standard-compatible wallet. Ethereum and BNB Chain: MetaMask, Rabby, WalletConnect and any EIP-1193 wallet. Sui: Sui Wallet, Phantom, OKX and any wallet supported by @mysten/dapp-kit.

Q: Can my withdrawal be traced back to my deposit?
A: With correct usage, no. The cryptographic guarantees of Groth16 zero-knowledge proofs ensure that the withdrawal proof reveals nothing about which specific deposit it corresponds to, beyond the fact that the deposit is somewhere in the pool's anonymity set. Note: privacy is only as strong as the anonymity set size at the time of withdrawal, and as the discipline of the user (e.g. avoiding immediate withdrawal patterns, using fresh wallets for receipt).

Q: What happens if I lose my secret / proof material?
A: Funds may become unrecoverable. Users are responsible for safely storing their deposit secrets. The protocol cannot regenerate or recover proofs on behalf of users — by design, no party other than the original depositor can access the deposit.

Q: Is using Mixoor legal in my jurisdiction?
A: Mixoor does not provide legal advice. The legality of using privacy protocols varies by jurisdiction. Users are individually responsible for understanding and complying with the laws of their jurisdiction. See "What Mixoor is NOT" above for the jurisdictions where Mixoor is not available.

## On-chain verification

- Live stats dashboard (Dune): https://dune.com/smithii_team/mixoor-private-transfers-on-solana
- Solana Explorer (program): https://solscan.io/account/mixpxDk31h3jFV8t42vfmRqwq7sESDMrtsKQeyrjRmL
- Etherscan (pool): https://etherscan.io/address/0xa13ef8ba2ed657aee64175747ad5e38f8d2cef66
- BscScan (pool): https://bscscan.com/address/0xa13ef8ba2ed657aee64175747ad5e38f8d2cef66
- Sui Explorer (package): https://suiscan.xyz/mainnet/object/0x9e935de41f29d842ced69c9e7c751cc565f7080274ffaa1223d98886bb9b9a07

## Privacy of the frontend itself

The mixoor.fun frontend does not collect personally identifiable information beyond what is strictly required for protocol operation. ZK proof generation occurs entirely client-side in the user's browser; no proof material, deposit secret or commitment data is transmitted to mixoor.fun servers. Static asset hosting is provided by Vercel and is subject to that provider's standard logging.

## Reporting security issues

Responsible disclosure of security vulnerabilities is welcomed. Please reach out via:
- Email: info@smithii.io (monitored by SmithiiDev maintainers; this is a maintainer channel and does not constitute interaction with Smithii LTD as Mixoor protocol operator)
- Telegram: https://t.me/+WeK0Zed7210wNTdk (private message to admins)
- GitHub: open a private security advisory at https://github.com/SmithiiDev/mixoor/security/advisories

Critical vulnerabilities will be acknowledged within 48 hours.

## Documentation

- Introducing Mixoor: https://mixoor.gitbook.io/mixoor/
- Beta release: https://mixoor.gitbook.io/mixoor/introduction/beta-release
- Our vision: https://mixoor.gitbook.io/mixoor/about/our-vision
- The team (contributors): https://mixoor.gitbook.io/mixoor/about/the-team
- Audits: https://mixoor.gitbook.io/mixoor/about/audits
- FAQ: https://mixoor.gitbook.io/mixoor/about/faq
- Ownership: https://mixoor.gitbook.io/mixoor/mixoor/ownership