First principles
What a blockchain records, how signatures work, and why independent verification matters.
Read the transaction guideLEARNING DESK
Guides for building a mental model.
These guides assume no specialist background. They use plain language first, then add the technical detail needed to make the explanation useful.
Take one topic at a time. A reliable understanding is assembled through small, testable connections.
System roles
Validators, RPC providers, indexers, wallet teams, and users all see different parts of the same system.
Read the validator guideCareful participation
Key custody, permissions, phishing resistance, and the habits that reduce avoidable mistakes.
Read the security guide
Reading sequence
- Define the term in the glossary.
- Read the mechanism-level explanation.
- Look at a public example without treating it as a guarantee.
- Review the limits and the date of the article.
This sequence helps readers avoid confusing a product interface with the underlying protocol.
Guide principles
Specific language
We use “can,” “records,” and “observed” when those are the accurate verbs. Stronger claims need stronger evidence.
Visible boundaries
Articles identify what they do not cover, especially when a subject touches security, law, or financial decisions.
A note for new readers
Technical confidence grows from knowing where to look next, not from pretending every answer is simple.
Use the cross-references in each guide and contact the desk when a definition appears unclear or outdated.