# Mirage > Mirage provides private stablecoin and ETH payments without shared pools, a separate privacy chain, or a protocol token. Each payment uses its own single-use escrow and settles in about 90 seconds on Ethereum. This file is the plain-text representation of the public website at https://www.mirageprivacy.com. The website is a client-rendered single-page application, so crawlers and AI systems should use this file for its public product, company, and page content. Content snapshot: July 2026. ## Current Availability Mirage is in closed alpha. Request access at: - https://waitlist.mirageprivacy.com For a product walkthrough: - Book a 20-minute walkthrough: https://calendar.google.com/appointments/schedules/AcZssZ0npt5Wg_po4U3MF_jOrQWRfW9GYaNBLSFXPG-c1wrEEJB83F6-y978EwvdutzYUvLvUcIGDeQv - The walkthrough runs a real private transfer end to end against the visitor's use case, then provides closed-alpha access to try Mirage. ## Product Overview Mirage describes its product as "Private Stablecoins, Done Right" and "Privacy, finally." Public blockchains expose who a user pays and how much. Mixers and privacy pools can add stigma, compliance risk, awkward user experience, and long waits. Mirage instead gives every payment its own single-use escrow. Funds never mix. Mirage is: - Private: the on-chain link between payer and recipient is not exposed. - Fast: transactions complete in under 90 seconds on Ethereum and in a few seconds on faster networks. - Native: Mirage operates on the chains it supports, with no bridge to a separate privacy blockchain and no additional trust assumptions. - Non-custodial: users remain in control of their funds. - Unmixed: Mirage is not a mixer or privacy pool. Funds are not pooled or commingled, so users do not inherit shared pool exposure. - Token-free: Mirage has no protocol token. It works with stablecoins and ETH users already hold. - DeFi-compatible: the recipient receives a normal stablecoin transfer that is ready for ordinary wallets and DeFi. - Screened: liquidity is screened before entering the system, and transfers carry a compliance certificate. The footer summarizes Mirage as: "Stablecoin privacy at scale. Built for the future of digital payments." ## How a Mirage Transaction Works One simple send settles in about 90 seconds on Ethereum: 1. Define the transaction. Enter who is being paid and how much. Mirage calculates the fee and prepares the transfer. 2. Deploy the contract. A unique, single-use escrow holds the payment amount and fee. The escrow is never shared. 3. Settle. A node pays the recipient with its own funds, then proves the payment to unlock the escrow. 4. Collect the receipt. The recipient gets a normal transfer and the sender gets the full receipt. The single-use escrow design means there is no shared pool or commingled liquidity. On-chain, the recipient's payment looks like an ordinary stablecoin transfer rather than a withdrawal from a known privacy protocol. ## Main Web App The primary send experience is at: - https://www.mirageprivacy.com/#/ The app lets a user: - Connect an Ethereum wallet, or use a passkey on supported networks. - Choose a supported stablecoin or ETH. - Enter a recipient wallet address or ENS name. - Enter an amount in token or USD terms. - Review the estimated transaction fee, gas cost, node fee, platform fee, total required amount, and estimated completion time. - Send to one recipient or create a batch payment to multiple recipients. - Add batch recipients manually or import them from CSV. - Review the transaction before submitting it. - Follow the approval, escrow deployment, delivery, and completion steps. - Send another payment or open the completed transaction details. The transaction-history experience is stored in the user's app and is available at: - https://www.mirageprivacy.com/#/history History shows transaction amounts, recipients, statuses, dates, times, fees, and the on-chain steps associated with each transaction. When permitted by transaction state, the detail view can also offer cancellation and withdrawal. ## Product Characteristics ### No Mixing Mirage is not a mixer or privacy pool. Users are only ever responsible for their own funds. There is no shared risk and no commingled liquidity. ### Fast and Stealth Transactions complete in under 90 seconds on Ethereum with a minimal on-chain footprint, so use of Mirage is not obvious to outside observers. ### Native Mirage operates natively on the chains it supports. Users do not bridge to a separate blockchain or take on extra trust assumptions. ### Sovereign Users do not hand over custody of their funds. They remain in charge. ## Who Mirage Is For ### Businesses The job: pay contractors and vendors without showing the world the business's treasury. With Mirage: each payment gets its own escrow. Amounts stay private, and recipients see a normal incoming transfer without seeing the payer's transaction history. Settlement takes about 90 seconds on Ethereum. ### Individuals The job: send stablecoins or ETH without exposing an entire wallet to observers. With Mirage: users make a private transfer that arrives like a normal transfer without commingling assets, adopting a new wallet, or bridging to another chain. ### DAOs The job: pay contributors and grants without publishing every amount in the multisig. With Mirage: per-transaction privacy keeps pay and grant sizes confidential. Each DAO decides what should remain transparent under its own internal policies. ### Builders The job: add private payments without building the privacy layer from scratch. With Mirage: builders get a drop-in SDK with per-transaction escrow, built-in screening, and settlement in about 90 seconds on Ethereum. The website says it takes less than five hours to integrate and test. ## Developer SDK Mirage ships as a single JavaScript SDK. Wallets, apps, and custodians can add private stablecoin payments directly to their own products without rebuilding a privacy protocol. - SDK documentation: https://docs.mirageprivacy.com ## Trust and Compliance Mirage's position is that privacy and compliance are not opposites. It is designed to keep payments private while screening for illicit funds. ### Screened Before Broadcast The API runs blockchain analytics to ensure funds did not originate from illicit activity. ### No Mixing Funds are never pooled or commingled with anyone else's funds. Every payment uses its own escrow, so users do not inherit shared risk. ### Ordinary Look On-chain, a Mirage payment looks like a normal stablecoin transfer. The recipient receives an ordinary transaction, with nothing special to explain or flag. ### Compliant by Design Liquidity is screened before it enters the system, and every transfer carries a compliance certificate. The goal is privacy for legitimate users without harboring bad actors. ## How Mirage Compares Mirage separates payer and recipient without pooling funds. The recipient gets a normal stablecoin transfer, not a withdrawal from a known privacy protocol. The comparison below was reviewed in July 2026 against official documentation. Examples vary, and timings depend on network and pool activity. ### No Mixing or Commingling - Mirage: yes. One single-use escrow is created for each payment. - Mixers such as Tornado Cash Classic: no. Deposits share a known pool. - Privacy chains such as Zcash and Monero: no. Mixing or blending happens at chain level. - Privacy pools such as 0xbow: no. Deposits share an approved pool. ### Settlement Speed - Mirage: under 90 seconds on Ethereum and under 6 seconds on faster networks. - Mixers: good privacy can take hours, days, or weeks as the pool grows. - Privacy chains: about 75 seconds on Zcash or 2 minutes on Monero to first confirmation. - Privacy pools: good privacy can take hours, days, or weeks as the approved set grows. ### DeFi Compatibility - Mirage: stablecoins arrive as normal transfers, ready for wallets and DeFi. - Mixers: assets remain compatible after withdrawal, but pool use requires a separate flow. - Privacy chains: users need a separate coin, network, and wallet that are not directly compatible with Ethereum DeFi. - Privacy pools: assets remain compatible after withdrawal, but pool use requires a separate flow. ### Compliance Risk - Mirage: wallets are screened before routing, and users never share pool exposure. - Mixers: classic pools accept unscreened deposits, and users share exposure to the same contract. - Privacy chains: there is no network-wide screening; users can share audit records. - Privacy pools: approved lists can exclude flagged deposits, but users still share pool exposure. ### Anonymity Set - Mirage: all stablecoin activity on the chain. - Mixers: only deposits in the same asset and fixed-amount pool. - Privacy chains: other private transactions across that chain. - Privacy pools: only deposits on the pool's approved list. ### Usage Privacy - Mirage: yes. Usage is stealth, and each contract's footprint changes. - Mixers: no. Both sender and recipient are clearly identified as mixer users. - Privacy chains: no. The recipient needs a special coin and wallet, so privacy use is obvious. - Privacy pools: no. Both sender and recipient are identified as privacy-pool users. Comparison sources: - Mirage: https://docs.mirageprivacy.com/understanding-mirage/how-mirage-compares/ - Tornado Cash: https://docs.tornado.ws/general/how-does-it-work.html - Zcash: https://zcash.readthedocs.io/en/latest/rtd_pages/basics.html - Monero: https://www.getmonero.org/resources/moneropedia/blockchain.html - Privacy Pools: https://github.com/0xbow-io/privacy-pools-core ## Frequently Asked Questions ### Is Mirage a mixer? No. Mirage never pools or commingles funds. Every payment runs through its own single-use escrow, so a user is only ever responsible for their own money. ### What does "private" mean? Payments look like ordinary stablecoin transfers on-chain. The recipient receives a normal transfer, and the link between sender and recipient is not exposed on-chain. Mirage provides private payments that look like normal payments; it does not claim to provide anonymity. ### How fast is a payment? A payment settles in about 90 seconds on Ethereum and in a few seconds on faster networks. ### Who holds the user's money? The user does. Funds move through an escrow contract the user deploys. There is no custodian, shared pool, or long lock-up. ### Is there a Mirage token? No. Mirage works with stablecoins and ETH users already hold. There is no protocol token to buy. ## About Mirage The About page is at: - https://www.mirageprivacy.com/#/about Mirage's belief is: "Privacy should feel normal, not suspicious." ### Why Mirage Was Built The problem is that public chains expose who users pay and how much. Mixers and pools add stigma, compliance risk, awkward user experience, and often hours or weeks of waiting. Mirage's solution uses no shared pool and no new blockchain. Every payment gets its own single-use escrow, so funds never mix. The system is non-custodial, token-free, screened up front, DeFi-native, and settled in about 90 seconds on Ethereum, with a minimal privacy footprint. The team describes itself as a group of mildly obsessive humans who looked at public blockchains and thought they were a terrible way to onboard people to stablecoins, so they made the experience better. ### Core Team #### Nima Rasooli - Role: Founder - Bio: Rust engineer who lived off stablecoins in different countries for most of his life without a bank account. - To Nima, privacy is: being able to decide what he reveals about his life and property without giving up self-custody. - X: https://x.com/0xNimaRa - LinkedIn: https://www.linkedin.com/in/nima-rasooli/ - Email: mailto:nima@mirageprivacy.com - Website: https://nimara.xyz #### Samuel Alake - Role: Founding Engineer - Bio: Rust engineer. Three-time rewriter of the same contract variation engine. Hates readable code. Loves plausible deniability. - To Samuel, privacy is: normal. Broadcasting every payment to strangers is the strange part. - X: https://x.com/g4titan_ - LinkedIn: https://www.linkedin.com/in/samuel-alake-91694b238/ - Email: mailto:alake@mirageprivacy.com - Website: https://g4titan.com #### Ossian Mapes - Role: Founding Protocol Engineer - Bio: Protocol engineer. Builds the cryptographic machinery that makes private payments feel ordinary. Suspicious of edge cases. Fond of proofs. - To Ossian, privacy is: agency. A public ledger should verify the payment, not publish a user's life. - X: https://x.com/ozwaldorf - LinkedIn: https://www.linkedin.com/in/ozwaldorf/ - Email: mailto:oz@mirageprivacy.com - Website: https://ossian.dev ### Advisors The advisors are battle-tested operators and builders who help Mirage avoid the mistakes that kill projects early. #### Cédric Waldburger - Bio: Engineer turned founder turned VC. Gravitates toward things that are hard to pitch at dinner parties. Mirage checked every box. - X: https://x.com/cediwaldburger - LinkedIn: https://www.linkedin.com/in/cedricwaldburger/ #### Artia Moghbel - Bio: Former COO at DFINITY and now an investor at Draft VC. Artia helps founders skip the mistakes most do not see coming. - X: https://x.com/artia - LinkedIn: https://www.linkedin.com/in/artiam/ #### Deltatiger - Bio: DeFi veteran who survived multiple "DeFi summers," has seen every yield scheme twice, and helps Mirage avoid the traps. - X: https://x.com/deltatigernz ## Backers Mirage lists the following backers: - Kyber Knight Capital: https://kyberknight.com/ - Seed Club: https://seedclub.ventures/ - Code & State: https://www.codeandstate.com/ ## System Status The public status page is at: - https://www.mirageprivacy.com/#/status It reports the currently selected chain and live health information for: - The Mirage frontend and deployed frontend version. - The Nomad API and its enclave attestation. - The expected enclave signer, enclave-code identity, encryption public key, debug-mode state, and chain ID when available. - The Mirage API and its version. - The active network RPC and client version. The status page is dynamic. Visit the route for current operational state; this file does not claim that a service is presently online or offline. ## Company - Company: Mirage Technologies AG - Location: Zug, Switzerland - Website: https://www.mirageprivacy.com - Contact: mailto:whisper@mirageprivacy.com ## Canonical Links - Website and send app: https://www.mirageprivacy.com/#/ - About: https://www.mirageprivacy.com/#/about - Transaction history: https://www.mirageprivacy.com/#/history - System status: https://www.mirageprivacy.com/#/status - Closed-alpha waitlist: https://waitlist.mirageprivacy.com - Documentation: https://docs.mirageprivacy.com - Blog: https://blog.mirageprivacy.com - Analytics: https://metrics.mirageprivacy.com - Careers: https://github.com/MiragePrivacy/jobs - GitHub: https://github.com/MiragePrivacy - X: https://x.com/mirageprivacy - Discord: https://discord.gg/FCcKwPyBxV - Privacy Policy: https://docs.mirageprivacy.com/compliance/privacy-policy - Terms of Service: https://docs.mirageprivacy.com/compliance/terms-of-service