Sources and attribution
What this site trusts, and why
Every claim's source lives next to the claim, ranked by tier: code and releases settle it, interviews and libraries explain it, social posts only point at it.
Source hierarchy
What settles a claim
| Tier | What it settles | Where that is |
|---|---|---|
| 1. Code, KIPs, releases | Whether a feature exists, and when it turned on. | rusty-kaspa, the KIP repo, release tags |
| 2. A mainnet node or public API | What a number is right now, with the moment it was read. | api.kaspa.org, the block explorer |
| 3. Papers, docs, interviews | Nothing on its own. It explains why something was designed the way it was. | Kaspa Research, docs.kaspa.org, HashdagKaspa co-founder Yonatan Sompolinsky's research writing site, where he lays out design ideas ahead of protocol work. |
| 4. Posts and dashboards | Nothing. They point at something else worth checking. | X accounts, aggregators, community recaps |
Nothing on this site counts as shipped on tier 3 or 4 alone. A number without a read date is treated the same way.
Which source answers which question
| If the question is | Go to |
|---|---|
| Origin and fair launch | genesis.rs, and Hashdag's own launch-plan post |
| Whether a feature is live | release tags and the KIP files |
| What the chain reads right now | the blockDAG endpoint and the supply endpoint |
| Throughput limits and capacity | params.rs, the consensus constants themselves |
| Emission and supply | coinbase.rs, and the wiki's tokenomics page |
| Price, hash rate, mining cycle | the hash-rate endpoint and CoinGecko, each with the date it was read |
| How consensus works | Kaspa Research and its question archive |
| Toccata activation and timing | the v2.0.0 release and a dated mainnet DAA reading; use the Toccata guide for operator steps and changed fields |
| What a transaction can carry | the payload docs and the acceptance docs |
| Running a node, indexing, history | the node docs and the REST reference |
| vProgs and app architecture | the vProgs repo and the programmability docs |
| DAGKnight | KIP-2, still Proposed, and hashd.ag |
| RTDHashdag's framing: Bitcoin-style proof-of-work security operating in real time. and TangVMA proposed add-on, not yet built, that would let a smart contract watch outside data and trigger itself instead of waiting for someone to trigger it by hand. | hashd.ag/raw. Research writing, so tier 3. |
| A roadmap date | There is no tier 1 or 2 source for one. This site labels those Research and says so. |
Every claim's own links sit on the page that makes it: Build on Kaspa, Status, KIPs and KCCs, the origin story, how Kaspa compares, and What is Kaspa.
Excluded on purpose
Why kaspa.org's marketing pages are not a source
Checked 10 September 2026: Lore still calls Toccata the next hardfork, although it activated on mainnet in June. Build has since become developer documentation and no longer carries its earlier TN12-before-mainnet wording. For activation, use the release and score records. wiki.kaspa.org and docs.kaspa.org remain useful technical sources.
Community forums, social mirrors, and builder accounts to watch
kas-smiths.org, the KCC forum, feeds kaspanet/kccs and stays proposal-stage until merged as a KIP. kaspa.social mirrors Kaspa-related X posts as a scrape, not a curated feed: verify any claim against the original account. KASmedia (kasmagazine.com) runs recaps, interviews, and community context.
Builder accounts:
Found a stale claim? Open a correction.