Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

The Problem and the Solution

Stablecoins are already easy to send. The hard part is using them without making your whole financial life public.

Mirage is built so a private stablecoin payment can feel close to a regular transfer: choose the recipient, enter the amount, confirm, and move on. The recipient gets a normal stablecoin transfer. The sender keeps more of their financial context private.

The product goal is simple: privacy should be available inside everyday wallet and payment flows, not hidden behind a slow or intimidating crypto-native process.

Why This Matters

Public blockchains make balances, counterparties, timing, and payment amounts visible to anyone watching the chain. That creates real friction for normal payments.

Businesses do not want payroll, vendor relationships, treasury movement, or customer payments exposed to competitors and data brokers. Individuals should not need to publish their financial graph just to use digital cash.

Most crypto privacy tools were designed for users who are willing to leave the normal payment flow. They may require a separate asset, a long wait, a known privacy pool, or a new chain. Mirage takes a different route: keep the stablecoin payment experience familiar and make the privacy layer work around it.

Mirage's Answer

Mirage moves payment coordination offchain while keeping settlement and verification onchain. The user does not need to understand those mechanics to send a payment, but the model matters for trust.

At a high level, Mirage works like this:

  1. The user creates a private payment request in a wallet, app, or SDK integration.
  2. Mirage coordinates with a node network to execute the payment.
  3. The recipient receives a standard stablecoin transfer.
  4. The node gets paid back only after onchain proof confirms the transfer happened.

The public chain still sees activity. Mirage's design avoids routing every user through the same recognizable privacy pool.

What Mirage Brings to the Table

Simple Payment UX

The user experience is intentionally plain: enter a recipient, enter an amount, add a tip for execution, and send. On supported L2s, Mirage targets settlement in seconds. On Ethereum mainnet, the target is under 90 seconds depending on network conditions.

Stablecoin-Native Payments

Users can send stablecoins such as USDC without first buying a volatile privacy asset or moving to a separate privacy network. That makes Mirage more natural for payroll, supplier payments, treasury operations, DAOs, wallets, and payment applications.

No Shared Pool

Each transaction uses its own temporary escrow. User funds are not mixed into a shared contract with unrelated users, and execution is verified before the node is reimbursed.

Privacy Without a Single Public Pool

Mirage is designed so an observer cannot rely on one known pool, asset, or contract to classify privacy usage. The goal is practical: let private stablecoin transfers look closer to normal public-chain activity than to a separate privacy product.

Careful Defense in Depth

Mirage uses contract variation through Azoth and confidential-computing nodes through Nomad, but neither is presented as a standalone guarantee. Azoth keeps unique escrows verifiable. Nomad nodes reduce what node operators can see while onchain proofs control when they are reimbursed.

Compliance-Aware Routing

Mirage can screen wallet origin and route orderflow to screened node operators without taking custody. This helps legitimate users access privacy without inheriting the risks of a shared pool.

What It Feels Like

The intended experience is not "use a privacy protocol." It is "send a private stablecoin payment."

That difference matters for mainstream use. People should not have to learn new assets, wait days, manage pool denominations, or explain why their wallet touched a known privacy contract. They should be able to use stablecoins with the kind of financial discretion they already expect from normal payment products.

See A Simple Example for the user flow and Technical Model for the full lifecycle.

Who Uses Mirage

Mirage is for people and teams that need financial privacy without leaving the normal stablecoin payment experience.

Businesses can protect payroll, vendors, and treasury movement. DAOs can pay contributors without broadcasting strategy. Wallets and payment platforms can add privacy as a native feature. Individuals can use stablecoins without exposing a public financial profile to data brokers, competitors, or attackers.

The guiding principle is simple: legitimate financial privacy should feel like normal payment infrastructure.