In brief
Timeline material gives dates and sequence without converting history into current operational advice.
What this page explains#
Timeline material gives dates and sequence without converting history into current operational advice. This page sits in Foundations. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category gives the reader durable handles before any source walk begins. It keeps identity, motivation, vocabulary, history, and first practical routes separate so a later consensus or developer page does not have to carry every introduction at once.
The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0, RK-RELEASE-V2-0-1. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.
How to think about it#
The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.
For Timeline, the model is built around these anchors: historical pages use dates and status labels; release events are linked to release notes or source docs when behavior matters; project status can age quickly and must carry a last-checked date; history and current protocol behavior are separated; timeline entries should point readers to source pages when a feature is still relevant. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.
How it works#
1. historical pages use dates and status labels. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
2. release events are linked to release notes or source docs when behavior matters. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
3. project status can age quickly and must carry a last-checked date. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
4. history and current protocol behavior are separated. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
5. timeline entries should point readers to source pages when a feature is still relevant. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
This mechanism section is intentionally shallow-to-deep: it gives the first usable explanation, then names the later page where source-level mechanics belong. Foundation pages must not smuggle in covenant, ZK, or readiness claims unless the Source List and Source Notes support that exact bridge.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check historical pages use dates and status labels. | Use WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 2 | Check release events are linked to release notes or source docs when behavior matters. | Use WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 3 | Check project status can age quickly and must carry a last-checked date. | Use WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 4 | Check history and current protocol behavior are separated. | Use WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 5 | Check timeline entries should point readers to source pages when a feature is still relevant. | Use WIKI-TIMELINE, WIKI-PREHISTORY, RK-RELEASE-V2-0-0; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
When using this page for a wiki article, keep orientation separate from mechanics. The page can name the path and the next concept, but detailed wallet, node, mining, consensus, transaction, or Toccata behavior belongs in the downstream page that carries the stronger Source List.
Related Pages#
- kaspa-docs-flow-and-contribution-style
- foundations
- prehistory