In brief
Transaction evidence moves through layers: wallet intent, node or mempool response, block inclusion, virtual processing, and accepted UTXO effects.
What this page explains#
Turn ownership, UTXOs, transaction format, mass/fees, mempool admission, and accepted evidence into one source-backed learning path. This page sits in Transactions, UTXO, Fees, And Mempool. 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 follows a transaction from ownership model to structure, signing, validation, mempool admission, template selection, and accepted-state evidence. The main danger it prevents is collapsing all transaction states into one word.
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-UTXO, DOC-TOCCATA-TX-V1, RK-TX, RK-UTXO-ENTRY, RK-UTXO-DIFF. 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 Transactions, UTXO, Fees, And Mempool, the model is built around these anchors: Transaction stages must be named separately: built, signed, validated, admitted, templated, mined, accepted, or reflected in UTXO state; Transaction ID, full hash, sighash, payload digest, mass, and storage mass are distinct commitment or resource surfaces; Mempool insertion, block template selection, and accepted transaction evidence are separate states; RPC and indexer representations expose observations and fields but do not replace protocol source review; Contributor review follows structs, serialization, hashing, signing, validation, mempool, templates, virtual processing, and RPC. 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. Transaction stages must be named separately: built, signed, validated, admitted, templated, mined, accepted, or reflected in UTXO state. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
2. Transaction ID, full hash, sighash, payload digest, mass, and storage mass are distinct commitment or resource surfaces. Toccata-era transaction fields are application surfaces, so the guide must trace them through structs, serialization, hashing, signing, RPC, wallet tooling, mempool policy, and accepted evidence. The risk is not only invalid construction; it is a tool silently dropping or misunderstanding a field that the application relies on.
3. Mempool insertion, block template selection, and accepted transaction evidence are separate states. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
4. RPC and indexer representations expose observations and fields but do not replace protocol source review. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
5. Contributor review follows structs, serialization, hashing, signing, validation, mempool, templates, virtual processing, and RPC. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
This mechanism section follows a transaction through construction, identity, signing, validation, mempool policy, block templates, and accepted evidence. The stage must be named before the claim is reused.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check Transaction stages must be named separately: built, signed, validated, admitted, templated, mined, accepted, or reflected in UTXO state. | Use WIKI-UTXO, DOC-TOCCATA-TX-V1, RK-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 2 | Check Transaction ID, full hash, sighash, payload digest, mass, and storage mass are distinct commitment or resource surfaces. | Use WIKI-UTXO, DOC-TOCCATA-TX-V1, RK-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 3 | Check Mempool insertion, block template selection, and accepted transaction evidence are separate states. | Use WIKI-UTXO, DOC-TOCCATA-TX-V1, RK-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 4 | Check RPC and indexer representations expose observations and fields but do not replace protocol source review. | Use WIKI-UTXO, DOC-TOCCATA-TX-V1, RK-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
| 5 | Check Contributor review follows structs, serialization, hashing, signing, validation, mempool, templates, virtual processing, and RPC. | Use WIKI-UTXO, DOC-TOCCATA-TX-V1, RK-TX; name the stage: built, signed, validated, admitted, templated, mined, or accepted. |
When using this page for a transaction claim, name the stage precisely: built, signed, validated, admitted to a mempool, included in a template, mined, accepted, or reflected in a UTXO change. Each stage has a different evidence surface and should not be collapsed into a single success word.
Expanded Category Guide#
This category carries the transaction evidence path from inputs/outputs and signing through validation, mempool, templates, accepted evidence, UTXO diffs, RPC, and indexer representation.
Use this category as a curated path. Start with the category README to understand the boundary, then read the mechanism pages, then follow source-path or open-gap pages for claims that need stronger evidence. If a page contains needs checking rows, keep those claims visibly unresolved until a reader reads the cited public source directly.
The category should not be treated as final authority by folder name alone. The authority comes from page Source Notes, Source Lists, public URLs, and the status labels attached to each claim.
Related Pages#
- transactions-utxo-mempool
- 01-utxo-model
Topic pages#
- UTXO Model And Ownership: Kaspa ownership is best taught as spendable outputs rather than account balances.
- Transaction Structure: A transaction is a structured object interpreted by validation, hashing, signing, mempool, RPC, wallet, and block-template code.
- Inputs, Outputs, And Outpoints: Inputs, outputs, and outpoints are the vocabulary of UTXO spending.
- Transaction ID, Full Hash, Payload Digest, And Rest Digest: Txid and full transaction hash must be explained separately because they answer different identity and commitment questions.
- Sighash And Signing Commitments: Sighash defines what a signature commits to and is one of the highest-risk wallet/developer surfaces.
- Mass, Fees, And Storage Mass: Mass is resource accounting, not just a fee-size synonym.
- Transaction Validation Layers: Transaction validation is layered, and each layer rejects different classes of mistakes.
- Mempool Policy, Orphans, RBF, And Relay: Mempool admission is local node policy and not final chain acceptance.
- Block Templates And Transaction Selection: Block templates turn node state and mempool candidates into miner work.
- Accepted Transaction Evidence: Accepted evidence is the boundary between transaction intent and consensus-visible consequence.
- RPC, UTXO Index, And Explorer Boundaries: RPC and indexer shapes expose transaction data to tools, but they do not replace consensus source review.
- Source Path For Transaction Contributors: Transaction contributors need a guided source order so a change does not silently break hashing, signing, mempool policy, RPC, or accepted evidence.
Topic notes#
This category is accepted when the subpages explain the actual topics, not merely the source links. Each subpage carries public source IDs, claim labels, Open Questions, and a path from first contact into source review.