Explain something useful
Each guide answers a defined question with a practical example or decision framework. Topic hubs organize related guides; they are not pages that redirect readers to another website. We do not publish automated news summaries or create pages for every keyword variation.
Sources and AI assistance
Protocol documentation and standards are preferred for technical explanations. AI assists drafting and illustration. Generated artwork is conceptual, not a screenshot or evidence of a real event. Articles carry their publication date; dates should change only when substantive content changes. Source availability is not an endorsement of a product.
Links and relationships
References are selected for the reader’s next question. Links stay stable between visits. Related-publication links are disclosed in context. Paid placements, if introduced, must be clearly labeled and use appropriate sponsored link attributes. There are no paid placements in this edition.
Corrections and maintenance
Review material when protocol behavior or cited documentation changes. Material corrections should explain what changed and why. We do not claim independent expert review where none has occurred. See the correction process.
How a privacy claim should be explained
State what stays visible
A guide should name the observer, the information at risk, and the limit of each precaution. For example, a zero-knowledge proof may hide a secret without hiding the address that sends it. A broad claim of privacy needs that boundary made clear.