In brief
A compact public registry of the source classes used by the source-linked reference.
Purpose#
This page lists the core public sources used by the source-linked reference. It does not replace the complete source registry; it gives contributors a compact starting point.
Registry#
| Source ID | Title | Authority class | Status | Public location |
|---|---|---|---|---|
| WIKI-HOME | Kaspa Wiki Home | kaspa-docs-orientation | current-needs-periodic-refresh | https://wiki.kaspa.org/ |
| WIKI-KASPA | Kaspa | kaspa-docs-orientation | current-needs-periodic-refresh | https://wiki.kaspa.org/en/kaspa |
| WIKI-GETTING-STARTED | Getting Started | kaspa-docs-orientation | current-needs-periodic-refresh | https://wiki.kaspa.org/en/getting-started |
| WIKI-FAQ | FAQ | kaspa-docs-orientation | current-needs-periodic-refresh | https://wiki.kaspa.org/en/faq |
| RK-REPO | rusty-kaspa | implementation | current-needs-commit-refresh | https://github.com/kaspanet/rusty-kaspa |
| KIPS-REPO | Kaspa Improvement Proposals | KIP repository | current-needs-commit-refresh | https://github.com/kaspanet/kips |
| DOC-TOCCATA | Toccata Docs | official-docs | current-needs-periodic-refresh | https://docs.kaspa.org/toccata |
| TOOL-SILVERSCRIPT-REPO | SilverScript | official-tooling | current-needs-commit-refresh | https://github.com/kaspanet/silverscript |
| TOOL-VPROGS-REPO | vProgs | official-tooling | current-needs-commit-refresh | https://github.com/kaspanet/vprogs |
| PAPER-GHOSTDAG | PHANTOM/GHOSTDAG Paper | research-paper | research | https://eprint.iacr.org/2018/104 |
| PAPER-GROTH16 | Groth16 Paper | research-paper | research | https://eprint.iacr.org/2016/260 |
Expanded Registry Method#
The source registry is a navigation layer over public evidence. It should answer three questions for every source ID: where can the community access it, what kind of authority does it have, and what claims should not be supported by it?
This matters because not all public sources carry the same weight. A GitHub implementation path can support source behavior when read at the relevant commit. A docs page can support documented public guidance. A release page can support release status. A paper can support research framing. A tooling repository can support tool behavior. The registry should make those boundaries visible so future website pages do not cite a source merely because it is convenient.