Cake Wallet Web: Setting Up Multiple Subaddresses for Different Payment Streams Without Cross-Linking
A merchant accepts payment in Monero from three separate customer categories: retail buyers, wholesale distributors, and affiliate partners. Using a single receiving address for all three sources creates an obvious problem: any observer analyzing the blockchain can see that funds from different contexts are flowing into the same wallet address, establishing a relationship between customer types that should remain distinct. The merchant’s transaction graph becomes a liability.
Cake Wallet’s subaddress feature solves this by generating multiple receiving addresses from a single seed phrase, each isolated from the others in terms of privacy. Unlike creating separate wallets entirely—which would require managing multiple recovery phrases and fund consolidation—subaddresses maintain complete fungibility while allowing the wallet to track distinct payment streams separately. The method is not novel; it is a core part of how Monero is designed. What matters for practical use is understanding how to set it up correctly, when to use it, and what it does and does not prevent.

Why Monero subaddresses exist and how they differ from reusing one address
The fundamental problem is that Monero, despite its privacy features, still requires a receiving address. When a user publishes an address or provides it to a customer, that address becomes a publicly known identifier. If the same address is used repeatedly, an outside observer can recognize payments intended for the same recipient, even if transaction amounts and sender identities remain private due to Monero’s ring signatures and stealth addresses.
The Monero Project’s official documentation describes subaddresses as a standard way to generate unlimited receiving addresses from a single private key material. Each subaddress is mathematically distinct on the blockchain but controlled by the same wallet. When funds arrive at a subaddress, the wallet recognizes them immediately during synchronization because the wallet holds the view key needed to detect incoming transactions. No extra recovery information is needed; a single seed phrase recovers all subaddresses.
The operational difference is significant. Without subaddresses, a user might rotate addresses by publishing a new public wallet address each time, but this requires manual tracking and coordination with counterparties. Subaddresses can be generated on demand, distributed to different customers or contexts, and then aggregated in a single wallet view. The merchant in the earlier example can assign a unique subaddress to each customer category, review consolidated balance and transaction history in one application, and maintain privacy separation without operational chaos.
From the blockchain’s perspective, payments to different subaddresses appear as transactions to distinct addresses. An observer cannot determine that they belong to the same wallet without access to the private view key. This creates a practical boundary: anyone who knows both subaddress A and subaddress B, and who can confirm they belong to the same wallet, has learned something about the wallet’s structure. But a customer who receives a payment address from an affiliate merchant should not be able to link that address to the merchant’s retail customer base simply by looking at the blockchain.
Setting up subaddresses in Cake Wallet Web and mobile applications
The process begins with a working Monero wallet in Cake Wallet. The application supports multiple seed types, including Polyseed, 25-word Monero seeds, and BIP39 seeds. When creating a new wallet or restoring from an existing seed, users should verify that they have selected the Monero network and a restore height appropriate to when their wallet was first used. This prevents unnecessary scanning of the entire blockchain history and accelerates synchronization.
Once the wallet is open and synchronized, accessing subaddresses depends on the platform. On mobile versions of Cake Wallet, the subaddress section is typically accessible from the main wallet screen or settings menu. On cake wallet web, the interface follows a similar structure, with a dedicated area to view existing subaddresses and generate new ones. The application displays each subaddress with its associated label, allowing users to assign names such as “Retail,” “Wholesale,” or “Affiliate” to track which payment stream each address receives.
Generating a new subaddress requires only a few taps or clicks. No confirmation transaction, fee, or blockchain interaction is needed. The new address exists immediately in the wallet and can be used for receiving funds. The wallet maintains a sequential index for each subaddress; the primary address used during initial setup is index 0, and each newly generated subaddress increments the index. This indexing is internal to the wallet and does not appear on the blockchain, but it allows recovery of the correct subaddresses if the wallet is restored from the seed phrase alone.
Best practice is to generate subaddresses before distributing them to customers or payment sources. A user can create several addresses ahead of time, label them clearly, and then provide the appropriate address to each counterparty. Changing or regenerating subaddresses after funds have already arrived is unnecessary; the wallet will continue to recognize and receive payments at any previously generated subaddress for as long as the wallet exists.
Privacy boundaries: What subaddresses protect and what they do not
Subaddresses are not a replacement for responsible address management. A subaddress provides privacy against casual observers who see one address but do not know it belongs to you. It does not prevent a customer from learning more about you if they already have other information. Consider a scenario: a customer pays Invoice A to subaddress A, and separately learns your name through a business registration or social network. That customer can now search the blockchain for transactions involving you, potentially revealing that subaddresses A and B belong to the same entity if you later publish both addresses or if they receive funds during the same transaction batch.
The threat model is therefore contextual. Subaddresses are most valuable when the recipients are not in direct contact and cannot correlate information across sources. A retail customer and a wholesale buyer, operating independently, would not ordinarily cross-reference payment addresses. But if a security researcher, law enforcement, or a motivated adversary obtains records from multiple sources and can link them to the same entity, subaddresses offer limited protection. Privacy depends on the sum of available information, not on any single tool.
Similarly, subaddresses do not obscure the amount sent or received. Monero’s ring signatures and stealth addresses hide the sender’s identity and the transaction inputs, but the output amounts are still visible on the blockchain unless additional privacy measures are taken. A user receiving payments of exactly 1.5 XMR at five different subaddresses may still present a recognizable pattern to outside analysis. Varying amounts and spacing out payments in time can help, but operational discipline matters as much as cryptographic technique.
Another important boundary is that subaddresses are not separate wallets. They all share the same private key material derived from the seed phrase. If the seed phrase is compromised, all subaddresses are compromised equally. Backing up the seed is still the critical step; losing the seed means losing access to every subaddress associated with it. By contrast, if a user wanted true isolation—so that compromise of one receiving address or part of the wallet could not affect others—separate wallets and separate seeds would be required. That creates operational overhead but offers stronger isolation.
Monero subaddresses combined with other privacy practices
Using subaddresses effectively requires awareness of other privacy practices in Monero. Monero’s design includes ring signatures, stealth addresses, and RingCT (Ring Confidential Transactions), which collectively hide transaction amounts, sender identity, and transaction relationships. Subaddresses work alongside these features but are distinct from them. A subaddress is about receiving address separation; ring signatures are about sender anonymity in a transaction; stealth addresses are about preventing observers from linking a transaction output to a published address.
For a privacy-conscious user, the workflow might look like this: generate a unique subaddress for each customer or payment context, distribute those addresses as needed, and then monitor each subaddress separately within the wallet interface. When consolidating funds—moving money from multiple subaddresses to the same destination—the user should be aware that this consolidation happens on the blockchain and can create a transaction that links multiple addresses to the same wallet. If the goal is to avoid revealing that addresses A and B belong together, consolidation defeats that goal. Instead, funds can be held separately at each subaddress or consolidated to an intermediate address using an atomic swap or decentralized exchange before moving to a final destination.
Cake Wallet’s integration with Tor (marked as experimental) can add a network-level privacy layer. When enabled, the wallet routes its synchronization through the Tor network, obscuring the user’s IP address from the Monero node and network observers. This complements address-level privacy but should not be confused with it. A user connecting via Tor still needs to manage subaddresses and payment consolidation carefully; network privacy does not replace transaction privacy.
Testing and verification before relying on subaddresses for sensitive payment streams
Before using subaddresses to separate sensitive payment flows—such as anonymous donations, cross-border transfers, or payments from multiple employers—a user should run through a test. This involves creating a new subaddress, sending a small amount of Monero to it from an external source, and confirming that the wallet receives and correctly identifies the payment. This step reveals whether the user understands the wallet’s interface, whether synchronization is working correctly, and whether the subaddress was generated correctly.
A common mistake is generating a subaddress, sharing it with a counterparty, and then restoring the wallet from a different seed phrase (or the same seed phrase but with an incorrect restore height) and expecting the subaddress to still be present. Subaddresses are derived from the seed mathematically, so they will regenerate in the correct order if the wallet is restored. However, if the wallet is restored with the wrong parameters or a wrong seed, the subaddresses will not match. Testing this recovery process without risking real funds is prudent. Users can create a test wallet, generate several subaddresses, note them down, then restore the wallet from the seed phrase and verify that the same subaddresses appear in the same order.
Restore height is another critical parameter. If a wallet is restored with a restore height of 0 (the beginning of the Monero blockchain), synchronization will take a very long time and place unnecessary load on nodes. If the restore height is set to a point after the wallet was first used, the wallet may miss incoming transactions. The correct restore height is typically a block number from around the time the wallet was created or first received funds. Cake Wallet provides tools to adjust this, but users should understand that restore height and seed phrase are both necessary to recover a wallet correctly.
Address checkers and the limits of verification
A question that often arises is whether an “address checker” or third-party tool can verify that a given Monero address belongs to a specific entity or that two addresses are linked. The short answer is no. Monero’s privacy model intentionally makes it impossible for an outside party to link addresses or verify ownership without access to the wallet’s private keys. A tool that claims to do so is either using incomplete information or making inferences based on pattern recognition rather than cryptographic proof.
This is different from Bitcoin, where the blockchain is transparent and address clustering and heuristics can sometimes identify related addresses. Bitcoin’s protocol does not hide amounts or sender identity, so analysis tools can make probabilistic guesses about wallet ownership. Monero’s design specifically prevents this. An address checker for Monero would more appropriately be described as a transaction scanner that helps the wallet owner review their own transactions, not a tool for verifying addresses for external observers.
Users should be skeptical of any service claiming to link Monero addresses or to verify that an address belongs to a known entity. Such claims are typically either fraudulent (the service is phishing for private keys) or based on metadata outside the blockchain itself, such as payment records from an exchange or marketplace. The privacy property of Monero subaddresses is that they appear separate on the blockchain and require the private view key to recognize as belonging to the same wallet. An external observer cannot override this without access to the wallet itself.
Migration from centralized services and integrating subaddresses into existing workflows
Users migrating from closed services like MyMonero or Exodus to a self-custody wallet like Cake Wallet often face the question of whether to set up subaddresses from the beginning or use them later. The answer depends on the user’s privacy goals and operational complexity tolerance. If the user has been receiving payments at a single address and wants to start using subaddresses, the simplest approach is to generate new subaddresses for future payments and leave past funds at the original address. The wallet will still recognize and consolidate all funds correctly.
For users importing a recovery phrase from MyMonero or another service into Cake Wallet, it is important to verify that the seed type is correct. MyMonero used Monero’s standard 25-word seed format, which Cake Wallet supports. However, the restore height must be set to approximately when the wallet was first created or last used in MyMonero. If the restore height is unknown, users can find it by checking MyMonero’s records or by setting the restore height conservatively to an earlier block and allowing the wallet to synchronize.
Operational workflow changes when subaddresses are in use. Instead of maintaining a single wallet address and managing multiple payment streams externally, users can now organize receiving addresses within the wallet itself. This is particularly valuable for merchants, service providers, and organizations that receive payments from multiple sources. Each department, customer category, or project can have a dedicated subaddress, and financial reporting can be organized accordingly. Cake Wallet’s balance view can show the total, while the subaddress section shows individual details.
Frequently asked questions
Can I use Monero subaddresses to hide my wallet’s total balance from an external observer?
No. Subaddresses separate receiving addresses on the blockchain, but they do not hide the total balance within your wallet. If someone knows that subaddresses A, B, and C belong to you, they can see the balance at each address. To truly hide your total balance, you would need to use multiple separate wallets with separate seed phrases. Subaddresses prevent linking separate addresses unless an observer already knows they belong together.
Do I need to use the Cake Wallet Web version to set up subaddresses?
No. Subaddresses can be set up on Cake Wallet Web, mobile (iOS and Android), macOS, and Linux versions. The feature is available across all platforms. Choose the version that fits your workflow: web for browser access, mobile for convenience, or desktop for local control. The subaddresses are the same regardless of which version you use to create them, as long as they are derived from the same seed phrase.
If I restore my Monero wallet from the seed phrase, will my subaddresses still be there?
Yes. Subaddresses are mathematically derived from your private key, so they will regenerate in the same order during restoration. If you create subaddresses A, B, and C before losing your wallet, then restore from your seed phrase, Cake Wallet will recreate subaddresses A, B, and C in the same order automatically. However, the restore height must be set correctly so the wallet scans the blockchain back to when those subaddresses first received funds.
