# Mirage

## Docs

- [A Simple Example](/understanding-mirage/a-simple-example): Let's say Alice wants to send 100 USDC to Bob privately.
- [How Mirage Compares](/understanding-mirage/how-mirage-compares): Mirage differs from other privacy tools in fundamental ways. While other solutions, mostly mixers and privacy coins, rely on consolidating various users' funds in a shielded pool or smart contract and rely on the size of deposits and number of users to enhance their privacy guarantees, Mirage makes all stabelcoin activity be the anonymity set for each private transaction while providing usage privacy that protects the users against stigma.
- [The Problem And The Solution](/understanding-mirage/introduction): Privacy is a notoriously hard problem to solve on public blockchains. Over the years there have been many attempts at solving this significant issue, largely through privacy coins and mixers. Mirage takes a fundamentally different approach to address this issue on Ethereum, though Mirage can adapt the design for other networks such as L2s like Arbitrum and Base, or L1s like Solana.
- [The Undetectability Challenge](/understanding-mirage/the-undetectability-challenge): One of the core ideas behind Mirage is that **no one should know you used a privacy protocol to begin with**.
- [Nomad Overview](/nomad/overview): The Nomad network is a network of TEE-backed nodes that decrypt, validate, and execute client signals without exposing transaction details or node activity to any specific party.
- [Running a Nomad Node](/nomad/running-a-node): **Difficulty**: Medium (linux server management, cli usage)
- [An Introduction to Azoth](/azoth/introduction): Azoth is the most advanced open-source deterministic EVM bytecode obfuscator. It's the engine that makes Mirage's undetectability possible.