A business accountant needs to reconcile Monero transactions without accessing the ability to spend funds. A parent wants to verify that a teenager’s wallet is being used responsibly without taking direct control. An auditor must confirm that organizational reserves match reported balances while keeping spend authority with a hardware device. These scenarios share a common requirement: the ability to see transaction history, incoming payments, and current balances while explicitly denying the power to move money. Most cryptocurrency wallets conflate viewing rights with spending rights, forcing a choice between complete blindness and full control. Monero’s two-key architecture offers an alternative.
The separation of view keys and spend keys is not merely a convenience feature. It is a fundamental property of Monero’s cryptography that allows a wallet to be split into two asymmetric roles: one that monitors activity and one that authorizes movement. XMRWallet implements this distinction through a view-key-only mode that grants full transaction transparency while mathematically preventing any fund transfer. Understanding how this works, and where its protection begins and ends, determines whether the feature solves a genuine security problem or merely creates the appearance of separation without the substance.
Why Monero requires separate keys for different trust boundaries
Bitcoin and most other blockchains use a single private key (or key derivation path) to control both visibility and spending authority. This simplicity has a cost: whoever holds the key can do everything. Monero takes a different approach by design. Each wallet maintains two independent cryptographic secrets: a spend key that authorizes transactions and a view key that decrypts transaction metadata. The spend key is derived from the wallet seed, while the view key can be independently derived and shared without compromising spending power.
This separation exists because Monero’s privacy model is different from Bitcoin’s. Monero transactions use ring signatures and stealth addresses to hide the true sender and receiver from observers on the blockchain. The recipient’s stealth address is derived using the sender’s knowledge and the recipient’s view key, producing an address that only the recipient (holding the view key) can later recognize as belonging to their wallet. If the recipient never reveals the view key, no external observer can reliably determine which transaction outputs belong to them. However, the recipient themselves must be able to identify incoming payments to balance the wallet and manage address history.
The cryptographic insight is that identifying a payment to yourself does not require the same secret as spending it. A view-key-only wallet can decrypt transaction tags, calculate which stealth addresses correspond to received funds, and reconstruct the complete transaction history—all without ever holding the spend key. This is not a feature retrofit or a software limitation. It is a consequence of how Monero’s cryptography is structured. The view key is mathematically incapable of generating valid signatures, so no transaction can be sent from a view-key-only wallet, regardless of the software or the user’s intent.
The mechanics of view-key-only mode in XMRWallet
Creating a view-key-only wallet begins with extracting the view key from a complete wallet. In XMRWallet, a user with a full 25-word recovery seed phrase can export their view key, which is typically a 64-character hexadecimal string. Importing only that view key (without the spend key) into a new XMRWallet instance creates a read-only session. The imported view key allows the wallet to synchronize with the Monero blockchain, identify incoming transactions, calculate balances, and display address history.
The wallet authentication architecture in view-key-only mode remains cryptographic rather than account-based. There are no usernames, passwords, or centralized account stores to intercept. The view key itself serves as the credential; importing the correct view key grants access to that specific wallet’s transaction history. Since all key derivation occurs locally on the user’s device, XMRWallet never transmits the view key to external servers or stores it centrally. The wallet can connect to either a remote Monero node (for convenience) or a local node (for stronger privacy), but in both cases the view key remains on the device.
Synchronization in view-key-only mode follows the same protocol as a full wallet. The wallet queries the blockchain for outputs that match the view key’s stealth address derivation, retrieves the encrypted transaction metadata, and decrypts it locally. This process automatically happens after login, and the wallet displays incoming transactions, outgoing payments (if any were known to the device before the spend key was removed), and the current balance. However, the balance shown is the sum of outputs the view key can decrypt and identify as belonging to the wallet—not a server-maintained account balance. If a transaction was sent by the full wallet before the view key was exported, the view-key-only instance will not see it unless the view key was present during that transaction or the blockchain record is examined independently.
What view-key-only mode actually protects against
The primary threat model view-key-only mode addresses is accidental or coerced spending. If a business controller is authorized to monitor reserves but should not have unilateral spending power, or if a teenager’s guardian wants to observe activity without enabling unauthorized purchases, the view key creates a cryptographic barrier. A compromised device running XMRWallet in view-key-only mode cannot leak funds, because the software lacks the mathematical ability to construct a valid transaction, regardless of malware or coercion. An attacker with complete access to the view-key-only wallet cannot steal funds or move them without obtaining the spend key from somewhere else entirely.
This protection also extends to certain operational scenarios. An organization can distribute the same view key to multiple auditors, accountants, or compliance officers without requiring them to share a single spend key or trusting any one person with sole access. Each person running XMRWallet with the view key can independently verify the same transaction history and balance. The spend key remains with an isolated device, a hardware wallet, or a restricted individual whose role is to authorize transactions in response to properly documented requests. This separation of duties cannot be achieved with Bitcoin in the same way, because Bitcoin’s public-key cryptography does not support a read-only mode that is equally transparent.
The view key also offers transparency without disclosure. A user might want to prove to a tax authority or auditor that they own a certain balance at a specific point in time. Rather than revealing the spend key (which would expose all future transactions and require trusting the auditor forever), they can provide the view key. The auditor can then import it into their own XMRWallet instance and independently verify the balance and transaction history without any ability to move the funds. This is stronger than a centralized exchange account balance, where the exchange controls the keys and the user must trust its record-keeping.
Limitations and the boundaries of view-key-only security
View-key-only mode is not a complete delegation of authority in practice, even though it is mathematically absolute regarding spending. The first limitation is historical: a view-key-only wallet cannot see outgoing transactions that were sent using the spend key after the view key was extracted and the spend key was removed from that device. The spend key holder can move funds without the view-key-only wallet detecting it. For organizations, this requires a separate agreement or audit process to reconcile. If the spend key holder is trusted to report transactions accurately, this is manageable; if not, the view key’s transparency is incomplete.
Address management in view-key-only mode is also read-only. A user can view all generated subaddresses (which Monero uses to further partition the wallet for privacy), but cannot generate new subaddresses without access to the spend key. This is not a security vulnerability but an operational constraint. If a business uses a specific subaddress per customer, the person holding the view key cannot assign new customers to new addresses; they can only observe which addresses have received funds. For some workflows this is acceptable; for others it requires the spend key holder to periodically generate and distribute new subaddresses.
The node connection is another boundary to consider. If a user imports a view key into XMRWallet and connects to a remote Monero node, that node operator can observe which view key is querying the blockchain, which subaddresses are being checked, and the timing of those requests. This metadata does not reveal the spend key or enable transactions, but it does create a partial privacy leak regarding the wallet’s activity pattern. A local node eliminates this, but requires maintaining separate infrastructure. For auditing purposes, a trusted internal node is preferable; for a casual user, the trade-off between convenience and privacy may favor remote nodes despite the information leakage.
Recovery and backup for a view-key-only wallet differ from full wallet backup. The view key itself does not need secret backup because it cannot authorize spending. However, the device it resides on should be protected against loss, as losing the device means losing convenient access to the transaction history and balance. A new device can re-import the same view key (since it is not secret), but if the view key was accidentally modified or corrupted, recovery requires the original full wallet to re-export it. This inversion—where the read-only key is recoverable but the device is not—can be confusing to users accustomed to password-based account recovery.
When view-key-only separation adds meaningful security
The value of view-key-only mode increases when the monitoring role and the spending role have genuinely different risk profiles or trust relationships. A family office managing generational wealth might maintain the spend key on a hardware wallet held by senior partners, while operational staff use view-key-only access to verify distributions and expenses. If operational staff’s devices are compromised, no funds can be moved. If the hardware wallet is lost or damaged, it can be replaced or recovered from backup without affecting the ability to maintain transaction records, since the view key is independent.
Regulatory and compliance scenarios are similarly suited to this model. An exchange, custodian, or regulated entity holding Monero reserves can provide view-key-only access to auditors or government agencies without surrendering control. The auditor can run XMRWallet themselves and independently verify the balance, seeing the complete transaction history without requiring trust in the entity’s record-keeping or risking collusion. This is particularly valuable for jurisdictions that require proof of reserves but do not necessarily demand keys in escrow.
For individuals, the primary use case is reducing the attack surface of the spend key. If a person normally uses XMRWallet on an internet-connected device to check balances and review transactions, they can do so with only the view key. The spend key resides on a separate device, air-gapped or hardware-based, that is accessed only when transactions must be authorized. This layering does not prevent all attacks (a coordinated compromise of both devices would be devastating), but it raises the bar significantly. An attacker who gains access to the phone or computer cannot move funds without also compromising the separate signing device.
Practical workflows combining view-key-only and full wallets
A realistic setup might involve multiple devices and roles. Device A holds the 25-word recovery seed and the complete wallet, kept offline or on a highly restricted hardware device. Device B is an everyday phone or computer running XMRWallet with only the view key, used to check balances and review transactions without restriction. Device C is an audit or compliance system that also runs XMRWallet with the view key, maintaining a separate record of all transactions for reporting purposes. All three devices can import the same view key and will see identical transaction histories, yet only Device A can authorize spending.
For organizations, a more formal version separates custody from operations. The spend key is held by a custody provider, a secure facility, or a multi-signature setup (where Monero supports it). The view key is distributed to finance, accounting, and compliance teams, each running XMRWallet independently. Regular reconciliation ensures that the view-key-only wallets detect all transactions. Any discrepancy between what the view key shows and what the spend key holder reports would indicate misappropriation or record tampering. This design assumes that the view key holder is not actively trying to collude with the spend key holder, but it does create an independent audit trail that single-signature systems cannot match.
A technical consideration for such workflows is node synchronization. If multiple view-key-only wallets are querying the same remote node, the node can correlate the requests and infer that they are monitoring the same underlying wallet. For organizations with strict privacy requirements, running a dedicated internal node that only authorized wallets connect to is the appropriate solution. This requires maintaining Monero node infrastructure, which adds operational complexity but strengthens both privacy and the auditability of the monitoring process itself.
The assumptions that make view-key-only mode sufficient
View-key-only mode provides meaningful protection when the threat model is accurately defined. If the primary risk is accidental spending, device malware, or coercive pressure, the cryptographic impossibility of spending from a view-key-only wallet is a genuine safeguard. If the risk includes the view key holder actively attempting to deduce the spend key through cryptanalysis, Monero’s mathematics make this computationally infeasible with current algorithms. If the risk is that an attacker with physical access to the device might extract credentials, view-key-only mode is safer than a full wallet, but it does not eliminate the risk entirely—the attacker still gains access to a complete, detailed transaction history.
The assumptions become problematic when the monitoring role is expected to catch misbehavior by the spending role, but both parties have access to the same underlying blockchain. Monero’s privacy means that if the spend key holder wishes to obscure a transaction from the view key holder, they can use the spend key on a completely different device or application, and the transaction will still be visible on the blockchain to anyone holding the view key. In this sense, Monero creates stronger auditability than some other systems. However, the view key holder cannot see the *reason* for a transaction—only that it occurred and approximately when. For forensic purposes, the spend key holder must cooperate by documenting the business rationale.
The strongest use of view-key-only mode combines it with clear operational policies and periodic audits. The technical mechanism ensures that unauthorized spending is impossible, but it does not itself verify that authorized spending is appropriate. An organization using view-key-only monitoring should establish review procedures, approval workflows, and documentation standards separate from the wallet itself. The view key becomes a detective tool, not a preventive one, except for the specific risk of spending without authorization.
Future considerations for view-key-only wallets
As Monero’s ecosystem develops, view-key-only wallets may gain additional features. Better support for view-key-only subaddress generation (if cryptographically feasible) would improve operational flexibility. More sophisticated reporting tools that aggregate multiple view-key-only imports could streamline reconciliation for organizations managing many wallets. Standardized formats for sharing view keys with third parties could reduce manual entry errors and make the process more accessible to non-technical users.
However, the fundamental value proposition of view-key-only mode is unlikely to change: it is the only method in Monero to grant complete transaction visibility while mathematically preventing any spending authority. As privacy-focused systems become subject to greater regulatory scrutiny, this capability may become increasingly important for organizations that need to demonstrate reserves and transaction history to auditors or authorities without surrendering custody. The technical design of XMRWallet and similar non-custodial wallets supports this use case by keeping all key material and derivation local, with no central account system that could be compromised or forced to grant unintended access.
Frequently asked questions
Can I generate new subaddresses with only the view key?
No. Generating new subaddresses requires access to the spend key, as new addresses are derived from the spend key’s secret material. A view-key-only wallet can display and monitor all existing subaddresses that were generated when the full wallet was in use, but cannot create new ones. For workflows where address generation is needed, the spend key holder must periodically generate and distribute new addresses.
What happens to transactions sent after I extract the view key?
A view-key-only wallet cannot see outgoing transactions that were sent using the spend key on a different device or application after the view key was extracted. It can see incoming transactions because those are identified using the view key itself. For complete auditability, the spend key holder should report or log outgoing transactions separately, or maintain the full wallet on a monitored device.
Is the view key safe to share with auditors or third parties?
Yes, the view key is safe to share because it cannot authorize transactions. However, sharing it does reveal all transaction history and balances to that person. They will also be able to see the timing of queries if they observe network traffic. For privacy-sensitive situations, distribute the view key through secure channels and consider whether the auditor should connect through an internal node rather than a public remote node.
