Plain-English guide to Kaspa, fast Proof of Work, status lanes, sources, glossary, and crypto basics.
This is not an official Kaspa website and it is not investment advice. It is written to be useful for:
- readers who want a clear entry point,
- readers checking what is live, what is roadmap, and what is research,
- builders and researchers checking sources,
- search and retrieval systems,
- people trying to separate live Kaspa facts from roadmap, research, and speculation.
- people trying to separate real crypto use cases from forced blockchain/token use cases.
For contributor and editorial context, start with CONTENT_BRIEF.md.
kaspaexplained.com
The root CNAME file must contain exactly:
kaspaexplained.com- Repository:
parker2017code/kaspa-explained - Visibility: public
- Pages source: deploy from branch
- Branch:
main - Folder:
/root - Custom domain:
kaspaexplained.com - Enforce HTTPS when GitHub makes it available
For Namecheap or equivalent DNS:
- Apex
@A records:185.199.108.153185.199.109.153185.199.110.153185.199.111.153
wwwCNAME:parker2017code.github.io
Do not point www to the repository name.
Use primary or near-primary sources first:
Community portals, media sites, learning libraries, interviews, and recaps are useful source material, but they are not official protocol authority. Status-sensitive claims should be anchored in code, releases, KIPs, research papers, protocol documentation, or direct implementation notes from core technical contributors.
- https://hashd.ag/ - Hashdag / Yonatan Sompolinsky's writing archive
- https://hashd.ag/raw - raw archive view
- https://medium.com/@michaelsuttonil/kaspa-covenants-toccata-hard-fork-outlook-a4d81a40900c
- https://github.com/kaspanet/rusty-kaspa
- https://github.com/kaspanet/rusty-kaspa/releases
- https://research.kas.pa/
- https://qa.kas.pa/
- https://kasmedia.com/ - KASmedia articles, interviews, recaps, and theory posts; useful community context, not primary activation evidence
- https://kaspa.com/learn-kaspa - Kaspa.com Learn Kaspa / Kaspa Facts intro and intermediate learning library
- Bitcoin Takeover S16 E41 Yonatan Sompolinsky interview and transcript:
- https://www.youtube.com/live/GaJmYV8OHfQ
- https://podscan.fm/podcasts/bitcoin-takeover-podcast/episodes/s16-e41-yonatan-sompolinsky-on-bitcoin-kaspa-amp-proof-of-work
- Use for site framing: generalized Nakamoto consensus, current GHOSTDAG, future DAGKnight/vProgs, pruning nuance, and broader crypto context. Do not treat roadmap discussion as live activation evidence.
- Kaspa: Mining the Internet Yonatan Sompolinsky Tokenize talk
- https://kasmedia.com/article/weeklyknight-08282025 - recap of the Bitcoin Takeover Yonatan interview, with selected quotes and exact YouTube live URL
- https://www.youtube.com/watch?v=VIZGKoIaGR0 - Yonatan Sompolinsky Oxford Union address
- https://www.youtube.com/watch?v=S1dS1xvvFss - Yonatan Sompolinsky Oxford Union Q&A
- https://www.youtube.com/watch?v=xHlOcR1x2tU - Michael Sutton vProgs talk
- https://www.youtube.com/watch?v=p21KDrKEhB8 - Michael Sutton on Crescendo, based rollups, and DAGKnight
- https://github.com/kaspanet/kaspa-python-sdk - standalone Kaspa Python SDK repo for builder tooling and Python integration evidence
- https://github.com/kaspanet/kaspa-python-sdk/releases/tag/v1.1.0 - Python SDK v1.1.0 release with UtxoProcessor/UtxoContext and GetVirtualChainFromBlockV2
- kaspanet/rusty-kaspa#860 - TxIndex PR; optional transaction index and GetTransaction RPC evidence while open
- kaspanet/rusty-kaspa#930 - Fast Trusted Relay WIP/draft PR; infrastructure experiment, not stable release evidence
- https://kasmedia.com/article/ori-interview
- https://kasmedia.com/article/theweeklyknight081725
- https://kasmedia.com/article/weeklyknightl12s-and-pows
- https://kasmedia.com/article/moog-synthesizers-and-kaspa
- https://kaspa.org/ - current public Kaspa/KasMedia entry point, genesis-proof framing, and links into wallets, builder resources, explorer, GitHub, and DAG visualizer
- https://kaspa.org/lore - concise current public summary for Kaspa history, fair-launch framing, RTD, Crescendo, Toccata, DAGKnight, and longer-roadmap context; verify status-sensitive details against primary sources
- https://kaspa.org/build - current builder entry point for Rusty Kaspa, WASM SDK, docs, public node access, REST API, Docker, DB dumps, testnet, KIPs, Silverscript, vProgs, community infra, and R&D links
- https://kaspa.org/hodl - current wallet and self-custody entry point; useful for beginner custody flow and exchange-delay caveats, not investment advice
- https://docs.kaspa.org - current Kaspa builder docs entry point for programmability, integration, wallet flows, payloads, accepted transactions, and node infrastructure
- https://docs.kaspa.org/integrate/getting-started - official SDK/RPC starter path for JavaScript, Rust, and Python
- https://docs.kaspa.org/programmability - official builder routing for Covenants, Based Apps, Inline ZK, and future Full vProgs; use for model selection, not activation claims by itself
- https://docs.kaspa.org/integrate/transaction-payload - official payload guide for application data within standard mempool mass limits
- https://docs.kaspa.org/integrate/accepted-transactions - official accepted-transaction ingestion guide
- https://docs.kaspa.org/integrate/kaspa-node - official node integration guide
- https://docs.kaspa.org/references - official integration reference page
- https://kaspa.aspectron.org/docs/ - WASM SDK docs
- https://kaspa.aspectron.org/docs/classes/RpcClient.html - RpcClient constructor and submitTransaction request-shape docs
- https://kaspa-mdbook.aspectron.com/transactions/signing.html - Aspectron signing guide for SDK transaction signing and request-style submit
- https://api.kaspa.org/docs - best-effort community REST API docs
- https://kaspa.aspectron.org/rpc/pnn.html - Public Node Network docs
- https://hub.docker.com/r/kaspanet/rusty-kaspad - Rusty Kaspa Docker images
- https://db-dl.kaspa.org - explorer/API database dumps
- https://deepwiki.com/kaspanet/rusty-kaspa - generated Rusty Kaspa code navigation; useful for orientation, not source of truth
- https://github.com/supertypo/simply-kaspa-indexer - community indexing project
- https://github.com/kaspanet/dnsseeder - Kaspa DNS seeder
- https://github.com/aspectron/khost - node-hosting/community capacity tooling
- https://github.com/K-Kluster/kaspa-js - community JavaScript tooling
Active public technical accounts can be useful for discovery and replies:
- https://x.com/hashdag
- https://x.com/michaelsuttonil
- https://x.com/OriNewman
- https://x.com/hus_qy
- https://x.com/IzioDev
- https://x.com/coderofstuff_
- https://x.com/FreshAir08
- https://x.com/eliottmea
- https://x.com/KasSigner
Read public replies as well as top-level posts. Do not use stale team pages, recycled handle lists, or X alone for activation dates, shipped-feature claims, exchange claims, or protocol guarantees.
/- audience-routed Kaspa overview, real-time Proof-of-Work framing, zero-to-one crypto context links, status lanes, common-misconception routing, and blockDAG visual./start-here.html- true beginner router for readers who know nothing about crypto, market value, coin categories, tradeoffs, or Kaspa./crypto-from-zero.html- zero-to-one curriculum: records, keys, transactions, blocks, consensus, security, mining, staking, tokens, UTXO/account models, and Kaspa./why-crypto-has-value.html- market-value explainer for token necessity, prices, open markets, market cap, speculation, launch design, and who benefits./why-are-there-so-many-coins.html- category bridge explaining why Bitcoin, Ethereum, stablecoins, exchange tokens, payment coins, privacy coins, memes, infrastructure, and Kaspa are different assets./coin-atlas.html- coin-category atlas for major crypto assets and value stacks, including BTC, ETH, stablecoins, SOL, BNB, XRP, LTC, BCH, XMR, DOGE, LINK, and KAS./tradeoff-map.html- beginner tradeoff map for speed, security, decentralization, privacy, scaling, nodes, ASICs, staking, launch design, and Kaspa./analyze-any-coin.html- practical checklist for token necessity, supply, launch, security, validation, liquidity, market cap, risks, and who benefits./crypto-history.html- problem-first history map from digital cash and Bitcoin through Ethereum, ICOs, scaling conflicts, DeFi, stablecoins, rollups, and Kaspa./kaspa-in-one-screen.html- compact shareable Kaspa summary: what it is, what is live, why it matters, what is not live, common boundaries, and what would strengthen or weaken the case./adoption-metrics.html- non-price adoption and business lens for wallets, nodes, mining, fees, liquidity, builders, integrations, and post-Toccata app signals./application-layer.html- application-layer opportunity map for what builders can use now and what Toccata, vProgs, RTD, and research lanes may enable later./builder-guide.html- builder-specific programmability router for covenants, based apps, inline ZK, future full vProgs, SDKs, and infrastructure evidence./what-crypto-is-good-for.html- general crypto reality check for where crypto is useful and where a normal database, payment system, court, or trusted operator is better./status.html- compact shipped-vs-roadmap status page with a code-grounded implementation-evidence section./overview.html- 90-second first-reader overview./faq.html- direct answers to common Kaspa status, concept, speed, TPS, finality, testnet, roadmap, and ecosystem-tooling questions./why-kaspa-matters.html- bridge page from the general crypto reality check to Kaspa's live Proof-of-Work blockDAG settlement, base real-time decentralization framing, and future coordination-market / vProgs direction./where-kaspa-fits.html- comparison page and scannable table for Kaspa's lane among Bitcoin, Ethereum, Solana, XRP, BNB, TRON, stablecoins, exchange chains, meme assets, smart-contract L1s, Chainlink, and app-specific chains./knowledge-map.html- ordered concept map for average crypto readers, with supporting references and a status-labeled DAGKnight/vProgs comparison./glossary.html- compact plain-English glossary for common Kaspa terms./search.html- static page-map search for concepts, audiences, status lanes, and source terms./sources.html- public source hierarchy, external reference map, Kaspa.com Learn Kaspa topic index, and human/LLM file map./about.html- editorial policy, disclosures, and correction process./404.html- GitHub Pages custom not-found page that routes users back to search, status, and Start Here./CLAIMS.yml- lightweight status ledger for sensitive live/targeted/roadmap/research claims./CONTRIBUTING.md- correction and contribution rules for claim status, sources, local checks, and wording changes.
The scripts/ folder contains the local and CI validation gates:
scripts/check-site.shchecks the expected public pages and support files, custom domain, sitemap/canonical links, skip links, social metadata,dateModifiedmetadata, nav wiring, local anchors, sensitive claim markers, forbidden overclaim phrases, and nav synchronization.scripts/check-nav-sync.shcompares the copied static nav links across every HTML page so manual pages do not drift.scripts/check-links.shaudits external links for routine maintenance and runs separately from the push gate.
Run the static check before publishing:
bash scripts/check-site.shThe check verifies the custom domain, sitemap/canonical links, public pages,
skip-link targets, social-card metadata, date metadata, local anchors, the PNG
OpenGraph image, sensitive-claim consistency markers, and CLAIMS.yml
forbidden-copy phrases. It also runs scripts/check-nav-sync.sh so the
duplicated static nav does not drift between pages. The same check runs in
GitHub Actions on push, pull request, and a weekly schedule.
For public copy, layout, or framing changes, also check:
- mobile and desktop screenshots for affected pages,
- no text overlap in diagrams, tables, cards, axis labels, buttons, or hero areas,
- medium authority and medium visual weight in public copy,
llms.txt,CLAIMS.yml,sources.html, andCONTENT_BRIEF.mdwhen status/source boundaries change,- GitHub About metadata when the public framing or README intro changes,
- live HTML after GitHub Pages deploys.
The fast-PoW comparison graphic on why-kaspa-matters.html needs special care: it should separate inclusion speed from explicit vote/stake coordination and should not imply instant finality or a simple "stronger confirmation" ranking.
External links are audited separately:
bash scripts/check-links.shThat audit runs weekly and can be triggered manually in GitHub Actions. It is separate from the normal push check so temporary third-party outages do not block routine content fixes.
Content is licensed under CC BY 4.0. Code, CSS, scripts, and workflow files are
licensed under MIT. See LICENSE.md.
Do not flatten everything into "live."
- Live: Proof of Work blockDAG, UTXO model, GHOSTDAG, Crescendo 10 BPS era.
- Ecosystem live: KRC20 tokens and KRC721-style NFTs through ecosystem tooling, wallets, indexers, metadata, and APIs. Required deploy/mint gas fees are miner fees, while wallets or frontends may charge separately. Useful for tokens, coupons, event credits, rewards, access passes, and collectibles, but not native Kaspa smart contracts or Toccata/vProgs activation.
- Near-term track: Toccata/Covenants++ as the L1 hard-fork path for concrete rules such as spend constraints, asset rules, covenant IDs, Silverscript, ZK-facing verification work, sequencing commitments, native-asset groundwork, and standalone based-zk experiments. Treat this as targeted until activation is confirmed by primary sources.
- Architecture / roadmap: vProgs as apps that prove richer logic while sharing Kaspa ordering, plus app-level verifiable programs, computational-DAG metadata, prover-backed execution, Kaspa-native DeFi rails, native-feeling developer experience, and eventual synchronous composability.
- Research / speculative: DAGKnight activation, 100 BPS with probabilistic predecessor selection, app-level miner attestation/oracle incentive designs, TangVM-style extensions, Proof of Useful Work, post-quantum migration.
Kaspa programmability should be framed as concrete use first, neutral primitives second. Say what the user or app is trying to do: lock funds, enforce a vault rule, create an asset, route a payment, fund a public good, resolve a market, attest to an event, or prove app logic. Then explain that the protocol should expose durable L1 surfaces while apps define incentives, semantics, oracle sources, legal/risk constraints, and user-facing products. Apply that rule to attestations, prediction markets, DePIN freshness markets, portfolio automation, launch rails, AI-agent task boards, and DeFi.
Toccata/vProgs split: Toccata enables L1 covenant programming and standalone based-zk app foundations. Hans Moog's kaspanet/vprogs repo is early compatible runtime work for based computation on Kaspa, not proof that full synchronous vProgs are live. Avoid framing Kaspa as needing independent Ethereum-style L2s; the direction is L1-first shared sequencing, settlement, commitments, and verification.
Editorial voice: explain Kaspa in first-principles everyday language for the page's intended reader, then give deeper readers clear routes into technical, adoption, app-design, and source-checking material. Apply Concrete-First Translation: "one shared record without one operator" before "credible shared state," "apps that prove their rules" before "verification-oriented programmability," and "fast mined ordering" before "settlement layer." The target is not one page that serves every reader equally; it is a site with clear paths from absolute beginner through crypto-curious reader, crypto-native comparer, Bitcoin/PoW reader, adoption researcher, app designer, protocol expert, community educator, journalist, and source-checking reviewer.
Startup verification: before substantive edits, recheck current web/source state for drift-prone Kaspa facts such as Toccata activation, DAGKnight, vProgs, native DeFi, RTD-derived attestations/oracles, TangVM, Proof of Useful Work, and date windows. Keep public pages clean of visible verification boxes unless explicitly requested.
Builder verification rule: a local txid or signed object is not accepted app state. Builder-facing pages should tell readers to fetch accepted transaction evidence, record SDK/node/network/endpoint details, and label failures narrowly as bad config, stale tooling, submit mismatch, or confirmed consensus rejection.
This is a plain static site. A quick smoke check is enough:
python3 -m http.server 4173Then open http://127.0.0.1:4173/.