Privacy by default
A privacy system is strongest when ordinary use does not create a visibly weaker transaction class.
Sovereign money
Monero
Financial privacy is not concealment for its own sake. It is control over who can map your identity, balances, relationships, and behavior.
Primary reading
Mastering Monero, First Edition
- Author
- SerHack and the Monero Community
- Edition
- First edition, December 2018
- PDF release
- April 18, 2019
- Reading mode
- Principles first; current commands require re-verification
This page is an original synthesis of the book, not a replacement for it. The book's text is licensed CC BY-NC-SA 4.0. No cover art or book illustrations are reproduced here.
Read the original PDFFirst principles
What remains durable after the software changes.
Fungibility
Money works better when equal units remain interchangeable instead of inheriting public transaction histories.
Self-custody
Control follows the private spend authority. Backups and recovery are therefore part of the security model.
Verify, do not trust
Open code, independently checked software, and a validated node path reduce hidden third-party assumptions.
Privacy stack
Transaction privacy is a composition of protections.
01
Sender
Ring signatures obscure which eligible output was actually spent, providing plausible deniability for the source.
02
Recipient
One-time stealth addresses prevent a published receiving address from appearing directly on the blockchain.
03
Amount
Ring Confidential Transactions conceal values while allowing the network to verify balance and prevent inflation.
04
Network metadata
Dandelion++ helps at the node layer, but it is not complete IP protection. Stronger network privacy requires an intentional Tor or I2P path.
Trust boundaries
Keys and nodes answer different security questions.
Spend authority
The mnemonic or private spend key can recreate spending control. Keep it offline, private, and recoverable.
View authority
A private view key reveals incoming transaction visibility. Treat disclosure as a deliberate privacy decision.
Node path
A remote node cannot spend funds, but it can observe connection metadata and affect availability. A validated local node reduces that reliance.
2026 correction layer
The book is foundational, not operationally current.
Kovri is historical
The first edition presents Kovri as the future network privacy layer. The official Kovri repository is now archived; current documentation describes Dandelion++ and optional Tor/I2P.
Interfaces and parameters move
Wallet screens, RPC examples, address conventions, ring parameters, integrations, versions, fees, and storage estimates must be checked against current official documentation.
Privacy is not absolute
Protocol privacy does not neutralize endpoint compromise, exposed seeds, malicious software, exchange records, timing correlation, or careless network use.
Operating rules
EncryptedGuru Monero discipline
- Download wallet software only from official channels and verify the signed hash list before extraction.
- Learn and test on stagenet before using mainnet value.
- Prefer a fresh subaddress for each expected payment when the wallet supports the workflow.
- Never place a mnemonic, spend key, view key, wallet file, or recovery detail in chat, screenshots, repositories, or clipboard history.
- Treat remote nodes and block explorers as metadata observers; do not disclose transaction identifiers and private view material casually.
- Re-check current official documentation before following any command from a 2018 first edition.
Reading path
Use the book in layers.
Chapters 1-3: purpose, custody, and privacy concepts
Best starting point for the enduring mental model
Current technical specification
Use for present-day privacy components and protocol parameters
Current node documentation
Use for local-node configuration and network privacy
Mainnet, stagenet, and testnet
Use stagenet for learning without real value
Verify Monero binaries
Authenticate the signed hashes before running downloaded software