FAQ

Purpose#

This FAQ answers the first questions directly, then points to the page that owns the mechanism. It follows the Kaspa documentation's question-led habit while adding claim labels and source boundaries.

What should I understand first?#

Understand that Kaspa is a proof of work network whose guide path moves from blockDAG structure to GHOSTDAG ordering, virtual state, and UTXO evidence. Do not start with Toccata, ZK, or tooling before those anchors are clear.

Is seeing a transaction in a wallet the same as consensus acceptance?#

No. Wallet construction, RPC submission, mempool admission, block-template selection, mined block inclusion, accepted data, UTXO diff, and indexer/API observation are different stages.

Why does this guide talk so much about sources?#

Because current protocol claims, proposed KIP claims, research claims, and local project lessons need different evidence. The guide is meant to be useful for public contribution, so public URLs and source IDs matter.

Can I treat Toccata, covenants, ZK, SilverScript, and vProgs as finished production behavior?#

Not from this guide alone. Those topics need status labels. Some rows are current-source, some are proposed, some are research or tooling, and some remain Open Questions.

What does this source-linked reference still need?#

It needs the remaining source checking rows to be read directly against public sources. Until then, the safe release posture is a source-linked reference with visible open research gaps.

Expanded FAQ Method#

The FAQ should answer practical confusion directly, then send the mechanism to the right page. A short answer can be useful, but the page must avoid turning short answers into overclaims. If the question asks whether a wallet observation proves acceptance, the answer must route to the transaction lifecycle. If the question asks whether Toccata, covenants, or ZK are current production behavior, the answer must route to status labels and the high-risk topic pages. If the question asks where to start, the answer must route to first-contact and working-model pages before source paths.

This page follows the Kaspa documentation habit of question-led explanation, but it adds stricter source boundaries. The FAQ is allowed to orient the reader. It is not allowed to close high-risk implementation claims unless the cited source class can support the exact wording.

Use this FAQ as a triage page. It should reduce confusion, not replace the detailed pages. Each answer should make the next click obvious and should preserve uncertainty where the check still requires direct source checking.