Stealth Address: What Is a Stealth Address in Crypto?A stealth address is a one-time blockchain address created for a recipient so that outside observers cannot easily link the payment to the recipient’s public addresStealth Address: What Is a Stealth Address in Crypto?A stealth address is a one-time blockchain address created for a recipient so that outside observers cannot easily link the payment to the recipient’s public addres

Stealth Address

2026/08/07 17:57
#Advanced

What Is a Stealth Address in Crypto?

A stealth address is a one-time blockchain address created for a recipient so that outside observers cannot easily link the payment to the recipient’s public address.

In crypto, stealth addresses are used to improve recipient privacy on public blockchains.

A normal crypto payment often shows the sender address, receiver address, asset, and amount on a public ledger.

This transparency is useful for verification, but it can expose a user’s financial activity.

A stealth address reduces this exposure by letting the sender create a fresh destination address for the recipient each time.

The official Monero stealth address documentation explains that stealth addresses allow the sender to create random one-time addresses for every transaction on behalf of the recipient.

The Ethereum ERC-5564 stealth address standard describes stealth addresses as a way for senders to generate private accounts that are exclusively accessible by recipients.

For beginners, the simplest explanation is that a stealth address is like a private receiving address made for one payment.

The sender can send funds to that address, the recipient can control the funds, and outsiders cannot easily connect the address to the recipient’s public identity.

Stealth addresses are not the same as hiding the entire transaction, but they can make recipient linking much harder.

Why Stealth Addresses Matter

Stealth addresses matter because public blockchains expose more information than many users realize.

If one public address is reused, anyone can inspect that address and see its transaction history, token balances, counterparties, NFT activity, DeFi interactions, and possible behavior patterns.

This can create personal safety risks, business privacy risks, salary privacy risks, donation privacy risks, and treasury privacy risks.

A user may want to receive crypto without revealing that all payments belong to the same wallet identity.

A company may want to pay contractors without exposing a full wallet graph.

A donor may want to support a public cause without revealing personal financial links.

An NFT collector may want to receive an asset without connecting it to a known address.

Stealth addresses address this problem by breaking the obvious public link between a recipient’s published address and the address that receives a specific transfer.

Vitalik Buterin’s guide to stealth addresses describes the core idea as giving the same privacy benefit as the recipient generating a fresh address for every transaction, but without requiring the recipient to interact with the sender each time.

This non-interactive design is important because it keeps receiving crypto simple while improving privacy.

How a Stealth Address Works

A stealth address system usually begins with the recipient creating a stealth meta-address.

A stealth meta-address is not the final receiving address.

It is a public value that senders can use to generate unique one-time addresses for that recipient.

The recipient keeps private keys that allow them to detect and spend funds sent to those one-time addresses.

In many designs, the sender uses the recipient’s stealth meta-address and a fresh temporary key to create a new stealth address.

The sender then transfers the asset to that stealth address.

The sender also publishes a small piece of cryptographic information, often called an ephemeral public key or announcement data.

The recipient scans the public announcements and uses their viewing key to detect which stealth addresses belong to them.

After detecting a matching payment, the recipient derives the private key needed to control that stealth address.

Outside observers can see that a payment happened, but they should not be able to easily connect the one-time address to the recipient’s public identity.

Stealth Address vs. Public Address

A public address is a reusable receiving address that can be shared openly.

A stealth address is a one-time address created from a public stealth meta-address or similar privacy setup.

If a user receives many payments to one public address, those payments are easy to link together.

If a user receives many payments through stealth addresses, each payment can appear at a different address.

This makes blockchain analysis more difficult because the recipient’s real public identity is not directly shown as the receiver in every transaction.

A public address is easier to use and easier to scan manually.

A stealth address improves privacy but requires extra wallet support, key management, and transaction discovery logic.

A public address is usually enough for users who do not care about privacy or who are using a temporary address.

A stealth address is more useful when a user needs repeated receiving privacy without constantly creating and sharing new addresses manually.

The key difference is that a public address is usually reused, while a stealth address is meant to be unique for a specific transfer.

Stealth Address vs. Stealth Meta-Address

A stealth meta-address is the public information that lets senders create stealth addresses for a recipient.

A stealth address is the actual one-time address that receives a specific payment.

The Ethereum ERC-5564 standard defines a stealth meta-address as one or two public keys that can be used to compute a stealth address for a recipient.

This distinction is important because the recipient can publish a stealth meta-address without publishing every future receiving address.

A sender uses the stealth meta-address to generate a new one-time stealth address.

The recipient uses private viewing and spending information to detect and control the funds.

The stealth meta-address is reusable.

The stealth address should be unique.

Confusing these two terms can lead to privacy mistakes.

A user should share the meta-address or use a registry that exposes the meta-address, while the final stealth addresses should be generated per transfer.

Stealth Address vs. Disposable Address

A disposable address is a fresh address that a user manually creates for a single purpose.

A stealth address is generated by the sender for the recipient using cryptographic information.

Both methods can reduce address reuse.

The difference is workflow.

With disposable addresses, the recipient must create and send a new address to every sender.

With stealth addresses, the recipient can share one stealth meta-address and let senders generate unique receiving addresses automatically.

This makes stealth addresses more scalable for repeated payments.

Disposable addresses can still be useful for simple privacy when the recipient and sender communicate directly.

Stealth addresses are more powerful when the recipient wants a public receiving identity without exposing all incoming payments to the same address.

The main advantage of stealth addresses is non-interactive privacy.

Stealth Address vs. Privacy Coin

A stealth address is a privacy technique.

A privacy coin is a cryptocurrency or blockchain system designed with privacy features as a core part of the protocol.

Monero uses stealth addresses as one part of its privacy design.

Monero also uses other privacy mechanisms to hide different transaction details.

Other blockchains may add stealth address standards without becoming fully private by default.

For example, stealth addresses on an account-based smart contract platform can improve recipient privacy but may still expose asset type, timing, funding patterns, and spending behavior.

This means stealth addresses are not the same as full transaction privacy.

They mainly help hide the link between a recipient’s public identity and the one-time receiving address.

They may need to be combined with other privacy tools to protect sender privacy, amount privacy, and spending privacy.

A stealth address improves one important part of privacy, but it is not a complete privacy system by itself.

Stealth Addresses in Monero

Monero is the best-known example of a cryptocurrency where stealth addresses are part of the default privacy model.

The official Monero documentation says the sender creates random one-time addresses for every transaction on behalf of the recipient.

The same documentation explains that the recipient can publish one address while incoming payments go to unique addresses on the blockchain.

This means outsiders cannot simply search a recipient’s public address and see every payment sent to it.

Monero users have a public address, a private view key, and a private spend key.

The view key helps detect incoming transactions destined for the account.

The spend key is used to spend funds.

This separation is useful because a user may share a view key for limited transparency without giving spending power.

Monero’s stealth address design is stronger when combined with the rest of Monero’s privacy system.

In the broader crypto glossary context, Monero shows how stealth addresses can be built directly into a protocol rather than added as an optional application layer.

Stealth Addresses on Ethereum and EVM Networks

Stealth addresses have also been developed as a standard for Ethereum and EVM-compatible networks.

The Ethereum ERC-5564 standard is marked as final and provides a standardized method for interacting with stealth addresses.

ERC-5564 focuses on non-interactive private transfers where a sender can generate a stealth address for the recipient.

The standard includes concepts such as stealth meta-addresses, spending keys, viewing keys, ephemeral public keys, and view tags.

The standard also defines an announcer contract that emits information recipients can scan to find payments meant for them.

The related ERC-6538 stealth meta-address registry defines a standard way to store and retrieve stealth meta-addresses.

ERC-6538 is useful because senders and applications need a reliable way to find a recipient’s stealth meta-address.

These standards are important because Ethereum has many assets, smart contracts, NFTs, and application accounts that may benefit from recipient privacy.

However, Ethereum-style stealth addresses can create fee-payment challenges because a newly generated stealth address may not have native gas tokens.

This means wallet design, account abstraction, relayers, paymasters, or other fee solutions may be needed for smooth user experience.

Viewing Key

A viewing key is a private key or secret used to detect stealth address payments without spending the funds.

In stealth address systems, the recipient may need to scan many announcements or transactions to find which ones belong to them.

The viewing key helps the wallet identify matching stealth addresses.

The viewing key should be protected because it can reveal incoming payment information.

However, a viewing key usually should not be able to spend funds by itself when the system separates viewing and spending roles properly.

This can support accounting, auditing, and monitoring workflows.

For example, a user may want a tax professional or internal accounting tool to view incoming payments without moving funds.

The official Monero documentation notes that a watch-only wallet can use a view key to display incoming transactions.

In Ethereum-style stealth address systems, viewing keys help recipients discover stealth transfers from announcement data.

The viewing key is therefore a privacy-sensitive monitoring key rather than a normal public address.

Spending Key

A spending key is the private key or secret that allows the recipient to spend funds from a stealth address.

The spending key is more sensitive than the viewing key because it controls assets.

If an attacker gets the spending key, the attacker may be able to move funds.

In many stealth address designs, the recipient uses the spending key together with derived information to control each one-time address.

ERC-5564 defines a spending key as a private key that can be used to spend funds sent to a stealth address.

A good wallet should separate viewing and spending operations clearly.

This helps users avoid sharing the wrong key for accounting, auditing, or monitoring purposes.

A user should never share a spending key with anyone they do not fully trust.

Backup procedures must also protect spending keys because lost spending keys can make assets unrecoverable.

Stealth address privacy is useful only if key management remains secure.

Ephemeral Public Key

An ephemeral public key is a temporary public key published by the sender as part of the stealth address workflow.

Ephemeral means it is used for a short time or one specific purpose.

The sender creates a temporary secret and uses it with the recipient’s stealth meta-address to generate a one-time receiving address.

The sender publishes the corresponding ephemeral public key so the recipient can detect the payment.

Vitalik Buterin’s stealth address guide explains that the sender publishes extra cryptographic data on-chain to help the recipient discover that a stealth address belongs to them.

This extra data does not give outsiders the recipient’s spending key.

It lets the recipient compute the shared secret needed to recognize the payment.

In ERC-5564, the ephemeral public key is part of the announcement data emitted for recipients to scan.

Without this discovery data, the recipient might not know which one-time addresses belong to them.

The ephemeral public key is therefore a discovery tool, not a public label of ownership.

View Tag

A view tag is a small value that helps wallets scan stealth address announcements more efficiently.

Scanning every announcement fully can be expensive or slow, especially on high-activity chains.

ERC-5564 includes view tags as a way to reduce parsing time for recipients.

The standard explains that a one-byte view tag lets users skip extra computations for most announcements that are not meant for them.

This matters because privacy tools must also be practical.

If wallets need too much computation to scan for payments, users may avoid the system.

A view tag improves usability by making discovery faster.

However, it also adds a small privacy trade-off because one byte of information derived from the shared secret is revealed.

ERC-5564 states that this reduces the security margin but does not affect secure generation of a stealth address.

View tags are a good example of the balance between privacy, efficiency, and wallet usability.

Non-Interactive Receiving

Non-interactive receiving is one of the biggest benefits of stealth addresses.

It means the recipient does not need to create and send a fresh address for every payment.

The recipient can publish a stealth meta-address once.

Any sender can use that meta-address to create a unique stealth address.

This makes privacy easier for donations, payments, NFT transfers, payroll, grants, and recurring transfers.

Without non-interactive receiving, privacy often depends on manual address rotation.

Manual address rotation is easy to forget and hard to scale.

Stealth addresses automate that process through cryptography.

This creates a better user experience because the sender can still pay the recipient without a private chat or new invoice.

Non-interactive receiving is one reason stealth addresses are considered important for mainstream crypto privacy.

Recipient Privacy

Stealth addresses mainly protect recipient privacy.

They help prevent outside observers from linking a payment address to the recipient’s known public address.

This is useful because recipient linking can reveal who is receiving funds and how often they receive them.

It can also reveal donation flows, customer payments, salaries, grants, sales, and collectible transfers.

However, recipient privacy is not the same as total transaction privacy.

The sender may still be visible.

The asset type may still be visible.

The transaction timing may still be visible.

The amount may still be visible on many blockchains.

Spending the funds later can also reveal patterns that reduce the original privacy benefit.

Sender Privacy

Stealth addresses do not automatically hide the sender.

If the sender uses a public wallet with known history, observers may still identify the sender side of the payment.

The stealth address mainly makes it harder to identify the recipient side.

A sender who needs privacy may need other tools, careful funding behavior, fresh wallets, privacy-preserving protocols, or network-level protections.

Even then, privacy can be weakened by timing, amounts, wallet behavior, and off-chain identity leaks.

This is why users should not overestimate stealth addresses.

They are an important building block, not a full anonymity guarantee.

A payment can be private in one direction and still leak information in another direction.

The best privacy design considers sender, recipient, amount, timing, network metadata, and future spending behavior together.

A stealth address solves the recipient-linking problem more directly than the sender-linking problem.

Amount Privacy

Stealth addresses do not necessarily hide the transaction amount.

On transparent blockchains, observers may still see how many tokens were sent to the stealth address.

This means a user could hide who received the payment but still reveal that a payment of a certain size occurred.

Amount privacy requires separate cryptographic tools or protocol-level features.

Some privacy-focused systems combine stealth addresses with methods that hide amounts.

Other systems use stealth addresses without hiding amounts.

This difference matters for users who need strong confidentiality.

A salary payment, donation, business deal, or NFT purchase can still leak sensitive information if the amount is visible.

Users should check what a specific stealth address implementation actually hides before relying on it.

Privacy should be evaluated by what information remains visible, not only by what the tool is called.

Stealth Addresses and NFTs

Stealth addresses can be especially useful for NFT transfers.

NFT ownership is often easy to trace because each token has a unique identifier and public ownership history.

If an NFT is sent to a known address, observers can connect the asset to the recipient’s public wallet identity.

A stealth address can let the sender transfer an NFT to a one-time address controlled by the recipient.

This can reduce the visible link between the NFT and the recipient’s main address.

However, there can be a practical problem with gas fees.

A new stealth address that receives only an NFT may not have the native asset needed to pay for future transfers.

Vitalik Buterin’s stealth address guide highlights this fee problem for NFT recipients who receive an asset at an address that has no native gas token.

Wallets and account abstraction tools may need to solve this for stealth NFT transfers to become user-friendly.

Until then, NFT stealth address workflows can be powerful but operationally complex.

Stealth Addresses and DeFi

Stealth addresses can improve privacy when users receive tokens that may later be used in DeFi.

However, DeFi activity can weaken stealth address privacy if the user later connects the stealth address to a known wallet or pattern.

For example, moving funds from a stealth address into a DeFi protocol may create new on-chain links.

Providing liquidity, borrowing, claiming rewards, bridging assets, or consolidating balances can reveal behavior patterns.

Stealth addresses protect the receiving step, but later actions still matter.

DeFi users should understand that privacy can be lost after the initial receipt.

A wallet that automatically moves stealth funds to a public main address may destroy much of the privacy benefit.

A privacy-aware DeFi workflow requires careful planning from receiving to spending.

Developers should design apps that do not accidentally expose stealth recipients through poor transaction flows.

Stealth addresses and DeFi can work together, but the privacy design must cover the full asset lifecycle.

Stealth Addresses and Wallet Design

Wallet support is essential for stealth addresses.

A user should not have to manually scan every blockchain announcement or derive every one-time key by hand.

A good stealth address wallet should generate stealth meta-addresses, detect incoming transfers, manage viewing keys, protect spending keys, display balances, and help pay fees from stealth addresses.

It should also explain what information remains public.

Poor wallet design can create privacy leaks.

For example, a wallet might query a public server in a way that reveals which stealth addresses the user is checking.

A wallet might consolidate funds too quickly and link addresses together.

A wallet might expose a viewing key or confuse it with a spending key.

Wallet infrastructure is therefore not a minor detail.

Stealth address privacy depends on both cryptography and implementation quality.

Stealth Addresses and Gas Fees

Gas fees are a major challenge for stealth addresses on account-based smart contract chains.

If a stealth address receives tokens but no native gas token, the recipient may be unable to move the tokens.

This is especially relevant for NFTs and non-native tokens.

The recipient may need someone to fund the stealth address with gas.

That gas funding transaction can create a privacy leak if it comes from a known account.

Alternative solutions may include relayers, paymasters, fee abstraction, sponsored transactions, or special transaction tickets.

Each solution has trade-offs in cost, complexity, trust, and privacy.

This is one reason stealth addresses are easier to explain than to deploy smoothly.

A practical stealth address system must solve both receiving and spending.

Privacy that cannot be used safely after receipt is incomplete.

Stealth Addresses and Compliance

Stealth addresses can raise compliance questions because they reduce visible recipient links.

Privacy is legitimate for personal safety, business confidentiality, donations, salaries, and financial autonomy.

At the same time, privacy tools can be misused by bad actors.

Users should understand the laws and reporting requirements in their jurisdiction.

Businesses that use stealth addresses may still need accounting records, tax records, sanctions screening, counterparty checks, and audit trails.

A stealth address does not remove legal obligations.

It only changes what is visible on the public blockchain.

Organizations may use viewing keys, internal logs, invoices, or controlled disclosure to balance privacy and compliance.

The official Monero documentation notes that view keys can support optional semi-transparency in some contexts.

Responsible use of stealth addresses requires both technical privacy and lawful recordkeeping.

Stealth Addresses and Blockchain Analytics

Blockchain analytics tries to identify patterns across public ledger data.

Stealth addresses make analytics harder by creating unique recipient addresses that are not obviously tied to a known public address.

However, analytics may still use timing, amounts, gas funding, withdrawal patterns, token movements, wallet behavior, and off-chain information.

This means stealth addresses can improve privacy but do not guarantee perfect unlinkability.

Academic work on Ethereum stealth address systems has shown that implementation details and usage patterns can weaken anonymity.

For example, the anonymity analysis of the Umbra stealth address scheme studied heuristics that could deanonymize or link some stealth payments.

This research does not mean stealth addresses are useless.

It means privacy tools must be used carefully and improved over time.

The strongest privacy comes from good cryptography, good wallet behavior, good fee handling, and good user habits.

A stealth address is a privacy layer, not a magic invisibility layer.

Benefits of Stealth Addresses

The first benefit of stealth addresses is reduced address reuse.

The second benefit is better recipient privacy.

The third benefit is non-interactive receiving through a reusable stealth meta-address.

The fourth benefit is improved privacy for donations, payroll, grants, payments, and NFT transfers.

The fifth benefit is less public linking between a user’s identity and incoming transactions.

The sixth benefit is compatibility with public blockchains when standards such as ERC-5564 are supported.

The seventh benefit is possible separation between viewing keys and spending keys.

The eighth benefit is better privacy hygiene for users who receive many transfers.

The ninth benefit is improved business confidentiality for on-chain payments.

The main value of stealth addresses is that they make private receiving more practical without requiring a new address request every time.

Risks and Limitations of Stealth Addresses

The first limitation is that stealth addresses mainly protect recipient linking, not every part of the transaction.

The second limitation is that amounts may remain visible on transparent blockchains.

The third limitation is that sender addresses may still be visible.

The fourth limitation is that later spending can link stealth addresses back together.

The fifth limitation is that gas funding can create privacy leaks.

The sixth limitation is that wallets must scan announcements and manage extra keys correctly.

The seventh limitation is that poor implementation can weaken privacy.

The eighth limitation is that users may misunderstand what the system protects.

The ninth limitation is that compliance obligations may still apply.

The tenth limitation is that user experience can be harder than ordinary address-based receiving.

Common Misunderstandings About Stealth Addresses

One common misunderstanding is that a stealth address makes a transaction completely invisible.

In many systems, the transaction still appears on-chain, but the recipient link is hidden or reduced.

Another misunderstanding is that stealth addresses hide the sender.

They usually focus on recipient privacy rather than sender privacy.

A third misunderstanding is that stealth addresses always hide amounts.

Many stealth address designs do not hide transaction amounts by themselves.

A fourth misunderstanding is that a stealth meta-address is the same as a stealth address.

The meta-address is reusable information used to generate one-time addresses, while the stealth address is the one-time destination.

A fifth misunderstanding is that stealth addresses remove the need for safe custody.

Users still need to protect viewing keys, spending keys, backups, and wallet software.

Best Practices for Users

Use wallets that clearly support stealth address workflows rather than trying to manage the process manually.

Understand whether the implementation hides only the recipient or also protects other transaction details.

Protect spending keys with the same care as normal private keys.

Treat viewing keys as sensitive because they can reveal incoming payment history.

Avoid automatically consolidating stealth address funds into a known public wallet.

Be careful when funding stealth addresses with gas from a known account.

Use small test transactions before relying on a stealth address workflow for meaningful value.

Keep records for accounting, tax, and compliance where required.

Do not assume that privacy tools remove legal obligations.

Remember that privacy can be weakened by timing, amounts, wallet queries, and future spending behavior.

Best Practices for Developers

Follow established standards such as ERC-5564 when building EVM-compatible stealth address tools.

Use the ERC-6538 registry pattern when applications need a standard way to find stealth meta-addresses.

Design wallets to scan announcements without leaking user interest to public servers.

Separate viewing and spending permissions clearly in the user interface.

Explain the gas-funding problem before users receive NFTs or tokens into empty stealth addresses.

Warn users when an action may link a stealth address to a known address.

Support clear backups for stealth meta-addresses, viewing keys, and spending keys.

Test privacy assumptions against realistic blockchain analytics heuristics.

Provide user education that explains what the tool does and does not hide.

Build privacy features with default-safe behavior instead of expecting users to make expert decisions every time.

FAQ

What does stealth address mean?

A stealth address is a one-time crypto address generated for a recipient so that public observers cannot easily link the payment to the recipient’s known address.

Is a stealth address the same as a private address?

A stealth address is private in the sense that it hides the recipient link, but it may not hide the sender, amount, timing, or future spending behavior.

What is a stealth meta-address?

A stealth meta-address is reusable public information that senders use to generate unique stealth addresses for a recipient.

Does Monero use stealth addresses?

Yes, Monero uses stealth addresses by default so that incoming payments go to unique one-time addresses on the blockchain.

Does Ethereum support stealth addresses?

Ethereum has final ERC standards for stealth addresses and stealth meta-address registries, including ERC-5564 and ERC-6538.

Do stealth addresses hide transaction amounts?

Not always, because many stealth address systems hide the recipient link but do not hide the transferred amount.

Can a stealth address receive NFTs?

Yes, a stealth address can be used for NFT transfers when supported, but the recipient may need a way to pay gas from that new address later.

What is a viewing key?

A viewing key helps the recipient detect incoming stealth address payments without necessarily being able to spend the funds.

What is a spending key?

A spending key is the private key or secret that allows the recipient to move funds from a stealth address.

Are stealth addresses completely anonymous?

No, stealth addresses improve recipient privacy, but complete anonymity also depends on sender privacy, amount privacy, network behavior, wallet design, and future spending patterns.

Conclusion

A stealth address is a privacy tool that creates a unique one-time receiving address for a crypto payment.

Its main purpose is to make it harder for outsiders to link a payment to the recipient’s public address.

Stealth addresses are especially useful because they allow non-interactive receiving, meaning the recipient can publish one stealth meta-address while senders generate fresh addresses for each transfer.

Monero uses stealth addresses as part of its default privacy design.

Ethereum and EVM ecosystems have standardized stealth address workflows through ERC-5564 and ERC-6538.

The core parts of a stealth address system include a stealth meta-address, ephemeral public key, viewing key, spending key, and discovery process.

Stealth addresses are powerful, but they do not automatically hide every part of a transaction.

They may not hide the sender, amount, gas funding, timing, or later spending behavior.

Wallet implementation and user behavior are just as important as the cryptography.

For users, stealth addresses can improve privacy for payments, donations, payroll, grants, NFTs, and repeated receiving activity.

For developers, stealth addresses require careful support for scanning, key separation, gas payments, account discovery, and privacy-preserving user interfaces.

In the crypto glossary context, Stealth Address means a one-time blockchain address generated for private receiving, usually from a reusable stealth meta-address and cryptographic data shared between sender and recipient.

The key takeaway is that stealth addresses reduce public recipient linking, but strong privacy still requires careful wallet design, safe key management, and awareness of what remains visible on-chain.