Stealth Addresses and Confidential Transactions
Privacy primitives that hide who's receiving what — from Monero's foundational stealth addresses to Ethereum's ERC-5564 and the legal context post-Tornado-Cash.
Why Address Privacy Matters
Most blockchains are fully transparent. If someone knows your address, they can see every transaction you've ever made, your full balance, your trading patterns, and where you send money. Even using a fresh address for each transaction (a Bitcoin best practice) often doesn't help — chain analysis tools cluster addresses by behaviour. Privacy primitives exist to break this surveillance: stealth addresses hide the receiving address, confidential transactions hide the amounts, and shielded systems combine both.
Stealth Addresses
A stealth address scheme lets you publish a single 'meta-address' that anyone can derive a fresh, unique one-time address from for each transaction they send you. The sender computes the one-time address using your public meta-address and some random data; only you can scan the chain and find which addresses are yours. Observers see seemingly-random addresses receiving payments and can't link them to your meta-address or to each other.
Confidential Transactions
Confidential Transactions (CT) hide the amounts being transferred. Instead of a plaintext amount, the transaction commits to a Pedersen commitment of the amount, with a cryptographic proof that the inputs and outputs balance (no money created or destroyed) and that all amounts are non-negative. Observers see encrypted blobs; only the sender and receiver know the actual values.
- Default crypto address privacy: poor — everyone sees everything
- Stealth addresses: hide who the recipient is
- Confidential transactions: hide the amount
- Shielded systems (Zcash, Monero): combine both plus sender privacy
Key Takeaways
- Most blockchains are fully transparent by default — pseudonymous, not anonymous
- Stealth addresses hide recipient identity by letting senders derive unique one-time addresses
- Confidential transactions hide amounts via cryptographic commitments
- Combining both with sender privacy gives fully shielded transactions (Zcash, Monero)
Related Content
Related Coins
Related Topics
Key Terms
More Topics
Browse all 179 topicszk-SNARK vs zk-STARK vs PLONK
How the three major proof-system families compare on trusted setup, proof size, prover cost, and quantum resistance — and which production rollups picked which.
Threshold Signatures and MPC
How t-of-n threshold signatures and multi-party computation let multiple parties sign together without any one holding the full key — the cryptography behind Fireblocks, Lit Protocol, and modern institutional custody.
Verifiable Random Functions
How VRFs produce randomness that's both unpredictable before commitment and cryptographically verifiable after — enabling fair lotteries, leader election, and on-chain randomness without trusted parties.
Hash Functions Compared
SHA-256, Keccak-256, Blake3, and Poseidon — which one each chain uses, why ZK systems needed a new family of 'arithmetic-friendly' hashes, and what tradeoffs each makes.
CDP Lifecycle
How collateralized debt positions work end-to-end — minting DAI against ETH, paying stability fees, surviving liquidations, and the structural lessons from MakerDAO's Black Thursday and Liquity's no-fee model.
Perpetual Swap Mechanics
How perp futures actually work — funding rates that keep them pegged to spot, mark vs index price, insurance funds that backstop losses, and the liquidation cascades that wreck overleveraged accounts in seconds.
Intent-Based Architectures
Why CoW Swap, UniswapX, Across, and 1inch Fusion moved from 'sign a transaction' to 'sign an intent' — and how solver competition delivers better prices and MEV protection.
MEV-Share Mechanics
How Flashbots' MEV-Share lets users share metadata about their transactions in exchange for a cut of the MEV searchers extract — a structural shift from 'searchers prey on users' to 'searchers and users share value.'
References & further reading
- primary
- secondary