1. Choosing a topic
We write guides for questions people actually ask — "what is a crypto wallet", "how do bridge fees work", "can a transaction be reversed". We do not create pages to target keyword variations that would duplicate an existing guide.
2. Structure: answer first
Every guide opens with a Quick answer that responds to the question directly in two to four sentences. The rest of the page then supports that answer: a fuller explanation, how the mechanism works step by step, key facts, risks and limitations, an FAQ, and a list of sources.
3. Sources
We prioritise, in this order:
- The protocol's own specification or developer documentation.
- Technical standards (for example BIPs, EIPs) and standards bodies such as NIST.
- Established security-research and consumer-protection organisations.
- Reputable primary reporting for events and figures.
Each guide lists its sources with outbound links so you can check the claims yourself. We avoid citing marketing pages, price-prediction sites, or unverifiable social posts as facts.
4. Review
Drafts — including any prepared with AI assistance — are checked line by line against the sources by a human editor before publishing. We specifically check that no sentence implies a guaranteed return, a "free money" method, or a technically impossible action such as reversing a confirmed transaction.
5. Updates and corrections
Each guide shows a "last updated" date. We revisit guides when a protocol changes, when best practice shifts, or when a reader reports a problem. Send corrections to [email protected] with the URL and the specific issue; substantive fixes are made on the page and the date is bumped.
6. Scope and limits
Our guides explain technology. They are not personalised advice, they cannot cover every jurisdiction's rules, and they do not track live prices. Where a topic carries real financial risk, we say so plainly rather than smoothing it over.