By Chainwire
4 min read
Zug, Switzerland, April 15th, 2026, Chainwire
Backed by Seed Club Ventures and Kyber Knight, Mirage introduces a non-custodial protocol for private stablecoin transfers that avoids shared pools, is hard to distinguish from ordinary activity, and settles quickly on Ethereum and compatible networks.
In Brief
Mirage, a privacy protocol for stablecoin transfers on Ethereum and EVM-compatible networks, today announced its seed round led by Seed Club Ventures and Kyber Knight, alongside participation from Deltatiger, Valeriy Zamaraiev, and Brian Gerrard, and its closed alpha launch. The company previously completed a pre-seed raise through Code & State in Q1 2025, before closing its seed round in Q4 2025.
Founded by Nima Rasooli in November 2024, Mirage is focused on a persistent gap in crypto infrastructure: private digital dollar payments on public blockchains that are fast enough for real use, do not rely on shared mixer-style pools, and do not require users to move onto a separate privacy chain.
Closed alpha access is now opening to waitlisted users. A broader mainnet rollout is planned for later in 2026.
How Mirage Is Different
Most onchain privacy tools ask users to accept at least one major tradeoff: visible interaction with a known privacy system, shared counterparty risk from pooled funds, or slow settlement that makes the product impractical for normal payments.
Mirage is built to remove those tradeoffs. It is designed so that using the protocol should not clearly identify a user as interacting with a privacy system. It does not use shared pools or mixers, which means users do not commingle funds with strangers or inherit their risk. And it is built for speed, with settlement times measured in seconds on faster EVM networks and under two minutes on Ethereum mainnet.
This makes Mirage relevant for a broad range of stablecoin use cases, from everyday transfers to payroll, contractor payments, treasury operations, and business-to-business payments.
How It Works
Mirage does not route transfers through a shared pool. Instead, it uses transaction-specific escrow and a coordinated settlement flow that preserves privacy without exposing a direct onchain link between sender and recipient. It works with the stablecoins and networks users already rely on, and does not require a new token.
A core design goal is to make usage hard to distinguish from ordinary activity, reducing the stigma and risk signaling associated with conventional privacy systems. Recipients receive ordinary stablecoin transfers, deployments typically cost less than $5 on Ethereum mainnet at current gas prices, and an SDK allows wallets and applications to integrate Mirage without changing the assets or chains their users already use.
Built for Stablecoin Adoption
Mirage is being developed for users who want financial privacy without the friction and baggage associated with legacy privacy tools. By avoiding shared pools, Mirage reduces both the practical cost of privacy and the stigma that can come with using systems that visibly mark users as higher-risk. The result is a faster, simpler experience that is easier for mainstream users and businesses to adopt.
What Is Live Now
The closed alpha is running on Ethereum mainnet, Sepolia, and Tempo testnet. Mirage is currently working with early users and integration partners ahead of a broader release. A JavaScript SDK for wallet, custodian, and dApp integrations is available for development teams. Waitlist registration and documentation are available at mirageprivacy.com
About Mirage
Mirage is a privacy protocol for stablecoin transfers on Ethereum and EVM-compatible networks. It supports confidential transfers that look like ordinary onchain activity, without pooling or mixing user funds. The protocol is non-custodial, integrates compliance checks, and is built to easily plug into wallets, payment apps, and DeFi protocols. Mirage is headquartered in Zug, Switzerland.
Growth Lead
Demir Ametov
Mirage Technologies AG
whisper@mirageprivacy.com
Decrypt-a-cookie
This website or its third-party tools use cookies. Cookie policy By clicking the accept button, you agree to the use of cookies.